The reactor mode would only help if you had a parent above A and B that was aggregating both projects. Then all of them would be in the reactor together and you'd be able to influence what gets built. (by default it would build them in the correct order based on dependencies).
On Tue, Aug 4, 2009 at 10:46 AM, Lewis, Eric<[email protected]> wrote: > Hi > > I have a problem, which might be solved using Maven's make-like reactor mode > - but I'm not sure if it is! > > Consider the following projects/modules > > Project A > +--- Module A1 > +--- Module A2 > Project B > +--- Module B1 > +--- Module B2 > > Now, if A1 depends on B1, but B2 depends on A2, it's impossible to build a > refactoring done in the two projects. > Let's say I changed something in A1 and B2, then neither Project A nor > Project B will build, since they're caught in a kind of deadlock. > I will have to build and deploy some modules by hand until the whole build > works (talking of snapshots here, of course). > > Can the make-like reactor mode help me? > > As you can tell, I'm a bit confused ;-) > Thanks for any hints! > > Best regards, > Eric > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
