maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-2866) MavenProject objects of dependencies should be made available
Date Sat, 04 Dec 2010 23:50:08 GMT


Benjamin Bentmann closed MNG-2866.

       Resolution: Won't Fix
    Fix Version/s:     (was: Issues to be reviewed for 3.x)
         Assignee: Benjamin Bentmann

This concept of keeping stuff around just because some plugin might look at it someday doesn't
scale and hurts the memory footprint.

> MavenProject objects of dependencies should be made available
> -------------------------------------------------------------
>                 Key: MNG-2866
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Dependencies
>    Affects Versions: 2.0.4
>            Reporter: Kohsuke Kawaguchi
>            Assignee: Benjamin Bentmann
> Maven parses POM files of dependency jars recursively by using MavenMetadataSource.retrieve().
It needs to do so to find out the transitive dependencies.
> But currently, the parsed MavenProject object is immediately thrown away after dependency
list is fetched from it.
> POM files contain various useful information, so I'd like Maven to keep MavenProject
somewhere so that I can access it from my plugin. Possible use cases include:
> - find out all the licenses used in your dependency and generate a 3rd-party-license.txt
> - use information in POM to perform custom packaging

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message