[
http://jira.codehaus.org/browse/MDEP-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MDEP-76.
-------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha-4
> It would be nice to analyze dependencyManagement exclusions as well as
> versions
> -------------------------------------------------------------------------------
>
> Key: MDEP-76
> URL: http://jira.codehaus.org/browse/MDEP-76
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: analyze
> Affects Versions: 2.0-alpha-3
> Reporter: Daniel Kulp
> Assigned To: Brian Fox
> Fix For: 2.0-alpha-4
>
>
> In my depManagment section, I do:
> <dependency>
> <groupId>commons-logging</groupId>
> <artifactId>commons-logging</artifactId>
> <version>1.1</version>
> <exclusions>
> <exclusion>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> </exclusion>
> </exclusions>
> <dependency>
> to hopefully remove log4j from the build. However, if I depend on
> something else that depends on commons-logging (like spring or neethi), they
> suck in log4j. It would be nice if the analyzer would check if the
> exclusions are really occuring.
--
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
