>once again your examples are not well written - Romain, please clarify exactly what is "not well written" in https://github.com/vlsi/jarsplit/blob/b7dae3f1609b978e1a33ffa63d717bc66e45daa5/app-maven4/pom.xml
>You got several solutions in the thread Please pin-point a solution for https://github.com/vlsi/jarsplit/blob/b7dae3f1609b978e1a33ffa63d717bc66e45daa5/app-maven4/pom.xml So far there were zero solutions. >can maven enable you to switch artifact on the fly -> yes with extension, >see remapping thread as mentionned early, likely not desired in core AFAIK there's no "maven endorsed" extension. The suggestion of "create your own extension and force everybody using it" looks like a workaround to me rather than a solution. >The issue is not in maven was my point Romain, if you think "the issue is not in maven", please yield to the others too so they could express their opinions. There's a reproducer project, so it is truly surprising to hear "not an issue". >Why so much projects do not have these issues? Multiple reasons: a) Sometimes they switch to Gradle b) Sometimes they create workarounds like enforcer rules, style guides (which for instance, forbid jar splits). https://jlbp.dev/JLBP-6 was created as a workaround for Maven's inability to handle dependency splits. c) Sometimes they just don't know there are better options available. In other words, people just get their NoClassDefFoundErrors, and ask AI to resolve it. They don't even realize that a trivial fix in Maven could prevent the issue in the first place. >if you care about downstream consumers Please read the example again. I do care about downstream consumers, and what I would like to have is a transparent way for consumers to handle jar splits by the dependency maintainer. >once again your examples are not well written - Romain, please clarify exacly what is "not well written" in https://github.com/vlsi/jarsplit/blob/b7dae3f1609b978e1a33ffa63d717bc66e45daa5/app-maven4/pom.xml Vladimir
