[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350816#comment-350816
]
Jeremie BOUSQUET commented on MSITE-604:
----------------------------------------
Same issue here with m-site-p 3.3 and maven 3.1.0.
In my case there is no overriding : property is defined only in settings.xml,
not in pom.xml at all. Property is then not replaced at all in child links in
generated html, you get "${property}", url-encoded, in the child modules links
urls.
In effective pom everything is correct though.
> Properties from settings.xml are not recognized in site distribution
> management
> --------------------------------------------------------------------------------
>
> Key: MSITE-604
> URL: https://jira.codehaus.org/browse/MSITE-604
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 3.0
> Environment: Apache Maven 2.2.1 and 3.0.3
> Reporter: Marcin Kuthan
> Fix For: backlog
>
> Attachments: MSITE-604-it.patch, MSITE-604-maven3-2.patch,
> MSITE-604-maven3.patch, MSITE-604.tgz
>
>
> My distribution management section looks like:
> {code}
> <distributionManagement>
> <site>
> <id>${acme-corporate-pom.siteRepositoryId}</id>
> <url>${acme-corporate-pom.siteRepositoryUrl}</url>
> </site>
> </distributionManagement>
> {code}
> Where the default property values are defined in the pom:
> {code}
> <properties>
>
> <acme-corporate-pom.siteRepositoryId>acme-site</acme-corporate-pom.siteRepositoryId>
>
> <acme-corporate-pom.siteRepositoryUrl>scp://sites.intranet.acme.com/var/www</acme-corporate-pom.siteRepositoryUrl>
> </properties>
> {code}
> I'm able redefine properties from command line, the provided repository is
> used instead default one:
> {code}
> mvn site:site site:deploy
> -Dacme-corporate-pom.siteRepositoryUrl=scp://somehost/var/www/sites
> -Dacme-corporate-pom.siteRepositoryId=somehost
> {code}
> But when I redefine properties in the profile in {{settings.xml}}, they are
> ignored. The profile is activated in {{<activeProfiles}} element.
> It looks, than only m-site-p ignores properties defined in the
> {{settings.xml}} file. m-deploy-p recognizes properties as I expected
> (distribution management section for articats deployment is configured in
> similar way to site deployment).
> --
> Marcin Kuthan
> Maven For Enterprise - http://code.google.com/p/m4enterprise/
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
