Looks like JUnit 3.8 being used to compile the code, and 3.7 when running. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers
Robert Leftwich <[EMAIL PROTECTED]> wrote on 20/09/2002 09:39:54 PM: > I am just moving a project to Maven (outstanding tool that it is!) and have > come across some weird behavior when running unit tests under JUnit 3.8x. > Some of my tests are failing on calls to assertEquals(string, string, > string), and they don't when running the exact same code from inside > Eclipse (using a Maven-generated project). If I switch Maven over to JUnit > 3.7 and recompile then all is well. If I log the offending strings just > prior to the assertEquals() call, they are equal. Anyone have any ideas on > this one? > > Robert > > PS I am using w2000, jdk 1.4.0 and the Maven 1.0b6 binary distro. > > PPS I notice that Moritz Petersen > (http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-maven- > [EMAIL PROTECTED]&msgId=471814) > has reported something similar, but he saw java.lang.NoSuchMethodError > problems whereas I am seeing assertEquals() failing and reporting a JUnit > Error, i.e. Testcase: testDocumentCreation took 0.156 sec > Caused an ERROR > junit.framework.Assert.assertEquals(Ljava/lang/String; > Ljava/lang/String;Ljava/lang/String;).... > > > -- > To unsubscribe, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
