But then how does Maven know that it needs to re-build the parent artifact? Based on the changing snapshot id tied to the dependency taken from the repo?
Alan D. Salewski wrote: > > On Wed, Jan 03, 2007 at 07:18:17PM -0500, Trevor Torrez spake thus: >> Is it the suggested / best practice to have a subproject in a multi >> project >> setup to declare it's dependencies on the other subprojects in the >> dependency section? > > Yes. > > >> This leads to requiring some parts of the multi-project >> to be installed to the local repository before other parts can be >> developed >> (using the eclipse:eclipse goal fails if the dependency / subproject is >> not >> installed). [...] > > That's correct. The reason is that maven-2.x is (by design) repository > based; when maven needs a dependency, it looks for it in your local > repos (regardless of whether it's another subproject within the project > that is building, or something else). That's just how it's supposed to > work. > > -Al > > -- > :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: > :: > Alan D. Salewski > Software Developer > Health Market Science, Inc. > :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: > :: > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a9314490 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
