[ 
https://issues.apache.org/jira/browse/MENFORCER-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elliotte Rusty Harold resolved MENFORCER-513.
---------------------------------------------
    Resolution: Won't Do

This doesn't seem to be common enough a need to justify inclusion in the plugin 
itself. However, as you've noted new enforcer rules do not have to ship with 
the plugin.
There are many that are not bundled with the core plugin such as the
extra-enforcer-rules <https://www.mojohaus.org/extra-enforcer-rules/>
and the Java Linkage checker rule
<https://medium.com/google-cloud/squash-java-linkage-bugs-before-they-bite-92af79e31bfd>

It is fine to publish this from your own repo without involving the
Maven Project.

> Add rule to define and check for mutually exclusive profiles
> ------------------------------------------------------------
>
>                 Key: MENFORCER-513
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-513
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>            Reporter: Andy Law
>            Priority: Minor
>              Labels: pull-request-available
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> I typically develop code that is run in different environments e.g., develop, 
> sandbox, production etc., where I define the parameters specific to each 
> environment in a separate profile. The code needs to be compiled and run for 
> the specific environments, making those profiles mutually exclusive. I have 
> seen this pattern and requirement detailed elsewhere, so I don't believe this 
> is specific to _my_ development patterns.
> It would be useful to have a rule to enforce the mutual exclusions, and 
> optionally to ensure that one of the set of profiles is selected.
> I have code written that performs this function as an additional rule within 
> the Enforcer plugin. I'm happy to donate that code to the project if it is of 
> interest to others. It's in a forked copy of the code so a pull request 
> should be trivial if required.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to