Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Problems with custom config.ini
Problems with custom config.ini [message #533450] Thu, 13 May 2010 22:36 Go to next message
Ken is currently offline KenFriend
Messages: 36
Registered: July 2009
Member
I have a feature product and in the product configuration tab I set it to
"Use an existing config.ini" instead of "Generate a default config.ini
file". The file I'm using is the same as what you get when exporting, but
when I run the exported product, I get the exception below. I've noticed
that the configuration folder generated has less stuff; it's missing
org.eclipse.core.runtime, org.eclipse.equinox.app, and
org.eclipse.simpleconfigurator. Even if I add those manually, it still does
not work. Something seems to also be missing from my plugin, b/c it only
works if I copy that over as well.

Any one know what is going on here? Is there any way to just update the
config.ini without having the rest of the output different and therefore not
work?

!SESSION 2010-05-13
18:35:37.458 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2010-05-13 18:35:37.998
!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:368)
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: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

- Ken
Re: Problems with custom config.ini [message #533456 is a reply to message #533450] Fri, 14 May 2010 02:47 Go to previous message
Ken is currently offline KenFriend
Messages: 36
Registered: July 2009
Member
It seemd to only happen with feature based products. Following this solved
the problem:
http://dev.eclipse.org/newslists/news.eclipse.platform/msg76 259.html at
least within Eclipse product export.

- Ken

"Ken Prole" <kennyp@avi.com> wrote in message
news:hshusk$ebp$1@build.eclipse.org...
>I have a feature product and in the product configuration tab I set it to
>"Use an existing config.ini" instead of "Generate a default config.ini
>file". The file I'm using is the same as what you get when exporting, but
>when I run the exported product, I get the exception below. I've noticed
>that the configuration folder generated has less stuff; it's missing
>org.eclipse.core.runtime, org.eclipse.equinox.app, and
>org.eclipse.simpleconfigurator. Even if I add those manually, it still does
>not work. Something seems to also be missing from my plugin, b/c it only
>works if I copy that over as well.
>
> Any one know what is going on here? Is there any way to just update the
> config.ini without having the rest of the output different and therefore
> not work?
>
> !SESSION 2010-05-13
> 18:35:37.458 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_18
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Command-line arguments: -os win32 -ws win32 -arch x86
>
> !ENTRY org.eclipse.osgi 4 0 2010-05-13 18:35:37.998
> !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:368)
> 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: 559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>
> - Ken
>
Previous Topic:RCP examples
Next Topic:Inputs To Commands
Goto Forum:
  


Current Time: Fri Nov 28 09:06:16 GMT 2014

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

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