Have you received any respone from trademarks@a.o?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Le dimanche 12 octobre 2014 10:04:04 Benson Margulies a écrit :
One of Stephen's points is that the artifactId strings have an
influence on the prose: a thing with artifactId maven-popcorn-plugin
seems to lead, inexorably, towards 'The Maven Popcorn Plugin', which
is bad. But, is
Am 2014-10-12 um 00:30 schrieb Stephen Connolly:
On Saturday, 11 October 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov micha...@apache.org
wrote:
Well said...
I guess it is all about the
On Sunday, 12 October 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-10-12 um 00:30 schrieb Stephen Connolly:
On Saturday, 11 October 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov
I like the way Mojo makes common sense explicit without trademark drama:
http://mojo.codehaus.org/development/guidelines.html
- Use the plugin-maven-plugin convention for the artifactId of any developed
Maven plugin.
- Use the [Project] Maven Plugin convention to name your plugin e.g. Acme
On Sunday, October 12, 2014, Hervé BOUTEMY herve.bout...@free.fr wrote:
I like the way Mojo makes common sense explicit without trademark drama:
http://mojo.codehaus.org/development/guidelines.html
- Use the plugin-maven-plugin convention for the artifactId of any
developed
Maven plugin.
I think that I, amongst other people, are in danger of losing track of
the trademark forest for the trees.
I'm copying trademarks@, which is a closed list, but I don't think
that this discussion has to be restricted to private@. If anyone on
trademarks@ cares to correct me, please copy the Maven
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
:;
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
I'd like to sum up the consensus we have hopefully reached already:
1. Make maven-plugin-plugin fail the build if the plugin being build
does not adhere to our convention (next minor version).
2. Warn a user when a build is performed with a plugin which violates
the naming convention, just
I am very tempted to reopen the trademark question here. It seems to
me that this whole business ignores the groupId component of the name,
which distinguishes pretty clearly, and I would argue is enough to
avoid trademark dillution.
On Sat, Oct 11, 2014 at 2:57 PM, Michael Osipov
Am 2014-10-11 um 21:03 schrieb Benson Margulies:
I am very tempted to reopen the trademark question here. It seems to
me that this whole business ignores the groupId component of the name,
which distinguishes pretty clearly, and I would argue is enough to
avoid trademark dillution.
Well
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov micha...@apache.org wrote:
Well said...
I guess it is all about the order of the words: Maven X Plugin. It simply
implies that is provided by the Maven team. Which is not.
But is the order relevant in the artifactId or in the public display
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov micha...@apache.org wrote:
Well said...
I guess it is all about the order of the words: Maven X Plugin. It simply
implies that is provided by the Maven team. Which is not.
But is the order
On Saturday, 11 October 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov micha...@apache.org
wrote:
Well said...
I guess it is all about the order of the words: Maven X Plugin. It simply
They should rename going forward.
At some point (probably we could do so now) we will turn on enforcement in
the maven-plugin-plugin.
If they have not renamed then they will be stuck with the older tooling.
On 10 October 2014 12:08, Michael Osipov 1983-01...@gmx.net wrote:
Hi folks,
how do
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
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
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
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 bimargul...@gmail.com wrote:
Keep in mind that what we have here is almost certainly a
On Fri, Oct 10, 2014 at 7:42 AM, Stephen Connolly
stephen.alan.conno...@gmail.com 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
We just need to show best effort to defend our trademark... if we *see*
anyone doing that then we have to send them CD letters...
Note: my understanding is that we only have to send CD letters when we
know somebody is abusing our mark... we don't necessarily have to go
actively looking for people
Hi,
On 10/10/14 1:25 PM, Michael Osipov 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
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 CD 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 CD letters...
Note: my
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 CD too?
Michael
We just need to show best effort to defend our trademark... if we *see*
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 CDs.
/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
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 CDs.
/me runs away from this
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.
Shouldn't
Developers List dev@maven.apache.org
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
: Freitag, 10. Oktober 2014 um 15:23 Uhr
Von: Stephen Connolly stephen.alan.conno...@gmail.com
An: Maven Developers List dev@maven.apache.org
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
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
@maven.apache.org
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
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 this rule;
Am 10/10/14 14:00, schrieb Karl Heinz Marbaise:
Hi,
On 10/10/14 1:25 PM, Michael Osipov 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?
Hi,
On 10/10/14 4:20 PM, Michael Osipov wrote:
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
Hi,
On 10/10/14 4:31 PM, Christian Schulte wrote:
Am 10/10/14 14:00, schrieb Karl Heinz Marbaise:
Hi,
On 10/10/14 1:25 PM, Michael Osipov 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
relocations only make sense with version ranges and even then they
don't make much sense.
On 10 October 2014 15:31, Christian Schulte c...@schulte.it wrote:
Am 10/10/14 14:00, schrieb Karl Heinz Marbaise:
Hi,
On 10/10/14 1:25 PM, Michael Osipov wrote:
They should rename going
:23 Uhr
Von: Stephen Connolly stephen.alan.conno...@gmail.com
An: Maven Developers List dev@maven.apache.org
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
An: Maven Developers List dev@maven.apache.org
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
39 matches
Mail list logo
