The following comment has been added to this issue:

     Author: Brett Porter
    Created: Sat, 17 Jan 2004 6:46 PM
       Body:
Thanks Mike - will take a closer look when I have a chance.
It might take longer than usual to get applied if it works, just because of the 
current need to get 1.0 stuff finished.
---------------------------------------------------------------------
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1084&page=comments#action_15954

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1084

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1084
    Summary: Composition of dependencies from many projects (a route round multiple 
inheritance)
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: 4 hours
 Time Spent: Unknown
  Remaining: 4 hours

    Project: maven
 Components: 
             core
   Fix Fors:
             1.1

   Assignee: 
   Reporter: Mike Melia

    Created: Wed, 17 Dec 2003 12:40 AM
    Updated: Sat, 17 Jan 2004 6:46 PM

Description:
I have an EAR project that has (mostly) the same dependencies as an EJB project. 
The EAR project includes the dependent jars in the EAR artifact. 
The EJB project requires the dependent jars for compilation and for them to be 
included in the manifest classpath.
I also have another project that builds a utility jar for use by both the EAR and EJB 
project.

All projects extend a base project with the usual info defined (developers names 
etc.). This single inheritance forces me to duplicate the common dependency 
declarations in each subproject.

Ideally I would like an include tag in the dependencies section.

I have coded a workaround which allows for a space separated list of project files in 
the <extend> tag. e.g <extend>../project.xml ../common_dependencies.xml</extend>
The first file would be the parent project and the subsequent files would contain 
common dependencies. i.e. inherit from the parent and have dependencies composed from 
siblings.

I will submit a patch for that functionality as soon as I get away from the corporate 
firewall.

Please let me know if this sort of functionality has already been planned. TIA.


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

Reply via email to