From: Martin Olsson <mnemo@minimum.se>
To: audriusa@bluewin.ch
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve coding on Windows
Date: Sat, 10 Sep 2005 10:18:00 -0000 [thread overview]
Message-ID: <4323313D.7090205@minimum.se> (raw)
In-Reply-To: <43228CB8.2060305@bluewin.ch>
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
>>>>
>>>>
>>>
>>
>>
>
next prev parent reply other threads:[~2005-09-10 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 18:58 Martin Olsson
2005-09-09 20:01 ` Meskauskas Audrius
2005-09-09 23:54 ` Martin Olsson
2005-09-10 7:35 ` Meskauskas Audrius
2005-09-10 7:59 ` David Gilbert
2005-09-10 9:30 ` Mauve coding on Windows: The majority of tests runs under Windows Meskauskas Audrius
2005-09-10 10:18 ` Martin Olsson [this message]
2005-09-10 14:49 ` Mauve coding on Windows Dalibor Topic
2005-09-10 6:47 ` David Gilbert
2005-09-10 8:58 ` Andrew Haley
2005-09-10 17:15 ` Meskauskas Audrius
2005-09-16 17:08 ` Tom Tromey
2005-09-16 18:12 ` Meskauskas Audrius
2005-09-10 10:28 Jeroen Frijters
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=4323313D.7090205@minimum.se \
--to=mnemo@minimum.se \
--cc=audriusa@bluewin.ch \
--cc=mauve-discuss@sources.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).