Return-Path: Delivered-To: apmail-incubator-felix-dev-archive@www.apache.org Received: (qmail 89135 invoked from network); 22 Jan 2007 15:02:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2007 15:02:40 -0000 Received: (qmail 92328 invoked by uid 500); 22 Jan 2007 15:02:45 -0000 Delivered-To: apmail-incubator-felix-dev-archive@incubator.apache.org Received: (qmail 92302 invoked by uid 500); 22 Jan 2007 15:02:45 -0000 Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: felix-dev@incubator.apache.org Delivered-To: mailing list felix-dev@incubator.apache.org Received: (qmail 92291 invoked by uid 99); 22 Jan 2007 15:02:45 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2007 07:02:45 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [207.190.94.33] (HELO gadget.mwt.net) (207.190.94.33) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2007 07:02:35 -0800 Received: from 192.168.1.8 (dsl-67-41.westby.mwt.net [207.190.67.41]) by gadget.mwt.net (8.13.6/8.12.11) with ESMTP id l0MF2Cgi023740 for ; Mon, 22 Jan 2007 09:02:13 -0600 Subject: Re: Bundle-Classpath and Bnd From: "John E. Conlon" Reply-To: jconlon@verticon.com To: felix-dev@incubator.apache.org In-Reply-To: <45B3B523.2070701@ungoverned.org> References: <1169404286.5262.10.camel@trout> <45B3B523.2070701@ungoverned.org> Content-Type: text/plain Organization: Verticon, Inc. Date: Mon, 22 Jan 2007 09:02:11 -0600 Message-Id: <1169478131.4735.5.camel@trout> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-27.rhel4.6) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Sun, 2007-01-21 at 13:46 -0500, Richard S. Hall wrote: > John E. Conlon wrote: > > Ran across a case where a project bundle was using a Bundle-Classpath > > entry with the /target/classes/ value in it's manifest even though it > > had no such path in the bundle. As expected Bnd flagged this as an > > error. > > > > Over at the spring-osgi maillist someone mentioned this practice as a > > way to get their bundle working in an equinox environment. Don't > > understand this statement really - Although I run eclipse I don't have > > much experience with Equinox. > > > > Is fudging the behavior of Bundle-Classpath in this manner okay or is > > this verboten? > > Yes, they are using this trick to get their bundles to work correctly as > PDE projects (they are working with maven that puts classes in > target/classes, but PDE doesn't expect them there, so they can add this > to the bundle class path to get PDE to look in the right place...or > something like that). > > The spec says that missing class path entries should be ignored, so this > is ok I guess, but it does make life difficult for BND. > I may not understand this... but doesn't the path refer to resources within the bundle/jar? If a bundle is created with a Bundle-Classpath pointing to /target/classes/ why would the Equinox runtime look for resources on the file system? Do other frameworks do this? So if I create a production bundle and deploy it with such a Bundle- Classpath and one or more OSGi frameworks looks outside of the bundle for resources on the filesystem wouldn't this be a potential security issue? regards - John