David wrote:
What do you guys think of adding: <plugin> <groupId>org.apache.maven.plugin</groupId> <artifactId>maven-changes-plugin</artifactId> <version>2.1</version> [...] </plugin>to the mojo-parent?
Given that not all plugins have dedicated JIRA projects, it appears that would be troublesome for those. Just consider all the sandbox plugins. I'm not sure it's worth to create JIRA components for all of them just to get a reasonable report output.
Also - can we switch the surefire-reporting to report-only, to avoid rerunning tests in a normal build?
-0, I usually run "mvn clean site-deploy" for a deployment and having Surefire run the tests frees me from remembering to also run the test phase.
For quick site generation and review of hand-crafted docs, the latest mojo-parent provides a system property to skip most of the expensive reports in analogy to Surefire's skipTests
mvn site -D skipReports Benjamin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
