geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From siss...@insession.com
Subject Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Date Wed, 17 Aug 2005 22:40:04 GMT
"Geir Magnusson Jr." <geirm@apache.org> wrote on 18/08/2005 07:24:10 AM:

> 
> On Aug 17, 2005, at 1:10 PM, Bruce Snyder wrote:
> 
> > On 8/17/05, Geir Magnusson Jr. <geirm@apache.org> wrote:
> >
> >
> >> I think we should consider choosing appropriate timing - it sounds
> >> like a big effort, and how does this fit into what we want to do w/
> >> M5, 1.0, etc  I was going to suggest voting on even doing this, but I
> >> can't imagine that at *some* point in the future, we don't want to be
> >> on M2, so we will go there eventually.  it's just a matter of when...
> >>
> >
> > Is there ever an appropriate time to overhaul the build? Not really.
> 
> Sure there is.  Foe example, in a commercial shop, I'd do it after a 
> major release before knuckling down again.
> 
> >
> > Is the proposed change in the best interest of the project and the
> > community? Yes.
> 
> There's no objection from me on this.  I'm just trying to kick off a 
> conversation about priorities :)

I don't think M5 sounds like a realistic target.  AFAIK, we were 
originally aiming for M5 in August.

It would be helpful if we could identify JIRA issues that would benefit 
from or need m2.  What are the drivers for this work?  Does GERONIMO-853 
need m2, or is it a nice to have?  Any issues that need m2 should be 
linked to this (GERONIMO-851) issue.

Is there a JIRA for the work remaining on the assembly plugin (for maven 
1)?  Would it need or benefit from M2 (I seem to remember m2 being 
mentioned)?

John

> 
> geir
> 


This e-mail message and any attachments may contain confidential, 
proprietary or non-public information.  This information is intended 
solely for the designated recipient(s).  If an addressing or transmission 
error has misdirected this e-mail, please notify the sender immediately 
and destroy this e-mail.  Any review, dissemination, use or reliance upon 
this information by unintended recipients is prohibited.  Any opinions 
expressed in this e-mail are those of the author personally.

Mime
View raw message