Going to be a lot of work in order to get HarvesterDroid to work with JDK 9... The dependency graph was a nightmare and there's a ton of dependencies that aren't really needed and should be only done at compile time instead of runtime. The entirety of HarvesterDroid will basically need to be created from the ground up. Thankfully because of MvvmFX being used, it won't be relatively difficult, just the main business logic needs to be split out and rewritten. The problematic class is Launcher and how it's using DI which is trying to use now internal JDK modules. I think this is remnants from when HD was using Mongo or ObjectDB. Due to a need to refactor how trackers and resources are handled in order to work with multiple versions of SWG, the best approach is a creation from the ground up instead of fixing errors as I go like I've been doing.
Going to be a lot of work in order to get HarvesterDroid to work with JDK 9... The dependency graph was a nightmare and there's a ton of dependencies that aren't really needed and should be only done at compile time instead of runtime. The entirety of HarvesterDroid will basically need to be created from the ground up. Thankfully because of MvvmFX being used, it won't be relatively difficult, just the main business logic needs to be split out and rewritten. The problematic class is Launcher and how it's using DI which is trying to use now internal JDK modules. I think this is remnants from when HD was using Mongo or ObjectDB. Due to a need to refactor how trackers and resources are handled in order to work with multiple versions of SWG, the best approach is a creation from the ground up instead of fixing errors as I go like I've been doing.