Add option to populate module path with all maven dependencies
See original GitHub issueThis issue is close to Issue 89.
If I understand well, the javafx-maven-plugin reconstructs the module graph from the module-infos and populated the module path only with the required
modules. That’s a good behaviour in the majority of cases.
But if the application needs modules that are determined dynamically by maven dependency system and cannot be added statically in module-info, this doesn’t work. We would need to add all maven dependencies to the module path and use, e.g, the special --add-modules ALL-MODULE-PATH
command line argument.
This concerns both run and jlink goals.
Could you consider adding this option ?
EDIT: The Apache maven-jlink-plugin
has this option (but not the one that reads the module-info). Unfortunately the development of this plugin seems to have stopped.
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (1 by maintainers)
Top GitHub Comments
Sorry for this late answer. Forget my last message: the
compile
scope should be included in the runtime path, and it is. I forgot it was the default scope and it means runtime too.Hi @HGuillemet ,
Do you need a scope which can be used at compile time but not to be used during runtime?