Add java level profiles for java 17 and java 21 #893
Merged
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.
This change is meant to work in tandem with jenkinsci/maven-hpi-plugin#578. Without it, it is essentially a no-op (unless a user enables one of the new profiles explicitly e.g. via
-Pjava-level-17
)These will get used by IDEs (e.g. IDEA IntelliJ) to set the appropriate java level if it differs from the default java level defined in the pom file.
In practice,
maven-hpi-plugin
will generate and manage the files used as activation markers for these profiles, depending on the java level required by the jenkins version the plugin required.Testing done
Submitter checklist