[ http://jira.codehaus.org/browse/MECLIPSE-58?page=comments#action_76866 ] Stephen Duncan Jr commented on MECLIPSE-58: -------------------------------------------
Based on Eclipse 3.2's support for nested projects, I no longer have interest in the -Declipse.workspace= features. Won't fix is fine with me. > 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
