Hi, Emmanuel has done some good work on the reporting API and it is nearly ready. In discussing it, we noted a couple of issues worth discussing.
Firstly, are report JARs regular plugins, or should they have the type "maven-report"? We believe they should be one JAR - ie only a maven-plugin type. - On the upside, this means that when you have a goal and a report doing similar things (eg the clover test that fails if a certain coverage % is missed, as well as the generated report), the code is all together and there are just a mojo and report class in the JAR. - On the downside, you are incurring a maven-plugin-api dependency on someone only doing reporting, and a maven-reporting-api dependency on someone only doing a plugin when the JAR provides both. I don't believe this is a big deal. An alternative is to have the reporting mojo in a separate jar that depends on the mojo, overcoming the latter which is probably the only real problem. Thoughts? Now, currently the report manager is a separate entity, used by the site plugin. It resolves the reports on demand, similarly to the plugin manager. If a report is a plugin, should the single plugin manager be used? I think that it probably should, but we can defer the work on this until we are certain. Also, I think we need to introduce a pluginManagement section to <reports /> so that report plugin configuration can be done in the same way as build plugin configuration. Does everyone agree? Emmanuel, did I miss anything? Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
