geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bohn <>
Subject Re: M2 migration status
Date Thu, 09 Mar 2006 17:10:34 GMT
One other thing.  Most of my changes for little-G were in the 
configurations rather than the modules.  These aren't yet included in 
the list of "things to be migrated".

I've updated the Migration Status page to include lists for the configs 
and assemblies.


Joe Bohn wrote:
> Prasad Kashyap wrote:
>> Here's my next concern. For these modules that have migrated to m2, we
>> should include them in the daily G builds as soon as possible. If we
>> don't pull out the m1 build artifacts, project.xml and maven.xml from
>> the migrated modules, then there's a chance that those may get changed
>> behind our backs while we go forward converting more. There might be a
>> regression of issues.
> I have the same concern and voiced it (from the other direction) in my 
> post on little-G.
> We also need to ensure that when we clearly communicate what version(s) 
> of maven are required to build Geronimo, the updated build process, and 
> be aware of the waiting changes that may be impacted before we actually 
> start yanking things.
> To accomplish that last goal we need some way to communicate changes 
> that are waiting or in-progress which may affect or be affected by the 
> M2 conversion.  Then we can work together more closely to ensure that 
> nothing is lost during the conversion.  I will add comments to the M2 
> migration status list with a reference to the little-G JIRA for items 
> where I am aware of overlap.  Can others please do the same for items 
> they are involved in?
> Thanks,
> Joe

Joe Bohn
joe.bohn at

"He is no fool who gives what he cannot keep, to gain what he cannot 
lose."   -- Jim Elliot

View raw message