Christopher Redekop created MECLIPSE-727: --------------------------------------------
Summary: Add Support for Arbitrary Project Substitution Key: MECLIPSE-727 URL: https://jira.codehaus.org/browse/MECLIPSE-727 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.9 Environment: NA Reporter: Christopher Redekop 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira