As of now, every dependency (module/jar file) is placed in the module path. However, some legacy libraries are not yet compatible with the module system, and for these cases it would be easiest to leave them on the classpath (for example, if a jar file does not provide an automatic module name but it's file name is invalid for the module system). Could you please provide an option to specify a list of dependencies that should stay on the classpath.
tlinkowski
commented
5 years ago
As of now, every dependency (module/jar file) is placed in the module path. However, some legacy libraries are not yet compatible with the module system, and for these cases it would be easiest to leave them on the classpath (for example, if a jar file does not provide an automatic module name but it's file name is invalid for the module system). Could you please provide an option to specify a list of dependencies that should stay on the classpath.
I think the code related is the following: https://github.com/java9-modularity/gradle-modules-plugin/blob/227b4f74ab03df4bf0d185936babbfa0b846e35e/src/main/java/org/javamodularity/moduleplugin/tasks/RunTaskMutator.java#L125-L127