Properties defined in top-level profiles.xml do no propagate to child modules
-----------------------------------------------------------------------------

         Key: MNG-2157
         URL: http://jira.codehaus.org/browse/MNG-2157
     Project: Maven 2
        Type: Bug

  Components: POM  
    Versions: 2.0.2    
    Reporter: Jason Dillon
    Priority: Blocker


I have a multi-module build, and at the top-level I have a profile called 
'release-environment', which is activated by -Denv=release.

I need the local release build to use different values for JDBC configuration 
to run integration tests, and defined them in a profiles.xml:

{code}
<?xml version="1.0" encoding="UTF-8"?>

<settings>

    <profiles>
        <profile>
            <id>local-release-environment</id>
            <activation>
                <property>
                    <name>env</name>
                    <value>release</value>
                </property>
            </activation>
            
            <properties>
                <jdbc.username>mif_jason</jdbc.username>
                <jdbc.password>mif_jason</jdbc.password>
                <jdbc.schema>MIF_JASON</jdbc.schema>
            </properties>
        </profile>
    </profiles>
    
</settings>
{code}

My project looks like:

pom.xml
merchant/pom.xml
merchant/core/pom.xml
merchant/services/pom.xml

If i put profiles.xml as a peer to pom.xml and run {{mvn clean install 
-Denv=release}} from the top-level, I get errors because the properties are not 
propagated to the merchant/core/pom.xml module.

If I put profiles.xml as a peer to merchant/core/pom.xml and run {{mvn clean 
install -Denv=release}}, then it works as expected... properties are set as 
they are defined in profiles.xml.

But, this is not manageable, as I need to set some properties for all of the 
modules in a multi-module build... But I don't want to use those properties for 
all Maven2 projects, so I can not really put it into ~/.m2/settings.xml

I had expected that a top-level profiles.xml would work, but it does not.  Is 
this by design, is there another recommend way to provide per-top-level 
multi-module project configuration on a local user basis (ie. no pom.xml 
modifications)?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to