No idea. I suggest you reopen BUILDR-161 with your test case, and we'll do our best to fix the problem.
On Tue, Aug 31, 2010 at 07:32, Mark Petrovic <[email protected]> wrote: > This is still a headscratcher, as the test in question has been converted > to JUnit4: > > ... with --trace set in the invocation to buildr... > > Class org.apache.tools.ant.util.FileUtils loaded from parent loader > (parentFirst) > Could not load class > (org.apache.tools.ant.taskdefs.optional.junit.JUnitTask) for type junit > Could not load class > (org.apache.tools.ant.taskdefs.optional.junit.JUnitTask) for type junit > Trying to override old definition of datatype junit > +Datatype junit org.apache.tools.ant.taskdefs.optional.junit.JUnitTask > ... > > where > > $ env |grep ANT_HOME > ANT_HOME=/Users/petrovic/Ant/ant > > and > > $ jar tf $ANT_HOME/lib/ant-junit.jar |grep JUnitTask\.class > org/apache/tools/ant/taskdefs/optional/junit/JUnitTask.class > > > I'll try to dig into the buildr 1.4.1 source to figure this out. > > Or, is this is expected behavior until the 1.4.2 release? I thought it was > only expected behavior if the tests were written for JUnit3. > > > On Aug 28, 2010, at 11:03 AM, Antoine Toulme wrote: > > > I committed a test ; I had to fix the current behavior which assumes > junit4 > > is in the classpath, so this functionality will be released with 1.4.2. > > > > On Sat, Aug 28, 2010 at 10:10, Antoine Toulme <[email protected] > >wrote: > > > >> Pointing out ? You can use junit3 for your project by changing your user > >> setting or in the Buildfile do: > >> > >> Buildr.settings.build['junit'] = '3.8.1' > >> > >> I guess I need to add a test for that :) > >> > >> > >> On Sat, Aug 28, 2010 at 10:00, Mark Petrovic <[email protected]> > wrote: > >> > >>> Yes, in fact, they are junit3 tests. I should change them to junit4, > but > >>> can buildr automate pointing out the condition? > >>> > >>> > >>> On Aug 28, 2010, at 9:46 AM, Antoine Toulme wrote: > >>> > >>>> I think it might be because of junit3 tests running in junit4. Are > your > >>>> tests junit 3 tests ? > >>>> > >>>> The junit4 runner must be the one logging this. > >>>> > >>>> On Sat, Aug 28, 2010 at 07:17, Mark Petrovic <[email protected]> > >>> wrote: > >>>> > >>>>> I'm seeing > >>>>> > >>>>> "Trying to override old definition of datatype junit" > >>>>> > >>>>> when I run tests on a certain project. Appears to be the same issue > as > >>>>> https://issues.apache.org/jira/browse/BUILDR-161. > >>>>> > >>>>> What causes this? > >>>>> > >>>>> -- > >>>>> Mark Petrovic > >>>>> > >>>>> > >>>>> > >>> > >>> > >>> -- > >>> Mark Petrovic > >>> > >>> > >>> > >> > >
