[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?
|
What does it mean to deprecate "the API
package org.eclipse.osgi.service.resolver"? Does that affect the
use of things like org.eclipse.osgi.service.resolver.VersionRange,
org.eclipse.osgi.service.resolver.BundleDescription, and other
things in that package? These things are needed for stuff like
org.eclipse.pde.core.plugin.PluginRegistry.findModel(String, VersionRange,
PluginFilter) and
org.eclipse.pde.core.plugin.IPluginModelBase.getBundleDescription()
so surely there is not a suggestion here to deprecate these things
too?!
On 08.01.2021 15:40, Thomas Watson
wrote:
I would be in favor of deprecating the API
package org.eclipse.osgi.service.resolver which is contained
in the Equinox Framework (org.eclipse.osgi). The framework
fragment called org.eclipse.osgi.compatibility.state holds the
actual implementation, which is internal. But anything
needing to get an instance of the implementation should be
using the StateObjectFactory API to do so (See
org.eclipse.osgi.service.resolver.StateObjectFactory.defaultFactory)
Tom
----- Original message -----
From: Mickael Istria <mistria@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
To: Equinox development mailing list
<equinox-dev@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] [equinox-dev] Marking
org.eclipse.osgi.compatibility.state APIs as deprecated?
Date: Fri, Jan 8, 2021 3:47 AM
Hello,
If yes, should we mark them all as @Deprecated with
hints about which API should be used instead? I guess if
this was done, it would hint consumers to progressively
adopt newer/better APIs.
What do you think?
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/equinox-dev