maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (MAVEN-1084) Composition of dependencies from many projects (a route round multiple inheritance)
Date Wed, 31 Dec 2003 02:39:08 GMT
The following issue has been updated:

    Updater: Brett Porter (
       Date: Tue, 30 Dec 2003 8:37 PM
             Fix Version changed to 1.1
For a full history of the issue, see:

View the issue:

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
   Fix Fors:

   Reporter: Mike Melia

    Created: Wed, 17 Dec 2003 12:40 AM
    Updated: Tue, 30 Dec 2003 8:37 PM

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.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message