[jira] [Commented] (MCOMPILER-406) Problem trying to use old-style JARs along with JIGSAW modules!

["Robert Scholte (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MCOMPILER-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993732#comment-16993732 ] 

Robert Scholte commented on MCOMPILER-406:
------------------------------------------

The plugin does support both modulepath and classpath, and there are integration-tests that confirm that it works. 
To make it work you need to do the following:
1. upgrade the maven-compiler-plugin to 3.8.1
2. create {{src/main/java/module-info.java}}

If you can provide a project that demonstrates your issue, we're able to help.

> Problem trying to use old-style JARs along with JIGSAW modules!
> ---------------------------------------------------------------
>
>                 Key: MCOMPILER-406
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-406
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.8.1
>            Reporter: Colbert Philippe
>            Priority: Major
>
> I'm a senior programmer in Java.   I've used Maven for over 10 years and also used ANT before that.    I'm currently have major problems working with JIGSAW module system and the problem boils down to your maven-compiler-plugin.
> JIGSAWN designers say that both the old CLASSPATH and the new MODULEPATH concepts can be used at the same time, in the same compilation.   And it makes sense that they be used at the same time.   There is a huge amount of Java libraries out there in Maven Repository that are used throughout previous projects.   These older libraries will go in the CLASSPATH.   Newer modules with go in the MODULEPATH.
> So where it the problem?   Your plugin should also support both CLASSPATH and MODULEPATH simultaneously.   That's the solution!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)