From dev-return-105994-apmail-commons-dev-archive=commons.apache.org@commons.apache.org Wed Dec 19 15:48:14 2007 Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 36115 invoked from network); 19 Dec 2007 15:48:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Dec 2007 15:48:11 -0000 Received: (qmail 26434 invoked by uid 500); 19 Dec 2007 15:47:58 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 26338 invoked by uid 500); 19 Dec 2007 15:47:58 -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 26179 invoked by uid 99); 19 Dec 2007 15:47:57 -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 07:47:57 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 19 Dec 2007 15:47:43 +0000 Received: (qmail 35619 invoked from network); 19 Dec 2007 15:47:46 -0000 Received: from localhost (HELO carsten-ziegelers-computer.local) (127.0.0.1) by localhost with SMTP; 19 Dec 2007 15:47:46 -0000 Message-ID: <47693D21.5050805@apache.org> Date: Wed, 19 Dec 2007 16:47:45 +0100 From: Carsten Ziegeler User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Jakarta Commons Developers List CC: dev@felix.apache.org Subject: Re: Support for OSGi References: <47692CCB.7020608@apache.org> <4c39e3030712190704x61e18681oa78b1293fc93d7a3@mail.gmail.com> In-Reply-To: <4c39e3030712190704x61e18681oa78b1293fc93d7a3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org nicolas de loof wrote: > Could such support be added using maven-osgi ? > (https://svn.apache.org/repos/asf/maven/shared/trunk/maven-osgi/) This artifact contains some utility code - in fact it is used by the Felix bundleplugin http://svn.apache.org/repos/asf/felix/trunk/bundleplugin So, you need the bundleplugin. > I've never used it myself, but from what I've read on osgi, the bundle > meta-datas could be created based on the POM (for modules depdendencies, > version, etc..) Just the public API needs to be set in any way. Yes, exactly - it's not that much you have to define. > > The felix wrappers (http://svn.apache.org/repos/asf/felix/trunk/commons/) > use a custom bundle packaging based on felix maven-bundle-plugin. How to > this tooling overlap with maven-osgi ? The maven-bundle-plugin is the one to use (as outlined above) > > Latest question, why not just provide the required MANIFEST entries (or > plugin configuration) as patch ? All the required work seems to have been > done on felix side ! Yes, that's basically our idea - on the other hand, we don't want to provide all the patches when there is no interest in applying them :) So, this thread is about checking interest :) and perhaps some of the commons projects want to do it on their own :) Carsten > > Nico. > > 2007/12/19, Carsten Ziegeler : >> 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. >> >> 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. >> >> 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 >> >> > -- Carsten Ziegeler cziegeler@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org