Le 07/11/2025 à 12:18, Vladimir Sitnikov a écrit :
There are much bigger proposals like "let's build maven extension that would replace dependencies based on certain rules". Sure it would be helpful, however, it would be an overkill for a common cases like consuming multi-module libraries.
But since the bigger proposal is already a work in progress, the proposal could be retrofitted in that work, isn't it? It would be simpler than having two independent codes.
It addresses a different problem, and it does not help for "jar split" scenarios. Of course, implementing both proposals would yield much better results, however, Guillaume's proposal alone is not sufficient.
I though that the core issue was a conflict between dependency versions. The fact that the conflict is caused by a split of module provides context, and that context may be necessary for deciding how to resolve the conflict, but it still a version conflict issue, isn't it? If a mechanism allows to specify strategies as plugins, and if the plugin has access to information such as the dependency tree, what else would be needed?
Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
