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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
