maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Pyeron" <jpye...@pdinc.us>
Subject RE: JIRA projects for Maven
Date Mon, 29 Dec 2014 03:00:59 GMT

> -----Original Message-----
> From: Benson Margulies 
> Sent: Sunday, December 28, 2014 21:52
> 
> On Sun, Dec 28, 2014 at 9:18 PM, David Nalley <david@gnsa.us> wrote:
> > On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
> > <bimargulies@gmail.com> wrote:
> >> Dear Infra,
> >>
> >> For historical reasons, the Maven project has a host of 
> JIRA projects
> >> at codehaus. This is not an ideal situation for many reasons.
> >>
> >> In the past, discussions on moving onto ASF infrastructure have
> >> founded on the sheer number: dozens. Infrastructure didn't 
> feel that
> >> they could support that many project, and the Maven 
> project felt that
> >> it would be very difficult to combine all of the many 
> per-maven-plugin
> >> JIRA projects into a single project with many components.
> >>
> >
> > Can you tell me why it would be difficult? E.g. I am envisioning a
> > single maven project, an each plugin has a component instead of a
> > separate project.
> 
> David, I've restored dev@maven to this thread. I suspect that others
> may be more eloquent than I on this; if no one else joins in, I'll
> expand tomorrow some time.
> 
> >
> >> It seems to me that much has changed since the last time that this
> >> subject was explored, so I felt that it was worth re-opening the
> >> discussion. Could the existing main JIRA support a large influx of
> >> low-activity projects? Or would infra consider a separate instance?
> >>
> >
> > The number of projects is not a huge issue. Jira can support many
> > magnitudes more 'projects' than we currently have.
> >
> > Migrating 61 low-activity projects seems like a lot of work;
> > historically, that's involved dumping to XML, potentially 
> deploying to
> > a matching version of the source, and then upgrading the version to
> > match the destination version of Jira, then exporting again and
> > deploying to the destination version. Generally (depending 
> on the way
> > the restore happens) the ticket numbers may not stay the same.
> > Historically, we've had a lot of frustration on this front 
> when we've
> > attempted migrations. Though generally they tend to be larger
> > migrations.
> >
> > That said, how much of this work is Maven willing to bear?
> >
> > --David

I have some spare cycles right now to tackle this.

-Jason

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00. 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message