Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 10056 invoked from network); 20 Sep 2010 21:21:56 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Sep 2010 21:21:56 -0000 Received: (qmail 99205 invoked by uid 500); 20 Sep 2010 21:21:56 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 99086 invoked by uid 500); 20 Sep 2010 21:21:55 -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 99079 invoked by uid 99); 20 Sep 2010 21:21:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Sep 2010 21:21:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qy0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Sep 2010 21:21:50 +0000 Received: by qyk30 with SMTP id 30so3533987qyk.16 for ; Mon, 20 Sep 2010 14:21:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=vC80xAmobxYYCX3Fazkwa56qwWf6N67KYkxemS2QpM0=; b=FgycC5QzPFNxk20KCZ1bIUHnLQinBdGAd+wIcZ6TtHEFov9J6bQDpWwxgcnmPQrVUK k6saCVVYtgB9hZTiwFcqN/CJA9KMcMT4K5l+FVjz+u3GD/OnMZSpvnA3djHl3NpXHhp5 F8z1FgbA7T9dfW72W+nR9+ZhoWSueknvZ5/0w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=SCbFHAggBX9M8QKyODidQQmKVdo/DHpEvMqkf1YnYjQmHDYGIlpda0M9oJsj6miCwy t9y0J4ut3wkvKSmEQSdj/DcvcmoUI+TL9t0sepke0hXsLcP2kn8aYT7OP2H3I2e/Oskp StbHl8nPJhqjOT8c0zFc+KFlldZKyo3RoeOU4= MIME-Version: 1.0 Received: by 10.224.2.85 with SMTP id 21mr5301500qai.358.1285017689817; Mon, 20 Sep 2010 14:21:29 -0700 (PDT) Sender: akarasulu@gmail.com Received: by 10.229.248.72 with HTTP; Mon, 20 Sep 2010 14:21:29 -0700 (PDT) In-Reply-To: <4C954D8B.3090501@gmail.com> References: <4C94F265.5030901@gmail.com> <4C954D8B.3090501@gmail.com> Date: Tue, 21 Sep 2010 00:21:29 +0300 X-Google-Sender-Auth: HdxEfWC62S1AY-rOqbD0ahpqKH0 Message-ID: Subject: Re: shared-ldap merge done From: Alex Karasulu To: Apache Directory Developers List , elecharny@apache.org Content-Type: multipart/alternative; boundary=0015175cb8a0ee847b0490b77e57 --0015175cb8a0ee847b0490b77e57 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Sep 19, 2010 at 2:38 AM, Emmanuel Lecharny wrote: > On 9/18/10 9:20 PM, Stefan Seelmann wrote: > >> >> One more thing, just to clarify my last mail about OSGi (I read it and >>> found >>> it a bit like I was micro-managing) : I think that we should wait for the >>> next release of ADS (ie, post 2.0.0-RC1) because we will probably do some >>> other changes in shared (like rename it to API) and we would like to >>> release >>> this asap. Working in a branch on OSGi is just a way to be sure that >>> there >>> won't be any contention in this area, and of course, if the OSGi >>> implementation is finished before we are ready for a release, I have >>> nothing >>> against merging back the branch into trunk. >>> >> Is it really that difficult to make shared/api OSGi bundles? Please >> correct me if I' wrong, but we just need to add the right >> META-INF/MANIFEST.MF that could be generated by the Felix plugin. >> Additionally we need to make sure that we have now split packages, >> that is atm the case for o.a.d.shared.ldap.schema, but could be fixed >> easy. My hope is that we can then use the shared/api bundle directly >> in Studio. >> > > I have no idea. I just want to be sure that it does not stop us when we are > so close to a release. We may aven do that after we have released Shared/API > and before ApacheDS 2.0-RC1. I mean, we have almost closed all the issues we > have in API and shared expecting to be able to release this week, and now > that it's done, thinking about adding these OSGi stuff is just a bit too > much for me. More or less, it's just a problem in the agenda, not a > technical issue. > > I agree with Emm here it's not worth the hassle unless you guys see it as a clear benefit in Studio. > In other word,s if this take 2 hours, and not 3 days, I'm +1, but what I'm > afraid of is that we don't have enough people with some knowledge in this > area to solve an issue that would potentially arise just before, or even > worse, just after we have released. > > Yes this is a worry of mine as well but I was thinking this was a small effort for shared and much much more complicated for the server itself. > That's all what I had in mind when I asked Alex to do that in a branch : I > was scared that it can break the schedule we are trying to set :/ > > May be I'm wrong, or just extra cautious, I don't know... > > Let's play it safe and get the release out without worrying about this additional factor. Regards, -- Alex Karasulu My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://directory.apache.org Apache MINA :: http://mina.apache.org To set up a meeting with me: http://tungle.me/AlexKarasulu --0015175cb8a0ee847b0490b77e57 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sun, Sep 19, 2010 at 2:38 AM, Emmanue= l Lecharny <ele= charny@gmail.com> wrote:
=A0On 9/18/10 9:20 PM, Stefan Seelmann wrote:

One more thing, just to clarify my last mail about OSGi (I read it and foun= d
it a bit like I was micro-managing) : I think that we should wait for the next release of ADS (ie, post 2.0.0-RC1) because we will probably do some other changes in shared (like rename it to API) and we would like to releas= e
this asap. Working in a branch on OSGi is just a way to be sure that there<= br> won't be any contention in this area, and of course, if the OSGi
implementation is finished before we are ready for a release, I have nothin= g
against merging back the branch into trunk.
Is it really that difficult to make shared/api OSGi bundles? Please
correct me if I' wrong, but we just need to add the right
META-INF/MANIFEST.MF that could be generated by the Felix plugin.
Additionally we need to make sure that we have now split packages,
that is atm the case for o.a.d.shared.ldap.schema, but could be fixed
easy. My hope is that we can then use the shared/api bundle directly
in Studio.

I have no idea. I just want to be sure that it does not stop us when we are= so close to a release. We may aven do that after we have released Shared/A= PI and before ApacheDS 2.0-RC1. I mean, we have almost closed all the issue= s we have in API and shared expecting to be able to release this week, and = now that it's done, thinking about adding these OSGi stuff is just a bi= t too much for me. More or less, it's just a problem in the agenda, not= a technical issue.


I agree with Emm here it's not wor= th the hassle unless you guys see it as a clear benefit in Studio.
=A0
In other word,s if this take 2 hours, and not 3 days, I'm +1, but what = I'm afraid of is that we don't have enough people with some knowled= ge in this area to solve an issue that would potentially arise just before,= or even worse, just after we have released.


Yes this is a worry of mine as well bu= t I was thinking this was a small effort for shared and much much more comp= licated for the server itself.
=A0
That's all what I had in mind when I asked Alex to do that in a branch = : I was scared that it can break the schedule we are trying to set :/

May be I'm wrong, or just extra cautious, I don't know...
=


Le= t's play it safe and get the release out without worrying about this ad= ditional factor.=A0

Regards,

--
Alex Karasulu
= My Blog :: http://www.jroller= .com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu
--0015175cb8a0ee847b0490b77e57--