From: Meskauskas Audrius <audriusa@bluewin.ch>
To: Martin Olsson <mnemo@minimum.se>, mauve-discuss@sources.redhat.com
Subject: Re: Mauve coding on Windows
Date: Fri, 09 Sep 2005 20:01:00 -0000 [thread overview]
Message-ID: <4321E9E6.1020308@bluewin.ch> (raw)
In-Reply-To: <432259B7.70208@minimum.se>
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.
Store the unmodified copy of the source. Then remove
'BinaryCompatibility', 'gnu', 'java', 'javax', 'locales' and 'org' from
gnu/testlet. Try to build. Errors will be reported in
gnu/testlet/config.java, because the generated file names contain the
'\' character (separator under Windows!). Open that file and replace the
'\' by '\\' in all strings. Try to build again. Should succeed. Now,
look at the contents the previously deleted gnu/testlet/java,
gnu/testlet/javax and so on, to see how the tests look like and that
rules the folder system follows. All tests implement the Testlet
interface and has the line like "// Tags: JDK1.4" on the top. The Mauve
framework is rather clear, you will understand. Try to move back,
compile and run several tests that would look simple for you.
If still fails, check:
1. If Eclipse has copied all source files into the project folder in
workspace.
2. If your Ant is properly installed and added to the project build path.
Martin Olsson wrote:
> Hi,
>
> 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-09 20:01 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 [this message]
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 ` Mauve coding on Windows Martin Olsson
2005-09-10 14:49 ` 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=4321E9E6.1020308@bluewin.ch \
--to=audriusa@bluewin.ch \
--cc=mauve-discuss@sources.redhat.com \
--cc=mnemo@minimum.se \
/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).