Brett Okken wrote:
I would like to go ahead and cut another beta release.
+0, not using it. Notes:
As per r8844, the plugin requires Maven 2.0.9 for its execution. The
commit message for this revision only mentions "documentation changes"
so I wonder whether the implication of <prerequisites> is properly
understood. The prerequisites don't just mean "known to work with 2.0.9"
but "get yourself the latest Maven release or I will refuse my work". I
have no idea how many users are still bound to older Maven versions and
for whatever reasons can't update to 2.0.9, so if there are no technical
reasons to require 2.0.9 the minimum Maven version could possibly
relaxed to 2.0.6.
The plugin still uses plexus-utils:1.2. Given the various bugfixes since
then [1], e.g with regard to process forking, it might be worth to
consider an update to a recent version.
The POM is missing the <scm> element.
The usage.apt shows a POM snippet with plugin version 2.0. This version
doesn't exist which can frustrate users when trying to copy&paste this
snippet.
Similar, the POM snippet on example1.apt points users at plugin version
1.0-beta-1 which seems rather outdated, possibly leasing to confusion
why newer features are not available. A possible approach could be to
add the file extension ".vm" to those doc files which would enable
filtering of the version via ${project.version}.
Besides, the example1.apt suggests to add a <pluginRepository> element
to the POM. This should be deleted as it is unnecessary (Codehaus
releases are synced over to central).
Benjamin
[0] http://fisheye.codehaus.org/changelog/mojo/?cs=8844
[1] http://jira.codehaus.org/browse/PLXUTILS
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
