Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 30469 invoked from network); 4 Nov 2005 18:50:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Nov 2005 18:50:11 -0000 Received: (qmail 55561 invoked by uid 500); 4 Nov 2005 18:50:10 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 55505 invoked by uid 500); 4 Nov 2005 18:50:09 -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 55489 invoked by uid 99); 4 Nov 2005 18:50:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Nov 2005 10:50:09 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lyndon.washington@gmail.com designates 64.233.162.207 as permitted sender) Received: from [64.233.162.207] (HELO zproxy.gmail.com) (64.233.162.207) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Nov 2005 10:50:04 -0800 Received: by zproxy.gmail.com with SMTP id 13so314749nzn for ; Fri, 04 Nov 2005 10:49:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=XyNkXapoFfotfguj9g2m/NnRoaTu6G0vmfnmwt6wyH3uUqNAWc6f5CYklUy5OWiTns4Wgkajn4zlPXCZMHXJ2p6s4cI5ATEEYvI5ZZYJJjm+7gPMcdoX750ptvS2i12GDC7xKDS0dpkyjBZtWdtjra7t0216nVxp893d3cUxH+E= Received: by 10.65.137.20 with SMTP id p20mr2431679qbn; Fri, 04 Nov 2005 10:49:47 -0800 (PST) Received: by 10.65.124.13 with HTTP; Fri, 4 Nov 2005 10:49:47 -0800 (PST) Message-ID: <524960cd0511041049s17557ed7k657091cd52dda2a8@mail.gmail.com> Date: Fri, 4 Nov 2005 13:49:47 -0500 From: Lyndon Washington To: Apache Directory Developers List Subject: Re: OSGi RoadMap In-Reply-To: <436BA0BE.4050908@apache.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3177_30155631.1131130187273" References: <1131125604.4076.105.camel@trout> <436B9E90.9020607@bellsouth.net> <436BA0BE.4050908@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_3177_30155631.1131130187273 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Not that these two issues are directly dependent on one another, but will that mean that people who use Eclipse for the development environments, would be able to integrate the "OSGi enable components" with the new Equinoxproject? Cheers, -Lyndon- On 11/4/05, Enrique Rodriguez wrote: > > Alex Karasulu wrote: > > John E. Conlon wrote: > > > >> Did not see any reference to OSGi in the Directory RoadMap at > >> http://docs.safehaus.org/pages/viewpage.action?pageId=3D2394 > >> > >> Can anyone shed some light on the current idea for when/if the > Directory > >> will support OSGi container? Previous dev traffic (i.e. - Another > >> release (0.9.2) before we introduce OSGi) gave the impression it would > >> be soon after the 0.9.2 ? > >> > >> > > We're going to try to get 0.9.4 out with OSGi and m2 builds. We might > > even flatten the directory structure a bunch in an eclipse like fashion > > with package names for projects. We're getting ready. I think its > > probably safe to say that OSGi will come in 0.9.4. > > John, > > The sticking point was lack of support for some key bundle building > features in Maven ... which got addressed this week with the Felix M2 > Plugin. With that hurdle cleared we have started updating directories > to follow the M2 standard layout and we'll start adding pom.xml's in > parallel to the project.xml's. > > You'll also see us break up the core into finer-grained subprojects so > we can address different use cases. For example, we have a JDK Prefs > SPI implementation in the core that will spin off and be used to provide > the OSGi Preferences Service backed by just the JNDI provider. > > Enrique > ------=_Part_3177_30155631.1131130187273 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Not that these two issues are directly dependent on one another, but will that mean that people who use Eclipse for the development environments, would be able to integrate the "OSGi enable components&q= uot; with the new Equinox projec= t?

Cheers,
-Lyndon-

On 11/4/05, Enrique Rodriguez <enriqu= er9@gmail.com> wrote:
Alex Karasulu wrote:
> John E. Conlon wrote:
>
>> Did = not see any reference to OSGi in the Directory RoadMap at
>> http://= docs.safehaus.org/pages/viewpage.action?pageId=3D2394
>>
>> Can anyone shed some light on the current idea= for when/if the Directory
>> will support OSGi container? &n= bsp;Previous dev traffic (i.e. - Another
>> release (0.9.2) before= we introduce OSGi) gave the impression it would
>> be soon after the 0.9.2 ?
>>
>>
> We'r= e going to try to get 0.9.4 out with OSGi and m2 builds.  We migh= t
> even flatten the directory structure a bunch in an eclipse like f= ashion
> with package names for projects.  We're getting ready.&n= bsp; I think its
> probably safe to say that OSGi will come in 0= .9.4.

John,

The sticking point was lack of support for some k= ey bundle building
features in Maven ... which got addressed this week with the Felix M2Plugin.  With that hurdle cleared we have started updating dire= ctories
to follow the M2 standard layout and we'll start adding pom.xml'= s in
parallel to the project.xml's.

You'll also see us break up the core = into finer-grained subprojects so
we can address different use cases.&nb= sp; For example, we have a JDK Prefs
SPI implementation in the core= that will spin off and be used to provide
the OSGi Preferences Service backed by just the JNDI provider.

E= nrique



------=_Part_3177_30155631.1131130187273--