You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
GMF Runtime uses some of these, so must be adapted.
From a quick read of the comments on bug #546820, it seems that the replacements have only been complete starting from around 2020-06 (not sure yet). Depending on how GMF Runtime uses these classes, if we want to be compatible with 2022-09 where these will no longer be available, it might mean we need to drop support for platforms older than ~2020-06 (so that we can use the alternatives).
The text was updated successfully, but these errors were encountered:
As part of #6, support for platforms older than 2020-09 have been removed.
It seems that platforms supported in the upcoming version 1.15.0 now include complete replacements for the deprecated APIs, so if this is confirmed (and if time permits) this could be included in 1.15.0.
Starting in 2019, the Eclipse Platform has marked several databinding classes as deprecated for removal. See #546820 and the migration guide.
This includes:
org.eclipse.jface.databinding.viewers.ViewersObservablesorg.eclipse.jface.databinding.swt.SWTObservablesorg.eclipse.core.databinding.beans.BeansObservablesorg.eclipse.core.databinding.beans.PojoObservablesorg.eclipse.ui.databinding.WorkbenchObservablesThey will be completely removed in 2022-09.
GMF Runtime uses some of these, so must be adapted.
From a quick read of the comments on bug #546820, it seems that the replacements have only been complete starting from around 2020-06 (not sure yet). Depending on how GMF Runtime uses these classes, if we want to be compatible with 2022-09 where these will no longer be available, it might mean we need to drop support for platforms older than ~2020-06 (so that we can use the alternatives).
The text was updated successfully, but these errors were encountered: