Академический Документы
Профессиональный Документы
Культура Документы
>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- USE THIS TEMPLATE WHEN ENHANCEMENTS ARE LENGTHY; YOU THEN WILL USE A
SEPARATE FILE TO DOCUMENT THE ENHANCEMENTS OF EACH VERSION CURRENTLY
SUPPORTED
-->
<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
"en-US">
<head>
<title>Tools Enhancements in JDK 8</title>
<meta name="collection" content="reference" />
<link rel="stylesheet" type="text/css" href="../../technotes/css/guide.css" />
</head>
<body>
<!-- STATIC HEADER -->
<!-- header start -->
<div id="javaseheader">
<div id="javaseheaderlogo">
<img src="../../images/javalogo.gif"
alt="Java logo" />
</div>
<div id="javaseheaderindex">
<a href=
"../../index.html">Documentation Contents</a>
</div>
<div class="clear"></div>
</div>
<!-- header end -->
<h1>Tools Enhancements in JDK 8</h1>
<p><a href="index.html">JDK Tools and Utilities</a></p>
<p><strong>Note</strong>: Some of the following features require a commercial
license for use in production. To learn more about commercial features and how
to enable them please visit <a
href="http://www.oracle.com/technetwork/java/javaseproducts/">Oracle Java SE
Advanced & Suite Products</a>.</p>
<p><b>The following enhancements were introduced in JDK 8u40:</b></p>
<ul>
<li><p><code>java</code> tool:</p>
<ul>
<li><p>The <code>-XX:+CheckEndorsedAndExtDirs</code> has been added
because the endorsed-standards override mechanism (<a
href="https://bugs.openjdk.java.net/browse/JDK-8065675">JDK-8065675</a>) and the
extension mechanism (<a href="https://bugs.openjdk.java.net/browse/JDK8065702">JDK-8065702</a>) have been deprecated. The option helps identify any
existing uses of these mechanisms and is supported in JDK 7u80 and JDK 8u40. See
<a href="https://bugs.openjdk.java.net/browse/JDK-8064667">JDK8064667</a>.</p></li>
<li><p>Prior to JDK 8u40, if you want to use Java Flight Recorder (JFR)
and create a flight recording for a particular Java application, you must
specify both the <code>-XX:+UnlockCommercialFeatures</code> and <code>-XX:
+FlightRecorder</code> when launching the application. In JDK 8u40, you do not
have to specify these options at the command line. JFR offers a variety of ways
</ul>
</li>
<li><p><code>javapackager</code> tool:</p>
<ul>
<li><p>New arguments are available for OS X bundlers. The
<code>mac.CFBundleVersion</code> argument identifies the internal version number
to be used. The <code>mac.dmg.simple</code> argument indicates if DMG
customization steps that depend on executing AppleScript code are skipped. See
<a href="https://bugs.openjdk.java.net/browse/JDK-8043060">JDK8043060</a>.</p></li>
</ul>
</li>
<li><p><code>jcmd</code> tool:</p>
<ul>
<li><p>You can use the <code>jcmd</code> tool to dynamically interact with
Java Flight Recorder (JFR) in a JVM that is already running. You can use it to
unlock commercial features, enable/start/stop flight recordings, and obtain
various status messages from the system. For a list of examples, see the Java
Flight Recorder Runtime Guide at the <a
href="https://docs.oracle.com/javacomponents/">Java Components</a>
page.</p></li>
</ul>
</li>
<li><p><code>jstat</code> tool:</p>
<ul>
<li><p>The <code>jstat</code> tool has been updated with information about
compressed class space (a special part of metaspace). See <a
href="https://bugs.openjdk.java.net/browse/JDK-8040079">JDK8040079</a>.</p></li>
</ul>
</li>
</ul>
<p><b>The following enhancements were introduced in JDK 8u20:</b></p>
<ul>
<li><p>The <code>javafxpackager</code> tool has been renamed to <code><a
href="index.html#javapackager">javapackager</a></code>. This tool has been
enhanced with new arguments for self-contained application bundlers. See <a
href="https://bugs.openjdk.java.net/browse/JDK-8041516">JDK8041516</a>.</p></li>
<li><p>Enhancements related to the <a
href="index.html#java"><code>java</code></a> launcher tool:</p>
<ul>
<li><p>Experimental JIT compiler options related to Restricted
Transactional Memory (RTM) have been added. See <a
href="https://bugs.openjdk.java.net/browse/JDK-8031320">JDK8031320</a>.</p></li>
<li><p>Options related to string deduplication have been added. See <a
href="https://bugs.openjdk.java.net/browse/JDK-8029075">JDK8029075</a>.</p></li>
<li><p>Options related to Advanced Encryption Standard (AES) intrinsics
have been added. See <a href="https://bugs.openjdk.java.net/browse/JDK8034899">JDK-8034899</a>.</p></li>
<li><p>Rarely used combinations of garbage collection options have been
deprecated. See <a href="https://bugs.openjdk.java.net/browse/JDK-8026909">JDK-
8026909</a>.</p></li>
</ul>
</li>
</ul>
<p><b>The following enhancements were introduced in JDK 8:</b></p>
<ul>
<li>
<p>The <code>jjs</code> command was introduced, which invokes the
Nashorn engine either in interactive shell mode, or to interpret
script files. For more information, see the <a href=
"../guides/scripting/nashorn/index.html">Nashorn User's
Guide</a>.</p>
</li>
<li>
<p>The <code>java</code> command is capable of launching JavaFX
applications, provided that the JavaFX application is packaged
correctly. See <a href="findingclasses.html">How Classes are
Found</a>.</p>
</li>
<li>
<p>The <tt>java</tt> command man page (both nroff and HTML) has
been completely reworked. The advanced options are now divided into
Runtime, Compiler, Garbage Collection, and Serviceability,
according to the area that they affect. Several previously missing
options are now described. There is also a section for options that
were deprecated or removed since the previous release.</p>
</li>
<li>
<p>The new <tt>jdeps</tt> command-line tool allows the developer to
analyze class files to determine package-level or class-level
dependencies. See <a href=
"http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8003562">JDK8003562</a>.</p>
</li>
<li>
<p>JDK 8 provides remote access to diagnostic commands which were
previously accessible only locally via the <tt>jcmd</tt> tool.
Remote access is provided using the Java Management Extensions
(JMX), so diagnostic commands are exposed to a platform MBean
registered to the platform MBean server. The MBean is the
<tt>com.sun.management.DiagnosticCommandMBean</tt> interface. See
the <tt>jcmd</tt> documentation for <a href=
"unix/jcmd.html">
Solaris, Linux, and OS X</a> or <a href=
"windows/jcmd.html">
Windows</a>.<br />
<br /></p>
</li>
<li>
<p>The <code>jarsigner</code> tool contains a new option
<code>-tsapolicyid</code> which enables you to request a signed
time stamp from a Time Stamping Authority and attach it to a signed
JAR file. See <a href=
"http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8009636">JDK8009636</a></p>
</li>
<li>
<p>You can obtain the names of the formal parameters of any method
or constructor with the method <a href=
"../../api/java/lang/reflect/Executable.html#getParameters()"><code>
java.lang.reflect.Executable.getParameters</code></a>. However,
<code>.class</code> files do not store formal parameter names by
default. To store formal parameter names in a particular
</body>
</html>