Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 20110 invoked from network); 25 Jul 2005 10:13:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2005 10:13:53 -0000 Received: (qmail 35462 invoked by uid 500); 25 Jul 2005 10:13:51 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 34932 invoked by uid 500); 25 Jul 2005 10:13:50 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 34918 invoked by uid 99); 25 Jul 2005 10:13:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2005 03:13:49 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.111.4.28] (HELO out4.smtp.messagingengine.com) (66.111.4.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2005 03:13:43 -0700 Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id DB1C9CC2BF3 for ; Mon, 25 Jul 2005 06:13:47 -0400 (EDT) X-Sasl-enc: wrninFv905vPebMM6amj+cEo83ZnPivYBmmj4IgZ13T4 1122286426 Received: from [10.0.0.100] (elfriedeholmes.demon.co.uk [80.177.165.206]) by www.fastmail.fm (Postfix) with ESMTP id 1E7C21DC for ; Mon, 25 Jul 2005 06:13:46 -0400 (EDT) Message-ID: <42E4BB5A.7050606@odoko.co.uk> Date: Mon, 25 Jul 2005 11:13:46 +0100 From: Upayavira Organization: Odoko Ltd User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] The impact of using OSGi References: <42E4976F.30702@apache.org> <42E4BB30.1070704@apache.org> In-Reply-To: <42E4BB30.1070704@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: > Bertrand Delacretaz wrote: > >>Apart from that, my impression is that the biggest impact might be on >>the build system and on the directory structure of our code: separating >>the code in a way that makes sense for bundles (separate interfaces >>from implementations, separate units of functionality) would make the >>mapping to OSGI bundles much easier, and may make the core code easier >>to understand. >> >>BTW this maps nicely to the Maven concept of smaller projects organized >>in a hierarchy, and people are working on a Maven 2 plugin to create >>OSGI bundles, so we have some hints here ;-) >> >>I won't be able to help much this month due to more holidays, and as >>usual whoever does the work decides, but I just wanted to expose the >>mental connections that I've been making last week: if we consider >>moving to Maven, this might be the right time to do it, or at least >>try. >> > > Yes, definitly, +5 - has anyone already done some steps towards this? > I'm planning to have a look at it in the next days. Can someone explain how maven/OSGi would play together? OSGi has the ability to download and install packages. It doesn't though have any dependency resolution stuff in it. Does Maven provide that? However, IIUC, Maven is a build-time tool, and any dependency resolution we use should be usable at runtime (even if that isn't always the best time to do it). Could Maven handle this usecase too? Regards, Upayavira