Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as d

["Thomas Watson" <tjwatson@xxxxxxxxxx>]

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,

 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=570189 and https://git.eclipse.org/r/c/platform/eclipse.platform.releng.aggregator/+/174392 have revealed some bug in org.eclipse.osgi.compatibility.state. What's the status of the APIs in there? Are they actually deprecated and should be replaced with others whever possible?

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?

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/equinox-dev