Community
Participate
Working Groups
When my eclipse install is on a UNC drive, the creation of a workspace on a UNC drive fails saying that the location can't be locked or is in use.
Interestsing. I believe that Ben was running completely on a UNC drive (eclipse and workspace there). There were issues but not this one. This was using Parallels on a Mac.
Created attachment 103624 [details] patch The fix to bug 95832 introduced this issue way back in 3.2.
(In reply to comment #1) > Interestsing. I believe that Ben was running completely on a UNC drive > (eclipse and workspace there). There were issues but not this one. This was > using Parallels on a Mac. > I suspect you may have some unexpected paths that get created for locking the workspace. What ends up happening is we try to lock an incorrect file location. for example if your workspace instance URL looks like this //machine/data/ws Then we end up creating a new file with the path /data/ws. Depending on how you launched eclipse this path will give you inconsistent results. For example if your user.dir = c:\eclipse then the workspace lock will be placed under c:\data\ws. But if you launched eclipse from a UNC path then the user.dir will be something else and I'm not sure what you will get from a file with a path /data/ws, but I know it will be a path you do not want.
consider for 3.4.1
Accidentally marked this as FIXED.
Created attachment 103668 [details] patch There are a few other places broken. For example, when we compute the configuration area based off the install area.
*** Bug 236695 has been marked as a duplicate of this bug. ***
I released the patch to HEAD (3.5) under bug 239356. Leaving this bug open to consider a fix in 3.4.1.
I released the patch to 3.4 maintenance branch.