This is the mail archive of the mauve-discuss@sourceware.cygnus.com mailing list for the Mauve project. See the Mauve home page for more information.
Godmar wrote: > So, I'm trying to use mauve some more and am thoroughly confused. > Instead of going through the shell scripts and finding out what's > going on, I'm sending this mail --- should take the same time. > Please consider this user feedback. The only way to do this now is to create a file, say mauve-beans, which contains: ---- cut here ------------------------------------------------ # Config file that tells mauve about the `beans' tag. JDK1.1 !java.lang !java.io !java.util ---- cut here ------------------------------------------------ And run "make KEYS=beans check". We're basically telling it to run all tests with the JDK1.1 tag that aren't in java.lang, .io or .util - leaving .beans :-) > /mauve) > java gnu.testlet.SimpleTestHarness gnu/testlet > java.beans.IntrospectorTest <- I type > FAIL: uncaught exception loading java.beans.IntrospectorTest: java.lang.ClassNotFoundException: java/beans/IntrospectorTest > java.lang.Boolean.hashcode_Boolean <- I type > FAIL: uncaught exception loading java.lang.Boolean.hashcode_Boolean: java.lang.ClassNotFoundException: java/lang/Boolean/hashcode_Boolean > 2 of 2 tests failed > > Hmm, did I run the tests? No. Try: $ java gnu.testlet.SimpleTestHarness gnu/testlet gnu.testlet.java.beans.IntrospectorTest <- type this FAIL: gnu.testlet.java.beans.IntrospectorTest (number 6) 1 of 10 tests failed But really, you should try the tag-file above. AG -- Anthony Green Cygnus Solutions Sunnyvale, California