Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java 11 readiness: build using recommended configurations #92

Merged
merged 2 commits into from
Apr 18, 2019

Conversation

batmat
Copy link
Member

@batmat batmat commented Mar 25, 2019

Using the right variations of Jenkins versions, JDK 8 & 11, Windows/Linux...

For Java 11 readiness, apply recommended configuration:
https://wiki.jenkins.io/display/JENKINS/Java+11+Developer+Guidelines#Java11DeveloperGuidelines-MakesureyourpluginistestedinContinuousIntegrationonJava8andJava11atthesametime

And fixing what was revealed through this.

@jenkinsci/java11-support

Using the right variations of Jenkins versions, JDK 8 & 11,
Windows/Linux...
@batmat batmat closed this Mar 27, 2019
@batmat batmat reopened this Mar 27, 2019
@batmat batmat closed this Mar 27, 2019
@batmat batmat reopened this Apr 4, 2019
Picking up jenkinsci/plugin-pom#173
Also fix actual Javadoc error on JDK 11: <tt> is not allowed anymore
@batmat batmat changed the title [WIP] Java 11 readiness: build using recommended configurations Java 11 readiness: build using recommended configurations Apr 11, 2019
@batmat
Copy link
Member Author

batmat commented Apr 18, 2019

@dwnusbaum could you please consider merging this? Thanks!

@dwnusbaum dwnusbaum merged commit c0d800a into jenkinsci:master Apr 18, 2019
@batmat batmat deleted the java11-readiness branch April 18, 2019 14:00
@@ -157,7 +157,7 @@ private File getLogFile() throws IOException {
}

/**
* Used from <tt>console.jelly</tt> to write annotated log to the given output.
* Used from <code>console.jelly</code> to write annotated log to the given output.
Copy link
Member

Choose a reason for hiding this comment

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

{@code …} is preferred BTW.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants