ecated. I
>> would
>> > not want to deprecate a spec'ed API method that takes non-deprecated
>> types.
>> > Anyway, the discussion is happening now in the expert group.
>> >
>> > Tom
>> >
>> >
>> >
>> >
>> > -
ypes.
> > Anyway, the discussion is happening now in the expert group.
> >
> > Tom
> >
> >
> >
> >
> > - Original message -
> > From: Lars Vogel mailto:lars.vo...@vogella.com>>
> > Sent by: equinox-dev-boun...@eclipse.org
>
non-deprecated
> types.
> > Anyway, the discussion is happening now in the expert group.
> >
> > Tom
> >
> >
> >
> >
> > - Original message -
> > From: Lars Vogel
> > Sent by: equinox-dev-boun...@eclipse.org
> > To: Eq
happening now in the expert group.
>
> Tom
>
>
>
>
> - Original message -
> From: Lars Vogel
> Sent by: equinox-dev-boun...@eclipse.org
> To: Equinox development mailing list
> Cc:
> Subject: [equinox-dev] Provide new OSGi service API without obsolete AP
...@eclipse.orgTo: Equinox development mailing list Cc:Subject: [equinox-dev] Provide new OSGi service API without obsolete API (Dictionary)?Date: Fri, Jun 29, 2018 2:35 AMĀ
Hi,I wanted to give official feedback that my customers are surprisedthat OSGi service API is based on obsolete data types.From
Hi,
I wanted to give official feedback that my customers are surprised
that OSGi service API is based on obsolete data types.
From the Javadoc of Dictionary:
NOTE: This class is obsolete.
This makes the OSGi service API look outdated for several of the
customers I discussed this. OSGi