Interesting, I just added this line to MANIFEST.MF of the test plugin: Eclipse-RegisterBuddy: org.apache.log4j
Also I've added log4j as a dependency on my plugin. This is how the complete manifest looks: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Test Plug-in Bundle-SymbolicName: org.rcpmail.test Bundle-Version: 1.0.0 Require-Bundle: org.eclipse.ui, org.eclipse.core.runtime, org.rcpmail, net.sf.swtbot.eclipse.finder, net.sf.swtbot.finder, org.junit, org.apache.log4j Eclipse-RegisterBuddy: org.apache.log4j -- Ketan On 23-Jun-08, at 5:07 PM, Hans Schwaebli wrote: > This works for your example, the JUnit tests for the finder plugin. > > But it didn't work for my JUnit Plug-in Test. I put the log4j.xml > file in the SRC dir. It doesn't get it since it complains: > > log4j:WARN No appenders could be found for logger > (net.sf.swtbot.matcher.WidgetMatcherFactory$MenuMatcher). > log4j:WARN Please initialize the log4j system properly. > > I solved it by passing a VM argument when starting the JUnit Plug-in > Test: -Dlog4j.configuration=file:/c:/log4j.xml > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ SWTBot-users mailing list SWTBot-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/swtbot-users http://swtbot.org/ - a functional testing tool for SWT/Eclipse
