Cross-project reference uses wrong project name
-----------------------------------------------
Key: MECLIPSE-660
URL: http://jira.codehaus.org/browse/MECLIPSE-660
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path (.classpath)
Affects Versions: 2.2
Environment: Windows, Apache Maven 2.2.1 (r801777; 2009-08-06
20:16:01+0100)
Reporter: James Shaw
I have easymock checked out as an eclipse project. The project name in eclipse
is 'easymock-2.5.6', not easymock. When I run mvn eclipse:eclipse in another
project that depends upon easymock 2.5.6, it sees the project is in the
workspace, but generates a .classpath file that references 'easymock', not
'easymock-2.5.6'. I would guess that it's looking at the mvn project name, and
not the eclipse project name.
--
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