+1. BTW I noticed on Jira that the new 2.x plugin projects are not grouped into the maven section. If I didn't know they existed and scrolled further, I would have accidentally written a jira against m1, which is what a lot of people might do. (this is the page I'm talking about: http://jira.codehaus.org/secure/BrowseProjects.jspa)
-----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 27, 2005 1:41 PM To: [email protected] Subject: Re: [mojo-dev] managing issues Jeff Genender wrote: > Aren't each of the plugins already subprojects? They are components, not subprojects. There is no notion of a subproject in JIRA. The issues of the component just get globbed in with the rest of the issues as far as roadmapping and voting go. It would be nice if JIRA had this notion but it doesn't. It would also be nice if JIRA had project grouping so that we didn't flood the dashboard with our projects but it doesn't do that well either. > Jason van Zyl wrote: >> Hi, >> >> How are you guys finding working with one project for all the plugins? >> Do you think we should have separate projects like we did with the >> maven plugins themselves? This way we can get the roadmap features >> and apply any of the rules to the mojo plugins that we do to the maven plugins. >> >> Learning from the last time I did this (with the maven plugin) I can >> easily create projects for all the plugins. >> >> Thoughts? >> >> I would simply like to use the same rules and processes here that we >> are for Maven's own plugins. >> > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org the course of true love never did run smooth ... -- Shakespeare
