Hi Sameera, +1 for use Equniox Luna as C5 OSGi framework, Yes considering the C5 release schedule with Luna, we can't hold our works that far.
BTW I will play little bit with Equinox kepler framework hooks implementation to get an idea on how could we achive osgi level multi tenancy in C5. That will be a good background knowledge when we migrate to Equinox Luna. Thanks, Shameera. On Sun, Jan 12, 2014 at 6:30 PM, Sameera Jayasoma <[email protected]> wrote: > Hi Shameera, > > Looks like Equinox Luna is a complete revamp of the existing Equinox code > base to fix the core issues in Equinox. This is just like implementing C5 > to overcome the architectural issues in C4. > > We should consider Luna as the OSGi framework implementation for C5. But > my only concern is the Luna release schedule[1]. It does not align with the > C5 plan as of now. The scheduled release date of Luna is June 25th, 2014. > > I guess we should continue with Kepler for the moment. As Tom explained > there will not be any impact to the APIs except for the hooks which we are > yet to use. Once Luna is in a releasable state we should go for it. > > Thanks, > Sameera. > > [1] https://projects.eclipse.org/projects/rt.equinox/releases/4.4.0 > > > On Sun, Jan 12, 2014 at 11:49 AM, Shameera Rathnayaka > <[email protected]>wrote: > >> Hi devs, >> >> One of our major expectation with new Carbon 5 release is, use new >> technologies which will last for another 10 years. Hence we are using newly >> released version of equinox which is equinox kepler. But according to >> equinox team, with next major release which is equinox Luna , they are >> going to redesign the framework and core[1]. >> >> As we are planing to provide OSGi level multi-tenancy, which can be >> implement with framework hooks going to be completely changed with >> suggested framework redesign process. Not only the framework hooks there >> are few more areas will be change with Luna release. There are few >> limitations plus drawbacks in existing framework implementation. Tom Watson >> have explained the background reason for this new redesigning >> requirement[2]. >> >> If we go with kepler and migrate to Luna once it released , we need to >> put the exact same effort again to adopt to new framework changes. >> >> According to me once the Equnox Luna released kepler will be outdated >> equinox implantations. I would like to know your thoughts on what is the >> best way to deal with this new equinox famework redesign. >> >> [1] http://wiki.eclipse.org/Equinox/Luna_Framework >> [2] >> http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/EclipseCon%202013%20-%20Equinox_0.pdf >> >> >> >> >> * Thanks, Shameera.Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com <[email protected]> , shameera AT apache.org >> <[email protected]>* >> *phone: +9471 922 1454 <%2B9471%20922%201454>* >> >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > Sameera Jayasoma, > Architect, > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
