[ 
http://jira.codehaus.org/browse/MNG-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Bentmann updated MNG-4300:
-----------------------------------

    Attachment: pom.xml

See the attached file for a working example of multiple profiles activated from 
the same POM, e.g. run "mvn help:active-profiles".

Let me point out that Maven as a build tool is somehow similar to a filter, it 
gets some input and produces some output. So if we want to talk about bugs, 
please provide detailed information about the inputs you feed into the tool and 
the outputs you expect. Otherwise we have no basis for a proper analysis of the 
issue.

BTW, the issue the user had on the mailing list is simply a misunderstanding of 
{{<activeByDefault>}}. From [Introduction to 
Profiles|http://maven.apache.org/guides/introduction/introduction-to-profiles.html]:
{quote}
This profile will automatically be active for all builds unless another profile 
in the same pom is activated using one of the previously described methods. All 
profiles that are active by default are automatically deactivated when a 
profile in the pom is activated on the command line or through its activation 
config.
{quote}

> Maven does not support multiple activted profiles in the same pom.xml at the 
> same time.
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-4300
>                 URL: http://jira.codehaus.org/browse/MNG-4300
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 2.0.7, 2.0.8, 2.0.9, 2.0.10, 2.1.0-M1, 2.1.0
>         Environment: windows XP + sun jdk 1.6
>            Reporter: Shawn Jiang
>         Attachments: pom.xml
>
>
> Maven does not support multiple activted profiles in the same pom.xml at the 
> same time.  I found another users also met this before.
> http://n2.nabble.com/Activation-of-multiple-profiles-at-the-same-time-td2496510.html#none
> Currently, we workaround this by adding an additional parent pom to separate 
> the active profiles into different pom files. 
> But I still think this is a big limitation for profiles of MAVEN.

-- 
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