I am somewhat confused by the design of the site plugin with respect to adding additional goals.
The new pattern is to move from 'aggregate' configuration property booleans to more goals. However, goals have to be called out in executions, and the reporting section can't spec an execution, and we're moving away from the reporting section, anyway. So now you end up with the same plugin called out as an ordinary plugin as well as in a report, and it needs an execute method that does the same thing as its executeReport, and both get called. Is there anything written down about how all this is supposed to play? Can the site plugin be told which goal to run executeReport for, or are these additional executions actually needed. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
