Hi Not sure to understand the structure of this and the release cycle and if this includes maintenance of maven3 branches of plugins. If I understand correctly when cutting a release we will cut a release of every plugins?
On Fri, 16 Aug 2024 at 10:00 PM, Ozgun Oz <ozgunn...@gmail.com> wrote: > Just an outsider here, but I agree with Guillaume. Also I think Tamas' > proposal is to merge the existing plugins, so the repo of the old plugins > will be probably archived and the old plugins code will be moved to the new > plugin repo. > > Since the old plugins will not evolve and maintained by ASF, and honestly > as Tamas said I doubt anyone will try to fork the old plugin and compete > with ASF, I don't think we can talk about a risk of having "duplicate > standards competing" here. > > Maybe we should wait Tamas' clarification on the proposal. Is it about just > creating a new plugin on top of existing ones ? or merge the existing ones > into a new one ? > > > On Thu, Aug 15, 2024, 9:30 PM Guillaume Nodet <gno...@apache.org> wrote: > > > Well this would be the same plugins, not duplicates…. > > > > ------------------------ > > Guillaume Nodet > > > > > > > > Le jeu. 15 août 2024 à 20:10, Elliotte Rusty Harold <elh...@ibiblio.org> > a > > écrit : > > > > > On Thu, Aug 15, 2024 at 1:24 PM Delany <delany.middle...@gmail.com> > > wrote: > > > > > > > The $5000 question is how can the old plugins still even exist if the > > > code > > > > for them has been moved to a new core plugin? > > > > > > > > > In the git repo. In Maven central. In absolutely every existing plugin > > > and build that depends on these today. They aren't going away. Where > > > do I collect my $5000? :-) > > > > > > -- > > > 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 > > > > > > > > >
