From dev-return-105999-apmail-commons-dev-archive=commons.apache.org@commons.apache.org Wed Dec 19 20:42:44 2007 Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 55075 invoked from network); 19 Dec 2007 20:42:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Dec 2007 20:42:44 -0000 Received: (qmail 7269 invoked by uid 500); 19 Dec 2007 20:42:27 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 7160 invoked by uid 500); 19 Dec 2007 20:42:26 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 7141 invoked by uid 99); 19 Dec 2007 20:42:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2007 12:42:26 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of niall.pemberton@gmail.com designates 72.14.214.238 as permitted sender) Received: from [72.14.214.238] (HELO hu-out-0506.google.com) (72.14.214.238) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2007 20:42:04 +0000 Received: by hu-out-0506.google.com with SMTP id 38so1070144huc.5 for ; Wed, 19 Dec 2007 12:42:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=eOEk9kKU6JF3U3sUQqOQHJNexPZxGSde8cnlIThLBbo=; b=Tei21a8Hb/I6WsDtl7RomdX5HifNVXRCiso9ytRVlHTrPNlbom5GeJ1owxuNlSmZT2ynUOHAYPjFMulxhUOVb8bbX1pJFoEEx0rirQIDaS3OO5tJyQBNG4bptYkNxqw4s0HkKlUFqjYbtwlb7YI8beSd2QO10FtGYvgPcz4eVXM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GbdMrBK9zXczOD4je9saUDVYzxH5GTuOmGblQM16rhmuf9fLikAbu1xr/T6qlVwcDcbUCBxuLDoyxH72UP52R7ThXNCZGTGtXB8nK9vUW3TtaA+K/6SIsDovcH4h309W3sHNebGjVfZdChFT3xMOFS+eTsgtTFO6mtcQdtCJ1SY= Received: by 10.78.134.2 with SMTP id h2mr12925238hud.77.1198096925513; Wed, 19 Dec 2007 12:42:05 -0800 (PST) Received: by 10.78.40.11 with HTTP; Wed, 19 Dec 2007 12:42:05 -0800 (PST) Message-ID: <55afdc850712191242k32107b51pa1d4f83291bedb0a@mail.gmail.com> Date: Wed, 19 Dec 2007 20:42:05 +0000 From: "Niall Pemberton" To: "Commons Developers List" Subject: Re: Support for OSGi Cc: dev@felix.apache.org In-Reply-To: <47692CCB.7020608@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47692CCB.7020608@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org On Dec 19, 2007 2:38 PM, Carsten Ziegeler wrote: > Hi, > > the products of commons are highly used throughout many projects. > > It would be great, if the projects here at Apche Commons could help > those projects that are using OSGi. > > OSGi is based around the concept of a bundle - a bundle is a jar file > with additional meta data like the packages it exports and a list of > external packages it is using (please forgive me if I'm simplifying here > too much). > > As many projects are using artifacts from Apache Commons, they need the > specific jars as bundles. This is most often done by creating so called > wrapper bundles: these are jars that have the same contents as the > original library with the addition of the required meta data. > You can find several examples here: > > http://svn.apache.org/repos/asf/felix/trunk/commons/ > > Now, it would be great, if the projects here at Apache Commons would > already provide artifacs that can be directly used in an OSGi environment. +1 in principle and I'm happy to help do the work or apply patches. Don't have great deal of OSGi knowledge - just attended a presentation and went through a tutorial. > All that has to be done is adding some entries to the manifest. This is > usually a list of imported packages, a list of exported packages, a > symbolic name for the bundle and a version. (There are some more but > these are the most important ones). > > Adding these entries can be done by hand (not recommended) or with tools > automatically. For example the Apache Felix maven bundleplugin requires > just some lines of configuration and that's it. We have a mixed bag of build systems here at commons. Until recently we were pretty much maven1, with the odd ant/maven1 mixture. A few components have m2 builds that have been used in anger and recently we added m2 builds for all but 2 of the remaining components. However there has been no commons-wide decision to make m2 the primary build system and its quite likely that there will be future releases using m1. Thats the background and I would suggest that we focus on modifying the m2 builds to support OSGi. Each component's pom inherits from commons-parent[1] - is this something that could be configured there or does it need doing on a component-by-component basis? Perhaps you could either provide a patch for Commons parent - or an example for one component's pom so that we can get a better idea of what's involved to make this work. Niall [1] http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml > It would be great if some of the projects here could add these meta data > as part of their next release. This will make the life of all projects > using OSGi much much easier. > > So if you're interested in helping us, just let us know. We would be > happy to make the required changes to the poms or whatever needs to be > done. I cc'ed the Felix dev list as some Felix developers might not be > subscribed to the commons dev list, so please keep them cross posted. > > Thanks > Carsten > -- > Carsten Ziegeler > cziegeler@apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org