public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Zander <zander@javalobby.org>
To: mauve-discuss@sources.redhat.com
Cc: Andrew John Hughes <gnu_andrew@member.fsf.org>,
	classpath@gnu.org, tromey@redhat.com,
	Robert Lougher <rob.lougher@gmail.com>
Subject: Re: Mauve patches for SpinnerListModel
Date: Mon, 06 Sep 2004 16:24:00 -0000	[thread overview]
Message-ID: <200409061822.17777.zander@javalobby.org> (raw)
In-Reply-To: <1094412368.2117.98.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 05 September 2004 21:26, Mark Wielaard wrote:
> > Also, does anyone have any idea as to why Mauve only seems to test
> > java.io and java.net when I run make check?  Using ant, I can get it
> > to compile all the tests but it segfaults in
> > java.lang.reflect.Array.newInstance.
>
> For these kind of questions there is the
> mauve-discuss@sources.redhat.com mailinglist.

Immediately after reporting the bug :) you can alter the build.xml to only 
test the classes you wrote quite easilly.
In the "test" target there are some <fileset /> lines and all you have to 
do is to make sure the includes part points to the dir you want to test 
(it will take all subclasses as well if you use 2 *'s at the end)

Naturally you should remove the fileset tags you don't want (there are 2 by 
default)

- -- 
Regards
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBPI64CojCW6H2z/QRAmaQAKCEUrxJ5Fj+wL8V8PFxt8DWnrifqQCff/0o
HZHR71RZTMXYc6BzUWtPof8=
=aAyF
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2004-09-06 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040819003736.GA24589@middle-earth.co.uk>
2004-09-05 19:27 ` Mark Wielaard
2004-09-06  2:36   ` Robert Lougher
2004-09-06 16:24   ` Thomas Zander [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200409061822.17777.zander@javalobby.org \
    --to=zander@javalobby.org \
    --cc=classpath@gnu.org \
    --cc=gnu_andrew@member.fsf.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=rob.lougher@gmail.com \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).