[Build] Define all MANIFEST.MF entries through the bnd-maven-plugin #518
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.
Define all MANIFEST.MF entries through the bnd-maven-plugin and derive
Bundle-SymbolicName
header from theartifactId
.This changes the 'Bundle-SymbolicName' and 'Automatic-Module-Name' for the following modules:
maven-resolver-named-locks
fromorg.apache.maven.resolver.named
toorg.apache.maven.resolver.named.locks
maven-resolver-test-util
fromorg.apache.maven.resolver.testutil
toorg.apache.maven.resolver.test.util
This is effectively the back-port of #517 to the
maven-resolver-1.9.x
branch.The main difference is that unlike in #517, this change does not 'prepare' the introduction of JPMS
module-info.java/class
files.