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
It looks like Avaje Inject will solve some of our jlink issues -- by using jakarta.inject and being fully modular.
We should be able to create a new module that implements the FXLauncher interface using Avaje Inject. If we do that (and switch to a modular logger API) we may be able to build apps without doing the extensive reprocessing of JARs with the Badass Jlink Gradle Plugin.
The text was updated successfully, but these errors were encountered:
I tagged you mostly to make you aware I had created an issue for this.
(I'd much rather you look at integrating Supernaut.FX with Griffon, if you have any extra time. Hopefully, Supernaut.FX would provide you with a useful abstraction layer for multiple DI implementations. I'm really looking forward to hearing if you think this might work.)
It looks like Avaje Inject will solve some of our
jlink
issues -- by usingjakarta.inject
and being fully modular.We should be able to create a new module that implements the
FXLauncher
interface using Avaje Inject. If we do that (and switch to a modular logger API) we may be able to build apps without doing the extensive reprocessing of JARs with the Badass Jlink Gradle Plugin.The text was updated successfully, but these errors were encountered: