[equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as depre

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Fri, 8 Jan 2021 10:46:39 +0100
Delivered-to: equinox-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/equinox-dev>
List-help: <mailto:equinox-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=unsubscribe>

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

Follow-Ups:
- Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?
  - From: Mickael Istria
- Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?
  - From: Thomas Watson
- Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?
  - From: Mickael Istria

Prev by Date: [equinox-dev] Master Open
Next by Date: Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?
Previous by thread: [equinox-dev] Master Open
Next by thread: Re: [equinox-dev] Marking org.eclipse.osgi.compatibility.state APIs as deprecated?
Index(es):
- Date
- Thread

Breadcrumbs