I would be perfectly happy to fail the builds of plugin owners as a first step. Make it so.
I just want an additional JIRA created to emit a warning in core, to be scheduled in some future release (even as far out as 4.0), least we lose track of the next step. On Oct 11, 2014 1:30 AM, "Hervé BOUTEMY" <herve.bout...@free.fr> wrote: > I'm not a big fan of failing build in case of wrong plugin name > but we need to help people do the work to update their naming > > one step forward could be to fail maven-plugin-plugin (not core yet) when > generating plugin.xml for such a plugin: plugin owners would see they > cannot > continue to make release with wrong naming convention > > then failing at Maven core level could be done with Maven 4 > > WDYT? > > Regards, > > Hervé > > Le vendredi 10 octobre 2014 14:46:02 Stephen Connolly a écrit : > > On Friday, 10 October 2014, Michael Osipov <1983-01...@gmx.net> wrote: > > > Fine, I'd like to note that first: > > > > > > 1. Shouldn't we announce this publically on the users mailing list? > > > > Yes as part of announcing the maven-plugin-plugin release > > > > > 2. I think that this deserves a major bump in plugin version. WDYT? > > > > I am fine with minor as we have 3 years+ of warning. If whoever steps up > as > > release manager wants to call it a major bump, I'll not object > > > > > Michael > > > > > > > Gesendet: Freitag, 10. Oktober 2014 um 15:23 Uhr > > > > Von: "Stephen Connolly" <stephen.alan.conno...@gmail.com > <javascript:;>> > > > > An: "Maven Developers List" <dev@maven.apache.org <javascript:;>> > > > > Betreff: Re: Re: Re: Re: Maven plugin naming pattern > > > > > > > > That was the plan.... 3 years ago we decided to warn first and then > > > > > > switch > > > > > > > on failing after a while... now is a good time, perhaps you could > commit > > > > the change to fail the build? > > > > > > > > On 10 October 2014 13:48, Michael Osipov <1983-01...@gmx.net > > > > > > <javascript:;>> wrote: > > > > > Yes, resposibility isn't always good. > > > > > > > > > > Shouldn't simply make the build fail instead of log when such a > > > > > > collision > > > > > > > > happens? > > > > > > > > > > Michael > > > > > > > > > > > Thankfully for you, you are not on the PMC... if you were on the > PMC > > > > > > and > > > > > > > > > you did such a search you would then have to go and send C&Ds. > > > > > > > > > > > > /me runs away from this thread in case I happen to be made aware > of > > > > > > any > > > > > > > > > trademark misuse ;-) > > > > > > > > > > > > On 10 October 2014 13:39, Stephen Connolly < > > > > > > > > > > stephen.alan.conno...@gmail.com <javascript:;>> > > > > > > > > > > > wrote: > > > > > > > Yes > > > > > > > > > > > > > > On 10 October 2014 13:12, Michael Osipov <1983-01...@gmx.net > > > > > > <javascript:;>> wrote: > > > > > > >> If you do a quick search on Central, you'll that even other > > > > > > >> Apache > > > > > > > > > > project > > > > > > > > > > > >> don't adhere to this convention. Should they receive a C&D > too? > > > > > > >> > > > > > > >> Michael > > > > > > >> > > > > > > >> > We just need to show best effort to defend our trademark... > if > > > > > > we > > > > > > > > *see* > > > > > > > > > > > >> > anyone doing that then we have to send them C&D letters... > > > > > > >> > > > > > > > >> > Note: my understanding is that we only have to send C&D > letters > > > > > > > > > > when we > > > > > > > > > > > >> > know somebody is abusing our mark... we don't necessarily > have > > > > > > to go > > > > > > > > > >> > actively looking for people abusing our mark... just if we > went > > > > > > > > > > looking > > > > > > > > > > > >> and > > > > > > >> > > > > > > >> > found any then we have to send them C&Ds quite quickly > > > > > > >> > > > > > > > >> > On 10 October 2014 12:45, Benson Margulies < > > > > > > bimargul...@gmail.com <javascript:;>> > > > > > > > > > >> wrote: > > > > > > >> > > On Fri, Oct 10, 2014 at 7:42 AM, Stephen Connolly > > > > > > >> > > > > > > > > >> > > <stephen.alan.conno...@gmail.com <javascript:;>> wrote: > > > > > > >> > > > We, the PMC, agreed to allow permitted usage of the form > > > > > > >> > > > > > > >> ___-maven-plugin > > > > > > >> > > > > > > >> > > > as that clarified that the plugin was a plugin for maven > > > > > > not one > > > > > > > > > >> produced > > > > > > >> > > > > > > >> > > > by maven > > > > > > >> > > > > > > > > >> > > Yea, I know, and I'm not opposed to making the tooling > more > > > > > > >> > > obstreperous. I'm just warning people not to have high > hopes > > > > > > of > > > > > > > > > >> > > enforcement for anyone who chooses to hack the tooling and > > > > > > >> > > not > > > > > > >> > > cooperate. > > > > > > >> > > > > > > > > >> > > > On 10 October 2014 12:40, Benson Margulies < > > > > > > > > > > bimargul...@gmail.com <javascript:;>> > > > > > > > > > > > >> > > wrote: > > > > > > >> > > >> Keep in mind that what we have here is almost > certainly a > > > > > > >> > > >> _convention_, not a point of trademark law. As I > > > > > > understand it, > > > > > > > > > >> we'd > > > > > > >> > > > > > > >> > > >> as likely be laughed at for the suggestion that > reversing > > > > > > the > > > > > > > > > >> order of > > > > > > >> > > > > > > >> > > >> the components of a name leads to 'marketplace > confusion' > > > > > > at > > > > > > > > the > > > > > > > > > > > >> level > > > > > > >> > > > > > > >> > > >> at which trademarks can be enforced. > > > > > > >> > > >> > > > > > > >> > > >> On Fri, Oct 10, 2014 at 7:25 AM, Michael Osipov < > > > > > > >> > > > > > > >> 1983-01...@gmx.net <javascript:;>> > > > > > > >> > > > > > > >> > > >> wrote: > > > > > > >> > > >> >> They should rename going forward. > > > > > > >> > > >> >> > > > > > > >> > > >> >> At some point (probably we could do so now) we will > > > > > > turn on > > > > > > > > > >> > > enforcement > > > > > > >> > > > > > > > > >> > > >> in > > > > > > >> > > >> > > > > > > >> > > >> >> the maven-plugin-plugin. > > > > > > >> > > >> > > > > > > > >> > > >> > This will of course piss of a lot of people. Wouldn't > > > > > > >> > > >> > it? > > > > > > >> > > >> > > > > > > > >> > > >> > There are, of course, several reasons why people > can't: > > > > > > >> > > >> > > > > > > > >> > > >> > 1. Popularity of the old name > > > > > > >> > > >> > 2. Technical reasons > > > > > > >> > > >> > 3. Name collisions > > > > > > >> > > >> > > > > > > > >> > > >> > etc. > > > > > > >> > > >> > > > > > > > >> > > >> > Even if we enforce this, this should not happen > before > > > > > > Maven > > > > > > > > 4 > > > > > > > > > > > >> and > > > > > > >> > > > > > > >> > > >> should be added to the plugin dev center. > > > > > > >> > > >> > > > > > > >> > > >> > Michael > > > > > > --------------------------------------------------------------------- > > > > > > > > > >> > > >> > To unsubscribe, e-mail: > dev-unsubscr...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > >> > > >> > For additional commands, e-mail: > > > dev-h...@maven.apache.org <javascript:;> > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > >> > > >> To unsubscribe, e-mail: > dev-unsubscr...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > >> > > >> For additional commands, e-mail: > dev-h...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > >> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > >> > > For additional commands, e-mail: > dev-h...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > >> For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > <javascript:;> > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > <javascript:;> > > > For additional commands, e-mail: dev-h...@maven.apache.org > <javascript:;> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
