public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: some eclipse updates
Date: Tue, 20 Sep 2005 15:31:00 -0000	[thread overview]
Message-ID: <m3d5n34v8g.fsf@localhost.localdomain> (raw)

Just FYI, a couple of days ago I added an eclipse file template to
mauve cvs.  Now if you make a new mauve file in eclipse, it will
automatically fill in all the header stuff with a FIXME comment at
each place you must edit (the file's purpose, the copyright owner, and
the default Tags setting).

I have a patch here that makes Mauve depend on having classpath and
jamvm projects in the same workspace.  I wasn't sure if folks would
want that or not; personally I find it quite useful as it means I can
easily go from a classpath change to testing it in mauve (using the
just-built classpath and jamvm).

Is anybody out there using eclipse to work on mauve who doesn't want a
setup like this?  Speak up; if nobody else is doing this I will check
it in.

Tom

                 reply	other threads:[~2005-09-20 15:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3d5n34v8g.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).