Lenny Primak
Lenny Primak
Awesome, thank you! I think will finally have a way forward with the ability to properly review now.
Maven or maven resolver can theoretically be modified to support this.
Would this new maven 4 relocation support version ranges so you won't have to publish 2 GAV every time?
I'm not sure I understand what that means :(
I guess the question is will it work for a use case when any version later then micrprofile:config:5.0 could be relocated to Jakarta:EE:config:5.0 without publishing the former GAV every time.
I updated the heading of the issue to demonstrate the use case better. Hope this helps
When older transient dependencies use older GAV, you can use `` to upgrade the new version. Since some older dependencies won't upgrade GA for some time. This allows convergence of...
Yes, and I would like to enhanced so that: > consumer going GA:1.1 to GA:1.2 will fail (no such artifact), as he did not his "homework" when he upped from...
Obviously this can be done. However, it introduces confusion, as in which artifact is "legit / latest" even though obviously they would both be the same. We want to avoid...
I would love to avoid this.