[jira] [Assigned] (MENFORCER-389) Exclusions are not considered when looking at parent for requireReleaseDeps

["Slawomir Jaranowski (Jira)" <ji...@apache.org>]

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

Slawomir Jaranowski reassigned MENFORCER-389:
---------------------------------------------

    Assignee: Slawomir Jaranowski

> Exclusions are not considered when looking at parent for requireReleaseDeps
> ---------------------------------------------------------------------------
>
>                 Key: MENFORCER-389
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-389
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>    Affects Versions: 3.0.0
>            Reporter: Henri Tremblay
>            Assignee: Slawomir Jaranowski
>            Priority: Blocker
>
> I would like to prevent parent poms to be a snapshots. But I have a multi-module project. The rule is this on the parent pom:
> {code:java}
> <rules>
>   <requireReleaseDeps>
>     <message>No Snapshots Allowed!</message>
>     <excludes>
>       <exclude>${project.groupId}:*</exclude>
>     </excludes>
>     <failWhenParentIsSnapshot>true</failWhenParentIsSnapshot>
>   </requireReleaseDeps>
> </rules>
> {code}
> I would expect this to fail only when the parent pom is not in my groupId. But it's not what it does. It just makes {{failWhenParentIsSnapshot}} unusable for multi-module projects.
> See [https://github.com/henri-tremblay/enforce-parent-bug] for a full project to reproduce. Just type {{mvn enforcer:enforce}}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)