This is the mail archive of the
mauve-discuss@sources.redhat.com
mailing list for the Mauve project.
Re: Mauve usage with custom bootclasspath?
- From: Tom Tromey <tromey at redhat dot com>
- To: Daniel Naab <dann at broadjam dot com>
- Cc: "'mauve-discuss at sources dot redhat dot com'" <mauve-discuss at sources dot redhat dot com>
- Date: 05 May 2004 15:22:00 -0600
- Subject: Re: Mauve usage with custom bootclasspath?
- References: <91109D2A38887045A9549186D4D0EE06011B5670@hermes.broadjam.com>
- Reply-to: tromey at redhat dot com
>>>>> "Daniel" == Daniel Naab <dann@broadjam.com> writes:
>> ./configure JAVA="{PATH TO JAVA} -bootclasspath=BOOTCLASSPATH"
Daniel> JAVAC="{PATH TO JAVAC} -bootclasspath=BOOTCLASSPATH"
Daniel> Is this the correct approach? Any suggestions for how to
Daniel> isolate tests just to SwingWT?
This looks pretty good.
Once you have everything built, you just need to run the
`gnu.testlet.SimpleTestHarness' program. How you launch it is up to
you.
This program accepts test names on stdin. By default the Makefile
will run it with `cat classes | java ...'. You can easily subset
this: `grep whatever classes | java ...'
Tom