[jira] Commented: (MDEP-292) When selecting groupId fuzziness, exclude all artifacts based on groupId.

["Greg Vanore (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MDEP-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242127#action_242127 ] 

Greg Vanore commented on MDEP-292:
----------------------------------

I didn't mean to submit with Major priority - sorry about that.

> When selecting groupId fuzziness, exclude all artifacts based on groupId.
> -------------------------------------------------------------------------
>
>                 Key: MDEP-292
>                 URL: http://jira.codehaus.org/browse/MDEP-292
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>          Components: purge-local-repository
>    Affects Versions: 2.1
>            Reporter: Greg Vanore
>            Assignee: Brian Fox
>         Attachments: use-groupId-sensitivity-when-building-exclusions.diff
>
>
> This patch includes a simple change to the PurgeLocalRepositoryMojo class so that when the resolutionFuzziness is set to 'groupId,' the exclusions are treated by groupId.  This is because if I have two dependencies, such as 'org.slf4j:slf4j-api' and 'org.slf4j:slf4j-log4j' and I only list one of them in my exclusions and set the fuzziness to groupId, the entire group will still be deleted.  It seemed more natural to me that if the fuzziness is at the groupId level, that the exclusions should be based on which groupIds have been excluded.

-- 
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