Update plugin parent POM #83
Conversation
|
As in jenkinsci/checks-api-plugin#163 (comment), you cannot have your CI build set up to use Java 8 but your Maven build set up to use Checkstyle 10 (which requires Java 11). |
|
jenkinsci/analysis-pom-plugin#420 should be reverted. |
|
Actually this plugin is deprecated for almost a year now. I'm not sure if it makes sense to spent any effort here anymore. It has been superseded by https://github.com/jenkinsci/popper2-api-plugin |
|
Then finish jenkinsci/bom#571. |
This commit will not be tested in the CI build for this PR, since I do not have write access to this repository.
|
Java 8 removed from Jenkinsfile in commit fa87ca5. This commit will not be tested in the CI build for this PR, since I do not have write access to this repository. |
Well, I tried my best but it seems that we still have a deadlock in the JUnit plugin. Hopefully, it will be resolved if the UI tests will be merged. My changes (that are in production in all other plugins) are one year old now. |
I have been attempting to run PCT tests in
jenkinsci/bomagainst Java 17 and newer versions of PCT, and this plugin is running into failures because its parent POM is too old. This PR updates the parent POM to the latest build toolchain from jenkinsci/analysis-pom-plugin#446 to facilitate Java 17 compatibility testing and PCT updates injenkinsci/bom.