You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/02/01 16:40:57 UTC
[jira] Commented: (MNG-3229) Active by default profile is ignored
when another is specified explicitly.
[ http://jira.codehaus.org/browse/MNG-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122054 ]
Wendy Smoak commented on MNG-3229:
----------------------------------
I always understood activeByDefault to mean "active _unless_ another profile is explicitly specified".
Testing with 2.0.8, I'm seeing *both* profiles active, which is what you asked for, but *not* how it has ever worked in the past.
Can someone confirm?
> Active by default profile is ignored when another is specified explicitly.
> ---------------------------------------------------------------------------
>
> Key: MNG-3229
> URL: http://jira.codehaus.org/browse/MNG-3229
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.0.7
> Reporter: Oleksandr Maksymchuk
> Fix For: Documentation Deficit
>
>
> When default profile is added its used only when there is no another profile specified to be used on command line via -P option.
> So in the pom containig:
> <profile>
> <id>default</id>
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> <profile>
> <id>dev</id>
> <!-- Not active, should be called explicitly. -->
> default profile is used only when running command without -P dev
> mvn
> but not used when running:
> mvn -P dev
> Expected: should be used in both variants as per doc.
--
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