[ 
http://jira.codehaus.org/browse/MSITE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133734#action_133734
 ] 

Brian Jackson commented on MSITE-135:
-------------------------------------

I think I'm experiencing this issue or one related to it.  The projects in our 
organization defer their versioning to our release system.  To do this our 
pom.xml files all have their version as "${build.number}" which our release 
system (TeamCity) passes in as a -D style property.  When the pom.xml is 
deployed to our repository it still contains "${build.number}" instead of the 
substituted value.  The only thing this currently screws up is the site 
generation since the maven-site-plugin attempts to download the parent's 
site.xml using this value rather than the correct version number for the 
parent, which can be found in the parent element in the originating pom.xml or 
if that value is RELEASE, in the parent's maven-metadata.xml.  Any chance this 
can be fixed to use the value from one of those two locations instead of 
directly from the parent's pom.xml?

> inherited site.xml files are interpolated with the originating project's 
> model values and not the consumer project's values
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-135
>                 URL: http://jira.codehaus.org/browse/MSITE-135
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: inheritance
>    Affects Versions: 2.0-beta-5
>         Environment: 2.0.4
>            Reporter: John Allen
>             Fix For: 2.0-beta-7
>
>
> inherited site.xml files are interpolated with the originating project's 
> model values and not the consumer project's values
> i have a n-deep multiproject env; when a sub-project uses the root project's 
> site.xml file, any ${project.*} expressions defined in the root site.xml are 
> replaced with values from the root project and not the project that is being 
> rendered, ie. title in index.html would be "root project" and not 
> "sub-sub-sub-project". This applied to all ${project.*} expressions in the 
> site.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to