maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "fabrizio giustina (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MECLIPSE-40) Multi project dependencies should not require eclipse project names to be the artifactId
Date Wed, 05 Apr 2006 08:00:52 GMT
     [ http://jira.codehaus.org/browse/MECLIPSE-40?page=all ]

fabrizio giustina updated MECLIPSE-40:
--------------------------------------

    type: Improvement  (was: Bug)

> Multi project dependencies should not require eclipse project names to be the artifactId
> ----------------------------------------------------------------------------------------
>
>          Key: MECLIPSE-40
>          URL: http://jira.codehaus.org/browse/MECLIPSE-40
>      Project: Maven 2.x Eclipse Plugin
>         Type: Improvement

>     Versions: 2.0
>     Reporter: Dave Sann

>
>
> Multi project dependencies should not require eclipse project names to be the artifactId
> eg:
> eclipse workspace:
> > Project1 -> creates artifact-x
> > Protect2 -> creates artifact-y, depends on artifact-x
> > MultiBuild - to build a selected collection of checked out projects
> >> pom.xml includes,
> ...
> <modules>
>  <module>../Project1</module>
>  <module>../Project2</module>
> <modules>
> ...
> eclipse:eclipse will create a depencency to a project named artifact-x, where it should
create a dependency to Project1

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message