After applying a the new fluido skin to a few plugins I see that out
plugins use quite a different set of reports. I realized that I filed
a ticket about this some time ago, but as we all know filing a ticket
doesn't fix a problem but actually acting on it does. So, here goes:

I think that we should have a recommended (or maybe even required?)
set of reports that our plugins should use. There's my suggestions:

* Any production released plugin should use the jira-report of the
m-changes-plugin. We should settle on a common configuration.
* Don't use the changes-report of the m-changes-plugin. Manual updates
of an xml file is sooo the 90s.
* Don't use any of the reports of the m-changelog-plugin. I can't see
the benefit of this info on the site.

Basically, any plugin should just add one reporting plugin to its
reporting section, the maven-changes-plugin (jira-report). Anything
else is handled by the parent.

Comments? Add-ons?

/Anders

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to