I understand that there are more important things for JDK people to do right now. That said, on the JDK 26 Tool Specifications page there are two tools that are not described the way the rest of the tools are: jdeprscan and jnativescan.
Normally, a tool is described as follows: * <tool> - <verb> ... For example: * jar - create ... * jarsigner - sign and verify ... * java - launch ... * javac - read ... * javadoc - generate ... * javap - disassemble ... * ... * jshell - interactively evaluate ... * etc. This is clear and consistent. But these two are described as follows: * jdeprscan - static analysis tool that scans a jar file (or some other aggregation of class files) for uses of deprecated API elements * jnativescan - static analysis tool that scans one or more jar files for uses of native functionalities It's clear but inconsistent with the rest of the page. Could these be rephrased perhaps as follows? * jdeprscan - statically analyze a jar file (or some other aggregation of class files) for uses of deprecated API elements * jnativescan - statically analyze one or more jar files for uses of native functionalities Separately, this tool's description is overly generic: * jmap - print details of a specified process >From the actual tool page, it seems that it primarily, if not exclusively, deals with the heap: finalizations, snapshots, etc. If so, perhaps it should be conveyed in the tool summary. FWIW, it seems that in JDK 8 it was documented far more specifically: > Prints shared object memory maps or heap memory details for a process, core > file, or remote debug server. Thanks, -Pavel
