Skip to content

Update OSS release plugin version#501

Merged
lbalmaceda merged 3 commits intomasterfrom
upd-plugin
Jul 2, 2021
Merged

Update OSS release plugin version#501
lbalmaceda merged 3 commits intomasterfrom
upd-plugin

Conversation

@lbalmaceda
Copy link
Copy Markdown
Contributor

Changes

This PR updates the OSS release plugin version to 0.16.0, which makes use of a newer Javadoc HTML template.

I also removed the bintray plugin which is no longer used.

@lbalmaceda lbalmaceda added this to the v3-Next milestone Jun 29, 2021
@lbalmaceda lbalmaceda requested a review from a team as a code owner June 29, 2021 15:02
def javaVersion = 8
java {
toolchain {
languageVersion = JavaLanguageVersion.of(11)
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't seem to be needed even when the library outputs a multi-jar with module support.

image

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jimmyjames can you please double-check this one on your side? for me it keeps compiling after running something like ./gradlew clean build javadoc publishMavenJavaPublicationToMavenLocal --rerun-tasks

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, if you are running gradle with java 11 it will work. Using a toolchain you should be able to run gradle with say, java 8, and gradle will use the specified toolchain version for tasks. However the custom compileModuleInfoJava task does not appear to be respecting the toolchain, instead using the java version running gradle. Since our CI runs on 11 and this issue exists outside this change, I'd at least add a comment to the custom task with a todo to use the toolchain version so we can run the build with a different java version.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

I tried changing my local JDK back to JDK 8 and ran the command above. The build is still successful. Do you think the comment is necessary? And, would that be for the "compileJava" task?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per our discussion today, I'll add this block back to prevent potential issues when running the build using JDK 8.

def javaVersion = 8
java {
toolchain {
languageVersion = JavaLanguageVersion.of(11)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, if you are running gradle with java 11 it will work. Using a toolchain you should be able to run gradle with say, java 8, and gradle will use the specified toolchain version for tasks. However the custom compileModuleInfoJava task does not appear to be respecting the toolchain, instead using the java version running gradle. Since our CI runs on 11 and this issue exists outside this change, I'd at least add a comment to the custom task with a todo to use the toolchain version so we can run the build with a different java version.

@lbalmaceda lbalmaceda requested a review from jimmyjames July 1, 2021 17:00
@lbalmaceda lbalmaceda merged commit c9dff2a into master Jul 2, 2021
@lbalmaceda lbalmaceda deleted the upd-plugin branch July 2, 2021 07:30
@lbalmaceda lbalmaceda modified the milestones: v3-Next, 3.18.0 Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants