hello
If you put in a pom
<distributionManagement>
<site>
<id>website</id>
<name>company-project-web-site</name>
<url>
file:\\host\intranet/Maven/sites
</url>
</site>
</distributionManagement>
It defines the root of the website for this pom.
When you set this pom in a child pom, the plugin will automatically set
folder tree in the same way.
For example
in superPom defines the distribution site
in sharedPom1 defines whatever you need (pluginmanagement conf ... ) with
parent as superPom
in sharedPom2 defines whatever you need (pluginmanagement conf ... ) with
parent as sharedPom1
in childPom defines a project with parent as sharedPom2
you will get the website with
\\host\intranet/Maven/sites/sharedPom1/sharedPom2/childPom
now set the distributionManagement site in sharedPom1
you will get the website with
\\host\intranet/Maven/sites/sharedPom2/childPom
now set the distributionManagement site in childpom
you will get the website with \\host\intranet/Maven/sites/
-Using aggregation of pom will not change this behavior : it's always the
parent pom which use for the folder tree.
-I don't known what happen if you set a relativePath
hopes my engRish is understandable
cordialement.
--
View this message in context:
http://www.nabble.com/Maven2.-Variables.-pom-inheritance.-Strange-behavour.-tf1936878.html#a5310014
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
