It'd make more sense to have m1 exec m2 so that your master build is last to convert. This should be possible with <exec />.
Forking is probably slow, but forking m2 is probably faster than the m1 build anyway :) - Brett On 2/15/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > If m2 could exec an m1 build (following global dependencies) or if m1 > could invoke m2, this conversion would be much easier as we could > convert a module at at time. > > -dain > > On Feb 14, 2006, at 2:03 PM, Alan D. Cabrera wrote: > > > On 2/14/2006 3:09 AM, Anders Hessellund Jensen (Trifork) wrote: > > > >> I'd like to help migrating to maven 2. > >> > >> Where to start? I suppose a good start would be to write POM's for > >> some of the modules. This should be fairly straightforward, at > >> least for modules without complex jelly usage. Should the > >> directory layout be configured to maven 1 style in the parent POM? > > > > > > We've tried to do an uber move and it's never worked. I recommend > > that we move bits over one at a time. Maybe we could kill two > > birds with one stone and also perform the breakout that Aaron > > proposed at the same time. > > > > > > > > Regards, > > Alan > > > > > >
