Milos Kleint wrote:
I'd like to release nbm-maven-plugin 3.0
+0, not using it. Notes:
"mvn dependency:analyze" reports some undeclared dependencies.
The POM is missing the <scm> element.
The POM inherits from the old mojo-parent:19 which produces a bad JDK
requirement in plugin-info.html. mojo-parent:20 fixed this.
The site descriptor can be trimmed down, i.e. anything but the <menu>
should be inherited from the parent.
"mvn docck:check" reveals that "Parameter: 'outputDirectory' in mojo:
'autoupdate' is missing a description."
Several mojo parameters referring to build paths are of type String
instead of File, e.g. in BrandingMojo. Without basedir alignment, this
gives rise to errors [0].
There are a few incompatible changes, that's why it's 3.0, not 2.7
Hm, there are two "@since 2.7" in the code, should these then be updated
to "@since 3.0" as well?.
Benjamin
[0]
http://maven.apache.org/plugin-developers/common-bugs.html#Resolving_Relative_Paths
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
