Hi, I went ahead and updated that Lin
On Tue, Nov 24, 2009 at 10:54 AM, Alan Keane <[email protected]> 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 <[email protected]> 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 <[email protected]> >> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> >> >>> >> >>>> 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 <[email protected]> >> 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 <[email protected]> >> 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? >> >>>> >> >> >>>> >> <dependency> >> >>>> >> <groupId>org.osgi</groupId> >> >>>> >> <artifactId>org.osgi.core</artifactId> >> >>>> >> <version>4.2.0</version> >> >>>> >> </dependency> >> >>>> >> <dependency> >> >>>> >> <groupId>org.osgi</groupId> >> >>>> >> <artifactId>org.osgi.compendium</artifactId> >> >>>> >> <version>4.2.0</version> >> >>>> >> </dependency> >> >>>> >> >> >>>> >> 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 >> > >> >
