now that plexus-xml has more details, I see the key point causing the most issues: it uses not only maven-xml-api but also maven-xml-impl
maven-xml-impl is the Maven 4-specific reimplementation of XML parsing that is causing the incompatibility probably that this Maven XML Implementation component should be added to the list of libraries that deserve extracting from Maven core release cycle to have a dedicated Maven Shared Component. This won't solve the compatibility issue that started this thread, but a least go in the right direction by making things more clear: today, it's too much magic and inter-dependencies with Maven core Here is the list of Maven core components that should IMHO be extracted as separate Maven Shared Component: - Meta Annotation: https://maven.apache.org/ref/4.0.0-alpha-7/api/maven-api-meta/index.html - XML API: https://maven.apache.org/ref/4.0.0-alpha-7/api/maven-api-xml/index.html - XML Impl: https://maven.apache.org/ref/4.0.0-alpha-7/maven-xml-impl/index.html The discussion on plexus-xml compatibility with Maven 3 will required a next thinking: perhaps we should have had a plexus-xml release that was done *before* maven-xml-impl update = what is causing the compatibility issue Regards, Hervé Le samedi 9 septembre 2023, 11:33:59 CEST Hervé Boutemy a écrit : > > o.c.p:p-u 4.x that depends on > > -> o.c.p:p-xml 4 that depends on > > notice this dependency is *optional* > it's useful only for ReaderFactory/WriterFactory, for XmlReader/Writer > fully removing the dependency would have broken full compatibility by > removing a few methods: it was preferred to mark the dependency as optional > and keep full compatibility > > then I would not say that p-u 4 pulls new Maven 4 API > > > -> o.c.p:p-xml 4 that depends on > > -> o.a.m:m-api-xml that depends on > > -> o.a.m:m-api-meta > > to me, here is where an improvement would be useful > m-api-meta and m-api-xml are small very stable APIs, very non-Maven core > specific > I understand that we want to put them at Apache instead of Plexus, and I > agree. > But I think we should make their release cycle independent from Maven core: > they do not deserve the current 7 alphas, then new releases in the future > years. > > see https://maven.apache.org/ref/4.0.0-alpha-7/api/index.html for an > overview of all Maven 4 API artifacts: > - Model, Settings, Toolchains and Core are clearly here at their right place > - XML (1 interface: XmlNode) and meta annotation (6 annotations) are not so > much Maven core related, and stable enough > > IMHO, XML and meta annotation should fo to Maven Shared Components > https://maven.apache.org/shared/index.html > Better place, and better release cycle > > then depending on these from outside would not be problematic > > Regards, > > Hervé > > Le vendredi 8 septembre 2023, 19:42:40 CEST Tamás Cservenák a écrit : > > Howdy, > > > > Basil's issue is made me realize: > > o.c.p:p-u 4.x that depends on > > -> o.c.p:p-xml 4 that depends on > > -> o.a.m:m-api-xml that depends on > > -> o.a.m:m-api-meta > > > > This means that p-u pulls in new Maven4 API bits. > > Hence, Maven 3 plugin, that is built against maven-plugin-api 3.x, if > > switched to p-u 4, would start receiving bits of Maven4 new API... > > > > This is a big no for me, not to mention how this can prove problematic > > down > > the road too: > > this means that today (as all this is "just on CP") mvn3 plugin could use > > bits of Maven4 API that later -- if run in Maven4 -- becomes > > forbidden/unavailable... > > > > So, IMHO this just proves, that Maven 3.x level plugins should stick with > > p-u 3.x > > > > On Fri, Sep 8, 2023 at 6:24 PM Basil Crow <m...@basilcrow.com> wrote: > > > I raised this issue in > > > > > > https://github.com/jenkinsci/maven-hpi-plugin/pull/490#issuecomment-1557 > > > 97 > > > 0717 but did not receive a response. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
