Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Launching exported product in 3.4RC3
Launching exported product in 3.4RC3 [message #329361] Sat, 21 June 2008 01:10 Go to next message
Eclipse UserFriend
Originally posted by: automatic.javalobby.org

Hi,

I've updated to 3.4 rc3 & am now getting an error when trying to run the exported product:

<code>
!SESSION 2008-06-21 12:45:19.539 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_15
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_NZ
Command-line arguments: -os win32 -ws win32 -arch x86 -consoleLog -console

!ENTRY org.eclipse.osgi 4 0 2008-06-21 12:45:20.651
!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:382)
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)

</code>

The config.ini is automatically generated to:
<code>
#Product Runtime Configuration File

osgi.splashPath=platform:/base/plugins/nz.co.company.energyr econciliation.ui
eclipse.product=nz.co.company.energyreconciliation.ui.produc t
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
osgi.bundles.defaultStartLevel=4
</code>

This worked fine under Eclipse 3.3.2 but now with 3.4rc2, it's not. Any ideas?

Cheers
Re: Launching exported product in 3.4RC3 [message #329867 is a reply to message #329361] Tue, 08 July 2008 19:05 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mircea.luchian.matrox.com

Hello Glenn,

I came across your post from June and I still have the same problem with
Eclipse 3.4 (final build). Did you find a solution to your problem?

Thanks,

Mircea

Glenn Gilbert wrote:
> Hi,
>
> I've updated to 3.4 rc3 & am now getting an error when trying to run the exported product:
>
> <code>
> !SESSION 2008-06-21 12:45:19.539 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.5.0_15
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_NZ
> Command-line arguments: -os win32 -ws win32 -arch x86 -consoleLog -console
>
> !ENTRY org.eclipse.osgi 4 0 2008-06-21 12:45:20.651
> !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:382)
> 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)
>
> </code>
>
> The config.ini is automatically generated to:
> <code>
> #Product Runtime Configuration File
>
> osgi.splashPath=platform:/base/plugins/nz.co.company.energyr econciliation.ui
> eclipse.product=nz.co.company.energyreconciliation.ui.produc t
> osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
> osgi.bundles.defaultStartLevel=4
> </code>
>
> This worked fine under Eclipse 3.3.2 but now with 3.4rc2, it's not. Any ideas?
>
> Cheers
>
Re: Launching exported product in 3.4RC3 [message #329875 is a reply to message #329361] Wed, 09 July 2008 03:00 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: automatic.javalobby.org

Hi Mircea,
I've got a lot on, so I reverted the target platform to 3.3 until I get time to sort it. Keep an eye out. I'll post when I get it sorted.
Re: Launching exported product in 3.4RC3 [message #329888 is a reply to message #329875] Wed, 09 July 2008 14:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mircea.luchian.matrox.com

Hi Glenn,

I found a workaround. I wrote a bugzilla :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=240084
It's a bug on the Eclipse side and the workaround is explained there.
Just copy the missing parameters from your osgi_bundles line generated
in 3.3 to your 3.4 config.ini and it should work.

Mircea


Glenn Gilbert wrote:
> Hi Mircea,
> I've got a lot on, so I reverted the target platform to 3.3 until I get time to sort it. Keep an eye out. I'll post when I get it sorted.
>
Re: Launching exported product in 3.4RC3 [message #329897 is a reply to message #329888] Wed, 09 July 2008 21:14 Go to previous message
Eclipse UserFriend
Originally posted by: automatic.javalobby.org

Hi Mircea,

Thanks for the heads up.
Previous Topic:Eclipse FAQs + eScript
Next Topic:Eclipse update manager - hooks for custom tasks?
Goto Forum:
  


Current Time: Wed Jul 17 17:33:13 GMT 2024

Powered by FUDForum. Page generated in 0.03719 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top