On 25. 07. 23 20:56, Slawomir Jaranowski wrote:
HiI'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</exportedPackage> <exportedPackage>org.codehaus.plexus.util.xml.pull.XmlPullParser</exportedPackage> <exportedPackage>org.codehaus.plexus.util.xml.pull.XmlPullParserException</exportedPackage> <exportedPackage>org.codehaus.plexus.util.xml.pull.XmlSerializer</exportedPackage> 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?
-- VH --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
