From: Tom Tromey <tromey@redhat.com>
To: listas@lozano.eti.br
Cc: eclipse@sources.redhat.com
Subject: Re: Current Eclipse on Red Hat
Date: Tue, 25 Nov 2003 17:43:00 -0000 [thread overview]
Message-ID: <87vfp8xsix.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20031124203717.EA9D91A867E@smtp.infolink.com.br>
>>>>> ">" == listas <listas@lozano.eti.br> writes:
>> 1. What's the current state of Red Hat Eclipse? The packages tell
>> it's 2.1.x but the about box reports many plugins at 2.0.x.
This was a bug in that particular release... the plugins are lying.
It really is 2.1.0-ish.
>> 2. I got sucess compiling Java classes using only gcj/libgcj but I
>> could not find a way to run them using gij, so I had to configure a
>> Sun JVM. That was the end of my free software java ide. :-(
I think we've fixed this internally. Andrew wrote a patch to tell
eclipse about gij as a java runtime.
You could probably make it work by making a tree with various
symlinks in it. I think Mark Wielaard did that once.
Also, note that once you do get this working, you still won't be able
to debug with the JDT. gij doesn't support JDWP, this is a known
issue.
>> 3. Any plans to support native Java compilation using gcj?
It would be nice. I don't think anybody is working on it ATM.
We're taking patches :-)
>> 4. Plans to update to the latest CDT (1.2.0)? It has many nice
>> features that weren't on previous releases.
Internally we're running 2.1.1 with CDT 1.2.0. I'm not sure when
we'll be releasing it publicly.
Tom
prev parent reply other threads:[~2003-11-25 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 20:37 listas
2003-11-25 17:43 ` Tom Tromey [this message]
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=87vfp8xsix.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eclipse@sources.redhat.com \
--cc=listas@lozano.eti.br \
/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).