|Re: swtbot with non-default target platform [message #10524 is a reply to message #10491]
||Tue, 16 December 2008 17:51
| Ketan Padegaonkar
Registered: July 2009
You would infact need all the SWTBot plugins on the target platform.
This includes the ui plugin and net.sf.swtbot.finder and
net.sf.swtbot.eclipse.finder in addition to the dependencies for swtbot.
I've tried to minimize the dependencies of net.sf.swtbot.eclipse.ui, but
it still pulls in quite some dependencies. Any ideas around reducing
these dependencies are welcome. I'm thinking about splitting the plugin
into two, with one containing the actual UI that's needed in the
runtime, and the other containing the swtbottstapplication, and is
If packaging your plugins is your concern, then here's what I recommend:
Create two features com.foo.example and com.foo.example.test. The test
feature is what contains the test plugins and swtbot, and the is
dependent on the actual feature that contains your application.
On 16/12/08 21:26, Jonas Pfannschmidt wrote:
> At my job we don't use the default eclipse target platform. So, while
> playing around with swtbot (version 2), I tried to get the rcpmail
> sample running with a different target platform.
> It suprised me, that I have to add net.sf.swtbot.eclipse.ui to the
> target platform. Otherwise I get this error message: Application
> "net.sf.swtbot.eclipse.ui.swtbottestapplication" could not be found in
> the registry
> net.sf.swtbot.eclipse.ui depends on a lot of plugins. I would prefer not
> to add them to my target platform.
> As far as I understand, net.sf.swtbot.eclipse.ui starts the tests in a
> separate thread. Therefore it has to be installed in the running
> eclipse, from which the tests are started. But I don't understand why I
> need to put it in my target platform.
> Can someone clear this up for me?
Powered by FUDForum
. Page generated in 0.02188 seconds