Don't treat inner classes as test classes with ant. This had been causing errors like [junit] Testsuite: nom.tam.util.test.ArrayFuncsTest$CloneTest [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 0.039 sec [junit] [junit] Testcase: initializationError(nom.tam.util.test.ArrayFuncsTest$CloneTest): Caused an ERROR [junit] Test class should have exactly one public zero-argument constructor [junit] java.lang.Exception: Test class should have exactly one public zero-argument constructor [junit] at java.lang.reflect.Constructor.newInstance(Constructor.java:532) The fix follows a patch submitted by peter to the hamake project [1]. [1]: http://code.google.com/p/hamake/issues/detail?id=55
Include hamcrest-core explicitly in test classpath. Otherwise I get errors like: [junit] Testcase: initializationError(nom.tam.fits.test.AsciiTableTest): Caused an ERROR [junit] org/hamcrest/SelfDescribing [junit] java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing I don't have this problem with my Gentoo ebuid, because (I think) ANT_TASKS="ant-junit4" eant is taking care of the classpath adjustment automatically (hamcrest-core is listed in /usr/share/junit-4/package.env as a dependency).
Include JUnit4 explicitly in test classpath. Otherwise I get errors like: [junit] No tests found in nom.tam.fits.test.AsciiTableTest because ant is not recognizing the @Test annotation. I don't have this problem with my Gentoo ebuid, because (I think) ANT_TASKS="ant-junit4" eant is taking care of the classpath adjustment automatically.
Begin versioning.