maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MENFORCER-225) Add rules for mutually-exclusive profiles and banned profiles
Date Sun, 09 Aug 2015 13:00:47 GMT

    [ https://issues.apache.org/jira/browse/MENFORCER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679133#comment-14679133
] 

Karl Heinz Marbaise commented on MENFORCER-225:
-----------------------------------------------

Could you please make separate issue for BannedProfiles and RequireMutuallyExclusiveActiveProfiles
cause this issue mixes two things which is not a good idea...

> Add rules for mutually-exclusive profiles and banned profiles
> -------------------------------------------------------------
>
>                 Key: MENFORCER-225
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-225
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: Rule API, Standard Rules
>    Affects Versions: 1.4
>            Reporter: Amardeep Sarkar
>             Fix For: 1.4.1
>
>         Attachments: enforcer-rules.patch, site.patch
>
>
> I wrote 2 new enforces rules:
> * The ability to specify a set of mutually-exclusive profiles (p1,p2:p1,p3 would mean
p1 can't be active with either p2 or p3). This has been discussed on [this thread|http://stackoverflow.com/questions/24855678/enforce-exactly-one-of-two-maven-profiles]
on SO.
> * The ability to ban profiles (the contrary of {{requireActiveProfile}}). p1, p2 would
mean neither p1 nor p2 can be active for this build.
> Both of these rules support wildcards and consider inherited profiles as well. I've attached
a patch complete with unit test cases. {{mvn clean install}} passes in local. These are built
on v1.4 of the rules.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message