2009/4/16 David Hoffer <dhoff...@gmail.com>: > I have a few comments/questions. > > I do have the snapshot artifacts on a remote corporate repo. (I will see if > I can block this for this test.)
If you have the artifacts on a remote repository, then when the plugin goes looking for the artifacts (from outside the reactor) it will find them and the plugin at fault will therefore not fail the build. By ensuring that the only source of the artifacts is from the reactor, then whatever plugin is pulling the artifacts from the repository will be forced to fail (thereby finding your problem for you) > > What does -DreResolve do? reResolve will turn around and re-pull the dependencies from the remote repository unless you disable it with -DreResolve=false (reResolve is a parameter of the purge-... goal) > > -Dave > > On Thu, Apr 16, 2009 at 11:09 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> That would be my concern too. >> >> I suspect you can reproduce your build failures if you: >> >> mvn clean >> >> mvn dependency:purge-local-repository -DreResolve=false >> >> mvn install >> >> (assuming that you have not deployed any of the -SNAPSHOT artifacts to a >> remote repository) >> >> you should recreate the build failure and be able to identify the source of >> it better. >> >> -Stephen >> >> 2009/4/16 David Hoffer <dhoff...@gmail.com> >> >> > Isn't that adding yet another plugin to do what maven is supposed to do >> out >> > of the box? I'm concerned about the increase in complexity, when >> something >> > doesn't work is it maven or the incremental plugin? >> > >> > -Dave >> > >> > On Thu, Apr 16, 2009 at 10:37 AM, Dmitry Skavish <skav...@gmail.com> >> > wrote: >> > >> > > I asked the same question on OSGi maillist and they advised me to use >> > > incremental-build plugin: >> https://maven-incremental-build.dev.java.net/I >> > > does exactly what I need, check it out, it could solve your problem as >> > > well. >> > > >> > > On Thu, Apr 16, 2009 at 12:33 PM, David Hoffer <dhoff...@gmail.com> >> > wrote: >> > > >> > > > Then there is a big bug here because I have a multi-module project >> with >> > a >> > > > few modules, the dependent one was built first (as seen in the build >> > log) >> > > > but yet when the depending module was built it did NOT use the >> > dependent >> > > > build rather it went to the repo and downloaded the previously >> deployed >> > > > artifact snapshot. >> > > > >> > > > -Dave >> > > > >> > > > On Thu, Apr 16, 2009 at 10:24 AM, Todd Thiessen <thies...@nortel.com >> > >> > > > wrote: >> > > > >> > > > > FYI. Here is one reference, >> > > > > >> > > > > http://maven.apache.org/pom.html#Aggregation >> > > > > >> > > > > --- >> > > > > Todd Thiessen >> > > > > >> > > > > >> > > > > > -----Original Message----- >> > > > > > From: David Hoffer [mailto:dhoff...@gmail.com] >> > > > > > Sent: Thursday, April 16, 2009 11:46 AM >> > > > > > To: Maven Users List >> > > > > > Subject: Re: Multi-module build is not building with current >> > > > > > module source code >> > > > > > >> > > > > > Then I'm understanding the order of the reactor wrong. I >> > > > > > assumed its top to bottom, that is...just before internal is >> > > > > > built...public is built; and just before security-public is >> > > > > > built...internal is built. >> > > > > > >> > > > > > Can you clarify the order? >> > > > > > >> > > > > > -Dave >> > > > > > >> > > > > > On Thu, Apr 16, 2009 at 9:39 AM, Nick Stolwijk >> > > > > > <nick.stolw...@gmail.com>wrote: >> > > > > > >> > > > > > > Maven always takes the artifacts out of the local >> > > > > > repository. However, >> > > > > > > this is not a problem, because the reactor knows in which order >> > to >> > > > > > > built the projects. Just before your internal project is >> > > > > > built, maven >> > > > > > > has installed the most recent version of security-public in >> > > > > > the local >> > > > > > > repository. >> > > > > > > >> > > > > > > Maybe I don't understand your problem. If that is the case, >> > > > > > please clarify. >> > > > > > > >> > > > > > > Hth, >> > > > > > > >> > > > > > > Nick Stolwijk >> > > > > > > ~Java Developer~ >> > > > > > > >> > > > > > > Iprofs BV. >> > > > > > > Claus Sluterweg 125 >> > > > > > > 2012 WS Haarlem >> > > > > > > www.iprofs.nl >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > On Thu, Apr 16, 2009 at 5:26 PM, Dmitry Skavish >> > > > > > <skav...@gmail.com> wrote: >> > > > > > > > I am having the same problem and would like to know that >> > > > > > as well. Thanks! >> > > > > > > > >> > > > > > > > On Thu, Apr 16, 2009 at 10:19 AM, David Hoffer >> > > > > > <dhoff...@gmail.com> >> > > > > > > wrote: >> > > > > > > > >> > > > > > > >> I have a multi-module build where some modules are dependent >> > on >> > > > > > > >> other modules. What is happening is that the dependent >> > > > > > module is >> > > > > > > >> getting its dependency from the local/corporate maven >> > > > > > repo instead >> > > > > > > >> of the source >> > > > > > > code >> > > > > > > >> that was just built. How do I specify that modules always >> > build >> > > > > > > >> using current source not prior built snapshot jars? >> > > > > > > >> >> > > > > > > >> Here is an example of the problem (it is really simple) >> > > > > > > >> >> > > > > > > >> Parent pom: >> > > > > > > >> <version>0.1-SNAPSHOT</version> >> > > > > > > >> <modules> >> > > > > > > >> <module>public</module> >> > > > > > > >> <module>internal</module> >> > > > > > > >> <module>security-public</module> </modules> >> > > > > > > >> >> > > > > > > >> public pom: >> > > > > > > >> <version>0.1-SNAPSHOT</version> >> > > > > > > >> >> > > > > > > >> internal pom: >> > > > > > > >> <dependencies> >> > > > > > > >> <dependency> >> > > > > > > >> <groupId>${project.groupId}</groupId> >> > > > > > > >> <artifactId>public</artifactId> >> > > > > > > >> <version>0.1-SNAPSHOT</version> >> > > > > > > >> </dependency> >> > > > > > > >> </dependencies> >> > > > > > > >> >> > > > > > > >> security-public: >> > > > > > > >> <dependency> >> > > > > > > >> <groupId>${project.groupId}</groupId> >> > > > > > > >> <artifactId>public</artifactId> >> > > > > > > >> <version>0.1-SNAPSHOT</version> </dependency> >> > > > > > > >> >> > > > > > > >> So what is happening is that instead of internal & >> > > > > > security-public >> > > > > > > >> building using the just built public (note it is first so it >> > was >> > > > > > > >> built first) >> > > > > > > they >> > > > > > > >> go >> > > > > > > >> out and download the last deployed snapshot and build using >> > that >> > > > > > > instead. >> > > > > > > >> >> > > > > > > >> Nothing in the pom dependency syntax really says which >> > > > > > to use but I >> > > > > > > assumed >> > > > > > > >> that because maven 'knows' these are all in the reactor it >> > would >> > > > > > > >> use >> > > > > > > module >> > > > > > > >> source. However this doesn't seem to work, what do I >> > > > > > need to do to >> > > > > > > >> fix this? >> > > > > > > >> >> > > > > > > >> BTW, the goals being run are 'clean deploy site-deploy' >> > > > > > > >> >> > > > > > > >> -Dave >> > > > > > > >> >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > -- >> > > > > > > > Dmitry Skavish >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > >> > --------------------------------------------------------------------- >> > > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > > > > > > For additional commands, e-mail: users-h...@maven.apache.org >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > >> --------------------------------------------------------------------- >> > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > > > > For additional commands, e-mail: users-h...@maven.apache.org >> > > > > >> > > > > >> > > > >> > > >> > > >> > > >> > > -- >> > > Dmitry Skavish >> > > >> > >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
