I used to checkout my projects outside of my eclispe workspace, so that I can reinstall eclipse and reconfigure a workspace with no impact on my SVN working copy.
I then generate the eclispe configuration and use "import existing projects into workspace". Based on this, my project parent folder is not the eclipse workspace. Maybe a valuable option would be for the plugin to get the parent folder and look for a ".metadata" folder. If found, the project is located in the eclipse workspace and this can be used in replacement to manually setting the parameter. Nicolas. 2008/3/25, Barrie Treloar <[EMAIL PROTECTED]>: > > I'd like to have feedback about how/if you are using > -Declipse.workspace in eclipse:eclipse 2.5 > > There is a comment in > http://jira.codehaus.org/browse/MECLIPSE-344#action_126688 (after the > issue was closed) to request that this option not be needed. > > The reasoning should be if you have a project in your workspace just use > it. > > I shouldn't have to specify the workspace location as it should be > possible to walk up the parent directory structure until you find the > workspace root. > > Should this be the default behaviour? > Do other people have different use cases that would make this invalid? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
