maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Resolved: (MNG-78) create dependency classification system to minimize local repo bloat
Date Mon, 04 Apr 2005 21:37:56 GMT
     [ ]
John Casey resolved MNG-78:

    Resolution: Fixed

should be fixed, using dependency scoping and packaging combination.

this particular bug referred to scoping.

> create dependency classification system to minimize local repo bloat
> --------------------------------------------------------------------
>          Key: MNG-78
>          URL:
>      Project: m2
>         Type: Task
>  Environment: n/a
>     Reporter: John Casey

> Original Estimate: 8 hours
>         Remaining: 8 hours
> Currently, all dependencies are resolved and retrieved transitively before a project
is built. This means that any dependencies included in other projects' poms purely for testing
purposes (f.e. jmock, junit, httpunit, etc.) will also be downloaded, regardless of whether
the current project actually needs them for testing. The net result is a bloated local repository,
as all testing, etc. [non-runtime] dependencies of each dependency project is retrieved.
> One facet of the consequences of this can be seen in MNG-77.
> There has been some talk about how best to classify dependencies within maven, but as
far as I know, nothing concrete has come out of it. I would like to nail this particular functionality
down, and get it implemented, to reduce the overhead of manual POM construction, among other
> Often, it is completely inappropriate to include compile-time dependencies in a bundled
distro (f.e. EJBs cannot include j2ee.jar). This issue has seen some play on the maven-1 lists
lately, and I'd like to hit it out of the park with m2.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message