[MECLIPSE-40] Multi project dependencies should not require eclipse project names to be the artifactId

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.4
• Component/s: Core : Multi-projects
• Assignee: Brian E Fox
• Reporter: Dave Sann
• Created: 12/Dec/05 16:46
• Updated: 10/Mar/16 13:50
• Resolved: 06/Jul/07 22:40

Description

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

Issue Links

• relates to: MECLIPSE-119 Allow custom project name for eclipse projects
• relates to: MECLIPSE-189 addVersionToProjectName property