[MECLIPSE-660] Cross-project reference uses wrong project name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.2
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Environment: Windows, Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
• Assignee: Unassigned
• Reporter: James Shaw
• Created: 22/Jun/10 09:16
• Updated: 25/Nov/14 14:48
• Resolved: 25/Nov/14 14:48

Description

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.