You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Colbert Philippe (Jira)" <ji...@apache.org> on 2019/12/11 19:05:00 UTC
[jira] [Comment Edited] (MCOMPILER-406) Problem trying to use
old-style JARs along with JIGSAW modules!
[ https://issues.apache.org/jira/browse/MCOMPILER-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993828#comment-16993828 ]
Colbert Philippe edited comment on MCOMPILER-406 at 12/11/19 7:04 PM:
----------------------------------------------------------------------
Thanks for the informative reply. I had maven generate detailed traces with the "-eX" flag. I could see that dependencies are sorted out the way you mentioned. Your reply confirmed my observations.
However, when I put all my dependencies the way you mentioned, the old-style JAR libraries are NOT visible by the compiler. I get the message package x.y.z is not visible. The modules are visible though. Do you have any idea what I can do to resolve this?
was (Author: cp10000):
Thanks for the informative reply. I had maven generate detailed traces with the "-eX" flag. I could see that dependencies are sorted out the way you mentioned. You reply confirmed my observations.
However, when I put all my dependencies the way you mentioned, the old-style JAR libraries are NOT visible by the compiler. I get the message package x.y.z is not visible. The modules are visible though. Do you have any idea what I can do to resolve this?
> 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)