[jira] [Commented] (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=16993850#comment-16993850 ] Colbert Philippe commented on MCOMPILER-406: You can close this ticket. I found the description of "automatic module" on Stack Overflow. > 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 >Assignee: Robert Scholte >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)
[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=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: cp1): 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)
[jira] [Commented] (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=16993828#comment-16993828 ] Colbert Philippe commented on MCOMPILER-406: 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)
[jira] [Commented] (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=16993776#comment-16993776 ] Colbert Philippe commented on MCOMPILER-406: Can you provide an sample pom.xml that shows clearly the use of your maven-compiler-plugin using CLASSPATH and MODULE-PATH? I think many people would be looking for an example. > 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)
[jira] [Commented] (MCOMPILER-308) Compiler failure but no compiler message on the console
[
https://issues.apache.org/jira/browse/MCOMPILER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993694#comment-16993694
]
Colbert Philippe commented on MCOMPILER-308:
Look for some foreign character that might have infiltrated in your source.
It's hard to spot. The strategy I use is to recreate your souce by creating
a new copy of it. Gradually introduce new sections of the old source and test
if it compiles (or work). You can also try to submit your source to some
utilities on the Internet that test compliance with character encoding standard.
> Compiler failure but no compiler message on the console
> ---
>
> Key: MCOMPILER-308
> URL: https://issues.apache.org/jira/browse/MCOMPILER-308
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Using:
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T13:39:06-06:00)
> Maven home: C:\Java\apache-maven-3.5.0\bin\..
> Java version: 9, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> java version "9"
> Java(TM) SE Runtime Environment (build 9+181)
> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
> Steps to reproduce:
> * git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> * git checkout tags/log4j-2.9.1-rc1
> * mvn -e verify
> Will give you:
> {noformat}
> [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
> log4j-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 530 source files to
> C:\temp\rc\apache-log4j-2.9.1-src\log4j-core\target\test-classes
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 3.890
> s]
> [INFO] Apache Log4j API Java 9 support SUCCESS [ 8.330
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 37.451
> s]
> [INFO] Apache Log4j Core .. FAILURE [ 55.364
> s]
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:47 min
> [INFO] Finished at: 2017-09-18T10:00:51-06:00
> [INFO] Final Memory: 41M/137M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
>
[jira] [Created] (MCOMPILER-406) Problem trying to use old-style JARs along with JIGSAW modules!
Colbert Philippe created MCOMPILER-406: -- Summary: 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 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)
[jira] [Commented] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[
https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437203#comment-16437203
]
Colbert Philippe commented on MCOMPILER-337:
Robert, did you notice that using your maven-compiler-plugin declaration, the
compiler puts the list of jar dependencies in BOTH the classpath and the
module-path? You can view this in the detailed compiler logs.
I just want to say that the Java documentation says that the jar dependencies
should be in the module-path ONLY, not both. It still works but this is
something to look into.
Colbert
> Using old-style Jar files with Java9 Module project, Classpath and
> Module-path are mixed up!
>
>
> Key: MCOMPILER-337
> URL: https://issues.apache.org/jira/browse/MCOMPILER-337
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Colbert Philippe
>Priority: Major
> Attachments: quebec.lachine.zip
>
>
> I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
> I already contacted Maven to ask what version of Maven to use with Java 9
> module feature. They recommended the latest version: Maven 3.5.0 (latest)
> with the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using.
> I'm also using Java JDK 9.
> I want to report a problem with Maven when working with Java 9 module
> feature. It's not a big problem but it's big enough to prevent the use of
> Maven with Java 9 modules. The problem is with Maven, when used under
> Eclipse. I create Maven projects under Eclipse for speed.
> I created two identical projects with Java 9 module. The two projects make
> use of a few old-style Jar files by importing them as default module (as
> prescribed by the makers of Java 9). The jar files are: ant.jar,
> commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar,
> commons-lang3-3.7.jar.
> * The first project is a small project built from the command-line with a
> text-editor. It's a Java 9 module project (has a module-info.java) and makes
> use of these 4 libray jar files in the manner prescribed by the Java 9
> documentation. This project compiles and works. All Jar files are put the the
> module-path of the project and their respective 'requires' statement is in
> the module-info.java file. (see below)
>
> {code:java}
> module canada.ontario {
> exports canada.ontario;
> requires org.apache.commons.lang3;
> requires commons.collections4;
> requires commons.beanutils;
> }
> {code}
> *
> ** The second project is identical to the first one but is built using Maven
> (versions specified above) created under Eclipse. The project as created as
> intended based on Maven guidelines. First a parent project was created with
> packaging set with pom. The a child-project was created for the module.
> After the child-project was created, in the child-project POM file, I entered
> the full plug-in entries to use the new 'maven-compiler-plugin' version
> 3.7.0. This works because we can see its use on the compiling log display
> messages.
> On Eclipse Workspace view, I selected the parent project root (previously
> created), right clicking on the parent project, then selecting 'Maven', then
> selecting 'New Maven Module Project'. This creates a Maven child project for
> the new module.
> - I created a 'module-info.java' with the name of the module
> (canada.ontario) in the src directory.
> - I also created a package with the same name as the module (canada.ontario).
> - I entered the same 'exports' and 'requires' statements as displayed above.
> - I also entered all the Maven dependencies to each of the four (4)
> libraries stated above. I got these dependencies from the Maven repository.
> - I also enabled full compile-time log-message diplay, in order to get
> maximum information.
> HERE IS THE PROBLEM WHEN COMPILING THIS SECOND MAVEN CHILD-PROJECT!
> When compiling the second child-project for the module, there is an error. I
> have narrowed down the reason for the error.
> For some unknown reason, the Maven compiler plug-in DOES NOT put all the jar
> dependencies under the module-path. It splits the list of dependencies
> between the classpath and the module-path, WHICH IS WRONG! (see below)
> {noformat}
> [INFO] Changes detected - recompiling the module!
> [DEBUG] Classpath: <- There should be no jar under this Classpath list
> ***
> [DEBUG] C:\Users\Colbert
> Philippe\workspace\montreal\quebec.lachine\target\classes
> [DEBUG] C:\Users\Colbert
> Philippe\.m2\repository\org\apache\commons\commons-collections4\4.1\commons-collections4-4.1.jar
> [DEBUG] C:\Users\Colbert
> Philippe\.m2\repository\commons-beanutils\commons-beanutils\1.9.3\commons-beanutils-1.9.3.jar
> [DEBUG]
[jira] [Commented] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[
https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437202#comment-16437202
]
Colbert Philippe commented on MCOMPILER-337:
Robert, it finally works! The reason my build was failing is because I was
using the maven java compiler declaration from this page
[https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html]
By replacing it with your simplified declaration, it works! I am very
pleased because my company project can move forward.
Thank-You!
Colbert
> Using old-style Jar files with Java9 Module project, Classpath and
> Module-path are mixed up!
>
>
> Key: MCOMPILER-337
> URL: https://issues.apache.org/jira/browse/MCOMPILER-337
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Colbert Philippe
>Priority: Major
> Attachments: quebec.lachine.zip
>
>
> I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
> I already contacted Maven to ask what version of Maven to use with Java 9
> module feature. They recommended the latest version: Maven 3.5.0 (latest)
> with the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using.
> I'm also using Java JDK 9.
> I want to report a problem with Maven when working with Java 9 module
> feature. It's not a big problem but it's big enough to prevent the use of
> Maven with Java 9 modules. The problem is with Maven, when used under
> Eclipse. I create Maven projects under Eclipse for speed.
> I created two identical projects with Java 9 module. The two projects make
> use of a few old-style Jar files by importing them as default module (as
> prescribed by the makers of Java 9). The jar files are: ant.jar,
> commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar,
> commons-lang3-3.7.jar.
> * The first project is a small project built from the command-line with a
> text-editor. It's a Java 9 module project (has a module-info.java) and makes
> use of these 4 libray jar files in the manner prescribed by the Java 9
> documentation. This project compiles and works. All Jar files are put the the
> module-path of the project and their respective 'requires' statement is in
> the module-info.java file. (see below)
>
> {code:java}
> module canada.ontario {
> exports canada.ontario;
> requires org.apache.commons.lang3;
> requires commons.collections4;
> requires commons.beanutils;
> }
> {code}
> *
> ** The second project is identical to the first one but is built using Maven
> (versions specified above) created under Eclipse. The project as created as
> intended based on Maven guidelines. First a parent project was created with
> packaging set with pom. The a child-project was created for the module.
> After the child-project was created, in the child-project POM file, I entered
> the full plug-in entries to use the new 'maven-compiler-plugin' version
> 3.7.0. This works because we can see its use on the compiling log display
> messages.
> On Eclipse Workspace view, I selected the parent project root (previously
> created), right clicking on the parent project, then selecting 'Maven', then
> selecting 'New Maven Module Project'. This creates a Maven child project for
> the new module.
> - I created a 'module-info.java' with the name of the module
> (canada.ontario) in the src directory.
> - I also created a package with the same name as the module (canada.ontario).
> - I entered the same 'exports' and 'requires' statements as displayed above.
> - I also entered all the Maven dependencies to each of the four (4)
> libraries stated above. I got these dependencies from the Maven repository.
> - I also enabled full compile-time log-message diplay, in order to get
> maximum information.
> HERE IS THE PROBLEM WHEN COMPILING THIS SECOND MAVEN CHILD-PROJECT!
> When compiling the second child-project for the module, there is an error. I
> have narrowed down the reason for the error.
> For some unknown reason, the Maven compiler plug-in DOES NOT put all the jar
> dependencies under the module-path. It splits the list of dependencies
> between the classpath and the module-path, WHICH IS WRONG! (see below)
> {noformat}
> [INFO] Changes detected - recompiling the module!
> [DEBUG] Classpath: <- There should be no jar under this Classpath list
> ***
> [DEBUG] C:\Users\Colbert
> Philippe\workspace\montreal\quebec.lachine\target\classes
> [DEBUG] C:\Users\Colbert
> Philippe\.m2\repository\org\apache\commons\commons-collections4\4.1\commons-collections4-4.1.jar
> [DEBUG] C:\Users\Colbert
> Philippe\.m2\repository\commons-beanutils\commons-beanutils\1.9.3\commons-beanutils-1.9.3.jar
> [DEBUG] C:\Users\Colbert
>
[jira] [Commented] (MCOMPILER-336) Dependency that should be on modulepath sometime put on classpath
[
https://issues.apache.org/jira/browse/MCOMPILER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436114#comment-16436114
]
Colbert Philippe commented on MCOMPILER-336:
No XML entry 'useIncrementalCompilation' in my POM, even when I view Effective
POM using Eclipse! Since it's not there, there is nothing to delete. Can
you advise on what to do to find a good workaround?
> Dependency that should be on modulepath sometime put on classpath
> -
>
> Key: MCOMPILER-336
> URL: https://issues.apache.org/jira/browse/MCOMPILER-336
> Project: Maven Compiler Plugin
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Martin Desruisseaux
>Assignee: Robert Scholte
>Priority: Major
> Attachments: module-vs-classpath.zip
>
>
> {{maven-compiler-plugin}} sometime puts modularized dependencies on the
> {{javac}} {{-classpath}} option instead than {{-modulepath}}, which cause
> compilation failure. A test case is attached. Step to reproduce:
> {noformat}
> cd module-vs-classpath
> cd a
> mvn install
> cd ../b
> mvn clean install
> mvn install
> {noformat}
> The last command fail with the following error message:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project b: Compilation failure
> [ERROR] module not found: test.a
> {noformat}
> Execution with the {{-X}} option shows that the {{test.a}} dependency is
> correctly declared in {{-modulepath}} when executing {{mvn clean install}},
> but is wrongly declared in {{-classpath}} when executing {{mvn install}}.
> A workaround is to remove the
> {{false}} option in
> the {{pom.xml}} files, or to execute {{touch src/main/java/module-info.java}}
> before {{mvn install}}. However the same error message occurs when attempting
> to execute {{mvn site}}, for which case I have found no workaround yet (note:
> the {{mvn site}} problem is not reproduced by the attached
> {{module-vs-classpath.zip}} file).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[ https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436100#comment-16436100 ] Colbert Philippe commented on MCOMPILER-337: Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T14:49:05-05:00) Maven home: C:\Users\Colbert Philippe\workspace\montreal\quebec.lachine\EMBEDDED Java version: 9, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk-9 Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.annotation.* < plexus.core [DEBUG] Imported: javax.annotation.security.* < plexus.core [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.fusesource.jansi.* < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.helpers.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [INFO] Error stacktraces are turned on. [DEBUG] Message scheme: plain [DEBUG] Reading global settings from settings.xml [DEBUG] Reading user settings from C:\Users\Colbert
[jira] [Comment Edited] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[
https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436083#comment-16436083
]
Colbert Philippe edited comment on MCOMPILER-337 at 4/12/18 6:19 PM:
-
Hi Robert! Robert, I used Eclipse to create the entire project structure. I
didn't hand-code it! It takes too long by hand. I prefer to do it through
Eclipse. My version of Eclipse is the most recent one for Java9. It's
Eclipse 4.8M. There is another version: Eclipse 4.8M a for Java10. I think
both are very similar.
Here is how I created the project under Eclipse using Maven.
I create a new simple Java project using Maven. I make sure that it's package
is POM. That's my parent project. Within my parent project (right-click on
parent), go down the menu to Maven->Create New Maven Module, which creates a
new child-project for a module. The module-info is not in the child-project (it
should since I selected 'Create new Maven Module'). Eclipse should be doing
this automatically. I am forced to create my own module-info.java. I do
this using Eclipse menu option. Right-click
child-project->Configure->Create module-info I am also forced to create the
module package myself. Eclipse should be doing this. I populate the
module-info.java as show my original letter.
If you wish, we can do a Skype conference and do a screen-share. This might
save time narrowing down the problem.
The bottom-line is that Maven + maven-compiler-plugin is mixing-up Classpath
and module-path. That's WRONG! Only module-path should be used!
was (Author: cp1):
Hi Robert! Robert, I used Eclipse to create the entire project structure. I
didn't hand-code it! It takes too long by hand. I prefer to do it through
Eclipse. My version of Eclipse is the most recent one for Java9. It's
Eclipse 4.8M. There is another version: Eclipse 4.8M a for Java10. I think
both are very similar.
Here is how I created the project under Eclipse using Maven.
* I create a new simple Java project using Maven. I make sure that it's
package is POM. That's my parent project.
* Within my parent project (right-click on parent), go down the menu to
Maven->Create New Maven Module, which creates a new child-project for a module.
* The module-info is not in the child-project (it should since I selected
'Create new Maven Module'). Eclipse should be doing this automatically.
* I am forced to create my own module-info.java. I do this using Eclipse
menu option. Right-click child-project->Configure->Create module-info
* I am also forced to create the module package myself. Eclipse should be
doing this.
* I populate the module-info.java as show my original letter.
If you wish, we can do a Skype conference and do a screen-share. This might
save time narrowing down the problem.
The bottom-line is that Maven + maven-compiler-plugin is mixing-up Classpath
and module-path. That's WRONG! Only module-path should be used!
> Using old-style Jar files with Java9 Module project, Classpath and
> Module-path are mixed up!
>
>
> Key: MCOMPILER-337
> URL: https://issues.apache.org/jira/browse/MCOMPILER-337
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Colbert Philippe
>Priority: Major
>
> I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
> I already contacted Maven to ask what version of Maven to use with Java 9
> module feature. They recommended the latest version: Maven 3.5.0 (latest)
> with the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using.
> I'm also using Java JDK 9.
> I want to report a problem with Maven when working with Java 9 module
> feature. It's not a big problem but it's big enough to prevent the use of
> Maven with Java 9 modules. The problem is with Maven, when used under
> Eclipse. I create Maven projects under Eclipse for speed.
> I created two identical projects with Java 9 module. The two projects make
> use of a few old-style Jar files by importing them as default module (as
> prescribed by the makers of Java 9). The jar files are: ant.jar,
> commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar,
> commons-lang3-3.7.jar.
> * The first project is a small project built from the command-line with a
> text-editor. It's a Java 9 module project (has a module-info.java) and makes
> use of these 4 libray jar files in the manner prescribed by the Java 9
> documentation. This project compiles and works. All Jar files are put the the
> module-path of the project and their respective 'requires' statement is in
> the module-info.java file. (see below)
>
> {code:java}
>
[jira] [Comment Edited] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[ https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436083#comment-16436083 ] Colbert Philippe edited comment on MCOMPILER-337 at 4/12/18 6:15 PM: - Hi Robert! Robert, I used Eclipse to create the entire project structure. I didn't hand-code it! It takes too long by hand. I prefer to do it through Eclipse. My version of Eclipse is the most recent one for Java9. It's Eclipse 4.8M. There is another version: Eclipse 4.8M a for Java10. I think both are very similar. Here is how I created the project under Eclipse using Maven. * I create a new simple Java project using Maven. I make sure that it's package is POM. That's my parent project. * Within my parent project (right-click on parent), go down the menu to Maven->Create New Maven Module, which creates a new child-project for a module. * The module-info is not in the child-project (it should since I selected 'Create new Maven Module'). Eclipse should be doing this automatically. * I am forced to create my own module-info.java. I do this using Eclipse menu option. Right-click child-project->Configure->Create module-info * I am also forced to create the module package myself. Eclipse should be doing this. * I populate the module-info.java as show my original letter. If you wish, we can do a Skype conference and do a screen-share. This might save time narrowing down the problem. The bottom-line is that Maven + maven-compiler-plugin is mixing-up Classpath and module-path. That's WRONG! Only module-path should be used! was (Author: cp1): Hi Robert! Robert, I used Eclipse to create the entire project structure. I didn't hand-code it! It take too long my hand. I prefer to do it through Eclipse. My version of Eclipse is the most recent one for Java9. It's Eclipse 4.8M. There is another version: Eclipse 4.8M a for Java10. I think both are very similar. Here is how I created the project under Eclipse using Maven. * I create a new simple Java project using Maven. I make sure that it's package is POM. That's my parent project. * Within my parent project (right-click on parent), go down the menu to Maven->Create New Maven Module, which creates a new child-project for a module. * The module-info is not in the child-project (it should since I selected 'Create new Maven Module'). Eclipse should be doing this automatically. * I am forced to create my own module-info.java. I do this using Eclipse menu option. Right-click child-project->Configure->Create module-info * I am also forced to create the module package myself. Eclipse should be doing this. * I populate the module-info.java as show my original letter. If you wish, we can do a Skype conference and do a screen-share. This might save time narrowing down the problem. The bottom-line is that Maven + maven-compiler-plugin is mixing-up Classpath and module-path. That's WRONG! Only module-path should be used! > Using old-style Jar files with Java9 Module project, Classpath and > Module-path are mixed up! > > > Key: MCOMPILER-337 > URL: https://issues.apache.org/jira/browse/MCOMPILER-337 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.7.0 >Reporter: Colbert Philippe >Priority: Major > > I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module. > I already contacted Maven to ask what version of Maven to use with Java 9 > module feature. They recommended the latest version: Maven 3.5.0 (latest) > with the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using. > I'm also using Java JDK 9. > I want to report a problem with Maven when working with Java 9 module > feature. It's not a big problem but it's big enough to prevent the use of > Maven with Java 9 modules. The problem is with Maven, when used under > Eclipse. I create Maven projects under Eclipse for speed. > I created two identical projects with Java 9 module. The two projects make > use of a few old-style Jar files by importing them as default module (as > prescribed by the makers of Java 9). The jar files are: ant.jar, > commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar, > commons-lang3-3.7.jar. > * The first project is a small project built from the command-line with a > text-editor. It's a Java 9 module project (has a module-info.java) and makes > use of these 4 libray jar files in the manner prescribed by the Java 9 > documentation. This project compiles and works. All Jar files are put the the > module-path of the project and their respective 'requires' statement is in > the module-info.java file. (see below) > >
[jira] [Commented] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[
https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436083#comment-16436083
]
Colbert Philippe commented on MCOMPILER-337:
Hi Robert! Robert, I used Eclipse to create the entire project structure. I
didn't hand-code it! It take too long my hand. I prefer to do it through
Eclipse. My version of Eclipse is the most recent one for Java9. It's
Eclipse 4.8M. There is another version: Eclipse 4.8M a for Java10. I think
both are very similar.
Here is how I created the project under Eclipse using Maven.
* I create a new simple Java project using Maven. I make sure that it's
package is POM. That's my parent project.
* Within my parent project (right-click on parent), go down the menu to
Maven->Create New Maven Module, which creates a new child-project for a module.
* The module-info is not in the child-project (it should since I selected
'Create new Maven Module'). Eclipse should be doing this automatically.
* I am forced to create my own module-info.java. I do this using Eclipse
menu option. Right-click child-project->Configure->Create module-info
* I am also forced to create the module package myself. Eclipse should be
doing this.
* I populate the module-info.java as show my original letter.
If you wish, we can do a Skype conference and do a screen-share. This might
save time narrowing down the problem.
The bottom-line is that Maven + maven-compiler-plugin is mixing-up Classpath
and module-path. That's WRONG! Only module-path should be used!
> Using old-style Jar files with Java9 Module project, Classpath and
> Module-path are mixed up!
>
>
> Key: MCOMPILER-337
> URL: https://issues.apache.org/jira/browse/MCOMPILER-337
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Colbert Philippe
>Priority: Major
>
> I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
> I already contacted Maven to ask what version of Maven to use with Java 9
> module feature. They recommended the latest version: Maven 3.5.0 (latest)
> with the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using.
> I'm also using Java JDK 9.
> I want to report a problem with Maven when working with Java 9 module
> feature. It's not a big problem but it's big enough to prevent the use of
> Maven with Java 9 modules. The problem is with Maven, when used under
> Eclipse. I create Maven projects under Eclipse for speed.
> I created two identical projects with Java 9 module. The two projects make
> use of a few old-style Jar files by importing them as default module (as
> prescribed by the makers of Java 9). The jar files are: ant.jar,
> commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar,
> commons-lang3-3.7.jar.
> * The first project is a small project built from the command-line with a
> text-editor. It's a Java 9 module project (has a module-info.java) and makes
> use of these 4 libray jar files in the manner prescribed by the Java 9
> documentation. This project compiles and works. All Jar files are put the the
> module-path of the project and their respective 'requires' statement is in
> the module-info.java file. (see below)
>
> {code:java}
> module canada.ontario {
> exports canada.ontario;
> requires org.apache.commons.lang3;
> requires commons.collections4;
> requires commons.beanutils;
> }
> {code}
> *
> ** The second project is identical to the first one but is built using Maven
> (versions specified above) created under Eclipse. The project as created as
> intended based on Maven guidelines. First a parent project was created with
> packaging set with pom. The a child-project was created for the module.
> After the child-project was created, in the child-project POM file, I entered
> the full plug-in entries to use the new 'maven-compiler-plugin' version
> 3.7.0. This works because we can see its use on the compiling log display
> messages.
> On Eclipse Workspace view, I selected the parent project root (previously
> created), right clicking on the parent project, then selecting 'Maven', then
> selecting 'New Maven Module Project'. This creates a Maven child project for
> the new module.
> - I created a 'module-info.java' with the name of the module
> (canada.ontario) in the src directory.
> - I also created a package with the same name as the module (canada.ontario).
> - I entered the same 'exports' and 'requires' statements as displayed above.
> - I also entered all the Maven dependencies to each of the four (4)
> libraries stated above. I got these dependencies from the Maven repository.
> - I also enabled full compile-time log-message diplay, in order to
[jira] [Updated] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
[
https://issues.apache.org/jira/browse/MCOMPILER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colbert Philippe updated MCOMPILER-337:
---
Description:
I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
I already contacted Maven to ask what version of Maven to use with Java 9
module feature. They recommended the latest version: Maven 3.5.0 (latest) with
the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using. I'm
also using Java JDK 9.
I want to report a problem with Maven when working with Java 9 module feature.
It's not a big problem but it's big enough to prevent the use of Maven with
Java 9 modules. The problem is with Maven, when used under Eclipse. I create
Maven projects under Eclipse for speed.
I created two identical projects with Java 9 module. The two projects make use
of a few old-style Jar files by importing them as default module (as prescribed
by the makers of Java 9). The jar files are: ant.jar,
commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar,
commons-lang3-3.7.jar.
* The first project is a small project built from the command-line with a
text-editor. It's a Java 9 module project (has a module-info.java) and makes
use of these 4 libray jar files in the manner prescribed by the Java 9
documentation. This project compiles and works. All Jar files are put the the
module-path of the project and their respective 'requires' statement is in the
module-info.java file. (see below)
{code:java}
module canada.ontario {
exports canada.ontario;
requires org.apache.commons.lang3;
requires commons.collections4;
requires commons.beanutils;
}
{code}
*
** The second project is identical to the first one but is built using Maven
(versions specified above) created under Eclipse. The project as created as
intended based on Maven guidelines. First a parent project was created with
packaging set with pom. The a child-project was created for the module.
After the child-project was created, in the child-project POM file, I entered
the full plug-in entries to use the new 'maven-compiler-plugin' version 3.7.0.
This works because we can see its use on the compiling log display messages.
On Eclipse Workspace view, I selected the parent project root (previously
created), right clicking on the parent project, then selecting 'Maven', then
selecting 'New Maven Module Project'. This creates a Maven child project for
the new module.
- I created a 'module-info.java' with the name of the module (canada.ontario)
in the src directory.
- I also created a package with the same name as the module (canada.ontario).
- I entered the same 'exports' and 'requires' statements as displayed above.
- I also entered all the Maven dependencies to each of the four (4) libraries
stated above. I got these dependencies from the Maven repository.
- I also enabled full compile-time log-message diplay, in order to get maximum
information.
HERE IS THE PROBLEM WHEN COMPILING THIS SECOND MAVEN CHILD-PROJECT!
When compiling the second child-project for the module, there is an error. I
have narrowed down the reason for the error.
For some unknown reason, the Maven compiler plug-in DOES NOT put all the jar
dependencies under the module-path. It splits the list of dependencies between
the classpath and the module-path, WHICH IS WRONG! (see below)
[INFO] Changes detected - recompiling the module!
[DEBUG] Classpath: <- There should be no jar under this Classpath list ***
[DEBUG] C:\Users\Colbert
Philippe\workspace\montreal\quebec.lachine\target\classes
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\org\apache\commons\commons-collections4\4.1\commons-collections4-4.1.jar
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\commons-beanutils\commons-beanutils\1.9.3\commons-beanutils-1.9.3.jar
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\commons-logging\commons-logging\1.2\commons-logging-1.2.jar
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\commons-collections\commons-collections\3.2.2\commons-collections-3.2.2.jar
[DEBUG] Modulepath: <- All jar file dependencies should be under this
ModulePath list ***
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\org\apache\commons\commons-lang3\3.7\commons-lang3-3.7.jar
[DEBUG] Source roots:
This is the source of the error!
Since putting all the jar files under module-path works in my first
hand-created project works fine. I am certain that this is the cause of the
error.
was:
I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
I already contacted Maven to ask what version of Maven to use with Java 9
module feature. They recommended the latest version: Maven 3.5.0 (latest) with
the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using. I'm
also using Java JDK 9.
I want to report a problem with Eclipse when working with Java 9 module
feature. It's not a big
[jira] [Created] (MCOMPILER-337) Using old-style Jar files with Java9 Module project, Classpath and Module-path are mixed up!
Colbert Philippe created MCOMPILER-337:
--
Summary: Using old-style Jar files with Java9 Module project,
Classpath and Module-path are mixed up!
Key: MCOMPILER-337
URL: https://issues.apache.org/jira/browse/MCOMPILER-337
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.7.0
Reporter: Colbert Philippe
I'm trying to use Eclipse (4.8M4) with Maven to practice Java9 module.
I already contacted Maven to ask what version of Maven to use with Java 9
module feature. They recommended the latest version: Maven 3.5.0 (latest) with
the Maven plug-in: maven-compiler-plugin 3.7.0, which is what I'm using. I'm
also using Java JDK 9.
I want to report a problem with Eclipse when working with Java 9 module
feature. It's not a big problem but it's big enough to prevent the use of
Eclipse with Java 9 modules. The problem is with Eclipse, not Maven. The Maven
version that I'm using works fine! I tested it!
I created two identical projects with Java 9 module. The two projects make use
of a few old-style Jar files by importing them as default module (as prescribed
by the makers of Java 9). The jar files are: ant.jar,
commons-beanutils-1.9.3.jar, commons-collections4-4.1.jar,
commons-lang3-3.7.jar.
* The first project is a small project built from the command-line with a
text-editor. It's a Java 9 module project (has a module-info.java) and makes
use of these 4 libray jar files in the matter prescribed by the Java 9
documentation. This project compile and works. All Jar files are put the the
module-path of the project and their respective 'requires' statement is in the
module-info.java file. (see below)
module canada.ontario {
exports canada.ontario;
requires org.apache.commons.lang3;
requires commons.collections4;
requires commons.beanutils;
}
** The second project is identical to the first one but is built using Eclipse
& Maven (versions specified above). The project as created as intended with
Maven. First a parent project was created with packaging set with pom. The a
child-project was created for the module.
After the child-project was created, in the child-project POM file, I entered
the full plug-in entries to use the new 'maven-compiler-plugin' version 3.7.0.
This works because we can see its use on the compiling log display messages.
On Eclipse Workspace view, I selected the parent project root (previously
created), right clicking on the parent project, then selecting 'Maven', then
selecting 'New Maven Module Project'. This creates a Maven child project for
the new module.
- I created a 'module-info.java' with the name of the module (canada.ontario)
in the src directory.
- I also created a package with the same name as the module (canada.ontario).
- I entered the same 'exports' and 'requires' statements as displayed above.
- I also entered all the Maven dependencies to each of the four (4) libraries
stated above. I got these dependencies from the Maven repository.
- I also enabled full compile-time log-message diplay, in order to get maximum
information.
### HERE IS THE PROBLEM WHEN COMPILING THIS SECOND MAVEN CHILD-PROJECT! ###
When compiling the second child-project for the module, there is an error. I
have narrowed down the reason for the errror.
For some unknown reason, the Maven compiler plug-in DOES NOT put all the jar
dependencies under the module-path. It splits the list of dependencies between
the classpath and the module-path, WHICH IS WRONG! (see below)
[INFO] Changes detected - recompiling the module!
[DEBUG] Classpath: <- There should be no jar under this Classpath list ***
[DEBUG] C:\Users\Colbert
Philippe\workspace\montreal\quebec.lachine\target\classes
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\org\apache\commons\commons-collections4\4.1\commons-collections4-4.1.jar
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\commons-beanutils\commons-beanutils\1.9.3\commons-beanutils-1.9.3.jar
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\commons-logging\commons-logging\1.2\commons-logging-1.2.jar
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\commons-collections\commons-collections\3.2.2\commons-collections-3.2.2.jar
[DEBUG] Modulepath: <- All jar file dependencies should be under this
ModulePath list ***
[DEBUG] C:\Users\Colbert
Philippe\.m2\repository\org\apache\commons\commons-lang3\3.7\commons-lang3-3.7.jar
[DEBUG] Source roots:
This is the source of the error!
Since putting all the jar files under module-path works in my first
hand-created project works fine. I am certain that this is the cause of the
error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6390) Java9 Jigsaw ==> How to put Java library Jar files in Jigsaw "module-path"?
[ https://issues.apache.org/jira/browse/MNG-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431427#comment-16431427 ] Colbert Philippe commented on MNG-6390: --- Hello Robert! I got Maven with maven-compiler-plugin 3.7.0 to work as I want. I can use external jar libraries, which is what everybody wants. Furthermore, I got it to work inside Eclipse 4.8M4 an pre-release version. Now I am clear about what to do. The maven-compiler-plugin 3.7.0 should ship with the latest Eclipse to avoid waste of time and confusion. I does not! It's a bad reflection on Maven as a tool. You should push to have them use that latest version. The document should simply mention that the Classpath inside Eclipse should have paths to .class files (created in the project) and the module-path should have math to module and pathes to old-style jar files. > Java9 Jigsaw ==> How to put Java library Jar files in Jigsaw "module-path"? > --- > > Key: MNG-6390 > URL: https://issues.apache.org/jira/browse/MNG-6390 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.5.3 >Reporter: Colbert Philippe >Priority: Major > > I'm using Eclipse 4.8M4 (latest version at the time) with Maven used with > Java9. I want to use Java9 new module feature (project Jigsaw) in my new > application. > After carefully the documentation and Internet blogs, I can successfully use > legacy libraries with Java9. I do this WITHOUT Maven, using the > command-line. This process is now clear to me. > However, now I want to do the same with Maven. That's where things get > confusing. I need a way to put "old style" Java libraries (jar file) in the > new Jigsaw concept of "module-path" (actual command-line parameter of javac). > The big question is: How can I put my Java jar libraries in the > "module-path"?. I should be able to do this from Maven. > If this question is answered, the natural follow-up question is: How can I > do that from Eclipse? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6390) Java9 Jigsaw ==> How to put Java library Jar files in Jigsaw "module-path"?
[ https://issues.apache.org/jira/browse/MNG-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430897#comment-16430897 ] Colbert Philippe commented on MNG-6390: --- Thanks Robert Scholte! Since, I wrote the letter, I made some progress but not completely. What me and other people in my situation are missing is a small document and a *** full example of Maven (only, without IDE) *** of a Java project implemented in Maven and using 2 or 3 open-source old-style Jar file (maybe 2 or 3 apache commons libraries). Of course, we want to see the complete POM(s). As you know Mr. Robert Scholte, the most recent Eclipse ships with Maven 3.1 only, not 3.7.0. So people are wasting a lot time trying to do the impossible. I spend an entire weekend trying to get this work and I'm still not successful. There is a lot of confusion out there about Java9 module. This can be put on GitHub for all to access. The example given so far have been too simplistic! If you help me with my problems, I promise to make my this document and example! I will create an exmple from the command-line, using Maven 3.7.0. I need to see how to configure the maven-compiler-plugin to take module-path and classpath. Can you help me? > Java9 Jigsaw ==> How to put Java library Jar files in Jigsaw "module-path"? > --- > > Key: MNG-6390 > URL: https://issues.apache.org/jira/browse/MNG-6390 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.5.3 >Reporter: Colbert Philippe >Priority: Major > > I'm using Eclipse 4.8M4 (latest version at the time) with Maven used with > Java9. I want to use Java9 new module feature (project Jigsaw) in my new > application. > After carefully the documentation and Internet blogs, I can successfully use > legacy libraries with Java9. I do this WITHOUT Maven, using the > command-line. This process is now clear to me. > However, now I want to do the same with Maven. That's where things get > confusing. I need a way to put "old style" Java libraries (jar file) in the > new Jigsaw concept of "module-path" (actual command-line parameter of javac). > The big question is: How can I put my Java jar libraries in the > "module-path"?. I should be able to do this from Maven. > If this question is answered, the natural follow-up question is: How can I > do that from Eclipse? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6390) Java9 Jigsaw ==> How to put Java library Jar files in Jigsaw "module-path"?
Colbert Philippe created MNG-6390: - Summary: Java9 Jigsaw ==> How to put Java library Jar files in Jigsaw "module-path"? Key: MNG-6390 URL: https://issues.apache.org/jira/browse/MNG-6390 Project: Maven Issue Type: Improvement Components: core Affects Versions: 3.5.3 Reporter: Colbert Philippe I'm using Eclipse 4.8M4 (latest version at the time) with Maven used with Java9. I want to use Java9 new module feature (project Jigsaw) in my new application. After carefully the documentation and Internet blogs, I can successfully use legacy libraries with Java9. I do this WITHOUT Maven, using the command-line. This process is now clear to me. However, now I want to do the same with Maven. That's where things get confusing. I need a way to put "old style" Java libraries (jar file) in the new Jigsaw concept of "module-path" (actual command-line parameter of javac). The big question is: How can I put my Java jar libraries in the "module-path"?. I should be able to do this from Maven. If this question is answered, the natural follow-up question is: How can I do that from Eclipse? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNGSITE-238) Many dead links on webpage Maven Resource Plugin page!
Colbert Philippe created MNGSITE-238: Summary: Many dead links on webpage Maven Resource Plugin page! Key: MNGSITE-238 URL: https://issues.apache.org/jira/browse/MNGSITE-238 Project: Maven Project Web Site Issue Type: Bug Reporter: Colbert Philippe Many links on the left menu are dead. Look at links http://maven.apache.org/plugins/maven-resources-plugin/ - Filtering - Including and excluding files and directories - Escape Filtering - Copy Resources - Binaries Filtering - Custom Resources Filters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
