You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2010/08/26 18:55:32 UTC

[jira] Closed: (MENFORCER-85) Ability to exclude modules of multi-module project from requireReleaseDeps rule

     [ http://jira.codehaus.org/browse/MENFORCER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MENFORCER-85.
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0-beta-2
         Assignee: Paul Gier

Fixed in [r989820|http://svn.apache.org/viewvc?view=revision&revision=989820]

> Ability to exclude modules of multi-module project from requireReleaseDeps rule
> -------------------------------------------------------------------------------
>
>                 Key: MENFORCER-85
>                 URL: http://jira.codehaus.org/browse/MENFORCER-85
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>    Affects Versions: 1.0-beta-1
>            Reporter: Pete Muir
>            Assignee: Paul Gier
>             Fix For: 1.0-beta-2
>
>
> I would like to use this rule, however I only want it to apply to dependencies from outside my multi-module project. One way to achieve this would be to allow exclusions to requireReleaseDeps, though I think the use case of multi-module projects is common enough that having this as a special case is warranted.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira