From: Timothy W. <tw...@us...> - 2006-11-09 20:50:47
|
You have several options: 1) change abbot.AssertionFailedError itself to have a different definition in your local copy. you might be able to simply substitute another defnition upstream in the class path. 2) define your own junit.framework.AssertionFailedError, include it in the classpath and remove junit.jar It might be possible to use a different exception and then account for it in ComponentTestFixture, but that wouldn't cover all original cases which need to handle instances of the junit exception. On Nov 9, 2006, at 1:19 AM, Alex Ruiz wrote: > Dear Abbot developers, > > Is it possible to change abbot.AssertionFailedError for not > subclassing junit.framework.AssertionFailedError? The reason behind > my question is that I'm trying to run Abbot and TestNG (in TestNG- > Abbot) without any dependencies in JUnit. So far, I haven't been > able to run Script-based tests (without having JUnit in the > classpath) because of this dependency on JUnit. If by any reason it > is not possible, I'll try to find another way to accomplish my goal. > > Thank you very much in advance, > Alex. > ---------------------------------------------------------------------- > --- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642______________________________ > _________________ > abbot-users mailing list > abb...@li... > https://lists.sourceforge.net/lists/listinfo/abbot-users Timothy Wall http://abbot.sf.net |