You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kohsuke Kawaguchi (JIRA)" <ji...@codehaus.org> on 2007/03/10 01:22:12 UTC
[jira] Created: (MNG-2866) MavenProject objects of dependencies
should be made available
MavenProject objects of dependencies should be made available
-------------------------------------------------------------
Key: MNG-2866
URL: http://jira.codehaus.org/browse/MNG-2866
Project: Maven 2
Issue Type: Improvement
Components: Dependencies
Affects Versions: 2.0.4
Reporter: Kohsuke Kawaguchi
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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2866) MavenProject objects of dependencies
should be made available
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2866:
------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
3.x
review with Mercury
> MavenProject objects of dependencies should be made available
> -------------------------------------------------------------
>
> Key: MNG-2866
> URL: http://jira.codehaus.org/browse/MNG-2866
> Project: Maven 2
> Issue Type: Improvement
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Kohsuke Kawaguchi
> Fix For: 3.x
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2866) MavenProject objects of dependencies
should be made available
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: http://jira.codehaus.org/browse/MNG-2866
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira