Re: plexus-sec-dispatcher

2021-05-04 Thread Tamás Cservenák
> > > would makes sense with changing groupId/artifactId and packages > > but cons: release this if needed will take ages because of ASF procedures > > So, understood re ID/package But forgot about the ASF process... but it would be weird if I want to "de-plexus" plexus-sec-dispatcher in codehaus-

Re: plexus-sec-dispatcher

2021-05-04 Thread Michael Osipov
Am 2021-05-04 um 09:26 schrieb Tamás Cservenák: 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 r

Re: plexus-sec-dispatcher

2021-05-04 Thread Olivier Lamy
On Tue, 4 May 2021 at 17:27, Tamás Cservenák 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

Re: plexus-sec-dispatcher

2021-05-04 Thread Elliotte Rusty Harold
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.