every jar that matches a "requires"-entry of your projects module descriptor and all jars that matches the indirect requirements will be added to the module-path. The rest will stay on the classpath. If you want to do more, you need to verify the JPMS options available for java/javac[1]


[1] https://docs.oracle.com/javase/9/tools/javac.htm#JSWOR627

On Tue, 10 Apr 2018 16:23:10 +0200, Roman Grigoriadi <roman.grigori...@gmail.com> wrote:


I would like to place some of the project dependencies to --module-path to
make them automatic "derived name" modules during project compilation. I
can see that maven-compiler-plugin:3.7.0 tries to find module-info.class
and Automatic-Module-Name entry in MANIFEST. If found it uses those jars as

Is there any way I can force placement non-modularized dependencies on
module path?

Thank you,

To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to