Describe the problem
Most of the effort in running the JAR file comes from the several --add-opens options required to make JPMS happy. If users didn't have to do this, it would be a much more friendly option for running MapTool.
The improvement you'd like to see
I'm not sure which approach is most achievable, but something along the lines of one of these options:
- Change our release JAR to be modular. How this could interact with the shadow JAR I don't know. And maybe not all our dependencies will like to be in a modular build.
- Change the JAR main class to act as a shim, forking a separate process with the necessary
--add-opens provided.
Expected Benefits
Users will be able to run our JAR without having to worry about the implementation detail of how modular we are.
Additional Context
No response
Describe the problem
Most of the effort in running the JAR file comes from the several
--add-opensoptions required to make JPMS happy. If users didn't have to do this, it would be a much more friendly option for running MapTool.The improvement you'd like to see
I'm not sure which approach is most achievable, but something along the lines of one of these options:
--add-opensprovided.Expected Benefits
Users will be able to run our JAR without having to worry about the implementation detail of how modular we are.
Additional Context
No response