I've never tried this exact scenario, but couldn't you also do this in the root pom and remove A3 and B4 from the A and B poms respectively?
<module>A</module> <module>B</module> <module>A/A3</module> <module>B/B4</module> Of course this assumes that previous modules don't depend on A3 or B4. Chris On Tue, Mar 18, 2008 at 7:19 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Maven starts with the ordering listed in the poms (A and its children, > then B and its children, etc) unless there is a dependency. If it sees a > dependency, then it will automatically reorder by pushing down modules > that have a dependency so they build after their dep. > > I'm wondering why the order matters if you don't have a dependency > listed (I'm assuming you don't or it would be ordered already). > > -----Original Message----- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 18, 2008 4:42 AM > To: Maven Users List > Subject: Customizing Build order > > Hi, > I have a multi-module project with the following structure. > > Root > -A > -A1 > -A2 > -A3 > -B > -B1 > -B2 > -B3 > -B4 > > > In the Root's pom i have mentioned my modules as: > <module>A</module> > <module>B</module> > > Now is there a way that I can change the normal build order(which is) > > -Root > -A > -A1 > -A2 > -A3 > -B > -B1 > -B2 > -B3 > -B4 > > > to something like > > -Root > -A > -A1 > -A2 > -B > -B1 > -B2 > -A3 > -B4 > > It is actually a requirement. But I doubt that there is a possibility > that > the CVS structure itself is not competent enough then to handle > inter-module > dependencies. > > Any inputs? > > Thanks and regards, > Amit Kumar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
