Carlos Sanchez wrote:
bringing this thread back to life, seems there's people interested in jira
0, not using it, side notes:
The POM states compiler target 1.4 but the source does not compile
against a JDK 1.4.
The POM has no <scm> element, causing a bad "Source Repository" report.
The report mojo suffers from Common Bug #4 [0]. I suggest to split off
the directory part "emma" from the parameter outputDirectory into a
further parameter (say emmaDirectory) and set the output directory for
EMMA to
new File(getReportOutputDirectory(), emmaDirectory)
The new parameter emmaDirectory could also be reused for the method
getOutputName()
The plugin's site does not follow the "Plugin Documentation Standard"
[1]. In particular, I feel the link "Goals" is missing in the "Overview"
menu.
Updating the plugin to use the latest release of the Invoker Plugin
(1.2) could ease intergration testing:
- convenient staging of plugin artifact into isolated local repo [2]
- separation of IT build output from version controlled directories [3]
- checking for failing IT builds like it05 [4]
Benjamin
[0] http://www.nabble.com/Re%3A-Common-Bugs-p15246107.html
[1]
http://maven.apache.org/guides/development/guide-plugin-documentation.html
[2] http://maven.apache.org/plugins/maven-invoker-plugin/install-mojo.html
[3]
http://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html#cloneProjectsTo
[4] http://maven.apache.org/plugins/maven-invoker-plugin/faq.html#question2
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
