Matthew McCullough wrote:
>
> 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.
>
Yeah ... that is a limitation. However, once you have each pom.xml setup its
no longer a problem.
The following worked for me (maven 2.0.4) as each mvn invocation at a
particular level has the rootPOM defined according to its own path. I've got
a project that goes 4 directories deep and am using this in the root pom.xml
for setting pluginDefaults so i can have my filters for the entire project
in one directory.
<build>
<pluginManagement>
<plugins>
<plugin>
<inherited>true</inherited>
...
<configuration>
<defs>${rootPOM}/genericFilters</defs>
</configuration>
...
</plugin>
</plugins>
</pluginManagement>
</build>
-MatthewsProject <rootPOM>${basedir}</rootPOM>
+Core <rootPOM>${basedir}/../</rootPOM>
+Server <rootPOM>${basedir}/../../</rootPOM>
+Client <rootPOM>${basedir}/../../</rootPOM>
+Optional <rootPOM>${basedir}/../</rootPOM>
--
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#a13434676
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
