RE: [equinox-dev] Feature complete?

["Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>]

Ciao PaScaL :) 
I'm seeing an issue that showed up right after p2 took over (> M5):
On my linux box I like to install Eclipse as root and set the entire
installation to read-only.

Back on the old days this used to work, all configuration data got
stored in my ~/.eclipse directory, however, this is not working any more
(see below for ST).
For now I can work around this by setting my local installations
configuration directory to writable but that's clearly not an option for
multi-user installations...

Also, on my Windows box I saw this strange behaviour: 
My "links" directory contains multiple local extension locations. All
these seem to get picked up just fine (i.e. the UM shows them) however,
the actual functionality (e.g. Menus, Actions, Wizards) is not there
until I restart Eclipse once...

HTH,
Ciao, hh

P.S.: Stacktrace of issues with read-only installations:

!ENTRY org.eclipse.osgi 4 0 2008-05-05 11:04:21.267
!MESSAGE Error reading configuration:
<ro-eclipse>configuration/org.eclipse.osgi/.manager/.fileTableLock (No
such file or directory)
!STACK 0
java.io.FileNotFoundException:
<ro-eclipse>/configuration/org.eclipse.osgi/.manager/.fileTableLock (No
such file or directory)
        at java.io.RandomAccessFile.open(Native Method)
        at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
        at
org.eclipse.core.runtime.internal.adaptor.Locker_JavaNio.lock(Locker_Jav
aNio.java:32)
        at
org.eclipse.osgi.storagemanager.StorageManager.lock(StorageManager.java:
389)
        at
org.eclipse.osgi.storagemanager.StorageManager.open(StorageManager.java:
687)
        at
org.eclipse.osgi.internal.baseadaptor.BaseStorage.initFileManager(BaseSt
orage.java:208)
        at
org.eclipse.osgi.internal.baseadaptor.BaseStorage.initialize(BaseStorage
.java:142)
        at
org.eclipse.osgi.baseadaptor.BaseAdaptor.initializeStorage(BaseAdaptor.j
ava:124)
        at
org.eclipse.osgi.framework.internal.core.Framework.initialize(Framework.
java:180)
        at
org.eclipse.osgi.framework.internal.core.Framework.<init>(Framework.java
:152)
        at
org.eclipse.osgi.framework.internal.core.OSGi.createFramework(OSGi.java:
90)
        at
org.eclipse.osgi.framework.internal.core.OSGi.<init>(OSGi.java:31)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.j
ava:286)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
175)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: 02 May 2008 20:27
To: Equinox development mailing list;
cross-project-issues-dev-bounces@xxxxxxxxxxx; eclipse-dev@xxxxxxxxxxx
Subject: [equinox-dev] Feature complete?

Hello, 

With M7 out the door, eclipse 3.4 is now feature complete. For the first
release of p2, the feature completion metric was "Update Manager". This
means that p2 had to provide equivalent functionality to those of UM and
also be backward compatible with it.

With M7, we believe we are done. That said, since we are replacing a
system that has been around for years, we would like to know if you
agree with us. How? Simply use p2 in the same way you use to use UM and
let us know through bug reports of any problem / limitation you are
encountering.

Thanks in advance, and happy provisioning.

PaScaL