From: Tom Tromey <tromey@redhat.com>
To: Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: building with eclipse
Date: Thu, 18 Aug 2005 16:05:00 -0000 [thread overview]
Message-ID: <m3br3vfd5v.fsf@localhost.localdomain> (raw)
I've set things up so that you can build Mauve as an Eclipse project.
It requires you to also have a classpath project at the moment, and it
uses the classpath classes for the bootclasspath of the mauve build.
To see this, use Eclipse 3.1, check out Classpath (and wait for it to
build), then check out Mauve. That should be enough, no configury or
anything else should be required.
An idea for the future would be to add a standard launch
configuration so that you can easily run mauve using the just-built
classpath on jamvm.
A more complicated idea would be a test-running GUI of some sort
(standalone or an Eclipse plugin) that would let you pick subsets of
the tests, see regressions, see what tests are new, etc.
Tom
next reply other threads:[~2005-08-18 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 16:05 Tom Tromey [this message]
2005-08-20 0:35 ` Mark Wielaard
2005-08-22 19:35 ` Tom Tromey
2005-08-29 17:41 ` Mark Wielaard
2005-08-29 19:04 ` Tom Tromey
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=m3br3vfd5v.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--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).