On 2/20/2006 3:20 AM, Gianny Damour wrote:
Alan D. Cabrera wrote:
Does the entire system need to build using a single command for this
interim conversion? Why not have people do a
mvn install
maven new
The "mvn install" will build both maven 1 and 2 jars. The "maven
new" will use the maven 1 jars.
That also works. This approach assmes that the M2 modules that we
migrate do not depend on modules which have not yet been migrated to
M2 - basically, this implies that modules are migrated in the same
order than the build order derived by the M1 reactor.
I think that I like this approach better than my previous idea, where
any module could be migrated - whatever its dependencies. However, I
am not really keen to have people use two commands and would prefer to
simply use the maven command which triggers the mvn command under the
cover.
I think that this has already been suggested by David J.: we add a
goal, e.g. new000, which is executed between new00 and new1. new000
launches mvn install in the root project directory. We add to the
excludes list of new1 the migrated modules (we could also remove the
M1 project files after migration).
If I see yet *another* new fangled way to build Geronimo, I'll go
postal. Let's go w/ the two command system whereby we do things the
sane way in maven 2, i.e. "mvn install". Let us leave our sordid past
behind and begin anew.
Seriously, this futzing has got to stop.
Regards,
Alan
