maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-58) Links should not be created when current directory = target directory (eclipse.workspace=***)
Date Sat, 07 Oct 2006 00:48:26 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-58?page=comments#action_76856 ] 
            
Kenney Westerhof commented on MECLIPSE-58:
------------------------------------------

You should NEVER point the eclipse.workspace to the actual project locations!

I can see why you did it - flatten the project tree. But what's the use for that anyway?
Just create an empty workspace directory somewhere - you don't need anything in there.
Then just import the projects from the real location - they appear flat in eclipse. No need
to flatten them out. 
Only leaf projects (packaging!=pom) are imported anyway.

Tending towards 'won't fix'

> Links should not be created when current directory = target directory (eclipse.workspace=***)
> ---------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-58
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-58
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>            Reporter: Stephen Duncan Jr
>
> To avoid typing the location to my eclipse workspace, and to flatten multi-projects,
I have a property in my setting.xml that specifies eclipse.workspace property.  However, when
running eclipse:eclipse on a simple project that is already in the Eclipse workspace directory,
I get links to my folders created, and the classpath uses the links instead of the actual
directory.  This behaviour also occurs when I have a multi-project in the eclipse workspace
directory where the directory name matches the artifactId of the parent project, the pom.xml
file is linked over the top of the actual file.  
> The linking behavior of eclipse:eclipse when eclipse.workspace is set should only be
turned on when the target project directory (${eclipse.workspace}/${project.artifactId} does
not match the current directory.  In that case, the normal eclipse:eclipse behavior should
apply.

-- 
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