Split analyse from report and then provide an aggregate mojo
------------------------------------------------------------
Key: MJNCSS-26
URL: http://jira.codehaus.org/browse/MJNCSS-26
Project: Maven 2.x JavaNCSS Plugin
Issue Type: Improvement
Reporter: John Allen
Assignee: Jean-Laurent de Morlhon
We have followed clovers approach and turned all our quality analysis plugins
into non-atomic reporting plugins.
By that I mean that for any tools that can analyse code we have an analyse mojo
that produces, usually, and XML file.
The check mojo can of course now just process this file
An aggregate mojo can now aggregate this XML file up the project hierarchy and
is bound to pre-site
And of course the report mojo simply generates a report for any XML files it
finds, aggregated or not.
Yes this does mean that 'site' is no longer an atomic operation and one must
have previously performed an 'install with analysis' build before hand, but as
that makes sense for check and alike, plus many more mojos are going that way.
This loss of 'one click builds all' is not really any loss at all. Plus of
course you can still provide mojos that call the other 'component' mojos to
give the appearance of an atomic execution.
Just something to consider anyway.
We have PMD, Checkstyle, Clover, JDepend, Findbugs and Surefire (to a degree)
working to this pattern and it's pretty cool despite the loss of 'mvn clean
site' doing everything magically for you.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
