Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rt-pmc] ECF 3.9.0

On 7/24/2014 8:01 AM, Wayne Beaton wrote:
> I'm curious. If ECF has no dependency on this library, then why even
bring it up?

ECF has a dependency on this library.   It is classes from
org.osgi.service.remoteserviceadmin package, which are the classes defined
by the RSA specification (chap 122).  It's the specified/standardized API
for RSA.

ECF's implementation of RSA *must* depend upon these classes in order to
be an impl of the spec.   This is analogous to Equinox's inclusio and
redistribution of org.osgi.framework.* classes, but for a non-framework
part of specification (RSA).

>
> If the library is required by Equinox and not directly
>referenced/linked/called/implemented/used/considered/whatever by ECF,
and >ECF is distributing Equinox, then >no CQ is required.

The RSA packages/classes are not required by Equinox.  There are parts of
the compendium APIs that are required by Equinox (I believe that includes
ds, httpservice, and some others, but I'm not sure), but Equinox doesn't
implement RSA, so these compendium classes are not included in Equinox.  
If they were we would indeed be using them rather than redistributing
them.

>
> No CQ required:
>
> ECF -> Equinox -> OSGi
>
> CQ required:
>
> ECF -> OSGi

Got that.   But this is a strange case, because although Thomas has been
filing the CQ's for the entire compendium [1]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=8495

Equinox doesn't actually use/redistribute RSA API, while ECF does/must.

It would probably be better if I filed the CQ directly for future versions
of RSA API, separate from the entire compendium set as Thomas currently
does.  Since I'm on the eeg now, I can do this directly, and that way I
can do it when needed specifically for ECF's impl.

Without objection, I'll plan to file a direct CT for RSA specifically for
the next time/release.

>
> We'll need to review the IP Log.
>
> If you're going to make the desired release date, then we need to get
this all together today. We need the IP Log submitted for review and
approval of the review documentation of the PMC.

I don't think I can do the IP log dance today (Thur) but I'll try.  But
because I need to find out the status of the RSA spec completion, and the
next meeting of the EEG is next Wed, I don't really think that we will be
able to release on August 1.  And  I have to figure out how the timing of
the OSGi spec completion relates to the releng work expected for
httpcomponents version bug

https://bugs.eclipse.org/bugs/show_bug.cgi?id=440265

In other words:  I don't think we are going to be able to release on
August 1 anyway because of other constraints, so please no rush.




Back to the top