You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks. I guess I made a mistake when I renamed this plugin after the naming
policy change.
However, I have not had any users with actual problems with the new name, so I
will sit on this issue until something comes up.
It had broke our maven build when we uploaded new version of plugin in our
Nexus repository. We have to manually rename artifactId in our pom.xml from
replacer-maven-plugin to replacer.
fwiw, there's also
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html#Plugin_
Naming_Convention_and_Apache_Maven_Trademark
Note that I *think* your groupId might also still be an issue, but you'd have
to check with the Apache Maven PMC to be sure.
Original comment by bmathus on 17 Dec 2013 at 8:26
Original issue reported on code.google.com by
pino.silvaggio
on 12 Apr 2012 at 6:17The text was updated successfully, but these errors were encountered: