[MECLIPSE-32] Allow for forcing the creation of direct project references for dependencies

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0
• Component/s: Core : Multi-projects
• Assignee: Arnaud Heritier
• Reporter: Barry Kaplan
• Created: 17/Nov/05 19:31
• Updated: 06/Jan/16 20:05
• Resolved: 31/Jan/08 08:07

Description

For some thirdparty dependencies, it is common (for me at least) that an eclipse project for that dependency does/will exist in the workspace. It would be nice if dependencies in eclipse projects can be forced to use a direct project reference. eg:

<dependency>
<groupId>backport-util-concurrent</groupId>
<artifactId>backport-util-concurrent</artifactId>
<version>2.0_01_pd</version>
<scope>runtime</scope>
<properties>
<property name="eclipse.dependencyType" value="XXXX"/>
</properties>
</dependency>

Where XXXX can be:

• 'project' – always create a project reference
• 'jar' – always create a jar reference as in MNG-955
• 'auto' – the behavior prior to MNG-955

Issue Links

• is duplicated by: MECLIPSE-260 Ignore artifact version mismatches on creating references to sub-projects
• is duplicated by: MECLIPSE-120 Force inter-project dependencies
• is related to: MECLIPSE-74 Workspace inspection when adding a project
• is related to: MECLIPSE-344 connecting existing workspace artifact-projects