Issue 22 in testability-explorer: maven2-testability-plugin name and version approach should match best practices.

[codesite...@google.com]

Status: Accepted
Owner: christianedwardgruber
Labels: Type-Defect Priority-Medium

New issue 22 by christianedwardgruber: maven2-testability-plugin name and
version approach should match best practices.
http://code.google.com/p/testability-explorer/issues/detail?id=22

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.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Status: new
Labels: -Type-Defect -Priority-Medium Type-Other Priority-Low

Comment #1 on issue 22 by christianedwardgruber: maven2-testability-plugin

name and version approach should match best practices.
http://code.google.com/p/testability-explorer/issues/detail?id=22

(No comment was entered for this change.)

[codesite...@google.com]

Comment #2 on issue 22 by aeagle22206: maven2-testability-plugin name and

version approach should match best practices.
http://code.google.com/p/testability-explorer/issues/detail?id=22

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?

[codesite...@google.com]

Comment #3 on issue 22 by cedric.lamalle: maven2-testability-plugin name

and version approach should match best practices.
http://code.google.com/p/testability-explorer/issues/detail?id=22

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>

[codesite...@google.com]

Updates:
Status: Fixed

Comment #4 on issue 22 by aeagle22206: maven2-testability-plugin name and

version approach should match best practices.
http://code.google.com/p/testability-explorer/issues/detail?id=22

Thanks Cedric, updated.