Mauve usage with custom bootclasspath?

Mauve usage with custom bootclasspath?

[Daniel Naab]

I'm attempting to create some scripts to test the SwingWT library, a Swing
implementation over SWT:

http://swingwt.sourceforge.net

Given the nature of the library (replacement for existing base runtime
libraries) and a desire to allow the test suite to run under any JVM
configuration, I'd like to run the tests with SwingWT in the boot class
path.  Assume running with the Sun JDK, how would I go about this?  I'm
trying something along these lines currently:

> autoreconf
> ./configure JAVA="{PATH TO JAVA} -bootclasspath=BOOTCLASSPATH"
JAVAC="{PATH TO JAVAC} -bootclasspath=BOOTCLASSPATH"
> make check

where BOOTCLASSPATH = {PATH TO SWINGWT JAR};{PATH TO RT.JAR}

Is this the correct approach?  Any suggestions for how to isolate tests just
to SwingWT?  Forgive my ignorance if this is the incorrect way to use Mauve,
but I found it difficult for find documentation.

Thank you!

Daniel Naab

Re: Mauve usage with custom bootclasspath?

[Tom Tromey]

>>>>> "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

RE: Mauve usage with custom bootclasspath?

[Daniel Naab]

I was able to get things going in a cross-platform way by using a
combination of configure and an external call to the build.xml compile tag.
Thanks for the help.

Dan

> -----Original Message-----
> From: Daniel Naab 
> Sent: Wednesday, May 05, 2004 11:35 PM
> To: 'tromey@redhat.com'
> Cc: 'mauve-discuss@sources.redhat.com'
> Subject: RE: Mauve usage with custom bootclasspath?
> 
> 
> Thank you much, things seem to be working well.  I have a 
> couple comments/questions:

RE: Mauve usage with custom bootclasspath?

[Daniel Naab]

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...

        <filter token="SRCDIR" value="${user.dir}"/>
        <filter token="TMPDIR" value="${java.io.tmpdir}" />
        <filter token="CHECK_PATH_SEPARATOR" value="${path.separator}"/>
        <filter token="CHECK_FILE_SEPARATOR" value="${file.separator}"/>

.... 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 <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
>