From: Tom Tromey <tromey@redhat.com>
To: audriusa@bluewin.ch
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve coding on Windows
Date: Fri, 16 Sep 2005 17:08:00 -0000 [thread overview]
Message-ID: <m3wtlheyic.fsf@localhost.localdomain> (raw)
In-Reply-To: <432314BD.9000202@bluewin.ch>
>>>>> "Audrius" == Meskauskas Audrius <audriusa@bluewin.ch> writes:
Audrius> I created Eclipse project from existing Mauve sources using "New ->
Audrius> Java project from existing Ant build file". Then the build is
Audrius> initiated as "Run as -> Ant build" in the context menu on build.xml in
Audrius> the Package Explorer view.
Mauve is already set up in Eclipse as a plain old java project, where
the internal eclipse builder is used. I think this is preferable as
it yields a nicer development environment...
Also in my setup, the mauve project depends on having a Classpath
project in the same workspace, the idea being that mauve will be built
against the just-built Classpath. I also have it depending on a jamvm
project, to make it really easy to run mauve against classpath from
inside Eclipse. I haven't checked this part in yet.
Tom
next prev parent reply other threads:[~2005-09-16 17:08 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 ` 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 [this message]
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=m3wtlheyic.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--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).