From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31954 invoked by alias); 10 Sep 2005 10:18:24 -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 31940 invoked by uid 22791); 10 Sep 2005 10:18:19 -0000 Received: from hermes.gsix.se (HELO hermes.gsix.se) (193.11.224.23) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 10 Sep 2005 10:18:19 +0000 Received: from toronto.pst.sgsnet.se ([193.11.239.6]) by hermes.gsix.se with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1EE2R2-000778-U1; Sat, 10 Sep 2005 12:18:12 +0200 Message-ID: <4323313D.7090205@minimum.se> Date: Sat, 10 Sep 2005 10:18:00 -0000 From: Martin Olsson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728 MIME-Version: 1.0 To: audriusa@bluewin.ch CC: mauve-discuss@sources.redhat.com Subject: Re: Mauve coding on Windows References: <432259B7.70208@minimum.se> <4321E9E6.1020308@bluewin.ch> <43229EF9.5090408@minimum.se> <43228CB8.2060305@bluewin.ch> In-Reply-To: <43228CB8.2060305@bluewin.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q3/txt/msg00028.txt.bz2 Meskauskas Audrius wrote: > 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. I would really much rater be able to runs all the tests too and they would also be good for reference when I need to check how some problem was solved earlier. And in the long run I'm hoping that my contribution to Mauve will enable me to learn more about the classpath project so that I will be able to contribute to the actual classpath code later. David Gilbert wrote: > It won't be easy to run all the tests on Windows initially, but I > think if we can solve the problem of checking out the CVS into > Eclipse on Windows, it won't be long before someone writes a > utility to make it simple to compile and run all (or a selected > subset of) the tests. And if the end result is more developers > working on Mauve, then I think it is worth the effort. When and if someone fixes the naming problems you got atleast one more developer going into the project; me. If my Eclipse error log is complete it's a matter of renaming at a very minimum say 25 files (or the corresponding dirs ofc). But it would be much nicer to have a consistant naming for the entire directory structure. I would definately vote for renaming the classes that test class Xxxx to XxxxClass instead of Xxxx_ because I think the first name is more descriptive and would confuse mauve newcomers less. regards, martin > > > 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 >>>> >>>> >>> >> >> >