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 >> >> >> >
