From: Andrew Overholt <overholt@redhat.com>
To: Anthony Green <green@redhat.com>, Ben Konrath <bkonrath@redhat.com>
Cc: Phil Muldoon <pmuldoon@redhat.com>,
fedora-devel-java-list@redhat.com,
Frysk Hackers <frysk@sourceware.org>
Subject: Re: [fedora-java] src.zip's and rpms in Eclipse
Date: Wed, 29 Nov 2006 16:45:00 -0000 [thread overview]
Message-ID: <1164818423.30106.9.camel@toxic.toronto.redhat.com> (raw)
In-Reply-To: <1164817735.2943.47.camel@to-dhcp1.toronto.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Wed, 2006-29-11 at 08:28 -0800, Anthony Green wrote:
> On Tue, 2006-11-28 at 18:57 -0600, Phil Muldoon wrote:
> > Is
> > there a Wiki page, guide .. or general advice to accomplish this as it
> > is done via the Classpath rpm?
>
> I was under the impression that Eclipse finds the target JDK's src.zip
> based on well known conventions of JDK layout (which we follow in
> java-1.4.2-gcj-compat). As far as I know there's no way to do this for
> random jar files. You need to manually attach the source jar/zip to the
> jar file within Eclipse.
No, I think it can be done for any jar. Ben will know, though.
> Perhaps it makes sense to add a manifest file tag identifying the
> location of the jar file's source code. Then Eclipse could be taught to
> look for the source itself. Maybe this is something Andrew and team can
> tackle as part of their new Eclipse Linux packaging effort at
> eclipse.org.
Har-har :)
Andrew
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-29 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:57 Phil Muldoon
2006-11-29 16:29 ` [fedora-java] " Anthony Green
2006-11-29 16:45 ` Andrew Overholt [this message]
2006-11-30 20:26 ` Ben Konrath
2006-12-05 21:57 ` Nicolas Mailhot
2006-12-06 5:41 ` Ben Konrath
2006-11-29 16:53 ` Phil Muldoon
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=1164818423.30106.9.camel@toxic.toronto.redhat.com \
--to=overholt@redhat.com \
--cc=bkonrath@redhat.com \
--cc=fedora-devel-java-list@redhat.com \
--cc=frysk@sourceware.org \
--cc=green@redhat.com \
--cc=pmuldoon@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).