[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Schaible updated MSITE-604:
--------------------------------
Attachment: MSITE-604-it.patch
New MSITE-604-it.patch against svn rev 1630660. IT executed with:
{noformat}
rm -rf target/it
mvn integration-test -Prun-its -Dinvoker.test=MSITE-604
{noformat}
The patch modifies the IT to reflect my local setup. However, the embarrassing
part is, that it succeeds. My setup:
{noformat}
$ mvn -version
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T22:58:10+02:00)
Maven home: /usr/share/maven-bin-3.2
Java version: 1.7.0_67, vendor: Oracle Corporation
Java home: /opt/oracle-jdk-bin-1.7.0.67/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.14.14-gentoo", arch: "amd64", family: "unix"
{noformat}
Nevertheless, I still have this error in my real projects:
{noformat}
[INFO] --- maven-site-plugin:3.4:deploy (default-cli) @ scalaris-commons-xam ---
[INFO] Parent project loaded from repository:
com.scalaris.buildsystem.maven2:master:pom:273
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.222 s
[INFO] Finished at: 2014-10-10T14:07:46+02:00
[INFO] Final Memory: 61M/603M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:deploy (default-cli) on project
scalaris-commons-xam: Execution default-cli of goal
org.apache.maven.plugins:maven-site-plugin:3.4:deploy failed: Base URI is not
absolute: $%7bscalaris.site.url.base%7d -> [Help 1]
{noformat}
In contrast to the IT, the site plugin generated some real reports before.
Maybe the classpath is poluted with an old version of the component handling
the substitutions in the URL? Can someone tell me, which component is
internally actual responsible for it?
> 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-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)
