[
https://jira.codehaus.org/browse/MSITE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324296#comment-324296
]
Herve Boutemy commented on MSITE-672:
-------------------------------------
"It could honour the effective pom!": how do you think the effective pom is
calculated? it is the dump of the result, nothing more.
"these fields will be abused and manipulated in bizarre ways out side of the
usual effective-pom contract": nothing is used nor abused, you're completely
mistaken. Everything follows the "effective-pom contract" because the contract
is in fact done before the effective-pom dump you know.
The way effective POM is calculated is written [in the
doc|http://maven.apache.org/ref/3-LATEST/maven-model-builder/]: I wrote it in
plain english just because it's not so easy to understand. Nothing is random,
confused, abused nor manipulated in bizarre ways: it's just not so easy to
really understand because the order in computation steps has important impacts.
Having more configuration options can be good, if people undertand them, or it
will even more wreak havok because more options represents more complexity.
For the moment, what I get from this discussion with someone feeling it is
confused is that I need to improve [POM reference
documentation|http://maven.apache.org/ref/3-LATEST/maven-model/maven.html] to
explain how interpolation happens in "magical" fields like
distributionManagement url: if users don't understand the actual "basic"
situation, adding options will only add confusion
> 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
