From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20504 invoked by alias); 29 Oct 2004 06:51:34 -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 20490 invoked from network); 29 Oct 2004 06:51:33 -0000 Received: from unknown (HELO mail2.ewetel.de) (212.6.122.16) by sourceware.org with SMTP; 29 Oct 2004 06:51:33 -0000 Received: from majestix.konqueror.de (dynadsl-080-228-92-239.ewetel.net [80.228.92.239]) by mail2.ewetel.de (8.12.1/8.12.9) with ESMTP id i9T6pQNM006184; Fri, 29 Oct 2004 08:51:27 +0200 (MEST) Received: from [192.168.1.3] (helo=asterix.konqueror.de) by majestix.konqueror.de with esmtp (Exim 4.34) id 1CNQcx-0000Q2-LO; Fri, 29 Oct 2004 08:52:47 +0200 From: Michael Koch To: mauve-discuss@sources.redhat.com Subject: Re: future plans for mauve Date: Fri, 29 Oct 2004 06:51:00 -0000 User-Agent: KMail/1.6.2 Cc: Noa Resare References: <1099032100.2198.50.camel@c-241f72d5.01-60-6c6b701.cust.bredbandsbolaget.se> In-Reply-To: <1099032100.2198.50.camel@c-241f72d5.01-60-6c6b701.cust.bredbandsbolaget.se> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200410290851.50695.konqueror@gmx.de> X-CheckCompat: OK X-SW-Source: 2004-q4/txt/msg00037.txt.bz2 Am Freitag, 29. Oktober 2004 08:41 schrieb Noa Resare: > Hello > > While using mauve for a while now I have felt an urge to put some > time into change/fix some things that I think could be done better. > This will not happen right now, as I would like to see kaffe-1.1.5 > out the door first and I'm going offline for a week tonight but I > thought it would be a good idea to share my ideas with the list > anyway, especially since David Gilbert seems to be thinking about > using a mauve for testing other code than the class library. > > Note that these are just random thoughts, and I'm really open to > suggestions. > > > * The './configure; make tests ARGS' invocation scheme is a little > odd. I'd like to have a small script perhaps called 'mauve' that > took arguments --java=/path/to/java --javac=/path/to/javac. The > rest of the args should be like the KEYS variable. I like to use the ./batch_run. I just ./configure mauve without arguments once. Then I can set COMPILER and RUNTIME accordingly to my test I wanna do and run ./batch_run. Thats much more easy then re-reconfiguring each time. > * Package structure. The part that could be called the 'testlet > api' should live in gnu.testlet. The test runner implementation > should be in gnu.mauve.runner (?) and test hierarchy perhaps in > gnu.mauve.tests. Mauving things around in CVS is a bad idea as the history of changes for the moved files get lost. I often look into such informations. Michael -- Homepage: http://www.worldforge.org/