If granddaddy has child2 as a <module>, then it will go into that directory, build the module, and use that module when it is building the other dependencies.
You could test this by "mvn clean install" then adding a new method in child2, and finally using that method in grandchild1's code. If it fails, you have a good idea it is using the previously-installed code. Wayne On Mon, May 12, 2008 at 5:09 PM, Dhruva Reddy <[EMAIL PROTECTED]> wrote: > Sorry if this scenario is a bit involved.... > > Take the following multi-module project: > > -granddaddy > -child1 > -grandchild1 > -child2 > -child3 > -grandchild2 > > granddaddy is a parent of child1, child2 and child3, child1 is a parent > of grandchild1 and child3 is a parent of grandchild2. granddaddy > aggregates child1, child2 and child3. child1 aggregates grandchild1 and > child3 aggregates grandchild2. > > child2 does not depend on any of its sister projects, but grandchild1 > and grandchild2 both depend on child2. > > My question is, if you build and install child2 (i.e., navigating to the > child2 directory and running "mvn clean install"), then run "mvn clean > package" at the top, how is the dependency on child2 resolved? Does it > look in the local repository, or does it still build child2 as needed > and use that? > > Thanks, > Dhruva > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
