You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joerg Schaible (JIRA)" <ji...@codehaus.org> on 2012/10/18 11:02:36 UTC
[jira] (MSITE-604) Properties from settings.xml are not recognized
in site distribution management
[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311763#comment-311763 ]
Joerg Schaible commented on MSITE-604:
--------------------------------------
bq. What am I missing?
Don't know. I even tried to modify the IT with:
{noformat}
Index: src/it/MSITE-604/invoker.properties
===================================================================
--- src/it/MSITE-604/invoker.properties (revision 1399549)
+++ src/it/MSITE-604/invoker.properties (working copy)
@@ -1 +1 @@
-invoker.profiles = msite604
+#invoker.profiles = msite604
Index: src/it/MSITE-604/pom.xml
===================================================================
--- src/it/MSITE-604/pom.xml (revision 1399549)
+++ src/it/MSITE-604/pom.xml (working copy)
@@ -33,14 +33,15 @@
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+ <msite604.siteProtocol>scpexe://</msite604.siteProtocol>
<msite604.siteRepositoryId>defaultId</msite604.siteRepositoryId>
<msite604.siteRepositoryUrl>defaultRepositoryUrl</msite604.siteRepositoryUrl>
</properties>
<distributionManagement>
<site>
<id>${msite604.siteRepositoryId}</id>
- <url>file://@project.build.directory@/it/MSITE-604/target/${msite604.siteRepositoryUrl}</url>
+ <url>${msite604.siteProtocol}@project.build.directory@/it/MSITE-604/target/${msite604.siteRepositoryUrl}</url>
</site>
</distributionManagement>
Index: src/it/settings.xml
===================================================================
--- src/it/settings.xml (revision 1399549)
+++ src/it/settings.xml (working copy)
@@ -63,9 +63,13 @@
<profile>
<id>msite604</id>
<properties>
+ <msite604.siteProtocol>file://</msite604.siteProtocol>
<msite604.siteRepositoryId>settingsId</msite604.siteRepositoryId>
<msite604.siteRepositoryUrl>settingsRepositoryUrl</msite604.siteRepositoryUrl>
</properties>
</profile>
</profiles>
+ <activeProfiles>
+ <activeProfile>msite604</activeProfile>
+ </activeProfiles>
</settings>
{noformat}
but it runs still...
However, even with version 3.2 we get in our real projects:
{noformat}
$ mvn clean site site:deploy
...
[INFO] --- maven-site-plugin:3.2:deploy (default-cli) @ acmepro-report-parent ---
[INFO] Parent project loaded from repository: buildsystem.maven:master:pom:x-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] acmepro Report Parent Project ..................... FAILURE [13.295s]
[INFO] acmepro Report Providers .......................... SKIPPED
[INFO] acmepro Report EAR ................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.701s
[INFO] Finished at: Thu Oct 18 09:01:49 CEST 2012
[INFO] Final Memory: 26M/265M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:deploy (default-cli) on project acmepro-report-parent: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.2:deploy failed: Base URI is not absolute: $%7bacmepro.site.url.base%7d -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{noformat}
Since it retrieves the parent from the repository (which contains also an URL for the site with that property), it does probably complain about that one?
> 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-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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira