You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ws...@cox.net on 2012/10/30 22:15:03 UTC

Re: [jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

PLEASE REMOVE ME FROM THIS MAILING LIST!!!

---- "Herve Boutemy (JIRA)" <ji...@codehaus.org> wrote: 

=============

    [ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312635#comment-312635 ] 

Herve Boutemy commented on MSITE-604:
-------------------------------------

yes, you should force users to define the value in their settings.xml, and cannot provide a default value in pom for those that didn't do their config

(for the doc, I'm writing things I'm learning year after year on Maven internals, then doc is improving version after version: see http://maven.apache.org/ref/3.1-SNAPSHOT/ for latest improvements)
                
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

--
Wayne E Seth PMP CEA
Enterprise Architect
(c) 520-456-6169

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org