That's right about the dep plugin and others that expect to manipulate a jar (if you wanted me to copy a jar, what should I do when I'm handed a folder with classes?). In compile of a reactor build, you get a handle to the classes folder, package will get you a handle to the jar in the target folder and install+ will get you a handle to the jar in the local repo.
-----Original Message----- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 2:00 AM To: Maven Users List Subject: Re: Running two builds of the same branch simultaneously On Thu, Mar 20, 2008 at 3:36 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote: > Brian E. Fox wrote: > > >> Samuel Le Berrigaud wrote: > >> > >>> 1. only run mvn verify, this way nothing gets installed into the local > >>> repository, > >> > >> This doesn't work in a multi-module reactor build where the modules > >> depend on each other, does it? > > > No, it will only work if you at least do compile (then a reference to > > /target/classes is passed instead of the jar) > > Huh? verify is after compile, right before install. (Actually, I did > "package", then later tried "verify" to see if it would work; neither > did.) Should that have worked? > > -Dan > Are you using maven-dependency-plugin at all? if you are then you should be using the "copy-dependencies" or "unpack-dependencies" goals and not the "copy" or "unpack" goals for those dependencies that come from the reactor, otherwise the build will fail as you describe -Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
