+1 to what Romain said. Let's reduce dependencies to other orgs where possible and feasible. It is, in this case.
On Fri, 30 Dec 2022, 10:27 Romain Manni-Bucau, <rmannibu...@gmail.com> wrote: > Hi Hervé, > > As mentionned in the thread I think it makes sense to freeze plexus and > slowly import to maven the related code so I'd be to import the parts we > need (guess some abstraction can be dropped at the same time). > So +1 to split, -0 to do it at plexus, +1 to do it in maven. > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > < > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > Le ven. 30 déc. 2022 à 10:22, Hervé Boutemy <herve.bout...@free.fr> a > écrit : > > > while working on the XML side of Maven 4 immutable API, we had the idea > of > > extracting the XML code from plexus-utils to a new separate plexus-xml > > artifact > > that could be done for version 4 > > > > see https://github.com/codehaus-plexus/plexus-utils/issues/228 > > > > any objection? > > > > Regards, > > > > Hervé > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
