Stijn, You must explicitly include B and C dependencies in project D's project.xml. As mentioned earlier in this thread, Maven 2 will support what is called "transitive dependencies", meaning that in the future, you will not have to explicitly specify these implicit dependencies. However, for now, you must explicitly specify them.
-- Chuck > -----Original Message----- > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 03, 2004 11:57 AM > To: Maven Users List > Subject: Re: List all dependencies or only main ones? > > > Hi Reddy, > > Let me show it with an example > > Project a is a maven project, using two jars, B-1.0.jar and C-1.0.jar. > Projects B and C are plain jars > Project D is a maven project, using 1 jar, A.1.0.jar. > > A: project.xml > .. > <dependencies> > <dependency> > <groupId>B</groupdId> > <artifactId>B</artifactId> > <version>1.0</version> > <properties /> > </dependency> > > <dependency> > <groupId>C</groupdId> > <artifactId>C</artifactId> > <version>1.0</version> > <properties /> > </dependency> > </dependencies> > .. > > D: project.xml > .. > <dependencies> > <dependency> > <groupId>A</groupdId> > <artifactId>A</artifactId> > <version>1.0</version> > <properties /> > </dependency> > </dependencies> > .. > > The final program (D) will need all 4 jars to run, but does that > mean that I > have to add the dependencies from project A to D, or will maven be able to > determine from project A's pom that it has to include B-1.0.jar and > C-1.0.jar to? > > "...why don't you try using remote repository call them in project A > (project.xml) instead of calling in each and every project." > > This sounds like an interesting possibility, could you explain > some further? > > Thanks, > -Stijn > > > ----- Original Message ----- > From: "Reddy MVS" <[EMAIL PROTECTED]> > To: "'Maven Users List'" <[EMAIL PROTECTED]> > Sent: Tuesday, August 03, 2004 12:37 PM > Subject: RE: List all dependencies or only main ones? > > > > Hi Stijn, > > > > > > > > I am not sure. Let me do some research let you know the status, why > don't > > you try using remote repository call them in project A (project.xml) > instead > > of calling in each and every project. The compilation needs all the > > dependencies in local repository. I think it doesn't worry about weather > you > > call all the dependencies in Project A or Project B if it's depending on > > other project. If you run alone you need to call dependencies for > respective > > Library files (.jar). Also what do you mean by main ones? > > > > Thanks > > > > Reddy MVS > > > > > > > > -----Original Message----- > > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, August 03, 2004 3:40 PM > > To: Maven Users List > > Subject: List all dependencies or only main ones? > > > > > > > > Hi, > > > > > > > > A quick question. Assume a project A, which depends on projects B and C. > If > > > > project D depends on A, does it also have to state it's (implicit) > > > > dependencies on B and C in project.xml? > > > > > > > > TIA, > > > > -Stijn > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
