1) sorry should've been more clear...
the partial stack trace is as follows
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: No suitable Log
constructor [Ljava.lang.Class;@8cf401 for
org.apache.commons.logging.impl.Log4JLogger (Caused by
java.lang.NoClassDefFoundError: org/apache/log4j/Category) (Caused by
org.apache.commons.logging.LogConfigurationException: No suitable Log
constructor [Ljava.lang.Class;@8cf401 for
org.apache.commons.logging.impl.Log4JLogger (Caused by
java.lang.NoClassDefFoundError: org/apache/log4j/Category))
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at net.sf.swtbot.finder.ControlFinder.<clinit>(ControlFinder.java:53)
... 31 more
it throws the exception when its trying to initialize a logger.
i see that this is fixed in the nightly but the nightly ain't working for me
as yet cos of the issues i mentioned previously. so m wondering if there's a
way to hack the installed plugin and remove its dependency on
apache,common.logger.
2) I see that SWTBotTable.java has changed quite a bit. it used to have
several methods but i only see click and doubleclick() i'll try it out.
3) so about click()... take a look at notify(int, event, widget ). version
number 519 i think from 2008-05-13. there is an syncExec at the end of the
notify. this is where the click lands and hence was waiting. now there's a
sleep there. Conditions.Shellcloses() ...hmm...that's new...i'll try that
too..
4) so here's a truth table kind of way of what things are
3.3.1 && 1.1(released) - works fine. the apache.commons.logging throws and
exception but continues.
3.3.1 && nightly : all the failures i mentioned ...but that can be
attributed to a lot of changes.
3.3.2 && 1.1 - see stack trace above . apache commons.logging screwing
things up
3.3.2 && nightly : same as 3.3.1 && nightly
the bottom line is i don't want to use the trunk till its officially
released or there is a real compelling reason. Why? we're developing a
plugin too..the nightly isn't the most stable
*so, basically i need to get the 3.3.2 && 1.1 working. which is the
commons.logging error. Can you suggest a way to fix this. maybe delete the
commons.jar file from plugins and change the feature.xml/manifest of the
released plugin.?
*this doesn't seem to be a compelling reason to switch to the nightly cos it
might be an easy fix that i don't know about and also a whole bunch of my
tests will fail...
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
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
