Hello,
while we are at this, it would come quit handy when the cobertura report would render XML as well, so CI systems are able to pick up the values :-). In regards to changes from JIRA: Every non trivial change should come with a corresponding JIRA issue then, right? My only concern here would be that a lot of MOJOs do not have an own project in JIRA and the "standard" MOJO project should at least define a component for those. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Mon, Apr 9, 2012 at 20:15, Anders Hammar <and...@hammar.net> wrote: > 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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
