[
https://jira.codehaus.org/browse/MSITE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273059#comment-273059
]
Lukas Theussl commented on MSITE-585:
-------------------------------------
The problem arises when the distMgmnt section is inherited from the parent but
uses properties that are only defined in the child. I am not sure if this is
supposed to be a supported use-case, it is certainly not best practice (e.g.
the parent pom will not be deployable by itself). Inheritance only works from
parent to child, not from child to parent.
This probably only worked in older versions of the site plugin because the
parent site url was not used for deploy. This is not the case anymore since
site-plugin-2.3 to fix some other issues with multi-module deploy, eg
MSITE-537.
Note:
*) according to the
[docs|http://maven.apache.org/plugins/maven-site-plugin/usage.html] ??''If
subprojects inherit the site URL from a parent POM, they will automatically
append their <artifactId> to form their effective deployment location.''?? so
even in the original setup of the IT the resulting deploy location is probably
not what was intented, as given by ${site.repository}.
*) as per remarks above, the parent pom has to include some default values for
any used properties. Those may be overridden by inheriting poms, but each pom
needs to be fully resolvable based on its own inheritance structure.
> site-deploy: empty deploy protocol when properties are used
> -----------------------------------------------------------
>
> Key: MSITE-585
> URL: https://jira.codehaus.org/browse/MSITE-585
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: property interpolation
> Affects Versions: 2.3
> Reporter: Lukas Theussl
>
> See http://www.mail-archive.com/dev@maven.apache.org/msg88029.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
