You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/03/15 02:57:43 UTC
[jira] Created: (MNG-201) repository: transitive dependency report
repository: transitive dependency report
----------------------------------------
Key: MNG-201
URL: http://jira.codehaus.org/browse/MNG-201
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:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (MNG-201) repository: transitive dependency report
Posted by "Rafal Krzewski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-201?page=comments#action_30942 ]
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: http://jira.codehaus.org/browse/MNG-201
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (MNG-201) repository: transitive dependency report
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-201?page=comments#action_30952 ]
Brett Porter commented on MNG-201:
----------------------------------
Rafal - thanks, that's a possible feature for later. I think for now this is fine to run on ibiblio itself so we've got the most upstream server in good condition.
I'd prefer for users running this, to start with, to use something like maven-proxy so they actually have a local copy of all the deps they use, but we can certainly extend it in the ways you've suggested.
> repository: transitive dependency report
> ----------------------------------------
>
> Key: MNG-201
> URL: http://jira.codehaus.org/browse/MNG-201
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira