Sorry I didn't point that out a little better: Yes, it should be a new project which only contains a pom.xml.
Dependencies are only set when they are in the POM. This means that if you have project A as a dependency inside the POM of project B, the dependency is set from B to A and NOT the other way around. Packaging the projects does not change compared to what you're used to, since the eclipse-plugin ONLY works on the eclipse-projects (not the JARs). Or do you package using Eclipse? In that case I'm not sure what happens, but using Maven there's is no problem. > > Would this parent POM be in project A or B, or would it be in its own > Eclipse > project that contains nothing but a pom.xml? > > Wouldn't your suggested approach result in project A getting included as a > project-dependency in project B, which isn't necessary? (There'd be a > bidirectional relationship between project A and B?) > > When packaging project A, would project B's JAR be packaged and included, > or > would I add a separate dependency element just for that? > > Thanks. > > > > MALICE wrote: >> >> Create a POM that you use as a parent to both. If you build this POM, >> the >> eclipse=plugin for Maven will automatically add project B as a >> dependency >> in >> A. And it will add it as Eclipse project-dependencies, not as >> JAR-dependencies. >> >> Small example: >> >> <project> >> <groupId>some.thing</groupId> >> <artifactId>eclipse-master-pom</artifactId> >> <version>unversioned</version> >> <modules> >> <module>../project-a</module> >> <module>../project-b</module> >> </modules> >> </project> >> >> >> >> On Thursday 08 November 2007 16:44, lightbulb432 wrote: >>> Is it possible to specify, as a dependency, another Java project within >>> Eclipse? If I have project A that depends on project B and both are >>> Maven-managed projects, my current options are as follows: >>> - package and install project B everytime it changes, then run mvn >>> eclipse:eclipse of project A to point to the latest version of project >>> B >>> - >>> the problem being that this is inefficient >>> - within Eclipse, simply add project B as a dependency of project A - >>> the >>> problem being that I must do this everytime I update any dependency of >>> project A must re-run eclipse:eclipse, which overwrites the .classpath >>> file >>> >>> Is there a way of adding, in the dependency element, a reference to >>> another >>> Eclipse project so that running eclipse:eclipse points to the Eclipse >>> workspace version of another project? >>> >>> Thanks. >> >> -- >> Roland Asmann >> >> CFC Informationssysteme Entwicklungsgesellschaft m.b.H >> Bäckerstrasse 1/2/7 >> A-1010 Wien >> FN 266155f, Handelsgericht Wien >> >> Tel.: +43/1/513 88 77 - 27 >> Fax.: +43/1/513 88 62 >> Email: [EMAIL PROTECTED] >> Web: www.cfc.at >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/Dependency-on-another-project-tf4771718s177.html#a13650420 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
