Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8190667

which command doesn't populate for jmod, jlink and jaotc

    Details

    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      os_x

      Description

      FULL PRODUCT VERSION :
      java version "9"
      Java(TM) SE Runtime Environment (build 9+181)
      Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)

      ADDITIONAL OS VERSION INFORMATION :
      Darwin Macintosh.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64

      EXTRA RELEVANT SYSTEM CONFIGURATION :
      Not applicable

      A DESCRIPTION OF THE PROBLEM :
      Java command line tools are missing or seem to point to the wrong versions.
      This might be because I have had earlier Apple releases installed since some seem to point to old Apple install files...

      which jdeps
      /usr/bin/jdeps

      ls -l /usr/bin/jdeps
      lrwxr-xr-x 1 root wheel 75 Jun 4 20:48 /usr/bin/jdeps -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/jdeps

      which I believe goes back to old Apple and not Oracle but possibly Oracle does still use this Framework for installations?

      Sizes seem to differ between what shows in the Framework and what shows at the install location.

      For java.

      ls -l /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java
      -rwxr-xr-x 1 root wheel 58288 Apr 28 2017 /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java

      For installed...

      ls -l `/usr/libexec/java_home`/bin/java
      -rwxrwxr-x 1 root wheel 81200 Aug 2 23:17 /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/bin/java

      However, versions still seem to be correct...

      For installed...

      /usr/libexec/java_home
      /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home

      `/usr/libexec/java_home`/bin/java -version
      java version "9"
      Java(TM) SE Runtime Environment (build 9+181)
      Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)

      For Framework...

      /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java -version
      java version "9"
      Java(TM) SE Runtime Environment (build 9+181)
      Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)

      So whatever is pointed to by the Framework might be correct despite the size difference.
      For the other tools it is harder to be sure the version matches because they just show as version 9 with no build information.

      Also, the jlink command doesn't seem to have anything pointing to it. Again for jdeps...

      echo `which jdeps` is here
      /usr/bin/jdeps is here

      but for jlink...

      echo `which jlink` is here
      is here

      Nothing is here.

      So.
      1). Is the java Framework mechanism still what should be used for command line tools?

      2). If it is does it always point to correct versions?

      3). There is nothing pointing to the jlink command line tool.




      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Install java 9

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      Command line tools present and correct versions in supported locations.

      ACTUAL -
      The command line tools are indirectly through a possibly Apple legacy java Framework.

      The jlink although present in the installed JRE seems to be missing.


      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      Not applicable

      REPRODUCIBILITY :
      This bug can be reproduced always.

      ---------- BEGIN SOURCE ----------
      Not applicable
      ---------- END SOURCE ----------

      CUSTOMER SUBMITTED WORKAROUND :
      For jlink for now I added an alias in my .bash_profile. I didn't want to mess with symbolic links which might interfere with a possible more permanent later fix.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                asemenyuk Alexey Semenyuk
                Reporter:
                webbuggrp Webbug Group
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: