[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290463#comment-290463
]
Joerg Schaible edited comment on MSITE-604 at 2/1/12 5:23 AM:
--------------------------------------------------------------
We face the same problems. In our case we deploy the site documentation to our
intranet and depending on the environment the base URL is a file protocol with
different paths or scpexe. Therefore we have to use a property from
settings.xml.
The attached test project MSITE-604.tgz demonstrates the effect. Since our
property contains the protocol, we get this "{{Wagon protocol '' doesn't
support directory copying}}" error.
However, it seems that the usage of a parent located in the repository is part
of the problem.
You may test the project with the call
{noformat}
mvn -s settings.xml clean package site site:deploy
{noformat}
Have a look at the README.txt for simple preparation and alternate calls to
select the site-plugin version from command-line.
M3 fails with site-plugin 3.0, but succeeds with 3.0-beta-3 and will generate
no HTMLs for site-plugin version 2.x. M221 fails with site-plugin versions 3.0
and 2.3.
I've also linked this issue to MNG-617, MNG-585 and MNG-501 that seem to be
related.
was (Author: joehni):
We face the same problems. In our case we deploy the site documentation to
our intranet and depending on the environment the base URL is a file protocol
with different paths or scpexe. Therefore we have to use a property from
settings.xml.
The attached test project demonstrates the effect. Since our property contains
the protocol, we get this "{{Wagon protocol '' doesn't support directory
copying}}" error.
However, it seems that the usage of a parent located in the repository is part
of the problem.
You may test the project with the call
mvn -s settings.xml clean package site site:deploy
Have a look at the README.txt for simple preparation and alternate calls to
select the site-plugin version from command-line.
M3 fails with site-plugin 3.0, but succeeds with 3.0-beta-3 and will generate
no HTMLs for site-plugin version 2.x. M221 fails with site-plugin versions 3.0
and 2.3.
> 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: 3.1
>
> Attachments: 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
