From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32461 invoked by alias); 10 Sep 2005 07:35:58 -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 32320 invoked by uid 22791); 10 Sep 2005 07:35:32 -0000 Received: from mail13.bluewin.ch (HELO mail13.bluewin.ch) (195.186.18.62) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 10 Sep 2005 07:35:32 +0000 Received: from [127.0.0.1] (62.202.68.103) by mail13.bluewin.ch (Bluewin 7.2.063) id 42DF67480098D384; Sat, 10 Sep 2005 07:35:29 +0000 Message-ID: <43228CB8.2060305@bluewin.ch> Date: Sat, 10 Sep 2005 07:35:00 -0000 From: Meskauskas Audrius Reply-To: audriusa@bluewin.ch User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Martin Olsson , mauve-discuss@sources.redhat.com Subject: Re: Mauve coding on Windows References: <432259B7.70208@minimum.se> <4321E9E6.1020308@bluewin.ch> <43229EF9.5090408@minimum.se> In-Reply-To: <43229EF9.5090408@minimum.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q3/txt/msg00024.txt.bz2 No, I understand. You want to contribute to GNU Classpath project by writing new Mauve tests. But just for this you do not need to run all EXISTING Mauve tests. The existing tests are used to ensure that the new changes in GNU Classpath library itself do not introduce regressions, that nothing is spoiled while improving another part. You can write and run your tests on Sun's jre even without trying to build Classpath itself. After you commit them to CVS, others will run them on Classpath and use the results of your tests.. Of course, it is worthwhile to learn how to to run a complete Mauve test set, and how to build Classpath, and join the main project developing and so on. All this would be great from your side, but it takes time and may not be easy under Windows. The new Mauve tests are very important for us; our coverage is still not sufficient. There are still several important packages where no single class is covered. You told me you want to join us by writing new Mauve tests, I explained how to set up the developing platform in the fastest possible way. Regards. Audrius. Martin Olsson wrote: > > I think you misunderstood; I actually intend to write tests for GNU > classpath. > > > regards, > martin > > > Meskauskas Audrius wrote: > >> As your purpose is to just write some new tests and not to test GNU >> Classpath, the simplest and easiest way would be without much >> thinking to delete all tests. > > > > >>> I would like to write some test cases for the GNU classpath project. >>> I fetched Mauve from CVS (using eclipse "create project from cvs") >>> but I ran into a whole bunch of errors: >>> >>> http://mnemo.minimum.se/error.txt >>> >>> I think these errors are related to me running Windows 2000 and >>> windows does not allow a file called "Color" and a dir called "color". >>> >>> Someone on IRC said that there is atleast one other guy that uses >>> Windows for Mauve development (Jeroen?). If anyone can provide >>> information how I can setup a proper Mauve-compatible dev >>> environment on Windows please drop me a line. >>> >>> --- >>> >>> I also have another question, how do I know what test cases are >>> missing and needs to be implemented? >>> >>> >>> rgrds >>> martin >>> >>> >> > >