Very interesting trademark claim. I would love to these two merged btw, the first commit of codehaus plugin is at
Revision: 1465 Author: jgenender Date: Saturday, February 11, 2006 11:17:59 PM Message: New JAXB 2.0 plugin ---- Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/pom.xml Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main/java Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main/java/org Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main/java/org/codehaus Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main/java/org/codehaus/mojo Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main/java/org/codehaus/mojo/jaxb2 Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/main/java/org/codehaus/mojo/jaxb2/XjcMojo.java Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/site Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/site/apt Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/site/apt/usage.apt Added : /trunk/mojo/mojo-sandbox/jaxb2-maven-plugin/src/site/site.xml On Mon, Oct 13, 2014 at 2:38 PM, Aleksei Valikov <aleksei.vali...@gmail.com> wrote: > Hi guys, > > I actually wanted to address the authors of the jaxb2-maven-plugin but was > pointed by Robert Sholte to this mailing list. > > I'm the developer of the maven-jaxb2-plugin, the *other* Maven JAXB2 > plugin, I might have heard of it. > > I have an issue I'd like to inform you about. > > Our plugins always coexisted peacefully. There were also no big issues > with that. It was easy to undestand that if someone writes > jaxb2-maven-plugin then your plugin is meant, and maven-jaxb2-plugin is > mine. > > I have started my project almost 8 years ago and took the name > maven-jaxb2-plugin as it seemed to be _the_ right convention back then. > > Few years later Apache estabinished the some-maven-plugin convention for > non-Apache plugins. This is how they define it here: > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html > > > *You will typically name your plugin <yourplugin>-maven-plugin.* > > *Calling it maven-<yourplugin>-plugin (note "Maven" is at the beginning of > the plugin name) is strongly discouraged since it's a reserved naming > pattern for official Apache Maven plugins maintained by the Apache Maven > team with groupId org.apache.maven.plugins. Using this naming pattern is an > infringement of the Apache Maven Trademark.* > This became a warning during the build around three years ago. My plugin > was ~5 years old back then, with an already established user base etc. I > did not want to rename. This was a mistake, but it is a mistake already > made. > > Now an Apache committer, also a user of my plugin tried to clarified the > legal terms of this naming. Unfortunately, Apache seems to have a very > strict position on the issue. Please check this message: > > http://www.mail-archive.com/dev@maven.apache.org/msg102491.html > > And the further discussion. > > So in the current situation, using the maven-jaxb2-plugin further on, I am > * facing a threat of cease-and-desist letter and > * a probability that my plugin will stop working/compiling any time soon. > > I would not speculate on whether this trademark infringement thing is > legally sound or not. It does not matter. They're an organisation, I'm a > private person. I can't fight them. An even if the legal threat is unsound, > they can easily shut down my plugin technically in any next version of > Maven. > > So the thing is that I have no other choice as to rename my plugin. > > I have not yet desided on the name. The first choice would be > jaxb2-maven-plugin, but this artifactId is connected to your plugin. Yes, > sure, groupId is different but people will mix them up, definitely. > I also believe this option may hurt your user base. > > Any other name will disconnect my plugin from its longstanding history > even more. This will hurt my user base. I don't want this. > > Merging the projects is probably not an option. > > I am sorry to disturb you on this matter. I hope you see I am forced to. > Please let me know what you think, maybe there are further options. > > Best wishes, > Alexey >
