[
http://jira.codehaus.org/browse/MNG-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2234:
-------------------------------
Fix Version/s: (was: 2.0.x)
2.1-alpha-1
After chatting with John, we can turn this on because a proposal is forth
coming that will limit downstream profile activation to os, jdk, and
activeByDefault. Everything else should be ignored. So we can let users turn on
profiles in their settings but this begs the question, what is not being
triggered by default in the project you're working on?
> activeProfile in ~/.m2/settings.xml is ignored when profiles section is
> missing or empty
> ----------------------------------------------------------------------------------------
>
> Key: MNG-2234
> URL: http://jira.codehaus.org/browse/MNG-2234
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles, Settings
> Affects Versions: 2.0.4
> Reporter: Manfred Geiler
> Assignee: Jason van Zyl
> Fix For: 2.1-alpha-1
>
>
> When i have this settings.xml file in my user home dir, the activeProfile
> setting is simply ignored by Maven:
> <settings>
> <activeProfiles>
> <activeProfile>env-test</activeProfile>
> </activeProfiles>
> </settings>
> Adding an empty profiles section does not help:
> <settings>
> <profiles>
> </profiles>
> <activeProfiles>
> <activeProfile>env-test</activeProfile>
> </activeProfiles>
> </settings>
> Well, adding a dummy profile makes it work:
> <settings>
> <profiles>
> <profile>
> <id>dummy</id>
> </profile>
> </profiles>
> <activeProfiles>
> <activeProfile>env-test</activeProfile>
> </activeProfiles>
> </settings>
> Funny, isn't it?
> Regards,
> Manfred
--
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
