[jira] Updated: (MNG-702) Add ability to exclude all transitive dependencies except those specified as inclusions

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-702?page=all ]

Brett Porter updated MNG-702:
-----------------------------

    Remaining Estimate:     (was: 3 hours)
     Original Estimate:     (was: 10800)

I'm not certain about this any more, I'm inclined to WON'T FIX as its behaviour isn't consistent. Where excludes filters to any depth, that would make includes not very useful.

I think we need to focus on correcting the metadata which we are doing, and for poms where this is likely to be an ongoing problem (eg dom4j and its optional dependencies), we should create a profile within it that can be used, so the default is light on dependencies.

Still up for consideration, but cut from beta-1

> Add ability to exclude all transitive dependencies except those specified as inclusions
> ---------------------------------------------------------------------------------------
>
>          Key: MNG-702
>          URL: http://jira.codehaus.org/browse/MNG-702
>      Project: Maven 2
>         Type: Improvement
>     Versions: 2.0-alpha-3
>     Reporter: Ken Weiner
>     Assignee: Brett Porter
>     Priority: Critical
>      Fix For: 2.0-beta-1

>
>
> Currently there is an ability to specify an optional <exclusions> element as a child of <dependency> within a POM.   This has the effect of excluding one or more of a dependency's transitive dependencies.
> It is often the case that a dependency itself has many dependencies needed for compilation, but are not necessarily needed at runtime.
> This is a request to add an optional <inclusions> element as a child to <dependency> within a POM so that it is possible to express the instruction "Don't get any of the transitive dependencies except for X, Y, Z, etc."   For example:
> <dependency>
>     <groupId>springframework</groupId>
>     <artifactId>spring</artifactId>
>     <version>1.2.2</version>
>     <scope>compile</scope>
>     <inclusions>
>         <inclusion>
>             <groupId>hibernate</groupId>
>             <artifactId>hibernate</artifactId>
>         </inclusion>
>     </inclusions>
> </dependency>
> Brett Porter pointed out on the maven users mailing list that this approach could have some pitfalls, but that I should still submit the issue for discussion.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org