This is the mail archive of the mauve-discuss@sources.redhat.com mailing list for the Mauve project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: A place for the Classpath specific tests

From: Tom Tromey <tromey at redhat dot com>
To: Mark Wielaard <mark at klomp dot org>
Cc: Dalibor Topic <robilad at kaffe dot org>, Michael Koch <konqueror at gmx dot de>, Meskauskas Audrius <audriusa at bluewin dot ch>, mauve-discuss at sources dot redhat dot com
Date: 15 Mar 2005 10:52:35 -0700
Subject: Re: A place for the Classpath specific tests
References: <000701c5257c$0afc0c70$2101a8c0@computername><20050310160510.GI4737@papacharly.konqueror.de><423073F3.6000102@kaffe.org> <m3d5u44qlz.fsf@localhost.localdomain><1110908210.1186.53.camel@localhost>
Reply-to: tromey at redhat dot com

Mark> OK. How about the following patch to the README:

Looks good.

Mark> By having a tag and a special subdirectory for these tests it should be
Mark> simple to enable/disable these special tests for the various ways people
Mark> run mauve (by hand, make, batch_run, ant script, etc).

I think just putting them in a directory named after their class, like
we do for everything, will suffice.  Using 'gnu.javax.swing....'  is
just as selectable -- and obviously classpath-specific, IMO -- as
'classpath.gnu.javax.swing...'

But I don't have a strong opinion on it.

Tom

References:
- A place for the Classpath specific tests
  - From: Meskauskas Audrius
- Re: A place for the Classpath specific tests
  - From: Michael Koch
- Re: A place for the Classpath specific tests
  - From: Dalibor Topic
- Re: A place for the Classpath specific tests
  - From: Tom Tromey
- Re: A place for the Classpath specific tests
  - From: Mark Wielaard

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]