Return-Path: Delivered-To: apmail-incubator-aries-dev-archive@minotaur.apache.org Received: (qmail 5815 invoked from network); 24 Nov 2009 16:43:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Nov 2009 16:43:10 -0000 Received: (qmail 11576 invoked by uid 500); 24 Nov 2009 16:43:10 -0000 Delivered-To: apmail-incubator-aries-dev-archive@incubator.apache.org Received: (qmail 11481 invoked by uid 500); 24 Nov 2009 16:43:10 -0000 Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: aries-dev@incubator.apache.org Delivered-To: mailing list aries-dev@incubator.apache.org Received: (qmail 11471 invoked by uid 99); 24 Nov 2009 16:43:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2009 16:43:09 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of linsun.unc@gmail.com designates 209.85.220.216 as permitted sender) Received: from [209.85.220.216] (HELO mail-fx0-f216.google.com) (209.85.220.216) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2009 16:43:06 +0000 Received: by fxm8 with SMTP id 8so7057523fxm.27 for ; Tue, 24 Nov 2009 08:42:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=99Dt5Y44yslhc0S2xo98TJDF1EvGIIxlsdnb9sEyR1g=; b=gFt36fRbwVQ9HDbHDETvcVz+SVnnr39L2QIUcCDMjqtAk3BqC1oguai/3coX+JzwJA cXBg7NgImnldTWTeRfbn/Xob051AckhUm0g8Y5U2Epugx2K1T2/XsrwOoYRI7O1J/7be OFFk8UusAluenTcoH4RCs20GAwKR/eKKgwgus= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=IV9LGBa1Xp6lnNYik1PFI4A9IB0qEHf7C3QvmcSNIpibC+ZdBy2wMMncT8dGbt4f3K VZaMx1oM3odkM5PvMQLNhb9o98wqbwrgCv0D1ih4ue9nIgMVnsbjN1g9b6IHweY0GuQM 6YAbGqW4hIsk0nsGFYznQKd95087yKhMeH5go= MIME-Version: 1.0 Received: by 10.223.14.140 with SMTP id g12mr913978faa.50.1259080965356; Tue, 24 Nov 2009 08:42:45 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Nov 2009 11:42:45 -0500 Message-ID: Subject: Re: pick up latest org.osgi.core & org.osgi.compendium? From: Lin Sun To: aries-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, I went ahead and updated that Lin On Tue, Nov 24, 2009 at 10:54 AM, Alan Keane wrote: > Hi, > > JMX also has a dependency on 4.2.. (Framework version 1.5) > The JMX API defines static versioned ObjectNames for the MBeans > > /Alan > > On Tue, Nov 24, 2009 at 3:11 PM, Lin Sun wrote: > >> Ok cool, I'll make the change for blueprint only for now. Thanks >> >> Lin >> >> On Tue, Nov 24, 2009 at 10:05 AM, Guillaume Nodet >> wrote: >> > For blueprint, there's no real question because the blueprint api >> > already depends on 4.2 ... >> > >> > On Tue, Nov 24, 2009 at 15:52, Lin Sun wrote: >> >> Yes i'd agree with that too, if they can upgrade their framework. >> >> The question is if they decide to stay with their old version of osgi >> >> framework, do we want to support them? >> >> >> >> Lin >> >> >> >> On Tue, Nov 24, 2009 at 12:06 AM, Rex Wang wrote: >> >>> Because of the backward-compatible of osgi framework, If people uses an >> >>> older framework, it should be smooth to update the framework from 4.0, >> 4.1 >> >>> to the new version. I think we should not bind ourselves to go forward. >> >>> >> >>> -Rex >> >>> >> >>> 2009/11/24 Lin Sun >> >>> >> >>>> I wonder if we have to live with that prob, otherwise, we won't be >> >>>> able to use the latest stuff from the core or compendium, such as the >> >>>> BundleTracker util. >> >>>> >> >>>> Lin >> >>>> >> >>>> On Mon, Nov 23, 2009 at 4:26 PM, Guillaume Nodet >> wrote: >> >>>> > I agree to use the osgi artifacts instead of the felix onesm but i'm >> >>>> > not sure about using only 4.2 >> >>>> > If we do that, people using an older framework won't be able to >> >>>> > consume aries components... >> >>>> > >> >>>> > On Mon, Nov 23, 2009 at 22:18, Lin Sun >> wrote: >> >>>> >> Hi, >> >>>> >> >> >>>> >> I found out that we have a couple of places pull in different level >> of >> >>>> >> osgi core or compendium from different sources. For example, >> >>>> >> >> >>>> >> blueprint is using the org.osgi.core 1.4.2 & org.osgi.compendium >> v1.2 >> >>>> >> from apache Felix >> >>>> >> transaction is using org.osgi.core v4.1 and org.osgi.compendium >> v4.1 >> >>>> >> from org.osgi >> >>>> >> application is using org.osgi.core v4.2 from org.osgi >> >>>> >> jmx is using the org.osgi.core 1.4.2 & org.osgi.compendium v1.2 >> from >> >>>> >> apache Felix >> >>>> >> >> >>>> >> I'd like to update to the latest version of core and compendium. >> How >> >>>> >> about we use the following from the org.osgi which is avail at >> >>>> >> http://repo1.maven.org/maven2/org/osgi/ to be consistent? >> >>>> >> >> >>>> >> >> >>>> >> org.osgi >> >>>> >> org.osgi.core >> >>>> >> 4.2.0 >> >>>> >> >> >>>> >> >> >>>> >> org.osgi >> >>>> >> org.osgi.compendium >> >>>> >> 4.2.0 >> >>>> >> >> >>>> >> >> >>>> >> Please let me know if you have any objection in the next day or >> two. >> >>>> Thanks >> >>>> >> >> >>>> >> Lin >> >>>> >> >> >>>> > >> >>>> > >> >>>> > >> >>>> > -- >> >>>> > Cheers, >> >>>> > Guillaume Nodet >> >>>> > ------------------------ >> >>>> > Blog: http://gnodet.blogspot.com/ >> >>>> > ------------------------ >> >>>> > Open Source SOA >> >>>> > http://fusesource.com >> >>>> > >> >>>> >> >>> >> >> >> > >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > ------------------------ >> > Blog: http://gnodet.blogspot.com/ >> > ------------------------ >> > Open Source SOA >> > http://fusesource.com >> > >> >