gnodet commented on PR #942: URL: https://github.com/apache/maven/pull/942#issuecomment-1367565090
> https://issues.apache.org/jira/browse/MNG-7655 > > keeping `plexus-utils` artifactId with `org.apache.maven` vs `org.codehaus.plexus` groupId is confusing: let's name it `maven-plexus-utils` > > and `maven-xml-impl` is better named `maven-plexus-utils-xml`, to show that it reimplements plexus-utils' content I don't have any problem with this PR. However, I wonder that the final outcome should be. In the long term, the repackaging is a bit of a hack and a pain to maintain, especially the xml part which is reimplemented. I see several solutions: * deprecate the xml part in `plexus-utils` * move the implementation to a `plexus-utils` 3.0 (that would mean that `plexus-utils` would depend on the xml api from maven * deprecate `plexus-utils` artfifact and move the whole code into maven (this could have been beneficial in the maven 3 architecture where `plexus-utils` was exported, but this is no longer the case in 3.x and the new 4.x api does not depend on the `plexus-utils` artifact) -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
