maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <rfscho...@apache.org>
Subject Re: maven-compiler-plugin JPMS module resolution
Date Tue, 10 Apr 2018 18:55:01 GMT
Hi

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]

thanks
Robert

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

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

> Hi,
>
> 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
> modules.
>
> Is there any way I can force placement non-modularized dependencies on
> module path?
>
>
> Thank you,
> Roman

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


Mime
View raw message