avaje-inject VS Useful-Things

Avaje Inject has quickly become one of my favorite libraries. Inject is basically like Dagger if Dagger was focused on server side instead of Android. It's a tiny lib (~76kb) that uses the power of annotation processing to generate DI classes. Recently I've been using it for AWS lambdas and it works pretty great.

https://avaje.io/inject/ - Implements JSR-330 and JSR-250

Have you tried out Avaje inject? It's currently my favorite DI lib.

Been building a web service with avaje inject and avaje http lately. It has a very spring-like feel for a DI lib, (Lifecycles, Test annotations) but the libs are tiny and totally reflection free through codegen.

Avaje is pretty cool, it's a compact DI library based on APT. https://github.com/avaje/avaje-inject

Like avaje inject ? DI as source code generation done at build time?

Just to say, I also created a DI library called avaje-inject - https://avaje.io/inject/ ... which uses Java annotation processing to do DI as mostly source code generation. So the runtime dependency is ~ 67Kb. It also supports AOP aspects via source code gen which I think is kind of cool - you can have your own aspects like `@Retry` etc and it's actually done using source code generation.

I am a bit fan of using annotation processing (source code generation) to simplify things - DI https://avaje.io/inject/ , JSON binding (https://github.com/avaje/avaje-jsonb) and rest servers and clients (https://avaje.io/http).

Dagger2 and avaje-inject are other options (DI as source code generation via annotation processing). https://avaje.io/inject/

Creating fat-jar's for maven/gradle projects each release using automated CI (Like GitHub Actions, or Jenkins)

You can refer to my example demonstrating the fix if you want a visual here: https://github.com/Col-E/Useful-Things/tree/master/tutorials/javafx/maven-setup/src/main/java/org/example

On the other side, I think you did a really good job illustrating how DI works with this document.

No, just use a normal Java template for Maven/Gradle and add JavaFX as a dependency. I have examples here: https://github.com/Col-E/Useful-Things/tree/master/tutorials/javafx

JavaFX FatJar with Maven

Using Maven, declare JavaFX as a dependency

If the steps are confusing, I have a maven empty demo project here: https://github.com/Col-E/Useful-Things/tree/master/tutorials/javafx/maven-setup

You can make a sorta kinda "Multi-platform" JavaFX jar, but only for one architecture per OS. Their dll/so/dylib path names all conflict which is infuriating.

I typically roll with a standard fatJar plugin. I made a short guide for somebody before. Is that the direction you were looking for?

Check the reddit links in this post.