[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325020#comment-325020
]
Jörg Schaible commented on MSITE-604:
-------------------------------------
Is there anything else we can do to bring this forward? We have now a release
3.3 and we're still, stuck with version 3.0-beta-3, since we cannot deploy our
reports with any newer version! We do exactly, what Herve and Vincent said in
their last comments: All properties used in the distribution URL are defined in
the settings.xml, but instead of being interpolated they are URL escaped:
{noformat}
[INFO] --- maven-site-plugin:3.3:deploy (default-cli) @ scalaris-commons-xam ---
[INFO] Parent project loaded from repository:
com.scalaris.buildsystem.maven2:master:pom:261
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.083s
[INFO] Finished at: Tue May 14 08:58:55 CEST 2013
[INFO] Final Memory: 47M/385M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:deploy (default-cli) on project
scalaris-commons-xam: Execution default-cli of goal
org.apache.maven.plugins:maven-site-plugin:3.3:deploy failed: Base URI is not
absolute: $%7bscalaris.site.url.base%7d -> [Help 1]
{noformat}
An IT is available, a patch is available and all of it simply bit rots!
> Properties from settings.xml are not recognized in site distribution
> management
> --------------------------------------------------------------------------------
>
> Key: MSITE-604
> URL: https://jira.codehaus.org/browse/MSITE-604
> Project: Maven 2.x and 3.x 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 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
