Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » SWTBot » SWTBot and log4j 1.2.15
SWTBot and log4j 1.2.15 [message #531227] Tue, 04 May 2010 05:02 Go to next message
Eclipse UserFriend
Hello... I'm new to SWTBot and unfortunately I've been having a lot of problems trying to get it to work with my RCP application. I'm working under Eclipse 3.5 and my application has a dependency to log4j 1.2.15 which is what seems to be causing the problems. I presume that is where the problem lies because when I set up the Run Configuration to use log4j 1.2.13, the unit test runs but fails because instead of loading the actual application I want to test, it opens a resource window. However, if I use the right version of log4j for my application, this is loaded but the unit test is unable to execute and throws a "No Classloader found for plug-in org.eclipsecon.swtbot.example":

Exception in thread "WorkbenchTestable" java.lang.IllegalArgumentException: No Classloader found for plug-in org.eclipsecon.swtbot.example
at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.getCl assLoader(RemotePluginTestRunner.java:79)
at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.getTe stClassLoader(RemotePluginTestRunner.java:73)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadC lass(RemoteTestRunner.java:693)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadC lasses(RemoteTestRunner.java:429)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:452)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:390)
at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.main( RemotePluginTestRunner.java:64)
at org.eclipse.swtbot.eclipse.core.UITestApplication.runTests(U ITestApplication.java:117)
at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(Work benchTestable.java:71)
at java.lang.Thread.run(Thread.java:619)

Has anyone else had this kind of problem before or knows how this could be resolved?

Thank you.
Re: SWTBot and log4j 1.2.15 [message #537074 is a reply to message #531227] Tue, 01 June 2010 05:02 Go to previous messageGo to next message
Eclipse UserFriend
No Message Body

[Updated on: Tue, 01 June 2010 05:12] by Moderator

Re: SWTBot and log4j 1.2.15 [message #537077 is a reply to message #531227] Tue, 01 June 2010 05:11 Go to previous messageGo to next message
Eclipse UserFriend
for the solution of your problem you can read:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=307076
I think you must add org.eclipsecon.swtbot.example to your dependencies with "Run / Run Configurations... / Plug-ins". I hope this helps

[Updated on: Tue, 01 June 2010 05:37] by Moderator

Re: SWTBot and log4j 1.2.15 [message #537323 is a reply to message #531227] Tue, 01 June 2010 19:54 Go to previous messageGo to next message
Eclipse UserFriend
If you launch your tests using -consoleLog -debug arguments, you'll see
a list of bundles which don't load up. Most often this happens because
of a missing dependency.

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

On 5/4/10 2:32 PM, paolizq@gmail.com wrote:
> Hello... I'm new to SWTBot and unfortunately I've been having a lot of
> problems trying to get it to work with my RCP application. I'm working
> under Eclipse 3.5 and my application has a dependency to log4j 1.2.15
> which is what seems to be causing the problems. I presume that is where
> the problem lies because when I set up the Run Configuration to use
> log4j 1.2.13, the unit test runs but fails because instead of loading
> the actual application I want to test, it opens a resource window.
> However, if I use the right version of log4j for my application, this is
> loaded but the unit test is unable to execute and throws a "No
> Classloader found for plug-in org.eclipsecon.swtbot.example":
>
> Exception in thread "WorkbenchTestable"
> java.lang.IllegalArgumentException: No Classloader found for plug-in
> org.eclipsecon.swtbot.example
> at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.getCl
> assLoader(RemotePluginTestRunner.java:79)
> at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.getTe
> stClassLoader(RemotePluginTestRunner.java:73)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadC
> lass(RemoteTestRunner.java:693)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadC
> lasses(RemoteTestRunner.java:429)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe
> sts(RemoteTestRunner.java:452)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe
> sts(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R
> emoteTestRunner.java:390)
> at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.main(
> RemotePluginTestRunner.java:64)
> at org.eclipse.swtbot.eclipse.core.UITestApplication.runTests(U
> ITestApplication.java:117)
> at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(Work
> benchTestable.java:71)
> at java.lang.Thread.run(Thread.java:619)
>
> Has anyone else had this kind of problem before or knows how this could
> be resolved?
>
> Thank you.
Re: SWTBot and log4j 1.2.15 [message #537324 is a reply to message #531227] Tue, 01 June 2010 19:57 Go to previous message
Eclipse UserFriend
Also it seems that swtbot has a dep on org.apache.log4j=1.2.13, it
should instead be >=1.2.13. Could you open a bug ?

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

On 5/4/10 2:32 PM, paolizq@gmail.com wrote:
> Hello... I'm new to SWTBot and unfortunately I've been having a lot of
> problems trying to get it to work with my RCP application. I'm working
> under Eclipse 3.5 and my application has a dependency to log4j 1.2.15
> which is what seems to be causing the problems. I presume that is where
> the problem lies because when I set up the Run Configuration to use
> log4j 1.2.13, the unit test runs but fails because instead of loading
> the actual application I want to test, it opens a resource window.
> However, if I use the right version of log4j for my application, this is
> loaded but the unit test is unable to execute and throws a "No
> Classloader found for plug-in org.eclipsecon.swtbot.example":
>
> Exception in thread "WorkbenchTestable"
> java.lang.IllegalArgumentException: No Classloader found for plug-in
> org.eclipsecon.swtbot.example
> at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.getCl
> assLoader(RemotePluginTestRunner.java:79)
> at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.getTe
> stClassLoader(RemotePluginTestRunner.java:73)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadC
> lass(RemoteTestRunner.java:693)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadC
> lasses(RemoteTestRunner.java:429)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe
> sts(RemoteTestRunner.java:452)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe
> sts(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R
> emoteTestRunner.java:390)
> at org.eclipse.swtbot.eclipse.core.RemotePluginTestRunner.main(
> RemotePluginTestRunner.java:64)
> at org.eclipse.swtbot.eclipse.core.UITestApplication.runTests(U
> ITestApplication.java:117)
> at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(Work
> benchTestable.java:71)
> at java.lang.Thread.run(Thread.java:619)
>
> Has anyone else had this kind of problem before or knows how this could
> be resolved?
>
> Thank you.
Previous Topic:Support of Nebula-widgets in SWTBot
Next Topic:Update problems
Goto Forum:
  


Current Time: Wed Jul 23 08:18:01 EDT 2025

Powered by FUDForum. Page generated in 0.04024 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly