[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-4565: --- Description: According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: {code:xml} activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation{code} and another profile that is activated like this: {code:xml}activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation{code} Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. was: According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1, 3.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Jason van Zyl Fix For: 3.2.2 According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: {code:xml} activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation{code} and another profile that is activated like this: {code:xml}activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation{code} Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-4565. -- Resolution: Fixed Assignee: Jason van Zyl (was: brianfox brianfox) Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1, 3.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Jason van Zyl Fix For: 3.2.2 According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-4565: --- Fix Version/s: (was: Issues to be reviewed for 3.x) 3.2.2 Affects Version/s: 3.2.1 Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1, 3.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: brianfox brianfox Fix For: 3.2.2 According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=347896#comment-347896 ] Jason van Zyl commented on MNG-4565: Fixed on c6529932f9e3efdfc86ed73f59a307a8f8b6ea5f Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1, 3.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Jason van Zyl Fix For: 3.2.2 According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=347540#comment-347540 ] Konstantin Perikov commented on MNG-4565: - I've create pull request for this functionality - https://github.com/apache/maven/pull/16 Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: brianfox brianfox Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344985#comment-344985 ] SebbASF commented on MNG-4565: -- The Sonatype book still says that activation conditions are ANDed http://books.sonatype.com/mvnref-book/reference/profiles-sect-activation.html#profiles-sect-activation-config A profile is activated when all activation criteria has been satisfied. (sic) Still broken in Maven 3.0.5 Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Brian Fox Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317477#comment-317477 ] Ronny Pscheidl commented on MNG-4565: - This extension should solve the problem when all activation conditions are met: https://github.com/johnjcool/and-activation-profile-selector Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Brian Fox Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=313329#comment-313329 ] Ondrej Zizka commented on MNG-4565: --- Seems that Karel's extension solves MNG-5194. Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Brian Fox Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-4565: --- Comment: was deleted (was: From the looks of the details (assignee, fix version), doesn't look very promising. Maybe this issue needs some [sponsoring|http://www.freedomsponsors.org//core/issue/sponsor?trackerURL=http://jira.codehaus.org/browse/MNG-4565] :-) Have anyone tried Eric's github fork? ) Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox reassigned MNG-4565: -- Assignee: Brian Fox Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Assignee: Brian Fox Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=311779#comment-311779 ] Karel Piwko commented on MNG-4565: -- Guys, you can check following Maven extension https://github.com/kpiwko/el-profile-activator-extension. You just drop two jars into $MAVEN_HOME/lib/ext and you'll get MVEL support in property value. Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305714#comment-305714 ] Ivan commented on MNG-4565: --- What is the status of that fix ? Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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
[jira] (MNG-4565) Multiple profile activation conditions does not work
[ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305721#comment-305721 ] Tony Lampada commented on MNG-4565: --- From the looks of the details (assignee, fix version), doesn't look very promising. Maybe this issue needs some [sponsoring|http://www.freedomsponsors.org//core/issue/sponsor?trackerURL=http://jira.codehaus.org/browse/MNG-4565] :-) Have anyone tried Eric's github fork? Multiple profile activation conditions does not work Key: MNG-4565 URL: https://jira.codehaus.org/browse/MNG-4565 Project: Maven 2 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.1 Environment: All platforms. Reporter: Nicholas Allen Fix For: Issues to be reviewed for 3.x According to the documentation at http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html a profile is activated when all activation conditions are met (which makes sense of course). But when I try to use this it does not work. It seems maven does an OR instead of an AND (which is not rearly as useful and is the opposite of what the documentation says at the previous link). For example, if I have one profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os /activation and another profile that is activated like this: activation activeByDefaultfalse/activeByDefault os namelinux/name /os property namerelease/name valuetrue/value /property /activation Then I would expect the second profile to only be activated if the OS is linux and the release property is defined. When I run 'mvn help:active-profiles' however, maven shows that both profiles are active even though the release property is not defined. -- 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