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

JENKINS-57341 - Update plugin archetype for Java 11 #41

Merged
merged 13 commits into from Jun 19, 2019
Merged

JENKINS-57341 - Update plugin archetype for Java 11 #41

merged 13 commits into from Jun 19, 2019

Conversation

MarkEWaite
Copy link
Contributor

JENKINS-57341 Update plugin archetype for Java 11

Update jenkins.version and java.level so that plugins generated from the archetype support Java 8 and Java 11.

Update other dependencies to allow Java 8 and Java 11.

Base on the latest long term support release so that the plugin author
can choose to develop with either Java 8 or Java 11.
Parent pom versions prior to 3.43 do not have correct settings for
javadoc generation.
Use parent pom 3.43 and require Jenkins version 2.164.1.  That will
allow development with either Java 8 or Java 11.
workflow-support 3.2 is required for Java 11 compile.
Adding workflow-support 3.2 requires script-security and scm-api.
workflow-api 2.30 and workflow-step-api 2.19 required for upper bounds dependencies.
structs 1.18 for upper bounds dependencies
@MarkEWaite
Copy link
Contributor Author

MarkEWaite commented May 6, 2019

I don't understand why the pull request build is failing. I've run it on my Debian 10 machine with Java 8 update 212 and it runs successfully. It fails with Java 11 on my Debian 10 machine, but the docker image is Java 8, so that failure seems unlikely to be happening here.

Still no hint why the job fails on the CI server and passes consistently with the same command in my environment. The failed to initialize exploded war has happened in the past when the CI server was out of disc space, but always included an out of disc space message in the log.

Maven 3.5.4 includes changes for Java 11 compatibility.
@jglick jglick self-requested a review June 18, 2019 14:23
@jglick
Copy link
Member

jglick commented Jun 18, 2019

When I get a chance I can try to reproduce the test error.

@jglick
Copy link
Member

jglick commented Jun 19, 2019

After this gets merged, @oleg-nenashev I guess we can set up @dependabot here? At least I think it will offer to update the parent POM versions.

@oleg-nenashev
Copy link
Member

oleg-nenashev commented Jun 19, 2019 via email

<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>script-security</artifactId>
<version>1.39</version>
<scope>test</scope>
Copy link
Member

Choose a reason for hiding this comment

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

I think you can omit the scope here, but it is probably fine.

@jglick jglick merged commit 32a0c68 into jenkinsci:master Jun 19, 2019
@oleg-nenashev oleg-nenashev changed the title Update plugin archetype for Java 11 - JENKINS-57341 JENKINS-57341 - Update plugin archetype for Java 11 Jun 19, 2019
@MarkEWaite MarkEWaite deleted the allow-java-11-not-java-7 branch July 31, 2019 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants