ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré>
Subject Re: Mavenization
Date Sun, 06 Dec 2009 20:10:32 GMT
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).


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