The following comment has been added to this issue:
Author: Simone Zorzetti
Created: Sat, 16 Aug 2003 9:14 AM
Body:
It would be great if a Dependency could have itself dependencies realizing a
transitive dependency schema.
If associated to an artifact (Dependency) we can download a dependencies file witch
contains the dependencies of that artifact then, at runtime, we would be able to
recursively build the project dependency tree (excluding duplicates).
In this way a project could have primary dependencies (stated in the POM) and acquired
dependencies (derived from the primary ones).
Of course when deploying an artifact into the central repository we should be able to
produce and deploy the primary dependencies file associated to that artifact
The entire mechanism should be an optional feature
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-466
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-466
Summary: Post description of transitive dependency mechanism
Type: Task
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1
Assignee:
Reporter: Jason van Zyl
Created: Mon, 9 Jun 2003 11:11 AM
Updated: Mon, 4 Aug 2003 11:12 AM
Description:
Post a full description of the transitive dependency mechanism.
---------------------------------------------------------------------
JIRA INFORMATION:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
