maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Closed] (MECLIPSE-727) Add Support for Arbitrary Project Substitution
Date Sun, 06 Sep 2015 20:45:20 GMT


Michael Osipov closed MECLIPSE-727.
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Add Support for Arbitrary Project Substitution
> ----------------------------------------------
>                 Key: MECLIPSE-727
>                 URL:
>             Project: Maven Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.9
>         Environment: NA
>            Reporter: christopher
> 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:

This message was sent by Atlassian JIRA

View raw message