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.Dismiss alert
The SwingScheduler and SwtScheduler adapters don't seem to have much traction, as far as we're aware.
The SWT one is using outdated SWT libraries and complexifies the build infrastructure for little gain.
(for instance, searching for reactor.swing.SwingScheduler results in 2 code hits in all of GitHub. The other one gets 3 hits total...)
Deprecation and removal plan
Deprecation in 3.4.7 (estimated early March 2022)
Removal in 3.6.0 (no planned date, probably late 2023 or late 2024) 2. Removal in 3.5.0 (estimated last quarter of 2022) (see comment below)
A have a client using the SWTScheduler but we copied the scheduler over to our code base to compile against the right SWT libraries, so removal in this project would be fine for us.
Note: despite the low criticality of these adapters, we might want to avoid making any exceptions to our deprecation policy, so technically this would be removable in 3.6.0 at the earliest (and we definitely won't keep it past that).
simonbasle
changed the title
Deprecating reactor-extra's Swing/SwtScheduler (removal in 3.5.0)
Deprecating reactor-extra's Swing/SwtScheduler (removal in 3.6.0)
Mar 11, 2022
This commit marks the SWT extension as deprecated, mirroring the
deprecation in reactor-extra (see reactor/reactor-addons#273).
Unlike in addons where the code is a bit more involved, the extension
is a single line of code. It adds some complexity to the build to
select the SWT variant, and adds a dependency (which is a bit dated).
As a result, exceptionally, we are going to remove it in 1.2.0 instead
of 1.3.0. Any dependency to SWT would also be removed from this project
at that point.
Fixes#38.
simonbasle
added a commit
to reactor/reactor-core
that referenced
this issue
Mar 11, 2022
Motivation
The
SwingScheduler
andSwtScheduler
adapters don't seem to have much traction, as far as we're aware.The SWT one is using outdated SWT libraries and complexifies the build infrastructure for little gain.
(for instance, searching for
reactor.swing.SwingScheduler
results in 2 code hits in all of GitHub. The other one gets 3 hits total...)Deprecation and removal plan
2. Removal in 3.5.0 (estimated last quarter of 2022)(see comment below)Additional steps
SwtScheduler
in all of GitHub btw) => [guide] Remove ref to Swing/SwtScheduler in addons appendix reactor-core#2959reactor-kotlin-extensions
=> Deprecate Swing/Swt extentions since deprecated in reactor-extra reactor-kotlin-extensions#38reactor-kotlin-extensions
1.2.0 (see also Deprecate Swing/Swt extentions since deprecated in reactor-extra reactor-kotlin-extensions#38)The text was updated successfully, but these errors were encountered: