ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Topping <>
Subject Re: Mavenization
Date Sun, 06 Dec 2009 23:20:03 GMT
Hi guys,

Sorry I'm coming late on this, had a network emergency locally.

I agree that the github repo should be disregarded moving out.  We  
didn't do anything with it and changes are hard.

I might differ that we should be working on a branch, unless all  
committers are prepared to do a clean checkout and build until we are  
done.  Leftover artifacts in source and build directories can be  
troublesome, and it may be easier to not take chances with the Ant  
build as we get things moved around for Maven.

I'm okay in any event, just wanted to add $0.02...

Cheers, Brian

On Dec 6, 2009, at 3:10 PM, Jean-Baptiste Onofré wrote:

> Hi Toni,
> Totally agree to work directly on the asf repo and we should  
> consider the github repo as deprecated.
> I propose:
> 1/ to commit the ace-pom containing all informations shared between  
> ace sub-projects and branches
> 2/ begin to create sub-projects per module. For example, I think  
> that the current ace current is too large. We should consider to  
> split into several maven sub-project (modularize).
> Regards
> JB
> Toni Menzel wrote:
>> Hi,
>> Because
>> - Brian, Jean-Babtiste, and me are now full committers
>> - Changes on github fork are small, i would go for keeping the  
>> mavenization
>> work at the apache repo and commit stuff right away in either:
>> a.) a branch[ant2maven]
>> b.) directly in trunk, but keeping the current structure alive in  
>> parallel.
>> (doable because changes are either new (poms, folders) or copies
>> (resources/sources).
>> c.) history is preserved and no git/svn bridging work is required  
>> when
>> merging back.
>> whats the way to go for ? Would then try to keep this in sync (for  
>> everyone
>> to collaborate) and done as soon as possible.
>> wdyt ?
>> Toni
> -- 
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> PGP : 17D4F086

View raw message