Romain, I would appreciate if you try running jarsplit example (see [1]), or clarify how Maven team suggests resolving it. It is a single-pom reproducer, and it does fail with Maven in runtime no matter what options are set.
>There is no link to maven there but actually java if you go one step >further Romain, I assume you somehow missed the link to maven. The link is in [2] 1) Chris Povirk explicitly mentions "we also worried that Maven users would end up with" It is a direct link to Maven tool rather than Maven ecosystem or Java or whatever else. 2) Chris Povirk explicitly mentions "...that is best solved with...Gradle" This again contrasts Gradle tool being a solution for Maven tool's issue 3) As I asked a targeted question "...key culprit is Maven’s inability to deal with..." Chris Povirk agreed. That is a clear link from the issue to Maven tool. 4) Chris Povirk explicitly mentions "We *could reconsider* someday *if the ecosystem* were to have better support for *splitting up artifacts* in the future." That signals Maven tool inability to support splitting artifacts holds Guava. 5) The example in [1] fails with Maven, and the same example does not fail with Gradle. >But ultimately Java was preventing the buggy guava design to be split >easily as Tamas explained. Romain, neither Chris, nor Tamas used the words like "Java was preventing". Java itself does not prevent the split. It is Maven tool that does. Gradle supports artifact splits, and it is transparent for the end-users. [1] https://github.com/vlsi/jarsplit/tree/b7dae3f1609b978e1a33ffa63d717bc66e45daa5/app-maven4 [2] https://github.com/google/guava/issues/8079#issuecomment-3486410334 Vladimir
