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

Christian Schulte closed MNG-5959.
----------------------------------
       Resolution: Fixed
         Assignee: Christian Schulte
    Fix Version/s: 3.4.0

Starting with Maven 3.4, you can set those dependencies to {{optional}} in 
dependency management. That  is the same as excluding them globally when not 
explicitly declared as a direct dependency.

> Can maven provide a features that exclude dependency gloablly
> -------------------------------------------------------------
>
>                 Key: MNG-5959
>                 URL: https://issues.apache.org/jira/browse/MNG-5959
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: vongosling
>            Assignee: Christian Schulte
>             Fix For: 3.4.0
>
>
> if maven provide the feature,such as property like
> <exclude-property>
>    com.xxx.xxx:test.unit:4.0.9
>    com.xxx.xxx:test.spring:2.0.1
>    com.xxx.xxx:jakarta.log4j:1.2.6
> <exclude-propety>
> no matter these jar scome from(directly or transitivly).yeah.when some 
> architect optimizing or refactoring some very old project,this can help 
> greatly



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to