>But since the bigger proposal is already a work in progress >proposal could be retrofitted in that work, isn't it?
There's no progress since 2021 (see https://lists.apache.org/thread/xg99zym3xxp60gm4prdlfm68xlbysn48) At the same time, retrofitting my proposal into MNG-4530 would result in the same proposal implemented along with MNG-4530. MNG-4530 provides no means for aligning multi-artifact library versions or dealing with library splits. In other words, 4530 is an orthogonal proposal. >If a mechanism allows to specify strategies as plugins Going for a pluggable solutions for a common use case does not sound right since it would make life of non-Maven consumers much harder. In other words, if you suggest that published poms on Central would require "resolution plugins", then the tooling like IDE, non-Maven build systems would have to execute the same plugins which would be extremely hard to get workable. Think of resolution plugin written in Java and an IDE written in JavaScript. The plugins might be fine for local reactors, however, my proposal focuses on consuming other's published pom files, so I do not see how pluggable resolvers help. Vladimir
