----- Original Message ----- 
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[email protected]>
Sent: Thursday, April 28, 2005 4:21 AM
Subject: reporting API


> 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?

I prefer the first solution because these two dependency are very light
(<10k).
I think it's better for developpers and users to have the goal and the
report in the same place, they will not have to search where are the two
parts.

>
> 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?

Yes.

>
> Emmanuel, did I miss anything?

We still need to define the process for internaltionalize report.

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]

Reply via email to