maven2-testability-plugin name and version approach should match best practices.

[GoogleCodeExporter]

There are two standard plugin naming conventions maven-*-plugin or 
*-maven-plugin.  We 
should really follow convention.  Especially since there's a resolver 
internally that knows about this 
convention for quick goal resolution.

Additionally, the version shouldn't really track the core tool's version, since 
the core tool is a 
separate piece of software which can be released separately from the plugin.  
This would allow us 
more flexibility in releasing, since we can fix bugs in the plugin without 
having to roll a new release 
of core.

Original issue reported on code.google.com by christia...@gmail.com on 23 Apr 2009 at 9:09

[GoogleCodeExporter]

Original comment by christia...@gmail.com on 23 Apr 2009 at 9:10

• Changed state: new
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

The name of the plugin has gone through a few iterations. Agree that we should 
follow
convention, I'll remove the 2.

As for releasing, I'm not sure yet about having different versions of different
parts. I would think every release of core would include stuff that maven users 
would
want, so we would always release together. Also, my experience on another 
project was
that maven doesn't understand how to perform a release of only some components 
and
not the whole app. I'd want to be sure that has been solved before assuming it's
possible. Anyway, if we do reach a point where we want to release just one 
component,
we can uncouple the versions in the POM at that time without much hassle, right?

Original comment by aeagle22206 on 24 Apr 2009 at 2:31

[GoogleCodeExporter]

Seems it has been done. The section 'Running with Maven' of the wiki 'Getting
Started' page should be updated to reflect this, should be:
<plugin>
    <groupId>com.google.testability-explorer</groupId>
    <artifactId>maven-testability-plugin</artifactId>
    <version>1.3.2-SNAPSHOT</version>
</plugin>

Instead of:
<plugin>
    <groupId>com.google.testability-explorer</groupId>
    <artifactId>maven2-testability-plugin</artifactId>
    <version>1.3.1-SNAPSHOT</version>
</plugin>

Original comment by cedric.l...@gmail.com on 15 Jun 2009 at 11:56

[GoogleCodeExporter]

Thanks Cedric, updated.

Original comment by aeagle22206 on 16 Jun 2009 at 8:01

• Changed state: Fixed