maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafal Krzewski (JIRA)" <>
Subject [jira] Commented: (MNG-201) repository: transitive dependency report
Date Tue, 15 Mar 2005 12:00:37 GMT
     [ ]
Rafal Krzewski commented on MNG-201:

Note: that such check must span multiple repositories: An organization may publish their artifacts
to a their private repository, but the artifacts could have dependencies both in the private
and public repositories.
If the scan were performed on a single repository only, dependencies from public repository
would have to be replicated in private repository to pass the check, which would a waste of
bandwidth and resources.

> repository: transitive dependency report
> ----------------------------------------
>          Key: MNG-201
>          URL:
>      Project: m2
>         Type: Improvement
>   Components: repository-tools
>     Reporter: Brett Porter

> repository tool to ensure that transitive dependencies will work. 
> we basically need to know that every artifact that
> is referenced in one POM is actually in the repository along with its
> POM. We need to know that the dependency relationships among
> all artifacts in the repository form a closed set. otherwise the
> transitive dependency mechanism in m2 will break and we need to be wary
> of this. eventually i would like to create graphical representations of
> the dependencies amongst projects but this can come later. 

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