Home » Eclipse Projects » SWTBot » Testing exported RCP fails with StackOverflow
|
| Re: Testing exported RCP fails with StackOverflow [message #495388 is a reply to message #495375] |
Wed, 04 November 2009 17:00   |
Eclipse User |
|
|
|
Originally posted by: plenty.groover.gmail.com
Java/Eclipse newbie here, where exactly are you adding "feature id..."?
Can you provide the steps you've used to get to where you are so
far? I'm sure I could use the info to help with my own problems.
thx,
Plenty
Sakis Kotisis wrote:
> I am trying to set up a test version or our RCP, but keep failing thus far.
> Following Ketan's comments in a previous post i have added features
>
> <feature id="org.eclipse.swtbot" version="2.0.0.394-dev-e34"/>
> <feature id="org.eclipse.swtbot.eclipse" version="2.0.0.394-dev-e34"/>
>
> to my product.
> I have also added the plug-ins
>
> gr.osmosis.posterizer.update.tests.swtbot (my test plug-in)
> org.eclipse.swtbot.eclipse.junit4.headless
> org.eclipse.jdt.junit4.runtime
> org.junit4
> org.junit
>
> and all their dependencies to the feature which includes my product
> plug-in.
> Also setting the following launch arguments to the product:
>
> "-application
> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion
> formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJU nitResultFormatter,junit-results.xml
>
> -testPluginName
> gr.osmosis.posterizer.update.tests.swtbot
> -className
> UpdateTests"
>
> Unfortunately, the resulting launcher cannot even start the application
> and i am getting the following entry in the log :
>
> !ENTRY org.eclipse.osgi
> !MESSAGE Application error
> !STACK 1
> java.lang.StackOverflowError
> at java.lang.ThreadLocal.get(ThreadLocal.java:125)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:85)
>
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
>
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:370)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:446)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:399)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:387)
>
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:315)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1274)
>
> at
> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)
>
> at
> org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:867)
>
> at
> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
>
> at
> org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .getApplication(UITestApplication.java:85)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:45)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>
> at
> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>
> ....
>
> repeating.
>
> The same happens if i try to launch the test RCP from Ant.
>
> Has anybody encountered this error? Why is the application unable to
> start? Is it stuck in a loop?
>
> Thank you in advance for any insight,
> Sakis
>
|
|
|
| Re: Testing exported RCP fails with StackOverflow [message #495415 is a reply to message #495388] |
Wed, 04 November 2009 18:30 |
 Sakis Kotisis
Messages: 33
Registered: July 2009
Location: Belgium |
Member |
|
|
Plenty,
the following only applies if you are building a feature based product
(The product configuration is based on features).
In this case, the swtbot features (org.eclipse.swtbot,
org.eclipse.swtbot.eclipse) are added to the product configuration, along
with your own features.
Also, i added the following plug-ins to a feature included in my product
configuration :
<plugin id="org.eclipse.swtbot.eclipse.junit4.headless"
version="2.0.0.394-dev-e34"/>
<plugin id="org.eclipse.jdt.junit4.runtime"
version="1.0.200.v20080603-2000" unpack="false"/>
<plugin id="org.junit4" version="4.3.1"/>
<plugin id="org.eclipse.pde.core" version="3.4.0.v20090202"
unpack="false"/>
<plugin id="org.eclipse.pde.ui" version="3.4.0.v20090202" unpack="false"/>
<plugin id="org.eclipse.jdt.ui" version="3.4.2.r342_v20090107-0800"
unpack="false"/>
<plugin id="org.eclipse.jdt.core" version="3.4.4.v_894_R34x"
unpack="false"/>
<plugin id="org.eclipse.debug.ui" version="3.4.2.v20090110_r342"
unpack="false"/>
<plugin id="org.eclipse.jdt.launching" version="3.4.1.v20080729_r341"
unpack="false"/>
<plugin id="org.eclipse.debug.core" version="3.4.1.v20090106_r342"
unpack="false"/>
<plugin id="org.eclipse.jdt.junit" version="3.4.0.v20080603-2000"
unpack="false"/>
<plugin id="org.eclipse.team.core" version="3.4.2.r34x_20080115"
unpack="false"/>
<plugin id="org.eclipse.ant.core" version="3.2.0.v20080529"
unpack="false"/>
<plugin id="org.eclipse.core.filebuffers" version="3.4.0.v20080603-2000"
unpack="false"/>
<plugin id="org.eclipse.pde.build" version="3.4.1.R34x_v20081217"/>
<plugin id="org.eclipse.jdt.debug" version="3.4.1.v20081216_r342"/>
<plugin id="org.eclipse.jdt.core.manipulation"
version="1.2.0.v20080603-2000" unpack="false"/>
<plugin id="org.eclipse.ui.navigator" version="3.3.102.M20090127-1700"
unpack="false"/>
<plugin id="org.eclipse.compare" version="3.4.1.r34x_20090121"
unpack="false"/>
<plugin id="org.eclipse.ui.editors" version="3.4.0.v20080603-2000"
unpack="false"/>
<plugin id="org.eclipse.ltk.core.refactoring"
version="3.4.2.r342_v20081028-0800" unpack="false"/>
<plugin id="org.eclipse.team.ui" version="3.4.1.r34x_20080827"
unpack="false"/>
<plugin id="org.eclipse.ltk.ui.refactoring"
version="3.4.1.r341_v20080716-0800" unpack="false"/>
<plugin id="org.eclipse.search" version="3.4.1.r341_v20080813-0800"
unpack="false"/>
<plugin id="org.eclipse.jdt.debug.ui" version="3.3.1.v20080730_r341"
unpack="false"/>
<plugin id="org.eclipse.jdt.junit.runtime" version="3.3.0.v20080603-2000"
unpack="false"/>
<plugin id="org.eclipse.ui.cheatsheets" version="3.3.101.v20080702_34x"
unpack="false"/>
<plugin id="org.eclipse.ui.views.log" version="1.0.0.v20080803-1700"
unpack="false"/>
<plugin id="org.eclipse.ant.ui" version="3.3.1.v20090120_r342"
unpack="false"/>
<plugin id="org.eclipse.ui.navigator.resources"
version="3.3.101.M20080910-0800" unpack="false"/>
<plugin id="org.eclipse.ui.externaltools" version="3.2.0.v20080514-1542"
unpack="false"/>
<plugin id="org.apache.lucene" version="1.9.1.v20080530-1600"
unpack="false"/>
<plugin id="org.junit" version="3.8.2.v20080602-1318"/>
This list has been created through trial and error, you might have to
inlude several others as well.
I'd like to know myself if all these plug-ins are really required by
swtbot.
Finally, i found out why the UITestApplication went into a loop.
I was specifying
org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion as the
application to run in the product overview page.
UITestApplication is trying to read the launch arguments on startup.
If an application argument is specified, it tries to run the application
specified.
Hence, combined with the "-testapplication" launch argument i was
providing, the swtbottestapplication was constantly trying to call itself.
In short, don't specify swtbottestapplication as the application to run,
both in the product overview page and the launch arguments.
Unfortunately, it still doesn't run. Another error on my part perhaps.
That's all actually. Now, if it would actually run it would make me happy
:D
On Wed, 04 Nov 2009 19:00:22 +0200, Plenty Groover Jr.
<plenty.groover@gmail.com> wrote:
> Java/Eclipse newbie here, where exactly are you adding "feature id..."?
> Can you provide the steps you've used to get to where you are so
> far? I'm sure I could use the info to help with my own problems.
>
> thx,
> Plenty
>
> Sakis Kotisis wrote:
>
>> I am trying to set up a test version or our RCP, but keep failing thus
>> far.
>> Following Ketan's comments in a previous post i have added features
>> <feature id="org.eclipse.swtbot" version="2.0.0.394-dev-e34"/>
>> <feature id="org.eclipse.swtbot.eclipse" version="2.0.0.394-dev-e34"/>
>> to my product.
>> I have also added the plug-ins
>> gr.osmosis.posterizer.update.tests.swtbot (my test plug-in)
>> org.eclipse.swtbot.eclipse.junit4.headless
>> org.eclipse.jdt.junit4.runtime
>> org.junit4
>> org.junit
>> and all their dependencies to the feature which includes my product
>> plug-in.
>> Also setting the following launch arguments to the product:
>> "-application
>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion
>> formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJU nitResultFormatter,junit-results.xml
>> -testPluginName
>> gr.osmosis.posterizer.update.tests.swtbot
>> -className
>> UpdateTests"
>> Unfortunately, the resulting launcher cannot even start the
>> application and i am getting the following entry in the log :
>> !ENTRY org.eclipse.osgi
>> !MESSAGE Application error
>> !STACK 1
>> java.lang.StackOverflowError
>> at java.lang.ThreadLocal.get(ThreadLocal.java:125)
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:85)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:370)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:446)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:399)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:387)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:315)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1274)
>> at
>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)
>> at
>> org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:867)
>> at
>> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
>> at
>> org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .getApplication(UITestApplication.java:85)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:45)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>> at
>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>> ....
>> repeating.
>> The same happens if i try to launch the test RCP from Ant.
>> Has anybody encountered this error? Why is the application unable to
>> start? Is it stuck in a loop?
>> Thank you in advance for any insight,
>> Sakis
>>
--
Sakis Kotisis
SciGen Technologies, Inc.
|
|
|
| Re: Testing exported RCP fails with StackOverflow [message #495439 is a reply to message #495415] |
Wed, 04 November 2009 21:28 |
| Eclipse User |
|
|
|
Originally posted by: plenty.groover.gmail.com
Sakis,
Where exactly does this information go? Which file? I've been looking
through my directory structure and can't find anything similar, granted
I could have missed it.
With my application, I can start up a new instance of Eclipse and make
that do as I want, but not the actual one I'm to test.
Thanks for the info,
Plenty
Sakis Kotisis wrote:
> Plenty,
>
> the following only applies if you are building a feature based product
> (The product configuration is based on features).
> In this case, the swtbot features (org.eclipse.swtbot,
> org.eclipse.swtbot.eclipse) are added to the product configuration,
> along with your own features.
>
> Also, i added the following plug-ins to a feature included in my product
> configuration :
>
> <plugin id="org.eclipse.swtbot.eclipse.junit4.headless"
> version="2.0.0.394-dev-e34"/>
> <plugin id="org.eclipse.jdt.junit4.runtime"
> version="1.0.200.v20080603-2000" unpack="false"/>
> <plugin id="org.junit4" version="4.3.1"/>
> <plugin id="org.eclipse.pde.core" version="3.4.0.v20090202"
> unpack="false"/>
> <plugin id="org.eclipse.pde.ui" version="3.4.0.v20090202" unpack="false"/>
> <plugin id="org.eclipse.jdt.ui" version="3.4.2.r342_v20090107-0800"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.core" version="3.4.4.v_894_R34x"
> unpack="false"/>
> <plugin id="org.eclipse.debug.ui" version="3.4.2.v20090110_r342"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.launching" version="3.4.1.v20080729_r341"
> unpack="false"/>
> <plugin id="org.eclipse.debug.core" version="3.4.1.v20090106_r342"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.junit" version="3.4.0.v20080603-2000"
> unpack="false"/>
> <plugin id="org.eclipse.team.core" version="3.4.2.r34x_20080115"
> unpack="false"/>
> <plugin id="org.eclipse.ant.core" version="3.2.0.v20080529"
> unpack="false"/>
> <plugin id="org.eclipse.core.filebuffers" version="3.4.0.v20080603-2000"
> unpack="false"/>
> <plugin id="org.eclipse.pde.build" version="3.4.1.R34x_v20081217"/>
> <plugin id="org.eclipse.jdt.debug" version="3.4.1.v20081216_r342"/>
> <plugin id="org.eclipse.jdt.core.manipulation"
> version="1.2.0.v20080603-2000" unpack="false"/>
> <plugin id="org.eclipse.ui.navigator" version="3.3.102.M20090127-1700"
> unpack="false"/>
> <plugin id="org.eclipse.compare" version="3.4.1.r34x_20090121"
> unpack="false"/>
> <plugin id="org.eclipse.ui.editors" version="3.4.0.v20080603-2000"
> unpack="false"/>
> <plugin id="org.eclipse.ltk.core.refactoring"
> version="3.4.2.r342_v20081028-0800" unpack="false"/>
> <plugin id="org.eclipse.team.ui" version="3.4.1.r34x_20080827"
> unpack="false"/>
> <plugin id="org.eclipse.ltk.ui.refactoring"
> version="3.4.1.r341_v20080716-0800" unpack="false"/>
> <plugin id="org.eclipse.search" version="3.4.1.r341_v20080813-0800"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.debug.ui" version="3.3.1.v20080730_r341"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.junit.runtime"
> version="3.3.0.v20080603-2000" unpack="false"/>
> <plugin id="org.eclipse.ui.cheatsheets" version="3.3.101.v20080702_34x"
> unpack="false"/>
> <plugin id="org.eclipse.ui.views.log" version="1.0.0.v20080803-1700"
> unpack="false"/>
> <plugin id="org.eclipse.ant.ui" version="3.3.1.v20090120_r342"
> unpack="false"/>
> <plugin id="org.eclipse.ui.navigator.resources"
> version="3.3.101.M20080910-0800" unpack="false"/>
> <plugin id="org.eclipse.ui.externaltools" version="3.2.0.v20080514-1542"
> unpack="false"/>
> <plugin id="org.apache.lucene" version="1.9.1.v20080530-1600"
> unpack="false"/>
> <plugin id="org.junit" version="3.8.2.v20080602-1318"/>
>
> This list has been created through trial and error, you might have to
> inlude several others as well.
> I'd like to know myself if all these plug-ins are really required by
> swtbot.
>
> Finally, i found out why the UITestApplication went into a loop.
> I was specifying
> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion as the
> application to run in the product overview page.
> UITestApplication is trying to read the launch arguments on startup.
> If an application argument is specified, it tries to run the application
> specified.
> Hence, combined with the "-testapplication" launch argument i was
> providing, the swtbottestapplication was constantly trying to call itself.
>
> In short, don't specify swtbottestapplication as the application to run,
> both in the product overview page and the launch arguments.
>
> Unfortunately, it still doesn't run. Another error on my part perhaps.
>
> That's all actually. Now, if it would actually run it would make me
> happy :D
>
>
> On Wed, 04 Nov 2009 19:00:22 +0200, Plenty Groover Jr.
> <plenty.groover@gmail.com> wrote:
>
>> Java/Eclipse newbie here, where exactly are you adding "feature
>> id..."? Can you provide the steps you've used to get to where you
>> are so far? I'm sure I could use the info to help with my own problems.
>>
>> thx,
>> Plenty
>>
>> Sakis Kotisis wrote:
>>
>>> I am trying to set up a test version or our RCP, but keep failing
>>> thus far.
>>> Following Ketan's comments in a previous post i have added features
>>> <feature id="org.eclipse.swtbot" version="2.0.0.394-dev-e34"/>
>>> <feature id="org.eclipse.swtbot.eclipse" version="2.0.0.394-dev-e34"/>
>>> to my product.
>>> I have also added the plug-ins
>>> gr.osmosis.posterizer.update.tests.swtbot (my test plug-in)
>>> org.eclipse.swtbot.eclipse.junit4.headless
>>> org.eclipse.jdt.junit4.runtime
>>> org.junit4
>>> org.junit
>>> and all their dependencies to the feature which includes my product
>>> plug-in.
>>> Also setting the following launch arguments to the product:
>>> "-application
>>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion
>>> formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJU nitResultFormatter,junit-results.xml
>>> -testPluginName
>>> gr.osmosis.posterizer.update.tests.swtbot
>>> -className
>>> UpdateTests"
>>> Unfortunately, the resulting launcher cannot even start the
>>> application and i am getting the following entry in the log :
>>> !ENTRY org.eclipse.osgi
>>> !MESSAGE Application error
>>> !STACK 1
>>> java.lang.StackOverflowError
>>> at java.lang.ThreadLocal.get(ThreadLocal.java:125)
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:85)
>>> at
>>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:370)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:446)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:399)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:387)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:315)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1274)
>>> at
>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)
>>> at
>>> org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:867)
>>> at
>>> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
>>> at
>>> org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .getApplication(UITestApplication.java:85)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:45)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> ....
>>> repeating.
>>> The same happens if i try to launch the test RCP from Ant.
>>> Has anybody encountered this error? Why is the application unable to
>>> start? Is it stuck in a loop?
>>> Thank you in advance for any insight,
>>> Sakis
>>>
>
>
>
|
|
|
| Re: Testing exported RCP fails with StackOverflow [message #495519 is a reply to message #495439] |
Thu, 05 November 2009 08:12 |
Sakis Kotisis
Messages: 33
Registered: July 2009
Location: Belgium |
Member |
|
|
Plenty,
these entries are intended for the product configuration file.
If you don't have a product file, then this thread is probably not of
interest to you :)
Info on how you can build your own RCP can be found in:
http://wiki.eclipse.org/index.php/Rich_Client_Platform
How you can define you own product:
http://help.eclipse.org/help33/topic/org.eclipse.platform.do c.isv/guide/product_def.htm
You are best advised to direct further questions regarding rcp at the
eclipse.platform.rcp newsgroup.
On Wed, 04 Nov 2009 23:28:14 +0200, Plenty Groover Jr.
<plenty.groover@gmail.com> wrote:
> Sakis,
> Where exactly does this information go? Which file? I've been looking
> through my directory structure and can't find anything similar, granted
> I could have missed it.
>
> With my application, I can start up a new instance of Eclipse and make
> that do as I want, but not the actual one I'm to test.
>
> Thanks for the info,
> Plenty
>
> Sakis Kotisis wrote:
>> Plenty,
>> the following only applies if you are building a feature based product
>> (The product configuration is based on features).
>> In this case, the swtbot features (org.eclipse.swtbot,
>> org.eclipse.swtbot.eclipse) are added to the product configuration,
>> along with your own features.
>> Also, i added the following plug-ins to a feature included in my
>> product configuration :
>> <plugin id="org.eclipse.swtbot.eclipse.junit4.headless"
>> version="2.0.0.394-dev-e34"/>
>> <plugin id="org.eclipse.jdt.junit4.runtime"
>> version="1.0.200.v20080603-2000" unpack="false"/>
>> <plugin id="org.junit4" version="4.3.1"/>
>> <plugin id="org.eclipse.pde.core" version="3.4.0.v20090202"
>> unpack="false"/>
>> <plugin id="org.eclipse.pde.ui" version="3.4.0.v20090202"
>> unpack="false"/>
>> <plugin id="org.eclipse.jdt.ui" version="3.4.2.r342_v20090107-0800"
>> unpack="false"/>
>> <plugin id="org.eclipse.jdt.core" version="3.4.4.v_894_R34x"
>> unpack="false"/>
>> <plugin id="org.eclipse.debug.ui" version="3.4.2.v20090110_r342"
>> unpack="false"/>
>> <plugin id="org.eclipse.jdt.launching" version="3.4.1.v20080729_r341"
>> unpack="false"/>
>> <plugin id="org.eclipse.debug.core" version="3.4.1.v20090106_r342"
>> unpack="false"/>
>> <plugin id="org.eclipse.jdt.junit" version="3.4.0.v20080603-2000"
>> unpack="false"/>
>> <plugin id="org.eclipse.team.core" version="3.4.2.r34x_20080115"
>> unpack="false"/>
>> <plugin id="org.eclipse.ant.core" version="3.2.0.v20080529"
>> unpack="false"/>
>> <plugin id="org.eclipse.core.filebuffers"
>> version="3.4.0.v20080603-2000" unpack="false"/>
>> <plugin id="org.eclipse.pde.build" version="3.4.1.R34x_v20081217"/>
>> <plugin id="org.eclipse.jdt.debug" version="3.4.1.v20081216_r342"/>
>> <plugin id="org.eclipse.jdt.core.manipulation"
>> version="1.2.0.v20080603-2000" unpack="false"/>
>> <plugin id="org.eclipse.ui.navigator" version="3.3.102.M20090127-1700"
>> unpack="false"/>
>> <plugin id="org.eclipse.compare" version="3.4.1.r34x_20090121"
>> unpack="false"/>
>> <plugin id="org.eclipse.ui.editors" version="3.4.0.v20080603-2000"
>> unpack="false"/>
>> <plugin id="org.eclipse.ltk.core.refactoring"
>> version="3.4.2.r342_v20081028-0800" unpack="false"/>
>> <plugin id="org.eclipse.team.ui" version="3.4.1.r34x_20080827"
>> unpack="false"/>
>> <plugin id="org.eclipse.ltk.ui.refactoring"
>> version="3.4.1.r341_v20080716-0800" unpack="false"/>
>> <plugin id="org.eclipse.search" version="3.4.1.r341_v20080813-0800"
>> unpack="false"/>
>> <plugin id="org.eclipse.jdt.debug.ui" version="3.3.1.v20080730_r341"
>> unpack="false"/>
>> <plugin id="org.eclipse.jdt.junit.runtime"
>> version="3.3.0.v20080603-2000" unpack="false"/>
>> <plugin id="org.eclipse.ui.cheatsheets" version="3.3.101.v20080702_34x"
>> unpack="false"/>
>> <plugin id="org.eclipse.ui.views.log" version="1.0.0.v20080803-1700"
>> unpack="false"/>
>> <plugin id="org.eclipse.ant.ui" version="3.3.1.v20090120_r342"
>> unpack="false"/>
>> <plugin id="org.eclipse.ui.navigator.resources"
>> version="3.3.101.M20080910-0800" unpack="false"/>
>> <plugin id="org.eclipse.ui.externaltools"
>> version="3.2.0.v20080514-1542" unpack="false"/>
>> <plugin id="org.apache.lucene" version="1.9.1.v20080530-1600"
>> unpack="false"/>
>> <plugin id="org.junit" version="3.8.2.v20080602-1318"/>
>> This list has been created through trial and error, you might have to
>> inlude several others as well.
>> I'd like to know myself if all these plug-ins are really required by
>> swtbot.
>> Finally, i found out why the UITestApplication went into a loop.
>> I was specifying
>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion as the
>> application to run in the product overview page.
>> UITestApplication is trying to read the launch arguments on startup.
>> If an application argument is specified, it tries to run the
>> application specified.
>> Hence, combined with the "-testapplication" launch argument i was
>> providing, the swtbottestapplication was constantly trying to call
>> itself.
>> In short, don't specify swtbottestapplication as the application to
>> run, both in the product overview page and the launch arguments.
>> Unfortunately, it still doesn't run. Another error on my part perhaps.
>> That's all actually. Now, if it would actually run it would make me
>> happy :D
>> On Wed, 04 Nov 2009 19:00:22 +0200, Plenty Groover Jr.
>> <plenty.groover@gmail.com> wrote:
>>
>>> Java/Eclipse newbie here, where exactly are you adding "feature
>>> id..."? Can you provide the steps you've used to get to where you
>>> are so far? I'm sure I could use the info to help with my own
>>> problems.
>>>
>>> thx,
>>> Plenty
>>>
>>> Sakis Kotisis wrote:
>>>
>>>> I am trying to set up a test version or our RCP, but keep failing
>>>> thus far.
>>>> Following Ketan's comments in a previous post i have added features
>>>> <feature id="org.eclipse.swtbot" version="2.0.0.394-dev-e34"/>
>>>> <feature id="org.eclipse.swtbot.eclipse" version="2.0.0.394-dev-e34"/>
>>>> to my product.
>>>> I have also added the plug-ins
>>>> gr.osmosis.posterizer.update.tests.swtbot (my test plug-in)
>>>> org.eclipse.swtbot.eclipse.junit4.headless
>>>> org.eclipse.jdt.junit4.runtime
>>>> org.junit4
>>>> org.junit
>>>> and all their dependencies to the feature which includes my product
>>>> plug-in.
>>>> Also setting the following launch arguments to the product:
>>>> "-application
>>>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion
>>>> formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJU nitResultFormatter,junit-results.xml
>>>> -testPluginName
>>>> gr.osmosis.posterizer.update.tests.swtbot
>>>> -className
>>>> UpdateTests"
>>>> Unfortunately, the resulting launcher cannot even start the
>>>> application and i am getting the following entry in the log :
>>>> !ENTRY org.eclipse.osgi
>>>> !MESSAGE Application error
>>>> !STACK 1
>>>> java.lang.StackOverflowError
>>>> at java.lang.ThreadLocal.get(ThreadLocal.java:125)
>>>> at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:85)
>>>> at
>>>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
>>>> at
>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:370)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:446)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:399)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:387)
>>>> at
>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:315)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1274)
>>>> at
>>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)
>>>> at
>>>> org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:867)
>>>> at
>>>> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
>>>> at
>>>> org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .getApplication(UITestApplication.java:85)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:45)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>> at
>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>> ....
>>>> repeating.
>>>> The same happens if i try to launch the test RCP from Ant.
>>>> Has anybody encountered this error? Why is the application unable to
>>>> start? Is it stuck in a loop?
>>>> Thank you in advance for any insight,
>>>> Sakis
>>>>
>>
--
Sakis Kotisis
SciGen Technologies, Inc.
|
|
|
| Re: Testing exported RCP fails with StackOverflow [message #495609 is a reply to message #495415] |
Thu, 05 November 2009 13:40 |
Sakis Kotisis
Messages: 33
Registered: July 2009
Location: Belgium |
Member |
|
|
Finally found out why i needed all those dependencies.
Feature org.eclipse.swtbot.eclipse is actually not required, hence should
not be included in the product configuration.
This means only a handful of dependency plug-ins need to be included in
the build.
On Wed, 04 Nov 2009 20:30:17 +0200, Sakis Kotisis
<sakis.kotisis@scigentech.com> wrote:
> Plenty,
>
> the following only applies if you are building a feature based product
> (The product configuration is based on features).
> In this case, the swtbot features (org.eclipse.swtbot,
> org.eclipse.swtbot.eclipse) are added to the product configuration,
> along with your own features.
>
> Also, i added the following plug-ins to a feature included in my product
> configuration :
>
> <plugin id="org.eclipse.swtbot.eclipse.junit4.headless"
> version="2.0.0.394-dev-e34"/>
> <plugin id="org.eclipse.jdt.junit4.runtime"
> version="1.0.200.v20080603-2000" unpack="false"/>
> <plugin id="org.junit4" version="4.3.1"/>
> <plugin id="org.eclipse.pde.core" version="3.4.0.v20090202"
> unpack="false"/>
> <plugin id="org.eclipse.pde.ui" version="3.4.0.v20090202"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.ui" version="3.4.2.r342_v20090107-0800"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.core" version="3.4.4.v_894_R34x"
> unpack="false"/>
> <plugin id="org.eclipse.debug.ui" version="3.4.2.v20090110_r342"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.launching" version="3.4.1.v20080729_r341"
> unpack="false"/>
> <plugin id="org.eclipse.debug.core" version="3.4.1.v20090106_r342"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.junit" version="3.4.0.v20080603-2000"
> unpack="false"/>
> <plugin id="org.eclipse.team.core" version="3.4.2.r34x_20080115"
> unpack="false"/>
> <plugin id="org.eclipse.ant.core" version="3.2.0.v20080529"
> unpack="false"/>
> <plugin id="org.eclipse.core.filebuffers" version="3.4.0.v20080603-2000"
> unpack="false"/>
> <plugin id="org.eclipse.pde.build" version="3.4.1.R34x_v20081217"/>
> <plugin id="org.eclipse.jdt.debug" version="3.4.1.v20081216_r342"/>
> <plugin id="org.eclipse.jdt.core.manipulation"
> version="1.2.0.v20080603-2000" unpack="false"/>
> <plugin id="org.eclipse.ui.navigator" version="3.3.102.M20090127-1700"
> unpack="false"/>
> <plugin id="org.eclipse.compare" version="3.4.1.r34x_20090121"
> unpack="false"/>
> <plugin id="org.eclipse.ui.editors" version="3.4.0.v20080603-2000"
> unpack="false"/>
> <plugin id="org.eclipse.ltk.core.refactoring"
> version="3.4.2.r342_v20081028-0800" unpack="false"/>
> <plugin id="org.eclipse.team.ui" version="3.4.1.r34x_20080827"
> unpack="false"/>
> <plugin id="org.eclipse.ltk.ui.refactoring"
> version="3.4.1.r341_v20080716-0800" unpack="false"/>
> <plugin id="org.eclipse.search" version="3.4.1.r341_v20080813-0800"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.debug.ui" version="3.3.1.v20080730_r341"
> unpack="false"/>
> <plugin id="org.eclipse.jdt.junit.runtime"
> version="3.3.0.v20080603-2000" unpack="false"/>
> <plugin id="org.eclipse.ui.cheatsheets" version="3.3.101.v20080702_34x"
> unpack="false"/>
> <plugin id="org.eclipse.ui.views.log" version="1.0.0.v20080803-1700"
> unpack="false"/>
> <plugin id="org.eclipse.ant.ui" version="3.3.1.v20090120_r342"
> unpack="false"/>
> <plugin id="org.eclipse.ui.navigator.resources"
> version="3.3.101.M20080910-0800" unpack="false"/>
> <plugin id="org.eclipse.ui.externaltools" version="3.2.0.v20080514-1542"
> unpack="false"/>
> <plugin id="org.apache.lucene" version="1.9.1.v20080530-1600"
> unpack="false"/>
> <plugin id="org.junit" version="3.8.2.v20080602-1318"/>
>
> This list has been created through trial and error, you might have to
> inlude several others as well.
> I'd like to know myself if all these plug-ins are really required by
> swtbot.
>
> Finally, i found out why the UITestApplication went into a loop.
> I was specifying
> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion as the
> application to run in the product overview page.
> UITestApplication is trying to read the launch arguments on startup.
> If an application argument is specified, it tries to run the application
> specified.
> Hence, combined with the "-testapplication" launch argument i was
> providing, the swtbottestapplication was constantly trying to call
> itself.
>
> In short, don't specify swtbottestapplication as the application to run,
> both in the product overview page and the launch arguments.
>
> Unfortunately, it still doesn't run. Another error on my part perhaps.
>
> That's all actually. Now, if it would actually run it would make me
> happy :D
>
>
> On Wed, 04 Nov 2009 19:00:22 +0200, Plenty Groover Jr.
> <plenty.groover@gmail.com> wrote:
>
>> Java/Eclipse newbie here, where exactly are you adding "feature id..."?
>> Can you provide the steps you've used to get to where you are so
>> far? I'm sure I could use the info to help with my own problems.
>>
>> thx,
>> Plenty
>>
>> Sakis Kotisis wrote:
>>
>>> I am trying to set up a test version or our RCP, but keep failing thus
>>> far.
>>> Following Ketan's comments in a previous post i have added features
>>> <feature id="org.eclipse.swtbot" version="2.0.0.394-dev-e34"/>
>>> <feature id="org.eclipse.swtbot.eclipse" version="2.0.0.394-dev-e34"/>
>>> to my product.
>>> I have also added the plug-ins
>>> gr.osmosis.posterizer.update.tests.swtbot (my test plug-in)
>>> org.eclipse.swtbot.eclipse.junit4.headless
>>> org.eclipse.jdt.junit4.runtime
>>> org.junit4
>>> org.junit
>>> and all their dependencies to the feature which includes my product
>>> plug-in.
>>> Also setting the following launch arguments to the product:
>>> "-application
>>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion
>>> formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJU nitResultFormatter,junit-results.xml
>>> -testPluginName
>>> gr.osmosis.posterizer.update.tests.swtbot
>>> -className
>>> UpdateTests"
>>> Unfortunately, the resulting launcher cannot even start the
>>> application and i am getting the following entry in the log :
>>> !ENTRY org.eclipse.osgi
>>> !MESSAGE Application error
>>> !STACK 1
>>> java.lang.StackOverflowError
>>> at java.lang.ThreadLocal.get(ThreadLocal.java:125)
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:85)
>>> at
>>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:370)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:446)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:399)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:387)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:315)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1274)
>>> at
>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)
>>> at
>>> org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:867)
>>> at
>>> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
>>> at
>>> org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .getApplication(UITestApplication.java:85)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:45)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> at
>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>> ....
>>> repeating.
>>> The same happens if i try to launch the test RCP from Ant.
>>> Has anybody encountered this error? Why is the application unable to
>>> start? Is it stuck in a loop?
>>> Thank you in advance for any insight,
>>> Sakis
>>>
>
>
>
--
Sakis Kotisis
SciGen Technologies, Inc.
|
|
|
| Re: Testing exported RCP fails with StackOverflow [message #495622 is a reply to message #495519] |
Thu, 05 November 2009 14:23 |
| Eclipse User |
|
|
|
Originally posted by: plenty.groover.gmail.com
Thanks for the links, I'll jump on those pages shortly. I'm sure the
answer I'm looking for will be found there, or at least get me on the
right track to find it otherwise.
thx!
Plenty
Sakis Kotisis wrote:
> Plenty,
> these entries are intended for the product configuration file.
> If you don't have a product file, then this thread is probably not of
> interest to you :)
>
> Info on how you can build your own RCP can be found in:
> http://wiki.eclipse.org/index.php/Rich_Client_Platform
>
> How you can define you own product:
> http://help.eclipse.org/help33/topic/org.eclipse.platform.do c.isv/guide/product_def.htm
>
>
> You are best advised to direct further questions regarding rcp at the
> eclipse.platform.rcp newsgroup.
>
> On Wed, 04 Nov 2009 23:28:14 +0200, Plenty Groover Jr.
> <plenty.groover@gmail.com> wrote:
>
>> Sakis,
>> Where exactly does this information go? Which file? I've been
>> looking through my directory structure and can't find anything
>> similar, granted I could have missed it.
>>
>> With my application, I can start up a new instance of Eclipse and make
>> that do as I want, but not the actual one I'm to test.
>>
>> Thanks for the info,
>> Plenty
>>
>> Sakis Kotisis wrote:
>>> Plenty,
>>> the following only applies if you are building a feature based
>>> product (The product configuration is based on features).
>>> In this case, the swtbot features (org.eclipse.swtbot,
>>> org.eclipse.swtbot.eclipse) are added to the product configuration,
>>> along with your own features.
>>> Also, i added the following plug-ins to a feature included in my
>>> product configuration :
>>> <plugin id="org.eclipse.swtbot.eclipse.junit4.headless"
>>> version="2.0.0.394-dev-e34"/>
>>> <plugin id="org.eclipse.jdt.junit4.runtime"
>>> version="1.0.200.v20080603-2000" unpack="false"/>
>>> <plugin id="org.junit4" version="4.3.1"/>
>>> <plugin id="org.eclipse.pde.core" version="3.4.0.v20090202"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.pde.ui" version="3.4.0.v20090202"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.jdt.ui" version="3.4.2.r342_v20090107-0800"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.jdt.core" version="3.4.4.v_894_R34x"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.debug.ui" version="3.4.2.v20090110_r342"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.jdt.launching" version="3.4.1.v20080729_r341"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.debug.core" version="3.4.1.v20090106_r342"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.jdt.junit" version="3.4.0.v20080603-2000"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.team.core" version="3.4.2.r34x_20080115"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.ant.core" version="3.2.0.v20080529"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.core.filebuffers"
>>> version="3.4.0.v20080603-2000" unpack="false"/>
>>> <plugin id="org.eclipse.pde.build" version="3.4.1.R34x_v20081217"/>
>>> <plugin id="org.eclipse.jdt.debug" version="3.4.1.v20081216_r342"/>
>>> <plugin id="org.eclipse.jdt.core.manipulation"
>>> version="1.2.0.v20080603-2000" unpack="false"/>
>>> <plugin id="org.eclipse.ui.navigator"
>>> version="3.3.102.M20090127-1700" unpack="false"/>
>>> <plugin id="org.eclipse.compare" version="3.4.1.r34x_20090121"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.ui.editors" version="3.4.0.v20080603-2000"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.ltk.core.refactoring"
>>> version="3.4.2.r342_v20081028-0800" unpack="false"/>
>>> <plugin id="org.eclipse.team.ui" version="3.4.1.r34x_20080827"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.ltk.ui.refactoring"
>>> version="3.4.1.r341_v20080716-0800" unpack="false"/>
>>> <plugin id="org.eclipse.search" version="3.4.1.r341_v20080813-0800"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.jdt.debug.ui" version="3.3.1.v20080730_r341"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.jdt.junit.runtime"
>>> version="3.3.0.v20080603-2000" unpack="false"/>
>>> <plugin id="org.eclipse.ui.cheatsheets"
>>> version="3.3.101.v20080702_34x" unpack="false"/>
>>> <plugin id="org.eclipse.ui.views.log" version="1.0.0.v20080803-1700"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.ant.ui" version="3.3.1.v20090120_r342"
>>> unpack="false"/>
>>> <plugin id="org.eclipse.ui.navigator.resources"
>>> version="3.3.101.M20080910-0800" unpack="false"/>
>>> <plugin id="org.eclipse.ui.externaltools"
>>> version="3.2.0.v20080514-1542" unpack="false"/>
>>> <plugin id="org.apache.lucene" version="1.9.1.v20080530-1600"
>>> unpack="false"/>
>>> <plugin id="org.junit" version="3.8.2.v20080602-1318"/>
>>> This list has been created through trial and error, you might have
>>> to inlude several others as well.
>>> I'd like to know myself if all these plug-ins are really required by
>>> swtbot.
>>> Finally, i found out why the UITestApplication went into a loop.
>>> I was specifying
>>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion as
>>> the application to run in the product overview page.
>>> UITestApplication is trying to read the launch arguments on startup.
>>> If an application argument is specified, it tries to run the
>>> application specified.
>>> Hence, combined with the "-testapplication" launch argument i was
>>> providing, the swtbottestapplication was constantly trying to call
>>> itself.
>>> In short, don't specify swtbottestapplication as the application to
>>> run, both in the product overview page and the launch arguments.
>>> Unfortunately, it still doesn't run. Another error on my part perhaps.
>>> That's all actually. Now, if it would actually run it would make me
>>> happy :D
>>> On Wed, 04 Nov 2009 19:00:22 +0200, Plenty Groover Jr.
>>> <plenty.groover@gmail.com> wrote:
>>>
>>>> Java/Eclipse newbie here, where exactly are you adding "feature
>>>> id..."? Can you provide the steps you've used to get to where
>>>> you are so far? I'm sure I could use the info to help with my own
>>>> problems.
>>>>
>>>> thx,
>>>> Plenty
>>>>
>>>> Sakis Kotisis wrote:
>>>>
>>>>> I am trying to set up a test version or our RCP, but keep failing
>>>>> thus far.
>>>>> Following Ketan's comments in a previous post i have added features
>>>>> <feature id="org.eclipse.swtbot" version="2.0.0.394-dev-e34"/>
>>>>> <feature id="org.eclipse.swtbot.eclipse" version="2.0.0.394-dev-e34"/>
>>>>> to my product.
>>>>> I have also added the plug-ins
>>>>> gr.osmosis.posterizer.update.tests.swtbot (my test plug-in)
>>>>> org.eclipse.swtbot.eclipse.junit4.headless
>>>>> org.eclipse.jdt.junit4.runtime
>>>>> org.junit4
>>>>> org.junit
>>>>> and all their dependencies to the feature which includes my
>>>>> product plug-in.
>>>>> Also setting the following launch arguments to the product:
>>>>> "-application
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplica tion
>>>>> formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJU nitResultFormatter,junit-results.xml
>>>>> -testPluginName
>>>>> gr.osmosis.posterizer.update.tests.swtbot
>>>>> -className
>>>>> UpdateTests"
>>>>> Unfortunately, the resulting launcher cannot even start the
>>>>> application and i am getting the following entry in the log :
>>>>> !ENTRY org.eclipse.osgi
>>>>> !MESSAGE Application error
>>>>> !STACK 1
>>>>> java.lang.StackOverflowError
>>>>> at java.lang.ThreadLocal.get(ThreadLocal.java:125)
>>>>> at
>>>>> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:85)
>>>>> at
>>>>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
>>>>> at
>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:370)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:446)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:399)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:387)
>>>>> at
>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:315)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1274)
>>>>> at
>>>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)
>>>>> at
>>>>> org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:867)
>>>>> at
>>>>> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
>>>>> at
>>>>> org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .getApplication(UITestApplication.java:85)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:45)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>>> at
>>>>> org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication .start(UITestApplication.java:53)
>>>>> ....
>>>>> repeating.
>>>>> The same happens if i try to launch the test RCP from Ant.
>>>>> Has anybody encountered this error? Why is the application unable
>>>>> to start? Is it stuck in a loop?
>>>>> Thank you in advance for any insight,
>>>>> Sakis
>>>>>
>>>
>
>
>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 05:27:00 GMT 2024
Powered by FUDForum. Page generated in 0.03145 seconds |
] 
Search
Help
Register
Login
Home
