You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/10/06 18:52:38 UTC

[jira] Created: (MNG-4388) Allow inspection of dependency tree

Allow inspection of dependency tree
-----------------------------------

                 Key: MNG-4388
                 URL: http://jira.codehaus.org/browse/MNG-4388
             Project: Maven 2
          Issue Type: Task
          Components: Artifacts and Repositories
            Reporter: Benjamin Bentmann


We currently lack proper support in the core to easily inspect the dependency tree of a project. The existing artifact collector hands back a set of artifacts, allowing reconstruction of the dependency tree only via events.

For better dependency reporting and analysis and more flexibility with regard to future extensions, we should look into
- clear separation of conflict resolution, i.e. allow inspection of the dependency tree before and after conflicts have been resolved
- customizable scope handling, i..e. consider use cases where plugins might want to traverse dependencies deeper than usually done for classpaths or need to handle custom scopes like in Flex Mojos

-- 
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-4388) Allow inspection of dependency tree

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4388.
----------------------------------

    Resolution: Duplicate
      Assignee: Benjamin Bentmann

> Allow inspection of dependency tree
> -----------------------------------
>
>                 Key: MNG-4388
>                 URL: http://jira.codehaus.org/browse/MNG-4388
>             Project: Maven 2 & 3
>          Issue Type: Task
>          Components: Artifacts and Repositories
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>
> We currently lack proper support in the core to easily inspect the dependency tree of a project. The existing artifact collector hands back a set of artifacts, allowing reconstruction of the dependency tree only via events.
> For better dependency reporting and analysis and more flexibility with regard to future extensions, we should look into
> - clear separation of conflict resolution, i.e. allow inspection of the dependency tree before and after conflicts have been resolved
> - customizable scope handling, i..e. consider use cases where plugins might want to traverse dependencies deeper than usually done for classpaths or need to handle custom scopes like in Flex Mojos

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