Use Implementation-Build
rather than Plugin-GitHash
#527
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 jenkinsci/pom#419 and jenkinsci/maven-hpi-plugin#471. In jenkinsci/pom#419 I am planning to add the default specification and default implementation entries in core and core component
.jar
and.war
files, consistent with plugin.jar
and.hpi
files. In jenkinsci/pom#419 I am also planning to add the Git hash asImplementation-Build
to core and core component.jar
and.war
files, and in jenkinsci/maven-hpi-plugin#471 I am renaming this information fromPlugin-GitHash
(recently added) toImplementation-Build
for consistency. This PR adapts to jenkinsci/maven-hpi-plugin#471. While I am temporarily supportingPlugin-GitHash
for now, I plan to rip outPlugin-GitHash
shortly (in a month or so) once it's no longer used by anything (not much is using it today, just the AWS Java SDK plugin I think).