EnforceBytecodeVersion
fails with "Restricted to JDK 11 yet […] contains […] targeted to JDK 17" (second try)
#583
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #582 (comment); the previous fix was not tested properly and did not actually work. I tried for several hours to figure out how to update the Enforcer configuration from a different mojo but failed. Things I tried:
MojoExecution
object uses a different copy of the XML)enforcer.rules
Maven property (did not work, as that property does not support rules that take parameters)MojoExecution
programmatically from thevalidate
MojoExecution
(could not find a Maven API to do this)Having run out of options, I decided to skip the
enforceBytecodeVersion
on the first invocation. I confirmed it works on the second invocation (using the profile activated by the marker file written in the first invocation).Testing done
Built Jenkins core with
-Dmaven.compiler.release=17
and built Text Finder with that core and these changes, after runninggit clean -fxd
.Before this PR, Enforcer failed on the first invocation. After this PR, the first invocation prints:
and the second invocation prints