maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Heritier (JIRA)" <>
Subject [jira] Closed: (MECLIPSE-74) Workspace inspection when adding a project
Date Thu, 31 Jan 2008 14:07:58 GMT


Arnaud Heritier closed MECLIPSE-74.

         Assignee: Arnaud Heritier
       Resolution: Duplicate
    Fix Version/s: 2.5

This issue is considered as fixed with MECLIPSE-344.
To try the latest SNAPSHOT (2.5-20080131.135640-18) of the incoming version you have to define
and activate this profile :
          <name>Maven Snapshots</name>
          <name>Maven Plugin Snapshots</name>
Then you have to call this command :
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
If you think that your problem isn't resolved, please give us your feedback and we'll reopen
the issue.

> Workspace inspection when adding a project
> ------------------------------------------
>                 Key: MECLIPSE-74
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: Workspace settings
>    Affects Versions: 2.1
>            Reporter: Gilles Scokart
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
> The eclipse plugin should lookup which project is present in a workspace and update/create
the project in function of what is already present.
> *Scénario 1* : Module A use module B.  Module B is already present as a project in the
workspace.  When adding A, the created project A should be dependent of the project B instead
of dependent of the jar in the repository.
> *Scénario 2* : idem, but A is first added, then B.  When B is added, the project A is
updated in order to be dependent of B instead of the jar in the repository.
> *Scénario 3* : Add a goal to remove a project (and update dependencies accordingly).
> Of curse all those scenario should take into account the version numbers present in the
poms inside the project.
> This is an alternative to MECLIPSE-32 .

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message