Brett Porter wrote:
ping?
Brett Porter wrote:
As per my comment here:
http://jira.codehaus.org/browse/MNG-366#action_40689
This is what I think needs to be changed WRT the reporting to get them
properly configured and consistent with the build plugins. Please let
me know if you disagree or have any questions.
- if in <reports> the configuration applies to the report, which may
be different to the mojo in <build/> if the plugin is executed there.
So we need that separate section.
I think it's more usable if user configure reports only in <reports>.
- currently, the report is not configured at all, as we use a map lookup
- similar to executeMojo, a getReport method should get a configured
MavenReport
- really, the site mojo is like another lifecycle executor in its role
for hooking into the plugin manager and executing a report instead of
a mojo. share commons code. It may actually be another lifecycle?
I think we need it because some reports need to execute some other mojo
like compile for clover and jcoverage, and surefire for test report.
We can have a similar lifecycle to the actual, and we put the site mojo
in place of package
- also remove the MavenConfiguration inline with this, as above
+1
- how does this correlate to the new <executions/> element? Should
also apply here, so a report can run twice with different configurations.
<reports>
<plugins>
<plugin>
<g/a/v>
<configuration />
<report>
<id>mail-lists</id>
<configuration />
+1
Emmanuel
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
