You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
gradle-modules-plugin/src/main/java/org/javamodularity/moduleplugin/tasks/RunTaskMutator.java
Lines 125 to 127 in 227b4f7
The text was updated successfully, but these errors were encountered: