ah nice, how could I have missed that? but it doesn't fix the NoClassDefFoundError errors that you get when writing tests for a newer version of the api.
what do you think about pushing the jr core version to 2.0 on the perf base? are we still writing tests for 1.6? ... and adding junit as a dependency to the test suite. This is just nice to have, so I can run the tests directly from Eclipse ;) it would not change anything, we'd just add the @Test from junit too, so Eclipse would be happy to run any test for you. thanks, alex On Thu, Oct 6, 2011 at 12:10 PM, Jukka Zitting <[email protected]>wrote: > Hi, > > On Tue, Oct 4, 2011 at 7:00 PM, Alex Parvulescu > <[email protected]> wrote: > > What is the best way to exclude a test from a version down? (or include > it > > from a version up, for that matter :) > > See the failOnRepositoryVersions() method in AbstractTest. It's used > by the BigFileWriteTest to exclude test runs on repository versions > where the test case simply doesn't work. > > A call like failOnReposiotyrVersions("1.") in the beforeSuite() method > will disable a test for all Jackrabbit 1.x versions. > > BR, > > Jukka Zitting >
