Eclipse Community Forums: Jubula » Jubula doesn´t recognize running AUT after upgrade to 2.0

Home » Archived » Jubula » Jubula doesn´t recognize running AUT after upgrade to 2.0

Jubula doesn´t recognize running AUT after upgrade to 2.0 [message #1064220]

Tue, 18 June 2013 06:27

Eclipse User

Hi there,

upgraded Jubula from 1.2 to 2.0 (latest), switched jar-file and run a clean. AUT is a RCP-Application, wich is installed via Java Web Start (Jubula executes a Batch-file).

After the upgrade Jubula starts the AUT -but when workbench is loaded Jubula does not recognize it and the progress "starting aut" continuous.

Thanks for any tips / hints

Re: Jubula doesn´t recognize running AUT after upgrade to 2.0 [message #1064315 is a reply to message #1064220]

Tue, 18 June 2013 11:47

Eclipse User

I don't know if you've reinstalled your AUT along with the Jubula upgrade, but with an RCP app, the first thing I always check is to make sure Jubula's RCP support plugin is properly installed in the AUT. Smile

Jubula 2.0 may have a new version of the plugin that needs to be installed.

Re: Jubula doesn´t recognize running AUT after upgrade to 2.0 [message #1064316 is a reply to message #1064220]

Tue, 18 June 2013 11:50

Eclipse User

Solved.
JNLP "overwrites" config.ini --> declare property in JNLP:

<resources>
    <property name="osgi.bundles" value="org.eclipse.jubula.rc.rcp@start" />
</resources>

Reference: http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fjava_web_start.htm

Re: Jubula doesn´t recognize running AUT after upgrade to 2.0 [message #1064406 is a reply to message #1064316]

Wed, 19 June 2013 02:31

Eclipse User

Great info. We'll add that to the FAQs.

Thanks

Achim

Re: Jubula doesn´t recognize running AUT after upgrade to 2.0 [message #1070342 is a reply to message #1064316]

Wed, 17 July 2013 15:35

Eclipse User

Fabian Ruckwied wrote on Tue, 18 June 2013 17:50

Solved.
JNLP "overwrites" config.ini --> declare property in JNLP

@Fabian Ruckwied
This is so helpful!

I had the same problem when I tried to use a project that was working with 1.3 and no longer with 2.0 (I have seen there is a new version 2.1 but I have not tried it yet).

Of course I replaced the old org.eclipse.jubula.rc.rcp_1.3.0.201210161256.jar plugin with the new one org.eclipse.jubula.rc.rcp_2.0.0.201303141505.jar in my RCP app.

I solved my problem by adding org.eclipse.jubula.rc.rcp @ start to the osgi.bundles line in my configuration/config.ini file:

#Product Runtime Configuration File
osgi.configuration.area=C:/programdata/<xxxxxx>/configuration
osgi.instance.area=C:/programdata/<xxxxxx>/workspace
osgi.splashPath=platform:/base/plugins/<xxxxxx>.client.ui
eclipse.application=<xxxxxx>.ui.application
eclipse.product=<xxxxxx>.client.ui.product
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start,org.eclipse.jubula.rc.rcp@start
osgi.bundles.defaultStartLevel=4
#Default connect and read timeouts
sun.net.client.defaultConnectTimeout=5000
sun.net.client.defaultReadTimeout=15000

Thank you a lot for your input.

Previous Topic:	extend jubula
Next Topic:	How to properly integrate Jubula with Jenkins

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 07:05:58 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter