Should be karma-maven-plugin

[NateRedding]

The name 'maven--plugin' is actually reserved for plugins coming from Apache. 3rd-party plugins should use '-maven-plugin'. When building the plugin as-is, this error message is received:

[ERROR]
Artifact Ids of the format maven-___-plugin are reserved for
plugins in the Group Id org.apache.maven.plugins
Please change your artifactId to the format ___-maven-plugin
In the future this error will break the build.

[kelveden]

Yes, I've seen that. I've held back on moving across to the convention for a few reasons:

• It's not a convention that ever seems to have been adhered to very strongly in Maven-world.
• Given that artifacts are qualified with the group id I actually can't see a point to it.
• Following on from the above point, I actually think it's a counter-productive convention too - from my experience, what most people search for by default when looking for a Maven plugin to solve their problem is the "maven-dosomething-plugin".
• It's an utter ball-ache getting a new artifact set up in Nexus.
• People would have to make an explicit transition from maven-karma-plugin to karma-maven-plugin.

I honestly can't believe that they're going to follow through with their "In the future this error will break the build" threat - it'll break too many existing plugins.

BUT having said all that, I don't feel that strongly about it. I've been moving away from Maven as my default build too for a while so the maven-karma-plugin is something I'm not using much these days. I'm probably going to retire from maintainership of it soon. So, if you're happy to setup and maintain a karma-maven-plugin under the karma-runner project I'll happily talk to Vojta about deprecating the maven-karma-plugin in favour of your plugin.

[kelveden]

No activity on this and I don't plan any so closing.