[
https://jira.codehaus.org/browse/MSITE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324292#comment-324292
]
Fred Cooke commented on MSITE-672:
----------------------------------
Herve, it certainly can be different! It could honour the effective pom! If it
did that, even if we were forced to *configure* it to do that, due to backward
compatibility with 28340986098 SVN projects, then that would be adequate. The
expectation of any user of maven is that variables will trickle down and end up
defined at the lowest level. Injecting "random" hard coded behaviour into the
middle of this just creates confusion and chaos. A lower level plugin could
explore the tree to find specific details if it so wished, however a lower
level user is SOL if it's all hard coded above them. No where in any maven docs
does it state that these fields will be abused and manipulated in bizarre ways
out side of the usual effective-pom contract. At least give us the power to
have that fundamental functionality in these fields. Thanks in advance :-)
> Interpolation of site deploy URL not done in child
> --------------------------------------------------
>
> Key: MSITE-672
> URL: https://jira.codehaus.org/browse/MSITE-672
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 3.0
> Environment: Debian Linux OpenJDK 7 mvn 3.0.4
> Reporter: Fred Cooke
>
> I have my parent distribution site config filled out like so:
> {{<url>scp://private-site/home/private/site/releases/$\{project.groupId}/$\{project.artifactId}/$\{project.version}/</url>}}
> When the child tries to release:perform or {{site:deploy}} it tries to upload
> with the parent arifactId, groupId and version instead of the current project
> values. These should be interpolated like any other variables in the POM to
> prevent needless duplication in all children.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
