You can influence it by moving it to the bottom of the modules list in the reactor. If that doesn't do it, then insert a dependency on the others so that it builds last.
-----Original Message----- From: Arthur Gawronski [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 2:50 PM To: [email protected] Subject: Reworking Build Reactor Order Currently, I have Core Project 1 +SubProject 1-1 +SubProject 1-2 +SubProject 1-3 +CoreProject 1pom -> pom.xml Core Project 2 +SubProject 2-1 +SubProject 2-2 +SubProject 2-3 +CoreProject2pom -> pom.xml I have no flexibility as to the locations of the folders. The pom in CoreProject2pom references all subprojects as modules. When doing a clean install, the reactor list is built similarly to the following: SubProject1-3 SubProject1-1 SubProject1-2 coreProject2pom SubProject2-2 SubProject2-3 SubProject2-1 The problem is that coreProject2pom creates my distributable. It tries to move copy and create an assembly of SubProject2 jars that haven't packaged yet. How do I change a dependency or include a script in order to force the coreProject2pom to be built last in my reactor? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
