From dev-return-39217-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Oct 5 16:02:02 2011 Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9426E9308 for ; Wed, 5 Oct 2011 16:02:02 +0000 (UTC) Received: (qmail 44183 invoked by uid 500); 5 Oct 2011 16:02:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 44130 invoked by uid 500); 5 Oct 2011 16:02:02 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 44123 invoked by uid 99); 5 Oct 2011 16:02:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 16:02:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-wy0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 16:01:55 +0000 Received: by wyf23 with SMTP id 23so2173881wyf.37 for ; Wed, 05 Oct 2011 09:01:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=mD9Bn2zRLd9zREARNR2FNRDbF8y7ydeyL4+As5pnVGk=; b=I1rSIkPekp7fq5YEIoSKLZiRXLk4wlRizrGz5XEn1VkAt8euVkP4mC2dVZMWEWiuXz GtHJaw040RHw/dA6+eXsRUyhkGs937045JB5MvUhWA4LSfnQDypI54nQop6ZuYl2v9q8 7j52eJ9iFDnIs9RPlfp6J95TR69jUNHKe23UI= Received: by 10.216.221.162 with SMTP id r34mr6656611wep.35.1317830494315; Wed, 05 Oct 2011 09:01:34 -0700 (PDT) Received: from emmanuel-lecharnys-MacBook-Pro.local (lon92-10-78-226-4-211.fbx.proxad.net. [78.226.4.211]) by mx.google.com with ESMTPS id gg21sm3622941wbb.15.2011.10.05.09.01.33 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 05 Oct 2011 09:01:33 -0700 (PDT) Message-ID: <4E8C7F5D.3080301@gmail.com> Date: Wed, 05 Oct 2011 18:01:33 +0200 From: Emmanuel Lecharny Reply-To: elecharny@apache.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: Apache Directory Developers List Subject: [ADS 2.0] OSGi Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi guys, we have had some plan to make ADS OSGi compliant for 2.0. I think it's time to move forward. Right now, we have reorganized shared in order to make it somehow OSGi compliant (well, at least the bare minimum has been done), but it's not enough. And on the server side, we have almost everything to do. We have three aspects to consider : - modularization - lifecycle - services The very first step is to create modules. That means we must be sure we don't have conflicting packages (we have a few in the server). In order to do that, we must identify the different modules. I suggest we first focus on this aspect atm, because it will shake the code a lot. As I'm not (yet :) and OSGi expert, please feel free to push any ideas you have about a decent roadmap to get this done. Thanks ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com