Closed philippTheCat closed 11 months ago
Some of this looks fixable (Change map keys from String to Type or Class). Some of this is JDK 11+ (ReentrantLock, System.Logger).
So we could get closer but then it looks like some things would need to be removed? maintain a fork? Other option?
It could be that you might be interested in using Dagger2 instead? That would mean no lifecycle support & no component testing support but might be closer to what this app needs?
Other option
a pattern I see quite often in the GDX world is that there is usually a central library, and then additional libraries that are backend specific (see here for example: https://github.com/xpenatan/gdx-imgui). Many Libraries also have ios/android specific backends, but these are usually for native libraries and I expect you wouldnt need these
I am aware of dagger2, but I was hoping to use avaje specifically for the lifecycle support, but I think I dont really need it actually So I am gonna give that a go.
Tried to give it a go, but too much stuff is missing from these runtimes to get this to work without a significant rewrite of the core API.
GWT and TeaVM have quite a limited reflection ability at runtime. This led me to want to switch from Spring-context to avaje.
While Avaje seems to not use reflection per say at runtime it still uses some classes from the java.reflect namespace that are unavailable.
Here are the errors I receive: