You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Dave Sann (JIRA)" <ji...@codehaus.org> on 2005/12/12 23:46:46 UTC
[jira] Created: (MNG-1816) Multi project dependencies should not
require eclipse project names to be the artifactId
Multi project dependencies should not require eclipse project names to be the artifactId
----------------------------------------------------------------------------------------
Key: MNG-1816
URL: http://jira.codehaus.org/browse/MNG-1816
Project: Maven 2
Type: Improvement
Components: maven-eclipse-plugin
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MECLIPSE-40) Multi project dependencies should not
require eclipse project names to be the artifactId
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-40?page=all ]
fabrizio giustina updated MECLIPSE-40:
--------------------------------------
Version: 2.0
> 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: Bug
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org