3

In previous versions of Java if you had for example a user-defined package org.mypackage in windows with directory structure

D:\myprogram\
      |
      ---> org\  
            |
            ---> mypackage\
                     |
                     ---> HelloWorld.class       
                     ---> SupportClass.class   
                     ---> UtilClass.class

you make the JVM aware of the package by using the CLASSPATH environment variable.

For example:

set CLASSPATH=D:\myprogram

Does set MODULEPATH command instead make the JVM aware of the location of user-defined modules in the latest versions of Java ?

If so why is classpath command still around and what purpose does it serve now?

Omid
  • 5,823
  • 4
  • 41
  • 50
Mahamed Ducale
  • 119
  • 1
  • 8

1 Answers1

1

No, the jdk does not read any MODULEPATH environment variable or similar.

The MODULEPATH only exists as a command-line argument --module-path, but not as an environment variable.

See http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-September/009345.html

Unlike CLASSPATH, there is no equivalent MODULEPATH to get the option off of the command line.

Also see the linked question Is it possible to mix --class-path and --module-path in javac (JDK 9)? for more details on the differences between boths paths.

If you put a normal jar on the modulepath, it becomes an automatic module, exporting its packages (and reserving those packages for itself).

While you can put any normal jar file into the MODULEPATH, there is a restriction: If 2 jar files contain the same package, then java will not allow both of them in the modulepath. That's why Java still has the classpath, because several existing jar files still have overlapping packages, and it is not possible to put them all on the MODULEPATH. They have to be cleaned up first.

In the far future, when all libraries have been migrated to modules (or cleaned up), maybe classpath can be removed.

tkruse
  • 10,222
  • 7
  • 53
  • 80
  • Does using the `MODULEPATH` environment variable really only work with explicit modules? I would expect non-modular jars to become automatic modules. – Slaw May 29 '19 at 06:25
  • I think you're right, thanks. – tkruse May 29 '19 at 06:51
  • 1
    What is meant by 'In the far future, when all libraries have been migrated to modules' ? – Mahamed Ducale May 29 '19 at 15:13
  • It means one day java might only use MODULEPATH, not both. But it is not clear which Java version will do so. – tkruse May 29 '19 at 23:25
  • 1
    It seems to be working only if set as a command-line option (e.g., java -p). It did not work with set module-path/modulepath/module_path. That is after setting via set, I ran java -m / and it says "Error occurred during initialization of boot layer. java.lang.module.FindException ..." – Dheeru Mundluru Sep 13 '19 at 06:57
  • Ditto on comment by @DheeruMundluru and I could not find any reference to a MODULEPATH variable here: https://docs.oracle.com/javase/9/tools/java.htm#JSWOR624 – pinkston00 Sep 15 '19 at 00:42