>
> Hi,
>
> On 10/10/14 3:41 PM, Paul Benedict wrote:
> > I would prefer this should be part of Maven Core's warning system. If the
> > plugin starts with maven- and it's not an org.apache.maven.plugins group,
> > then we should spit out the error. I am not sure enforcer is the right
> > place for
p in plugin version. WDYT?
>
> Michael
>
> > Gesendet: Freitag, 10. Oktober 2014 um 15:23 Uhr
> > Von: "Stephen Connolly"
> > An: "Maven Developers List"
> > Betreff: Re: Re: Re: Re: Maven plugin naming pattern
> >
> > That was the plan..
t; An: "Maven Developers List"
> 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?
>
>
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> wrote:
> Yes, resposibility isn't always good.
>
> Should
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 th
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
wrote:
> Yes
>
> On 10
Yes
On 10 October 2014 13:12, Michael Osipov <1983-01...@gmx.net> 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
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 u
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 peopl
On Fri, Oct 10, 2014 at 7:42 AM, Stephen Connolly
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
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
On 10 October 2014 12:40, Benson Margulies wrote:
> Keep in mind that what we have here is almost certainly a
> _convention_, not a point o
1. We sent an announcement a long time ago.
2. We switched the maven-plugin-plugin to a warning a good while ago:
https://github.com/apache/maven-plugin-tools/commit/f88a58cecb4599e70b8fecf8b13d77d5e084be9c
If people have ignored that warning for three years, then we have done all
we can. The PMC
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 enf
> 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. Techni
14 matches
Mail list logo