maven2-testability-plugin name and version approach should match best practices. about testability-explorer HOT 4 CLOSED

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?

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>

Thanks Cedric, updated.