3.4m6 and readonly directories. [message #107689] |
Tue, 08 April 2008 00:05 |
Eclipse User |
|
|
|
Originally posted by: r-c-l-e-v-e-n-g-remove-dashes.g-m-ai-l.com
I've been digging through the archive and wiki, but can't find anything
on this.
I grabbed the 3.4M6 SDK archive (eclipse-SDK-3.4M6-linux-gtk.tar.gz) and
unzipped it into /opt/eclipse (as I did with 3.3) as root where it's
read only for all users.
When I run eclipse as my user, I get an exception at startup, however if
I make /opt/eclipse writable it works.
Here's the command I use: /opt/eclipse/eclipse -configuration
/tmp/eclipse34config -data /tmp/eclipse34workspace
Here's the exception:
!SESSION 2008-04-07 16:44:14.933
-----------------------------------------------
eclipse.buildId=I20080330-1350
java.version=1.6.0_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -data /tmp/w4
!ENTRY org.eclipse.osgi 4 0 2008-04-07 16:44:15.441
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service.
Ensure that the org.eclipse.core.runtime bundle is resolved and started
(see config.ini).
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:74)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:362)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
Is this a bug, or just a limitation that will go away with the next
milestone.
Thanks,
Rob
|
|
|
Re: 3.4m6 and readonly directories. [message #107741 is a reply to message #107689] |
Tue, 08 April 2008 13:34 |
Simon Kaegi Messages: 381 Registered: July 2009 |
Senior Member |
|
|
Hi Rob,
You should log a bug to help ensure it's not in the next milestone ;)
-Simon
"Rob Clevenger" <r-c-l-e-v-e-n-g-remove-dashes@g-m-ai-l.com> wrote in
message news:ftecs9$5tj$1@build.eclipse.org...
> I've been digging through the archive and wiki, but can't find anything on
> this.
>
> I grabbed the 3.4M6 SDK archive (eclipse-SDK-3.4M6-linux-gtk.tar.gz) and
> unzipped it into /opt/eclipse (as I did with 3.3) as root where it's read
> only for all users.
>
> When I run eclipse as my user, I get an exception at startup, however if I
> make /opt/eclipse writable it works.
>
> Here's the command I use: /opt/eclipse/eclipse -configuration
> /tmp/eclipse34config -data /tmp/eclipse34workspace
>
> Here's the exception:
> !SESSION 2008-04-07
> 16:44:14.933 -----------------------------------------------
> eclipse.buildId=I20080330-1350
> java.version=1.6.0_01
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -os linux -ws gtk -arch x86 -data /tmp/w4
>
> !ENTRY org.eclipse.osgi 4 0 2008-04-07 16:44:15.441
> !MESSAGE Application error
> !STACK 1
> java.lang.IllegalStateException: Unable to acquire application service.
> Ensure that the org.eclipse.core.runtime bundle is resolved and started
> (see config.ini).
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:74)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:362)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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)
>
> Is this a bug, or just a limitation that will go away with the next
> milestone.
>
> Thanks,
>
> Rob
|
|
|
Powered by
FUDForum. Page generated in 0.03194 seconds