Changing artifact and group ID but leaving package names the same is a recipe for classpath conflicts and broken builds:
https://jlbp.dev/JLBP-6 https://jlbp.dev/JLBP-19 If you change the artifact ID, change package names too. There's no such thing as a drop-in replacement with a different ID. On Tue, May 4, 2021 at 7:27 AM Tamás Cservenák <ta...@cservenak.net> wrote: > > Howdy, > > plexus-sec-dispatcher is a really widely used dependency, is used in maven > itself, but also in many shared components and plugins (nb: there are even > some org.sonatype.plexus:plexus-sec-dispatcher among shared deps!). > > Given this module is really maven specific, I see no reason to keep it > "outside" (in codehaus-plexus org), as I am really unaware of anything else > using it. Moreover, the module has a single dependency on plexus-cipher. > Both projects are just a handful of classes. > > So, my proposal: > * create maven-sec-dispatcher project (among maven-shared-components) > * collapse the two projects (both has handful of classes, > plexus-sec-dispatcher and plexus-cipher) in there > * org.apache.maven.shared:maven-sec-dispatcher becomes a "drop in" > replacement for org.plexus/org.sonatype.plexus:plexus-sec-dispatcher. > * bonus, this cuts (transitive) dependencies by one as well > > WDYT? > > Thanks > T -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
