|
|
|
|
| Re: Need an explanation of workspace locking [message #1710969 is a reply to message #1710947] |
Mon, 12 October 2015 05:33   |
 Ed Merks
Messages: 33217
Registered: July 2009 |
Senior Member |
|
|
Rob,
Comments below.
On 11/10/2015 7:03 PM, Rob Lewis wrote:
> I realize this is not specific to JDT but I couldn't find a more
> appropriate place to post it. Please advise.
Either eclipse.newcomer or eclipse.platform would seem more appropriate.
> And I don't understand why putting my workspace on Google Drive
> doesn't make sense. It's only me who will be accessing it, just from
> different machines.
As an example, on different machines there may be different JDKs/JREs
installed so any reference to a JRE location that's specific to a
machine will not be sharable.
> I was able to find some discussion of an option called "osgi.locking"
> in two contexts: 1. as a VM argument: -Dosgi.locking=none
> 2. in Eclipse's config.ini file: osgi.locking=none
Given that it's not clear what locking you're referring to with "But
there seems to be some kind of locking that prevents this." it's not
clear that this will help. I know Eclipse creates a
<workspace>/.metadata/.lock file to prevent more than one IDE from
opening the workspace at the same time. If that file can't be opened
for writing (presumable because it's opened and hence locked in another
process, but potentially because write access is not authorized), the
IDE will refuse to open that workspace. That might be the locking to
which you refer and there is no way to circumvent that, other than
ensuring it is possible to open that file for writing.
>
> but I can't find a full explanation of exactly what this does, whether
> it will accomplish my goal, and how using it in these different
> contexts might conflict or interact.
> Is this documented anywhere?
I would suggest a different approach. You can always open a new
workspace, and then you can use, File -> Import... -> General ->
Existing Projects into Workspace. From there you can locate a root
folder (this can be your "workspace" folder on the Google drive). Make
sure that the "Copy projects into workspace" is disabled. This will
link all those projects into the workspace. As such, the actual
projects will be maintained on the Google drive.
I.e., trying to share the workspace is probably doomed to failure, so
best focus on how best to share the projects. Though even the above
seems like a bad idea. Better to properly maintain the projects at
Github or Bitbucket. You could use something like Oomph to automate the
process of extracting those projects into a workspace.
https://wiki.eclipse.org/Eclipse_Oomph_Authoring
https://wiki.eclipse.org/Eclipse_Installer
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.05012 seconds
] 
Search
Help
Register
Login
Home
