Hi,
From how I understand on how the relativePath works, it is used for
resolving the parent pom (being inside the parent tag).
When you run mvn on a sub-module, mvn detects that the sub-module has a
parent and mvn tries to resolve that using either the
groupId:artifactId:version for the
-Original Message-
From: Edwin Punzalan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 14, 2006 10:40 AM
To: Maven Users List
Subject: Re: [m2] Multi-Project setup and relativePath
[...]
So the approach is, if you want to use an artifact, then that artifact
must have been
Hi maven-users!
I've got a m2 project with several levels of sub-modules, held together by a
main pom of packaging type pom. In each sub-module there is a parent entry
pointing to the module above, including the relativePath tag pointing to
../ .
I don't quite understand the use of the
