From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7474 invoked by alias); 6 May 2004 04:28:38 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 7431 invoked from network); 6 May 2004 04:28:37 -0000 Received: from unknown (HELO hermes.broadjam.com) (64.73.35.111) by sources.redhat.com with SMTP; 6 May 2004 04:28:37 -0000 Received: by hermes.broadjam.com with Internet Mail Service (5.5.2653.19) id ; Wed, 5 May 2004 23:34:37 -0500 Message-ID: <91109D2A38887045A9549186D4D0EE06011B5671@hermes.broadjam.com> From: Daniel Naab To: "'tromey@redhat.com'" Cc: "'mauve-discuss@sources.redhat.com'" Subject: RE: Mauve usage with custom bootclasspath? Date: Thu, 06 May 2004 04:28:00 -0000 MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2004-q2/txt/msg00069.txt.bz2 Thank you much, things seem to be working well. I have a couple comments/questions: There's a problem with build.xml on Windows, which surfaces when building either through cmd.exe or Cygwin (bash). The lines... .... successfully replace the specified paths in the source, but since Windows uses "\" as the file separator, the resulting Java code won't compile. Somehow those portions of the paths should be escaped out. I got to this point by trying to create an Ant script to do a Mauve checkout and build.. I have no trouble building manually, but when trying to run the configure script from Ant, I ran into the problem that it doesn't seem to have a way to call a shell script with parameters.. of which some escaped " characters may exist. I'm probably just missing something, but noticing that the Ant script also exists, I realized it would probably be easier just to call the appropriate compile target instead. Do I still need to run configure if using the Ant script? What would be the steps necessary to execute the compile target, assuming a clean checkout? I suppose I could just use a makefile instead, but now that I'm as far as I am, that urge to finish is too strong. :) Thanks. The test suite looks excellent, and will be a very useful tool for SwingWT! Dan Naab > -----Original Message----- > From: Tom Tromey [mailto:tromey@redhat.com] > Sent: Wednesday, May 05, 2004 4:22 PM > To: Daniel Naab > Cc: 'mauve-discuss@sources.redhat.com' > Subject: Re: Mauve usage with custom bootclasspath? > > > >>>>> "Daniel" == Daniel Naab 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 >