There's probably a more definitive link somewhere but you can get an idea of the syntax here:
http://stackoverflow.com/questions/5273802/buildr-multiple-ant-versions-when-testing On Feb 6, 2013, at 2:37 AM, Magnus Melander <[email protected]> wrote: > How did you reject it? > By removing the dependency all together? > > If there is a buildr code snippet for blacklisting jars I'd really like to > get hold of it myself. > > Regards > Magnus > > El 5 feb 2013, a las 23.10, Chris Bozic escribió: > >> You guessed it! I had a transitive dependency for ant-optional coming in >> off of commons-jxpath. Once rejected, my tests run fine. Thanks! >> >> On Tue, Feb 5, 2013 at 4:58 PM, Alex Boisvert <[email protected]>wrote: >> >>> Wild guess: Any chance that one of the .jars in your classpath contain an >>> old version of Ant? Some J2EE platforms sometimes include older versions >>> of Ant in their .jars .... Or maybe one of your dependencies transitively >>> includes an old version of Ant. >>> >>> On Tue, Feb 5, 2013 at 1:51 PM, Chris Bozic <[email protected]> wrote: >>> >>>> Unfortunately, I don't think I can because I can't get it to happen in >>> any >>>> other project I have and I can't figure out the cause of it in the >>> project >>>> where it happens. I can delete any random tests out of the project and >>> it >>>> still happens. >>>> >>>> On Tue, Feb 5, 2013 at 4:41 PM, Alex Boisvert <[email protected] >>>>> wrote: >>>> >>>>> Any chance you can create a small project that reproduces this? >>>>> >>>>> alex >>>>> >>>>> >>>>> On Tue, Feb 5, 2013 at 1:34 PM, Chris Bozic <[email protected]> wrote: >>>>> >>>>>> I'm getting a strange error when I run junit4 tests in an existing >>>>> project >>>>>> I'm converting to work with Buildr. Previously, I've converted >>> several >>>>>> other very similar projects to use Buildr and have never seen >>> anything >>>>> like >>>>>> this. The following error occurs every time I run tests in the >>> default >>>>>> forked test mode: >>>>>> >>>>>> Trying to override old definition of datatype junit >>>>>> [junit] Testsuite: >>> testsfile=/blah/workspace/blah/junittestcases3244787827808189351.properties >>>>>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec >>>>>> [junit] >>>>>> [junit] Caused an ERROR >>>>>> [junit] >>> testsfile=/blah/workspace/blah/junittestcases3244787827808189351.properties >>>>>> [junit] java.lang.ClassNotFoundException: >>> testsfile=/blah/workspace/blah/junittestcases3244787827808189351.properties >>>>>> [junit] at java.lang.Class.forName0(Native Method) >>>>>> [junit] at java.lang.Class.forName(Class.java:186) >>>>>> [junit] >>>>>> [junit] Testsuite: blah.base.validators.Batch-With-Multiple-Tests >>>>>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec >>>>>> [junit] >>>>>> [junit] Testcase: null took 0 sec >>>>>> [junit] Caused an ERROR >>>>>> [junit] Forked Java VM exited abnormally. Please note the time in >>>> the >>>>>> report does not reflect the time until the VM exit. >>>>>> [junit] junit.framework.AssertionFailedError: Forked Java VM >>> exited >>>>>> abnormally. Please note the time in the report does not reflect the >>>> time >>>>>> until the VM exit. >>>>>> [junit] >>>>>> [junit] Tests FAILED (crashed) >>>>>> >>>>>> Can anyone help me figure out why I can't run my tests in forked >>> mode? >
