Sure you could use the ticket, but my experience is that is is not a nice
medium for discussions. Jira-pages can get very long and chaotic.My idea is to
create a table with at least the current reports/plugins, mark it as "to keep"
or "to remove" and the preferred reports/plugins. Robert > Date: Sat, 14 Apr
2012 15:26:36 +0200
> From: and...@hammar.net
> To: dev@mojo.codehaus.org
> Subject: Re: [mojo-dev] Updating development guidelines (MOJO-1654)
>
> What do you mean by overview? What I suggest or what is used in all
> different mojos? I could outline what I suggest here or in the ticket
> (MOJO-1654) and then we could add it to the dev guidelines. I don't
> think we need to use the docs space for this as the dev guidelines are
> on the site.
>
> /Anders
>
> On Sat, Apr 14, 2012 at 15:18, Robert Scholte <rfscho...@codehaus.org> wrote:
> >
> > I don't think cobertura should do that by default, a good CI has the option
> > the specify extra parameters.
> > If there are projects wihch aren't defined as a MOJO-component, all
> > mojo-developers have the rights to add these.
> >
> > Anders, could you create an overview of the current plugins?
> > Maybe we should add a page to http://docs.codehaus.org/display/MOJO/Home for
> > this.
> >
> > -Robert
> >> From: mfriedenha...@gmail.com
> >> Date: Mon, 9 Apr 2012 23:13:51 +0200
> >> To: dev@mojo.codehaus.org
> >> Subject: Re: [mojo-dev] Updating development guidelines (MOJO-1654)
> >
> >>
> >> 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
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
