This is a creative idea, but appears only to work if your leaf nodes of the
project are all at the same level so that the ../../ is consistently just
the right amount "back up" the directory tree.
For example, it doesn't appear to work on a project structure like this,
where each node has a pom.xml:
-MatthewsProject
+Core
+Server
+Client
+Optional
It works for Server and Client, but Core and Optional complain because they
are reaching one level too far out for the parent.
Suggestions? Is this consistent with what you are seeing as well if you
have a 2 and 3 level deep tree of projects?
Sincerely,
Matthew McCullough
Managing Partner
Ambient Ideas, LLC
clamb wrote:
>
> OK, i've been fighting this battle for a few days now and have a fairly
> ugly solution.
>
> in every pom.xml define a common root property:
>
> <properties>
> <rootPOM>${basedir}/../</rootPOM>
> </properties>
>
> Ensure that you have enough ../ to reference the rootPOM directory.
>
> Everywhere you need to refer to this super root directory use ${rootPOM}.
>
>
>
> Matthew McCullough wrote:
>>
>> My far-from-modern CM group requires that we check in the binary
>> artifacts for our 3ps, and depend on them from a VOB checked out of
>> ClearCase. So our repo, as is now supported in Maven 2, is a
>> "file://../../3pvob" type of path rather than an HTTP path.
>>
>> Let me know if you have any more ideas on this. And thanks again all.
>>
>> -Matthew
>>
>
>
--
View this message in context:
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html#a13434309
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
