[MECLIPSE-727] Add Support for Arbitrary Project Substitution

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.9
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Environment: NA
• Assignee: Unassigned
• Reporter: christopher
• Created: 26/Jun/12 09:36
• Updated: 06/Sep/15 20:44
• Resolved: 06/Sep/15 20:44

Description

The Eclipse plugin currently has a "workspace" configuration option.
This option directs the plugin to figure out
repo-artifact-to-Eclipse-project dependency substitutions by analyzing
the existing projects in the specified Eclipse workspace.

Rather than have the Eclipse plugin figure out these substitutions, I
want to directly configure the substitutions with a map of

{dependency (GAV) -> project}

. When the Eclipse plugin handles a dependency, it
can first check the map. If the map contains an entry for the
dependency, then the specified project is used; otherwise, the
repo-artifact is used.

The old Maven 1 plugin had something like this, in the form of a "project" flag:

http://maven.apache.org/maven-1.x/plugins/eclipse/faq.html#project_dependencies