0.2.3-SNAPSHOT

Moves to GEB 0.5.4 and fixes the dispatcher registration it needs. No breaking changes to the signal API.

Fixed

• SignalBus now registers the dispatcher for its own events on the GEB bus it uses. It used to rely on GEB finding a generated dispatcher by itself, and GEB 0.5.4 does not: a new GEB registers no dispatchers and drops events that have none without any warning, so no signal reached a listener.
• The "GEB Direct Use" example in the README could not work on that GEB either, because nothing registered the dispatcher of the plugin's own listener. It now shows the registration step.

Added

• GebBridge.registerDispatcher, unregisterDispatcher and loadAndRegisterDispatchers(ClassLoader). The last one reads the service file GEB's annotation processor writes into a plugin's jar, so a plugin with its own @Listen methods registers its dispatchers with one call.
• 6 new signals-core tests (48 in total, was 42): a SignalBus on a plain GEB, sub-bus forwarding, events without a dispatcher being dropped (kept as a canary for GEB upgrades), registering and unregistering a dispatcher, loading dispatchers from a class loader's service file, and null checks.

Changed

• GEB core 0.5.0 is now 0.5.4, and the README points plugins at the annotation processor 0.4.9.
• signals-core no longer uses GEB's annotation processor. SignalEnvelopeDispatcher is written by hand, which is what the processor would have generated, and SignalBus registers it. The module needs no annotation processing and does not depend on a service file being visible to a particular class loader.
• Version is now 0.2.3-SNAPSHOT.