Stop the Maven runtime pin from freezing maven-archiver - #1364
Merged
Conversation
The wildcard covered org.apache.maven:maven-archiver, which is a library on its own version, not part of the runtime pin. Name the runtime artifacts instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
org.apache.maven:*matches that groupId exactly, andorg.apache.maven:maven-archiverlives in it. It is a shared library carrying its own version,3.6.4here, not part of the${mavenVersion}runtime pin — so the wildcard has been holding it back since 2022. Central is at 3.6.6.The six runtime artifacts are now named individually and stay pinned at
mavenVersion3.6.3, which is what the rule was written for.Part of a sweep across the thirteen repositories carrying this wildcard; see apache/maven-archiver#394.
This change was created with AI assistance.