slachiewicz commented on PR #11583: URL: https://github.com/apache/maven/pull/11583#issuecomment-5483513885
@elharo In Maven 4, the relationship between Plexus and Maven XML was inverted by design: * `org.apache.maven.api.xml.XmlNode` is the immutable core API in Maven 4. * `plexus-xml` **4.x** was created specifically as a backward-compatibility bridge for legacy plugins—`org.codehaus.plexus.util.xml.Xpp3Dom` in `plexus-xml` 4.x wraps and delegates to `XmlNode`. Because `plexus-xml` is an external dependency (`codehaus-plexus/plexus-xml`), modifying or removing existing method names on `XmlNode` breaks compatibility with the released `plexus-xml 4.x` artifacts. Given that we are close to cutting the Maven 4 release: 1. We should avoid breaking changes to `XmlNode` at this stage (or only add getter aliases as `default` methods rather than renaming existing ones). 2. Otherwise, this would require coordinating a release of `plexus-xml` before we can integrate changes here. What do you think about either adding default getter methods alongside the current methods or deferring this cleanup post-4.0? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
