Community
Participate
Working Groups
3.2RC4 Background: For some reason our hpux box is unable to create a .lock file for new workspaces on NFS servers, so we work around this by specifying system property -Dosgi.locking=none at startup time. This is a known workaround that has been used for ~ 2 years, and is not isolated to our hpux box (it has been reported on installations of other *ix flavours as well, though no one seems sure of the underlying cause). During testing I accidentally tried to self-host on our hpux box without specifying the -Dosgi.locking=none property for the runtime workspace, and I got an error dialog with the very helpful message "...you probably need to define -Dosgi.locking=none...". Unfortunately someone who gets this far probably already knows this because they had to use this to get their original workspace running in the first place. It would be very helpful if a similar error message could be shown when first starting eclipse as well, not just when self-hosting.
Isn't this one a dup of bug 59780?
Thanks for pointing this out, marking report as a duplicate. *** This bug has been marked as a duplicate of bug 59780 ***