Eclipse Community Forums: SWTBot » How to define plugin start level in SWTBot run configuration (Spring DM)

Help

Home

Home » Eclipse Projects » SWTBot » How to define plugin start level in SWTBot run configuration (Spring DM)

Show: Today's Messages :: Show Polls :: Message Navigator

How to define plugin start level in SWTBot run configuration (Spring DM) [message #547363]

Fri, 16 July 2010 13:15

Vlastimil Dolejs

Messages: 6
Registered: July 2010

Junior Member

Hi,
I'm facing problem with start level of plugins in SWTBot run configuration. We use Spring DM in our product. Spring DM requires that plugin org.springframework.osgi.extender has lower start level than our plugins (start before our plugins).
I've simply tried, what works with our Eclipse Application run configuration - on tab Plug-ins checked all required plugins and for org.springframework.osgi.extender plugin selected Start Level: 1 and Auto-Start: true.
But when i run this confguration, it ignores selected start level.
I run it with tracing org.eclipse.osgi/debug.startlevel and output is:

Trying to resume bundle org.springframework.osgi.extender_1.2.1 [176]
SLL: Bundle Startlevel set to 4
SLL: bundle active=false; newSL = 4; activeSL = 6
SLL: starting bundle 177

Bundle has start level 4 which is default.

Is there any way haw to set start level of bundles?
Are you anybody running SWTBot tests on Spring DM enabled product?

Thanks

Report message to a moderator

Re: How to define plugin start level in SWTBot run configuration (Spring DM) [message #547398 is a reply to message #547363]

Fri, 16 July 2010 15:25

Ketan Padegaonkar

Messages: 873
Registered: July 2009

Senior Member

Please pardon my ignorance about Spring DM. I've not used spring DM
ever, but might be able to help if you can describe what specific
problems you're facing?

Could you try running with -debug -consoleLog arguments ?

--
Ketan
http://ketan.padegaonkar.name | http://eclipse.org/swtbot

On 7/16/10 6:15 AM, Vlastimil Dolejs wrote:
> Hi,
> I'm facing problem with start level of plugins in SWTBot run
> configuration. We use Spring DM in our product. Spring DM requires that
> plugin org.springframework.osgi.extender has lower start level than our
> plugins (start before our plugins).
> I've simply tried, what works with our Eclipse Application run
> configuration - on tab Plug-ins checked all required plugins and for
> org.springframework.osgi.extender plugin selected Start Level: 1 and
> Auto-Start: true.
> But when i run this confguration, it ignores selected start level.
> I run it with tracing org.eclipse.osgi/debug.startlevel and output is:
>
>
> Trying to resume bundle org.springframework.osgi.extender_1.2.1 [176]
> SLL: Bundle Startlevel set to 4
> SLL: bundle active=false; newSL = 4; activeSL = 6
> SLL: starting bundle 177
>
>
> Bundle has start level 4 which is default.
>
> Is there any way haw to set start level of bundles?
> Are you anybody running SWTBot tests on Spring DM enabled product?
>
> Thanks

Report message to a moderator

Re: How to define plugin start level in SWTBot run configuration (Spring DM) [message #547948 is a reply to message #547398]

Tue, 20 July 2010 09:04

Vlastimil Dolejs

Messages: 6
Registered: July 2010

Junior Member

Hi,
Problem is, that SWTBot run configuration ignores start level of bundles on plug-ins tab.
I set start level for bundle org.springframework.osgi.extender to 1 and it starts with 4 (default).

I've been elaborating this issue and found, that normal run config (eclipse application) generates config.ini with param osgi.bundles={bundles} where {bundles} is list of bundles selected on plug-ins tab with their start level.
SWTBot run configuration generates config.ini which has allways param osgi.bundles set to:

osgi.bundles=reference\:file\:D\:/apps/eclipse/eclipse 3.5.2/plugins/org.eclipse.equinox.common_3.5.1.R35x_v20090807-1100.jar@2\:start,reference\:file\:D\:/apps/eclipse/eclipse 3.5.2/plugins/org.eclipse.update.configurator_3.3.0.v20090312.jar@3\:start,reference\:file\:D\:/apps/eclipse/eclipse 3.5.2/plugins/org.eclipse.core.runtime_3.5.0.v20090525.jar@start

If I check Use an existing config.ini file as a template and select template with osgi.bundles parameter copy-pasted from Eclipse Application run configuration then it works.

So i think problem is with generation a config.ini file.

Spring DM is not involved in problem. I just mentioned it as for Spring DM are start levels of bundles essential.
Thanks

Report message to a moderator

Re: How to define plugin start level in SWTBot run configuration (Spring DM) [message #548029 is a reply to message #547948]

Tue, 20 July 2010 13:06

Pascal G

Messages: 157
Registered: July 2009

Senior Member

On 10-07-20 05:04 AM, Vlastimil Dolejs wrote:
> Hi,
> Problem is, that SWTBot run configuration ignores start level of bundles
> on plug-ins tab.
> I set start level for bundle org.springframework.osgi.extender to 1 and
> it starts with 4 (default).
>
> I've been elaborating this issue and found, that normal run config
> (eclipse application) generates config.ini with param
> osgi.bundles={bundles} where {bundles} is list of bundles selected on
> plug-ins tab with their start level.
> SWTBot run configuration generates config.ini which has allways param
> osgi.bundles set to:
> osgi.bundles=reference\:file\:D\:/apps/eclipse/eclipse
> 3.5.2/plugins/org.eclipse.equinox.common_3.5.1.R35x_v20090807-1100.jar@2\:start,reference\:file\:D\:/apps/eclipse/eclipse
> 3.5.2/plugins/org.eclipse.update.configurator_3.3.0.v20090312.jar@3\:start,reference\:file\:D\:/apps/eclipse/eclipse
> 3.5.2/plugins/org.eclipse.core.runtime_3.5.0.v20090525.jar@start
> If I check Use an existing config.ini file as a template and select
> template with osgi.bundles parameter copy-pasted from Eclipse
> Application run configuration then it works.
>
> So i think problem is with generation a config.ini file.
>
> Spring DM is not involved in problem. I just mentioned it as for Spring
> DM are start levels of bundles essential.
> Thanks

I'm not even sure that this might be SWTBot-related. You see, the SWTBot
run configuration is a clone of PDE's JUnit configuration. Could you try
to run your tests using this instead? There's not much difference,
probably the only thing different you should do is uncheck "Run in the
UI thread". If this still doesn't work, then it is most probably because
PDE's JUnit launcher doesn't handle plugins start level and you might
want to check with PDE/JUnit guys. If it works, well, we'll try and poke
around to see what's wrong ;)

Hope this helps
--
Pascal Gélinas | Software Developer
*Nu Echo Inc.*
http://www.nuecho.com/ | http://blog.nuecho.com/

*Because performance matters.*

Report message to a moderator