Home » Eclipse Projects » Plugin Development Environment (PDE) » RCP Export Problems -- "Unable to acquire application service"
| RCP Export Problems -- "Unable to acquire application service" [message #51363] |
Sat, 21 March 2009 14:37  |
Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------070809080608020406070802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
(Apologies for the cross post...please let me know if this was better
suited in one newsgroup over another)
I was seeing this problem in a separate application that I was trying to
export, but I also see it when creating a brand new headless RCP app
using the "Hello World" template.
First off, I created the new app and a launch config using only those
plugins deemed required by the system. When I attempt to run, I get the
trace listed as "Trace 1" below. After manually adding the
org.eclipse.update.configurator plugin, the launch runs successfully.
Next I created a product (HelloWorld.product) based off of the launch
config and tried to export it. Everything seems to export fine, but
when I run the eclipse.exe file, I get the "Trace 2" trace.
Would anyone have an idea as to whether or not there is something that
I'm doing wrong? I've got the sample app that I can send if need be.
Thanks in advance,
Jesse
*Trace 1:*
!SESSION 2009-03-21 12:14:23.437
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product HelloWorld.product
Command-line arguments: -product HelloWorld.product -data
C:\dev\ChiroPOS2/../runtime-HelloWorld.product -dev
file:C:/dev/ChiroPOS2/.metadata/.plugins/org.eclipse.pde.cor e/HelloWorld.product/dev.properties
-os win32 -ws win32 -arch x86
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:14:24.109
!MESSAGE An unexpected runtime error has occurred.
!STACK 0
java.lang.IllegalArgumentException: The System Bundle's start level can
not be modified.
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.s etBundleStartLevel(StartLevelManager.java:415)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundl es(EclipseStarter.java:1122)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBun dles(EclipseStarter.java:646)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(Ecl ipseStarter.java:623)
at
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChan ged(EclipseStarter.java:308)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.d ispatchEvent(BundleContextImpl.java:1234)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:211)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv entSynchronous(ListenerQueue.java:141)
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEventPrivileged(Framework.java:1518)
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEvent(Framework.java:1469)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:281)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.l aunch(StartLevelManager.java:247)
at
org.eclipse.osgi.framework.internal.core.SystemBundle.resume (SystemBundle.java:201)
at
org.eclipse.osgi.framework.internal.core.Framework.launch(Fr amework.java:644)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.ja va:51)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:313)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
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)
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:14:24.109
!MESSAGE
!STACK 0
java.lang.IllegalArgumentException: The System Bundle's start level can
not be modified.
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.s etBundleStartLevel(StartLevelManager.java:415)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundl es(EclipseStarter.java:1122)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBun dles(EclipseStarter.java:646)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(Ecl ipseStarter.java:623)
at
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChan ged(EclipseStarter.java:308)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.d ispatchEvent(BundleContextImpl.java:1234)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:211)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv entSynchronous(ListenerQueue.java:141)
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEventPrivileged(Framework.java:1518)
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEvent(Framework.java:1469)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:281)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.l aunch(StartLevelManager.java:247)
at
org.eclipse.osgi.framework.internal.core.SystemBundle.resume (SystemBundle.java:201)
at
org.eclipse.osgi.framework.internal.core.Framework.launch(Fr amework.java:644)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.ja va:51)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:313)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
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)
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:14:24.125
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Platform not running
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:374)
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)
*
Trace 2:
*!SESSION 2009-03-21 12:05:43.000
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_05
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 2009-03-21 12:05:43.781
!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:386)
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)
--------------070809080608020406070802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
(Apologies for the cross post...please let me know if this was better
suited in one newsgroup over another)<br>
<br>
I was seeing this problem in a separate application that I was trying
to export, but I also see it when creating a brand new headless RCP app
using the "Hello World" template.<br>
<br>
First off, I created the new app and a launch config using only those
plugins deemed required by the system. When I attempt to run, I get
the trace listed as "Trace 1" below. After manually adding the
org.eclipse.update.configurator plugin, the launch runs successfully.<br>
<br>
Next I created a product (HelloWorld.product) based off of the launch
config and tried to export it. Everything seems to export fine, but
when I run the eclipse.exe file, I get the "Trace 2" trace.<br>
<br>
Would anyone have an idea as to whether or not there is something that
I'm doing wrong? I've got the sample app that I can send if need be.<br>
<br>
Thanks in advance,<br>
Jesse<br>
<br>
<b>Trace 1:</b><br>
<br>
!SESSION 2009-03-21 12:14:23.437
-----------------------------------------------<br>
eclipse.buildId=unknown<br>
java.version=1.6.0_05<br>
java.vendor=Sun Microsystems Inc.<br>
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US<br>
Framework arguments: -product HelloWorld.product<br>
Command-line arguments: -product HelloWorld.product -data
C:\dev\ChiroPOS2/../runtime-HelloWorld.product -dev
<a class="moz-txt-link-freetext" href=" file:C:/dev/ChiroPOS2/.metadata/.plugins/org.eclipse.pde.cor e/HelloWorld.product/dev.properties "> file:C:/dev/ChiroPOS2/.metadata/.plugins/org.eclipse.pde.cor e/HelloWorld.product/dev.properties </a>
-os win32 -ws win32 -arch x86<br>
<br>
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:14:24.109<br>
!MESSAGE An unexpected runtime error has occurred.<br>
!STACK 0<br>
java.lang.IllegalArgumentException: The System Bundle's start level can
not be modified.<br>
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.s etBundleStartLevel(StartLevelManager.java:415) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundl es(EclipseStarter.java:1122) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBun dles(EclipseStarter.java:646) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(Ecl ipseStarter.java:623) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChan ged(EclipseStarter.java:308) <br>
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.d ispatchEvent(BundleContextImpl.java:1234) <br>
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:211) <br>
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv entSynchronous(ListenerQueue.java:141) <br>
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEventPrivileged(Framework.java:1518) <br>
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEvent(Framework.java:1469) <br>
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:281) <br>
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.l aunch(StartLevelManager.java:247) <br>
at
org.eclipse.osgi.framework.internal.core.SystemBundle.resume (SystemBundle.java:201) <br>
at
org.eclipse.osgi.framework.internal.core.Framework.launch(Fr amework.java:644) <br>
at
org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.ja va:51) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:313) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175) <br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)<br>
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)<br>
at java.lang.reflect.Method.invoke(Unknown Source)<br>
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) <br>
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)<br >
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)<br>
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)<br>
<br>
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:14:24.109<br>
!MESSAGE <br>
!STACK 0<br>
java.lang.IllegalArgumentException: The System Bundle's start level can
not be modified.<br>
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.s etBundleStartLevel(StartLevelManager.java:415) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundl es(EclipseStarter.java:1122) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBun dles(EclipseStarter.java:646) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(Ecl ipseStarter.java:623) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChan ged(EclipseStarter.java:308) <br>
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.d ispatchEvent(BundleContextImpl.java:1234) <br>
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:211) <br>
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv entSynchronous(ListenerQueue.java:141) <br>
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEventPrivileged(Framework.java:1518) <br>
at
org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEvent(Framework.java:1469) <br>
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:281) <br>
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.l aunch(StartLevelManager.java:247) <br>
at
org.eclipse.osgi.framework.internal.core.SystemBundle.resume (SystemBundle.java:201) <br>
at
org.eclipse.osgi.framework.internal.core.Framework.launch(Fr amework.java:644) <br>
at
org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.ja va:51) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:313) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175) <br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)<br>
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)<br>
at java.lang.reflect.Method.invoke(Unknown Source)<br>
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) <br>
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)<br >
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)<br>
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)<br>
<br>
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:14:24.125<br>
!MESSAGE Application error<br>
!STACK 1<br>
java.lang.IllegalStateException: Platform not running<br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:374) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179) <br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)<br>
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)<br>
at java.lang.reflect.Method.invoke(Unknown Source)<br>
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) <br>
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)<br >
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)<br>
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)<br>
<br>
<br>
<br>
<b><br>
Trace 2:<br>
<br>
</b>!SESSION 2009-03-21 12:05:43.000
-----------------------------------------------<br>
eclipse.buildId=unknown<br>
java.version=1.6.0_05<br>
java.vendor=Sun Microsystems Inc.<br>
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US<br>
Command-line arguments: -os win32 -ws win32 -arch x86<br>
<br>
!ENTRY org.eclipse.osgi 4 0 2009-03-21 12:05:43.781<br>
!MESSAGE Application error<br>
!STACK 1<br>
java.lang.IllegalStateException: Unable to acquire application service.
Ensure that the org.eclipse.core.runtime bundle is resolved and started
(see config.ini).<br>
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:74) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386) <br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179) <br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)<br>
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)<br>
at java.lang.reflect.Method.invoke(Unknown Source)<br>
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) <br>
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)<br >
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)<br>
<br>
</body>
</html>
--------------070809080608020406070802--
|
|
| | | | |
| Re: RCP Export Problems -- "Unable to acquire application service" [message #51502 is a reply to message #51475] |
Sun, 22 March 2009 07:26  |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------070503060200030905080303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
After a week of researching, I think I found my needle in the haystack.
:-)
After trying the same thing out with an SR1 build, I noticed that in my
config.ini file, the start level for SR1 was:
*org.eclipse.core.runtime@start*
where my 3.4.2 export was:
*org.eclipse.core.runtime@2:start*
After making the change in my 3.4.2 exported application to match that
of the SR1 one, things seemed to work fine.
I'm curious, though, if anyone else is seeing this problem in 3.4.2 or
if it's just me.
Thanks for reading,
Jesse
Jesse Riggins wrote:
> Chris Aniszczyk wrote:
>> Jesse Riggins wrote:
>>> (Apologies for the cross post...please let me know if this was
>>> better suited in one newsgroup over another)
>>>
>>> I was seeing this problem in a separate application that I was
>>> trying to export, but I also see it when creating a brand new
>>> headless RCP app using the "Hello World" template.
>>>
>>> First off, I created the new app and a launch config using only
>>> those plugins deemed required by the system. When I attempt to run,
>>> I get the trace listed as "Trace 1" below. After manually adding
>>> the org.eclipse.update.configurator plugin, the launch runs
>>> successfully.
>>>
>>> Next I created a product (HelloWorld.product) based off of the
>>> launch config and tried to export it. Everything seems to export
>>> fine, but when I run the eclipse.exe file, I get the "Trace 2" trace.
>>>
>>> Would anyone have an idea as to whether or not there is something
>>> that I'm doing wrong? I've got the sample app that I can send if
>>> need be.
>>
>> What version of Eclipse are you using? What version of Eclipse are
>> you targetting in your target platform?
> 3.4.2 for both.
> Thanks,
> Jesse
--------------070503060200030905080303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
After a week of researching, I think I found my needle in the
haystack. :-) <br>
<br>
After trying the same thing out with an SR1 build, I noticed that in my
config.ini file, the start level for SR1 was:<br>
<br>
<b>org.eclipse.core.runtime@start</b><br>
<br>
where my 3.4.2 export was:<br>
<br>
<b>org.eclipse.core.runtime@2:start</b><br>
<br>
After making the change in my 3.4.2 exported application to match that
of the SR1 one, things seemed to work fine.<br>
<br>
I'm curious, though, if anyone else is seeing this problem in 3.4.2 or
if it's just me.<br>
<br>
Thanks for reading,<br>
Jesse<br>
<br>
Jesse Riggins wrote:
<blockquote cite="mid:gq3vsu$80k$1@build.eclipse.org" type="cite">Chris
Aniszczyk wrote:
<br>
<blockquote type="cite">Jesse Riggins wrote:
<br>
<blockquote type="cite">(Apologies for the cross post...please let
me know if this was better suited in one newsgroup over another)
<br>
<br>
I was seeing this problem in a separate application that I was trying
to export, but I also see it when creating a brand new headless RCP app
using the "Hello World" template.
<br>
<br>
First off, I created the new app and a launch config using only those
plugins deemed required by the system. When I attempt to run, I get
the trace listed as "Trace 1" below. After manually adding the
org.eclipse.update.configurator plugin, the launch runs successfully.
<br>
<br>
Next I created a product (HelloWorld.product) based off of the launch
config and tried to export it. Everything seems to export fine, but
when I run the eclipse.exe file, I get the "Trace 2" trace.
<br>
<br>
Would anyone have an idea as to whether or not there is something that
I'm doing wrong? I've got the sample app that I can send if need be.
<br>
</blockquote>
<br>
What version of Eclipse are you using? What version of Eclipse are you
targetting in your target platform?
<br>
</blockquote>
3.4.2 for both. <br>
Thanks,
<br>
Jesse
<br>
</blockquote>
<br>
</body>
</html>
--------------070503060200030905080303--
|
|
| |
| Re: RCP Export Problems -- "Unable to acquire application service" [message #593700 is a reply to message #51363] |
Sat, 21 March 2009 16:26 |
| Eclipse User |
|
|
|
Jesse Riggins wrote:
> (Apologies for the cross post...please let me know if this was better
> suited in one newsgroup over another)
>
> I was seeing this problem in a separate application that I was trying to
> export, but I also see it when creating a brand new headless RCP app
> using the "Hello World" template.
>
> First off, I created the new app and a launch config using only those
> plugins deemed required by the system. When I attempt to run, I get the
> trace listed as "Trace 1" below. After manually adding the
> org.eclipse.update.configurator plugin, the launch runs successfully.
>
> Next I created a product (HelloWorld.product) based off of the launch
> config and tried to export it. Everything seems to export fine, but
> when I run the eclipse.exe file, I get the "Trace 2" trace.
>
> Would anyone have an idea as to whether or not there is something that
> I'm doing wrong? I've got the sample app that I can send if need be.
>
> Thanks in advance,
> Jesse
1. Whats your eclipse version?
2. Did you try using RCP cheatsheet instead?
Ankur..
|
|
|
| Re: RCP Export Problems -- "Unable to acquire application service" [message #593707 is a reply to message #51391] |
Sat, 21 March 2009 18:40 |
| Eclipse User |
|
|
|
Ankur Sharma wrote:
> Jesse Riggins wrote:
>> (Apologies for the cross post...please let me know if this was better
>> suited in one newsgroup over another)
>>
>> I was seeing this problem in a separate application that I was trying
>> to export, but I also see it when creating a brand new headless RCP
>> app using the "Hello World" template.
>>
>> First off, I created the new app and a launch config using only those
>> plugins deemed required by the system. When I attempt to run, I get
>> the trace listed as "Trace 1" below. After manually adding the
>> org.eclipse.update.configurator plugin, the launch runs successfully.
>>
>> Next I created a product (HelloWorld.product) based off of the launch
>> config and tried to export it. Everything seems to export fine, but
>> when I run the eclipse.exe file, I get the "Trace 2" trace.
>>
>> Would anyone have an idea as to whether or not there is something
>> that I'm doing wrong? I've got the sample app that I can send if
>> need be.
>>
>> Thanks in advance,
>> Jesse
>
>
> 1. Whats your eclipse version?
3.4.2
> 2. Did you try using RCP cheatsheet instead?
>
No. Are you talking in terms of using the org.eclipse.ui.cheatsheets
plugin somehow?
Thanks for your help,
Jesse
|
|
|
| Re: RCP Export Problems -- "Unable to acquire application service" [message #593720 is a reply to message #51363] |
Sat, 21 March 2009 20:06 |
| Eclipse User |
|
|
|
Jesse Riggins wrote:
> (Apologies for the cross post...please let me know if this was better
> suited in one newsgroup over another)
>
> I was seeing this problem in a separate application that I was trying to
> export, but I also see it when creating a brand new headless RCP app
> using the "Hello World" template.
>
> First off, I created the new app and a launch config using only those
> plugins deemed required by the system. When I attempt to run, I get the
> trace listed as "Trace 1" below. After manually adding the
> org.eclipse.update.configurator plugin, the launch runs successfully.
>
> Next I created a product (HelloWorld.product) based off of the launch
> config and tried to export it. Everything seems to export fine, but
> when I run the eclipse.exe file, I get the "Trace 2" trace.
>
> Would anyone have an idea as to whether or not there is something that
> I'm doing wrong? I've got the sample app that I can send if need be.
What version of Eclipse are you using? What version of Eclipse are you
targetting in your target platform?
Cheers,
~ Chris
|
|
|
| Re: RCP Export Problems -- "Unable to acquire application service" [message #593729 is a reply to message #51447] |
Sat, 21 March 2009 20:14 |
| Eclipse User |
|
|
|
Chris Aniszczyk wrote:
> Jesse Riggins wrote:
>> (Apologies for the cross post...please let me know if this was better
>> suited in one newsgroup over another)
>>
>> I was seeing this problem in a separate application that I was trying
>> to export, but I also see it when creating a brand new headless RCP
>> app using the "Hello World" template.
>>
>> First off, I created the new app and a launch config using only those
>> plugins deemed required by the system. When I attempt to run, I get
>> the trace listed as "Trace 1" below. After manually adding the
>> org.eclipse.update.configurator plugin, the launch runs successfully.
>>
>> Next I created a product (HelloWorld.product) based off of the launch
>> config and tried to export it. Everything seems to export fine, but
>> when I run the eclipse.exe file, I get the "Trace 2" trace.
>>
>> Would anyone have an idea as to whether or not there is something
>> that I'm doing wrong? I've got the sample app that I can send if
>> need be.
>
> What version of Eclipse are you using? What version of Eclipse are you
> targetting in your target platform?
3.4.2 for both.
Thanks,
Jesse
|
|
|
| Re: RCP Export Problems -- "Unable to acquire application service" [message #593736 is a reply to message #51475] |
Sun, 22 March 2009 07:26 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------070503060200030905080303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
After a week of researching, I think I found my needle in the haystack.
:-)
After trying the same thing out with an SR1 build, I noticed that in my
config.ini file, the start level for SR1 was:
*org.eclipse.core.runtime@start*
where my 3.4.2 export was:
*org.eclipse.core.runtime@2:start*
After making the change in my 3.4.2 exported application to match that
of the SR1 one, things seemed to work fine.
I'm curious, though, if anyone else is seeing this problem in 3.4.2 or
if it's just me.
Thanks for reading,
Jesse
Jesse Riggins wrote:
> Chris Aniszczyk wrote:
>> Jesse Riggins wrote:
>>> (Apologies for the cross post...please let me know if this was
>>> better suited in one newsgroup over another)
>>>
>>> I was seeing this problem in a separate application that I was
>>> trying to export, but I also see it when creating a brand new
>>> headless RCP app using the "Hello World" template.
>>>
>>> First off, I created the new app and a launch config using only
>>> those plugins deemed required by the system. When I attempt to run,
>>> I get the trace listed as "Trace 1" below. After manually adding
>>> the org.eclipse.update.configurator plugin, the launch runs
>>> successfully.
>>>
>>> Next I created a product (HelloWorld.product) based off of the
>>> launch config and tried to export it. Everything seems to export
>>> fine, but when I run the eclipse.exe file, I get the "Trace 2" trace.
>>>
>>> Would anyone have an idea as to whether or not there is something
>>> that I'm doing wrong? I've got the sample app that I can send if
>>> need be.
>>
>> What version of Eclipse are you using? What version of Eclipse are
>> you targetting in your target platform?
> 3.4.2 for both.
> Thanks,
> Jesse
--------------070503060200030905080303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
After a week of researching, I think I found my needle in the
haystack. :-) <br>
<br>
After trying the same thing out with an SR1 build, I noticed that in my
config.ini file, the start level for SR1 was:<br>
<br>
<b>org.eclipse.core.runtime@start</b><br>
<br>
where my 3.4.2 export was:<br>
<br>
<b>org.eclipse.core.runtime@2:start</b><br>
<br>
After making the change in my 3.4.2 exported application to match that
of the SR1 one, things seemed to work fine.<br>
<br>
I'm curious, though, if anyone else is seeing this problem in 3.4.2 or
if it's just me.<br>
<br>
Thanks for reading,<br>
Jesse<br>
<br>
Jesse Riggins wrote:
<blockquote cite="mid:gq3vsu$80k$1@build.eclipse.org" type="cite">Chris
Aniszczyk wrote:
<br>
<blockquote type="cite">Jesse Riggins wrote:
<br>
<blockquote type="cite">(Apologies for the cross post...please let
me know if this was better suited in one newsgroup over another)
<br>
<br>
I was seeing this problem in a separate application that I was trying
to export, but I also see it when creating a brand new headless RCP app
using the "Hello World" template.
<br>
<br>
First off, I created the new app and a launch config using only those
plugins deemed required by the system. When I attempt to run, I get
the trace listed as "Trace 1" below. After manually adding the
org.eclipse.update.configurator plugin, the launch runs successfully.
<br>
<br>
Next I created a product (HelloWorld.product) based off of the launch
config and tried to export it. Everything seems to export fine, but
when I run the eclipse.exe file, I get the "Trace 2" trace.
<br>
<br>
Would anyone have an idea as to whether or not there is something that
I'm doing wrong? I've got the sample app that I can send if need be.
<br>
</blockquote>
<br>
What version of Eclipse are you using? What version of Eclipse are you
targetting in your target platform?
<br>
</blockquote>
3.4.2 for both. <br>
Thanks,
<br>
Jesse
<br>
</blockquote>
<br>
</body>
</html>
--------------070503060200030905080303--
|
|
| |
Goto Forum:
Current Time: Fri Oct 31 10:07:48 EDT 2025
Powered by FUDForum. Page generated in 0.05572 seconds |
Home