From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30014 invoked by alias); 29 Nov 2006 16:29:14 -0000 Received: (qmail 30000 invoked by uid 22791); 29 Nov 2006 16:29:13 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,TW_GC X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 29 Nov 2006 16:29:01 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id kATGSxJ2024780 for ; Wed, 29 Nov 2006 11:28:59 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id kATGSw4Q006119; Wed, 29 Nov 2006 11:28:58 -0500 Received: from [172.16.14.101] (to-dhcp1.toronto.redhat.com [172.16.14.101]) by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id kATGSuo5027891; Wed, 29 Nov 2006 11:28:56 -0500 Subject: Re: [fedora-java] src.zip's and rpms in Eclipse From: Anthony Green To: Phil Muldoon Cc: fedora-devel-java-list@redhat.com, Frysk Hackers In-Reply-To: <456CDAE1.10006@redhat.com> References: <456CDAE1.10006@redhat.com> Content-Type: text/plain Date: Wed, 29 Nov 2006 16:29:00 -0000 Message-Id: <1164817735.2943.47.camel@to-dhcp1.toronto.redhat.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 (2.8.1.1-3.fc6) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00242.txt.bz2 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. 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. AG