Yes, I'm completely mad.
Yes, I know about Wakefield, and Caciocavallo, both have been in progress(ish) for years... nothing has arrived in mainline JDK that fixes the internal JDK bugs that prevent a proper Wayland AWT Toolkit. There is a horrid fix which uses reflection to monkey about inside the JDK, and needs many command line switches to circumvent security controls...
Yes, I know about XWayland - it's horribly broken for Swing applications (try one!) and is intended as a stop gap, not a long term solution.
By re-using the interfaces of Swing, and providing completely new implementations that lean on Wayland and maybe a component toolkit..
Presently, we build a new module / package com.ashbysoft.swingland, so client code will have to adjust imports to use us - this is by design
and also avoids horrible pain in replacing a system module (java.desktop) which is apparantly impossible without rebuilding the whole JDK..
I've chosen to use Ant as it provides just enough build tooling, is self contained, plus I know how to drive it.
Build/clean:
% ant [clean|compile] [...]
.....Test:
% ant [test-wayland|test-swingland|test]
.....where the test-wayland target directly creates a Wayland window on screen, fills it with random dots for a few seconds and terminates.
The test-swingland target runs a Swing GUI application that extends a JComponent and draws stuff in the paintComponent() method.
test-swingland also demonstrates a simple pop up Dialog (AWT flavour), with a JLabel and JButton in... more to come as I write it!
The test target runs both tests.
See LICENCE.md