Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
1.4
-
None
-
None
-
Patch
Description
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 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.