Thanks for the suggestions. I'll implement this then call the vote again.
-john
Benjamin Bentmann wrote:
John Casey wrote:
I would like to propose the release of the clirr-maven-plugin,
version 2.3.
0, not using it.
Some side notes:
I have just fixed MCLIRR-12, which is actually a pretty major bug.
This seems to be the only change since the last release. Based on [0]
I would have expected this version to be 2.2.1.
The POM has no <scm> element, making its "Source Repository" report
erroneously point to
http://svn.codehaus.org/mojo/tags/mojo-16/clirr-maven-plugin
You could consider to inherit from the latest Mojo parent (17). Among
others, this would update the plugin to use the
maven-plugin-plugin:2.4.1, improving its goal documentation.
Using the latest maven-plugin-plugin would also enable you to add the
auto-generated help mojo (not yet enforced via the Mojo parent).
The plugin has a changes.xml which hasn't been updated yet.
To promote the best practice of specifying plugin versions, it might
be good to extend the POM snippets in the docs to have a <version>
element.
The file src/site/apt/examples/specific-artifacts.apt has a typo in
line 36 (unbalanced "<" around "clirr:check").
Benjamin
[0] http://mojo.codehaus.org/development/process.html
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
