[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=16436100#comment-16436100
]
Robert Scholte edited comment on MCOMPILER-337 at 4/13/18 7:40 AM:
---
{noformat}
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) > >
