[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ecf-dev] target platform for Photon, ECF support of OSGi R7 RS
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Fri, 9 Mar 2018 10:19:38 -0800
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
Some context:Â ECF is currently using Neon as our target platform.ÂÂÂ
The eventual question below is:Â Should this be changed to use/require
Oxygen for ECF Photon?
Why would this be useful for ECF RS consumers? Â Well, as you probably
know in R6 ECF has a spec-compliant impl of OSGi Remote Services (chap
100) and Remote Service Admin (chap 122).
For R7 (which is just being finalized now...they are at final draft form
of R7 spec), some new use of intents has been added in the Remote
Services spec for supporting async services.ÂÂ What this means for us is
that if we want to support R7 , we have to include a reference to the
org.osgi.promise.Promise class...present in Oxygen, but does not seem to
be in Neon (I'm trying to determine when it was introduced in Equinox).
This only affects ECF RS/RSA...i.e. ECF filetransfer will still support
back to Neon.
Would anyone have objections to moving the ECF build target to
oxygen...rather than neon?ÂÂ I already have an ecf-oxygen.target in the
releng.target project and have been using it myself locally.
If we move to Oxygen as target this will mean that ECF RS will require
at least R6 for OSGi (Equinox or Felix).Â Actually ECF RS can support
older versions of OSGi framework, but it will require some additional
work (using an older version of one bundle).
I'm inclined to move to Oxygen for our Photon release.Â Please speak
soon if this creates problems.