maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marek Bieganski (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects
Date Mon, 28 Aug 2006 08:35:58 GMT
    [ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_73452 ] 
            
Marek Bieganski commented on MNGECLIPSE-59:
-------------------------------------------

Step 0:
Turn on auto build 

Step 1: 
Import attached simple projects

Step 2: 
Deploy library project (jar and pom) into maven2 repository 

Setp 3: 
Clean workspace to ensure situation on picture 1

Step 4:
Close library project (picture 2). 
Repository jar should be used, but eclipse is still looking for project
"Project application is missing required Java project: 'library'"
Cleaning workspace has no effect.

Step 5: 
Close eclipse, and reopen it
Situation is still like on picture 2

Step 6: 
Clean workspace
This time it has effect, and jar from repository is used (picture 3).

Step 7:
Open library project 
Project is available, but jar is still used. (picture 4)
First clean has no effect.
Second clean has effect and we are back in step 3

Similar problems occurs on deleting and e.g importing library project.
When auto build is on, no workspace cleaning nor closing eclipse should be needed.


> Allow artifact resolution from workspace projects
> -------------------------------------------------
>
>                 Key: MNGECLIPSE-59
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-59
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: New Feature
>          Components: Dependency Resolver
>    Affects Versions: 0.0.4
>            Reporter: Leonardo Quijano Vincenzi
>         Attachments: ArtifactResolver-try3.patch, MNGECLIPSE-59, mngeclipse-59-drew-hack.txt,
project-artifacts-2006062701.patch, project-artifacts-2006062900.patch, project-artifacts.patch
>
>
> Provide artifact resolution from workspace projects, which override the same artifact
from the local or remote repositories. This would allow to work with dependant Eclipse projects
without specifying the Eclipse dependency manually.
> The workspace artifact resolution would have to be specified manually, since several
Maven-Enabled projects in the same workspace could have the same artifact and version Id.
Or at least automatic resolution with an optional override would be nice.
> More comments here:
> http://jira.codehaus.org/browse/MNGECLIPSE-58

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message