[
https://jira.codehaus.org/browse/MSITE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318425#comment-318425
]
Fred Cooke commented on MSITE-672:
----------------------------------
Thanks for the insight! I have to say, I'm quite surprised to find that the
interpolation is done almost manually on a per field basis. That just seems
insane.
For reference:
https://maven.apache.org/ref/3.0.4/xref/org/apache/maven/model/merge/MavenModelMerger.html#419
Your possible fix around would work for me, I think.
Currently my work around is to declare the property with vars in the parent
with a short name, and just fill out the site distribution with that variable
in the children, but I strongly dislike the duplication of it. My goal is an
empty pom for simple library builds.
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
