[
https://issues.apache.org/jira/browse/MENFORCER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822962#comment-15822962
]
Mikko Johannes Koivunalho edited comment on MENFORCER-225 at 1/14/17 9:42 PM:
------------------------------------------------------------------------------
I have created a new issue for the rule Ban Profiles:
https://issues.apache.org/jira/browse/MENFORCER-261
With a new patch based on the current repo HEAD.
was (Author: mikko.koivunalho):
I have created a new issue for the rule Ban Profiles:
https://issues.apache.org/jira/browse/MENFORCER-261
> 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: waiting-for-feedback
>
> 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)
