It would be nice to have litiengine be a modular jar:
- It allows consumers of the library to bundle their game using jpackage
- Currently the utiLITI executable created by jpackage isn't fully self contained (as it's not a modular jar)
i.e. on windows the /app directory is also necessary as it contains all dependencies. For fully modular projects
it's possible to package all dependencies in the resulting jar making it portable.
As the engine is already build using a newer java version (>= Java 9) being compliant with the module system shouldn't be a big problem ... except:
jinput isn't modular (this isn't a big problem as it can be used as an automatic module without much headache)- Most of the
soudlib.* dependencies behave have split packages (i.e. multiple jars contain the same packages or even the same classes). This is really unfortunate as it is a hard blocker for going modular. A possible workaround would be to fork the repository and modify the build process to produce compatible jars.
Any thoughts on this?
It would be nice to have litiengine be a modular jar:
i.e. on windows the
/appdirectory is also necessary as it contains all dependencies. For fully modular projectsit's possible to package all dependencies in the resulting jar making it portable.
As the engine is already build using a newer java version (>= Java 9) being compliant with the module system shouldn't be a big problem ... except:
jinputisn't modular (this isn't a big problem as it can be used as an automatic module without much headache)soudlib.*dependencies behave have split packages (i.e. multiple jars contain the same packages or even the same classes). This is really unfortunate as it is a hard blocker for going modular. A possible workaround would be to fork the repository and modify the build process to produce compatible jars.Any thoughts on this?