working on it, I created a branch for plexus-xml 3.x: https://github.com/codehaus-plexus/plexus-xml/tree/3.x
we should probably release such plexus-xml 3 that is the "normal" usual XML code that we used for years, extracted from plexus-utils 3 plexus-xml 4 is currently only for Maven 4 FYI, I tried to upgrade plexus-utils in a few Maven-maintained plugins My findings are: - many plugins use XML API, sometime just for Xpp3ParserException from Maven core API, sometimes because they use Modello to read/write XML... then we have many Maven-maintained plugins to test strategies - a few plugins don't use XML at all: in this case, upgrading plexus-utils from 3 to 4 is feasible just now: https://github.com/apache/maven-jarsigner-plugin/pull/12 Regards, Hervé Le dimanche 10 septembre 2023, 10:11:14 CEST Sylwester Lachiewicz a écrit : > And looks like this apply not only to plugins but also to shared libs for > maven (ASF also plexus and mojohous) > > Sylwester > > niedz., 10 wrz 2023, 09:00 użytkownik Hervé Boutemy <herve.bout...@free.fr> > > napisał: > > Le samedi 9 septembre 2023, 19:33:51 CEST Václav Haisman a écrit : > > > On 25. 07. 23 20:56, Slawomir Jaranowski wrote: > > > > Hi > > > > > > > > I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x > > > > in > > > > > > maven-enforcer .... > > > > > > > > In maven-enforcer (and in many other plugins ...) is used, code like: > > > > Xpp3Dom enforcerRules = > > > > Xpp3DomBuilder.build(descriptorStream, > > > > > > > > "UTF-8"); > > > > > > > > Xpp3Dom and Xpp3DomBuilder - has new implementation in plexus-xml .... > > > > but > > > > > > Maven 3.x exports > > > > > > > > <!-- plexus-utils (for DOM-type fields in maven-model) --> > > > > <exportedPackage>org.codehaus.plexus.util.xml.Xpp3Dom</exportedPackag > > > > > > e> > > > > <exportedPackage>org.codehaus.plexus.util.xml.pull.XmlPullParser</exported > > > > > > Package> > > > > <exportedPackage>org.codehaus.plexus.util.xml.pull.XmlPullParserException< > > > > > > /exportedPackage> > > > > <exportedPackage>org.codehaus.plexus.util.xml.pull.XmlSerializer</exported > > > > > > Package> > > > > > > > > It is very magical that we export classes but not export artifact > > > > which contains those classes ... > > > > > > > > so incompatibilite code for Xpp3Dom is used ... > > > > > > > > Any hints on how to process it. > > > > > > So, what is the takeaway of this tread for casual Maven plugin > > > developers like me? Should I avoid plexus-utils 4.x in Maven 3 plugins? > > > > more precisely: don't upgrade plexus-utils to 4 *if you need plexus-xml* > > > > our intent of splitting concerns between general non-XML utils vs XML is a > > success: upgrading plexus-utils will make clear which plugins > > > > but when you need XML details in your plugin = where Maven core has an > > impact, > > we are not clear yet on how to make the plexus xml update Maven 3 and 4 > > compliant at the same time > > > > this thread needs to continue because we're not yet at the final > > conclusion, > > > > but this intermediate small message can be used for now: > > don't upgrade plexus-utils to 4 *if you need plexus-xml* > > > > Regards, > > > > Hervé > > > > > > > > --------------------------------------------------------------------- > > 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
