Hi, I skimmed through the jlink man page recently, and I think it should be rectified in some places and improved in others. Below are the two issues I noticed.
1. --module-path description is misleading > -p or --module-path modulepath > Specifies the module path. > > If this option is not specified, then the default module path is > $JAVA_HOME/jmods. This directory contains the java.base module and the other > standard and JDK modules. If this option is specified but the java.base > module cannot be resolved from it, then the jlink command appends > $JAVA_HOME/jmods to the module path. >From what I could see in my environment, the $JAVA_HOME environment variable has nothing to do with the default value for module path. This variable might be undefined or specified incorrectly, but the modules are located correctly anyway. >From peeking into the source, it seems that it's the java.home property that is consulted. I think this description should be rectified. 2. --strip-debug and --strip-java-debug-attributes description could be more useful It's not clear which kind of debug information this is. The reader should be able to clearly see the tradeoff between lightening the output and losing some important diagnostic aid. It should be either linked to relevant javac options or explained in place. For example: do these mean I will lose line numbers in stack trackes (pertaining to JDK itself), variable names during remote debug or perhaps something else? -Pavel
