Launching 3.4M7 as PDE runtime workbench from Eclipse 3.3.2 [message #328254] |
Tue, 20 May 2008 11:26 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: eclipse.shedid.de
Hi,
I'm trying to use the new 3.4M7 platform runtime as PDE target platform
for testing our Eclipse plugins. (via Preferences -> PDE -> Target Platform)
Unfortunately I cannot launch the runtime workbench from my current
development Eclipse (3.3.2).
I can launch the target from a different 3.4M7 installation, but
launching it from my 3.3.2 gives stack trace below.
Do you have any idea what's going wrong here?
!SESSION 2008-05-20 13:22:47.608
-----------------------------------------------
eclipse.buildId=I20080502-0100
java.version=1.5.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -application org.eclipse.ui.ide.workbench
Command-line arguments: -application org.eclipse.ui.ide.workbench -data
C:\Workspaces\xxxxxxxx -dev
file:C:/Workspaces/xxxxxxx/.metadata/.plugins/org.eclipse.pd e.core/xxx/dev.properties
-console -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.osgi 4 0 2008-05-20 13:22:48.296
!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:379)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)
|
|
|
Re: Launching 3.4M7 as PDE runtime workbench from Eclipse 3.3.2 [message #328262 is a reply to message #328254] |
Tue, 20 May 2008 13:17 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: zx.us.ibm.com
Are you sure your launch configuration is OK?
In your launch configuration, there should be an option to 'validate
plug-ins'
That error generally means that org.eclipse.core.runtime wasn't properly
started...
I just tried using 3.4M7, pointing to eclipse 3.3.2, creating an RCP
mail application and things look like they work OK.
Do you have access to the config.ini that is generated when you launch?
Cheers,
~ Chris
|
|
|
Re: Launching 3.4M7 as PDE runtime workbench from Eclipse 3.3.2 [message #328269 is a reply to message #328262] |
Tue, 20 May 2008 15:16 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: eclipse.shedid.de
Chris Aniszczyk schrieb:
> Are you sure your launch configuration is OK?
>
> In your launch configuration, there should be an option to 'validate
> plug-ins'
>
> That error generally means that org.eclipse.core.runtime wasn't properly
> started...
>
> I just tried using 3.4M7, pointing to eclipse 3.3.2, creating an RCP
> mail application and things look like they work OK.
>
> Do you have access to the config.ini that is generated when you launch?
>
> Cheers,
>
> ~ Chris
Hi Chris,
since I wanted Eclipse to create a new config.ini, I removed config.ini
from folder <my3.4Target>\eclipse\configuration. This finnaly did the
trick, now I can start the runtime workbench.
I do not actually understand what happened, but anyway it works now.
Thanks for the hint,
Dirk
|
|
|
Powered by
FUDForum. Page generated in 0.03306 seconds