From: winstone77 Date: Wed, 15 Jan 2025 05:53:13 +0000 (+0900) Subject: jdk bundle for GBS X-Git-Tag: accepted/tizen/unified/20250122.054554^0 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;p=sdk%2Ftools%2Fjdk.git jdk bundle for GBS Change-Id: Ib96362db9e815da652007b6f8ed4553f866d0470 Signed-off-by: winstone77 --- diff --git a/README.md b/README.md new file mode 100755 index 0000000..47f1723 --- /dev/null +++ b/README.md @@ -0,0 +1,2 @@ +# jdk (v1.8.0.261) +JDK Package for gbs build diff --git a/jdk-1.8.0.281/COPYRIGHT b/jdk-1.8.0.281/COPYRIGHT new file mode 100755 index 0000000..15c35f6 --- /dev/null +++ b/jdk-1.8.0.281/COPYRIGHT @@ -0,0 +1,69 @@ +Copyright © 1993, 2021, Oracle and/or its affiliates. +All rights reserved. + +This software and related documentation are provided under a +license agreement containing restrictions on use and +disclosure and are protected by intellectual property laws. +Except as expressly permitted in your license agreement or +allowed by law, you may not use, copy, reproduce, translate, +broadcast, modify, license, transmit, distribute, exhibit, +perform, publish, or display any part, in any form, or by +any means. Reverse engineering, disassembly, or +decompilation of this software, unless required by law for +interoperability, is prohibited. + +The information contained herein is subject to change +without notice and is not warranted to be error-free. If you +find any errors, please report them to us in writing. + +If this is software or related documentation that is +delivered to the U.S. Government or anyone licensing it on +behalf of the U.S. Government, the following notice is +applicable: + +U.S. GOVERNMENT END USERS: Oracle programs, including any +operating system, integrated software, any programs +installed on the hardware, and/or documentation, delivered +to U.S. Government end users are "commercial computer +software" pursuant to the applicable Federal Acquisition +Regulation and agency-specific supplemental regulations. As +such, use, duplication, disclosure, modification, and +adaptation of the programs, including any operating system, +integrated software, any programs installed on the hardware, +and/or documentation, shall be subject to license terms and +license restrictions applicable to the programs. No other +rights are granted to the U.S. Government. + +This software or hardware is developed for general use in a +variety of information management applications. It is not +developed or intended for use in any inherently dangerous +applications, including applications that may create a risk +of personal injury. If you use this software or hardware in +dangerous applications, then you shall be responsible to +take all appropriate fail-safe, backup, redundancy, and +other measures to ensure its safe use. Oracle Corporation +and its affiliates disclaim any liability for any damages +caused by use of this software or hardware in dangerous +applications. + +Oracle and Java are registered trademarks of Oracle and/or +its affiliates. Other names may be trademarks of their +respective owners. + +Intel and Intel Xeon are trademarks or registered trademarks +of Intel Corporation. All SPARC trademarks are used under +license and are trademarks or registered trademarks of SPARC +International, Inc. AMD, Opteron, the AMD logo, and the AMD +Opteron logo are trademarks or registered trademarks of +Advanced Micro Devices. UNIX is a registered trademark of +The Open Group. + +This software or hardware and documentation may provide +access to or information on content, products, and services +from third parties. Oracle Corporation and its affiliates +are not responsible for and expressly disclaim all +warranties of any kind with respect to third-party content, +products, and services. Oracle Corporation and its +affiliates will not be responsible for any loss, costs, or +damages incurred due to your access to or use of third-party +content, products, or services. diff --git a/jdk-1.8.0.281/LICENSE b/jdk-1.8.0.281/LICENSE new file mode 100755 index 0000000..6a33d4a --- /dev/null +++ b/jdk-1.8.0.281/LICENSE @@ -0,0 +1 @@ +Please refer to https://java.com/otnlicense diff --git a/jdk-1.8.0.281/README.html b/jdk-1.8.0.281/README.html new file mode 100755 index 0000000..10ea506 --- /dev/null +++ b/jdk-1.8.0.281/README.html @@ -0,0 +1,9 @@ + + +README + + + +Please refer to http://java.com/licensereadme + + diff --git a/jdk-1.8.0.281/THIRDPARTYLICENSEREADME-JAVAFX.txt b/jdk-1.8.0.281/THIRDPARTYLICENSEREADME-JAVAFX.txt new file mode 100755 index 0000000..b1d2cf6 --- /dev/null +++ b/jdk-1.8.0.281/THIRDPARTYLICENSEREADME-JAVAFX.txt @@ -0,0 +1,3 @@ +The licenses for Third Party components included with this product can +be found under the /legal/javafx subdirectory. Each component's license +is available as a separate markdown (.md) file diff --git a/jdk-1.8.0.281/THIRDPARTYLICENSEREADME.txt b/jdk-1.8.0.281/THIRDPARTYLICENSEREADME.txt new file mode 100755 index 0000000..ac4e1ff --- /dev/null +++ b/jdk-1.8.0.281/THIRDPARTYLICENSEREADME.txt @@ -0,0 +1,3 @@ +The licenses for Third Party components included with this product can +be found under the /legal/jdk subdirectory. Each component's license is +available as a separate markdown (.md) file. diff --git a/jdk-1.8.0.281/bin/ControlPanel b/jdk-1.8.0.281/bin/ControlPanel new file mode 100755 index 0000000..57f80a8 --- /dev/null +++ b/jdk-1.8.0.281/bin/ControlPanel @@ -0,0 +1,245 @@ +#!/bin/bash +# +# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# Shell Script to run the Java Plug-in control panel. +# +# Parse the command-line options +# -r means make associate with the container (i.e browser) +# -u means remove the association with the container +# -c provides the location of the container install +# -j provides the location of the jre install +# if neither -r or -u are specified, run the ControlPanel UI + +USAGE='usage: ControlPanel [ (-u scheme | -r scheme) -c cpath -j jrepath ]' +JLERROR='ControlPanel: Error: Invalid JRE location: ' +CLERROR='ControlPanel: Error: Invalid container location: ' +IPERROR='ControlPanel: Error: Insufficient permission' +ISERROR='ControlPanel: Error: Invalid scheme: ' +XLERROR='ControlPanel: Error: Invalid link or copy: ' + +check_container_dir() { + + if [ ! -d ${1} ]; then + echo "${CLERROR}${2}" + exit 1 + fi + if [ ! -w ${1} ]; then + echo "${IPERROR}" + exit 1 + fi +} + +link_logic() { + if [ ${mode} = "reg" ]; then + ln -s ${1} ${2} + else + rm -f ${2} + fi +} + +# +# Get the absolute path to a symbolic link's reference. +# +# Parameters: +# $* : path - the path to the file (link) to dereference (can have spaces in +# the path). +# +# Output: +# This function writes the path to the link reference to stdout. +# +# +dereference() { + path="$*" + result= + + # + # Make sure the path is absolute + # + parent="`cd \`dirname \"${path}\"\`; pwd -P`" + child="`basename \"${path}\"`" + + # + # if parent == child, then path == /, and is already absolute + # + if [ "${parent}" != "${child}" ]; then + path="${parent}/${child}" + fi + + if [ -h "${path}" ]; then + path=`ls -l "${path}" | sed -e "s#^.*${path} -> ##"` + + # make sure the path is still absolute (starts with '/') + if expr "${path}" : '[^/]' > /dev/null; then + path="${parent}/${path}" + fi + fi + + echo ${path} +} + +# +# Check for all the parts required to launch the control panel relative to the +# given path. +# +# +# Parameters: +# $* : path - the path to examine, presumably the resolved path to this +# script (can have spaces in the path). +# +# Output: +# If successful, this function outputs the absolute path to a directory +# containing the Java binary, and ../lib/deploy.jar; otherwise it outputs +# an empty string. (Output is to stdout.) +# +# Note: the assumption is that this function returns either: +# +# /jre/bin, or +# /bin +# +# However, as long as the directory pointed by the path returned by this +# function contains: +# +# ./java +# ../lib/deploy.jar +# +# it should be possible to successfully launch the JCP from the given +# information. +# +check_parts() { + result="`cd \`dirname \"$*\"\`; pwd -P`" + + # if this is a JDK, we need the JRE subdir + if [ -d "${result}/../jre/bin" ]; then + result="`cd \`dirname \"$*\"\`/../jre/bin; pwd -P`" + fi + + if [ ! -x "${result}/java" ] || [ ! -f "${result}/../lib/deploy.jar" ]; then + result= + fi + + echo ${result} +} + +# +# Launch the Java Control Panel. +# +# Parameters: +# $* : path - the path of this script (can have spaces in the path). +# +launch_jcp() { + path="$*" + while [ -h ${path} ]; do + path="`dereference ${path}`" + done + + java_home="`check_parts ${path}`" + if [ -n "${java_home}" ]; then + # launch the JCP using paths relative to + ${java_home}/java -Djavaplugin.user.profile=${USER_JPI_PROFILE} \ + -Xbootclasspath/a:${java_home}/../lib/deploy.jar \ + ${_JAVA_VM_OPTIONS} \ + com.sun.deploy.panel.ControlPanel + else + echo "${XLERROR}${java_home}" + exit 1 + fi +} + +# +# Manage the process of registering/unregistering the Java Plug-in with a given +# container (browser). +# +manage_container() { + # Do the "right" thing based on the provided scheme. + plugin_stem=${java_home}/plugin/${proc} + if [ ! -d ${plugin_stem} ]; then + echo "${JLERROR}${java_home}" + exit 1 + fi + + case ${scheme} in + ns4 | ns4E ) + plugin_location="${plugin_stem}/ns4" + if [ ${mode} = "reg" ]; then + echo "${plugin_location}" + fi + ;; + ns4L ) + plugin_location="${plugin_stem}/ns4" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + ns610 | ns610L ) + plugin_location="${plugin_stem}/ns610" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + * ) + echo ${ISERROR}${scheme} + exit 1 + esac +} + +while getopts ":r:u:c:j:" opt; do + case $opt in + r ) mode="reg";scheme=${OPTARG} + ;; + u ) mode="unreg";scheme=${OPTARG} + ;; + c ) container_home=${OPTARG} + ;; + j ) java_home=${OPTARG} + ;; + : ) echo ${USAGE} + exit 1 + ;; + \? ) echo ${USAGE} + exit 1 + ;; + esac +done + +os=`uname -s` +if [ "${os}" = "Linux" ]; then + case "`uname -m`" in + i[3-9]86 | ia32 | ia64 | x86_64) + proc=i386 + ;; + sparc*) + proc=sparc + ;; + arm*) + proc=arm + ;; + ppc*) + proc=ppc + ;; + *) + proc="`uname -m`" + ;; + esac +else + proc=`uname -p` +fi + +if [ -z "${scheme}" ] && + [ -z "${java_home}" ] && [ -z "${container_home}" ] +then + # just run the control panel + launch_jcp $0 +elif [ -n "${scheme}" ] && + [ -n "${java_home}" ] && [ -n "${container_home}" ] +then + # try to register/unregister the plugin + manage_container +else + # one or more missing args + echo ${USAGE} + exit 1 +fi diff --git a/jdk-1.8.0.281/bin/appletviewer b/jdk-1.8.0.281/bin/appletviewer new file mode 100755 index 0000000..0f01e98 Binary files /dev/null and b/jdk-1.8.0.281/bin/appletviewer differ diff --git a/jdk-1.8.0.281/bin/extcheck b/jdk-1.8.0.281/bin/extcheck new file mode 100755 index 0000000..02fe4c3 Binary files /dev/null and b/jdk-1.8.0.281/bin/extcheck differ diff --git a/jdk-1.8.0.281/bin/idlj b/jdk-1.8.0.281/bin/idlj new file mode 100755 index 0000000..83d1233 Binary files /dev/null and b/jdk-1.8.0.281/bin/idlj differ diff --git a/jdk-1.8.0.281/bin/jar b/jdk-1.8.0.281/bin/jar new file mode 100755 index 0000000..8ff29ef Binary files /dev/null and b/jdk-1.8.0.281/bin/jar differ diff --git a/jdk-1.8.0.281/bin/jarsigner b/jdk-1.8.0.281/bin/jarsigner new file mode 100755 index 0000000..4295d06 Binary files /dev/null and b/jdk-1.8.0.281/bin/jarsigner differ diff --git a/jdk-1.8.0.281/bin/java b/jdk-1.8.0.281/bin/java new file mode 100755 index 0000000..cba6d8e Binary files /dev/null and b/jdk-1.8.0.281/bin/java differ diff --git a/jdk-1.8.0.281/bin/java-rmi.cgi b/jdk-1.8.0.281/bin/java-rmi.cgi new file mode 100755 index 0000000..baf2091 --- /dev/null +++ b/jdk-1.8.0.281/bin/java-rmi.cgi @@ -0,0 +1,74 @@ +#!/bin/sh + +# +# Copyright (c) 1996, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# + +# +# + +# +# This script executes the Java interpreter, defines properties +# that correspond to the CGI 1.0 environment variables, and executes +# the class "sun.rmi.transport.proxy.CGIHandler". It should be +# installed in the directory to which the HTTP server maps the +# URL path "/cgi-bin". +# +# (Configuration is necessary as noted below.) +# +# This class will support a QUERY_STRING of the form "forward=" +# with a REQUEST_METHOD "POST". The body of the request will be +# forwarded (as another POST request) to the server listening on the +# specified port (must be >= 1024). The response from this forwarded +# request will be the response to the original request. +# +# CONFIGURATION: +# +# Fill in correct absolute path to Java interpreter below. For example, +# the "PATH=" line might be changed to the follow if the JDK is installed +# at the path "/home/peter/java": +# +# PATH=/home/peter/java/bin:$PATH +# +PATH=/usr/local/java/bin:$PATH +exec java \ + -DAUTH_TYPE="$AUTH_TYPE" \ + -DCONTENT_LENGTH="$CONTENT_LENGTH" \ + -DCONTENT_TYPE="$CONTENT_TYPE" \ + -DGATEWAY_INTERFACE="$GATEWAY_INTERFACE" \ + -DHTTP_ACCEPT="$HTTP_ACCEPT" \ + -DPATH_INFO="$PATH_INFO" \ + -DPATH_TRANSLATED="$PATH_TRANSLATED" \ + -DQUERY_STRING="$QUERY_STRING" \ + -DREMOTE_ADDR="$REMOTE_ADDR" \ + -DREMOTE_HOST="$REMOTE_HOST" \ + -DREMOTE_IDENT="$REMOTE_IDENT" \ + -DREMOTE_USER="$REMOTE_USER" \ + -DREQUEST_METHOD="$REQUEST_METHOD" \ + -DSCRIPT_NAME="$SCRIPT_NAME" \ + -DSERVER_NAME="$SERVER_NAME" \ + -DSERVER_PORT="$SERVER_PORT" \ + -DSERVER_PROTOCOL="$SERVER_PROTOCOL" \ + -DSERVER_SOFTWARE="$SERVER_SOFTWARE" \ + sun.rmi.transport.proxy.CGIHandler diff --git a/jdk-1.8.0.281/bin/javac b/jdk-1.8.0.281/bin/javac new file mode 100755 index 0000000..435004f Binary files /dev/null and b/jdk-1.8.0.281/bin/javac differ diff --git a/jdk-1.8.0.281/bin/javadoc b/jdk-1.8.0.281/bin/javadoc new file mode 100755 index 0000000..b42f4d3 Binary files /dev/null and b/jdk-1.8.0.281/bin/javadoc differ diff --git a/jdk-1.8.0.281/bin/javafxpackager b/jdk-1.8.0.281/bin/javafxpackager new file mode 100755 index 0000000..ee3ecff --- /dev/null +++ b/jdk-1.8.0.281/bin/javafxpackager @@ -0,0 +1,89 @@ +#!/bin/sh +# +# JavaFX Packager tool execution script for Linux/Solaris/OS X. +# + +# resolve symlinks +PRG=$0 +while [ -h "$PRG" ]; do + ls=`ls -ld "$PRG"` + link=`expr "$ls" : '^.*-> \(.*\)$' 2>/dev/null` + if expr "$link" : '^/' 2> /dev/null >/dev/null; then + PRG="$link" + else + PRG="`dirname "$PRG"`/$link" + fi +done + +# detect Darwin and Cygwin environments +darwin=false; +cygwin=false; +case "`uname`" in + Darwin*) darwin=true; + if [ -z "$JAVA_HOME" ] ; then + BIN_DIR=`dirname $PRG` + JAVA_HOME=`cd $BIN_DIR > /dev/null; pwd`/.. + fi + ;; + CYGWIN*) cygwin=true;; +esac + +if [ -n "$JAVA_HOME" -a -x "$JAVA_HOME/bin/javac" ] ; then + JAVA_CMD="$JAVA_HOME/bin/java" + export JAVA_HOME +else + JAVAC_CMD=`which javac 2> /dev/null ` + while [ -h "$JAVAC_CMD" ]; do + ls=`ls -ld "$JAVAC_CMD"` + link=`expr "$ls" : '^.*-> \(.*\)$' 2>/dev/null` + if expr "$link" : '^/' 2> /dev/null >/dev/null; then + JAVAC_CMD="$link" + else + JAVAC_CMD="`dirname "$JAVAC_CMD"`/$link" + fi + done + BIN_DIR=`dirname "$JAVAC_CMD"` + JAVA_HOME=`dirname "$BIN_DIR"` + if [ "m$JAVA_HOME" != "m." ]; then + JAVA_CMD="$JAVA_HOME/bin/java" + export JAVA_HOME + else + unset JAVA_HOME + JAVA_CMD=`which java 2> /dev/null ` + if [ -z "$JAVA_CMD" ]; then + JAVA_CMD="java" + fi + fi +fi + + +if [ ! -x "$JAVA_CMD" ] ; then + echo 'Error: JAVA_HOME is not defined, cannot find "java" command.' + exit 1 +fi + +case "$PRG" in + *javafxpackager) + echo 'javafxpackager has been renamed javapackager'; + echo 'The original file may be removed in a future release in lieu of javapackager.'; + echo 'Please update your scripts.'; + echo ;; +esac + +javafx_home=`dirname "$PRG"`/.. + +classpath=".:$javafx_home/lib/ant-javafx.jar" + +if [ -e "$javafx_home/jre/lib/ext/jfxrt.jar" ] ; then + classpath="$classpath:$javafx_home/jre/lib/ext/jfxrt.jar" +elif [ -e "$javafx_home/rt/lib/ext/jfxrt.jar" ] ; then + classpath="$classpath:$javafx_home/rt/lib/ext/jfxrt.jar" +fi + +if $cygwin ; then + classpath=`cygpath --path --windows "$classpath"` + javafx_home=`cygpath --windows "$javafx_home"` + JAVA_CMD=`cygpath --unix "$JAVA_CMD"` +fi + +exec "$JAVA_CMD" -Xmx256M "-Djavafx.home=$javafx_home" -classpath "$classpath" com.sun.javafx.tools.packager.Main "$@" diff --git a/jdk-1.8.0.281/bin/javah b/jdk-1.8.0.281/bin/javah new file mode 100755 index 0000000..7f9bd0a Binary files /dev/null and b/jdk-1.8.0.281/bin/javah differ diff --git a/jdk-1.8.0.281/bin/javap b/jdk-1.8.0.281/bin/javap new file mode 100755 index 0000000..3121ac8 Binary files /dev/null and b/jdk-1.8.0.281/bin/javap differ diff --git a/jdk-1.8.0.281/bin/javapackager b/jdk-1.8.0.281/bin/javapackager new file mode 100755 index 0000000..ee3ecff --- /dev/null +++ b/jdk-1.8.0.281/bin/javapackager @@ -0,0 +1,89 @@ +#!/bin/sh +# +# JavaFX Packager tool execution script for Linux/Solaris/OS X. +# + +# resolve symlinks +PRG=$0 +while [ -h "$PRG" ]; do + ls=`ls -ld "$PRG"` + link=`expr "$ls" : '^.*-> \(.*\)$' 2>/dev/null` + if expr "$link" : '^/' 2> /dev/null >/dev/null; then + PRG="$link" + else + PRG="`dirname "$PRG"`/$link" + fi +done + +# detect Darwin and Cygwin environments +darwin=false; +cygwin=false; +case "`uname`" in + Darwin*) darwin=true; + if [ -z "$JAVA_HOME" ] ; then + BIN_DIR=`dirname $PRG` + JAVA_HOME=`cd $BIN_DIR > /dev/null; pwd`/.. + fi + ;; + CYGWIN*) cygwin=true;; +esac + +if [ -n "$JAVA_HOME" -a -x "$JAVA_HOME/bin/javac" ] ; then + JAVA_CMD="$JAVA_HOME/bin/java" + export JAVA_HOME +else + JAVAC_CMD=`which javac 2> /dev/null ` + while [ -h "$JAVAC_CMD" ]; do + ls=`ls -ld "$JAVAC_CMD"` + link=`expr "$ls" : '^.*-> \(.*\)$' 2>/dev/null` + if expr "$link" : '^/' 2> /dev/null >/dev/null; then + JAVAC_CMD="$link" + else + JAVAC_CMD="`dirname "$JAVAC_CMD"`/$link" + fi + done + BIN_DIR=`dirname "$JAVAC_CMD"` + JAVA_HOME=`dirname "$BIN_DIR"` + if [ "m$JAVA_HOME" != "m." ]; then + JAVA_CMD="$JAVA_HOME/bin/java" + export JAVA_HOME + else + unset JAVA_HOME + JAVA_CMD=`which java 2> /dev/null ` + if [ -z "$JAVA_CMD" ]; then + JAVA_CMD="java" + fi + fi +fi + + +if [ ! -x "$JAVA_CMD" ] ; then + echo 'Error: JAVA_HOME is not defined, cannot find "java" command.' + exit 1 +fi + +case "$PRG" in + *javafxpackager) + echo 'javafxpackager has been renamed javapackager'; + echo 'The original file may be removed in a future release in lieu of javapackager.'; + echo 'Please update your scripts.'; + echo ;; +esac + +javafx_home=`dirname "$PRG"`/.. + +classpath=".:$javafx_home/lib/ant-javafx.jar" + +if [ -e "$javafx_home/jre/lib/ext/jfxrt.jar" ] ; then + classpath="$classpath:$javafx_home/jre/lib/ext/jfxrt.jar" +elif [ -e "$javafx_home/rt/lib/ext/jfxrt.jar" ] ; then + classpath="$classpath:$javafx_home/rt/lib/ext/jfxrt.jar" +fi + +if $cygwin ; then + classpath=`cygpath --path --windows "$classpath"` + javafx_home=`cygpath --windows "$javafx_home"` + JAVA_CMD=`cygpath --unix "$JAVA_CMD"` +fi + +exec "$JAVA_CMD" -Xmx256M "-Djavafx.home=$javafx_home" -classpath "$classpath" com.sun.javafx.tools.packager.Main "$@" diff --git a/jdk-1.8.0.281/bin/javaws b/jdk-1.8.0.281/bin/javaws new file mode 100755 index 0000000..cc20fe4 Binary files /dev/null and b/jdk-1.8.0.281/bin/javaws differ diff --git a/jdk-1.8.0.281/bin/jcmd b/jdk-1.8.0.281/bin/jcmd new file mode 100755 index 0000000..e1e27e4 Binary files /dev/null and b/jdk-1.8.0.281/bin/jcmd differ diff --git a/jdk-1.8.0.281/bin/jconsole b/jdk-1.8.0.281/bin/jconsole new file mode 100755 index 0000000..3b7899b Binary files /dev/null and b/jdk-1.8.0.281/bin/jconsole differ diff --git a/jdk-1.8.0.281/bin/jcontrol b/jdk-1.8.0.281/bin/jcontrol new file mode 100755 index 0000000..57f80a8 --- /dev/null +++ b/jdk-1.8.0.281/bin/jcontrol @@ -0,0 +1,245 @@ +#!/bin/bash +# +# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# Shell Script to run the Java Plug-in control panel. +# +# Parse the command-line options +# -r means make associate with the container (i.e browser) +# -u means remove the association with the container +# -c provides the location of the container install +# -j provides the location of the jre install +# if neither -r or -u are specified, run the ControlPanel UI + +USAGE='usage: ControlPanel [ (-u scheme | -r scheme) -c cpath -j jrepath ]' +JLERROR='ControlPanel: Error: Invalid JRE location: ' +CLERROR='ControlPanel: Error: Invalid container location: ' +IPERROR='ControlPanel: Error: Insufficient permission' +ISERROR='ControlPanel: Error: Invalid scheme: ' +XLERROR='ControlPanel: Error: Invalid link or copy: ' + +check_container_dir() { + + if [ ! -d ${1} ]; then + echo "${CLERROR}${2}" + exit 1 + fi + if [ ! -w ${1} ]; then + echo "${IPERROR}" + exit 1 + fi +} + +link_logic() { + if [ ${mode} = "reg" ]; then + ln -s ${1} ${2} + else + rm -f ${2} + fi +} + +# +# Get the absolute path to a symbolic link's reference. +# +# Parameters: +# $* : path - the path to the file (link) to dereference (can have spaces in +# the path). +# +# Output: +# This function writes the path to the link reference to stdout. +# +# +dereference() { + path="$*" + result= + + # + # Make sure the path is absolute + # + parent="`cd \`dirname \"${path}\"\`; pwd -P`" + child="`basename \"${path}\"`" + + # + # if parent == child, then path == /, and is already absolute + # + if [ "${parent}" != "${child}" ]; then + path="${parent}/${child}" + fi + + if [ -h "${path}" ]; then + path=`ls -l "${path}" | sed -e "s#^.*${path} -> ##"` + + # make sure the path is still absolute (starts with '/') + if expr "${path}" : '[^/]' > /dev/null; then + path="${parent}/${path}" + fi + fi + + echo ${path} +} + +# +# Check for all the parts required to launch the control panel relative to the +# given path. +# +# +# Parameters: +# $* : path - the path to examine, presumably the resolved path to this +# script (can have spaces in the path). +# +# Output: +# If successful, this function outputs the absolute path to a directory +# containing the Java binary, and ../lib/deploy.jar; otherwise it outputs +# an empty string. (Output is to stdout.) +# +# Note: the assumption is that this function returns either: +# +# /jre/bin, or +# /bin +# +# However, as long as the directory pointed by the path returned by this +# function contains: +# +# ./java +# ../lib/deploy.jar +# +# it should be possible to successfully launch the JCP from the given +# information. +# +check_parts() { + result="`cd \`dirname \"$*\"\`; pwd -P`" + + # if this is a JDK, we need the JRE subdir + if [ -d "${result}/../jre/bin" ]; then + result="`cd \`dirname \"$*\"\`/../jre/bin; pwd -P`" + fi + + if [ ! -x "${result}/java" ] || [ ! -f "${result}/../lib/deploy.jar" ]; then + result= + fi + + echo ${result} +} + +# +# Launch the Java Control Panel. +# +# Parameters: +# $* : path - the path of this script (can have spaces in the path). +# +launch_jcp() { + path="$*" + while [ -h ${path} ]; do + path="`dereference ${path}`" + done + + java_home="`check_parts ${path}`" + if [ -n "${java_home}" ]; then + # launch the JCP using paths relative to + ${java_home}/java -Djavaplugin.user.profile=${USER_JPI_PROFILE} \ + -Xbootclasspath/a:${java_home}/../lib/deploy.jar \ + ${_JAVA_VM_OPTIONS} \ + com.sun.deploy.panel.ControlPanel + else + echo "${XLERROR}${java_home}" + exit 1 + fi +} + +# +# Manage the process of registering/unregistering the Java Plug-in with a given +# container (browser). +# +manage_container() { + # Do the "right" thing based on the provided scheme. + plugin_stem=${java_home}/plugin/${proc} + if [ ! -d ${plugin_stem} ]; then + echo "${JLERROR}${java_home}" + exit 1 + fi + + case ${scheme} in + ns4 | ns4E ) + plugin_location="${plugin_stem}/ns4" + if [ ${mode} = "reg" ]; then + echo "${plugin_location}" + fi + ;; + ns4L ) + plugin_location="${plugin_stem}/ns4" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + ns610 | ns610L ) + plugin_location="${plugin_stem}/ns610" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + * ) + echo ${ISERROR}${scheme} + exit 1 + esac +} + +while getopts ":r:u:c:j:" opt; do + case $opt in + r ) mode="reg";scheme=${OPTARG} + ;; + u ) mode="unreg";scheme=${OPTARG} + ;; + c ) container_home=${OPTARG} + ;; + j ) java_home=${OPTARG} + ;; + : ) echo ${USAGE} + exit 1 + ;; + \? ) echo ${USAGE} + exit 1 + ;; + esac +done + +os=`uname -s` +if [ "${os}" = "Linux" ]; then + case "`uname -m`" in + i[3-9]86 | ia32 | ia64 | x86_64) + proc=i386 + ;; + sparc*) + proc=sparc + ;; + arm*) + proc=arm + ;; + ppc*) + proc=ppc + ;; + *) + proc="`uname -m`" + ;; + esac +else + proc=`uname -p` +fi + +if [ -z "${scheme}" ] && + [ -z "${java_home}" ] && [ -z "${container_home}" ] +then + # just run the control panel + launch_jcp $0 +elif [ -n "${scheme}" ] && + [ -n "${java_home}" ] && [ -n "${container_home}" ] +then + # try to register/unregister the plugin + manage_container +else + # one or more missing args + echo ${USAGE} + exit 1 +fi diff --git a/jdk-1.8.0.281/bin/jdb b/jdk-1.8.0.281/bin/jdb new file mode 100755 index 0000000..e1675ef Binary files /dev/null and b/jdk-1.8.0.281/bin/jdb differ diff --git a/jdk-1.8.0.281/bin/jdeps b/jdk-1.8.0.281/bin/jdeps new file mode 100755 index 0000000..60a8cdd Binary files /dev/null and b/jdk-1.8.0.281/bin/jdeps differ diff --git a/jdk-1.8.0.281/bin/jhat b/jdk-1.8.0.281/bin/jhat new file mode 100755 index 0000000..f003387 Binary files /dev/null and b/jdk-1.8.0.281/bin/jhat differ diff --git a/jdk-1.8.0.281/bin/jinfo b/jdk-1.8.0.281/bin/jinfo new file mode 100755 index 0000000..d03f663 Binary files /dev/null and b/jdk-1.8.0.281/bin/jinfo differ diff --git a/jdk-1.8.0.281/bin/jjs b/jdk-1.8.0.281/bin/jjs new file mode 100755 index 0000000..2bd7f11 Binary files /dev/null and b/jdk-1.8.0.281/bin/jjs differ diff --git a/jdk-1.8.0.281/bin/jmap b/jdk-1.8.0.281/bin/jmap new file mode 100755 index 0000000..279addb Binary files /dev/null and b/jdk-1.8.0.281/bin/jmap differ diff --git a/jdk-1.8.0.281/bin/jps b/jdk-1.8.0.281/bin/jps new file mode 100755 index 0000000..9e2c28c Binary files /dev/null and b/jdk-1.8.0.281/bin/jps differ diff --git a/jdk-1.8.0.281/bin/jrunscript b/jdk-1.8.0.281/bin/jrunscript new file mode 100755 index 0000000..5319e7d Binary files /dev/null and b/jdk-1.8.0.281/bin/jrunscript differ diff --git a/jdk-1.8.0.281/bin/jsadebugd b/jdk-1.8.0.281/bin/jsadebugd new file mode 100755 index 0000000..97f7edc Binary files /dev/null and b/jdk-1.8.0.281/bin/jsadebugd differ diff --git a/jdk-1.8.0.281/bin/jstack b/jdk-1.8.0.281/bin/jstack new file mode 100755 index 0000000..beded26 Binary files /dev/null and b/jdk-1.8.0.281/bin/jstack differ diff --git a/jdk-1.8.0.281/bin/jstat b/jdk-1.8.0.281/bin/jstat new file mode 100755 index 0000000..4ba841d Binary files /dev/null and b/jdk-1.8.0.281/bin/jstat differ diff --git a/jdk-1.8.0.281/bin/jstatd b/jdk-1.8.0.281/bin/jstatd new file mode 100755 index 0000000..3b7501c Binary files /dev/null and b/jdk-1.8.0.281/bin/jstatd differ diff --git a/jdk-1.8.0.281/bin/jvisualvm b/jdk-1.8.0.281/bin/jvisualvm new file mode 100755 index 0000000..29dfbb1 --- /dev/null +++ b/jdk-1.8.0.281/bin/jvisualvm @@ -0,0 +1,201 @@ +#!/bin/sh +# +# Copyright (c) 2007, 2014, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# resolve symlinks +# + +PRG=$0 + +while [ -h "$PRG" ]; do + ls=`ls -ld "$PRG"` + link=`expr "$ls" : '^.*-> \(.*\)$' 2>/dev/null` + if expr "$link" : '^/' 2> /dev/null >/dev/null; then + PRG="$link" + else + PRG="`dirname "$PRG"`/$link" + fi +done + +progdir=`dirname "$PRG"` +old=`pwd` +cd "$progdir"/.. +basedir=`pwd` +cd "$old" + +case "`uname`" in + Darwin*) + # set default userdir and cachedir on Mac OS X + DEFAULT_USERDIR_ROOT="${HOME}/Library/Application Support/VisualVM" + DEFAULT_CACHEDIR_ROOT=${HOME}/Library/Caches/VisualVM + ;; + *) + # set default userdir and cachedir on unix systems + DEFAULT_USERDIR_ROOT=${HOME}/.visualvm + DEFAULT_CACHEDIR_ROOT=${HOME}/.cache/visualvm + ;; +esac + + +if [ -f "$progdir"/../lib/visualvm/etc/visualvm.conf ] ; then + visualvm_jdkhome="$basedir" + old=`pwd` + cd "$progdir/../lib/visualvm/" + basedir=`pwd` + cd "$old" + . "$progdir"/../lib/visualvm/etc/visualvm.conf +elif [ -f "$progdir"/../etc/visualvm.conf ] ; then + . "$progdir"/../etc/visualvm.conf +fi + + +export DEFAULT_USERDIR_ROOT + +# #68373: look for userdir, but do not modify "$@" +userdir="${visualvm_default_userdir}" +cachedir="${visualvm_default_cachedir}" + +founduserdir="" +for opt in "$@"; do + if [ "${founduserdir}" = "yes" ]; then + userdir="$opt" + break + elif [ "$opt" = "--userdir" ]; then + founduserdir="yes" + fi +done +foundcachedir="" +for opt in "$@"; do + if [ "${foundcachedir}" = "yes" ]; then + cachedir="$opt" + break + elif [ "$opt" = "--cachedir" ]; then + foundcachedir="yes" + fi +done + +if [ -f "${userdir}"/etc/visualvm.conf ] ; then + . "${userdir}"/etc/visualvm.conf +fi + + +if [ ! -f "$basedir"/etc/visualvm.clusters ]; then + echo Cannot read cluster file: "$basedir"/etc/visualvm.clusters 1>&2 + exit 1 +fi + +readClusters() { + grep -v "^#" "$basedir"/etc/visualvm.clusters | grep -v "^$" | grep -v platform | while read X; do + if expr "$X" : "/.*" >/dev/null; then + echo "$X" + else + echo "$basedir/$X" + fi + done +} + +absolutize_paths() { + while read path; do + if [ -d "$path" ]; then + (cd "$path" 2>/dev/null && pwd) + else + echo "$path" + fi + done +} + +visualvm_clusters=`readClusters | absolutize_paths | tr '\012' ':'` + +if [ ! -z "$visualvm_extraclusters" ] ; then + visualvm_clusters ="$visualvm_clusters:$visualvm_extraclusters" +fi + +heap_size () { + mem=640 + case "`uname`" in + Linux*) + mem=`cat /proc/meminfo | grep MemTotal | tr -d [:space:][:alpha:]:` + mem=`expr $mem / 1024` + ;; + SunOS*) + mem=`/usr/sbin/prtconf | grep Memory | /usr/bin/tr -dc '[0-9]'` + ;; + Darwin*) + mem=`/usr/sbin/sysctl hw.memsize | tr -d [:alpha:][:space:].:` + mem=`expr $mem / 1048576` + ;; + *) + ;; + esac + if [ -z "$mem" ] ; then + mem=640 + fi + mem=`expr $mem / 5` + if [ $mem -gt 1024 ] ; then + mem=1024 + elif [ $mem -lt 96 ] ; then + mem=96 + fi + max_heap_size=$mem + return 0 +} + + +if grep -v -- "-J-Xmx" >/dev/null </dev/null; then + echo $X/lib/nbexec + elif [ -f "$basedir"/$X/lib/nbexec ]; then + echo "$basedir"/$X/lib/nbexec + fi + done | head -n 1` + if [ \! -n "$nbexec" ] ; then + nbexec="$basedir"/platform/lib/nbexec + fi + sh=sh + # #73162: Ubuntu uses the ancient Bourne shell, which does not implement trap well. + if [ -x /bin/bash ] + then + sh=/bin/bash + fi + if [ "${founduserdir}" = "yes" ]; then + exec $sh "$nbexec" "$@" + else + if [ "${foundcachedir}" = "yes" ]; then + exec $sh "$nbexec" --userdir "${userdir}" "$@" + else + exec $sh "$nbexec" --userdir "${userdir}" --cachedir "${cachedir}" "$@" + fi + fi +} + +# in case of macosx, the apple.laf.useScreenMenuBar property should be ideally in the Info.plist file +# but it doesn't get propagated into the executed java VM. +case "`uname`" in + Darwin*) + eval launchNbexec \ + --jdkhome '"$visualvm_jdkhome"' \ + -J-Xdock:name=VisualVM \ + '"-J-Xdock:icon=$basedir/etc/visualvm.icns"' \ + --branding visualvm \ + --clusters '"$visualvm_clusters"' \ + ${visualvm_default_options} \ + '"$@"' + ;; + *) + eval launchNbexec \ + --jdkhome '"$visualvm_jdkhome"' \ + --branding visualvm \ + --clusters '"$visualvm_clusters"' \ + ${visualvm_default_options} \ + '"$@"' + ;; +esac diff --git a/jdk-1.8.0.281/bin/keytool b/jdk-1.8.0.281/bin/keytool new file mode 100755 index 0000000..c8acf21 Binary files /dev/null and b/jdk-1.8.0.281/bin/keytool differ diff --git a/jdk-1.8.0.281/bin/native2ascii b/jdk-1.8.0.281/bin/native2ascii new file mode 100755 index 0000000..55d93a0 Binary files /dev/null and b/jdk-1.8.0.281/bin/native2ascii differ diff --git a/jdk-1.8.0.281/bin/orbd b/jdk-1.8.0.281/bin/orbd new file mode 100755 index 0000000..81422f5 Binary files /dev/null and b/jdk-1.8.0.281/bin/orbd differ diff --git a/jdk-1.8.0.281/bin/pack200 b/jdk-1.8.0.281/bin/pack200 new file mode 100755 index 0000000..290798a Binary files /dev/null and b/jdk-1.8.0.281/bin/pack200 differ diff --git a/jdk-1.8.0.281/bin/policytool b/jdk-1.8.0.281/bin/policytool new file mode 100755 index 0000000..eea9a1c Binary files /dev/null and b/jdk-1.8.0.281/bin/policytool differ diff --git a/jdk-1.8.0.281/bin/rmic b/jdk-1.8.0.281/bin/rmic new file mode 100755 index 0000000..9bd9bc3 Binary files /dev/null and b/jdk-1.8.0.281/bin/rmic differ diff --git a/jdk-1.8.0.281/bin/rmid b/jdk-1.8.0.281/bin/rmid new file mode 100755 index 0000000..96ea921 Binary files /dev/null and b/jdk-1.8.0.281/bin/rmid differ diff --git a/jdk-1.8.0.281/bin/rmiregistry b/jdk-1.8.0.281/bin/rmiregistry new file mode 100755 index 0000000..9a7874d Binary files /dev/null and b/jdk-1.8.0.281/bin/rmiregistry differ diff --git a/jdk-1.8.0.281/bin/schemagen b/jdk-1.8.0.281/bin/schemagen new file mode 100755 index 0000000..72d562f Binary files /dev/null and b/jdk-1.8.0.281/bin/schemagen differ diff --git a/jdk-1.8.0.281/bin/serialver b/jdk-1.8.0.281/bin/serialver new file mode 100755 index 0000000..67f7582 Binary files /dev/null and b/jdk-1.8.0.281/bin/serialver differ diff --git a/jdk-1.8.0.281/bin/servertool b/jdk-1.8.0.281/bin/servertool new file mode 100755 index 0000000..bd3bd9a Binary files /dev/null and b/jdk-1.8.0.281/bin/servertool differ diff --git a/jdk-1.8.0.281/bin/tnameserv b/jdk-1.8.0.281/bin/tnameserv new file mode 100755 index 0000000..29216a8 Binary files /dev/null and b/jdk-1.8.0.281/bin/tnameserv differ diff --git a/jdk-1.8.0.281/bin/unpack200 b/jdk-1.8.0.281/bin/unpack200 new file mode 100755 index 0000000..a90e02a Binary files /dev/null and b/jdk-1.8.0.281/bin/unpack200 differ diff --git a/jdk-1.8.0.281/bin/wsgen b/jdk-1.8.0.281/bin/wsgen new file mode 100755 index 0000000..d772d60 Binary files /dev/null and b/jdk-1.8.0.281/bin/wsgen differ diff --git a/jdk-1.8.0.281/bin/wsimport b/jdk-1.8.0.281/bin/wsimport new file mode 100755 index 0000000..3f685b7 Binary files /dev/null and b/jdk-1.8.0.281/bin/wsimport differ diff --git a/jdk-1.8.0.281/bin/xjc b/jdk-1.8.0.281/bin/xjc new file mode 100755 index 0000000..97808ee Binary files /dev/null and b/jdk-1.8.0.281/bin/xjc differ diff --git a/jdk-1.8.0.281/include/classfile_constants.h b/jdk-1.8.0.281/include/classfile_constants.h new file mode 100755 index 0000000..e5c20cd --- /dev/null +++ b/jdk-1.8.0.281/include/classfile_constants.h @@ -0,0 +1,560 @@ +/* + * Copyright (c) 2004, 2012, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +#ifndef CLASSFILE_CONSTANTS_H +#define CLASSFILE_CONSTANTS_H + +#ifdef __cplusplus +extern "C" { +#endif + +/* Classfile version number for this information */ +#define JVM_CLASSFILE_MAJOR_VERSION 52 +#define JVM_CLASSFILE_MINOR_VERSION 0 + +/* Flags */ + +enum { + JVM_ACC_PUBLIC = 0x0001, + JVM_ACC_PRIVATE = 0x0002, + JVM_ACC_PROTECTED = 0x0004, + JVM_ACC_STATIC = 0x0008, + JVM_ACC_FINAL = 0x0010, + JVM_ACC_SYNCHRONIZED = 0x0020, + JVM_ACC_SUPER = 0x0020, + JVM_ACC_VOLATILE = 0x0040, + JVM_ACC_BRIDGE = 0x0040, + JVM_ACC_TRANSIENT = 0x0080, + JVM_ACC_VARARGS = 0x0080, + JVM_ACC_NATIVE = 0x0100, + JVM_ACC_INTERFACE = 0x0200, + JVM_ACC_ABSTRACT = 0x0400, + JVM_ACC_STRICT = 0x0800, + JVM_ACC_SYNTHETIC = 0x1000, + JVM_ACC_ANNOTATION = 0x2000, + JVM_ACC_ENUM = 0x4000 +}; + +/* Used in newarray instruction. */ + +enum { + JVM_T_BOOLEAN = 4, + JVM_T_CHAR = 5, + JVM_T_FLOAT = 6, + JVM_T_DOUBLE = 7, + JVM_T_BYTE = 8, + JVM_T_SHORT = 9, + JVM_T_INT = 10, + JVM_T_LONG = 11 +}; + +/* Constant Pool Entries */ + +enum { + JVM_CONSTANT_Utf8 = 1, + JVM_CONSTANT_Unicode = 2, /* unused */ + JVM_CONSTANT_Integer = 3, + JVM_CONSTANT_Float = 4, + JVM_CONSTANT_Long = 5, + JVM_CONSTANT_Double = 6, + JVM_CONSTANT_Class = 7, + JVM_CONSTANT_String = 8, + JVM_CONSTANT_Fieldref = 9, + JVM_CONSTANT_Methodref = 10, + JVM_CONSTANT_InterfaceMethodref = 11, + JVM_CONSTANT_NameAndType = 12, + JVM_CONSTANT_MethodHandle = 15, // JSR 292 + JVM_CONSTANT_MethodType = 16, // JSR 292 + JVM_CONSTANT_InvokeDynamic = 18 +}; + +/* JVM_CONSTANT_MethodHandle subtypes */ +enum { + JVM_REF_getField = 1, + JVM_REF_getStatic = 2, + JVM_REF_putField = 3, + JVM_REF_putStatic = 4, + JVM_REF_invokeVirtual = 5, + JVM_REF_invokeStatic = 6, + JVM_REF_invokeSpecial = 7, + JVM_REF_newInvokeSpecial = 8, + JVM_REF_invokeInterface = 9 +}; + +/* StackMapTable type item numbers */ + +enum { + JVM_ITEM_Top = 0, + JVM_ITEM_Integer = 1, + JVM_ITEM_Float = 2, + JVM_ITEM_Double = 3, + JVM_ITEM_Long = 4, + JVM_ITEM_Null = 5, + JVM_ITEM_UninitializedThis = 6, + JVM_ITEM_Object = 7, + JVM_ITEM_Uninitialized = 8 +}; + +/* Type signatures */ + +enum { + JVM_SIGNATURE_ARRAY = '[', + JVM_SIGNATURE_BYTE = 'B', + JVM_SIGNATURE_CHAR = 'C', + JVM_SIGNATURE_CLASS = 'L', + JVM_SIGNATURE_ENDCLASS = ';', + JVM_SIGNATURE_ENUM = 'E', + JVM_SIGNATURE_FLOAT = 'F', + JVM_SIGNATURE_DOUBLE = 'D', + JVM_SIGNATURE_FUNC = '(', + JVM_SIGNATURE_ENDFUNC = ')', + JVM_SIGNATURE_INT = 'I', + JVM_SIGNATURE_LONG = 'J', + JVM_SIGNATURE_SHORT = 'S', + JVM_SIGNATURE_VOID = 'V', + JVM_SIGNATURE_BOOLEAN = 'Z' +}; + +/* Opcodes */ + +enum { + JVM_OPC_nop = 0, + JVM_OPC_aconst_null = 1, + JVM_OPC_iconst_m1 = 2, + JVM_OPC_iconst_0 = 3, + JVM_OPC_iconst_1 = 4, + JVM_OPC_iconst_2 = 5, + JVM_OPC_iconst_3 = 6, + JVM_OPC_iconst_4 = 7, + JVM_OPC_iconst_5 = 8, + JVM_OPC_lconst_0 = 9, + JVM_OPC_lconst_1 = 10, + JVM_OPC_fconst_0 = 11, + JVM_OPC_fconst_1 = 12, + JVM_OPC_fconst_2 = 13, + JVM_OPC_dconst_0 = 14, + JVM_OPC_dconst_1 = 15, + JVM_OPC_bipush = 16, + JVM_OPC_sipush = 17, + JVM_OPC_ldc = 18, + JVM_OPC_ldc_w = 19, + JVM_OPC_ldc2_w = 20, + JVM_OPC_iload = 21, + JVM_OPC_lload = 22, + JVM_OPC_fload = 23, + JVM_OPC_dload = 24, + JVM_OPC_aload = 25, + JVM_OPC_iload_0 = 26, + JVM_OPC_iload_1 = 27, + JVM_OPC_iload_2 = 28, + JVM_OPC_iload_3 = 29, + JVM_OPC_lload_0 = 30, + JVM_OPC_lload_1 = 31, + JVM_OPC_lload_2 = 32, + JVM_OPC_lload_3 = 33, + JVM_OPC_fload_0 = 34, + JVM_OPC_fload_1 = 35, + JVM_OPC_fload_2 = 36, + JVM_OPC_fload_3 = 37, + JVM_OPC_dload_0 = 38, + JVM_OPC_dload_1 = 39, + JVM_OPC_dload_2 = 40, + JVM_OPC_dload_3 = 41, + JVM_OPC_aload_0 = 42, + JVM_OPC_aload_1 = 43, + JVM_OPC_aload_2 = 44, + JVM_OPC_aload_3 = 45, + JVM_OPC_iaload = 46, + JVM_OPC_laload = 47, + JVM_OPC_faload = 48, + JVM_OPC_daload = 49, + JVM_OPC_aaload = 50, + JVM_OPC_baload = 51, + JVM_OPC_caload = 52, + JVM_OPC_saload = 53, + JVM_OPC_istore = 54, + JVM_OPC_lstore = 55, + JVM_OPC_fstore = 56, + JVM_OPC_dstore = 57, + JVM_OPC_astore = 58, + JVM_OPC_istore_0 = 59, + JVM_OPC_istore_1 = 60, + JVM_OPC_istore_2 = 61, + JVM_OPC_istore_3 = 62, + JVM_OPC_lstore_0 = 63, + JVM_OPC_lstore_1 = 64, + JVM_OPC_lstore_2 = 65, + JVM_OPC_lstore_3 = 66, + JVM_OPC_fstore_0 = 67, + JVM_OPC_fstore_1 = 68, + JVM_OPC_fstore_2 = 69, + JVM_OPC_fstore_3 = 70, + JVM_OPC_dstore_0 = 71, + JVM_OPC_dstore_1 = 72, + JVM_OPC_dstore_2 = 73, + JVM_OPC_dstore_3 = 74, + JVM_OPC_astore_0 = 75, + JVM_OPC_astore_1 = 76, + JVM_OPC_astore_2 = 77, + JVM_OPC_astore_3 = 78, + JVM_OPC_iastore = 79, + JVM_OPC_lastore = 80, + JVM_OPC_fastore = 81, + JVM_OPC_dastore = 82, + JVM_OPC_aastore = 83, + JVM_OPC_bastore = 84, + JVM_OPC_castore = 85, + JVM_OPC_sastore = 86, + JVM_OPC_pop = 87, + JVM_OPC_pop2 = 88, + JVM_OPC_dup = 89, + JVM_OPC_dup_x1 = 90, + JVM_OPC_dup_x2 = 91, + JVM_OPC_dup2 = 92, + JVM_OPC_dup2_x1 = 93, + JVM_OPC_dup2_x2 = 94, + JVM_OPC_swap = 95, + JVM_OPC_iadd = 96, + JVM_OPC_ladd = 97, + JVM_OPC_fadd = 98, + JVM_OPC_dadd = 99, + JVM_OPC_isub = 100, + JVM_OPC_lsub = 101, + JVM_OPC_fsub = 102, + JVM_OPC_dsub = 103, + JVM_OPC_imul = 104, + JVM_OPC_lmul = 105, + JVM_OPC_fmul = 106, + JVM_OPC_dmul = 107, + JVM_OPC_idiv = 108, + JVM_OPC_ldiv = 109, + JVM_OPC_fdiv = 110, + JVM_OPC_ddiv = 111, + JVM_OPC_irem = 112, + JVM_OPC_lrem = 113, + JVM_OPC_frem = 114, + JVM_OPC_drem = 115, + JVM_OPC_ineg = 116, + JVM_OPC_lneg = 117, + JVM_OPC_fneg = 118, + JVM_OPC_dneg = 119, + JVM_OPC_ishl = 120, + JVM_OPC_lshl = 121, + JVM_OPC_ishr = 122, + JVM_OPC_lshr = 123, + JVM_OPC_iushr = 124, + JVM_OPC_lushr = 125, + JVM_OPC_iand = 126, + JVM_OPC_land = 127, + JVM_OPC_ior = 128, + JVM_OPC_lor = 129, + JVM_OPC_ixor = 130, + JVM_OPC_lxor = 131, + JVM_OPC_iinc = 132, + JVM_OPC_i2l = 133, + JVM_OPC_i2f = 134, + JVM_OPC_i2d = 135, + JVM_OPC_l2i = 136, + JVM_OPC_l2f = 137, + JVM_OPC_l2d = 138, + JVM_OPC_f2i = 139, + JVM_OPC_f2l = 140, + JVM_OPC_f2d = 141, + JVM_OPC_d2i = 142, + JVM_OPC_d2l = 143, + JVM_OPC_d2f = 144, + JVM_OPC_i2b = 145, + JVM_OPC_i2c = 146, + JVM_OPC_i2s = 147, + JVM_OPC_lcmp = 148, + JVM_OPC_fcmpl = 149, + JVM_OPC_fcmpg = 150, + JVM_OPC_dcmpl = 151, + JVM_OPC_dcmpg = 152, + JVM_OPC_ifeq = 153, + JVM_OPC_ifne = 154, + JVM_OPC_iflt = 155, + JVM_OPC_ifge = 156, + JVM_OPC_ifgt = 157, + JVM_OPC_ifle = 158, + JVM_OPC_if_icmpeq = 159, + JVM_OPC_if_icmpne = 160, + JVM_OPC_if_icmplt = 161, + JVM_OPC_if_icmpge = 162, + JVM_OPC_if_icmpgt = 163, + JVM_OPC_if_icmple = 164, + JVM_OPC_if_acmpeq = 165, + JVM_OPC_if_acmpne = 166, + JVM_OPC_goto = 167, + JVM_OPC_jsr = 168, + JVM_OPC_ret = 169, + JVM_OPC_tableswitch = 170, + JVM_OPC_lookupswitch = 171, + JVM_OPC_ireturn = 172, + JVM_OPC_lreturn = 173, + JVM_OPC_freturn = 174, + JVM_OPC_dreturn = 175, + JVM_OPC_areturn = 176, + JVM_OPC_return = 177, + JVM_OPC_getstatic = 178, + JVM_OPC_putstatic = 179, + JVM_OPC_getfield = 180, + JVM_OPC_putfield = 181, + JVM_OPC_invokevirtual = 182, + JVM_OPC_invokespecial = 183, + JVM_OPC_invokestatic = 184, + JVM_OPC_invokeinterface = 185, + JVM_OPC_invokedynamic = 186, + JVM_OPC_new = 187, + JVM_OPC_newarray = 188, + JVM_OPC_anewarray = 189, + JVM_OPC_arraylength = 190, + JVM_OPC_athrow = 191, + JVM_OPC_checkcast = 192, + JVM_OPC_instanceof = 193, + JVM_OPC_monitorenter = 194, + JVM_OPC_monitorexit = 195, + JVM_OPC_wide = 196, + JVM_OPC_multianewarray = 197, + JVM_OPC_ifnull = 198, + JVM_OPC_ifnonnull = 199, + JVM_OPC_goto_w = 200, + JVM_OPC_jsr_w = 201, + JVM_OPC_MAX = 201 +}; + +/* Opcode length initializer, use with something like: + * unsigned char opcode_length[JVM_OPC_MAX+1] = JVM_OPCODE_LENGTH_INITIALIZER; + */ +#define JVM_OPCODE_LENGTH_INITIALIZER { \ + 1, /* nop */ \ + 1, /* aconst_null */ \ + 1, /* iconst_m1 */ \ + 1, /* iconst_0 */ \ + 1, /* iconst_1 */ \ + 1, /* iconst_2 */ \ + 1, /* iconst_3 */ \ + 1, /* iconst_4 */ \ + 1, /* iconst_5 */ \ + 1, /* lconst_0 */ \ + 1, /* lconst_1 */ \ + 1, /* fconst_0 */ \ + 1, /* fconst_1 */ \ + 1, /* fconst_2 */ \ + 1, /* dconst_0 */ \ + 1, /* dconst_1 */ \ + 2, /* bipush */ \ + 3, /* sipush */ \ + 2, /* ldc */ \ + 3, /* ldc_w */ \ + 3, /* ldc2_w */ \ + 2, /* iload */ \ + 2, /* lload */ \ + 2, /* fload */ \ + 2, /* dload */ \ + 2, /* aload */ \ + 1, /* iload_0 */ \ + 1, /* iload_1 */ \ + 1, /* iload_2 */ \ + 1, /* iload_3 */ \ + 1, /* lload_0 */ \ + 1, /* lload_1 */ \ + 1, /* lload_2 */ \ + 1, /* lload_3 */ \ + 1, /* fload_0 */ \ + 1, /* fload_1 */ \ + 1, /* fload_2 */ \ + 1, /* fload_3 */ \ + 1, /* dload_0 */ \ + 1, /* dload_1 */ \ + 1, /* dload_2 */ \ + 1, /* dload_3 */ \ + 1, /* aload_0 */ \ + 1, /* aload_1 */ \ + 1, /* aload_2 */ \ + 1, /* aload_3 */ \ + 1, /* iaload */ \ + 1, /* laload */ \ + 1, /* faload */ \ + 1, /* daload */ \ + 1, /* aaload */ \ + 1, /* baload */ \ + 1, /* caload */ \ + 1, /* saload */ \ + 2, /* istore */ \ + 2, /* lstore */ \ + 2, /* fstore */ \ + 2, /* dstore */ \ + 2, /* astore */ \ + 1, /* istore_0 */ \ + 1, /* istore_1 */ \ + 1, /* istore_2 */ \ + 1, /* istore_3 */ \ + 1, /* lstore_0 */ \ + 1, /* lstore_1 */ \ + 1, /* lstore_2 */ \ + 1, /* lstore_3 */ \ + 1, /* fstore_0 */ \ + 1, /* fstore_1 */ \ + 1, /* fstore_2 */ \ + 1, /* fstore_3 */ \ + 1, /* dstore_0 */ \ + 1, /* dstore_1 */ \ + 1, /* dstore_2 */ \ + 1, /* dstore_3 */ \ + 1, /* astore_0 */ \ + 1, /* astore_1 */ \ + 1, /* astore_2 */ \ + 1, /* astore_3 */ \ + 1, /* iastore */ \ + 1, /* lastore */ \ + 1, /* fastore */ \ + 1, /* dastore */ \ + 1, /* aastore */ \ + 1, /* bastore */ \ + 1, /* castore */ \ + 1, /* sastore */ \ + 1, /* pop */ \ + 1, /* pop2 */ \ + 1, /* dup */ \ + 1, /* dup_x1 */ \ + 1, /* dup_x2 */ \ + 1, /* dup2 */ \ + 1, /* dup2_x1 */ \ + 1, /* dup2_x2 */ \ + 1, /* swap */ \ + 1, /* iadd */ \ + 1, /* ladd */ \ + 1, /* fadd */ \ + 1, /* dadd */ \ + 1, /* isub */ \ + 1, /* lsub */ \ + 1, /* fsub */ \ + 1, /* dsub */ \ + 1, /* imul */ \ + 1, /* lmul */ \ + 1, /* fmul */ \ + 1, /* dmul */ \ + 1, /* idiv */ \ + 1, /* ldiv */ \ + 1, /* fdiv */ \ + 1, /* ddiv */ \ + 1, /* irem */ \ + 1, /* lrem */ \ + 1, /* frem */ \ + 1, /* drem */ \ + 1, /* ineg */ \ + 1, /* lneg */ \ + 1, /* fneg */ \ + 1, /* dneg */ \ + 1, /* ishl */ \ + 1, /* lshl */ \ + 1, /* ishr */ \ + 1, /* lshr */ \ + 1, /* iushr */ \ + 1, /* lushr */ \ + 1, /* iand */ \ + 1, /* land */ \ + 1, /* ior */ \ + 1, /* lor */ \ + 1, /* ixor */ \ + 1, /* lxor */ \ + 3, /* iinc */ \ + 1, /* i2l */ \ + 1, /* i2f */ \ + 1, /* i2d */ \ + 1, /* l2i */ \ + 1, /* l2f */ \ + 1, /* l2d */ \ + 1, /* f2i */ \ + 1, /* f2l */ \ + 1, /* f2d */ \ + 1, /* d2i */ \ + 1, /* d2l */ \ + 1, /* d2f */ \ + 1, /* i2b */ \ + 1, /* i2c */ \ + 1, /* i2s */ \ + 1, /* lcmp */ \ + 1, /* fcmpl */ \ + 1, /* fcmpg */ \ + 1, /* dcmpl */ \ + 1, /* dcmpg */ \ + 3, /* ifeq */ \ + 3, /* ifne */ \ + 3, /* iflt */ \ + 3, /* ifge */ \ + 3, /* ifgt */ \ + 3, /* ifle */ \ + 3, /* if_icmpeq */ \ + 3, /* if_icmpne */ \ + 3, /* if_icmplt */ \ + 3, /* if_icmpge */ \ + 3, /* if_icmpgt */ \ + 3, /* if_icmple */ \ + 3, /* if_acmpeq */ \ + 3, /* if_acmpne */ \ + 3, /* goto */ \ + 3, /* jsr */ \ + 2, /* ret */ \ + 99, /* tableswitch */ \ + 99, /* lookupswitch */ \ + 1, /* ireturn */ \ + 1, /* lreturn */ \ + 1, /* freturn */ \ + 1, /* dreturn */ \ + 1, /* areturn */ \ + 1, /* return */ \ + 3, /* getstatic */ \ + 3, /* putstatic */ \ + 3, /* getfield */ \ + 3, /* putfield */ \ + 3, /* invokevirtual */ \ + 3, /* invokespecial */ \ + 3, /* invokestatic */ \ + 5, /* invokeinterface */ \ + 5, /* invokedynamic */ \ + 3, /* new */ \ + 2, /* newarray */ \ + 3, /* anewarray */ \ + 1, /* arraylength */ \ + 1, /* athrow */ \ + 3, /* checkcast */ \ + 3, /* instanceof */ \ + 1, /* monitorenter */ \ + 1, /* monitorexit */ \ + 0, /* wide */ \ + 4, /* multianewarray */ \ + 3, /* ifnull */ \ + 3, /* ifnonnull */ \ + 5, /* goto_w */ \ + 5 /* jsr_w */ \ +} + +#ifdef __cplusplus +} /* extern "C" */ +#endif /* __cplusplus */ + +#endif /* CLASSFILE_CONSTANTS */ diff --git a/jdk-1.8.0.281/include/jawt.h b/jdk-1.8.0.281/include/jawt.h new file mode 100755 index 0000000..f06e807 --- /dev/null +++ b/jdk-1.8.0.281/include/jawt.h @@ -0,0 +1,299 @@ +/* + * Copyright (c) 1999, 2013, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +#ifndef _JAVASOFT_JAWT_H_ +#define _JAVASOFT_JAWT_H_ + +#include "jni.h" + +#ifdef __cplusplus +extern "C" { +#endif + +/* + * AWT native interface (new in JDK 1.3) + * + * The AWT native interface allows a native C or C++ application a means + * by which to access native structures in AWT. This is to facilitate moving + * legacy C and C++ applications to Java and to target the needs of the + * community who, at present, wish to do their own native rendering to canvases + * for performance reasons. Standard extensions such as Java3D also require a + * means to access the underlying native data structures of AWT. + * + * There may be future extensions to this API depending on demand. + * + * A VM does not have to implement this API in order to pass the JCK. + * It is recommended, however, that this API is implemented on VMs that support + * standard extensions, such as Java3D. + * + * Since this is a native API, any program which uses it cannot be considered + * 100% pure java. + */ + +/* + * AWT Native Drawing Surface (JAWT_DrawingSurface). + * + * For each platform, there is a native drawing surface structure. This + * platform-specific structure can be found in jawt_md.h. It is recommended + * that additional platforms follow the same model. It is also recommended + * that VMs on Win32 and Solaris support the existing structures in jawt_md.h. + * + ******************* + * EXAMPLE OF USAGE: + ******************* + * + * In Win32, a programmer wishes to access the HWND of a canvas to perform + * native rendering into it. The programmer has declared the paint() method + * for their canvas subclass to be native: + * + * + * MyCanvas.java: + * + * import java.awt.*; + * + * public class MyCanvas extends Canvas { + * + * static { + * System.loadLibrary("mylib"); + * } + * + * public native void paint(Graphics g); + * } + * + * + * myfile.c: + * + * #include "jawt_md.h" + * #include + * + * JNIEXPORT void JNICALL + * Java_MyCanvas_paint(JNIEnv* env, jobject canvas, jobject graphics) + * { + * JAWT awt; + * JAWT_DrawingSurface* ds; + * JAWT_DrawingSurfaceInfo* dsi; + * JAWT_Win32DrawingSurfaceInfo* dsi_win; + * jboolean result; + * jint lock; + * + * // Get the AWT + * awt.version = JAWT_VERSION_1_3; + * result = JAWT_GetAWT(env, &awt); + * assert(result != JNI_FALSE); + * + * // Get the drawing surface + * ds = awt.GetDrawingSurface(env, canvas); + * assert(ds != NULL); + * + * // Lock the drawing surface + * lock = ds->Lock(ds); + * assert((lock & JAWT_LOCK_ERROR) == 0); + * + * // Get the drawing surface info + * dsi = ds->GetDrawingSurfaceInfo(ds); + * + * // Get the platform-specific drawing info + * dsi_win = (JAWT_Win32DrawingSurfaceInfo*)dsi->platformInfo; + * + * ////////////////////////////// + * // !!! DO PAINTING HERE !!! // + * ////////////////////////////// + * + * // Free the drawing surface info + * ds->FreeDrawingSurfaceInfo(dsi); + * + * // Unlock the drawing surface + * ds->Unlock(ds); + * + * // Free the drawing surface + * awt.FreeDrawingSurface(ds); + * } + * + */ + +/* + * JAWT_Rectangle + * Structure for a native rectangle. + */ +typedef struct jawt_Rectangle { + jint x; + jint y; + jint width; + jint height; +} JAWT_Rectangle; + +struct jawt_DrawingSurface; + +/* + * JAWT_DrawingSurfaceInfo + * Structure for containing the underlying drawing information of a component. + */ +typedef struct jawt_DrawingSurfaceInfo { + /* + * Pointer to the platform-specific information. This can be safely + * cast to a JAWT_Win32DrawingSurfaceInfo on Windows or a + * JAWT_X11DrawingSurfaceInfo on Solaris. On Mac OS X this is a + * pointer to a NSObject that conforms to the JAWT_SurfaceLayers + * protocol. See jawt_md.h for details. + */ + void* platformInfo; + /* Cached pointer to the underlying drawing surface */ + struct jawt_DrawingSurface* ds; + /* Bounding rectangle of the drawing surface */ + JAWT_Rectangle bounds; + /* Number of rectangles in the clip */ + jint clipSize; + /* Clip rectangle array */ + JAWT_Rectangle* clip; +} JAWT_DrawingSurfaceInfo; + +#define JAWT_LOCK_ERROR 0x00000001 +#define JAWT_LOCK_CLIP_CHANGED 0x00000002 +#define JAWT_LOCK_BOUNDS_CHANGED 0x00000004 +#define JAWT_LOCK_SURFACE_CHANGED 0x00000008 + +/* + * JAWT_DrawingSurface + * Structure for containing the underlying drawing information of a component. + * All operations on a JAWT_DrawingSurface MUST be performed from the same + * thread as the call to GetDrawingSurface. + */ +typedef struct jawt_DrawingSurface { + /* + * Cached reference to the Java environment of the calling thread. + * If Lock(), Unlock(), GetDrawingSurfaceInfo() or + * FreeDrawingSurfaceInfo() are called from a different thread, + * this data member should be set before calling those functions. + */ + JNIEnv* env; + /* Cached reference to the target object */ + jobject target; + /* + * Lock the surface of the target component for native rendering. + * When finished drawing, the surface must be unlocked with + * Unlock(). This function returns a bitmask with one or more of the + * following values: + * + * JAWT_LOCK_ERROR - When an error has occurred and the surface could not + * be locked. + * + * JAWT_LOCK_CLIP_CHANGED - When the clip region has changed. + * + * JAWT_LOCK_BOUNDS_CHANGED - When the bounds of the surface have changed. + * + * JAWT_LOCK_SURFACE_CHANGED - When the surface itself has changed + */ + jint (JNICALL *Lock) + (struct jawt_DrawingSurface* ds); + /* + * Get the drawing surface info. + * The value returned may be cached, but the values may change if + * additional calls to Lock() or Unlock() are made. + * Lock() must be called before this can return a valid value. + * Returns NULL if an error has occurred. + * When finished with the returned value, FreeDrawingSurfaceInfo must be + * called. + */ + JAWT_DrawingSurfaceInfo* (JNICALL *GetDrawingSurfaceInfo) + (struct jawt_DrawingSurface* ds); + /* + * Free the drawing surface info. + */ + void (JNICALL *FreeDrawingSurfaceInfo) + (JAWT_DrawingSurfaceInfo* dsi); + /* + * Unlock the drawing surface of the target component for native rendering. + */ + void (JNICALL *Unlock) + (struct jawt_DrawingSurface* ds); +} JAWT_DrawingSurface; + +/* + * JAWT + * Structure for containing native AWT functions. + */ +typedef struct jawt { + /* + * Version of this structure. This must always be set before + * calling JAWT_GetAWT() + */ + jint version; + /* + * Return a drawing surface from a target jobject. This value + * may be cached. + * Returns NULL if an error has occurred. + * Target must be a java.awt.Component (should be a Canvas + * or Window for native rendering). + * FreeDrawingSurface() must be called when finished with the + * returned JAWT_DrawingSurface. + */ + JAWT_DrawingSurface* (JNICALL *GetDrawingSurface) + (JNIEnv* env, jobject target); + /* + * Free the drawing surface allocated in GetDrawingSurface. + */ + void (JNICALL *FreeDrawingSurface) + (JAWT_DrawingSurface* ds); + /* + * Since 1.4 + * Locks the entire AWT for synchronization purposes + */ + void (JNICALL *Lock)(JNIEnv* env); + /* + * Since 1.4 + * Unlocks the entire AWT for synchronization purposes + */ + void (JNICALL *Unlock)(JNIEnv* env); + /* + * Since 1.4 + * Returns a reference to a java.awt.Component from a native + * platform handle. On Windows, this corresponds to an HWND; + * on Solaris and Linux, this is a Drawable. For other platforms, + * see the appropriate machine-dependent header file for a description. + * The reference returned by this function is a local + * reference that is only valid in this environment. + * This function returns a NULL reference if no component could be + * found with matching platform information. + */ + jobject (JNICALL *GetComponent)(JNIEnv* env, void* platformInfo); + +} JAWT; + +/* + * Get the AWT native structure. This function returns JNI_FALSE if + * an error occurs. + */ +_JNI_IMPORT_OR_EXPORT_ +jboolean JNICALL JAWT_GetAWT(JNIEnv* env, JAWT* awt); + +#define JAWT_VERSION_1_3 0x00010003 +#define JAWT_VERSION_1_4 0x00010004 +#define JAWT_VERSION_1_7 0x00010007 + +#ifdef __cplusplus +} /* extern "C" */ +#endif + +#endif /* !_JAVASOFT_JAWT_H_ */ diff --git a/jdk-1.8.0.281/include/jdwpTransport.h b/jdk-1.8.0.281/include/jdwpTransport.h new file mode 100755 index 0000000..4f4b92e --- /dev/null +++ b/jdk-1.8.0.281/include/jdwpTransport.h @@ -0,0 +1,259 @@ +/* + * Copyright (c) 2003, 2016, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +/* + * Java Debug Wire Protocol Transport Service Provider Interface. + */ + +#ifndef JDWPTRANSPORT_H +#define JDWPTRANSPORT_H + +#include "jni.h" + +enum { + JDWPTRANSPORT_VERSION_1_0 = 0x00010000 +}; + +#ifdef __cplusplus +extern "C" { +#endif + +struct jdwpTransportNativeInterface_; + +struct _jdwpTransportEnv; + +#ifdef __cplusplus +typedef _jdwpTransportEnv jdwpTransportEnv; +#else +typedef const struct jdwpTransportNativeInterface_ *jdwpTransportEnv; +#endif /* __cplusplus */ + +/* + * Errors. Universal errors with JVMTI/JVMDI equivalents keep the + * values the same. + */ +typedef enum { + JDWPTRANSPORT_ERROR_NONE = 0, + JDWPTRANSPORT_ERROR_ILLEGAL_ARGUMENT = 103, + JDWPTRANSPORT_ERROR_OUT_OF_MEMORY = 110, + JDWPTRANSPORT_ERROR_INTERNAL = 113, + JDWPTRANSPORT_ERROR_ILLEGAL_STATE = 201, + JDWPTRANSPORT_ERROR_IO_ERROR = 202, + JDWPTRANSPORT_ERROR_TIMEOUT = 203, + JDWPTRANSPORT_ERROR_MSG_NOT_AVAILABLE = 204 +} jdwpTransportError; + + +/* + * Structure to define capabilities + */ +typedef struct { + unsigned int can_timeout_attach :1; + unsigned int can_timeout_accept :1; + unsigned int can_timeout_handshake :1; + unsigned int reserved3 :1; + unsigned int reserved4 :1; + unsigned int reserved5 :1; + unsigned int reserved6 :1; + unsigned int reserved7 :1; + unsigned int reserved8 :1; + unsigned int reserved9 :1; + unsigned int reserved10 :1; + unsigned int reserved11 :1; + unsigned int reserved12 :1; + unsigned int reserved13 :1; + unsigned int reserved14 :1; + unsigned int reserved15 :1; +} JDWPTransportCapabilities; + + +/* + * Structures to define packet layout. + * + * See: http://java.sun.com/j2se/1.5/docs/guide/jpda/jdwp-spec.html + */ + +enum { + /* + * If additional flags are added that apply to jdwpCmdPacket, + * then debugLoop.c: reader() will need to be updated to + * accept more than JDWPTRANSPORT_FLAGS_NONE. + */ + JDWPTRANSPORT_FLAGS_NONE = 0x0, + JDWPTRANSPORT_FLAGS_REPLY = 0x80 +}; + +typedef struct { + jint len; + jint id; + jbyte flags; + jbyte cmdSet; + jbyte cmd; + jbyte *data; +} jdwpCmdPacket; + +typedef struct { + jint len; + jint id; + jbyte flags; + jshort errorCode; + jbyte *data; +} jdwpReplyPacket; + +typedef struct { + union { + jdwpCmdPacket cmd; + jdwpReplyPacket reply; + } type; +} jdwpPacket; + +/* + * JDWP functions called by the transport. + */ +typedef struct jdwpTransportCallback { + void *(*alloc)(jint numBytes); /* Call this for all allocations */ + void (*free)(void *buffer); /* Call this for all deallocations */ +} jdwpTransportCallback; + +typedef jint (JNICALL *jdwpTransport_OnLoad_t)(JavaVM *jvm, + jdwpTransportCallback *callback, + jint version, + jdwpTransportEnv** env); + + + +/* Function Interface */ + +struct jdwpTransportNativeInterface_ { + /* 1 : RESERVED */ + void *reserved1; + + /* 2 : Get Capabilities */ + jdwpTransportError (JNICALL *GetCapabilities)(jdwpTransportEnv* env, + JDWPTransportCapabilities *capabilities_ptr); + + /* 3 : Attach */ + jdwpTransportError (JNICALL *Attach)(jdwpTransportEnv* env, + const char* address, + jlong attach_timeout, + jlong handshake_timeout); + + /* 4: StartListening */ + jdwpTransportError (JNICALL *StartListening)(jdwpTransportEnv* env, + const char* address, + char** actual_address); + + /* 5: StopListening */ + jdwpTransportError (JNICALL *StopListening)(jdwpTransportEnv* env); + + /* 6: Accept */ + jdwpTransportError (JNICALL *Accept)(jdwpTransportEnv* env, + jlong accept_timeout, + jlong handshake_timeout); + + /* 7: IsOpen */ + jboolean (JNICALL *IsOpen)(jdwpTransportEnv* env); + + /* 8: Close */ + jdwpTransportError (JNICALL *Close)(jdwpTransportEnv* env); + + /* 9: ReadPacket */ + jdwpTransportError (JNICALL *ReadPacket)(jdwpTransportEnv* env, + jdwpPacket *pkt); + + /* 10: Write Packet */ + jdwpTransportError (JNICALL *WritePacket)(jdwpTransportEnv* env, + const jdwpPacket* pkt); + + /* 11: GetLastError */ + jdwpTransportError (JNICALL *GetLastError)(jdwpTransportEnv* env, + char** error); + +}; + + +/* + * Use inlined functions so that C++ code can use syntax such as + * env->Attach("mymachine:5000", 10*1000, 0); + * + * rather than using C's :- + * + * (*env)->Attach(env, "mymachine:5000", 10*1000, 0); + */ +struct _jdwpTransportEnv { + const struct jdwpTransportNativeInterface_ *functions; +#ifdef __cplusplus + + jdwpTransportError GetCapabilities(JDWPTransportCapabilities *capabilities_ptr) { + return functions->GetCapabilities(this, capabilities_ptr); + } + + jdwpTransportError Attach(const char* address, jlong attach_timeout, + jlong handshake_timeout) { + return functions->Attach(this, address, attach_timeout, handshake_timeout); + } + + jdwpTransportError StartListening(const char* address, + char** actual_address) { + return functions->StartListening(this, address, actual_address); + } + + jdwpTransportError StopListening(void) { + return functions->StopListening(this); + } + + jdwpTransportError Accept(jlong accept_timeout, jlong handshake_timeout) { + return functions->Accept(this, accept_timeout, handshake_timeout); + } + + jboolean IsOpen(void) { + return functions->IsOpen(this); + } + + jdwpTransportError Close(void) { + return functions->Close(this); + } + + jdwpTransportError ReadPacket(jdwpPacket *pkt) { + return functions->ReadPacket(this, pkt); + } + + jdwpTransportError WritePacket(const jdwpPacket* pkt) { + return functions->WritePacket(this, pkt); + } + + jdwpTransportError GetLastError(char** error) { + return functions->GetLastError(this, error); + } + + +#endif /* __cplusplus */ +}; + +#ifdef __cplusplus +} /* extern "C" */ +#endif /* __cplusplus */ + +#endif /* JDWPTRANSPORT_H */ diff --git a/jdk-1.8.0.281/include/jni.h b/jdk-1.8.0.281/include/jni.h new file mode 100755 index 0000000..0ffe244 --- /dev/null +++ b/jdk-1.8.0.281/include/jni.h @@ -0,0 +1,1960 @@ +/* + * Copyright (c) 1996, 2013, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +/* + * We used part of Netscape's Java Runtime Interface (JRI) as the starting + * point of our design and implementation. + */ + +/****************************************************************************** + * Java Runtime Interface + * Copyright (c) 1996 Netscape Communications Corporation. All rights reserved. + *****************************************************************************/ + +#ifndef _JAVASOFT_JNI_H_ +#define _JAVASOFT_JNI_H_ + +#include +#include + +/* jni_md.h contains the machine-dependent typedefs for jbyte, jint + and jlong */ + +#include "jni_md.h" + +#ifdef __cplusplus +extern "C" { +#endif + +/* + * JNI Types + */ + +#ifndef JNI_TYPES_ALREADY_DEFINED_IN_JNI_MD_H + +typedef unsigned char jboolean; +typedef unsigned short jchar; +typedef short jshort; +typedef float jfloat; +typedef double jdouble; + +typedef jint jsize; + +#ifdef __cplusplus + +class _jobject {}; +class _jclass : public _jobject {}; +class _jthrowable : public _jobject {}; +class _jstring : public _jobject {}; +class _jarray : public _jobject {}; +class _jbooleanArray : public _jarray {}; +class _jbyteArray : public _jarray {}; +class _jcharArray : public _jarray {}; +class _jshortArray : public _jarray {}; +class _jintArray : public _jarray {}; +class _jlongArray : public _jarray {}; +class _jfloatArray : public _jarray {}; +class _jdoubleArray : public _jarray {}; +class _jobjectArray : public _jarray {}; + +typedef _jobject *jobject; +typedef _jclass *jclass; +typedef _jthrowable *jthrowable; +typedef _jstring *jstring; +typedef _jarray *jarray; +typedef _jbooleanArray *jbooleanArray; +typedef _jbyteArray *jbyteArray; +typedef _jcharArray *jcharArray; +typedef _jshortArray *jshortArray; +typedef _jintArray *jintArray; +typedef _jlongArray *jlongArray; +typedef _jfloatArray *jfloatArray; +typedef _jdoubleArray *jdoubleArray; +typedef _jobjectArray *jobjectArray; + +#else + +struct _jobject; + +typedef struct _jobject *jobject; +typedef jobject jclass; +typedef jobject jthrowable; +typedef jobject jstring; +typedef jobject jarray; +typedef jarray jbooleanArray; +typedef jarray jbyteArray; +typedef jarray jcharArray; +typedef jarray jshortArray; +typedef jarray jintArray; +typedef jarray jlongArray; +typedef jarray jfloatArray; +typedef jarray jdoubleArray; +typedef jarray jobjectArray; + +#endif + +typedef jobject jweak; + +typedef union jvalue { + jboolean z; + jbyte b; + jchar c; + jshort s; + jint i; + jlong j; + jfloat f; + jdouble d; + jobject l; +} jvalue; + +struct _jfieldID; +typedef struct _jfieldID *jfieldID; + +struct _jmethodID; +typedef struct _jmethodID *jmethodID; + +/* Return values from jobjectRefType */ +typedef enum _jobjectType { + JNIInvalidRefType = 0, + JNILocalRefType = 1, + JNIGlobalRefType = 2, + JNIWeakGlobalRefType = 3 +} jobjectRefType; + + +#endif /* JNI_TYPES_ALREADY_DEFINED_IN_JNI_MD_H */ + +/* + * jboolean constants + */ + +#define JNI_FALSE 0 +#define JNI_TRUE 1 + +/* + * possible return values for JNI functions. + */ + +#define JNI_OK 0 /* success */ +#define JNI_ERR (-1) /* unknown error */ +#define JNI_EDETACHED (-2) /* thread detached from the VM */ +#define JNI_EVERSION (-3) /* JNI version error */ +#define JNI_ENOMEM (-4) /* not enough memory */ +#define JNI_EEXIST (-5) /* VM already created */ +#define JNI_EINVAL (-6) /* invalid arguments */ + +/* + * used in ReleaseScalarArrayElements + */ + +#define JNI_COMMIT 1 +#define JNI_ABORT 2 + +/* + * used in RegisterNatives to describe native method name, signature, + * and function pointer. + */ + +typedef struct { + char *name; + char *signature; + void *fnPtr; +} JNINativeMethod; + +/* + * JNI Native Method Interface. + */ + +struct JNINativeInterface_; + +struct JNIEnv_; + +#ifdef __cplusplus +typedef JNIEnv_ JNIEnv; +#else +typedef const struct JNINativeInterface_ *JNIEnv; +#endif + +/* + * JNI Invocation Interface. + */ + +struct JNIInvokeInterface_; + +struct JavaVM_; + +#ifdef __cplusplus +typedef JavaVM_ JavaVM; +#else +typedef const struct JNIInvokeInterface_ *JavaVM; +#endif + +struct JNINativeInterface_ { + void *reserved0; + void *reserved1; + void *reserved2; + + void *reserved3; + jint (JNICALL *GetVersion)(JNIEnv *env); + + jclass (JNICALL *DefineClass) + (JNIEnv *env, const char *name, jobject loader, const jbyte *buf, + jsize len); + jclass (JNICALL *FindClass) + (JNIEnv *env, const char *name); + + jmethodID (JNICALL *FromReflectedMethod) + (JNIEnv *env, jobject method); + jfieldID (JNICALL *FromReflectedField) + (JNIEnv *env, jobject field); + + jobject (JNICALL *ToReflectedMethod) + (JNIEnv *env, jclass cls, jmethodID methodID, jboolean isStatic); + + jclass (JNICALL *GetSuperclass) + (JNIEnv *env, jclass sub); + jboolean (JNICALL *IsAssignableFrom) + (JNIEnv *env, jclass sub, jclass sup); + + jobject (JNICALL *ToReflectedField) + (JNIEnv *env, jclass cls, jfieldID fieldID, jboolean isStatic); + + jint (JNICALL *Throw) + (JNIEnv *env, jthrowable obj); + jint (JNICALL *ThrowNew) + (JNIEnv *env, jclass clazz, const char *msg); + jthrowable (JNICALL *ExceptionOccurred) + (JNIEnv *env); + void (JNICALL *ExceptionDescribe) + (JNIEnv *env); + void (JNICALL *ExceptionClear) + (JNIEnv *env); + void (JNICALL *FatalError) + (JNIEnv *env, const char *msg); + + jint (JNICALL *PushLocalFrame) + (JNIEnv *env, jint capacity); + jobject (JNICALL *PopLocalFrame) + (JNIEnv *env, jobject result); + + jobject (JNICALL *NewGlobalRef) + (JNIEnv *env, jobject lobj); + void (JNICALL *DeleteGlobalRef) + (JNIEnv *env, jobject gref); + void (JNICALL *DeleteLocalRef) + (JNIEnv *env, jobject obj); + jboolean (JNICALL *IsSameObject) + (JNIEnv *env, jobject obj1, jobject obj2); + jobject (JNICALL *NewLocalRef) + (JNIEnv *env, jobject ref); + jint (JNICALL *EnsureLocalCapacity) + (JNIEnv *env, jint capacity); + + jobject (JNICALL *AllocObject) + (JNIEnv *env, jclass clazz); + jobject (JNICALL *NewObject) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jobject (JNICALL *NewObjectV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jobject (JNICALL *NewObjectA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jclass (JNICALL *GetObjectClass) + (JNIEnv *env, jobject obj); + jboolean (JNICALL *IsInstanceOf) + (JNIEnv *env, jobject obj, jclass clazz); + + jmethodID (JNICALL *GetMethodID) + (JNIEnv *env, jclass clazz, const char *name, const char *sig); + + jobject (JNICALL *CallObjectMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jobject (JNICALL *CallObjectMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jobject (JNICALL *CallObjectMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue * args); + + jboolean (JNICALL *CallBooleanMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jboolean (JNICALL *CallBooleanMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jboolean (JNICALL *CallBooleanMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue * args); + + jbyte (JNICALL *CallByteMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jbyte (JNICALL *CallByteMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jbyte (JNICALL *CallByteMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + jchar (JNICALL *CallCharMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jchar (JNICALL *CallCharMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jchar (JNICALL *CallCharMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + jshort (JNICALL *CallShortMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jshort (JNICALL *CallShortMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jshort (JNICALL *CallShortMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + jint (JNICALL *CallIntMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jint (JNICALL *CallIntMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jint (JNICALL *CallIntMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + jlong (JNICALL *CallLongMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jlong (JNICALL *CallLongMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jlong (JNICALL *CallLongMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + jfloat (JNICALL *CallFloatMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jfloat (JNICALL *CallFloatMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jfloat (JNICALL *CallFloatMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + jdouble (JNICALL *CallDoubleMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + jdouble (JNICALL *CallDoubleMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + jdouble (JNICALL *CallDoubleMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue *args); + + void (JNICALL *CallVoidMethod) + (JNIEnv *env, jobject obj, jmethodID methodID, ...); + void (JNICALL *CallVoidMethodV) + (JNIEnv *env, jobject obj, jmethodID methodID, va_list args); + void (JNICALL *CallVoidMethodA) + (JNIEnv *env, jobject obj, jmethodID methodID, const jvalue * args); + + jobject (JNICALL *CallNonvirtualObjectMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jobject (JNICALL *CallNonvirtualObjectMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jobject (JNICALL *CallNonvirtualObjectMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue * args); + + jboolean (JNICALL *CallNonvirtualBooleanMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jboolean (JNICALL *CallNonvirtualBooleanMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jboolean (JNICALL *CallNonvirtualBooleanMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue * args); + + jbyte (JNICALL *CallNonvirtualByteMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jbyte (JNICALL *CallNonvirtualByteMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jbyte (JNICALL *CallNonvirtualByteMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + jchar (JNICALL *CallNonvirtualCharMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jchar (JNICALL *CallNonvirtualCharMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jchar (JNICALL *CallNonvirtualCharMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + jshort (JNICALL *CallNonvirtualShortMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jshort (JNICALL *CallNonvirtualShortMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jshort (JNICALL *CallNonvirtualShortMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + jint (JNICALL *CallNonvirtualIntMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jint (JNICALL *CallNonvirtualIntMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jint (JNICALL *CallNonvirtualIntMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + jlong (JNICALL *CallNonvirtualLongMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jlong (JNICALL *CallNonvirtualLongMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jlong (JNICALL *CallNonvirtualLongMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + jfloat (JNICALL *CallNonvirtualFloatMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jfloat (JNICALL *CallNonvirtualFloatMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jfloat (JNICALL *CallNonvirtualFloatMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + jdouble (JNICALL *CallNonvirtualDoubleMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + jdouble (JNICALL *CallNonvirtualDoubleMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + jdouble (JNICALL *CallNonvirtualDoubleMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue *args); + + void (JNICALL *CallNonvirtualVoidMethod) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, ...); + void (JNICALL *CallNonvirtualVoidMethodV) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + va_list args); + void (JNICALL *CallNonvirtualVoidMethodA) + (JNIEnv *env, jobject obj, jclass clazz, jmethodID methodID, + const jvalue * args); + + jfieldID (JNICALL *GetFieldID) + (JNIEnv *env, jclass clazz, const char *name, const char *sig); + + jobject (JNICALL *GetObjectField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jboolean (JNICALL *GetBooleanField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jbyte (JNICALL *GetByteField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jchar (JNICALL *GetCharField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jshort (JNICALL *GetShortField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jint (JNICALL *GetIntField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jlong (JNICALL *GetLongField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jfloat (JNICALL *GetFloatField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + jdouble (JNICALL *GetDoubleField) + (JNIEnv *env, jobject obj, jfieldID fieldID); + + void (JNICALL *SetObjectField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jobject val); + void (JNICALL *SetBooleanField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jboolean val); + void (JNICALL *SetByteField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jbyte val); + void (JNICALL *SetCharField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jchar val); + void (JNICALL *SetShortField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jshort val); + void (JNICALL *SetIntField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jint val); + void (JNICALL *SetLongField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jlong val); + void (JNICALL *SetFloatField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jfloat val); + void (JNICALL *SetDoubleField) + (JNIEnv *env, jobject obj, jfieldID fieldID, jdouble val); + + jmethodID (JNICALL *GetStaticMethodID) + (JNIEnv *env, jclass clazz, const char *name, const char *sig); + + jobject (JNICALL *CallStaticObjectMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jobject (JNICALL *CallStaticObjectMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jobject (JNICALL *CallStaticObjectMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jboolean (JNICALL *CallStaticBooleanMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jboolean (JNICALL *CallStaticBooleanMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jboolean (JNICALL *CallStaticBooleanMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jbyte (JNICALL *CallStaticByteMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jbyte (JNICALL *CallStaticByteMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jbyte (JNICALL *CallStaticByteMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jchar (JNICALL *CallStaticCharMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jchar (JNICALL *CallStaticCharMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jchar (JNICALL *CallStaticCharMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jshort (JNICALL *CallStaticShortMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jshort (JNICALL *CallStaticShortMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jshort (JNICALL *CallStaticShortMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jint (JNICALL *CallStaticIntMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jint (JNICALL *CallStaticIntMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jint (JNICALL *CallStaticIntMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jlong (JNICALL *CallStaticLongMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jlong (JNICALL *CallStaticLongMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jlong (JNICALL *CallStaticLongMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jfloat (JNICALL *CallStaticFloatMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jfloat (JNICALL *CallStaticFloatMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jfloat (JNICALL *CallStaticFloatMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + jdouble (JNICALL *CallStaticDoubleMethod) + (JNIEnv *env, jclass clazz, jmethodID methodID, ...); + jdouble (JNICALL *CallStaticDoubleMethodV) + (JNIEnv *env, jclass clazz, jmethodID methodID, va_list args); + jdouble (JNICALL *CallStaticDoubleMethodA) + (JNIEnv *env, jclass clazz, jmethodID methodID, const jvalue *args); + + void (JNICALL *CallStaticVoidMethod) + (JNIEnv *env, jclass cls, jmethodID methodID, ...); + void (JNICALL *CallStaticVoidMethodV) + (JNIEnv *env, jclass cls, jmethodID methodID, va_list args); + void (JNICALL *CallStaticVoidMethodA) + (JNIEnv *env, jclass cls, jmethodID methodID, const jvalue * args); + + jfieldID (JNICALL *GetStaticFieldID) + (JNIEnv *env, jclass clazz, const char *name, const char *sig); + jobject (JNICALL *GetStaticObjectField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jboolean (JNICALL *GetStaticBooleanField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jbyte (JNICALL *GetStaticByteField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jchar (JNICALL *GetStaticCharField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jshort (JNICALL *GetStaticShortField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jint (JNICALL *GetStaticIntField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jlong (JNICALL *GetStaticLongField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jfloat (JNICALL *GetStaticFloatField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + jdouble (JNICALL *GetStaticDoubleField) + (JNIEnv *env, jclass clazz, jfieldID fieldID); + + void (JNICALL *SetStaticObjectField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jobject value); + void (JNICALL *SetStaticBooleanField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jboolean value); + void (JNICALL *SetStaticByteField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jbyte value); + void (JNICALL *SetStaticCharField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jchar value); + void (JNICALL *SetStaticShortField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jshort value); + void (JNICALL *SetStaticIntField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jint value); + void (JNICALL *SetStaticLongField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jlong value); + void (JNICALL *SetStaticFloatField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jfloat value); + void (JNICALL *SetStaticDoubleField) + (JNIEnv *env, jclass clazz, jfieldID fieldID, jdouble value); + + jstring (JNICALL *NewString) + (JNIEnv *env, const jchar *unicode, jsize len); + jsize (JNICALL *GetStringLength) + (JNIEnv *env, jstring str); + const jchar *(JNICALL *GetStringChars) + (JNIEnv *env, jstring str, jboolean *isCopy); + void (JNICALL *ReleaseStringChars) + (JNIEnv *env, jstring str, const jchar *chars); + + jstring (JNICALL *NewStringUTF) + (JNIEnv *env, const char *utf); + jsize (JNICALL *GetStringUTFLength) + (JNIEnv *env, jstring str); + const char* (JNICALL *GetStringUTFChars) + (JNIEnv *env, jstring str, jboolean *isCopy); + void (JNICALL *ReleaseStringUTFChars) + (JNIEnv *env, jstring str, const char* chars); + + + jsize (JNICALL *GetArrayLength) + (JNIEnv *env, jarray array); + + jobjectArray (JNICALL *NewObjectArray) + (JNIEnv *env, jsize len, jclass clazz, jobject init); + jobject (JNICALL *GetObjectArrayElement) + (JNIEnv *env, jobjectArray array, jsize index); + void (JNICALL *SetObjectArrayElement) + (JNIEnv *env, jobjectArray array, jsize index, jobject val); + + jbooleanArray (JNICALL *NewBooleanArray) + (JNIEnv *env, jsize len); + jbyteArray (JNICALL *NewByteArray) + (JNIEnv *env, jsize len); + jcharArray (JNICALL *NewCharArray) + (JNIEnv *env, jsize len); + jshortArray (JNICALL *NewShortArray) + (JNIEnv *env, jsize len); + jintArray (JNICALL *NewIntArray) + (JNIEnv *env, jsize len); + jlongArray (JNICALL *NewLongArray) + (JNIEnv *env, jsize len); + jfloatArray (JNICALL *NewFloatArray) + (JNIEnv *env, jsize len); + jdoubleArray (JNICALL *NewDoubleArray) + (JNIEnv *env, jsize len); + + jboolean * (JNICALL *GetBooleanArrayElements) + (JNIEnv *env, jbooleanArray array, jboolean *isCopy); + jbyte * (JNICALL *GetByteArrayElements) + (JNIEnv *env, jbyteArray array, jboolean *isCopy); + jchar * (JNICALL *GetCharArrayElements) + (JNIEnv *env, jcharArray array, jboolean *isCopy); + jshort * (JNICALL *GetShortArrayElements) + (JNIEnv *env, jshortArray array, jboolean *isCopy); + jint * (JNICALL *GetIntArrayElements) + (JNIEnv *env, jintArray array, jboolean *isCopy); + jlong * (JNICALL *GetLongArrayElements) + (JNIEnv *env, jlongArray array, jboolean *isCopy); + jfloat * (JNICALL *GetFloatArrayElements) + (JNIEnv *env, jfloatArray array, jboolean *isCopy); + jdouble * (JNICALL *GetDoubleArrayElements) + (JNIEnv *env, jdoubleArray array, jboolean *isCopy); + + void (JNICALL *ReleaseBooleanArrayElements) + (JNIEnv *env, jbooleanArray array, jboolean *elems, jint mode); + void (JNICALL *ReleaseByteArrayElements) + (JNIEnv *env, jbyteArray array, jbyte *elems, jint mode); + void (JNICALL *ReleaseCharArrayElements) + (JNIEnv *env, jcharArray array, jchar *elems, jint mode); + void (JNICALL *ReleaseShortArrayElements) + (JNIEnv *env, jshortArray array, jshort *elems, jint mode); + void (JNICALL *ReleaseIntArrayElements) + (JNIEnv *env, jintArray array, jint *elems, jint mode); + void (JNICALL *ReleaseLongArrayElements) + (JNIEnv *env, jlongArray array, jlong *elems, jint mode); + void (JNICALL *ReleaseFloatArrayElements) + (JNIEnv *env, jfloatArray array, jfloat *elems, jint mode); + void (JNICALL *ReleaseDoubleArrayElements) + (JNIEnv *env, jdoubleArray array, jdouble *elems, jint mode); + + void (JNICALL *GetBooleanArrayRegion) + (JNIEnv *env, jbooleanArray array, jsize start, jsize l, jboolean *buf); + void (JNICALL *GetByteArrayRegion) + (JNIEnv *env, jbyteArray array, jsize start, jsize len, jbyte *buf); + void (JNICALL *GetCharArrayRegion) + (JNIEnv *env, jcharArray array, jsize start, jsize len, jchar *buf); + void (JNICALL *GetShortArrayRegion) + (JNIEnv *env, jshortArray array, jsize start, jsize len, jshort *buf); + void (JNICALL *GetIntArrayRegion) + (JNIEnv *env, jintArray array, jsize start, jsize len, jint *buf); + void (JNICALL *GetLongArrayRegion) + (JNIEnv *env, jlongArray array, jsize start, jsize len, jlong *buf); + void (JNICALL *GetFloatArrayRegion) + (JNIEnv *env, jfloatArray array, jsize start, jsize len, jfloat *buf); + void (JNICALL *GetDoubleArrayRegion) + (JNIEnv *env, jdoubleArray array, jsize start, jsize len, jdouble *buf); + + void (JNICALL *SetBooleanArrayRegion) + (JNIEnv *env, jbooleanArray array, jsize start, jsize l, const jboolean *buf); + void (JNICALL *SetByteArrayRegion) + (JNIEnv *env, jbyteArray array, jsize start, jsize len, const jbyte *buf); + void (JNICALL *SetCharArrayRegion) + (JNIEnv *env, jcharArray array, jsize start, jsize len, const jchar *buf); + void (JNICALL *SetShortArrayRegion) + (JNIEnv *env, jshortArray array, jsize start, jsize len, const jshort *buf); + void (JNICALL *SetIntArrayRegion) + (JNIEnv *env, jintArray array, jsize start, jsize len, const jint *buf); + void (JNICALL *SetLongArrayRegion) + (JNIEnv *env, jlongArray array, jsize start, jsize len, const jlong *buf); + void (JNICALL *SetFloatArrayRegion) + (JNIEnv *env, jfloatArray array, jsize start, jsize len, const jfloat *buf); + void (JNICALL *SetDoubleArrayRegion) + (JNIEnv *env, jdoubleArray array, jsize start, jsize len, const jdouble *buf); + + jint (JNICALL *RegisterNatives) + (JNIEnv *env, jclass clazz, const JNINativeMethod *methods, + jint nMethods); + jint (JNICALL *UnregisterNatives) + (JNIEnv *env, jclass clazz); + + jint (JNICALL *MonitorEnter) + (JNIEnv *env, jobject obj); + jint (JNICALL *MonitorExit) + (JNIEnv *env, jobject obj); + + jint (JNICALL *GetJavaVM) + (JNIEnv *env, JavaVM **vm); + + void (JNICALL *GetStringRegion) + (JNIEnv *env, jstring str, jsize start, jsize len, jchar *buf); + void (JNICALL *GetStringUTFRegion) + (JNIEnv *env, jstring str, jsize start, jsize len, char *buf); + + void * (JNICALL *GetPrimitiveArrayCritical) + (JNIEnv *env, jarray array, jboolean *isCopy); + void (JNICALL *ReleasePrimitiveArrayCritical) + (JNIEnv *env, jarray array, void *carray, jint mode); + + const jchar * (JNICALL *GetStringCritical) + (JNIEnv *env, jstring string, jboolean *isCopy); + void (JNICALL *ReleaseStringCritical) + (JNIEnv *env, jstring string, const jchar *cstring); + + jweak (JNICALL *NewWeakGlobalRef) + (JNIEnv *env, jobject obj); + void (JNICALL *DeleteWeakGlobalRef) + (JNIEnv *env, jweak ref); + + jboolean (JNICALL *ExceptionCheck) + (JNIEnv *env); + + jobject (JNICALL *NewDirectByteBuffer) + (JNIEnv* env, void* address, jlong capacity); + void* (JNICALL *GetDirectBufferAddress) + (JNIEnv* env, jobject buf); + jlong (JNICALL *GetDirectBufferCapacity) + (JNIEnv* env, jobject buf); + + /* New JNI 1.6 Features */ + + jobjectRefType (JNICALL *GetObjectRefType) + (JNIEnv* env, jobject obj); +}; + +/* + * We use inlined functions for C++ so that programmers can write: + * + * env->FindClass("java/lang/String") + * + * in C++ rather than: + * + * (*env)->FindClass(env, "java/lang/String") + * + * in C. + */ + +struct JNIEnv_ { + const struct JNINativeInterface_ *functions; +#ifdef __cplusplus + + jint GetVersion() { + return functions->GetVersion(this); + } + jclass DefineClass(const char *name, jobject loader, const jbyte *buf, + jsize len) { + return functions->DefineClass(this, name, loader, buf, len); + } + jclass FindClass(const char *name) { + return functions->FindClass(this, name); + } + jmethodID FromReflectedMethod(jobject method) { + return functions->FromReflectedMethod(this,method); + } + jfieldID FromReflectedField(jobject field) { + return functions->FromReflectedField(this,field); + } + + jobject ToReflectedMethod(jclass cls, jmethodID methodID, jboolean isStatic) { + return functions->ToReflectedMethod(this, cls, methodID, isStatic); + } + + jclass GetSuperclass(jclass sub) { + return functions->GetSuperclass(this, sub); + } + jboolean IsAssignableFrom(jclass sub, jclass sup) { + return functions->IsAssignableFrom(this, sub, sup); + } + + jobject ToReflectedField(jclass cls, jfieldID fieldID, jboolean isStatic) { + return functions->ToReflectedField(this,cls,fieldID,isStatic); + } + + jint Throw(jthrowable obj) { + return functions->Throw(this, obj); + } + jint ThrowNew(jclass clazz, const char *msg) { + return functions->ThrowNew(this, clazz, msg); + } + jthrowable ExceptionOccurred() { + return functions->ExceptionOccurred(this); + } + void ExceptionDescribe() { + functions->ExceptionDescribe(this); + } + void ExceptionClear() { + functions->ExceptionClear(this); + } + void FatalError(const char *msg) { + functions->FatalError(this, msg); + } + + jint PushLocalFrame(jint capacity) { + return functions->PushLocalFrame(this,capacity); + } + jobject PopLocalFrame(jobject result) { + return functions->PopLocalFrame(this,result); + } + + jobject NewGlobalRef(jobject lobj) { + return functions->NewGlobalRef(this,lobj); + } + void DeleteGlobalRef(jobject gref) { + functions->DeleteGlobalRef(this,gref); + } + void DeleteLocalRef(jobject obj) { + functions->DeleteLocalRef(this, obj); + } + + jboolean IsSameObject(jobject obj1, jobject obj2) { + return functions->IsSameObject(this,obj1,obj2); + } + + jobject NewLocalRef(jobject ref) { + return functions->NewLocalRef(this,ref); + } + jint EnsureLocalCapacity(jint capacity) { + return functions->EnsureLocalCapacity(this,capacity); + } + + jobject AllocObject(jclass clazz) { + return functions->AllocObject(this,clazz); + } + jobject NewObject(jclass clazz, jmethodID methodID, ...) { + va_list args; + jobject result; + va_start(args, methodID); + result = functions->NewObjectV(this,clazz,methodID,args); + va_end(args); + return result; + } + jobject NewObjectV(jclass clazz, jmethodID methodID, + va_list args) { + return functions->NewObjectV(this,clazz,methodID,args); + } + jobject NewObjectA(jclass clazz, jmethodID methodID, + const jvalue *args) { + return functions->NewObjectA(this,clazz,methodID,args); + } + + jclass GetObjectClass(jobject obj) { + return functions->GetObjectClass(this,obj); + } + jboolean IsInstanceOf(jobject obj, jclass clazz) { + return functions->IsInstanceOf(this,obj,clazz); + } + + jmethodID GetMethodID(jclass clazz, const char *name, + const char *sig) { + return functions->GetMethodID(this,clazz,name,sig); + } + + jobject CallObjectMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jobject result; + va_start(args,methodID); + result = functions->CallObjectMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jobject CallObjectMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallObjectMethodV(this,obj,methodID,args); + } + jobject CallObjectMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallObjectMethodA(this,obj,methodID,args); + } + + jboolean CallBooleanMethod(jobject obj, + jmethodID methodID, ...) { + va_list args; + jboolean result; + va_start(args,methodID); + result = functions->CallBooleanMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jboolean CallBooleanMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallBooleanMethodV(this,obj,methodID,args); + } + jboolean CallBooleanMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallBooleanMethodA(this,obj,methodID, args); + } + + jbyte CallByteMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jbyte result; + va_start(args,methodID); + result = functions->CallByteMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jbyte CallByteMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallByteMethodV(this,obj,methodID,args); + } + jbyte CallByteMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallByteMethodA(this,obj,methodID,args); + } + + jchar CallCharMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jchar result; + va_start(args,methodID); + result = functions->CallCharMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jchar CallCharMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallCharMethodV(this,obj,methodID,args); + } + jchar CallCharMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallCharMethodA(this,obj,methodID,args); + } + + jshort CallShortMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jshort result; + va_start(args,methodID); + result = functions->CallShortMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jshort CallShortMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallShortMethodV(this,obj,methodID,args); + } + jshort CallShortMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallShortMethodA(this,obj,methodID,args); + } + + jint CallIntMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jint result; + va_start(args,methodID); + result = functions->CallIntMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jint CallIntMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallIntMethodV(this,obj,methodID,args); + } + jint CallIntMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallIntMethodA(this,obj,methodID,args); + } + + jlong CallLongMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jlong result; + va_start(args,methodID); + result = functions->CallLongMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jlong CallLongMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallLongMethodV(this,obj,methodID,args); + } + jlong CallLongMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallLongMethodA(this,obj,methodID,args); + } + + jfloat CallFloatMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jfloat result; + va_start(args,methodID); + result = functions->CallFloatMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jfloat CallFloatMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallFloatMethodV(this,obj,methodID,args); + } + jfloat CallFloatMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallFloatMethodA(this,obj,methodID,args); + } + + jdouble CallDoubleMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + jdouble result; + va_start(args,methodID); + result = functions->CallDoubleMethodV(this,obj,methodID,args); + va_end(args); + return result; + } + jdouble CallDoubleMethodV(jobject obj, jmethodID methodID, + va_list args) { + return functions->CallDoubleMethodV(this,obj,methodID,args); + } + jdouble CallDoubleMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + return functions->CallDoubleMethodA(this,obj,methodID,args); + } + + void CallVoidMethod(jobject obj, jmethodID methodID, ...) { + va_list args; + va_start(args,methodID); + functions->CallVoidMethodV(this,obj,methodID,args); + va_end(args); + } + void CallVoidMethodV(jobject obj, jmethodID methodID, + va_list args) { + functions->CallVoidMethodV(this,obj,methodID,args); + } + void CallVoidMethodA(jobject obj, jmethodID methodID, + const jvalue * args) { + functions->CallVoidMethodA(this,obj,methodID,args); + } + + jobject CallNonvirtualObjectMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jobject result; + va_start(args,methodID); + result = functions->CallNonvirtualObjectMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jobject CallNonvirtualObjectMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualObjectMethodV(this,obj,clazz, + methodID,args); + } + jobject CallNonvirtualObjectMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualObjectMethodA(this,obj,clazz, + methodID,args); + } + + jboolean CallNonvirtualBooleanMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jboolean result; + va_start(args,methodID); + result = functions->CallNonvirtualBooleanMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jboolean CallNonvirtualBooleanMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualBooleanMethodV(this,obj,clazz, + methodID,args); + } + jboolean CallNonvirtualBooleanMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualBooleanMethodA(this,obj,clazz, + methodID, args); + } + + jbyte CallNonvirtualByteMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jbyte result; + va_start(args,methodID); + result = functions->CallNonvirtualByteMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jbyte CallNonvirtualByteMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualByteMethodV(this,obj,clazz, + methodID,args); + } + jbyte CallNonvirtualByteMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualByteMethodA(this,obj,clazz, + methodID,args); + } + + jchar CallNonvirtualCharMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jchar result; + va_start(args,methodID); + result = functions->CallNonvirtualCharMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jchar CallNonvirtualCharMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualCharMethodV(this,obj,clazz, + methodID,args); + } + jchar CallNonvirtualCharMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualCharMethodA(this,obj,clazz, + methodID,args); + } + + jshort CallNonvirtualShortMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jshort result; + va_start(args,methodID); + result = functions->CallNonvirtualShortMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jshort CallNonvirtualShortMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualShortMethodV(this,obj,clazz, + methodID,args); + } + jshort CallNonvirtualShortMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualShortMethodA(this,obj,clazz, + methodID,args); + } + + jint CallNonvirtualIntMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jint result; + va_start(args,methodID); + result = functions->CallNonvirtualIntMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jint CallNonvirtualIntMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualIntMethodV(this,obj,clazz, + methodID,args); + } + jint CallNonvirtualIntMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualIntMethodA(this,obj,clazz, + methodID,args); + } + + jlong CallNonvirtualLongMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jlong result; + va_start(args,methodID); + result = functions->CallNonvirtualLongMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jlong CallNonvirtualLongMethodV(jobject obj, jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallNonvirtualLongMethodV(this,obj,clazz, + methodID,args); + } + jlong CallNonvirtualLongMethodA(jobject obj, jclass clazz, + jmethodID methodID, const jvalue * args) { + return functions->CallNonvirtualLongMethodA(this,obj,clazz, + methodID,args); + } + + jfloat CallNonvirtualFloatMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jfloat result; + va_start(args,methodID); + result = functions->CallNonvirtualFloatMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jfloat CallNonvirtualFloatMethodV(jobject obj, jclass clazz, + jmethodID methodID, + va_list args) { + return functions->CallNonvirtualFloatMethodV(this,obj,clazz, + methodID,args); + } + jfloat CallNonvirtualFloatMethodA(jobject obj, jclass clazz, + jmethodID methodID, + const jvalue * args) { + return functions->CallNonvirtualFloatMethodA(this,obj,clazz, + methodID,args); + } + + jdouble CallNonvirtualDoubleMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + jdouble result; + va_start(args,methodID); + result = functions->CallNonvirtualDoubleMethodV(this,obj,clazz, + methodID,args); + va_end(args); + return result; + } + jdouble CallNonvirtualDoubleMethodV(jobject obj, jclass clazz, + jmethodID methodID, + va_list args) { + return functions->CallNonvirtualDoubleMethodV(this,obj,clazz, + methodID,args); + } + jdouble CallNonvirtualDoubleMethodA(jobject obj, jclass clazz, + jmethodID methodID, + const jvalue * args) { + return functions->CallNonvirtualDoubleMethodA(this,obj,clazz, + methodID,args); + } + + void CallNonvirtualVoidMethod(jobject obj, jclass clazz, + jmethodID methodID, ...) { + va_list args; + va_start(args,methodID); + functions->CallNonvirtualVoidMethodV(this,obj,clazz,methodID,args); + va_end(args); + } + void CallNonvirtualVoidMethodV(jobject obj, jclass clazz, + jmethodID methodID, + va_list args) { + functions->CallNonvirtualVoidMethodV(this,obj,clazz,methodID,args); + } + void CallNonvirtualVoidMethodA(jobject obj, jclass clazz, + jmethodID methodID, + const jvalue * args) { + functions->CallNonvirtualVoidMethodA(this,obj,clazz,methodID,args); + } + + jfieldID GetFieldID(jclass clazz, const char *name, + const char *sig) { + return functions->GetFieldID(this,clazz,name,sig); + } + + jobject GetObjectField(jobject obj, jfieldID fieldID) { + return functions->GetObjectField(this,obj,fieldID); + } + jboolean GetBooleanField(jobject obj, jfieldID fieldID) { + return functions->GetBooleanField(this,obj,fieldID); + } + jbyte GetByteField(jobject obj, jfieldID fieldID) { + return functions->GetByteField(this,obj,fieldID); + } + jchar GetCharField(jobject obj, jfieldID fieldID) { + return functions->GetCharField(this,obj,fieldID); + } + jshort GetShortField(jobject obj, jfieldID fieldID) { + return functions->GetShortField(this,obj,fieldID); + } + jint GetIntField(jobject obj, jfieldID fieldID) { + return functions->GetIntField(this,obj,fieldID); + } + jlong GetLongField(jobject obj, jfieldID fieldID) { + return functions->GetLongField(this,obj,fieldID); + } + jfloat GetFloatField(jobject obj, jfieldID fieldID) { + return functions->GetFloatField(this,obj,fieldID); + } + jdouble GetDoubleField(jobject obj, jfieldID fieldID) { + return functions->GetDoubleField(this,obj,fieldID); + } + + void SetObjectField(jobject obj, jfieldID fieldID, jobject val) { + functions->SetObjectField(this,obj,fieldID,val); + } + void SetBooleanField(jobject obj, jfieldID fieldID, + jboolean val) { + functions->SetBooleanField(this,obj,fieldID,val); + } + void SetByteField(jobject obj, jfieldID fieldID, + jbyte val) { + functions->SetByteField(this,obj,fieldID,val); + } + void SetCharField(jobject obj, jfieldID fieldID, + jchar val) { + functions->SetCharField(this,obj,fieldID,val); + } + void SetShortField(jobject obj, jfieldID fieldID, + jshort val) { + functions->SetShortField(this,obj,fieldID,val); + } + void SetIntField(jobject obj, jfieldID fieldID, + jint val) { + functions->SetIntField(this,obj,fieldID,val); + } + void SetLongField(jobject obj, jfieldID fieldID, + jlong val) { + functions->SetLongField(this,obj,fieldID,val); + } + void SetFloatField(jobject obj, jfieldID fieldID, + jfloat val) { + functions->SetFloatField(this,obj,fieldID,val); + } + void SetDoubleField(jobject obj, jfieldID fieldID, + jdouble val) { + functions->SetDoubleField(this,obj,fieldID,val); + } + + jmethodID GetStaticMethodID(jclass clazz, const char *name, + const char *sig) { + return functions->GetStaticMethodID(this,clazz,name,sig); + } + + jobject CallStaticObjectMethod(jclass clazz, jmethodID methodID, + ...) { + va_list args; + jobject result; + va_start(args,methodID); + result = functions->CallStaticObjectMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jobject CallStaticObjectMethodV(jclass clazz, jmethodID methodID, + va_list args) { + return functions->CallStaticObjectMethodV(this,clazz,methodID,args); + } + jobject CallStaticObjectMethodA(jclass clazz, jmethodID methodID, + const jvalue *args) { + return functions->CallStaticObjectMethodA(this,clazz,methodID,args); + } + + jboolean CallStaticBooleanMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jboolean result; + va_start(args,methodID); + result = functions->CallStaticBooleanMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jboolean CallStaticBooleanMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticBooleanMethodV(this,clazz,methodID,args); + } + jboolean CallStaticBooleanMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticBooleanMethodA(this,clazz,methodID,args); + } + + jbyte CallStaticByteMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jbyte result; + va_start(args,methodID); + result = functions->CallStaticByteMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jbyte CallStaticByteMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticByteMethodV(this,clazz,methodID,args); + } + jbyte CallStaticByteMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticByteMethodA(this,clazz,methodID,args); + } + + jchar CallStaticCharMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jchar result; + va_start(args,methodID); + result = functions->CallStaticCharMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jchar CallStaticCharMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticCharMethodV(this,clazz,methodID,args); + } + jchar CallStaticCharMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticCharMethodA(this,clazz,methodID,args); + } + + jshort CallStaticShortMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jshort result; + va_start(args,methodID); + result = functions->CallStaticShortMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jshort CallStaticShortMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticShortMethodV(this,clazz,methodID,args); + } + jshort CallStaticShortMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticShortMethodA(this,clazz,methodID,args); + } + + jint CallStaticIntMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jint result; + va_start(args,methodID); + result = functions->CallStaticIntMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jint CallStaticIntMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticIntMethodV(this,clazz,methodID,args); + } + jint CallStaticIntMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticIntMethodA(this,clazz,methodID,args); + } + + jlong CallStaticLongMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jlong result; + va_start(args,methodID); + result = functions->CallStaticLongMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jlong CallStaticLongMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticLongMethodV(this,clazz,methodID,args); + } + jlong CallStaticLongMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticLongMethodA(this,clazz,methodID,args); + } + + jfloat CallStaticFloatMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jfloat result; + va_start(args,methodID); + result = functions->CallStaticFloatMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jfloat CallStaticFloatMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticFloatMethodV(this,clazz,methodID,args); + } + jfloat CallStaticFloatMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticFloatMethodA(this,clazz,methodID,args); + } + + jdouble CallStaticDoubleMethod(jclass clazz, + jmethodID methodID, ...) { + va_list args; + jdouble result; + va_start(args,methodID); + result = functions->CallStaticDoubleMethodV(this,clazz,methodID,args); + va_end(args); + return result; + } + jdouble CallStaticDoubleMethodV(jclass clazz, + jmethodID methodID, va_list args) { + return functions->CallStaticDoubleMethodV(this,clazz,methodID,args); + } + jdouble CallStaticDoubleMethodA(jclass clazz, + jmethodID methodID, const jvalue *args) { + return functions->CallStaticDoubleMethodA(this,clazz,methodID,args); + } + + void CallStaticVoidMethod(jclass cls, jmethodID methodID, ...) { + va_list args; + va_start(args,methodID); + functions->CallStaticVoidMethodV(this,cls,methodID,args); + va_end(args); + } + void CallStaticVoidMethodV(jclass cls, jmethodID methodID, + va_list args) { + functions->CallStaticVoidMethodV(this,cls,methodID,args); + } + void CallStaticVoidMethodA(jclass cls, jmethodID methodID, + const jvalue * args) { + functions->CallStaticVoidMethodA(this,cls,methodID,args); + } + + jfieldID GetStaticFieldID(jclass clazz, const char *name, + const char *sig) { + return functions->GetStaticFieldID(this,clazz,name,sig); + } + jobject GetStaticObjectField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticObjectField(this,clazz,fieldID); + } + jboolean GetStaticBooleanField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticBooleanField(this,clazz,fieldID); + } + jbyte GetStaticByteField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticByteField(this,clazz,fieldID); + } + jchar GetStaticCharField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticCharField(this,clazz,fieldID); + } + jshort GetStaticShortField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticShortField(this,clazz,fieldID); + } + jint GetStaticIntField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticIntField(this,clazz,fieldID); + } + jlong GetStaticLongField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticLongField(this,clazz,fieldID); + } + jfloat GetStaticFloatField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticFloatField(this,clazz,fieldID); + } + jdouble GetStaticDoubleField(jclass clazz, jfieldID fieldID) { + return functions->GetStaticDoubleField(this,clazz,fieldID); + } + + void SetStaticObjectField(jclass clazz, jfieldID fieldID, + jobject value) { + functions->SetStaticObjectField(this,clazz,fieldID,value); + } + void SetStaticBooleanField(jclass clazz, jfieldID fieldID, + jboolean value) { + functions->SetStaticBooleanField(this,clazz,fieldID,value); + } + void SetStaticByteField(jclass clazz, jfieldID fieldID, + jbyte value) { + functions->SetStaticByteField(this,clazz,fieldID,value); + } + void SetStaticCharField(jclass clazz, jfieldID fieldID, + jchar value) { + functions->SetStaticCharField(this,clazz,fieldID,value); + } + void SetStaticShortField(jclass clazz, jfieldID fieldID, + jshort value) { + functions->SetStaticShortField(this,clazz,fieldID,value); + } + void SetStaticIntField(jclass clazz, jfieldID fieldID, + jint value) { + functions->SetStaticIntField(this,clazz,fieldID,value); + } + void SetStaticLongField(jclass clazz, jfieldID fieldID, + jlong value) { + functions->SetStaticLongField(this,clazz,fieldID,value); + } + void SetStaticFloatField(jclass clazz, jfieldID fieldID, + jfloat value) { + functions->SetStaticFloatField(this,clazz,fieldID,value); + } + void SetStaticDoubleField(jclass clazz, jfieldID fieldID, + jdouble value) { + functions->SetStaticDoubleField(this,clazz,fieldID,value); + } + + jstring NewString(const jchar *unicode, jsize len) { + return functions->NewString(this,unicode,len); + } + jsize GetStringLength(jstring str) { + return functions->GetStringLength(this,str); + } + const jchar *GetStringChars(jstring str, jboolean *isCopy) { + return functions->GetStringChars(this,str,isCopy); + } + void ReleaseStringChars(jstring str, const jchar *chars) { + functions->ReleaseStringChars(this,str,chars); + } + + jstring NewStringUTF(const char *utf) { + return functions->NewStringUTF(this,utf); + } + jsize GetStringUTFLength(jstring str) { + return functions->GetStringUTFLength(this,str); + } + const char* GetStringUTFChars(jstring str, jboolean *isCopy) { + return functions->GetStringUTFChars(this,str,isCopy); + } + void ReleaseStringUTFChars(jstring str, const char* chars) { + functions->ReleaseStringUTFChars(this,str,chars); + } + + jsize GetArrayLength(jarray array) { + return functions->GetArrayLength(this,array); + } + + jobjectArray NewObjectArray(jsize len, jclass clazz, + jobject init) { + return functions->NewObjectArray(this,len,clazz,init); + } + jobject GetObjectArrayElement(jobjectArray array, jsize index) { + return functions->GetObjectArrayElement(this,array,index); + } + void SetObjectArrayElement(jobjectArray array, jsize index, + jobject val) { + functions->SetObjectArrayElement(this,array,index,val); + } + + jbooleanArray NewBooleanArray(jsize len) { + return functions->NewBooleanArray(this,len); + } + jbyteArray NewByteArray(jsize len) { + return functions->NewByteArray(this,len); + } + jcharArray NewCharArray(jsize len) { + return functions->NewCharArray(this,len); + } + jshortArray NewShortArray(jsize len) { + return functions->NewShortArray(this,len); + } + jintArray NewIntArray(jsize len) { + return functions->NewIntArray(this,len); + } + jlongArray NewLongArray(jsize len) { + return functions->NewLongArray(this,len); + } + jfloatArray NewFloatArray(jsize len) { + return functions->NewFloatArray(this,len); + } + jdoubleArray NewDoubleArray(jsize len) { + return functions->NewDoubleArray(this,len); + } + + jboolean * GetBooleanArrayElements(jbooleanArray array, jboolean *isCopy) { + return functions->GetBooleanArrayElements(this,array,isCopy); + } + jbyte * GetByteArrayElements(jbyteArray array, jboolean *isCopy) { + return functions->GetByteArrayElements(this,array,isCopy); + } + jchar * GetCharArrayElements(jcharArray array, jboolean *isCopy) { + return functions->GetCharArrayElements(this,array,isCopy); + } + jshort * GetShortArrayElements(jshortArray array, jboolean *isCopy) { + return functions->GetShortArrayElements(this,array,isCopy); + } + jint * GetIntArrayElements(jintArray array, jboolean *isCopy) { + return functions->GetIntArrayElements(this,array,isCopy); + } + jlong * GetLongArrayElements(jlongArray array, jboolean *isCopy) { + return functions->GetLongArrayElements(this,array,isCopy); + } + jfloat * GetFloatArrayElements(jfloatArray array, jboolean *isCopy) { + return functions->GetFloatArrayElements(this,array,isCopy); + } + jdouble * GetDoubleArrayElements(jdoubleArray array, jboolean *isCopy) { + return functions->GetDoubleArrayElements(this,array,isCopy); + } + + void ReleaseBooleanArrayElements(jbooleanArray array, + jboolean *elems, + jint mode) { + functions->ReleaseBooleanArrayElements(this,array,elems,mode); + } + void ReleaseByteArrayElements(jbyteArray array, + jbyte *elems, + jint mode) { + functions->ReleaseByteArrayElements(this,array,elems,mode); + } + void ReleaseCharArrayElements(jcharArray array, + jchar *elems, + jint mode) { + functions->ReleaseCharArrayElements(this,array,elems,mode); + } + void ReleaseShortArrayElements(jshortArray array, + jshort *elems, + jint mode) { + functions->ReleaseShortArrayElements(this,array,elems,mode); + } + void ReleaseIntArrayElements(jintArray array, + jint *elems, + jint mode) { + functions->ReleaseIntArrayElements(this,array,elems,mode); + } + void ReleaseLongArrayElements(jlongArray array, + jlong *elems, + jint mode) { + functions->ReleaseLongArrayElements(this,array,elems,mode); + } + void ReleaseFloatArrayElements(jfloatArray array, + jfloat *elems, + jint mode) { + functions->ReleaseFloatArrayElements(this,array,elems,mode); + } + void ReleaseDoubleArrayElements(jdoubleArray array, + jdouble *elems, + jint mode) { + functions->ReleaseDoubleArrayElements(this,array,elems,mode); + } + + void GetBooleanArrayRegion(jbooleanArray array, + jsize start, jsize len, jboolean *buf) { + functions->GetBooleanArrayRegion(this,array,start,len,buf); + } + void GetByteArrayRegion(jbyteArray array, + jsize start, jsize len, jbyte *buf) { + functions->GetByteArrayRegion(this,array,start,len,buf); + } + void GetCharArrayRegion(jcharArray array, + jsize start, jsize len, jchar *buf) { + functions->GetCharArrayRegion(this,array,start,len,buf); + } + void GetShortArrayRegion(jshortArray array, + jsize start, jsize len, jshort *buf) { + functions->GetShortArrayRegion(this,array,start,len,buf); + } + void GetIntArrayRegion(jintArray array, + jsize start, jsize len, jint *buf) { + functions->GetIntArrayRegion(this,array,start,len,buf); + } + void GetLongArrayRegion(jlongArray array, + jsize start, jsize len, jlong *buf) { + functions->GetLongArrayRegion(this,array,start,len,buf); + } + void GetFloatArrayRegion(jfloatArray array, + jsize start, jsize len, jfloat *buf) { + functions->GetFloatArrayRegion(this,array,start,len,buf); + } + void GetDoubleArrayRegion(jdoubleArray array, + jsize start, jsize len, jdouble *buf) { + functions->GetDoubleArrayRegion(this,array,start,len,buf); + } + + void SetBooleanArrayRegion(jbooleanArray array, jsize start, jsize len, + const jboolean *buf) { + functions->SetBooleanArrayRegion(this,array,start,len,buf); + } + void SetByteArrayRegion(jbyteArray array, jsize start, jsize len, + const jbyte *buf) { + functions->SetByteArrayRegion(this,array,start,len,buf); + } + void SetCharArrayRegion(jcharArray array, jsize start, jsize len, + const jchar *buf) { + functions->SetCharArrayRegion(this,array,start,len,buf); + } + void SetShortArrayRegion(jshortArray array, jsize start, jsize len, + const jshort *buf) { + functions->SetShortArrayRegion(this,array,start,len,buf); + } + void SetIntArrayRegion(jintArray array, jsize start, jsize len, + const jint *buf) { + functions->SetIntArrayRegion(this,array,start,len,buf); + } + void SetLongArrayRegion(jlongArray array, jsize start, jsize len, + const jlong *buf) { + functions->SetLongArrayRegion(this,array,start,len,buf); + } + void SetFloatArrayRegion(jfloatArray array, jsize start, jsize len, + const jfloat *buf) { + functions->SetFloatArrayRegion(this,array,start,len,buf); + } + void SetDoubleArrayRegion(jdoubleArray array, jsize start, jsize len, + const jdouble *buf) { + functions->SetDoubleArrayRegion(this,array,start,len,buf); + } + + jint RegisterNatives(jclass clazz, const JNINativeMethod *methods, + jint nMethods) { + return functions->RegisterNatives(this,clazz,methods,nMethods); + } + jint UnregisterNatives(jclass clazz) { + return functions->UnregisterNatives(this,clazz); + } + + jint MonitorEnter(jobject obj) { + return functions->MonitorEnter(this,obj); + } + jint MonitorExit(jobject obj) { + return functions->MonitorExit(this,obj); + } + + jint GetJavaVM(JavaVM **vm) { + return functions->GetJavaVM(this,vm); + } + + void GetStringRegion(jstring str, jsize start, jsize len, jchar *buf) { + functions->GetStringRegion(this,str,start,len,buf); + } + void GetStringUTFRegion(jstring str, jsize start, jsize len, char *buf) { + functions->GetStringUTFRegion(this,str,start,len,buf); + } + + void * GetPrimitiveArrayCritical(jarray array, jboolean *isCopy) { + return functions->GetPrimitiveArrayCritical(this,array,isCopy); + } + void ReleasePrimitiveArrayCritical(jarray array, void *carray, jint mode) { + functions->ReleasePrimitiveArrayCritical(this,array,carray,mode); + } + + const jchar * GetStringCritical(jstring string, jboolean *isCopy) { + return functions->GetStringCritical(this,string,isCopy); + } + void ReleaseStringCritical(jstring string, const jchar *cstring) { + functions->ReleaseStringCritical(this,string,cstring); + } + + jweak NewWeakGlobalRef(jobject obj) { + return functions->NewWeakGlobalRef(this,obj); + } + void DeleteWeakGlobalRef(jweak ref) { + functions->DeleteWeakGlobalRef(this,ref); + } + + jboolean ExceptionCheck() { + return functions->ExceptionCheck(this); + } + + jobject NewDirectByteBuffer(void* address, jlong capacity) { + return functions->NewDirectByteBuffer(this, address, capacity); + } + void* GetDirectBufferAddress(jobject buf) { + return functions->GetDirectBufferAddress(this, buf); + } + jlong GetDirectBufferCapacity(jobject buf) { + return functions->GetDirectBufferCapacity(this, buf); + } + jobjectRefType GetObjectRefType(jobject obj) { + return functions->GetObjectRefType(this, obj); + } + +#endif /* __cplusplus */ +}; + +typedef struct JavaVMOption { + char *optionString; + void *extraInfo; +} JavaVMOption; + +typedef struct JavaVMInitArgs { + jint version; + + jint nOptions; + JavaVMOption *options; + jboolean ignoreUnrecognized; +} JavaVMInitArgs; + +typedef struct JavaVMAttachArgs { + jint version; + + char *name; + jobject group; +} JavaVMAttachArgs; + +/* These will be VM-specific. */ + +#define JDK1_2 +#define JDK1_4 + +/* End VM-specific. */ + +struct JNIInvokeInterface_ { + void *reserved0; + void *reserved1; + void *reserved2; + + jint (JNICALL *DestroyJavaVM)(JavaVM *vm); + + jint (JNICALL *AttachCurrentThread)(JavaVM *vm, void **penv, void *args); + + jint (JNICALL *DetachCurrentThread)(JavaVM *vm); + + jint (JNICALL *GetEnv)(JavaVM *vm, void **penv, jint version); + + jint (JNICALL *AttachCurrentThreadAsDaemon)(JavaVM *vm, void **penv, void *args); +}; + +struct JavaVM_ { + const struct JNIInvokeInterface_ *functions; +#ifdef __cplusplus + + jint DestroyJavaVM() { + return functions->DestroyJavaVM(this); + } + jint AttachCurrentThread(void **penv, void *args) { + return functions->AttachCurrentThread(this, penv, args); + } + jint DetachCurrentThread() { + return functions->DetachCurrentThread(this); + } + + jint GetEnv(void **penv, jint version) { + return functions->GetEnv(this, penv, version); + } + jint AttachCurrentThreadAsDaemon(void **penv, void *args) { + return functions->AttachCurrentThreadAsDaemon(this, penv, args); + } +#endif +}; + +#ifdef _JNI_IMPLEMENTATION_ +#define _JNI_IMPORT_OR_EXPORT_ JNIEXPORT +#else +#define _JNI_IMPORT_OR_EXPORT_ JNIIMPORT +#endif +_JNI_IMPORT_OR_EXPORT_ jint JNICALL +JNI_GetDefaultJavaVMInitArgs(void *args); + +_JNI_IMPORT_OR_EXPORT_ jint JNICALL +JNI_CreateJavaVM(JavaVM **pvm, void **penv, void *args); + +_JNI_IMPORT_OR_EXPORT_ jint JNICALL +JNI_GetCreatedJavaVMs(JavaVM **, jsize, jsize *); + +/* Defined by native libraries. */ +JNIEXPORT jint JNICALL +JNI_OnLoad(JavaVM *vm, void *reserved); + +JNIEXPORT void JNICALL +JNI_OnUnload(JavaVM *vm, void *reserved); + +#define JNI_VERSION_1_1 0x00010001 +#define JNI_VERSION_1_2 0x00010002 +#define JNI_VERSION_1_4 0x00010004 +#define JNI_VERSION_1_6 0x00010006 +#define JNI_VERSION_1_8 0x00010008 + +#ifdef __cplusplus +} /* extern "C" */ +#endif /* __cplusplus */ + +#endif /* !_JAVASOFT_JNI_H_ */ diff --git a/jdk-1.8.0.281/include/jvmti.h b/jdk-1.8.0.281/include/jvmti.h new file mode 100755 index 0000000..74243f5 --- /dev/null +++ b/jdk-1.8.0.281/include/jvmti.h @@ -0,0 +1,2534 @@ +/* + * Copyright (c) 2003, 2011, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + + /* AUTOMATICALLY GENERATED FILE - DO NOT EDIT */ + + + /* Include file for the Java(tm) Virtual Machine Tool Interface */ + +#ifndef _JAVA_JVMTI_H_ +#define _JAVA_JVMTI_H_ + +#include "jni.h" + +#ifdef __cplusplus +extern "C" { +#endif + +enum { + JVMTI_VERSION_1 = 0x30010000, + JVMTI_VERSION_1_0 = 0x30010000, + JVMTI_VERSION_1_1 = 0x30010100, + JVMTI_VERSION_1_2 = 0x30010200, + + JVMTI_VERSION = 0x30000000 + (1 * 0x10000) + (2 * 0x100) + 1 /* version: 1.2.1 */ +}; + +JNIEXPORT jint JNICALL +Agent_OnLoad(JavaVM *vm, char *options, void *reserved); + +JNIEXPORT jint JNICALL +Agent_OnAttach(JavaVM* vm, char* options, void* reserved); + +JNIEXPORT void JNICALL +Agent_OnUnload(JavaVM *vm); + + /* Forward declaration of the environment */ + +struct _jvmtiEnv; + +struct jvmtiInterface_1_; + +#ifdef __cplusplus +typedef _jvmtiEnv jvmtiEnv; +#else +typedef const struct jvmtiInterface_1_ *jvmtiEnv; +#endif /* __cplusplus */ + +/* Derived Base Types */ + +typedef jobject jthread; +typedef jobject jthreadGroup; +typedef jlong jlocation; +struct _jrawMonitorID; +typedef struct _jrawMonitorID *jrawMonitorID; +typedef struct JNINativeInterface_ jniNativeInterface; + + /* Constants */ + + + /* Thread State Flags */ + +enum { + JVMTI_THREAD_STATE_ALIVE = 0x0001, + JVMTI_THREAD_STATE_TERMINATED = 0x0002, + JVMTI_THREAD_STATE_RUNNABLE = 0x0004, + JVMTI_THREAD_STATE_BLOCKED_ON_MONITOR_ENTER = 0x0400, + JVMTI_THREAD_STATE_WAITING = 0x0080, + JVMTI_THREAD_STATE_WAITING_INDEFINITELY = 0x0010, + JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT = 0x0020, + JVMTI_THREAD_STATE_SLEEPING = 0x0040, + JVMTI_THREAD_STATE_IN_OBJECT_WAIT = 0x0100, + JVMTI_THREAD_STATE_PARKED = 0x0200, + JVMTI_THREAD_STATE_SUSPENDED = 0x100000, + JVMTI_THREAD_STATE_INTERRUPTED = 0x200000, + JVMTI_THREAD_STATE_IN_NATIVE = 0x400000, + JVMTI_THREAD_STATE_VENDOR_1 = 0x10000000, + JVMTI_THREAD_STATE_VENDOR_2 = 0x20000000, + JVMTI_THREAD_STATE_VENDOR_3 = 0x40000000 +}; + + /* java.lang.Thread.State Conversion Masks */ + +enum { + JVMTI_JAVA_LANG_THREAD_STATE_MASK = JVMTI_THREAD_STATE_TERMINATED | JVMTI_THREAD_STATE_ALIVE | JVMTI_THREAD_STATE_RUNNABLE | JVMTI_THREAD_STATE_BLOCKED_ON_MONITOR_ENTER | JVMTI_THREAD_STATE_WAITING | JVMTI_THREAD_STATE_WAITING_INDEFINITELY | JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT, + JVMTI_JAVA_LANG_THREAD_STATE_NEW = 0, + JVMTI_JAVA_LANG_THREAD_STATE_TERMINATED = JVMTI_THREAD_STATE_TERMINATED, + JVMTI_JAVA_LANG_THREAD_STATE_RUNNABLE = JVMTI_THREAD_STATE_ALIVE | JVMTI_THREAD_STATE_RUNNABLE, + JVMTI_JAVA_LANG_THREAD_STATE_BLOCKED = JVMTI_THREAD_STATE_ALIVE | JVMTI_THREAD_STATE_BLOCKED_ON_MONITOR_ENTER, + JVMTI_JAVA_LANG_THREAD_STATE_WAITING = JVMTI_THREAD_STATE_ALIVE | JVMTI_THREAD_STATE_WAITING | JVMTI_THREAD_STATE_WAITING_INDEFINITELY, + JVMTI_JAVA_LANG_THREAD_STATE_TIMED_WAITING = JVMTI_THREAD_STATE_ALIVE | JVMTI_THREAD_STATE_WAITING | JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT +}; + + /* Thread Priority Constants */ + +enum { + JVMTI_THREAD_MIN_PRIORITY = 1, + JVMTI_THREAD_NORM_PRIORITY = 5, + JVMTI_THREAD_MAX_PRIORITY = 10 +}; + + /* Heap Filter Flags */ + +enum { + JVMTI_HEAP_FILTER_TAGGED = 0x4, + JVMTI_HEAP_FILTER_UNTAGGED = 0x8, + JVMTI_HEAP_FILTER_CLASS_TAGGED = 0x10, + JVMTI_HEAP_FILTER_CLASS_UNTAGGED = 0x20 +}; + + /* Heap Visit Control Flags */ + +enum { + JVMTI_VISIT_OBJECTS = 0x100, + JVMTI_VISIT_ABORT = 0x8000 +}; + + /* Heap Reference Enumeration */ + +typedef enum { + JVMTI_HEAP_REFERENCE_CLASS = 1, + JVMTI_HEAP_REFERENCE_FIELD = 2, + JVMTI_HEAP_REFERENCE_ARRAY_ELEMENT = 3, + JVMTI_HEAP_REFERENCE_CLASS_LOADER = 4, + JVMTI_HEAP_REFERENCE_SIGNERS = 5, + JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN = 6, + JVMTI_HEAP_REFERENCE_INTERFACE = 7, + JVMTI_HEAP_REFERENCE_STATIC_FIELD = 8, + JVMTI_HEAP_REFERENCE_CONSTANT_POOL = 9, + JVMTI_HEAP_REFERENCE_SUPERCLASS = 10, + JVMTI_HEAP_REFERENCE_JNI_GLOBAL = 21, + JVMTI_HEAP_REFERENCE_SYSTEM_CLASS = 22, + JVMTI_HEAP_REFERENCE_MONITOR = 23, + JVMTI_HEAP_REFERENCE_STACK_LOCAL = 24, + JVMTI_HEAP_REFERENCE_JNI_LOCAL = 25, + JVMTI_HEAP_REFERENCE_THREAD = 26, + JVMTI_HEAP_REFERENCE_OTHER = 27 +} jvmtiHeapReferenceKind; + + /* Primitive Type Enumeration */ + +typedef enum { + JVMTI_PRIMITIVE_TYPE_BOOLEAN = 90, + JVMTI_PRIMITIVE_TYPE_BYTE = 66, + JVMTI_PRIMITIVE_TYPE_CHAR = 67, + JVMTI_PRIMITIVE_TYPE_SHORT = 83, + JVMTI_PRIMITIVE_TYPE_INT = 73, + JVMTI_PRIMITIVE_TYPE_LONG = 74, + JVMTI_PRIMITIVE_TYPE_FLOAT = 70, + JVMTI_PRIMITIVE_TYPE_DOUBLE = 68 +} jvmtiPrimitiveType; + + /* Heap Object Filter Enumeration */ + +typedef enum { + JVMTI_HEAP_OBJECT_TAGGED = 1, + JVMTI_HEAP_OBJECT_UNTAGGED = 2, + JVMTI_HEAP_OBJECT_EITHER = 3 +} jvmtiHeapObjectFilter; + + /* Heap Root Kind Enumeration */ + +typedef enum { + JVMTI_HEAP_ROOT_JNI_GLOBAL = 1, + JVMTI_HEAP_ROOT_SYSTEM_CLASS = 2, + JVMTI_HEAP_ROOT_MONITOR = 3, + JVMTI_HEAP_ROOT_STACK_LOCAL = 4, + JVMTI_HEAP_ROOT_JNI_LOCAL = 5, + JVMTI_HEAP_ROOT_THREAD = 6, + JVMTI_HEAP_ROOT_OTHER = 7 +} jvmtiHeapRootKind; + + /* Object Reference Enumeration */ + +typedef enum { + JVMTI_REFERENCE_CLASS = 1, + JVMTI_REFERENCE_FIELD = 2, + JVMTI_REFERENCE_ARRAY_ELEMENT = 3, + JVMTI_REFERENCE_CLASS_LOADER = 4, + JVMTI_REFERENCE_SIGNERS = 5, + JVMTI_REFERENCE_PROTECTION_DOMAIN = 6, + JVMTI_REFERENCE_INTERFACE = 7, + JVMTI_REFERENCE_STATIC_FIELD = 8, + JVMTI_REFERENCE_CONSTANT_POOL = 9 +} jvmtiObjectReferenceKind; + + /* Iteration Control Enumeration */ + +typedef enum { + JVMTI_ITERATION_CONTINUE = 1, + JVMTI_ITERATION_IGNORE = 2, + JVMTI_ITERATION_ABORT = 0 +} jvmtiIterationControl; + + /* Class Status Flags */ + +enum { + JVMTI_CLASS_STATUS_VERIFIED = 1, + JVMTI_CLASS_STATUS_PREPARED = 2, + JVMTI_CLASS_STATUS_INITIALIZED = 4, + JVMTI_CLASS_STATUS_ERROR = 8, + JVMTI_CLASS_STATUS_ARRAY = 16, + JVMTI_CLASS_STATUS_PRIMITIVE = 32 +}; + + /* Event Enable/Disable */ + +typedef enum { + JVMTI_ENABLE = 1, + JVMTI_DISABLE = 0 +} jvmtiEventMode; + + /* Extension Function/Event Parameter Types */ + +typedef enum { + JVMTI_TYPE_JBYTE = 101, + JVMTI_TYPE_JCHAR = 102, + JVMTI_TYPE_JSHORT = 103, + JVMTI_TYPE_JINT = 104, + JVMTI_TYPE_JLONG = 105, + JVMTI_TYPE_JFLOAT = 106, + JVMTI_TYPE_JDOUBLE = 107, + JVMTI_TYPE_JBOOLEAN = 108, + JVMTI_TYPE_JOBJECT = 109, + JVMTI_TYPE_JTHREAD = 110, + JVMTI_TYPE_JCLASS = 111, + JVMTI_TYPE_JVALUE = 112, + JVMTI_TYPE_JFIELDID = 113, + JVMTI_TYPE_JMETHODID = 114, + JVMTI_TYPE_CCHAR = 115, + JVMTI_TYPE_CVOID = 116, + JVMTI_TYPE_JNIENV = 117 +} jvmtiParamTypes; + + /* Extension Function/Event Parameter Kinds */ + +typedef enum { + JVMTI_KIND_IN = 91, + JVMTI_KIND_IN_PTR = 92, + JVMTI_KIND_IN_BUF = 93, + JVMTI_KIND_ALLOC_BUF = 94, + JVMTI_KIND_ALLOC_ALLOC_BUF = 95, + JVMTI_KIND_OUT = 96, + JVMTI_KIND_OUT_BUF = 97 +} jvmtiParamKind; + + /* Timer Kinds */ + +typedef enum { + JVMTI_TIMER_USER_CPU = 30, + JVMTI_TIMER_TOTAL_CPU = 31, + JVMTI_TIMER_ELAPSED = 32 +} jvmtiTimerKind; + + /* Phases of execution */ + +typedef enum { + JVMTI_PHASE_ONLOAD = 1, + JVMTI_PHASE_PRIMORDIAL = 2, + JVMTI_PHASE_START = 6, + JVMTI_PHASE_LIVE = 4, + JVMTI_PHASE_DEAD = 8 +} jvmtiPhase; + + /* Version Interface Types */ + +enum { + JVMTI_VERSION_INTERFACE_JNI = 0x00000000, + JVMTI_VERSION_INTERFACE_JVMTI = 0x30000000 +}; + + /* Version Masks */ + +enum { + JVMTI_VERSION_MASK_INTERFACE_TYPE = 0x70000000, + JVMTI_VERSION_MASK_MAJOR = 0x0FFF0000, + JVMTI_VERSION_MASK_MINOR = 0x0000FF00, + JVMTI_VERSION_MASK_MICRO = 0x000000FF +}; + + /* Version Shifts */ + +enum { + JVMTI_VERSION_SHIFT_MAJOR = 16, + JVMTI_VERSION_SHIFT_MINOR = 8, + JVMTI_VERSION_SHIFT_MICRO = 0 +}; + + /* Verbose Flag Enumeration */ + +typedef enum { + JVMTI_VERBOSE_OTHER = 0, + JVMTI_VERBOSE_GC = 1, + JVMTI_VERBOSE_CLASS = 2, + JVMTI_VERBOSE_JNI = 4 +} jvmtiVerboseFlag; + + /* JLocation Format Enumeration */ + +typedef enum { + JVMTI_JLOCATION_JVMBCI = 1, + JVMTI_JLOCATION_MACHINEPC = 2, + JVMTI_JLOCATION_OTHER = 0 +} jvmtiJlocationFormat; + + /* Resource Exhaustion Flags */ + +enum { + JVMTI_RESOURCE_EXHAUSTED_OOM_ERROR = 0x0001, + JVMTI_RESOURCE_EXHAUSTED_JAVA_HEAP = 0x0002, + JVMTI_RESOURCE_EXHAUSTED_THREADS = 0x0004 +}; + + /* Errors */ + +typedef enum { + JVMTI_ERROR_NONE = 0, + JVMTI_ERROR_INVALID_THREAD = 10, + JVMTI_ERROR_INVALID_THREAD_GROUP = 11, + JVMTI_ERROR_INVALID_PRIORITY = 12, + JVMTI_ERROR_THREAD_NOT_SUSPENDED = 13, + JVMTI_ERROR_THREAD_SUSPENDED = 14, + JVMTI_ERROR_THREAD_NOT_ALIVE = 15, + JVMTI_ERROR_INVALID_OBJECT = 20, + JVMTI_ERROR_INVALID_CLASS = 21, + JVMTI_ERROR_CLASS_NOT_PREPARED = 22, + JVMTI_ERROR_INVALID_METHODID = 23, + JVMTI_ERROR_INVALID_LOCATION = 24, + JVMTI_ERROR_INVALID_FIELDID = 25, + JVMTI_ERROR_NO_MORE_FRAMES = 31, + JVMTI_ERROR_OPAQUE_FRAME = 32, + JVMTI_ERROR_TYPE_MISMATCH = 34, + JVMTI_ERROR_INVALID_SLOT = 35, + JVMTI_ERROR_DUPLICATE = 40, + JVMTI_ERROR_NOT_FOUND = 41, + JVMTI_ERROR_INVALID_MONITOR = 50, + JVMTI_ERROR_NOT_MONITOR_OWNER = 51, + JVMTI_ERROR_INTERRUPT = 52, + JVMTI_ERROR_INVALID_CLASS_FORMAT = 60, + JVMTI_ERROR_CIRCULAR_CLASS_DEFINITION = 61, + JVMTI_ERROR_FAILS_VERIFICATION = 62, + JVMTI_ERROR_UNSUPPORTED_REDEFINITION_METHOD_ADDED = 63, + JVMTI_ERROR_UNSUPPORTED_REDEFINITION_SCHEMA_CHANGED = 64, + JVMTI_ERROR_INVALID_TYPESTATE = 65, + JVMTI_ERROR_UNSUPPORTED_REDEFINITION_HIERARCHY_CHANGED = 66, + JVMTI_ERROR_UNSUPPORTED_REDEFINITION_METHOD_DELETED = 67, + JVMTI_ERROR_UNSUPPORTED_VERSION = 68, + JVMTI_ERROR_NAMES_DONT_MATCH = 69, + JVMTI_ERROR_UNSUPPORTED_REDEFINITION_CLASS_MODIFIERS_CHANGED = 70, + JVMTI_ERROR_UNSUPPORTED_REDEFINITION_METHOD_MODIFIERS_CHANGED = 71, + JVMTI_ERROR_UNMODIFIABLE_CLASS = 79, + JVMTI_ERROR_NOT_AVAILABLE = 98, + JVMTI_ERROR_MUST_POSSESS_CAPABILITY = 99, + JVMTI_ERROR_NULL_POINTER = 100, + JVMTI_ERROR_ABSENT_INFORMATION = 101, + JVMTI_ERROR_INVALID_EVENT_TYPE = 102, + JVMTI_ERROR_ILLEGAL_ARGUMENT = 103, + JVMTI_ERROR_NATIVE_METHOD = 104, + JVMTI_ERROR_CLASS_LOADER_UNSUPPORTED = 106, + JVMTI_ERROR_OUT_OF_MEMORY = 110, + JVMTI_ERROR_ACCESS_DENIED = 111, + JVMTI_ERROR_WRONG_PHASE = 112, + JVMTI_ERROR_INTERNAL = 113, + JVMTI_ERROR_UNATTACHED_THREAD = 115, + JVMTI_ERROR_INVALID_ENVIRONMENT = 116, + JVMTI_ERROR_MAX = 116 +} jvmtiError; + + /* Event IDs */ + +typedef enum { + JVMTI_MIN_EVENT_TYPE_VAL = 50, + JVMTI_EVENT_VM_INIT = 50, + JVMTI_EVENT_VM_DEATH = 51, + JVMTI_EVENT_THREAD_START = 52, + JVMTI_EVENT_THREAD_END = 53, + JVMTI_EVENT_CLASS_FILE_LOAD_HOOK = 54, + JVMTI_EVENT_CLASS_LOAD = 55, + JVMTI_EVENT_CLASS_PREPARE = 56, + JVMTI_EVENT_VM_START = 57, + JVMTI_EVENT_EXCEPTION = 58, + JVMTI_EVENT_EXCEPTION_CATCH = 59, + JVMTI_EVENT_SINGLE_STEP = 60, + JVMTI_EVENT_FRAME_POP = 61, + JVMTI_EVENT_BREAKPOINT = 62, + JVMTI_EVENT_FIELD_ACCESS = 63, + JVMTI_EVENT_FIELD_MODIFICATION = 64, + JVMTI_EVENT_METHOD_ENTRY = 65, + JVMTI_EVENT_METHOD_EXIT = 66, + JVMTI_EVENT_NATIVE_METHOD_BIND = 67, + JVMTI_EVENT_COMPILED_METHOD_LOAD = 68, + JVMTI_EVENT_COMPILED_METHOD_UNLOAD = 69, + JVMTI_EVENT_DYNAMIC_CODE_GENERATED = 70, + JVMTI_EVENT_DATA_DUMP_REQUEST = 71, + JVMTI_EVENT_MONITOR_WAIT = 73, + JVMTI_EVENT_MONITOR_WAITED = 74, + JVMTI_EVENT_MONITOR_CONTENDED_ENTER = 75, + JVMTI_EVENT_MONITOR_CONTENDED_ENTERED = 76, + JVMTI_EVENT_RESOURCE_EXHAUSTED = 80, + JVMTI_EVENT_GARBAGE_COLLECTION_START = 81, + JVMTI_EVENT_GARBAGE_COLLECTION_FINISH = 82, + JVMTI_EVENT_OBJECT_FREE = 83, + JVMTI_EVENT_VM_OBJECT_ALLOC = 84, + JVMTI_MAX_EVENT_TYPE_VAL = 84 +} jvmtiEvent; + + + /* Pre-Declarations */ +struct _jvmtiThreadInfo; +typedef struct _jvmtiThreadInfo jvmtiThreadInfo; +struct _jvmtiMonitorStackDepthInfo; +typedef struct _jvmtiMonitorStackDepthInfo jvmtiMonitorStackDepthInfo; +struct _jvmtiThreadGroupInfo; +typedef struct _jvmtiThreadGroupInfo jvmtiThreadGroupInfo; +struct _jvmtiFrameInfo; +typedef struct _jvmtiFrameInfo jvmtiFrameInfo; +struct _jvmtiStackInfo; +typedef struct _jvmtiStackInfo jvmtiStackInfo; +struct _jvmtiHeapReferenceInfoField; +typedef struct _jvmtiHeapReferenceInfoField jvmtiHeapReferenceInfoField; +struct _jvmtiHeapReferenceInfoArray; +typedef struct _jvmtiHeapReferenceInfoArray jvmtiHeapReferenceInfoArray; +struct _jvmtiHeapReferenceInfoConstantPool; +typedef struct _jvmtiHeapReferenceInfoConstantPool jvmtiHeapReferenceInfoConstantPool; +struct _jvmtiHeapReferenceInfoStackLocal; +typedef struct _jvmtiHeapReferenceInfoStackLocal jvmtiHeapReferenceInfoStackLocal; +struct _jvmtiHeapReferenceInfoJniLocal; +typedef struct _jvmtiHeapReferenceInfoJniLocal jvmtiHeapReferenceInfoJniLocal; +struct _jvmtiHeapReferenceInfoReserved; +typedef struct _jvmtiHeapReferenceInfoReserved jvmtiHeapReferenceInfoReserved; +union _jvmtiHeapReferenceInfo; +typedef union _jvmtiHeapReferenceInfo jvmtiHeapReferenceInfo; +struct _jvmtiHeapCallbacks; +typedef struct _jvmtiHeapCallbacks jvmtiHeapCallbacks; +struct _jvmtiClassDefinition; +typedef struct _jvmtiClassDefinition jvmtiClassDefinition; +struct _jvmtiMonitorUsage; +typedef struct _jvmtiMonitorUsage jvmtiMonitorUsage; +struct _jvmtiLineNumberEntry; +typedef struct _jvmtiLineNumberEntry jvmtiLineNumberEntry; +struct _jvmtiLocalVariableEntry; +typedef struct _jvmtiLocalVariableEntry jvmtiLocalVariableEntry; +struct _jvmtiParamInfo; +typedef struct _jvmtiParamInfo jvmtiParamInfo; +struct _jvmtiExtensionFunctionInfo; +typedef struct _jvmtiExtensionFunctionInfo jvmtiExtensionFunctionInfo; +struct _jvmtiExtensionEventInfo; +typedef struct _jvmtiExtensionEventInfo jvmtiExtensionEventInfo; +struct _jvmtiTimerInfo; +typedef struct _jvmtiTimerInfo jvmtiTimerInfo; +struct _jvmtiAddrLocationMap; +typedef struct _jvmtiAddrLocationMap jvmtiAddrLocationMap; + + /* Function Types */ + +typedef void (JNICALL *jvmtiStartFunction) + (jvmtiEnv* jvmti_env, JNIEnv* jni_env, void* arg); + +typedef jint (JNICALL *jvmtiHeapIterationCallback) + (jlong class_tag, jlong size, jlong* tag_ptr, jint length, void* user_data); + +typedef jint (JNICALL *jvmtiHeapReferenceCallback) + (jvmtiHeapReferenceKind reference_kind, const jvmtiHeapReferenceInfo* reference_info, jlong class_tag, jlong referrer_class_tag, jlong size, jlong* tag_ptr, jlong* referrer_tag_ptr, jint length, void* user_data); + +typedef jint (JNICALL *jvmtiPrimitiveFieldCallback) + (jvmtiHeapReferenceKind kind, const jvmtiHeapReferenceInfo* info, jlong object_class_tag, jlong* object_tag_ptr, jvalue value, jvmtiPrimitiveType value_type, void* user_data); + +typedef jint (JNICALL *jvmtiArrayPrimitiveValueCallback) + (jlong class_tag, jlong size, jlong* tag_ptr, jint element_count, jvmtiPrimitiveType element_type, const void* elements, void* user_data); + +typedef jint (JNICALL *jvmtiStringPrimitiveValueCallback) + (jlong class_tag, jlong size, jlong* tag_ptr, const jchar* value, jint value_length, void* user_data); + +typedef jint (JNICALL *jvmtiReservedCallback) + (); + +typedef jvmtiIterationControl (JNICALL *jvmtiHeapObjectCallback) + (jlong class_tag, jlong size, jlong* tag_ptr, void* user_data); + +typedef jvmtiIterationControl (JNICALL *jvmtiHeapRootCallback) + (jvmtiHeapRootKind root_kind, jlong class_tag, jlong size, jlong* tag_ptr, void* user_data); + +typedef jvmtiIterationControl (JNICALL *jvmtiStackReferenceCallback) + (jvmtiHeapRootKind root_kind, jlong class_tag, jlong size, jlong* tag_ptr, jlong thread_tag, jint depth, jmethodID method, jint slot, void* user_data); + +typedef jvmtiIterationControl (JNICALL *jvmtiObjectReferenceCallback) + (jvmtiObjectReferenceKind reference_kind, jlong class_tag, jlong size, jlong* tag_ptr, jlong referrer_tag, jint referrer_index, void* user_data); + +typedef jvmtiError (JNICALL *jvmtiExtensionFunction) + (jvmtiEnv* jvmti_env, ...); + +typedef void (JNICALL *jvmtiExtensionEvent) + (jvmtiEnv* jvmti_env, ...); + + + /* Structure Types */ +struct _jvmtiThreadInfo { + char* name; + jint priority; + jboolean is_daemon; + jthreadGroup thread_group; + jobject context_class_loader; +}; +struct _jvmtiMonitorStackDepthInfo { + jobject monitor; + jint stack_depth; +}; +struct _jvmtiThreadGroupInfo { + jthreadGroup parent; + char* name; + jint max_priority; + jboolean is_daemon; +}; +struct _jvmtiFrameInfo { + jmethodID method; + jlocation location; +}; +struct _jvmtiStackInfo { + jthread thread; + jint state; + jvmtiFrameInfo* frame_buffer; + jint frame_count; +}; +struct _jvmtiHeapReferenceInfoField { + jint index; +}; +struct _jvmtiHeapReferenceInfoArray { + jint index; +}; +struct _jvmtiHeapReferenceInfoConstantPool { + jint index; +}; +struct _jvmtiHeapReferenceInfoStackLocal { + jlong thread_tag; + jlong thread_id; + jint depth; + jmethodID method; + jlocation location; + jint slot; +}; +struct _jvmtiHeapReferenceInfoJniLocal { + jlong thread_tag; + jlong thread_id; + jint depth; + jmethodID method; +}; +struct _jvmtiHeapReferenceInfoReserved { + jlong reserved1; + jlong reserved2; + jlong reserved3; + jlong reserved4; + jlong reserved5; + jlong reserved6; + jlong reserved7; + jlong reserved8; +}; +union _jvmtiHeapReferenceInfo { + jvmtiHeapReferenceInfoField field; + jvmtiHeapReferenceInfoArray array; + jvmtiHeapReferenceInfoConstantPool constant_pool; + jvmtiHeapReferenceInfoStackLocal stack_local; + jvmtiHeapReferenceInfoJniLocal jni_local; + jvmtiHeapReferenceInfoReserved other; +}; +struct _jvmtiHeapCallbacks { + jvmtiHeapIterationCallback heap_iteration_callback; + jvmtiHeapReferenceCallback heap_reference_callback; + jvmtiPrimitiveFieldCallback primitive_field_callback; + jvmtiArrayPrimitiveValueCallback array_primitive_value_callback; + jvmtiStringPrimitiveValueCallback string_primitive_value_callback; + jvmtiReservedCallback reserved5; + jvmtiReservedCallback reserved6; + jvmtiReservedCallback reserved7; + jvmtiReservedCallback reserved8; + jvmtiReservedCallback reserved9; + jvmtiReservedCallback reserved10; + jvmtiReservedCallback reserved11; + jvmtiReservedCallback reserved12; + jvmtiReservedCallback reserved13; + jvmtiReservedCallback reserved14; + jvmtiReservedCallback reserved15; +}; +struct _jvmtiClassDefinition { + jclass klass; + jint class_byte_count; + const unsigned char* class_bytes; +}; +struct _jvmtiMonitorUsage { + jthread owner; + jint entry_count; + jint waiter_count; + jthread* waiters; + jint notify_waiter_count; + jthread* notify_waiters; +}; +struct _jvmtiLineNumberEntry { + jlocation start_location; + jint line_number; +}; +struct _jvmtiLocalVariableEntry { + jlocation start_location; + jint length; + char* name; + char* signature; + char* generic_signature; + jint slot; +}; +struct _jvmtiParamInfo { + char* name; + jvmtiParamKind kind; + jvmtiParamTypes base_type; + jboolean null_ok; +}; +struct _jvmtiExtensionFunctionInfo { + jvmtiExtensionFunction func; + char* id; + char* short_description; + jint param_count; + jvmtiParamInfo* params; + jint error_count; + jvmtiError* errors; +}; +struct _jvmtiExtensionEventInfo { + jint extension_event_index; + char* id; + char* short_description; + jint param_count; + jvmtiParamInfo* params; +}; +struct _jvmtiTimerInfo { + jlong max_value; + jboolean may_skip_forward; + jboolean may_skip_backward; + jvmtiTimerKind kind; + jlong reserved1; + jlong reserved2; +}; +struct _jvmtiAddrLocationMap { + const void* start_address; + jlocation location; +}; + +typedef struct { + unsigned int can_tag_objects : 1; + unsigned int can_generate_field_modification_events : 1; + unsigned int can_generate_field_access_events : 1; + unsigned int can_get_bytecodes : 1; + unsigned int can_get_synthetic_attribute : 1; + unsigned int can_get_owned_monitor_info : 1; + unsigned int can_get_current_contended_monitor : 1; + unsigned int can_get_monitor_info : 1; + unsigned int can_pop_frame : 1; + unsigned int can_redefine_classes : 1; + unsigned int can_signal_thread : 1; + unsigned int can_get_source_file_name : 1; + unsigned int can_get_line_numbers : 1; + unsigned int can_get_source_debug_extension : 1; + unsigned int can_access_local_variables : 1; + unsigned int can_maintain_original_method_order : 1; + unsigned int can_generate_single_step_events : 1; + unsigned int can_generate_exception_events : 1; + unsigned int can_generate_frame_pop_events : 1; + unsigned int can_generate_breakpoint_events : 1; + unsigned int can_suspend : 1; + unsigned int can_redefine_any_class : 1; + unsigned int can_get_current_thread_cpu_time : 1; + unsigned int can_get_thread_cpu_time : 1; + unsigned int can_generate_method_entry_events : 1; + unsigned int can_generate_method_exit_events : 1; + unsigned int can_generate_all_class_hook_events : 1; + unsigned int can_generate_compiled_method_load_events : 1; + unsigned int can_generate_monitor_events : 1; + unsigned int can_generate_vm_object_alloc_events : 1; + unsigned int can_generate_native_method_bind_events : 1; + unsigned int can_generate_garbage_collection_events : 1; + unsigned int can_generate_object_free_events : 1; + unsigned int can_force_early_return : 1; + unsigned int can_get_owned_monitor_stack_depth_info : 1; + unsigned int can_get_constant_pool : 1; + unsigned int can_set_native_method_prefix : 1; + unsigned int can_retransform_classes : 1; + unsigned int can_retransform_any_class : 1; + unsigned int can_generate_resource_exhaustion_heap_events : 1; + unsigned int can_generate_resource_exhaustion_threads_events : 1; + unsigned int : 7; + unsigned int : 16; + unsigned int : 16; + unsigned int : 16; + unsigned int : 16; + unsigned int : 16; +} jvmtiCapabilities; + + + /* Event Definitions */ + +typedef void (JNICALL *jvmtiEventReserved)(void); + + +typedef void (JNICALL *jvmtiEventBreakpoint) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jlocation location); + +typedef void (JNICALL *jvmtiEventClassFileLoadHook) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jclass class_being_redefined, + jobject loader, + const char* name, + jobject protection_domain, + jint class_data_len, + const unsigned char* class_data, + jint* new_class_data_len, + unsigned char** new_class_data); + +typedef void (JNICALL *jvmtiEventClassLoad) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jclass klass); + +typedef void (JNICALL *jvmtiEventClassPrepare) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jclass klass); + +typedef void (JNICALL *jvmtiEventCompiledMethodLoad) + (jvmtiEnv *jvmti_env, + jmethodID method, + jint code_size, + const void* code_addr, + jint map_length, + const jvmtiAddrLocationMap* map, + const void* compile_info); + +typedef void (JNICALL *jvmtiEventCompiledMethodUnload) + (jvmtiEnv *jvmti_env, + jmethodID method, + const void* code_addr); + +typedef void (JNICALL *jvmtiEventDataDumpRequest) + (jvmtiEnv *jvmti_env); + +typedef void (JNICALL *jvmtiEventDynamicCodeGenerated) + (jvmtiEnv *jvmti_env, + const char* name, + const void* address, + jint length); + +typedef void (JNICALL *jvmtiEventException) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jlocation location, + jobject exception, + jmethodID catch_method, + jlocation catch_location); + +typedef void (JNICALL *jvmtiEventExceptionCatch) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jlocation location, + jobject exception); + +typedef void (JNICALL *jvmtiEventFieldAccess) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jlocation location, + jclass field_klass, + jobject object, + jfieldID field); + +typedef void (JNICALL *jvmtiEventFieldModification) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jlocation location, + jclass field_klass, + jobject object, + jfieldID field, + char signature_type, + jvalue new_value); + +typedef void (JNICALL *jvmtiEventFramePop) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jboolean was_popped_by_exception); + +typedef void (JNICALL *jvmtiEventGarbageCollectionFinish) + (jvmtiEnv *jvmti_env); + +typedef void (JNICALL *jvmtiEventGarbageCollectionStart) + (jvmtiEnv *jvmti_env); + +typedef void (JNICALL *jvmtiEventMethodEntry) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method); + +typedef void (JNICALL *jvmtiEventMethodExit) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jboolean was_popped_by_exception, + jvalue return_value); + +typedef void (JNICALL *jvmtiEventMonitorContendedEnter) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jobject object); + +typedef void (JNICALL *jvmtiEventMonitorContendedEntered) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jobject object); + +typedef void (JNICALL *jvmtiEventMonitorWait) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jobject object, + jlong timeout); + +typedef void (JNICALL *jvmtiEventMonitorWaited) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jobject object, + jboolean timed_out); + +typedef void (JNICALL *jvmtiEventNativeMethodBind) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + void* address, + void** new_address_ptr); + +typedef void (JNICALL *jvmtiEventObjectFree) + (jvmtiEnv *jvmti_env, + jlong tag); + +typedef void (JNICALL *jvmtiEventResourceExhausted) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jint flags, + const void* reserved, + const char* description); + +typedef void (JNICALL *jvmtiEventSingleStep) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jmethodID method, + jlocation location); + +typedef void (JNICALL *jvmtiEventThreadEnd) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread); + +typedef void (JNICALL *jvmtiEventThreadStart) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread); + +typedef void (JNICALL *jvmtiEventVMDeath) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env); + +typedef void (JNICALL *jvmtiEventVMInit) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread); + +typedef void (JNICALL *jvmtiEventVMObjectAlloc) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env, + jthread thread, + jobject object, + jclass object_klass, + jlong size); + +typedef void (JNICALL *jvmtiEventVMStart) + (jvmtiEnv *jvmti_env, + JNIEnv* jni_env); + + /* Event Callback Structure */ + +typedef struct { + /* 50 : VM Initialization Event */ + jvmtiEventVMInit VMInit; + /* 51 : VM Death Event */ + jvmtiEventVMDeath VMDeath; + /* 52 : Thread Start */ + jvmtiEventThreadStart ThreadStart; + /* 53 : Thread End */ + jvmtiEventThreadEnd ThreadEnd; + /* 54 : Class File Load Hook */ + jvmtiEventClassFileLoadHook ClassFileLoadHook; + /* 55 : Class Load */ + jvmtiEventClassLoad ClassLoad; + /* 56 : Class Prepare */ + jvmtiEventClassPrepare ClassPrepare; + /* 57 : VM Start Event */ + jvmtiEventVMStart VMStart; + /* 58 : Exception */ + jvmtiEventException Exception; + /* 59 : Exception Catch */ + jvmtiEventExceptionCatch ExceptionCatch; + /* 60 : Single Step */ + jvmtiEventSingleStep SingleStep; + /* 61 : Frame Pop */ + jvmtiEventFramePop FramePop; + /* 62 : Breakpoint */ + jvmtiEventBreakpoint Breakpoint; + /* 63 : Field Access */ + jvmtiEventFieldAccess FieldAccess; + /* 64 : Field Modification */ + jvmtiEventFieldModification FieldModification; + /* 65 : Method Entry */ + jvmtiEventMethodEntry MethodEntry; + /* 66 : Method Exit */ + jvmtiEventMethodExit MethodExit; + /* 67 : Native Method Bind */ + jvmtiEventNativeMethodBind NativeMethodBind; + /* 68 : Compiled Method Load */ + jvmtiEventCompiledMethodLoad CompiledMethodLoad; + /* 69 : Compiled Method Unload */ + jvmtiEventCompiledMethodUnload CompiledMethodUnload; + /* 70 : Dynamic Code Generated */ + jvmtiEventDynamicCodeGenerated DynamicCodeGenerated; + /* 71 : Data Dump Request */ + jvmtiEventDataDumpRequest DataDumpRequest; + /* 72 */ + jvmtiEventReserved reserved72; + /* 73 : Monitor Wait */ + jvmtiEventMonitorWait MonitorWait; + /* 74 : Monitor Waited */ + jvmtiEventMonitorWaited MonitorWaited; + /* 75 : Monitor Contended Enter */ + jvmtiEventMonitorContendedEnter MonitorContendedEnter; + /* 76 : Monitor Contended Entered */ + jvmtiEventMonitorContendedEntered MonitorContendedEntered; + /* 77 */ + jvmtiEventReserved reserved77; + /* 78 */ + jvmtiEventReserved reserved78; + /* 79 */ + jvmtiEventReserved reserved79; + /* 80 : Resource Exhausted */ + jvmtiEventResourceExhausted ResourceExhausted; + /* 81 : Garbage Collection Start */ + jvmtiEventGarbageCollectionStart GarbageCollectionStart; + /* 82 : Garbage Collection Finish */ + jvmtiEventGarbageCollectionFinish GarbageCollectionFinish; + /* 83 : Object Free */ + jvmtiEventObjectFree ObjectFree; + /* 84 : VM Object Allocation */ + jvmtiEventVMObjectAlloc VMObjectAlloc; +} jvmtiEventCallbacks; + + + /* Function Interface */ + +typedef struct jvmtiInterface_1_ { + + /* 1 : RESERVED */ + void *reserved1; + + /* 2 : Set Event Notification Mode */ + jvmtiError (JNICALL *SetEventNotificationMode) (jvmtiEnv* env, + jvmtiEventMode mode, + jvmtiEvent event_type, + jthread event_thread, + ...); + + /* 3 : RESERVED */ + void *reserved3; + + /* 4 : Get All Threads */ + jvmtiError (JNICALL *GetAllThreads) (jvmtiEnv* env, + jint* threads_count_ptr, + jthread** threads_ptr); + + /* 5 : Suspend Thread */ + jvmtiError (JNICALL *SuspendThread) (jvmtiEnv* env, + jthread thread); + + /* 6 : Resume Thread */ + jvmtiError (JNICALL *ResumeThread) (jvmtiEnv* env, + jthread thread); + + /* 7 : Stop Thread */ + jvmtiError (JNICALL *StopThread) (jvmtiEnv* env, + jthread thread, + jobject exception); + + /* 8 : Interrupt Thread */ + jvmtiError (JNICALL *InterruptThread) (jvmtiEnv* env, + jthread thread); + + /* 9 : Get Thread Info */ + jvmtiError (JNICALL *GetThreadInfo) (jvmtiEnv* env, + jthread thread, + jvmtiThreadInfo* info_ptr); + + /* 10 : Get Owned Monitor Info */ + jvmtiError (JNICALL *GetOwnedMonitorInfo) (jvmtiEnv* env, + jthread thread, + jint* owned_monitor_count_ptr, + jobject** owned_monitors_ptr); + + /* 11 : Get Current Contended Monitor */ + jvmtiError (JNICALL *GetCurrentContendedMonitor) (jvmtiEnv* env, + jthread thread, + jobject* monitor_ptr); + + /* 12 : Run Agent Thread */ + jvmtiError (JNICALL *RunAgentThread) (jvmtiEnv* env, + jthread thread, + jvmtiStartFunction proc, + const void* arg, + jint priority); + + /* 13 : Get Top Thread Groups */ + jvmtiError (JNICALL *GetTopThreadGroups) (jvmtiEnv* env, + jint* group_count_ptr, + jthreadGroup** groups_ptr); + + /* 14 : Get Thread Group Info */ + jvmtiError (JNICALL *GetThreadGroupInfo) (jvmtiEnv* env, + jthreadGroup group, + jvmtiThreadGroupInfo* info_ptr); + + /* 15 : Get Thread Group Children */ + jvmtiError (JNICALL *GetThreadGroupChildren) (jvmtiEnv* env, + jthreadGroup group, + jint* thread_count_ptr, + jthread** threads_ptr, + jint* group_count_ptr, + jthreadGroup** groups_ptr); + + /* 16 : Get Frame Count */ + jvmtiError (JNICALL *GetFrameCount) (jvmtiEnv* env, + jthread thread, + jint* count_ptr); + + /* 17 : Get Thread State */ + jvmtiError (JNICALL *GetThreadState) (jvmtiEnv* env, + jthread thread, + jint* thread_state_ptr); + + /* 18 : Get Current Thread */ + jvmtiError (JNICALL *GetCurrentThread) (jvmtiEnv* env, + jthread* thread_ptr); + + /* 19 : Get Frame Location */ + jvmtiError (JNICALL *GetFrameLocation) (jvmtiEnv* env, + jthread thread, + jint depth, + jmethodID* method_ptr, + jlocation* location_ptr); + + /* 20 : Notify Frame Pop */ + jvmtiError (JNICALL *NotifyFramePop) (jvmtiEnv* env, + jthread thread, + jint depth); + + /* 21 : Get Local Variable - Object */ + jvmtiError (JNICALL *GetLocalObject) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jobject* value_ptr); + + /* 22 : Get Local Variable - Int */ + jvmtiError (JNICALL *GetLocalInt) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jint* value_ptr); + + /* 23 : Get Local Variable - Long */ + jvmtiError (JNICALL *GetLocalLong) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jlong* value_ptr); + + /* 24 : Get Local Variable - Float */ + jvmtiError (JNICALL *GetLocalFloat) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jfloat* value_ptr); + + /* 25 : Get Local Variable - Double */ + jvmtiError (JNICALL *GetLocalDouble) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jdouble* value_ptr); + + /* 26 : Set Local Variable - Object */ + jvmtiError (JNICALL *SetLocalObject) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jobject value); + + /* 27 : Set Local Variable - Int */ + jvmtiError (JNICALL *SetLocalInt) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jint value); + + /* 28 : Set Local Variable - Long */ + jvmtiError (JNICALL *SetLocalLong) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jlong value); + + /* 29 : Set Local Variable - Float */ + jvmtiError (JNICALL *SetLocalFloat) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jfloat value); + + /* 30 : Set Local Variable - Double */ + jvmtiError (JNICALL *SetLocalDouble) (jvmtiEnv* env, + jthread thread, + jint depth, + jint slot, + jdouble value); + + /* 31 : Create Raw Monitor */ + jvmtiError (JNICALL *CreateRawMonitor) (jvmtiEnv* env, + const char* name, + jrawMonitorID* monitor_ptr); + + /* 32 : Destroy Raw Monitor */ + jvmtiError (JNICALL *DestroyRawMonitor) (jvmtiEnv* env, + jrawMonitorID monitor); + + /* 33 : Raw Monitor Enter */ + jvmtiError (JNICALL *RawMonitorEnter) (jvmtiEnv* env, + jrawMonitorID monitor); + + /* 34 : Raw Monitor Exit */ + jvmtiError (JNICALL *RawMonitorExit) (jvmtiEnv* env, + jrawMonitorID monitor); + + /* 35 : Raw Monitor Wait */ + jvmtiError (JNICALL *RawMonitorWait) (jvmtiEnv* env, + jrawMonitorID monitor, + jlong millis); + + /* 36 : Raw Monitor Notify */ + jvmtiError (JNICALL *RawMonitorNotify) (jvmtiEnv* env, + jrawMonitorID monitor); + + /* 37 : Raw Monitor Notify All */ + jvmtiError (JNICALL *RawMonitorNotifyAll) (jvmtiEnv* env, + jrawMonitorID monitor); + + /* 38 : Set Breakpoint */ + jvmtiError (JNICALL *SetBreakpoint) (jvmtiEnv* env, + jmethodID method, + jlocation location); + + /* 39 : Clear Breakpoint */ + jvmtiError (JNICALL *ClearBreakpoint) (jvmtiEnv* env, + jmethodID method, + jlocation location); + + /* 40 : RESERVED */ + void *reserved40; + + /* 41 : Set Field Access Watch */ + jvmtiError (JNICALL *SetFieldAccessWatch) (jvmtiEnv* env, + jclass klass, + jfieldID field); + + /* 42 : Clear Field Access Watch */ + jvmtiError (JNICALL *ClearFieldAccessWatch) (jvmtiEnv* env, + jclass klass, + jfieldID field); + + /* 43 : Set Field Modification Watch */ + jvmtiError (JNICALL *SetFieldModificationWatch) (jvmtiEnv* env, + jclass klass, + jfieldID field); + + /* 44 : Clear Field Modification Watch */ + jvmtiError (JNICALL *ClearFieldModificationWatch) (jvmtiEnv* env, + jclass klass, + jfieldID field); + + /* 45 : Is Modifiable Class */ + jvmtiError (JNICALL *IsModifiableClass) (jvmtiEnv* env, + jclass klass, + jboolean* is_modifiable_class_ptr); + + /* 46 : Allocate */ + jvmtiError (JNICALL *Allocate) (jvmtiEnv* env, + jlong size, + unsigned char** mem_ptr); + + /* 47 : Deallocate */ + jvmtiError (JNICALL *Deallocate) (jvmtiEnv* env, + unsigned char* mem); + + /* 48 : Get Class Signature */ + jvmtiError (JNICALL *GetClassSignature) (jvmtiEnv* env, + jclass klass, + char** signature_ptr, + char** generic_ptr); + + /* 49 : Get Class Status */ + jvmtiError (JNICALL *GetClassStatus) (jvmtiEnv* env, + jclass klass, + jint* status_ptr); + + /* 50 : Get Source File Name */ + jvmtiError (JNICALL *GetSourceFileName) (jvmtiEnv* env, + jclass klass, + char** source_name_ptr); + + /* 51 : Get Class Modifiers */ + jvmtiError (JNICALL *GetClassModifiers) (jvmtiEnv* env, + jclass klass, + jint* modifiers_ptr); + + /* 52 : Get Class Methods */ + jvmtiError (JNICALL *GetClassMethods) (jvmtiEnv* env, + jclass klass, + jint* method_count_ptr, + jmethodID** methods_ptr); + + /* 53 : Get Class Fields */ + jvmtiError (JNICALL *GetClassFields) (jvmtiEnv* env, + jclass klass, + jint* field_count_ptr, + jfieldID** fields_ptr); + + /* 54 : Get Implemented Interfaces */ + jvmtiError (JNICALL *GetImplementedInterfaces) (jvmtiEnv* env, + jclass klass, + jint* interface_count_ptr, + jclass** interfaces_ptr); + + /* 55 : Is Interface */ + jvmtiError (JNICALL *IsInterface) (jvmtiEnv* env, + jclass klass, + jboolean* is_interface_ptr); + + /* 56 : Is Array Class */ + jvmtiError (JNICALL *IsArrayClass) (jvmtiEnv* env, + jclass klass, + jboolean* is_array_class_ptr); + + /* 57 : Get Class Loader */ + jvmtiError (JNICALL *GetClassLoader) (jvmtiEnv* env, + jclass klass, + jobject* classloader_ptr); + + /* 58 : Get Object Hash Code */ + jvmtiError (JNICALL *GetObjectHashCode) (jvmtiEnv* env, + jobject object, + jint* hash_code_ptr); + + /* 59 : Get Object Monitor Usage */ + jvmtiError (JNICALL *GetObjectMonitorUsage) (jvmtiEnv* env, + jobject object, + jvmtiMonitorUsage* info_ptr); + + /* 60 : Get Field Name (and Signature) */ + jvmtiError (JNICALL *GetFieldName) (jvmtiEnv* env, + jclass klass, + jfieldID field, + char** name_ptr, + char** signature_ptr, + char** generic_ptr); + + /* 61 : Get Field Declaring Class */ + jvmtiError (JNICALL *GetFieldDeclaringClass) (jvmtiEnv* env, + jclass klass, + jfieldID field, + jclass* declaring_class_ptr); + + /* 62 : Get Field Modifiers */ + jvmtiError (JNICALL *GetFieldModifiers) (jvmtiEnv* env, + jclass klass, + jfieldID field, + jint* modifiers_ptr); + + /* 63 : Is Field Synthetic */ + jvmtiError (JNICALL *IsFieldSynthetic) (jvmtiEnv* env, + jclass klass, + jfieldID field, + jboolean* is_synthetic_ptr); + + /* 64 : Get Method Name (and Signature) */ + jvmtiError (JNICALL *GetMethodName) (jvmtiEnv* env, + jmethodID method, + char** name_ptr, + char** signature_ptr, + char** generic_ptr); + + /* 65 : Get Method Declaring Class */ + jvmtiError (JNICALL *GetMethodDeclaringClass) (jvmtiEnv* env, + jmethodID method, + jclass* declaring_class_ptr); + + /* 66 : Get Method Modifiers */ + jvmtiError (JNICALL *GetMethodModifiers) (jvmtiEnv* env, + jmethodID method, + jint* modifiers_ptr); + + /* 67 : RESERVED */ + void *reserved67; + + /* 68 : Get Max Locals */ + jvmtiError (JNICALL *GetMaxLocals) (jvmtiEnv* env, + jmethodID method, + jint* max_ptr); + + /* 69 : Get Arguments Size */ + jvmtiError (JNICALL *GetArgumentsSize) (jvmtiEnv* env, + jmethodID method, + jint* size_ptr); + + /* 70 : Get Line Number Table */ + jvmtiError (JNICALL *GetLineNumberTable) (jvmtiEnv* env, + jmethodID method, + jint* entry_count_ptr, + jvmtiLineNumberEntry** table_ptr); + + /* 71 : Get Method Location */ + jvmtiError (JNICALL *GetMethodLocation) (jvmtiEnv* env, + jmethodID method, + jlocation* start_location_ptr, + jlocation* end_location_ptr); + + /* 72 : Get Local Variable Table */ + jvmtiError (JNICALL *GetLocalVariableTable) (jvmtiEnv* env, + jmethodID method, + jint* entry_count_ptr, + jvmtiLocalVariableEntry** table_ptr); + + /* 73 : Set Native Method Prefix */ + jvmtiError (JNICALL *SetNativeMethodPrefix) (jvmtiEnv* env, + const char* prefix); + + /* 74 : Set Native Method Prefixes */ + jvmtiError (JNICALL *SetNativeMethodPrefixes) (jvmtiEnv* env, + jint prefix_count, + char** prefixes); + + /* 75 : Get Bytecodes */ + jvmtiError (JNICALL *GetBytecodes) (jvmtiEnv* env, + jmethodID method, + jint* bytecode_count_ptr, + unsigned char** bytecodes_ptr); + + /* 76 : Is Method Native */ + jvmtiError (JNICALL *IsMethodNative) (jvmtiEnv* env, + jmethodID method, + jboolean* is_native_ptr); + + /* 77 : Is Method Synthetic */ + jvmtiError (JNICALL *IsMethodSynthetic) (jvmtiEnv* env, + jmethodID method, + jboolean* is_synthetic_ptr); + + /* 78 : Get Loaded Classes */ + jvmtiError (JNICALL *GetLoadedClasses) (jvmtiEnv* env, + jint* class_count_ptr, + jclass** classes_ptr); + + /* 79 : Get Classloader Classes */ + jvmtiError (JNICALL *GetClassLoaderClasses) (jvmtiEnv* env, + jobject initiating_loader, + jint* class_count_ptr, + jclass** classes_ptr); + + /* 80 : Pop Frame */ + jvmtiError (JNICALL *PopFrame) (jvmtiEnv* env, + jthread thread); + + /* 81 : Force Early Return - Object */ + jvmtiError (JNICALL *ForceEarlyReturnObject) (jvmtiEnv* env, + jthread thread, + jobject value); + + /* 82 : Force Early Return - Int */ + jvmtiError (JNICALL *ForceEarlyReturnInt) (jvmtiEnv* env, + jthread thread, + jint value); + + /* 83 : Force Early Return - Long */ + jvmtiError (JNICALL *ForceEarlyReturnLong) (jvmtiEnv* env, + jthread thread, + jlong value); + + /* 84 : Force Early Return - Float */ + jvmtiError (JNICALL *ForceEarlyReturnFloat) (jvmtiEnv* env, + jthread thread, + jfloat value); + + /* 85 : Force Early Return - Double */ + jvmtiError (JNICALL *ForceEarlyReturnDouble) (jvmtiEnv* env, + jthread thread, + jdouble value); + + /* 86 : Force Early Return - Void */ + jvmtiError (JNICALL *ForceEarlyReturnVoid) (jvmtiEnv* env, + jthread thread); + + /* 87 : Redefine Classes */ + jvmtiError (JNICALL *RedefineClasses) (jvmtiEnv* env, + jint class_count, + const jvmtiClassDefinition* class_definitions); + + /* 88 : Get Version Number */ + jvmtiError (JNICALL *GetVersionNumber) (jvmtiEnv* env, + jint* version_ptr); + + /* 89 : Get Capabilities */ + jvmtiError (JNICALL *GetCapabilities) (jvmtiEnv* env, + jvmtiCapabilities* capabilities_ptr); + + /* 90 : Get Source Debug Extension */ + jvmtiError (JNICALL *GetSourceDebugExtension) (jvmtiEnv* env, + jclass klass, + char** source_debug_extension_ptr); + + /* 91 : Is Method Obsolete */ + jvmtiError (JNICALL *IsMethodObsolete) (jvmtiEnv* env, + jmethodID method, + jboolean* is_obsolete_ptr); + + /* 92 : Suspend Thread List */ + jvmtiError (JNICALL *SuspendThreadList) (jvmtiEnv* env, + jint request_count, + const jthread* request_list, + jvmtiError* results); + + /* 93 : Resume Thread List */ + jvmtiError (JNICALL *ResumeThreadList) (jvmtiEnv* env, + jint request_count, + const jthread* request_list, + jvmtiError* results); + + /* 94 : RESERVED */ + void *reserved94; + + /* 95 : RESERVED */ + void *reserved95; + + /* 96 : RESERVED */ + void *reserved96; + + /* 97 : RESERVED */ + void *reserved97; + + /* 98 : RESERVED */ + void *reserved98; + + /* 99 : RESERVED */ + void *reserved99; + + /* 100 : Get All Stack Traces */ + jvmtiError (JNICALL *GetAllStackTraces) (jvmtiEnv* env, + jint max_frame_count, + jvmtiStackInfo** stack_info_ptr, + jint* thread_count_ptr); + + /* 101 : Get Thread List Stack Traces */ + jvmtiError (JNICALL *GetThreadListStackTraces) (jvmtiEnv* env, + jint thread_count, + const jthread* thread_list, + jint max_frame_count, + jvmtiStackInfo** stack_info_ptr); + + /* 102 : Get Thread Local Storage */ + jvmtiError (JNICALL *GetThreadLocalStorage) (jvmtiEnv* env, + jthread thread, + void** data_ptr); + + /* 103 : Set Thread Local Storage */ + jvmtiError (JNICALL *SetThreadLocalStorage) (jvmtiEnv* env, + jthread thread, + const void* data); + + /* 104 : Get Stack Trace */ + jvmtiError (JNICALL *GetStackTrace) (jvmtiEnv* env, + jthread thread, + jint start_depth, + jint max_frame_count, + jvmtiFrameInfo* frame_buffer, + jint* count_ptr); + + /* 105 : RESERVED */ + void *reserved105; + + /* 106 : Get Tag */ + jvmtiError (JNICALL *GetTag) (jvmtiEnv* env, + jobject object, + jlong* tag_ptr); + + /* 107 : Set Tag */ + jvmtiError (JNICALL *SetTag) (jvmtiEnv* env, + jobject object, + jlong tag); + + /* 108 : Force Garbage Collection */ + jvmtiError (JNICALL *ForceGarbageCollection) (jvmtiEnv* env); + + /* 109 : Iterate Over Objects Reachable From Object */ + jvmtiError (JNICALL *IterateOverObjectsReachableFromObject) (jvmtiEnv* env, + jobject object, + jvmtiObjectReferenceCallback object_reference_callback, + const void* user_data); + + /* 110 : Iterate Over Reachable Objects */ + jvmtiError (JNICALL *IterateOverReachableObjects) (jvmtiEnv* env, + jvmtiHeapRootCallback heap_root_callback, + jvmtiStackReferenceCallback stack_ref_callback, + jvmtiObjectReferenceCallback object_ref_callback, + const void* user_data); + + /* 111 : Iterate Over Heap */ + jvmtiError (JNICALL *IterateOverHeap) (jvmtiEnv* env, + jvmtiHeapObjectFilter object_filter, + jvmtiHeapObjectCallback heap_object_callback, + const void* user_data); + + /* 112 : Iterate Over Instances Of Class */ + jvmtiError (JNICALL *IterateOverInstancesOfClass) (jvmtiEnv* env, + jclass klass, + jvmtiHeapObjectFilter object_filter, + jvmtiHeapObjectCallback heap_object_callback, + const void* user_data); + + /* 113 : RESERVED */ + void *reserved113; + + /* 114 : Get Objects With Tags */ + jvmtiError (JNICALL *GetObjectsWithTags) (jvmtiEnv* env, + jint tag_count, + const jlong* tags, + jint* count_ptr, + jobject** object_result_ptr, + jlong** tag_result_ptr); + + /* 115 : Follow References */ + jvmtiError (JNICALL *FollowReferences) (jvmtiEnv* env, + jint heap_filter, + jclass klass, + jobject initial_object, + const jvmtiHeapCallbacks* callbacks, + const void* user_data); + + /* 116 : Iterate Through Heap */ + jvmtiError (JNICALL *IterateThroughHeap) (jvmtiEnv* env, + jint heap_filter, + jclass klass, + const jvmtiHeapCallbacks* callbacks, + const void* user_data); + + /* 117 : RESERVED */ + void *reserved117; + + /* 118 : RESERVED */ + void *reserved118; + + /* 119 : RESERVED */ + void *reserved119; + + /* 120 : Set JNI Function Table */ + jvmtiError (JNICALL *SetJNIFunctionTable) (jvmtiEnv* env, + const jniNativeInterface* function_table); + + /* 121 : Get JNI Function Table */ + jvmtiError (JNICALL *GetJNIFunctionTable) (jvmtiEnv* env, + jniNativeInterface** function_table); + + /* 122 : Set Event Callbacks */ + jvmtiError (JNICALL *SetEventCallbacks) (jvmtiEnv* env, + const jvmtiEventCallbacks* callbacks, + jint size_of_callbacks); + + /* 123 : Generate Events */ + jvmtiError (JNICALL *GenerateEvents) (jvmtiEnv* env, + jvmtiEvent event_type); + + /* 124 : Get Extension Functions */ + jvmtiError (JNICALL *GetExtensionFunctions) (jvmtiEnv* env, + jint* extension_count_ptr, + jvmtiExtensionFunctionInfo** extensions); + + /* 125 : Get Extension Events */ + jvmtiError (JNICALL *GetExtensionEvents) (jvmtiEnv* env, + jint* extension_count_ptr, + jvmtiExtensionEventInfo** extensions); + + /* 126 : Set Extension Event Callback */ + jvmtiError (JNICALL *SetExtensionEventCallback) (jvmtiEnv* env, + jint extension_event_index, + jvmtiExtensionEvent callback); + + /* 127 : Dispose Environment */ + jvmtiError (JNICALL *DisposeEnvironment) (jvmtiEnv* env); + + /* 128 : Get Error Name */ + jvmtiError (JNICALL *GetErrorName) (jvmtiEnv* env, + jvmtiError error, + char** name_ptr); + + /* 129 : Get JLocation Format */ + jvmtiError (JNICALL *GetJLocationFormat) (jvmtiEnv* env, + jvmtiJlocationFormat* format_ptr); + + /* 130 : Get System Properties */ + jvmtiError (JNICALL *GetSystemProperties) (jvmtiEnv* env, + jint* count_ptr, + char*** property_ptr); + + /* 131 : Get System Property */ + jvmtiError (JNICALL *GetSystemProperty) (jvmtiEnv* env, + const char* property, + char** value_ptr); + + /* 132 : Set System Property */ + jvmtiError (JNICALL *SetSystemProperty) (jvmtiEnv* env, + const char* property, + const char* value); + + /* 133 : Get Phase */ + jvmtiError (JNICALL *GetPhase) (jvmtiEnv* env, + jvmtiPhase* phase_ptr); + + /* 134 : Get Current Thread CPU Timer Information */ + jvmtiError (JNICALL *GetCurrentThreadCpuTimerInfo) (jvmtiEnv* env, + jvmtiTimerInfo* info_ptr); + + /* 135 : Get Current Thread CPU Time */ + jvmtiError (JNICALL *GetCurrentThreadCpuTime) (jvmtiEnv* env, + jlong* nanos_ptr); + + /* 136 : Get Thread CPU Timer Information */ + jvmtiError (JNICALL *GetThreadCpuTimerInfo) (jvmtiEnv* env, + jvmtiTimerInfo* info_ptr); + + /* 137 : Get Thread CPU Time */ + jvmtiError (JNICALL *GetThreadCpuTime) (jvmtiEnv* env, + jthread thread, + jlong* nanos_ptr); + + /* 138 : Get Timer Information */ + jvmtiError (JNICALL *GetTimerInfo) (jvmtiEnv* env, + jvmtiTimerInfo* info_ptr); + + /* 139 : Get Time */ + jvmtiError (JNICALL *GetTime) (jvmtiEnv* env, + jlong* nanos_ptr); + + /* 140 : Get Potential Capabilities */ + jvmtiError (JNICALL *GetPotentialCapabilities) (jvmtiEnv* env, + jvmtiCapabilities* capabilities_ptr); + + /* 141 : RESERVED */ + void *reserved141; + + /* 142 : Add Capabilities */ + jvmtiError (JNICALL *AddCapabilities) (jvmtiEnv* env, + const jvmtiCapabilities* capabilities_ptr); + + /* 143 : Relinquish Capabilities */ + jvmtiError (JNICALL *RelinquishCapabilities) (jvmtiEnv* env, + const jvmtiCapabilities* capabilities_ptr); + + /* 144 : Get Available Processors */ + jvmtiError (JNICALL *GetAvailableProcessors) (jvmtiEnv* env, + jint* processor_count_ptr); + + /* 145 : Get Class Version Numbers */ + jvmtiError (JNICALL *GetClassVersionNumbers) (jvmtiEnv* env, + jclass klass, + jint* minor_version_ptr, + jint* major_version_ptr); + + /* 146 : Get Constant Pool */ + jvmtiError (JNICALL *GetConstantPool) (jvmtiEnv* env, + jclass klass, + jint* constant_pool_count_ptr, + jint* constant_pool_byte_count_ptr, + unsigned char** constant_pool_bytes_ptr); + + /* 147 : Get Environment Local Storage */ + jvmtiError (JNICALL *GetEnvironmentLocalStorage) (jvmtiEnv* env, + void** data_ptr); + + /* 148 : Set Environment Local Storage */ + jvmtiError (JNICALL *SetEnvironmentLocalStorage) (jvmtiEnv* env, + const void* data); + + /* 149 : Add To Bootstrap Class Loader Search */ + jvmtiError (JNICALL *AddToBootstrapClassLoaderSearch) (jvmtiEnv* env, + const char* segment); + + /* 150 : Set Verbose Flag */ + jvmtiError (JNICALL *SetVerboseFlag) (jvmtiEnv* env, + jvmtiVerboseFlag flag, + jboolean value); + + /* 151 : Add To System Class Loader Search */ + jvmtiError (JNICALL *AddToSystemClassLoaderSearch) (jvmtiEnv* env, + const char* segment); + + /* 152 : Retransform Classes */ + jvmtiError (JNICALL *RetransformClasses) (jvmtiEnv* env, + jint class_count, + const jclass* classes); + + /* 153 : Get Owned Monitor Stack Depth Info */ + jvmtiError (JNICALL *GetOwnedMonitorStackDepthInfo) (jvmtiEnv* env, + jthread thread, + jint* monitor_info_count_ptr, + jvmtiMonitorStackDepthInfo** monitor_info_ptr); + + /* 154 : Get Object Size */ + jvmtiError (JNICALL *GetObjectSize) (jvmtiEnv* env, + jobject object, + jlong* size_ptr); + + /* 155 : Get Local Instance */ + jvmtiError (JNICALL *GetLocalInstance) (jvmtiEnv* env, + jthread thread, + jint depth, + jobject* value_ptr); + +} jvmtiInterface_1; + +struct _jvmtiEnv { + const struct jvmtiInterface_1_ *functions; +#ifdef __cplusplus + + + jvmtiError Allocate(jlong size, + unsigned char** mem_ptr) { + return functions->Allocate(this, size, mem_ptr); + } + + jvmtiError Deallocate(unsigned char* mem) { + return functions->Deallocate(this, mem); + } + + jvmtiError GetThreadState(jthread thread, + jint* thread_state_ptr) { + return functions->GetThreadState(this, thread, thread_state_ptr); + } + + jvmtiError GetCurrentThread(jthread* thread_ptr) { + return functions->GetCurrentThread(this, thread_ptr); + } + + jvmtiError GetAllThreads(jint* threads_count_ptr, + jthread** threads_ptr) { + return functions->GetAllThreads(this, threads_count_ptr, threads_ptr); + } + + jvmtiError SuspendThread(jthread thread) { + return functions->SuspendThread(this, thread); + } + + jvmtiError SuspendThreadList(jint request_count, + const jthread* request_list, + jvmtiError* results) { + return functions->SuspendThreadList(this, request_count, request_list, results); + } + + jvmtiError ResumeThread(jthread thread) { + return functions->ResumeThread(this, thread); + } + + jvmtiError ResumeThreadList(jint request_count, + const jthread* request_list, + jvmtiError* results) { + return functions->ResumeThreadList(this, request_count, request_list, results); + } + + jvmtiError StopThread(jthread thread, + jobject exception) { + return functions->StopThread(this, thread, exception); + } + + jvmtiError InterruptThread(jthread thread) { + return functions->InterruptThread(this, thread); + } + + jvmtiError GetThreadInfo(jthread thread, + jvmtiThreadInfo* info_ptr) { + return functions->GetThreadInfo(this, thread, info_ptr); + } + + jvmtiError GetOwnedMonitorInfo(jthread thread, + jint* owned_monitor_count_ptr, + jobject** owned_monitors_ptr) { + return functions->GetOwnedMonitorInfo(this, thread, owned_monitor_count_ptr, owned_monitors_ptr); + } + + jvmtiError GetOwnedMonitorStackDepthInfo(jthread thread, + jint* monitor_info_count_ptr, + jvmtiMonitorStackDepthInfo** monitor_info_ptr) { + return functions->GetOwnedMonitorStackDepthInfo(this, thread, monitor_info_count_ptr, monitor_info_ptr); + } + + jvmtiError GetCurrentContendedMonitor(jthread thread, + jobject* monitor_ptr) { + return functions->GetCurrentContendedMonitor(this, thread, monitor_ptr); + } + + jvmtiError RunAgentThread(jthread thread, + jvmtiStartFunction proc, + const void* arg, + jint priority) { + return functions->RunAgentThread(this, thread, proc, arg, priority); + } + + jvmtiError SetThreadLocalStorage(jthread thread, + const void* data) { + return functions->SetThreadLocalStorage(this, thread, data); + } + + jvmtiError GetThreadLocalStorage(jthread thread, + void** data_ptr) { + return functions->GetThreadLocalStorage(this, thread, data_ptr); + } + + jvmtiError GetTopThreadGroups(jint* group_count_ptr, + jthreadGroup** groups_ptr) { + return functions->GetTopThreadGroups(this, group_count_ptr, groups_ptr); + } + + jvmtiError GetThreadGroupInfo(jthreadGroup group, + jvmtiThreadGroupInfo* info_ptr) { + return functions->GetThreadGroupInfo(this, group, info_ptr); + } + + jvmtiError GetThreadGroupChildren(jthreadGroup group, + jint* thread_count_ptr, + jthread** threads_ptr, + jint* group_count_ptr, + jthreadGroup** groups_ptr) { + return functions->GetThreadGroupChildren(this, group, thread_count_ptr, threads_ptr, group_count_ptr, groups_ptr); + } + + jvmtiError GetStackTrace(jthread thread, + jint start_depth, + jint max_frame_count, + jvmtiFrameInfo* frame_buffer, + jint* count_ptr) { + return functions->GetStackTrace(this, thread, start_depth, max_frame_count, frame_buffer, count_ptr); + } + + jvmtiError GetAllStackTraces(jint max_frame_count, + jvmtiStackInfo** stack_info_ptr, + jint* thread_count_ptr) { + return functions->GetAllStackTraces(this, max_frame_count, stack_info_ptr, thread_count_ptr); + } + + jvmtiError GetThreadListStackTraces(jint thread_count, + const jthread* thread_list, + jint max_frame_count, + jvmtiStackInfo** stack_info_ptr) { + return functions->GetThreadListStackTraces(this, thread_count, thread_list, max_frame_count, stack_info_ptr); + } + + jvmtiError GetFrameCount(jthread thread, + jint* count_ptr) { + return functions->GetFrameCount(this, thread, count_ptr); + } + + jvmtiError PopFrame(jthread thread) { + return functions->PopFrame(this, thread); + } + + jvmtiError GetFrameLocation(jthread thread, + jint depth, + jmethodID* method_ptr, + jlocation* location_ptr) { + return functions->GetFrameLocation(this, thread, depth, method_ptr, location_ptr); + } + + jvmtiError NotifyFramePop(jthread thread, + jint depth) { + return functions->NotifyFramePop(this, thread, depth); + } + + jvmtiError ForceEarlyReturnObject(jthread thread, + jobject value) { + return functions->ForceEarlyReturnObject(this, thread, value); + } + + jvmtiError ForceEarlyReturnInt(jthread thread, + jint value) { + return functions->ForceEarlyReturnInt(this, thread, value); + } + + jvmtiError ForceEarlyReturnLong(jthread thread, + jlong value) { + return functions->ForceEarlyReturnLong(this, thread, value); + } + + jvmtiError ForceEarlyReturnFloat(jthread thread, + jfloat value) { + return functions->ForceEarlyReturnFloat(this, thread, value); + } + + jvmtiError ForceEarlyReturnDouble(jthread thread, + jdouble value) { + return functions->ForceEarlyReturnDouble(this, thread, value); + } + + jvmtiError ForceEarlyReturnVoid(jthread thread) { + return functions->ForceEarlyReturnVoid(this, thread); + } + + jvmtiError FollowReferences(jint heap_filter, + jclass klass, + jobject initial_object, + const jvmtiHeapCallbacks* callbacks, + const void* user_data) { + return functions->FollowReferences(this, heap_filter, klass, initial_object, callbacks, user_data); + } + + jvmtiError IterateThroughHeap(jint heap_filter, + jclass klass, + const jvmtiHeapCallbacks* callbacks, + const void* user_data) { + return functions->IterateThroughHeap(this, heap_filter, klass, callbacks, user_data); + } + + jvmtiError GetTag(jobject object, + jlong* tag_ptr) { + return functions->GetTag(this, object, tag_ptr); + } + + jvmtiError SetTag(jobject object, + jlong tag) { + return functions->SetTag(this, object, tag); + } + + jvmtiError GetObjectsWithTags(jint tag_count, + const jlong* tags, + jint* count_ptr, + jobject** object_result_ptr, + jlong** tag_result_ptr) { + return functions->GetObjectsWithTags(this, tag_count, tags, count_ptr, object_result_ptr, tag_result_ptr); + } + + jvmtiError ForceGarbageCollection() { + return functions->ForceGarbageCollection(this); + } + + jvmtiError IterateOverObjectsReachableFromObject(jobject object, + jvmtiObjectReferenceCallback object_reference_callback, + const void* user_data) { + return functions->IterateOverObjectsReachableFromObject(this, object, object_reference_callback, user_data); + } + + jvmtiError IterateOverReachableObjects(jvmtiHeapRootCallback heap_root_callback, + jvmtiStackReferenceCallback stack_ref_callback, + jvmtiObjectReferenceCallback object_ref_callback, + const void* user_data) { + return functions->IterateOverReachableObjects(this, heap_root_callback, stack_ref_callback, object_ref_callback, user_data); + } + + jvmtiError IterateOverHeap(jvmtiHeapObjectFilter object_filter, + jvmtiHeapObjectCallback heap_object_callback, + const void* user_data) { + return functions->IterateOverHeap(this, object_filter, heap_object_callback, user_data); + } + + jvmtiError IterateOverInstancesOfClass(jclass klass, + jvmtiHeapObjectFilter object_filter, + jvmtiHeapObjectCallback heap_object_callback, + const void* user_data) { + return functions->IterateOverInstancesOfClass(this, klass, object_filter, heap_object_callback, user_data); + } + + jvmtiError GetLocalObject(jthread thread, + jint depth, + jint slot, + jobject* value_ptr) { + return functions->GetLocalObject(this, thread, depth, slot, value_ptr); + } + + jvmtiError GetLocalInstance(jthread thread, + jint depth, + jobject* value_ptr) { + return functions->GetLocalInstance(this, thread, depth, value_ptr); + } + + jvmtiError GetLocalInt(jthread thread, + jint depth, + jint slot, + jint* value_ptr) { + return functions->GetLocalInt(this, thread, depth, slot, value_ptr); + } + + jvmtiError GetLocalLong(jthread thread, + jint depth, + jint slot, + jlong* value_ptr) { + return functions->GetLocalLong(this, thread, depth, slot, value_ptr); + } + + jvmtiError GetLocalFloat(jthread thread, + jint depth, + jint slot, + jfloat* value_ptr) { + return functions->GetLocalFloat(this, thread, depth, slot, value_ptr); + } + + jvmtiError GetLocalDouble(jthread thread, + jint depth, + jint slot, + jdouble* value_ptr) { + return functions->GetLocalDouble(this, thread, depth, slot, value_ptr); + } + + jvmtiError SetLocalObject(jthread thread, + jint depth, + jint slot, + jobject value) { + return functions->SetLocalObject(this, thread, depth, slot, value); + } + + jvmtiError SetLocalInt(jthread thread, + jint depth, + jint slot, + jint value) { + return functions->SetLocalInt(this, thread, depth, slot, value); + } + + jvmtiError SetLocalLong(jthread thread, + jint depth, + jint slot, + jlong value) { + return functions->SetLocalLong(this, thread, depth, slot, value); + } + + jvmtiError SetLocalFloat(jthread thread, + jint depth, + jint slot, + jfloat value) { + return functions->SetLocalFloat(this, thread, depth, slot, value); + } + + jvmtiError SetLocalDouble(jthread thread, + jint depth, + jint slot, + jdouble value) { + return functions->SetLocalDouble(this, thread, depth, slot, value); + } + + jvmtiError SetBreakpoint(jmethodID method, + jlocation location) { + return functions->SetBreakpoint(this, method, location); + } + + jvmtiError ClearBreakpoint(jmethodID method, + jlocation location) { + return functions->ClearBreakpoint(this, method, location); + } + + jvmtiError SetFieldAccessWatch(jclass klass, + jfieldID field) { + return functions->SetFieldAccessWatch(this, klass, field); + } + + jvmtiError ClearFieldAccessWatch(jclass klass, + jfieldID field) { + return functions->ClearFieldAccessWatch(this, klass, field); + } + + jvmtiError SetFieldModificationWatch(jclass klass, + jfieldID field) { + return functions->SetFieldModificationWatch(this, klass, field); + } + + jvmtiError ClearFieldModificationWatch(jclass klass, + jfieldID field) { + return functions->ClearFieldModificationWatch(this, klass, field); + } + + jvmtiError GetLoadedClasses(jint* class_count_ptr, + jclass** classes_ptr) { + return functions->GetLoadedClasses(this, class_count_ptr, classes_ptr); + } + + jvmtiError GetClassLoaderClasses(jobject initiating_loader, + jint* class_count_ptr, + jclass** classes_ptr) { + return functions->GetClassLoaderClasses(this, initiating_loader, class_count_ptr, classes_ptr); + } + + jvmtiError GetClassSignature(jclass klass, + char** signature_ptr, + char** generic_ptr) { + return functions->GetClassSignature(this, klass, signature_ptr, generic_ptr); + } + + jvmtiError GetClassStatus(jclass klass, + jint* status_ptr) { + return functions->GetClassStatus(this, klass, status_ptr); + } + + jvmtiError GetSourceFileName(jclass klass, + char** source_name_ptr) { + return functions->GetSourceFileName(this, klass, source_name_ptr); + } + + jvmtiError GetClassModifiers(jclass klass, + jint* modifiers_ptr) { + return functions->GetClassModifiers(this, klass, modifiers_ptr); + } + + jvmtiError GetClassMethods(jclass klass, + jint* method_count_ptr, + jmethodID** methods_ptr) { + return functions->GetClassMethods(this, klass, method_count_ptr, methods_ptr); + } + + jvmtiError GetClassFields(jclass klass, + jint* field_count_ptr, + jfieldID** fields_ptr) { + return functions->GetClassFields(this, klass, field_count_ptr, fields_ptr); + } + + jvmtiError GetImplementedInterfaces(jclass klass, + jint* interface_count_ptr, + jclass** interfaces_ptr) { + return functions->GetImplementedInterfaces(this, klass, interface_count_ptr, interfaces_ptr); + } + + jvmtiError GetClassVersionNumbers(jclass klass, + jint* minor_version_ptr, + jint* major_version_ptr) { + return functions->GetClassVersionNumbers(this, klass, minor_version_ptr, major_version_ptr); + } + + jvmtiError GetConstantPool(jclass klass, + jint* constant_pool_count_ptr, + jint* constant_pool_byte_count_ptr, + unsigned char** constant_pool_bytes_ptr) { + return functions->GetConstantPool(this, klass, constant_pool_count_ptr, constant_pool_byte_count_ptr, constant_pool_bytes_ptr); + } + + jvmtiError IsInterface(jclass klass, + jboolean* is_interface_ptr) { + return functions->IsInterface(this, klass, is_interface_ptr); + } + + jvmtiError IsArrayClass(jclass klass, + jboolean* is_array_class_ptr) { + return functions->IsArrayClass(this, klass, is_array_class_ptr); + } + + jvmtiError IsModifiableClass(jclass klass, + jboolean* is_modifiable_class_ptr) { + return functions->IsModifiableClass(this, klass, is_modifiable_class_ptr); + } + + jvmtiError GetClassLoader(jclass klass, + jobject* classloader_ptr) { + return functions->GetClassLoader(this, klass, classloader_ptr); + } + + jvmtiError GetSourceDebugExtension(jclass klass, + char** source_debug_extension_ptr) { + return functions->GetSourceDebugExtension(this, klass, source_debug_extension_ptr); + } + + jvmtiError RetransformClasses(jint class_count, + const jclass* classes) { + return functions->RetransformClasses(this, class_count, classes); + } + + jvmtiError RedefineClasses(jint class_count, + const jvmtiClassDefinition* class_definitions) { + return functions->RedefineClasses(this, class_count, class_definitions); + } + + jvmtiError GetObjectSize(jobject object, + jlong* size_ptr) { + return functions->GetObjectSize(this, object, size_ptr); + } + + jvmtiError GetObjectHashCode(jobject object, + jint* hash_code_ptr) { + return functions->GetObjectHashCode(this, object, hash_code_ptr); + } + + jvmtiError GetObjectMonitorUsage(jobject object, + jvmtiMonitorUsage* info_ptr) { + return functions->GetObjectMonitorUsage(this, object, info_ptr); + } + + jvmtiError GetFieldName(jclass klass, + jfieldID field, + char** name_ptr, + char** signature_ptr, + char** generic_ptr) { + return functions->GetFieldName(this, klass, field, name_ptr, signature_ptr, generic_ptr); + } + + jvmtiError GetFieldDeclaringClass(jclass klass, + jfieldID field, + jclass* declaring_class_ptr) { + return functions->GetFieldDeclaringClass(this, klass, field, declaring_class_ptr); + } + + jvmtiError GetFieldModifiers(jclass klass, + jfieldID field, + jint* modifiers_ptr) { + return functions->GetFieldModifiers(this, klass, field, modifiers_ptr); + } + + jvmtiError IsFieldSynthetic(jclass klass, + jfieldID field, + jboolean* is_synthetic_ptr) { + return functions->IsFieldSynthetic(this, klass, field, is_synthetic_ptr); + } + + jvmtiError GetMethodName(jmethodID method, + char** name_ptr, + char** signature_ptr, + char** generic_ptr) { + return functions->GetMethodName(this, method, name_ptr, signature_ptr, generic_ptr); + } + + jvmtiError GetMethodDeclaringClass(jmethodID method, + jclass* declaring_class_ptr) { + return functions->GetMethodDeclaringClass(this, method, declaring_class_ptr); + } + + jvmtiError GetMethodModifiers(jmethodID method, + jint* modifiers_ptr) { + return functions->GetMethodModifiers(this, method, modifiers_ptr); + } + + jvmtiError GetMaxLocals(jmethodID method, + jint* max_ptr) { + return functions->GetMaxLocals(this, method, max_ptr); + } + + jvmtiError GetArgumentsSize(jmethodID method, + jint* size_ptr) { + return functions->GetArgumentsSize(this, method, size_ptr); + } + + jvmtiError GetLineNumberTable(jmethodID method, + jint* entry_count_ptr, + jvmtiLineNumberEntry** table_ptr) { + return functions->GetLineNumberTable(this, method, entry_count_ptr, table_ptr); + } + + jvmtiError GetMethodLocation(jmethodID method, + jlocation* start_location_ptr, + jlocation* end_location_ptr) { + return functions->GetMethodLocation(this, method, start_location_ptr, end_location_ptr); + } + + jvmtiError GetLocalVariableTable(jmethodID method, + jint* entry_count_ptr, + jvmtiLocalVariableEntry** table_ptr) { + return functions->GetLocalVariableTable(this, method, entry_count_ptr, table_ptr); + } + + jvmtiError GetBytecodes(jmethodID method, + jint* bytecode_count_ptr, + unsigned char** bytecodes_ptr) { + return functions->GetBytecodes(this, method, bytecode_count_ptr, bytecodes_ptr); + } + + jvmtiError IsMethodNative(jmethodID method, + jboolean* is_native_ptr) { + return functions->IsMethodNative(this, method, is_native_ptr); + } + + jvmtiError IsMethodSynthetic(jmethodID method, + jboolean* is_synthetic_ptr) { + return functions->IsMethodSynthetic(this, method, is_synthetic_ptr); + } + + jvmtiError IsMethodObsolete(jmethodID method, + jboolean* is_obsolete_ptr) { + return functions->IsMethodObsolete(this, method, is_obsolete_ptr); + } + + jvmtiError SetNativeMethodPrefix(const char* prefix) { + return functions->SetNativeMethodPrefix(this, prefix); + } + + jvmtiError SetNativeMethodPrefixes(jint prefix_count, + char** prefixes) { + return functions->SetNativeMethodPrefixes(this, prefix_count, prefixes); + } + + jvmtiError CreateRawMonitor(const char* name, + jrawMonitorID* monitor_ptr) { + return functions->CreateRawMonitor(this, name, monitor_ptr); + } + + jvmtiError DestroyRawMonitor(jrawMonitorID monitor) { + return functions->DestroyRawMonitor(this, monitor); + } + + jvmtiError RawMonitorEnter(jrawMonitorID monitor) { + return functions->RawMonitorEnter(this, monitor); + } + + jvmtiError RawMonitorExit(jrawMonitorID monitor) { + return functions->RawMonitorExit(this, monitor); + } + + jvmtiError RawMonitorWait(jrawMonitorID monitor, + jlong millis) { + return functions->RawMonitorWait(this, monitor, millis); + } + + jvmtiError RawMonitorNotify(jrawMonitorID monitor) { + return functions->RawMonitorNotify(this, monitor); + } + + jvmtiError RawMonitorNotifyAll(jrawMonitorID monitor) { + return functions->RawMonitorNotifyAll(this, monitor); + } + + jvmtiError SetJNIFunctionTable(const jniNativeInterface* function_table) { + return functions->SetJNIFunctionTable(this, function_table); + } + + jvmtiError GetJNIFunctionTable(jniNativeInterface** function_table) { + return functions->GetJNIFunctionTable(this, function_table); + } + + jvmtiError SetEventCallbacks(const jvmtiEventCallbacks* callbacks, + jint size_of_callbacks) { + return functions->SetEventCallbacks(this, callbacks, size_of_callbacks); + } + + jvmtiError SetEventNotificationMode(jvmtiEventMode mode, + jvmtiEvent event_type, + jthread event_thread, + ...) { + return functions->SetEventNotificationMode(this, mode, event_type, event_thread); + } + + jvmtiError GenerateEvents(jvmtiEvent event_type) { + return functions->GenerateEvents(this, event_type); + } + + jvmtiError GetExtensionFunctions(jint* extension_count_ptr, + jvmtiExtensionFunctionInfo** extensions) { + return functions->GetExtensionFunctions(this, extension_count_ptr, extensions); + } + + jvmtiError GetExtensionEvents(jint* extension_count_ptr, + jvmtiExtensionEventInfo** extensions) { + return functions->GetExtensionEvents(this, extension_count_ptr, extensions); + } + + jvmtiError SetExtensionEventCallback(jint extension_event_index, + jvmtiExtensionEvent callback) { + return functions->SetExtensionEventCallback(this, extension_event_index, callback); + } + + jvmtiError GetPotentialCapabilities(jvmtiCapabilities* capabilities_ptr) { + return functions->GetPotentialCapabilities(this, capabilities_ptr); + } + + jvmtiError AddCapabilities(const jvmtiCapabilities* capabilities_ptr) { + return functions->AddCapabilities(this, capabilities_ptr); + } + + jvmtiError RelinquishCapabilities(const jvmtiCapabilities* capabilities_ptr) { + return functions->RelinquishCapabilities(this, capabilities_ptr); + } + + jvmtiError GetCapabilities(jvmtiCapabilities* capabilities_ptr) { + return functions->GetCapabilities(this, capabilities_ptr); + } + + jvmtiError GetCurrentThreadCpuTimerInfo(jvmtiTimerInfo* info_ptr) { + return functions->GetCurrentThreadCpuTimerInfo(this, info_ptr); + } + + jvmtiError GetCurrentThreadCpuTime(jlong* nanos_ptr) { + return functions->GetCurrentThreadCpuTime(this, nanos_ptr); + } + + jvmtiError GetThreadCpuTimerInfo(jvmtiTimerInfo* info_ptr) { + return functions->GetThreadCpuTimerInfo(this, info_ptr); + } + + jvmtiError GetThreadCpuTime(jthread thread, + jlong* nanos_ptr) { + return functions->GetThreadCpuTime(this, thread, nanos_ptr); + } + + jvmtiError GetTimerInfo(jvmtiTimerInfo* info_ptr) { + return functions->GetTimerInfo(this, info_ptr); + } + + jvmtiError GetTime(jlong* nanos_ptr) { + return functions->GetTime(this, nanos_ptr); + } + + jvmtiError GetAvailableProcessors(jint* processor_count_ptr) { + return functions->GetAvailableProcessors(this, processor_count_ptr); + } + + jvmtiError AddToBootstrapClassLoaderSearch(const char* segment) { + return functions->AddToBootstrapClassLoaderSearch(this, segment); + } + + jvmtiError AddToSystemClassLoaderSearch(const char* segment) { + return functions->AddToSystemClassLoaderSearch(this, segment); + } + + jvmtiError GetSystemProperties(jint* count_ptr, + char*** property_ptr) { + return functions->GetSystemProperties(this, count_ptr, property_ptr); + } + + jvmtiError GetSystemProperty(const char* property, + char** value_ptr) { + return functions->GetSystemProperty(this, property, value_ptr); + } + + jvmtiError SetSystemProperty(const char* property, + const char* value) { + return functions->SetSystemProperty(this, property, value); + } + + jvmtiError GetPhase(jvmtiPhase* phase_ptr) { + return functions->GetPhase(this, phase_ptr); + } + + jvmtiError DisposeEnvironment() { + return functions->DisposeEnvironment(this); + } + + jvmtiError SetEnvironmentLocalStorage(const void* data) { + return functions->SetEnvironmentLocalStorage(this, data); + } + + jvmtiError GetEnvironmentLocalStorage(void** data_ptr) { + return functions->GetEnvironmentLocalStorage(this, data_ptr); + } + + jvmtiError GetVersionNumber(jint* version_ptr) { + return functions->GetVersionNumber(this, version_ptr); + } + + jvmtiError GetErrorName(jvmtiError error, + char** name_ptr) { + return functions->GetErrorName(this, error, name_ptr); + } + + jvmtiError SetVerboseFlag(jvmtiVerboseFlag flag, + jboolean value) { + return functions->SetVerboseFlag(this, flag, value); + } + + jvmtiError GetJLocationFormat(jvmtiJlocationFormat* format_ptr) { + return functions->GetJLocationFormat(this, format_ptr); + } + +#endif /* __cplusplus */ +}; + + +#ifdef __cplusplus +} /* extern "C" */ +#endif /* __cplusplus */ + +#endif /* !_JAVA_JVMTI_H_ */ + diff --git a/jdk-1.8.0.281/include/jvmticmlr.h b/jdk-1.8.0.281/include/jvmticmlr.h new file mode 100755 index 0000000..a9c88f3 --- /dev/null +++ b/jdk-1.8.0.281/include/jvmticmlr.h @@ -0,0 +1,115 @@ +/* + * Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +/* + * This header file defines the data structures sent by the VM + * through the JVMTI CompiledMethodLoad callback function via the + * "void * compile_info" parameter. The memory pointed to by the + * compile_info parameter may not be referenced after returning from + * the CompiledMethodLoad callback. These are VM implementation + * specific data structures that may evolve in future releases. A + * JVMTI agent should interpret a non-NULL compile_info as a pointer + * to a region of memory containing a list of records. In a typical + * usage scenario, a JVMTI agent would cast each record to a + * jvmtiCompiledMethodLoadRecordHeader, a struct that represents + * arbitrary information. This struct contains a kind field to indicate + * the kind of information being passed, and a pointer to the next + * record. If the kind field indicates inlining information, then the + * agent would cast the record to a jvmtiCompiledMethodLoadInlineRecord. + * This record contains an array of PCStackInfo structs, which indicate + * for every pc address what are the methods on the invocation stack. + * The "methods" and "bcis" fields in each PCStackInfo struct specify a + * 1-1 mapping between these inlined methods and their bytecode indices. + * This can be used to derive the proper source lines of the inlined + * methods. + */ + +#ifndef _JVMTI_CMLR_H_ +#define _JVMTI_CMLR_H_ + +enum { + JVMTI_CMLR_MAJOR_VERSION_1 = 0x00000001, + JVMTI_CMLR_MINOR_VERSION_0 = 0x00000000, + + JVMTI_CMLR_MAJOR_VERSION = 0x00000001, + JVMTI_CMLR_MINOR_VERSION = 0x00000000 + + /* + * This comment is for the "JDK import from HotSpot" sanity check: + * version: 1.0.0 + */ +}; + +typedef enum { + JVMTI_CMLR_DUMMY = 1, + JVMTI_CMLR_INLINE_INFO = 2 +} jvmtiCMLRKind; + +/* + * Record that represents arbitrary information passed through JVMTI + * CompiledMethodLoadEvent void pointer. + */ +typedef struct _jvmtiCompiledMethodLoadRecordHeader { + jvmtiCMLRKind kind; /* id for the kind of info passed in the record */ + jint majorinfoversion; /* major and minor info version values. Init'ed */ + jint minorinfoversion; /* to current version value in jvmtiExport.cpp. */ + + struct _jvmtiCompiledMethodLoadRecordHeader* next; +} jvmtiCompiledMethodLoadRecordHeader; + +/* + * Record that gives information about the methods on the compile-time + * stack at a specific pc address of a compiled method. Each element in + * the methods array maps to same element in the bcis array. + */ +typedef struct _PCStackInfo { + void* pc; /* the pc address for this compiled method */ + jint numstackframes; /* number of methods on the stack */ + jmethodID* methods; /* array of numstackframes method ids */ + jint* bcis; /* array of numstackframes bytecode indices */ +} PCStackInfo; + +/* + * Record that contains inlining information for each pc address of + * an nmethod. + */ +typedef struct _jvmtiCompiledMethodLoadInlineRecord { + jvmtiCompiledMethodLoadRecordHeader header; /* common header for casting */ + jint numpcs; /* number of pc descriptors in this nmethod */ + PCStackInfo* pcinfo; /* array of numpcs pc descriptors */ +} jvmtiCompiledMethodLoadInlineRecord; + +/* + * Dummy record used to test that we can pass records with different + * information through the void pointer provided that they can be cast + * to a jvmtiCompiledMethodLoadRecordHeader. + */ + +typedef struct _jvmtiCompiledMethodLoadDummyRecord { + jvmtiCompiledMethodLoadRecordHeader header; /* common header for casting */ + char message[50]; +} jvmtiCompiledMethodLoadDummyRecord; + +#endif diff --git a/jdk-1.8.0.281/include/linux/jawt_md.h b/jdk-1.8.0.281/include/linux/jawt_md.h new file mode 100755 index 0000000..825142c --- /dev/null +++ b/jdk-1.8.0.281/include/linux/jawt_md.h @@ -0,0 +1,61 @@ +/* + * Copyright (c) 1999, 2001, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +#ifndef _JAVASOFT_JAWT_MD_H_ +#define _JAVASOFT_JAWT_MD_H_ + +#include +#include +#include +#include "jawt.h" + +#ifdef __cplusplus +extern "C" { +#endif + +/* + * X11-specific declarations for AWT native interface. + * See notes in jawt.h for an example of use. + */ +typedef struct jawt_X11DrawingSurfaceInfo { + Drawable drawable; + Display* display; + VisualID visualID; + Colormap colormapID; + int depth; + /* + * Since 1.4 + * Returns a pixel value from a set of RGB values. + * This is useful for paletted color (256 color) modes. + */ + int (JNICALL *GetAWTColor)(JAWT_DrawingSurface* ds, + int r, int g, int b); +} JAWT_X11DrawingSurfaceInfo; + +#ifdef __cplusplus +} +#endif + +#endif /* !_JAVASOFT_JAWT_MD_H_ */ diff --git a/jdk-1.8.0.281/include/linux/jni_md.h b/jdk-1.8.0.281/include/linux/jni_md.h new file mode 100755 index 0000000..ff30a32 --- /dev/null +++ b/jdk-1.8.0.281/include/linux/jni_md.h @@ -0,0 +1,51 @@ +/* + * Copyright (c) 1996, 2013, Oracle and/or its affiliates. All rights reserved. + * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + */ + +#ifndef _JAVASOFT_JNI_MD_H_ +#define _JAVASOFT_JNI_MD_H_ + +#ifndef __has_attribute + #define __has_attribute(x) 0 +#endif +#if (defined(__GNUC__) && ((__GNUC__ > 4) || (__GNUC__ == 4) && (__GNUC_MINOR__ > 2))) || __has_attribute(visibility) + #define JNIEXPORT __attribute__((visibility("default"))) + #define JNIIMPORT __attribute__((visibility("default"))) +#else + #define JNIEXPORT + #define JNIIMPORT +#endif + +#define JNICALL + +typedef int jint; +#ifdef _LP64 /* 64-bit Solaris */ +typedef long jlong; +#else +typedef long long jlong; +#endif + +typedef signed char jbyte; + +#endif /* !_JAVASOFT_JNI_MD_H_ */ diff --git a/jdk-1.8.0.281/jmc.txt b/jdk-1.8.0.281/jmc.txt new file mode 100755 index 0000000..e17e1f5 --- /dev/null +++ b/jdk-1.8.0.281/jmc.txt @@ -0,0 +1 @@ +This version of the JDK no longer includes a copy of Java Mission Control (JMC). JMC is now available as a separate download. Please visit https://www.oracle.com/javase/jmc for more information. diff --git a/jdk-1.8.0.281/jre/COPYRIGHT b/jdk-1.8.0.281/jre/COPYRIGHT new file mode 100755 index 0000000..15c35f6 --- /dev/null +++ b/jdk-1.8.0.281/jre/COPYRIGHT @@ -0,0 +1,69 @@ +Copyright © 1993, 2021, Oracle and/or its affiliates. +All rights reserved. + +This software and related documentation are provided under a +license agreement containing restrictions on use and +disclosure and are protected by intellectual property laws. +Except as expressly permitted in your license agreement or +allowed by law, you may not use, copy, reproduce, translate, +broadcast, modify, license, transmit, distribute, exhibit, +perform, publish, or display any part, in any form, or by +any means. Reverse engineering, disassembly, or +decompilation of this software, unless required by law for +interoperability, is prohibited. + +The information contained herein is subject to change +without notice and is not warranted to be error-free. If you +find any errors, please report them to us in writing. + +If this is software or related documentation that is +delivered to the U.S. Government or anyone licensing it on +behalf of the U.S. Government, the following notice is +applicable: + +U.S. GOVERNMENT END USERS: Oracle programs, including any +operating system, integrated software, any programs +installed on the hardware, and/or documentation, delivered +to U.S. Government end users are "commercial computer +software" pursuant to the applicable Federal Acquisition +Regulation and agency-specific supplemental regulations. As +such, use, duplication, disclosure, modification, and +adaptation of the programs, including any operating system, +integrated software, any programs installed on the hardware, +and/or documentation, shall be subject to license terms and +license restrictions applicable to the programs. No other +rights are granted to the U.S. Government. + +This software or hardware is developed for general use in a +variety of information management applications. It is not +developed or intended for use in any inherently dangerous +applications, including applications that may create a risk +of personal injury. If you use this software or hardware in +dangerous applications, then you shall be responsible to +take all appropriate fail-safe, backup, redundancy, and +other measures to ensure its safe use. Oracle Corporation +and its affiliates disclaim any liability for any damages +caused by use of this software or hardware in dangerous +applications. + +Oracle and Java are registered trademarks of Oracle and/or +its affiliates. Other names may be trademarks of their +respective owners. + +Intel and Intel Xeon are trademarks or registered trademarks +of Intel Corporation. All SPARC trademarks are used under +license and are trademarks or registered trademarks of SPARC +International, Inc. AMD, Opteron, the AMD logo, and the AMD +Opteron logo are trademarks or registered trademarks of +Advanced Micro Devices. UNIX is a registered trademark of +The Open Group. + +This software or hardware and documentation may provide +access to or information on content, products, and services +from third parties. Oracle Corporation and its affiliates +are not responsible for and expressly disclaim all +warranties of any kind with respect to third-party content, +products, and services. Oracle Corporation and its +affiliates will not be responsible for any loss, costs, or +damages incurred due to your access to or use of third-party +content, products, or services. diff --git a/jdk-1.8.0.281/jre/LICENSE b/jdk-1.8.0.281/jre/LICENSE new file mode 100755 index 0000000..6a33d4a --- /dev/null +++ b/jdk-1.8.0.281/jre/LICENSE @@ -0,0 +1 @@ +Please refer to https://java.com/otnlicense diff --git a/jdk-1.8.0.281/jre/README b/jdk-1.8.0.281/jre/README new file mode 100755 index 0000000..cdb30f2 --- /dev/null +++ b/jdk-1.8.0.281/jre/README @@ -0,0 +1 @@ +Please refer to http://java.com/licensereadme diff --git a/jdk-1.8.0.281/jre/THIRDPARTYLICENSEREADME-JAVAFX.txt b/jdk-1.8.0.281/jre/THIRDPARTYLICENSEREADME-JAVAFX.txt new file mode 100755 index 0000000..b1d2cf6 --- /dev/null +++ b/jdk-1.8.0.281/jre/THIRDPARTYLICENSEREADME-JAVAFX.txt @@ -0,0 +1,3 @@ +The licenses for Third Party components included with this product can +be found under the /legal/javafx subdirectory. Each component's license +is available as a separate markdown (.md) file diff --git a/jdk-1.8.0.281/jre/THIRDPARTYLICENSEREADME.txt b/jdk-1.8.0.281/jre/THIRDPARTYLICENSEREADME.txt new file mode 100755 index 0000000..ac4e1ff --- /dev/null +++ b/jdk-1.8.0.281/jre/THIRDPARTYLICENSEREADME.txt @@ -0,0 +1,3 @@ +The licenses for Third Party components included with this product can +be found under the /legal/jdk subdirectory. Each component's license is +available as a separate markdown (.md) file. diff --git a/jdk-1.8.0.281/jre/Welcome.html b/jdk-1.8.0.281/jre/Welcome.html new file mode 100755 index 0000000..0f39d9f --- /dev/null +++ b/jdk-1.8.0.281/jre/Welcome.html @@ -0,0 +1,28 @@ + + + +Welcome to the Java(TM) Platform + + + + +

Welcome to the JavaTM Platform

+

Welcome to the JavaTM Standard Edition Runtime + Environment. This provides complete runtime support for Java applications. +

The runtime environment includes the JavaTM + Plug-in product which supports the Java environment inside web browsers. +

References

+

+See the Java Plug-in product +documentation for more information on using the Java Plug-in product. +

See the Java Platform web site for + more information on the Java Platform. +

+ +Copyright (c) 2006, 2021, Oracle and/or its affiliates. All rights reserved. + +

+ + diff --git a/jdk-1.8.0.281/jre/bin/ControlPanel b/jdk-1.8.0.281/jre/bin/ControlPanel new file mode 100755 index 0000000..57f80a8 --- /dev/null +++ b/jdk-1.8.0.281/jre/bin/ControlPanel @@ -0,0 +1,245 @@ +#!/bin/bash +# +# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# Shell Script to run the Java Plug-in control panel. +# +# Parse the command-line options +# -r means make associate with the container (i.e browser) +# -u means remove the association with the container +# -c provides the location of the container install +# -j provides the location of the jre install +# if neither -r or -u are specified, run the ControlPanel UI + +USAGE='usage: ControlPanel [ (-u scheme | -r scheme) -c cpath -j jrepath ]' +JLERROR='ControlPanel: Error: Invalid JRE location: ' +CLERROR='ControlPanel: Error: Invalid container location: ' +IPERROR='ControlPanel: Error: Insufficient permission' +ISERROR='ControlPanel: Error: Invalid scheme: ' +XLERROR='ControlPanel: Error: Invalid link or copy: ' + +check_container_dir() { + + if [ ! -d ${1} ]; then + echo "${CLERROR}${2}" + exit 1 + fi + if [ ! -w ${1} ]; then + echo "${IPERROR}" + exit 1 + fi +} + +link_logic() { + if [ ${mode} = "reg" ]; then + ln -s ${1} ${2} + else + rm -f ${2} + fi +} + +# +# Get the absolute path to a symbolic link's reference. +# +# Parameters: +# $* : path - the path to the file (link) to dereference (can have spaces in +# the path). +# +# Output: +# This function writes the path to the link reference to stdout. +# +# +dereference() { + path="$*" + result= + + # + # Make sure the path is absolute + # + parent="`cd \`dirname \"${path}\"\`; pwd -P`" + child="`basename \"${path}\"`" + + # + # if parent == child, then path == /, and is already absolute + # + if [ "${parent}" != "${child}" ]; then + path="${parent}/${child}" + fi + + if [ -h "${path}" ]; then + path=`ls -l "${path}" | sed -e "s#^.*${path} -> ##"` + + # make sure the path is still absolute (starts with '/') + if expr "${path}" : '[^/]' > /dev/null; then + path="${parent}/${path}" + fi + fi + + echo ${path} +} + +# +# Check for all the parts required to launch the control panel relative to the +# given path. +# +# +# Parameters: +# $* : path - the path to examine, presumably the resolved path to this +# script (can have spaces in the path). +# +# Output: +# If successful, this function outputs the absolute path to a directory +# containing the Java binary, and ../lib/deploy.jar; otherwise it outputs +# an empty string. (Output is to stdout.) +# +# Note: the assumption is that this function returns either: +# +# /jre/bin, or +# /bin +# +# However, as long as the directory pointed by the path returned by this +# function contains: +# +# ./java +# ../lib/deploy.jar +# +# it should be possible to successfully launch the JCP from the given +# information. +# +check_parts() { + result="`cd \`dirname \"$*\"\`; pwd -P`" + + # if this is a JDK, we need the JRE subdir + if [ -d "${result}/../jre/bin" ]; then + result="`cd \`dirname \"$*\"\`/../jre/bin; pwd -P`" + fi + + if [ ! -x "${result}/java" ] || [ ! -f "${result}/../lib/deploy.jar" ]; then + result= + fi + + echo ${result} +} + +# +# Launch the Java Control Panel. +# +# Parameters: +# $* : path - the path of this script (can have spaces in the path). +# +launch_jcp() { + path="$*" + while [ -h ${path} ]; do + path="`dereference ${path}`" + done + + java_home="`check_parts ${path}`" + if [ -n "${java_home}" ]; then + # launch the JCP using paths relative to + ${java_home}/java -Djavaplugin.user.profile=${USER_JPI_PROFILE} \ + -Xbootclasspath/a:${java_home}/../lib/deploy.jar \ + ${_JAVA_VM_OPTIONS} \ + com.sun.deploy.panel.ControlPanel + else + echo "${XLERROR}${java_home}" + exit 1 + fi +} + +# +# Manage the process of registering/unregistering the Java Plug-in with a given +# container (browser). +# +manage_container() { + # Do the "right" thing based on the provided scheme. + plugin_stem=${java_home}/plugin/${proc} + if [ ! -d ${plugin_stem} ]; then + echo "${JLERROR}${java_home}" + exit 1 + fi + + case ${scheme} in + ns4 | ns4E ) + plugin_location="${plugin_stem}/ns4" + if [ ${mode} = "reg" ]; then + echo "${plugin_location}" + fi + ;; + ns4L ) + plugin_location="${plugin_stem}/ns4" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + ns610 | ns610L ) + plugin_location="${plugin_stem}/ns610" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + * ) + echo ${ISERROR}${scheme} + exit 1 + esac +} + +while getopts ":r:u:c:j:" opt; do + case $opt in + r ) mode="reg";scheme=${OPTARG} + ;; + u ) mode="unreg";scheme=${OPTARG} + ;; + c ) container_home=${OPTARG} + ;; + j ) java_home=${OPTARG} + ;; + : ) echo ${USAGE} + exit 1 + ;; + \? ) echo ${USAGE} + exit 1 + ;; + esac +done + +os=`uname -s` +if [ "${os}" = "Linux" ]; then + case "`uname -m`" in + i[3-9]86 | ia32 | ia64 | x86_64) + proc=i386 + ;; + sparc*) + proc=sparc + ;; + arm*) + proc=arm + ;; + ppc*) + proc=ppc + ;; + *) + proc="`uname -m`" + ;; + esac +else + proc=`uname -p` +fi + +if [ -z "${scheme}" ] && + [ -z "${java_home}" ] && [ -z "${container_home}" ] +then + # just run the control panel + launch_jcp $0 +elif [ -n "${scheme}" ] && + [ -n "${java_home}" ] && [ -n "${container_home}" ] +then + # try to register/unregister the plugin + manage_container +else + # one or more missing args + echo ${USAGE} + exit 1 +fi diff --git a/jdk-1.8.0.281/jre/bin/java b/jdk-1.8.0.281/jre/bin/java new file mode 100755 index 0000000..cba6d8e Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/java differ diff --git a/jdk-1.8.0.281/jre/bin/javaws b/jdk-1.8.0.281/jre/bin/javaws new file mode 100755 index 0000000..cc20fe4 Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/javaws differ diff --git a/jdk-1.8.0.281/jre/bin/jcontrol b/jdk-1.8.0.281/jre/bin/jcontrol new file mode 100755 index 0000000..57f80a8 --- /dev/null +++ b/jdk-1.8.0.281/jre/bin/jcontrol @@ -0,0 +1,245 @@ +#!/bin/bash +# +# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# Shell Script to run the Java Plug-in control panel. +# +# Parse the command-line options +# -r means make associate with the container (i.e browser) +# -u means remove the association with the container +# -c provides the location of the container install +# -j provides the location of the jre install +# if neither -r or -u are specified, run the ControlPanel UI + +USAGE='usage: ControlPanel [ (-u scheme | -r scheme) -c cpath -j jrepath ]' +JLERROR='ControlPanel: Error: Invalid JRE location: ' +CLERROR='ControlPanel: Error: Invalid container location: ' +IPERROR='ControlPanel: Error: Insufficient permission' +ISERROR='ControlPanel: Error: Invalid scheme: ' +XLERROR='ControlPanel: Error: Invalid link or copy: ' + +check_container_dir() { + + if [ ! -d ${1} ]; then + echo "${CLERROR}${2}" + exit 1 + fi + if [ ! -w ${1} ]; then + echo "${IPERROR}" + exit 1 + fi +} + +link_logic() { + if [ ${mode} = "reg" ]; then + ln -s ${1} ${2} + else + rm -f ${2} + fi +} + +# +# Get the absolute path to a symbolic link's reference. +# +# Parameters: +# $* : path - the path to the file (link) to dereference (can have spaces in +# the path). +# +# Output: +# This function writes the path to the link reference to stdout. +# +# +dereference() { + path="$*" + result= + + # + # Make sure the path is absolute + # + parent="`cd \`dirname \"${path}\"\`; pwd -P`" + child="`basename \"${path}\"`" + + # + # if parent == child, then path == /, and is already absolute + # + if [ "${parent}" != "${child}" ]; then + path="${parent}/${child}" + fi + + if [ -h "${path}" ]; then + path=`ls -l "${path}" | sed -e "s#^.*${path} -> ##"` + + # make sure the path is still absolute (starts with '/') + if expr "${path}" : '[^/]' > /dev/null; then + path="${parent}/${path}" + fi + fi + + echo ${path} +} + +# +# Check for all the parts required to launch the control panel relative to the +# given path. +# +# +# Parameters: +# $* : path - the path to examine, presumably the resolved path to this +# script (can have spaces in the path). +# +# Output: +# If successful, this function outputs the absolute path to a directory +# containing the Java binary, and ../lib/deploy.jar; otherwise it outputs +# an empty string. (Output is to stdout.) +# +# Note: the assumption is that this function returns either: +# +# /jre/bin, or +# /bin +# +# However, as long as the directory pointed by the path returned by this +# function contains: +# +# ./java +# ../lib/deploy.jar +# +# it should be possible to successfully launch the JCP from the given +# information. +# +check_parts() { + result="`cd \`dirname \"$*\"\`; pwd -P`" + + # if this is a JDK, we need the JRE subdir + if [ -d "${result}/../jre/bin" ]; then + result="`cd \`dirname \"$*\"\`/../jre/bin; pwd -P`" + fi + + if [ ! -x "${result}/java" ] || [ ! -f "${result}/../lib/deploy.jar" ]; then + result= + fi + + echo ${result} +} + +# +# Launch the Java Control Panel. +# +# Parameters: +# $* : path - the path of this script (can have spaces in the path). +# +launch_jcp() { + path="$*" + while [ -h ${path} ]; do + path="`dereference ${path}`" + done + + java_home="`check_parts ${path}`" + if [ -n "${java_home}" ]; then + # launch the JCP using paths relative to + ${java_home}/java -Djavaplugin.user.profile=${USER_JPI_PROFILE} \ + -Xbootclasspath/a:${java_home}/../lib/deploy.jar \ + ${_JAVA_VM_OPTIONS} \ + com.sun.deploy.panel.ControlPanel + else + echo "${XLERROR}${java_home}" + exit 1 + fi +} + +# +# Manage the process of registering/unregistering the Java Plug-in with a given +# container (browser). +# +manage_container() { + # Do the "right" thing based on the provided scheme. + plugin_stem=${java_home}/plugin/${proc} + if [ ! -d ${plugin_stem} ]; then + echo "${JLERROR}${java_home}" + exit 1 + fi + + case ${scheme} in + ns4 | ns4E ) + plugin_location="${plugin_stem}/ns4" + if [ ${mode} = "reg" ]; then + echo "${plugin_location}" + fi + ;; + ns4L ) + plugin_location="${plugin_stem}/ns4" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + ns610 | ns610L ) + plugin_location="${plugin_stem}/ns610" + filename=`ls ${plugin_location}` + container_target="${container_home}/plugins" + check_container_dir ${container_target} ${container_home} + link_logic ${plugin_location}/${filename} ${container_target}/${filename} + ;; + * ) + echo ${ISERROR}${scheme} + exit 1 + esac +} + +while getopts ":r:u:c:j:" opt; do + case $opt in + r ) mode="reg";scheme=${OPTARG} + ;; + u ) mode="unreg";scheme=${OPTARG} + ;; + c ) container_home=${OPTARG} + ;; + j ) java_home=${OPTARG} + ;; + : ) echo ${USAGE} + exit 1 + ;; + \? ) echo ${USAGE} + exit 1 + ;; + esac +done + +os=`uname -s` +if [ "${os}" = "Linux" ]; then + case "`uname -m`" in + i[3-9]86 | ia32 | ia64 | x86_64) + proc=i386 + ;; + sparc*) + proc=sparc + ;; + arm*) + proc=arm + ;; + ppc*) + proc=ppc + ;; + *) + proc="`uname -m`" + ;; + esac +else + proc=`uname -p` +fi + +if [ -z "${scheme}" ] && + [ -z "${java_home}" ] && [ -z "${container_home}" ] +then + # just run the control panel + launch_jcp $0 +elif [ -n "${scheme}" ] && + [ -n "${java_home}" ] && [ -n "${container_home}" ] +then + # try to register/unregister the plugin + manage_container +else + # one or more missing args + echo ${USAGE} + exit 1 +fi diff --git a/jdk-1.8.0.281/jre/bin/jjs b/jdk-1.8.0.281/jre/bin/jjs new file mode 100755 index 0000000..2bd7f11 Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/jjs differ diff --git a/jdk-1.8.0.281/jre/bin/keytool b/jdk-1.8.0.281/jre/bin/keytool new file mode 100755 index 0000000..c8acf21 Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/keytool differ diff --git a/jdk-1.8.0.281/jre/bin/orbd b/jdk-1.8.0.281/jre/bin/orbd new file mode 100755 index 0000000..81422f5 Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/orbd differ diff --git a/jdk-1.8.0.281/jre/bin/pack200 b/jdk-1.8.0.281/jre/bin/pack200 new file mode 100755 index 0000000..290798a Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/pack200 differ diff --git a/jdk-1.8.0.281/jre/bin/policytool b/jdk-1.8.0.281/jre/bin/policytool new file mode 100755 index 0000000..eea9a1c Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/policytool differ diff --git a/jdk-1.8.0.281/jre/bin/rmid b/jdk-1.8.0.281/jre/bin/rmid new file mode 100755 index 0000000..96ea921 Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/rmid differ diff --git a/jdk-1.8.0.281/jre/bin/rmiregistry b/jdk-1.8.0.281/jre/bin/rmiregistry new file mode 100755 index 0000000..9a7874d Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/rmiregistry differ diff --git a/jdk-1.8.0.281/jre/bin/servertool b/jdk-1.8.0.281/jre/bin/servertool new file mode 100755 index 0000000..bd3bd9a Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/servertool differ diff --git a/jdk-1.8.0.281/jre/bin/tnameserv b/jdk-1.8.0.281/jre/bin/tnameserv new file mode 100755 index 0000000..29216a8 Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/tnameserv differ diff --git a/jdk-1.8.0.281/jre/bin/unpack200 b/jdk-1.8.0.281/jre/bin/unpack200 new file mode 100755 index 0000000..a90e02a Binary files /dev/null and b/jdk-1.8.0.281/jre/bin/unpack200 differ diff --git a/jdk-1.8.0.281/jre/legal/javafx/directshow.md b/jdk-1.8.0.281/jre/legal/javafx/directshow.md new file mode 100755 index 0000000..bbe1e27 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/directshow.md @@ -0,0 +1,26 @@ +## Microsoft DirectShow Samples v156905 + +### MIT License (MIT) +``` + +Copyright (c) 1992-2004 Microsoft Corporation. All rights reserved. + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/glib.md b/jdk-1.8.0.281/jre/legal/javafx/glib.md new file mode 100755 index 0000000..1ee603b --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/glib.md @@ -0,0 +1,538 @@ +## GNU Glib v2.62.2 + +### Glib Notice +``` + +You are receiving a copy of GNU Glib, Version: 2.62.2 in either source or +object code in the JavaFX runtime or JavaFX SDK. The terms of the +Oracle license do NOT apply to the GNU Glib, Version: 2.62.2; it is +licensed under the following license, separately from the Oracle programs +you receive. If you do not wish to install this library, you may delete +this library: + + - On 32-bit Linux systems: delete $(JAVA_HOME)/lib/i386/libglib-lite.so + - On 64-bit Linux systems: delete $(JAVA_HOME)/lib/amd64/libglib-lite.so + - On Mac OS X systems: delete $(JAVA_HOME)/lib/libglib-lite.dylib + - On Windows systems: delete $(JAVA_HOME)\bin\glib-lite.dll + +A copy of the Oracle modified GNU Glib library source code is located +in the following OpenJDK git repository: + + https://github.com/openjdk/jfx + +You can use git to clone the repository or you can browse the +source using a web browser. The root directory of the GNU Glib source +code is here: + + rt/modules/javafx.media/src/main/native/gstreamer/3rd_party/glib/ + + +``` + +### LGPL 2.1 +``` + + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with this library; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/gstreamer.md b/jdk-1.8.0.281/jre/legal/javafx/gstreamer.md new file mode 100755 index 0000000..450ce80 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/gstreamer.md @@ -0,0 +1,536 @@ +## GStreamer v1.16.1 + +### GStreamer Notice +``` + +You are receiving a copy of GStreamer, Version: 1.16.1 in either source or +object code in the JavaFX runtime or JavaFX SDK. The terms of the +Oracle license do NOT apply to the GStreamer, Version: 1.16.1; it is +licensed under the following license, separately from the Oracle programs +you receive. If you do not wish to install this library, you may delete +this library: + + - On 32-bit Linux systems: delete $(JAVA_HOME)/lib/i386/libgstreamer-lite.so + - On 64-bit Linux systems: delete $(JAVA_HOME)/lib/amd64/libgstreamer-lite.so + - On Mac OS X systems: delete $(JAVA_HOME)/lib/libgstreamer-lite.dylib + - On Windows systems: delete $(JAVA_HOME)\bin\gstreamer-lite.dll + +A copy of the Oracle modified GStreamer library source code is located +in the following OpenJDK git repository: + + https://github.com/openjdk/jfx + +You can use git to clone the repository or you can browse the +source using a web browser. The root directory of the GStreamer source +code is here: + + rt/modules/javafx.media/src/main/native/gstreamer/gstreamer-lite/ +``` + +### LGPL 2.1 +``` + + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with this library; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/icu_web.md b/jdk-1.8.0.281/jre/legal/javafx/icu_web.md new file mode 100755 index 0000000..bbdc8d4 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/icu_web.md @@ -0,0 +1,421 @@ +## IBM International Components for Unicode (ICU4C) v64.2 + +### ICU License +``` + +COPYRIGHT AND PERMISSION NOTICE (ICU 58 and later) + +Copyright © 1991-2019 Unicode, Inc. All rights reserved. +Distributed under the Terms of Use in https://www.unicode.org/copyright.html. + +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Unicode data files and any associated documentation +(the "Data Files") or Unicode software and any associated documentation +(the "Software") to deal in the Data Files or Software +without restriction, including without limitation the rights to use, +copy, modify, merge, publish, distribute, and/or sell copies of +the Data Files or Software, and to permit persons to whom the Data Files +or Software are furnished to do so, provided that either +(a) this copyright and permission notice appear with all copies +of the Data Files or Software, or +(b) this copyright and permission notice appear in associated +Documentation. + +THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF +ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE +WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +NONINFRINGEMENT OF THIRD PARTY RIGHTS. +IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS +NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL +DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, +DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER +TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR +PERFORMANCE OF THE DATA FILES OR SOFTWARE. + +Except as contained in this notice, the name of a copyright holder +shall not be used in advertising or otherwise to promote the sale, +use or other dealings in these Data Files or Software without prior +written authorization of the copyright holder. + +--------------------- + +Third-Party Software Licenses + +This section contains third-party software notices and/or additional +terms for licensed third-party software components included within ICU +libraries. + +1. ICU License - ICU 1.8.1 to ICU 57.1 + +COPYRIGHT AND PERMISSION NOTICE + +Copyright (c) 1995-2016 International Business Machines Corporation and others +All rights reserved. + +Permission is hereby granted, free of charge, to any person obtaining +a copy of this software and associated documentation files (the +"Software"), to deal in the Software without restriction, including +without limitation the rights to use, copy, modify, merge, publish, +distribute, and/or sell copies of the Software, and to permit persons +to whom the Software is furnished to do so, provided that the above +copyright notice(s) and this permission notice appear in all copies of +the Software and that both the above copyright notice(s) and this +permission notice appear in supporting documentation. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR +HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY +SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER +RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF +CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN +CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Except as contained in this notice, the name of a copyright holder +shall not be used in advertising or otherwise to promote the sale, use +or other dealings in this Software without prior written authorization +of the copyright holder. + +All trademarks and registered trademarks mentioned herein are the +property of their respective owners. + +2. Chinese/Japanese Word Break Dictionary Data (cjdict.txt) + + # The Google Chrome software developed by Google is licensed under + # the BSD license. Other software included in this distribution is + # provided under other licenses, as set forth below. + # + # The BSD License + # http://opensource.org/licenses/bsd-license.php + # Copyright (C) 2006-2008, Google Inc. + # + # All rights reserved. + # + # Redistribution and use in source and binary forms, with or without + # modification, are permitted provided that the following conditions are met: + # + # Redistributions of source code must retain the above copyright notice, + # this list of conditions and the following disclaimer. + # Redistributions in binary form must reproduce the above + # copyright notice, this list of conditions and the following + # disclaimer in the documentation and/or other materials provided with + # the distribution. + # Neither the name of Google Inc. nor the names of its + # contributors may be used to endorse or promote products derived from + # this software without specific prior written permission. + # + # + # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + # CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, + # INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF + # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + # DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE + # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF + # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR + # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF + # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING + # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + # + # + # The word list in cjdict.txt are generated by combining three word lists + # listed below with further processing for compound word breaking. The + # frequency is generated with an iterative training against Google web + # corpora. + # + # * Libtabe (Chinese) + # - https://sourceforge.net/project/?group_id=1519 + # - Its license terms and conditions are shown below. + # + # * IPADIC (Japanese) + # - http://chasen.aist-nara.ac.jp/chasen/distribution.html + # - Its license terms and conditions are shown below. + # + # ---------COPYING.libtabe ---- BEGIN-------------------- + # + # /* + # * Copyright (c) 1999 TaBE Project. + # * Copyright (c) 1999 Pai-Hsiang Hsiao. + # * All rights reserved. + # * + # * Redistribution and use in source and binary forms, with or without + # * modification, are permitted provided that the following conditions + # * are met: + # * + # * . Redistributions of source code must retain the above copyright + # * notice, this list of conditions and the following disclaimer. + # * . Redistributions in binary form must reproduce the above copyright + # * notice, this list of conditions and the following disclaimer in + # * the documentation and/or other materials provided with the + # * distribution. + # * . Neither the name of the TaBE Project nor the names of its + # * contributors may be used to endorse or promote products derived + # * from this software without specific prior written permission. + # * + # * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + # * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + # * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS + # * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + # * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, + # * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES + # * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR + # * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + # * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, + # * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + # * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED + # * OF THE POSSIBILITY OF SUCH DAMAGE. + # */ + # + # /* + # * Copyright (c) 1999 Computer Systems and Communication Lab, + # * Institute of Information Science, Academia + # * Sinica. All rights reserved. + # * + # * Redistribution and use in source and binary forms, with or without + # * modification, are permitted provided that the following conditions + # * are met: + # * + # * . Redistributions of source code must retain the above copyright + # * notice, this list of conditions and the following disclaimer. + # * . Redistributions in binary form must reproduce the above copyright + # * notice, this list of conditions and the following disclaimer in + # * the documentation and/or other materials provided with the + # * distribution. + # * . Neither the name of the Computer Systems and Communication Lab + # * nor the names of its contributors may be used to endorse or + # * promote products derived from this software without specific + # * prior written permission. + # * + # * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + # * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + # * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS + # * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + # * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, + # * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES + # * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR + # * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + # * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, + # * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + # * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED + # * OF THE POSSIBILITY OF SUCH DAMAGE. + # */ + # + # Copyright 1996 Chih-Hao Tsai @ Beckman Institute, + # University of Illinois + # c-tsai4@uiuc.edu http://casper.beckman.uiuc.edu/~c-tsai4 + # + # ---------------COPYING.libtabe-----END-------------------------------- + # + # + # ---------------COPYING.ipadic-----BEGIN------------------------------- + # + # Copyright 2000, 2001, 2002, 2003 Nara Institute of Science + # and Technology. All Rights Reserved. + # + # Use, reproduction, and distribution of this software is permitted. + # Any copy of this software, whether in its original form or modified, + # must include both the above copyright notice and the following + # paragraphs. + # + # Nara Institute of Science and Technology (NAIST), + # the copyright holders, disclaims all warranties with regard to this + # software, including all implied warranties of merchantability and + # fitness, in no event shall NAIST be liable for + # any special, indirect or consequential damages or any damages + # whatsoever resulting from loss of use, data or profits, whether in an + # action of contract, negligence or other tortuous action, arising out + # of or in connection with the use or performance of this software. + # + # A large portion of the dictionary entries + # originate from ICOT Free Software. The following conditions for ICOT + # Free Software applies to the current dictionary as well. + # + # Each User may also freely distribute the Program, whether in its + # original form or modified, to any third party or parties, PROVIDED + # that the provisions of Section 3 ("NO WARRANTY") will ALWAYS appear + # on, or be attached to, the Program, which is distributed substantially + # in the same form as set out herein and that such intended + # distribution, if actually made, will neither violate or otherwise + # contravene any of the laws and regulations of the countries having + # jurisdiction over the User or the intended distribution itself. + # + # NO WARRANTY + # + # The program was produced on an experimental basis in the course of the + # research and development conducted during the project and is provided + # to users as so produced on an experimental basis. Accordingly, the + # program is provided without any warranty whatsoever, whether express, + # implied, statutory or otherwise. The term "warranty" used herein + # includes, but is not limited to, any warranty of the quality, + # performance, merchantability and fitness for a particular purpose of + # the program and the nonexistence of any infringement or violation of + # any right of any third party. + # + # Each user of the program will agree and understand, and be deemed to + # have agreed and understood, that there is no warranty whatsoever for + # the program and, accordingly, the entire risk arising from or + # otherwise connected with the program is assumed by the user. + # + # Therefore, neither ICOT, the copyright holder, or any other + # organization that participated in or was otherwise related to the + # development of the program and their respective officials, directors, + # officers and other employees shall be held liable for any and all + # damages, including, without limitation, general, special, incidental + # and consequential damages, arising out of or otherwise in connection + # with the use or inability to use the program or any product, material + # or result produced or otherwise obtained by using the program, + # regardless of whether they have been advised of, or otherwise had + # knowledge of, the possibility of such damages at any time during the + # project or thereafter. Each user will be deemed to have agreed to the + # foregoing by his or her commencement of use of the program. The term + # "use" as used herein includes, but is not limited to, the use, + # modification, copying and distribution of the program and the + # production of secondary products from the program. + # + # In the case where the program, whether in its original form or + # modified, was distributed or delivered to or received by a user from + # any person, organization or entity other than ICOT, unless it makes or + # grants independently of ICOT any specific warranty to the user in + # writing, such person, organization or entity, will also be exempted + # from and not be held liable to the user for any such damages as noted + # above as far as the program is concerned. + # + # ---------------COPYING.ipadic-----END---------------------------------- + +3. Lao Word Break Dictionary Data (laodict.txt) + + # Copyright (c) 2013 International Business Machines Corporation + # and others. All Rights Reserved. + # + # Project: http://code.google.com/p/lao-dictionary/ + # Dictionary: http://lao-dictionary.googlecode.com/git/Lao-Dictionary.txt + # License: http://lao-dictionary.googlecode.com/git/Lao-Dictionary-LICENSE.txt + # (copied below) + # + # This file is derived from the above dictionary, with slight + # modifications. + # ---------------------------------------------------------------------- + # Copyright (C) 2013 Brian Eugene Wilson, Robert Martin Campbell. + # All rights reserved. + # + # Redistribution and use in source and binary forms, with or without + # modification, + # are permitted provided that the following conditions are met: + # + # + # Redistributions of source code must retain the above copyright notice, this + # list of conditions and the following disclaimer. Redistributions in + # binary form must reproduce the above copyright notice, this list of + # conditions and the following disclaimer in the documentation and/or + # other materials provided with the distribution. + # + # + # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS + # FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + # COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + # INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES + # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR + # SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, + # STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED + # OF THE POSSIBILITY OF SUCH DAMAGE. + # -------------------------------------------------------------------------- + +4. Burmese Word Break Dictionary Data (burmesedict.txt) + + # Copyright (c) 2014 International Business Machines Corporation + # and others. All Rights Reserved. + # + # This list is part of a project hosted at: + # github.com/kanyawtech/myanmar-karen-word-lists + # + # -------------------------------------------------------------------------- + # Copyright (c) 2013, LeRoy Benjamin Sharon + # All rights reserved. + # + # Redistribution and use in source and binary forms, with or without + # modification, are permitted provided that the following conditions + # are met: Redistributions of source code must retain the above + # copyright notice, this list of conditions and the following + # disclaimer. Redistributions in binary form must reproduce the + # above copyright notice, this list of conditions and the following + # disclaimer in the documentation and/or other materials provided + # with the distribution. + # + # Neither the name Myanmar Karen Word Lists, nor the names of its + # contributors may be used to endorse or promote products derived + # from this software without specific prior written permission. + # + # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + # CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, + # INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF + # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + # DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS + # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, + # EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED + # TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, + # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON + # ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR + # TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF + # THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + # SUCH DAMAGE. + # -------------------------------------------------------------------------- + +5. Time Zone Database + + ICU uses the public domain data and code derived from Time Zone +Database for its time zone support. The ownership of the TZ database +is explained in BCP 175: Procedure for Maintaining the Time Zone +Database section 7. + + # 7. Database Ownership + # + # The TZ database itself is not an IETF Contribution or an IETF + # document. Rather it is a pre-existing and regularly updated work + # that is in the public domain, and is intended to remain in the + # public domain. Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do + # not apply to the TZ Database or contributions that individuals make + # to it. Should any claims be made and substantiated against the TZ + # Database, the organization that is providing the IANA + # Considerations defined in this RFC, under the memorandum of + # understanding with the IETF, currently ICANN, may act in accordance + # with all competent court orders. No ownership claims will be made + # by ICANN or the IETF Trust on the database or the code. Any person + # making a contribution to the database or code waives all rights to + # future claims in that contribution or in the TZ Database. + +6. Google double-conversion + +Copyright 2006-2011, the V8 project authors. All rights reserved. +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are +met: + + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + * Redistributions in binary form must reproduce the above + copyright notice, this list of conditions and the following + disclaimer in the documentation and/or other materials provided + with the distribution. + * Neither the name of Google Inc. nor the names of its + contributors may be used to endorse or promote products derived + from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR +A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT +OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, +SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/jpeg_fx.md b/jdk-1.8.0.281/jre/legal/javafx/jpeg_fx.md new file mode 100755 index 0000000..e4afe6e --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/jpeg_fx.md @@ -0,0 +1,51 @@ +## Independent JPEG Group (IJG) JPEG v9d + +### IJG License +``` + +/* + * jcapimin.c + * + * Copyright (C) 1994-1998, Thomas G. Lane. + * Modified 2003-2010 by Guido Vollbeding. + * This file is part of the Independent JPEG Group's software. + * For conditions of distribution and use, see the accompanying README file. + */ + +[From the README file] +The authors make NO WARRANTY or representation, either express or implied, +with respect to this software, its quality, accuracy, merchantability, or +fitness for a particular purpose. This software is provided "AS IS", and you, +its user, assume the entire risk as to its quality and accuracy. + +This software is copyright (C) 1991-2020, Thomas G. Lane, Guido Vollbeding. +All Rights Reserved except as specified below. + +Permission is hereby granted to use, copy, modify, and distribute this +software (or portions thereof) for any purpose, without fee, subject to these +conditions: +(1) If any part of the source code for this software is distributed, then this +README file must be included, with this copyright and no-warranty notice +unaltered; and any additions, deletions, or changes to the original files +must be clearly indicated in accompanying documentation. +(2) If only executable code is distributed, then the accompanying +documentation must state that "this software is based in part on the work of +the Independent JPEG Group". +(3) Permission for use of this software is granted only if the user accepts +full responsibility for any undesirable consequences; the authors accept +NO LIABILITY for damages of any kind. + +These conditions apply to any software derived from or based on the IJG code, +not just to the unmodified library. If you use our work, you ought to +acknowledge us. + +Permission is NOT granted for the use of any IJG author's name or company name +in advertising or publicity relating to this software or products derived from +it. This software may be referred to only as "the Independent JPEG Group's +software". + +We specifically permit and encourage the use of this software as the basis of +commercial products, provided that all warranty or liability claims are +assumed by the product vendor. + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/libffi.md b/jdk-1.8.0.281/jre/legal/javafx/libffi.md new file mode 100755 index 0000000..3f474b2 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/libffi.md @@ -0,0 +1,28 @@ +## LibFFI v3.3 + +### LibFFI License +``` + +libffi - Copyright (c) 1996-2019 Anthony Green, Red Hat, Inc and others. +See source files for details. + +Permission is hereby granted, free of charge, to any person obtaining +a copy of this software and associated documentation files (the +``Software''), to deal in the Software without restriction, including +without limitation the rights to use, copy, modify, merge, publish, +distribute, sublicense, and/or sell copies of the Software, and to +permit persons to whom the Software is furnished to do so, subject to +the following conditions: + +The above copyright notice and this permission notice shall be +included in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY +CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, +TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/libxml2.md b/jdk-1.8.0.281/jre/legal/javafx/libxml2.md new file mode 100755 index 0000000..c263490 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/libxml2.md @@ -0,0 +1,30 @@ +## xmlsoft.org: libxml2 v2.9.10 + +### libxml2 License +``` + +Except where otherwise noted in the source code (e.g. the files hash.c, +list.c and the trio files, which are covered by a similar licence but +with different Copyright notices) all the files are: + +Copyright (C) 1998-2012 Daniel Veillard. All Rights Reserved. + +Permission is hereby granted, free of charge, to any person obtaining a copy of +this software and associated documentation files (the "Software"), to deal in +the Software without restriction, including without limitation the rights to +use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies +of the Software, and to permit persons to whom the Software is furnished to do +so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/libxslt.md b/jdk-1.8.0.281/jre/legal/javafx/libxslt.md new file mode 100755 index 0000000..c0e5bd6 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/libxslt.md @@ -0,0 +1,60 @@ +## xmlsoft.org: libxslt v1.1.34 + +### libxslt License +``` + +Licence for libxslt except libexslt +---------------------------------------------------------------------- + Copyright (C) 2001-2002 Daniel Veillard. All Rights Reserved. + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is fur- +nished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT- +NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER +IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON- +NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +Except as contained in this notice, the name of Daniel Veillard shall not +be used in advertising or otherwise to promote the sale, use or other deal- +ings in this Software without prior written authorization from him. + +---------------------------------------------------------------------- + +Licence for libexslt +---------------------------------------------------------------------- + Copyright (C) 2001-2002 Thomas Broyer, Charlie Bozeman and Daniel Veillard. + All Rights Reserved. + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is fur- +nished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT- +NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER +IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON- +NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +Except as contained in this notice, the name of the authors shall not +be used in advertising or otherwise to promote the sale, use or other deal- +ings in this Software without prior written authorization from him. +---------------------------------------------------------------------- + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/mesa3d.md b/jdk-1.8.0.281/jre/legal/javafx/mesa3d.md new file mode 100755 index 0000000..b3f32d8 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/mesa3d.md @@ -0,0 +1,134 @@ +## Mesa 3-D Graphics Library v19.2.1 + +### Mesa License + +``` +Copyright (C) 1999-2007 Brian Paul All Rights Reserved. + +Permission is hereby granted, free of charge, to any person obtaining a +copy of this software and associated documentation files (the "Software"), +to deal in the Software without restriction, including without limitation +the rights to use, copy, modify, merge, publish, distribute, sublicense, +and/or sell copies of the Software, and to permit persons to whom the +Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included +in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +Attention, Contributors + +When contributing to the Mesa project you must agree to the licensing terms +of the component to which you're contributing. +The following section lists the primary components of the Mesa distribution +and their respective licenses. +Mesa Component Licenses + + + +Component Location License +------------------------------------------------------------------ +Main Mesa code src/mesa/ MIT +Device drivers src/mesa/drivers/* MIT, generally + +Gallium code src/gallium/ MIT + +Ext headers GL/glext.h Khronos + GL/glxext.h Khronos + GL/wglext.h Khronos + KHR/khrplatform.h Khronos + +***************************************************************************** + +---- +include/GL/gl.h : + + + Mesa 3-D graphics library + + Copyright (C) 1999-2006 Brian Paul All Rights Reserved. + Copyright (C) 2009 VMware, Inc. All Rights Reserved. + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and associated documentation files (the "Software"), + to deal in the Software without restriction, including without limitation + the rights to use, copy, modify, merge, publish, distribute, sublicense, + and/or sell copies of the Software, and to permit persons to whom the + Software is furnished to do so, subject to the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS + OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR + OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, + ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR + OTHER DEALINGS IN THE SOFTWARE. + + ***************************************************************************** + +---- +include/GL/glext.h +include/GL/glxext.h +include/GL/wglxext.h : + + + Copyright (c) 2013 - 2018 The Khronos Group Inc. + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and/or associated documentation files (the + "Materials"), to deal in the Materials without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Materials, and to + permit persons to whom the Materials are furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Materials. + + THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. + IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY + CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, + TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE + MATERIALS OR THE USE OR OTHER DEALINGS IN THE MATERIALS. + + ***************************************************************************** + +---- +include/KHR/khrplatform.h : + + Copyright (c) 2008 - 2018 The Khronos Group Inc. + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and/or associated documentation files (the + "Materials"), to deal in the Materials without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Materials, and to + permit persons to whom the Materials are furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Materials. + + THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. + IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY + CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, + TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE + MATERIALS OR THE USE OR OTHER DEALINGS IN THE MATERIALS. + + ***************************************************************************** + +``` diff --git a/jdk-1.8.0.281/jre/legal/javafx/webkit.md b/jdk-1.8.0.281/jre/legal/javafx/webkit.md new file mode 100755 index 0000000..f02a07b --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/javafx/webkit.md @@ -0,0 +1,536 @@ +## WebKit Open Source Project: WebKit v610.1 + +### WebKit Notice +``` + +You are receiving a copy of WebKit in either source or +object code in the JavaFX runtime or JavaFX SDK. The terms of the +Oracle license do NOT apply to WebKit; it is +licensed under the following license, separately from the Oracle programs +you receive. If you do not wish to install this library, you may delete +this library: + + - On 32-bit Linux systems: delete $(JAVA_HOME)/lib/i386/libjfxwebkit.so + - On 64-bit Linux systems: delete $(JAVA_HOME)/lib/amd64/libjfxwebkit.so + - On Mac OS X systems: delete $(JAVA_HOME)/lib/libjfxwebkit.dylib + - On Windows systems: delete $(JAVA_HOME)\bin\jfxwebkit.dll + +A copy of the Oracle modified WebKit library source code is located +in the following OpenJDK git repository: + + https://github.com/openjdk/jfx + +You can use git to clone the repository or you can browse the +source using a web browser. The root directory of the WebKit source +code is here: + + rt/modules/javafx.web/src/main/native/ +``` + +### LGPL 2.1 +``` + + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with this library; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/asm.md b/jdk-1.8.0.281/jre/legal/jdk/asm.md new file mode 100755 index 0000000..bbaf73e --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/asm.md @@ -0,0 +1,36 @@ +## ASM Bytecode Manipulation Framework v5.0.3 + +### ASM License +``` + +Copyright (c) 2000-2011 France Télécom +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + +1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + +2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + +3. Neither the name of the copyright holders nor the names of its + contributors may be used to endorse or promote products derived from + this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" +AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE +LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +THE POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/bcel.md b/jdk-1.8.0.281/jre/legal/jdk/bcel.md new file mode 100755 index 0000000..a5f1249 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/bcel.md @@ -0,0 +1,222 @@ +## Apache Commons Byte Code Engineering Library (BCEL) Version 6.3.1 + +### Apache Commons BCEL Notice +``` + + ========================================================================= + == NOTICE file corresponding to the section 4 d of == + == the Apache License, Version 2.0, == + == in this case for the Apache Commons BCEL distribution. == + ========================================================================= + + This product includes software developed by + The Apache Software Foundation (http://www.apache.org/). + +``` + +### Apache 2.0 License +``` + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + +TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + +1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + +2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + +3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + +4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + +5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + +6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + +7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + +8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + +9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + +END OF TERMS AND CONDITIONS + +APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + +Copyright [yyyy] [name of copyright owner] + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/cldr.md b/jdk-1.8.0.281/jre/legal/jdk/cldr.md new file mode 100755 index 0000000..666bd69 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/cldr.md @@ -0,0 +1,63 @@ +## Unicode Common Local Data Repository (CLDR) v21.0.1 + +### CLDR License + +``` + +UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE + +Unicode Data Files include all data files under the directories +http://www.unicode.org/Public/, http://www.unicode.org/reports/, and +http://www.unicode.org/cldr/data/. Unicode Data Files do not include PDF +online code charts under the directory http://www.unicode.org/Public/. +Software includes any source code published in the Unicode Standard or under +the directories http://www.unicode.org/Public/, +http://www.unicode.org/reports/, and http://www.unicode.org/cldr/data/. + +NOTICE TO USER: Carefully read the following legal agreement. BY DOWNLOADING, +INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S DATA FILES ("DATA +FILES"), AND/OR SOFTWARE ("SOFTWARE"), YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO +BE BOUND BY, ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT +AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR +SOFTWARE. + +COPYRIGHT AND PERMISSION NOTICE + +Copyright © 1991-2012 Unicode, Inc. All rights reserved. Distributed under the +Terms of Use in http://www.unicode.org/copyright.html. + +Permission is hereby granted, free of charge, to any person obtaining a copy +of the Unicode data files and any associated documentation (the "Data Files") +or Unicode software and any associated documentation (the "Software") to deal +in the Data Files or Software without restriction, including without +limitation the rights to use, copy, modify, merge, publish, distribute, and/or +sell copies of the Data Files or Software, and to permit persons to whom the +Data Files or Software are furnished to do so, provided that (a) the above +copyright notice(s) and this permission notice appear with all copies of the +Data Files or Software, (b) both the above copyright notice(s) and this +permission notice appear in associated documentation, and (c) there is clear +notice in each modified Data File or in the Software as well as in the +documentation associated with the Data File(s) or Software that the data or +software has been modified. + +THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY +KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD +PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN +THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL +DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR +PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS +ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE +DATA FILES OR SOFTWARE. + +Except as contained in this notice, the name of a copyright holder shall not +be used in advertising or otherwise to promote the sale, use or other dealings +in these Data Files or Software without prior written authorization of the +copyright holder. + +Unicode and the Unicode logo are trademarks of Unicode, Inc. in the United +States and other countries. All third party trademarks referenced herein are +the property of their respective owners. + + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/colorimaging.md b/jdk-1.8.0.281/jre/legal/jdk/colorimaging.md new file mode 100755 index 0000000..1ff8517 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/colorimaging.md @@ -0,0 +1,7 @@ +## Eastman Kodak Company: Portions of color management and imaging software + +### Eastman Kodak Notice +``` +Portions Copyright Eastman Kodak Company 1991-2003 +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/cryptix.md b/jdk-1.8.0.281/jre/legal/jdk/cryptix.md new file mode 100755 index 0000000..cd19206 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/cryptix.md @@ -0,0 +1,35 @@ +## Cryptix AES v3.2.0 + +### Cryptix General License +``` + +Copyright (c) 1995-2005 The Cryptix Foundation Limited. +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are +met: + + 1. Redistributions of source code must retain the copyright notice, + this list of conditions and the following disclaimer. + + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in + the documentation and/or other materials provided with the + distribution. + +THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND +CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, +INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BE +LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR +BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, +WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE +OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN +IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/dom.md b/jdk-1.8.0.281/jre/legal/jdk/dom.md new file mode 100755 index 0000000..fc8fd4b --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/dom.md @@ -0,0 +1,62 @@ +## DOM Level 3 Core Specification v1.0 + +### W3C License +``` + +W3C SOFTWARE NOTICE AND LICENSE + +http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 + +This work (and included software, documentation such as READMEs, or other +related items) is being provided by the copyright holders under the following +license. By obtaining, using and/or copying this work, you (the licensee) +agree that you have read, understood, and will comply with the following terms +and conditions. + +Permission to copy, modify, and distribute this software and its +documentation, with or without modification, for any purpose and without fee +or royalty is hereby granted, provided that you include the following on ALL +copies of the software and documentation or portions thereof, including +modifications: + + 1.The full text of this NOTICE in a location viewable to users of the + redistributed or derivative work. + + 2.Any pre-existing intellectual property disclaimers, notices, or terms and + conditions. If none exist, the W3C Software Short Notice should be included + (hypertext is preferred, text is permitted) within the body of any + redistributed or derivative code. + + 3.Notice of any changes or modifications to the files, including the date + changes were made. (We recommend you provide URIs to the location from + which the code is derived.) + +THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS +MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT +LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR +PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY +THIRD PARTY PATENTS,COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. + +COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL +OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR +DOCUMENTATION. The name and trademarks of copyright holders may NOT be used +in advertising or publicity pertaining to the software without specific, +written prior permission. Title to copyright in this software and any +associated documentation will at all times remain with copyright holders. + +____________________________________ + +This formulation of W3C's notice and license became active on December 31 +2002. This version removes the copyright ownership notice such that this +license can be used with materials other than those owned by the W3C, reflects +that ERCIM is now a host of the W3C, includes references to this specific +dated version of the license, and removes the ambiguous grant of "use". +Otherwise, this version is the same as the previous version and is written so +as to preserve the Free Software Foundation's assessment of GPL compatibility +and OSI's certification under the Open Source Definition. Please see our +Copyright FAQ for common questions about using materials from our site, +including specific terms and conditions for packages like libwww, Amaya, and +Jigsaw. Other questions about this notice can be directed to +site-policy@w3.org. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/dynalink.md b/jdk-1.8.0.281/jre/legal/jdk/dynalink.md new file mode 100755 index 0000000..cf08f12 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/dynalink.md @@ -0,0 +1,32 @@ +## Dynalink v.5 + +### Dynalink License +``` + +Copyright (c) 2009-2013, Attila Szegedi + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are +met: +* Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. +* Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. +* Neither the name of the copyright holder nor the names of + contributors may be used to endorse or promote products derived from + this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS +IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL COPYRIGHT HOLDER +BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR +BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, +WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR +OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF +ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/ecc.md b/jdk-1.8.0.281/jre/legal/jdk/ecc.md new file mode 100755 index 0000000..80dc503 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/ecc.md @@ -0,0 +1,581 @@ +## Mozilla Elliptic Curve Cryptography (ECC) + +### Mozilla ECC Notice + +``` +This notice is provided with respect to Elliptic Curve Cryptography, +which is included with JRE, JDK, and OpenJDK. + +You are receiving a copy +of the Elliptic Curve Cryptography library in source +form with the JDK and OpenJDK source distributions, and as object code in +the JRE & JDK runtimes. + +In the case of the JRE & JDK runtimes, the terms of the Oracle license do +NOT apply to the Elliptic Curve Cryptography library; it is licensed under the +following license, separately from Oracle's JDK & JRE. If you do not wish to +install the Elliptic Curve Cryptography library, you may delete the +Elliptic Curve Cryptography library: + - On Solaris and Linux systems: delete $(JAVA_HOME)/lib/libsunec.so + - On Windows systems: delete $(JAVA_HOME)\bin\sunec.dll + - On Mac OSX systems: delete + For JRE: /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/libsunec.dylib + For JDK: $(JAVA_HOME)/jre/lib/libsunec.dylib + +``` + +### Written Offer for Source Code +``` + +For third party technology that you receive from Oracle in binary form +which is licensed under an open source license that gives you the right +to receive the source code for that binary, you can obtain a copy of +the applicable source code from this page: +http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/tip/src/share/native/sun/security/ec/impl + +If the source code for the technology was not provided to you with the +binary, you can also receive a copy of the source code on physical +media by submitting a written request to: + + Oracle America, Inc. + Attn: Associate General Counsel, + Development and Engineering Legal + 500 Oracle Parkway, 10th Floor + Redwood Shores, CA 94065 + +Or, you may send an email to Oracle using the form at: + +http://www.oracle.com/goto/opensourcecode/request + +Your request should include: + + - The name of the component or binary file(s) for which you are requesting the source code + + - The name and version number of the Oracle product containing the binary + + - The date you received the Oracle product + + - Your name + + - Your company name (if applicable) + + - Your return mailing address and email and + + - A telephone number in the event we need to reach you. + +We may charge you a fee to cover the cost of physical media and processing. +Your request must be sent (i) within three (3) years of the date you +received the Oracle product that included the component or binary +file(s) that are the subject of your request, or (ii) in the case of +code licensed under the GPL v3, for as long as Oracle offers spare +parts or customer support for that product model. + +``` + +### LGPL 2.1 +``` + + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with this library; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/freebxml.md b/jdk-1.8.0.281/jre/legal/jdk/freebxml.md new file mode 100755 index 0000000..96623e1 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/freebxml.md @@ -0,0 +1,73 @@ +## freebXML Registry v3.1 + +### freebXML Notice +``` + + * + * This software consists of voluntary contributions made by many + * individuals on behalf of the freebxml Software Foundation. For more + * information on the freebxml Software Foundation, please see + * "http://www.freebxml.org/". + * + * This product includes software developed by the Apache Software + * Foundation (http://www.apache.org/). + * + * $Header: /cvsroot/ebxmlrr/omar/license.txt,v 1.3 2006/04/16 19:10:35 dougb62 Exp $ + * + +``` + + +### The freebXML License, Version 1.1 +``` + + ==================================================================== + * + * The freebxml License, Version 1.1 + * + * Copyright (c) 2001 freebxml.org. All rights + * reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in + * the documentation and/or other materials provided with the + * distribution. + * + * 3. The end-user documentation included with the redistribution, if + * any, must include the following acknowlegement: + * "This product includes software developed by + * freebxml.org (http://www.freebxml.org/)." + * Alternately, this acknowlegement may appear in the software itself, + * if and wherever such third-party acknowlegements normally appear. + * + * 4. The names "The freebXML Registry Project", "freebxml Software + * Foundation" must not be used to endorse or promote products derived + * from this software without prior written permission. For written + * permission, please contact ebxmlrr-team@lists.sourceforge.net. + * + * 5. Products derived from this software may not be called "freebxml", + * "freebXML Registry" nor may freebxml" appear in their names without prior + * written permission of the freebxml Group. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED + * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + * DISCLAIMED. IN NO EVENT SHALL THE freebxml SOFTWARE FOUNDATION OR + * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND + * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, + * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT + * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * ==================================================================== + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/giflib.md b/jdk-1.8.0.281/jre/legal/jdk/giflib.md new file mode 100755 index 0000000..3a9884d --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/giflib.md @@ -0,0 +1,32 @@ +## GIFLIB v5.2.1 + +### GIFLIB License +``` + +The GIFLIB distribution is Copyright (c) 1997 Eric S. Raymond + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. + + +https://sourceforge.net/p/giflib/code/ci/master/tree/openbsd-reallocarray.c + +Copyright (c) 2008 Otto Moerbeek +SPDX-License-Identifier: MIT + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/icu.md b/jdk-1.8.0.281/jre/legal/jdk/icu.md new file mode 100755 index 0000000..9bf02a6 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/icu.md @@ -0,0 +1,66 @@ +## International Components for Unicode (ICU4J) v60.2 + +### ICU4J License + +``` + +UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE +Unicode Data Files include all data files under the directories +http://www.unicode.org/Public/, http://www.unicode.org/reports/, +http://www.unicode.org/cldr/data/, +http://source.icu-project.org/repos/icu/, and +http://www.unicode.org/utility/trac/browser/. + +Unicode Data Files do not include PDF online code charts under the +directory http://www.unicode.org/Public/. + +Software includes any source code published in the Unicode Standard +or under the directories +http://www.unicode.org/Public/, http://www.unicode.org/reports/, +http://www.unicode.org/cldr/data/, +http://source.icu-project.org/repos/icu/, and +http://www.unicode.org/utility/trac/browser/. + +NOTICE TO USER: Carefully read the following legal agreement. +BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S +DATA FILES ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"), +YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE +TERMS AND CONDITIONS OF THIS AGREEMENT. +IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE +THE DATA FILES OR SOFTWARE. + +COPYRIGHT AND PERMISSION NOTICE + +Copyright © 1991-2018 Unicode, Inc. All rights reserved. +Distributed under the Terms of Use in http://www.unicode.org/copyright.html. + +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Unicode data files and any associated documentation +(the "Data Files") or Unicode software and any associated documentation +(the "Software") to deal in the Data Files or Software +without restriction, including without limitation the rights to use, +copy, modify, merge, publish, distribute, and/or sell copies of +the Data Files or Software, and to permit persons to whom the Data Files +or Software are furnished to do so, provided that either +(a) this copyright and permission notice appear with all copies +of the Data Files or Software, or +(b) this copyright and permission notice appear in associated +Documentation. + +THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF +ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE +WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +NONINFRINGEMENT OF THIRD PARTY RIGHTS. +IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS +NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL +DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, +DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER +TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR +PERFORMANCE OF THE DATA FILES OR SOFTWARE. + +Except as contained in this notice, the name of a copyright holder +shall not be used in advertising or otherwise to promote the sale, +use or other dealings in these Data Files or Software without prior +written authorization of the copyright holder. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/jcup.md b/jdk-1.8.0.281/jre/legal/jdk/jcup.md new file mode 100755 index 0000000..354d2f1 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/jcup.md @@ -0,0 +1,24 @@ +## CUP Parser Generator for Java v 0.11b + +### CUP Parser Generator License +``` + +Copyright 1996-2015 by Scott Hudson, Frank Flannery, C. Scott Ananian, Michael Petter + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, provided +that the above copyright notice appear in all copies and that both +the copyright notice and this permission notice and warranty disclaimer +appear in supporting documentation, and that the names of the authors or +their employers not be used in advertising or publicity pertaining to +distribution of the software without specific, written prior permission. + +The authors and their employers disclaim all warranties with regard to +this software, including all implied warranties of merchantability and +fitness. In no event shall the authors or their employers be liable for +any special, indirect or consequential damages or any damages whatsoever +resulting from loss of use, data or profits, whether in an action of +contract, negligence or other tortious action, arising out of or in +connection with the use or performance of this software. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/joni.md b/jdk-1.8.0.281/jre/legal/jdk/joni.md new file mode 100755 index 0000000..0a61f06 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/joni.md @@ -0,0 +1,27 @@ +## JRuby Joni v2.1.40 + +### MIT License +``` + +Copyright (c) 2017 JRuby Team + +Permission is hereby granted, free of charge, to any person obtaining a +copy of this software and associated documentation files (the "Software"), +to deal in the Software without restriction, including without limitation +the rights to use, copy, modify, merge, publish, distribute, sublicense, +and/or sell copies of the Software, and to permit persons to whom the +Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included +in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR +OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, +ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR +OTHER DEALINGS IN THE SOFTWARE. + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/jopt-simple.md b/jdk-1.8.0.281/jre/legal/jdk/jopt-simple.md new file mode 100755 index 0000000..404a6c2 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/jopt-simple.md @@ -0,0 +1,27 @@ +## jopt-simple v3.0 + +### MIT License +``` + +Copyright (c) 2004-2009 Paul R. Holser, Jr. + +Permission is hereby granted, free of charge, to any person obtaining +a copy of this software and associated documentation files (the +"Software"), to deal in the Software without restriction, including +without limitation the rights to use, copy, modify, merge, publish, +distribute, sublicense, and/or sell copies of the Software, and to +permit persons to whom the Software is furnished to do so, subject to +the following conditions: + +The above copyright notice and this permission notice shall be +included in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR +OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, +ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR +OTHER DEALINGS IN THE SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/jpeg.md b/jdk-1.8.0.281/jre/legal/jdk/jpeg.md new file mode 100755 index 0000000..be7b11f --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/jpeg.md @@ -0,0 +1,83 @@ +## Independent JPEG Group: JPEG release 6b + +### JPEG License +``` + +Must reproduce following license in documentation and/or other materials +provided with distribution: + +The authors make NO WARRANTY or representation, either express or implied, +with respect to this software, its quality, accuracy, merchantability, or +fitness for a particular purpose. This software is provided "AS IS", +and you, its user, assume the entire risk as to its quality and accuracy. + +This software is copyright (C) 1991-1998, Thomas G. Lane. +All Rights Reserved except as specified below. + +Permission is hereby granted to use, copy, modify, and distribute +this software (or portions thereof) for any purpose, without fee, +subject to these conditions: + +(1) If any part of the source code for this software is distributed, +then this README file must be included, with this copyright and no-warranty +notice unaltered; and any additions, deletions, or changes to the original +files must be clearly indicated in accompanying documentation. + +(2) If only executable code is distributed, then the accompanying documentation +must state that "this software is based in part on the work of the +Independent JPEG Group". + +(3) Permission for use of this software is granted only if the user accepts +full responsibility for any undesirable consequences; the authors accept +NO LIABILITY for damages of any kind. + +These conditions apply to any software derived from or based on the IJG code, +not just to the unmodified library. If you use our work, you ought to +acknowledge us. + +Permission is NOT granted for the use of any IJG author's name or company name +in advertising or publicity relating to this software or products derived +from it. This software may be referred to only as "the Independent JPEG +Group's software". + +We specifically permit and encourage the use of this software as the basis +of commercial products, provided that all warranty or liability claims are +assumed by the product vendor. + + +ansi2knr.c is included in this distribution by permission of L. Peter Deutsch, +sole proprietor of its copyright holder, Aladdin Enterprises of Menlo Park, CA. +ansi2knr.c is NOT covered by the above copyright and conditions, but instead +by the usual distribution terms of the Free Software Foundation; principally, +that you must include source code if you redistribute it. +(See the file ansi2knr.c for full details.) However, since ansi2knr.c is +not needed as part of any program generated from the IJG code, this does not +limit you more than the foregoing paragraphs do. + +The Unix configuration script "configure" was produced with GNU Autoconf. +It is copyright by the Free Software Foundation but is freely distributable. +The same holds for its supporting scripts (config.guess, config.sub, +ltconfig, ltmain.sh). Another support script, install-sh, is copyright +by M.I.T. but is also freely distributable. + +It appears that the arithmetic coding option of the JPEG spec is covered +by patents owned by IBM, AT&T, and Mitsubishi. Hence arithmetic coding +cannot legally be used without obtaining one or more licenses. For this +reason, support for arithmetic coding has been removed from the free +JPEG software. (Since arithmetic coding provides only a marginal gain +over the unpatented Huffman mode, it is unlikely that very many +implementations will support it.) So far as we are aware, there are +no patent restrictions on the remaining code. + +The IJG distribution formerly included code to read and write GIF files. +To avoid entanglement with the Unisys LZW patent, GIF reading support +has been removed altogether, and the GIF writer has been simplified to +produce "uncompressed GIFs". This technique does not use the LZW algorithm; +the resulting GIF files are larger than usual, but are readable by all +standard GIF decoders. + +We are required to state that "The Graphics Interchange Format(c) is +the Copyright property of CompuServe Incorporated. GIF(sm) is a +Service Mark property of CompuServe Incorporated." + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/lcms.md b/jdk-1.8.0.281/jre/legal/jdk/lcms.md new file mode 100755 index 0000000..134da8a --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/lcms.md @@ -0,0 +1,27 @@ +## Little Color Management System (LCMS) v2.11 + +### LCMS License +``` + +Little Color Management System +Copyright (c) 1998-2020 Marti Maria Saguer + +Permission is hereby granted, free of charge, to any person obtaining +a copy of this software and associated documentation files (the "Software"), +to deal in the Software without restriction, including without limitation +the rights to use, copy, modify, merge, publish, distribute, sublicense, +and/or sell copies of the Software, and to permit persons to whom the Software +is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO +THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE +LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION +OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION +WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/libpng.md b/jdk-1.8.0.281/jre/legal/jdk/libpng.md new file mode 100755 index 0000000..6fdf467 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/libpng.md @@ -0,0 +1,144 @@ +## libpng v1.6.37 + +### libpng License +``` + + + + COPYRIGHT NOTICE, DISCLAIMER, and LICENSE + ========================================= + + PNG Reference Library License version 2 + --------------------------------------- + + * Copyright (c) 1995-2019 The PNG Reference Library Authors. + * Copyright (c) 2018-2019 Cosmin Truta. + * Copyright (c) 2000-2002, 2004, 2006-2018 Glenn Randers-Pehrson. + * Copyright (c) 1996-1997 Andreas Dilger. + * Copyright (c) 1995-1996 Guy Eric Schalnat, Group 42, Inc. + + The software is supplied "as is", without warranty of any kind, + express or implied, including, without limitation, the warranties + of merchantability, fitness for a particular purpose, title, and + non-infringement. In no event shall the Copyright owners, or + anyone distributing the software, be liable for any damages or + other liability, whether in contract, tort or otherwise, arising + from, out of, or in connection with the software, or the use or + other dealings in the software, even if advised of the possibility + of such damage. + + Permission is hereby granted to use, copy, modify, and distribute + this software, or portions hereof, for any purpose, without fee, + subject to the following restrictions: + + 1. The origin of this software must not be misrepresented; you + must not claim that you wrote the original software. If you + use this software in a product, an acknowledgment in the product + documentation would be appreciated, but is not required. + + 2. Altered source versions must be plainly marked as such, and must + not be misrepresented as being the original software. + + 3. This Copyright notice may not be removed or altered from any + source or altered source distribution. + + + PNG Reference Library License version 1 (for libpng 0.5 through 1.6.35) + ----------------------------------------------------------------------- + + libpng versions 1.0.7, July 1, 2000, through 1.6.35, July 15, 2018 are + Copyright (c) 2000-2002, 2004, 2006-2018 Glenn Randers-Pehrson, are + derived from libpng-1.0.6, and are distributed according to the same + disclaimer and license as libpng-1.0.6 with the following individuals + added to the list of Contributing Authors: + + Simon-Pierre Cadieux + Eric S. Raymond + Mans Rullgard + Cosmin Truta + Gilles Vollant + James Yu + Mandar Sahastrabuddhe + Google Inc. + Vadim Barkov + + and with the following additions to the disclaimer: + + There is no warranty against interference with your enjoyment of + the library or against infringement. There is no warranty that our + efforts or the library will fulfill any of your particular purposes + or needs. This library is provided with all faults, and the entire + risk of satisfactory quality, performance, accuracy, and effort is + with the user. + + Some files in the "contrib" directory and some configure-generated + files that are distributed with libpng have other copyright owners, and + are released under other open source licenses. + + libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are + Copyright (c) 1998-2000 Glenn Randers-Pehrson, are derived from + libpng-0.96, and are distributed according to the same disclaimer and + license as libpng-0.96, with the following individuals added to the + list of Contributing Authors: + + Tom Lane + Glenn Randers-Pehrson + Willem van Schaik + + libpng versions 0.89, June 1996, through 0.96, May 1997, are + Copyright (c) 1996-1997 Andreas Dilger, are derived from libpng-0.88, + and are distributed according to the same disclaimer and license as + libpng-0.88, with the following individuals added to the list of + Contributing Authors: + + John Bowler + Kevin Bracey + Sam Bushell + Magnus Holmgren + Greg Roelofs + Tom Tanner + + Some files in the "scripts" directory have other copyright owners, + but are released under this license. + + libpng versions 0.5, May 1995, through 0.88, January 1996, are + Copyright (c) 1995-1996 Guy Eric Schalnat, Group 42, Inc. + + For the purposes of this copyright and license, "Contributing Authors" + is defined as the following set of individuals: + + Andreas Dilger + Dave Martindale + Guy Eric Schalnat + Paul Schmidt + Tim Wegner + + The PNG Reference Library is supplied "AS IS". The Contributing + Authors and Group 42, Inc. disclaim all warranties, expressed or + implied, including, without limitation, the warranties of + merchantability and of fitness for any purpose. The Contributing + Authors and Group 42, Inc. assume no liability for direct, indirect, + incidental, special, exemplary, or consequential damages, which may + result from the use of the PNG Reference Library, even if advised of + the possibility of such damage. + + Permission is hereby granted to use, copy, modify, and distribute this + source code, or portions hereof, for any purpose, without fee, subject + to the following restrictions: + + 1. The origin of this source code must not be misrepresented. + + 2. Altered versions must be plainly marked as such and must not + be misrepresented as being the original source. + + 3. This Copyright notice may not be removed or altered from any + source or altered source distribution. + + The Contributing Authors and Group 42, Inc. specifically permit, + without fee, and encourage the use of this source code as a component + to supporting the PNG file format in commercial products. If you use + this source code in a product, acknowledgment is not required but would + be appreciated. + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/libxrandr.md b/jdk-1.8.0.281/jre/legal/jdk/libxrandr.md new file mode 100755 index 0000000..dcd2bab --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/libxrandr.md @@ -0,0 +1,37 @@ +## libXrandr v1.5.2 (Unix only) + +Copyright notice and license for Xrandr.h. + +### libXrandr License +``` + + + Copyright © 2000 Compaq Computer Corporation, Inc. + Copyright © 2002 Hewlett-Packard Company, Inc. + Copyright © 2006 Intel Corporation + Copyright © 2008 Red Hat, Inc. + + Permission to use, copy, modify, distribute, and sell this software and its + documentation for any purpose is hereby granted without fee, provided that + the above copyright notice appear in all copies and that both that copyright + notice and this permission notice appear in supporting documentation, and + that the name of the copyright holders not be used in advertising or + publicity pertaining to distribution of the software without specific, + written prior permission. The copyright holders make no representations + about the suitability of this software for any purpose. It is provided "as + is" without express or implied warranty. + + THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, + INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO + EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR + CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, + DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER + TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE + OF THIS SOFTWARE. + + Author: Jim Gettys, HP Labs, Hewlett-Packard, Inc. + Keith Packard, Intel Corporation + + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/mesa3d.md b/jdk-1.8.0.281/jre/legal/jdk/mesa3d.md new file mode 100755 index 0000000..4a8b4f7 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/mesa3d.md @@ -0,0 +1,134 @@ +## Mesa 3-D Graphics Library v19.2.1 + +### Mesa License +``` + +Copyright (C) 1999-2007 Brian Paul All Rights Reserved. + +Permission is hereby granted, free of charge, to any person obtaining a +copy of this software and associated documentation files (the "Software"), +to deal in the Software without restriction, including without limitation +the rights to use, copy, modify, merge, publish, distribute, sublicense, +and/or sell copies of the Software, and to permit persons to whom the +Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included +in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +Attention, Contributors + +When contributing to the Mesa project you must agree to the licensing terms +of the component to which you're contributing. +The following section lists the primary components of the Mesa distribution +and their respective licenses. +Mesa Component Licenses + + + +Component Location License +------------------------------------------------------------------ +Main Mesa code src/mesa/ MIT +Device drivers src/mesa/drivers/* MIT, generally + +Gallium code src/gallium/ MIT + +Ext headers GL/glext.h Khronos + GL/glxext.h Khronos + GL/wglext.h Khronos + KHR/khrplatform.h Khronos + +***************************************************************************** + +---- +include/GL/gl.h : + + + Mesa 3-D graphics library + + Copyright (C) 1999-2006 Brian Paul All Rights Reserved. + Copyright (C) 2009 VMware, Inc. All Rights Reserved. + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and associated documentation files (the "Software"), + to deal in the Software without restriction, including without limitation + the rights to use, copy, modify, merge, publish, distribute, sublicense, + and/or sell copies of the Software, and to permit persons to whom the + Software is furnished to do so, subject to the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS + OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR + OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, + ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR + OTHER DEALINGS IN THE SOFTWARE. + + ***************************************************************************** + +---- +include/GL/glext.h +include/GL/glxext.h +include/GL/wglxext.h : + + + Copyright (c) 2013 - 2018 The Khronos Group Inc. + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and/or associated documentation files (the + "Materials"), to deal in the Materials without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Materials, and to + permit persons to whom the Materials are furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Materials. + + THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. + IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY + CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, + TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE + MATERIALS OR THE USE OR OTHER DEALINGS IN THE MATERIALS. + + ***************************************************************************** + +---- +include/KHR/khrplatform.h : + + Copyright (c) 2008 - 2018 The Khronos Group Inc. + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and/or associated documentation files (the + "Materials"), to deal in the Materials without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Materials, and to + permit persons to whom the Materials are furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Materials. + + THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. + IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY + CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, + TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE + MATERIALS OR THE USE OR OTHER DEALINGS IN THE MATERIALS. + + ***************************************************************************** + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/pcsclite.md b/jdk-1.8.0.281/jre/legal/jdk/pcsclite.md new file mode 100755 index 0000000..1731327 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/pcsclite.md @@ -0,0 +1,36 @@ +## PC/SC Lite v1.8.26 + +### PC/SC Lite License +``` + +Copyright (c) 1999-2003 David Corcoran +Copyright (c) 2001-2011 Ludovic Rousseau +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + +1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. +2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. +3. The name of the author may not be used to endorse or promote products + derived from this software without specific prior written permission. + +Changes to this license can be made only by the copyright author with +explicit written consent. + +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/pkcs11cryptotoken.md b/jdk-1.8.0.281/jre/legal/jdk/pkcs11cryptotoken.md new file mode 100755 index 0000000..8d2efca --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/pkcs11cryptotoken.md @@ -0,0 +1,33 @@ +## OASIS PKCS #11 Cryptographic Token Interface v2.40 + +### OASIS PKCS #11 Cryptographic Token Interface License +``` + +Copyright (c) OASIS Open 2016. All Rights Reserved. + +All capitalized terms in the following text have the meanings assigned to them in the OASIS +Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the +OASIS website: [http://www.oasis-open.org/policies-guidelines/ipr] + +This document and translations of it may be copied and furnished to others, and derivative works +that comment on or otherwise explain it or assist in its implementation may be prepared, copied, +published, and distributed, in whole or in part, without restriction of any kind, provided that +the above copyright notice and this section are included on all such copies and derivative works. +However, this document itself may not be modified in any way, including by removing the copyright +notice or references to OASIS, except as needed for the purpose of developing any document or +deliverable produced by an OASIS Technical Committee (in which case the rules applicable to +copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it +into languages other than English. + +The limited permissions granted above are perpetual and will not be revoked by OASIS or its +successors or assigns. + +This document and the information contained herein is provided on an "AS IS" basis and OASIS +DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE +USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF +MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS AND ITS MEMBERS WILL NOT BE LIABLE FOR +ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THIS DOCUMENT OR +ANY PART THEREOF. + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/pkcs11wrapper.md b/jdk-1.8.0.281/jre/legal/jdk/pkcs11wrapper.md new file mode 100755 index 0000000..793d6a2 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/pkcs11wrapper.md @@ -0,0 +1,46 @@ +## IAIK (Institute for Applied Information Processing and Communication) PKCS#11 wrapper files v1 + +### IAIK License +``` + +Copyright (c) 2002 Graz University of Technology. All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met: + +1. Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + +2. Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + +3. The end-user documentation included with the redistribution, if any, must + include the following acknowledgment: + + "This product includes software developed by IAIK of Graz University of + Technology." + + Alternately, this acknowledgment may appear in the software itself, if and + wherever such third-party acknowledgments normally appear. + +4. The names "Graz University of Technology" and "IAIK of Graz University of + Technology" must not be used to endorse or promote products derived from this + software without prior written permission. + +5. Products derived from this software may not be called "IAIK PKCS Wrapper", + nor may "IAIK" appear in their name, without prior written permission of + Graz University of Technology. + +THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, +INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND +FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, +OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/relaxngcc.md b/jdk-1.8.0.281/jre/legal/jdk/relaxngcc.md new file mode 100755 index 0000000..672600e --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/relaxngcc.md @@ -0,0 +1,48 @@ +## RelaxNGCC v 1.12 + +### RelaxNGCC License + +``` + +Copyright (c) 2000-2003 Daisuke Okajima and Kohsuke Kawaguchi. +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met: + +1. Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + +2. Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + +3. The end-user documentation included with the redistribution, if any, must + include the following acknowledgment: + + "This product includes software developed by Daisuke Okajima + and Kohsuke Kawaguchi (http://relaxngcc.sf.net/)." + +Alternately, this acknowledgment may appear in the software itself, if and +wherever such third-party acknowledgments normally appear. + +4. The names of the copyright holders must not be used to endorse or promote + products derived from this software without prior written permission. For + written permission, please contact the copyright holders. + +5. Products derived from this software may not be called "RELAXNGCC", nor may + "RELAXNGCC" appear in their name, without prior written permission of the + copyright holders. + +THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, +INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND +FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE APACHE +SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, +EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/relaxngdatatype.md b/jdk-1.8.0.281/jre/legal/jdk/relaxngdatatype.md new file mode 100755 index 0000000..cc15d01 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/relaxngdatatype.md @@ -0,0 +1,37 @@ +## RelaxNG Datatype v1.0 + +### RelaxNG Datatype License +``` + +Copyright (c) 2005, 2010 Thai Open Source Software Center Ltd +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are +met: + + Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + + Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in + the documentation and/or other materials provided with the + distribution. + + Neither the names of the copyright holders nor the names of its + contributors may be used to endorse or promote products derived + from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR +A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR +CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/relaxngom.md b/jdk-1.8.0.281/jre/legal/jdk/relaxngom.md new file mode 100755 index 0000000..922604b --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/relaxngom.md @@ -0,0 +1,24 @@ +## RelaxNG Object Model/Parser (RNGOM.jar) v20050510 + +### RelaxNG Object Model/Parser License +``` +Copyright (c) Kohsuke Kawaguchi + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: The above copyright +notice and this permission notice shall be included in all copies or +substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/santuario.md b/jdk-1.8.0.281/jre/legal/jdk/santuario.md new file mode 100755 index 0000000..d9209d8 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/santuario.md @@ -0,0 +1,238 @@ +## Apache Santuario XML Security for Java v2.1.4 + +### Apache Santuario Notice +``` + +Apache Santuario - XML Security for Java +Copyright 1999-2019 The Apache Software Foundation + +This product includes software developed at +The Apache Software Foundation (http://www.apache.org/). + +It was originally based on software copyright (c) 2001, Institute for +Data Communications Systems, . + +The development of this software was partly funded by the European +Commission in the project in the ISIS Programme. + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + + +``` + +### Apache 2.0 License +``` + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + +TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + +1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + +2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + +3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + +4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + +5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + +6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + +7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + +8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + +9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + +END OF TERMS AND CONDITIONS + +APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + +Copyright [yyyy] [name of copyright owner] + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/thaidict.md b/jdk-1.8.0.281/jre/legal/jdk/thaidict.md new file mode 100755 index 0000000..21edd2c --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/thaidict.md @@ -0,0 +1,31 @@ +## Thai Dictionary + +### Thai Dictionary License +``` + +Copyright (C) 1982 The Royal Institute, Thai Royal Government. + +Copyright (C) 1998 National Electronics and Computer Technology Center, +National Science and Technology Development Agency, +Ministry of Science Technology and Environment, +Thai Royal Government. + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/unicode.md b/jdk-1.8.0.281/jre/legal/jdk/unicode.md new file mode 100755 index 0000000..fc9dc4f --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/unicode.md @@ -0,0 +1,53 @@ +## Unicode Character Database v6.2 + +### Unicode Character Database + +``` + UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE + + See Terms of Use for definitions of Unicode Inc.'s + Data Files and Software. + + NOTICE TO USER: Carefully read the following legal agreement. + BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S + DATA FILES ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"), + YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE + TERMS AND CONDITIONS OF THIS AGREEMENT. + IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE + THE DATA FILES OR SOFTWARE. + + COPYRIGHT AND PERMISSION NOTICE + Copyright © 1991-2019 Unicode, Inc. All rights reserved. + Distributed under the Terms of Use in https://www.unicode.org/copyright.html. + + Permission is hereby granted, free of charge, to any person obtaining + a copy of the Unicode data files and any associated documentation + (the "Data Files") or Unicode software and any associated documentation + (the "Software") to deal in the Data Files or Software + without restriction, including without limitation the rights to use, + copy, modify, merge, publish, distribute, and/or sell copies of + the Data Files or Software, and to permit persons to whom the Data Files + or Software are furnished to do so, provided that either + (a) this copyright and permission notice appear with all copies + of the Data Files or Software, or + (b) this copyright and permission notice appear in associated + Documentation. + +THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF + ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE + WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT OF THIRD PARTY RIGHTS. + IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS + NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL + DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, + DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER + TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR + PERFORMANCE OF THE DATA FILES OR SOFTWARE. + +Except as contained in this notice, the name of a copyright holder +shall not be used in advertising or otherwise to promote the sale, + use or other dealings in these Data Files or Software without prior + written authorization of the copyright holder. + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/xalan.md b/jdk-1.8.0.281/jre/legal/jdk/xalan.md new file mode 100755 index 0000000..c2da5d2 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/xalan.md @@ -0,0 +1,234 @@ +## Apache Xalan v2.7.2 + +### Apache Xalan Notice +``` + + ====================================================================================== + == NOTICE file corresponding to the section 4d of the Apache License, Version 2.0, == + == in this case for the Apache Xalan distribution. == + ====================================================================================== + + This product includes software developed by + The Apache Software Foundation (http://www.apache.org/). + + Specifically, we only include the XSLTC portion of the source from the Xalan distribution. + The Xalan project has two processors: an interpretive one (Xalan Interpretive) and a + compiled one (The XSLT Compiler (XSLTC)). We *only* use the XSLTC part of Xalan; We use + the source from the packages that are part of the XSLTC sources. + + Portions of this software was originally based on the following: + + - software copyright (c) 1999-2002, Lotus Development Corporation., http://www.lotus.com. + - software copyright (c) 2001-2002, Sun Microsystems., http://www.sun.com. + - software copyright (c) 2003, IBM Corporation., http://www.ibm.com. + - voluntary contributions made by Ovidiu Predescu (ovidiu@cup.hp.com) on behalf of the + Apache Software Foundation and was originally developed at Hewlett Packard Company. + +``` + +### Apache 2.0 License +``` + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + +TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + +1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + +2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + +3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + +4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + +5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + +6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + +7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + +8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + +9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + +END OF TERMS AND CONDITIONS + +APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + +Copyright [yyyy] [name of copyright owner] + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/xerces.md b/jdk-1.8.0.281/jre/legal/jdk/xerces.md new file mode 100755 index 0000000..64a9ba5 --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/xerces.md @@ -0,0 +1,229 @@ +## Apache Xerces v2.12.1 + +### Apache Xerces Notice +``` + ========================================================================= + == NOTICE file corresponding to section 4(d) of the Apache License, == + == Version 2.0, in this case for the Apache Xerces Java distribution. == + ========================================================================= + + Apache Xerces Java + Copyright 1999-2020 The Apache Software Foundation + + This product includes software developed at + The Apache Software Foundation (http://www.apache.org/). + + Portions of this software were originally based on the following: + - software copyright (c) 1999, IBM Corporation., http://www.ibm.com. + - software copyright (c) 1999, Sun Microsystems., http://www.sun.com. + - voluntary contributions made by Paul Eng on behalf of the + Apache Software Foundation that were originally developed at iClick, Inc., + software copyright (c) 1999. +``` + +### Apache 2.0 License +``` + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + +TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + +1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + +2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + +3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + +4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + +5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + +6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + +7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + +8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + +9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + +END OF TERMS AND CONDITIONS + +APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + +Copyright [yyyy] [name of copyright owner] + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/xmlresolver.md b/jdk-1.8.0.281/jre/legal/jdk/xmlresolver.md new file mode 100755 index 0000000..0ee77ab --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/xmlresolver.md @@ -0,0 +1,233 @@ +## Apache XML Commons Resolver v1.2 + +### Apache XML Commons Resolver Notice + +``` + +This product includes software developed by The Apache Software +Foundation (http://www.apache.org/). + +Copyright 2001-2004 The Apache Software Foundation or its licensor, +as applicable. + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + +``` + +### Apache 2.0 License +``` + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + +TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + +1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + +2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + +3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + +4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + +5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + +6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + +7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + +8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + +9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + +END OF TERMS AND CONDITIONS + +APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + +Copyright [yyyy] [name of copyright owner] + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/xorgproto.md b/jdk-1.8.0.281/jre/legal/jdk/xorgproto.md new file mode 100755 index 0000000..20d8a5c --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/xorgproto.md @@ -0,0 +1,101 @@ +## xorgproto v2020.1 (Unix only) + +### X.Org Foundation xorgproto License + +``` + +This is the copyright for HPkeysym.h + +Copyright 1987, 1998 The Open Group + +Permission to use, copy, modify, distribute, and sell this software and its +documentation for any purpose is hereby granted without fee, provided that +the above copyright notice appear in all copies and that both that +copyright notice and this permission notice appear in supporting +documentation. + +The above copyright notice and this permission notice shall be included +in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR +OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, +ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR +OTHER DEALINGS IN THE SOFTWARE. + +Except as contained in this notice, the name of The Open Group shall +not be used in advertising or otherwise to promote the sale, use or +other dealings in this Software without prior written authorization +from The Open Group. + +Copyright 1987 by Digital Equipment Corporation, Maynard, Massachusetts, + + All Rights Reserved + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, +provided that the above copyright notice appear in all copies and that +both that copyright notice and this permission notice appear in +supporting documentation, and that the names of Hewlett Packard +or Digital not be +used in advertising or publicity pertaining to distribution of the +software without specific, written prior permission. + +DIGITAL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING +ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL +DIGITAL BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR +ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, +WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, +ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS +SOFTWARE. + +HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD +TO THIS SOFWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. Hewlett-Packard shall not be liable for errors +contained herein or direct, indirect, special, incidental or +consequential damages in connection with the furnishing, +performance, or use of this material. + +HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD +TO THIS SOFWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. Hewlett-Packard shall not be liable for errors +contained herein or direct, indirect, special, incidental or +consequential damages in connection with the furnishing, +performance, or use of this material. + + +This is the copyright for randr.h + +Copyright © 2000 Compaq Computer Corporation, Inc. +Copyright © 2002 Hewlett-Packard Company, Inc. +Copyright © 2006 Intel Corporation +Copyright © 2008 Red Hat, Inc. + +Permission to use, copy, modify, distribute, and sell this software and its +documentation for any purpose is hereby granted without fee, provided that +the above copyright notice appear in all copies and that both that copyright +notice and this permission notice appear in supporting documentation, and +that the name of the copyright holders not be used in advertising or +publicity pertaining to distribution of the software without specific, +written prior permission. The copyright holders make no representations +about the suitability of this software for any purpose. It is provided "as +is" without express or implied warranty. + +THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, +INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO +EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR +CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, +DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER +TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE +OF THIS SOFTWARE. + +Author: Jim Gettys, HP Labs, Hewlett-Packard, Inc. +Keith Packard, Intel Corporation + + +``` + diff --git a/jdk-1.8.0.281/jre/legal/jdk/xwd.md b/jdk-1.8.0.281/jre/legal/jdk/xwd.md new file mode 100755 index 0000000..18b026e --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/xwd.md @@ -0,0 +1,34 @@ +## XWD Utility v1.0.7 (Unix only) + +### X Windows System Image Dumping Utility License +``` + +This is the copyright for the files in src/solaris/native/sun/awt: list.h, +multiVis.h, wsutils.h, list.c, multiVis.c + +Copyright 1994 Hewlett-Packard Co. +Copyright 1996, 1998 The Open Group + +Permission to use, copy, modify, distribute, and sell this software and its +documentation for any purpose is hereby granted without fee, provided that +the above copyright notice appear in all copies and that both that +copyright notice and this permission notice appear in supporting +documentation. + +The above copyright notice and this permission notice shall be included +in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR +OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, +ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR +OTHER DEALINGS IN THE SOFTWARE. + +Except as contained in this notice, the name of The Open Group shall +not be used in advertising or otherwise to promote the sale, use or +other dealings in this Software without prior written authorization +from The Open Group. + +``` diff --git a/jdk-1.8.0.281/jre/legal/jdk/zlib.md b/jdk-1.8.0.281/jre/legal/jdk/zlib.md new file mode 100755 index 0000000..172baca --- /dev/null +++ b/jdk-1.8.0.281/jre/legal/jdk/zlib.md @@ -0,0 +1,27 @@ +## zlib v1.2.11 + +### zlib License +``` + +Copyright (C) 1995-2017 Jean-loup Gailly and Mark Adler + +This software is provided 'as-is', without any express or implied +warranty. In no event will the authors be held liable for any damages +arising from the use of this software. + +Permission is granted to anyone to use this software for any purpose, +including commercial applications, and to alter it and redistribute it +freely, subject to the following restrictions: + +1. The origin of this software must not be misrepresented; you must not + claim that you wrote the original software. If you use this software + in a product, an acknowledgment in the product documentation would be + appreciated but is not required. +2. Altered source versions must be plainly marked as such, and must not be + misrepresented as being the original software. +3. This notice may not be removed or altered from any source distribution. + +Jean-loup Gailly Mark Adler +jloup@gzip.org madler@alumni.caltech.edu + +``` diff --git a/jdk-1.8.0.281/jre/lib/amd64/jli/libjli.so b/jdk-1.8.0.281/jre/lib/amd64/jli/libjli.so new file mode 100755 index 0000000..e1ab3f1 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/jli/libjli.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/jvm.cfg b/jdk-1.8.0.281/jre/lib/amd64/jvm.cfg new file mode 100755 index 0000000..c8d3740 --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/amd64/jvm.cfg @@ -0,0 +1,35 @@ +# Copyright (c) 2003, 2013, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# List of JVMs that can be used as an option to java, javac, etc. +# Order is important -- first in this list is the default JVM. +# NOTE that this both this file and its format are UNSUPPORTED and +# WILL GO AWAY in a future release. +# +# You may also select a JVM in an arbitrary location with the +# "-XXaltjvm=" option, but that too is unsupported +# and may not be available in a future release. +# +-server KNOWN +-client IGNORE diff --git a/jdk-1.8.0.281/jre/lib/amd64/libattach.so b/jdk-1.8.0.281/jre/lib/amd64/libattach.so new file mode 100755 index 0000000..58ee005 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libattach.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-53.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-53.so new file mode 100755 index 0000000..a21dacd Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-53.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-54.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-54.so new file mode 100755 index 0000000..87b1a94 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-54.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-55.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-55.so new file mode 100755 index 0000000..fbe1630 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-55.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-56.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-56.so new file mode 100755 index 0000000..b301312 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-56.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-57.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-57.so new file mode 100755 index 0000000..d4ef65d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-57.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-56.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-56.so new file mode 100755 index 0000000..d109b55 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-56.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-57.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-57.so new file mode 100755 index 0000000..3345653 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-57.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-58.so b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-58.so new file mode 100755 index 0000000..8b06796 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libavplugin-ffmpeg-58.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libawt.so b/jdk-1.8.0.281/jre/lib/amd64/libawt.so new file mode 100755 index 0000000..9a34526 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libawt.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libawt_headless.so b/jdk-1.8.0.281/jre/lib/amd64/libawt_headless.so new file mode 100755 index 0000000..d2c90c0 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libawt_headless.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libawt_xawt.so b/jdk-1.8.0.281/jre/lib/amd64/libawt_xawt.so new file mode 100755 index 0000000..b6d7442 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libawt_xawt.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libbci.so b/jdk-1.8.0.281/jre/lib/amd64/libbci.so new file mode 100755 index 0000000..926f233 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libbci.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libdcpr.so b/jdk-1.8.0.281/jre/lib/amd64/libdcpr.so new file mode 100755 index 0000000..c540289 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libdcpr.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libdecora_sse.so b/jdk-1.8.0.281/jre/lib/amd64/libdecora_sse.so new file mode 100755 index 0000000..6566ff0 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libdecora_sse.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libdeploy.so b/jdk-1.8.0.281/jre/lib/amd64/libdeploy.so new file mode 100755 index 0000000..a92f3d0 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libdeploy.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libdt_socket.so b/jdk-1.8.0.281/jre/lib/amd64/libdt_socket.so new file mode 100755 index 0000000..9fd8fb2 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libdt_socket.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libfontmanager.so b/jdk-1.8.0.281/jre/lib/amd64/libfontmanager.so new file mode 100755 index 0000000..e60fdec Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libfontmanager.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libfxplugins.so b/jdk-1.8.0.281/jre/lib/amd64/libfxplugins.so new file mode 100755 index 0000000..4bba755 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libfxplugins.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libglass.so b/jdk-1.8.0.281/jre/lib/amd64/libglass.so new file mode 100755 index 0000000..c450491 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libglass.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libglassgtk2.so b/jdk-1.8.0.281/jre/lib/amd64/libglassgtk2.so new file mode 100755 index 0000000..1e59a9a Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libglassgtk2.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libglassgtk3.so b/jdk-1.8.0.281/jre/lib/amd64/libglassgtk3.so new file mode 100755 index 0000000..3354462 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libglassgtk3.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libglib-lite.so b/jdk-1.8.0.281/jre/lib/amd64/libglib-lite.so new file mode 100755 index 0000000..c6cd461 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libglib-lite.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libgstreamer-lite.so b/jdk-1.8.0.281/jre/lib/amd64/libgstreamer-lite.so new file mode 100755 index 0000000..fd1a0bc Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libgstreamer-lite.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libhprof.so b/jdk-1.8.0.281/jre/lib/amd64/libhprof.so new file mode 100755 index 0000000..c41c69d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libhprof.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libinstrument.so b/jdk-1.8.0.281/jre/lib/amd64/libinstrument.so new file mode 100755 index 0000000..e84d98d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libinstrument.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libj2gss.so b/jdk-1.8.0.281/jre/lib/amd64/libj2gss.so new file mode 100755 index 0000000..662fb96 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libj2gss.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libj2pcsc.so b/jdk-1.8.0.281/jre/lib/amd64/libj2pcsc.so new file mode 100755 index 0000000..baa66c1 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libj2pcsc.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libj2pkcs11.so b/jdk-1.8.0.281/jre/lib/amd64/libj2pkcs11.so new file mode 100755 index 0000000..ac1ea17 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libj2pkcs11.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjaas_unix.so b/jdk-1.8.0.281/jre/lib/amd64/libjaas_unix.so new file mode 100755 index 0000000..71587fa Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjaas_unix.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjava.so b/jdk-1.8.0.281/jre/lib/amd64/libjava.so new file mode 100755 index 0000000..dbae06e Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjava.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjava_crw_demo.so b/jdk-1.8.0.281/jre/lib/amd64/libjava_crw_demo.so new file mode 100755 index 0000000..bc98943 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjava_crw_demo.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font.so b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font.so new file mode 100755 index 0000000..7ce28ff Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font_freetype.so b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font_freetype.so new file mode 100755 index 0000000..5f029cc Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font_freetype.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font_pango.so b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font_pango.so new file mode 100755 index 0000000..5dcb4d3 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_font_pango.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjavafx_iio.so b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_iio.so new file mode 100755 index 0000000..84e8bfd Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjavafx_iio.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjawt.so b/jdk-1.8.0.281/jre/lib/amd64/libjawt.so new file mode 100755 index 0000000..ca917e4 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjawt.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjdwp.so b/jdk-1.8.0.281/jre/lib/amd64/libjdwp.so new file mode 100755 index 0000000..5c5e353 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjdwp.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjfr.so b/jdk-1.8.0.281/jre/lib/amd64/libjfr.so new file mode 100755 index 0000000..6483670 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjfr.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjfxmedia.so b/jdk-1.8.0.281/jre/lib/amd64/libjfxmedia.so new file mode 100755 index 0000000..9cdc351 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjfxmedia.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjfxwebkit.so b/jdk-1.8.0.281/jre/lib/amd64/libjfxwebkit.so new file mode 100755 index 0000000..d04bad3 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjfxwebkit.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjpeg.so b/jdk-1.8.0.281/jre/lib/amd64/libjpeg.so new file mode 100755 index 0000000..a819510 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjpeg.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjsdt.so b/jdk-1.8.0.281/jre/lib/amd64/libjsdt.so new file mode 100755 index 0000000..b600f0d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjsdt.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjsig.so b/jdk-1.8.0.281/jre/lib/amd64/libjsig.so new file mode 100755 index 0000000..597c130 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjsig.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjsound.so b/jdk-1.8.0.281/jre/lib/amd64/libjsound.so new file mode 100755 index 0000000..9c6ab02 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjsound.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libjsoundalsa.so b/jdk-1.8.0.281/jre/lib/amd64/libjsoundalsa.so new file mode 100755 index 0000000..20f805f Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libjsoundalsa.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/liblcms.so b/jdk-1.8.0.281/jre/lib/amd64/liblcms.so new file mode 100755 index 0000000..955a9a5 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/liblcms.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libmanagement.so b/jdk-1.8.0.281/jre/lib/amd64/libmanagement.so new file mode 100755 index 0000000..77637db Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libmanagement.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libmlib_image.so b/jdk-1.8.0.281/jre/lib/amd64/libmlib_image.so new file mode 100755 index 0000000..e568f89 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libmlib_image.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libnet.so b/jdk-1.8.0.281/jre/lib/amd64/libnet.so new file mode 100755 index 0000000..b927efd Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libnet.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libnio.so b/jdk-1.8.0.281/jre/lib/amd64/libnio.so new file mode 100755 index 0000000..9462283 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libnio.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libnpt.so b/jdk-1.8.0.281/jre/lib/amd64/libnpt.so new file mode 100755 index 0000000..5e06c24 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libnpt.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libprism_common.so b/jdk-1.8.0.281/jre/lib/amd64/libprism_common.so new file mode 100755 index 0000000..a655b6d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libprism_common.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libprism_es2.so b/jdk-1.8.0.281/jre/lib/amd64/libprism_es2.so new file mode 100755 index 0000000..59915ad Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libprism_es2.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libprism_sw.so b/jdk-1.8.0.281/jre/lib/amd64/libprism_sw.so new file mode 100755 index 0000000..ced447d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libprism_sw.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libresource.so b/jdk-1.8.0.281/jre/lib/amd64/libresource.so new file mode 100755 index 0000000..10f07dc Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libresource.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libsaproc.so b/jdk-1.8.0.281/jre/lib/amd64/libsaproc.so new file mode 100755 index 0000000..3ed66b2 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libsaproc.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libsctp.so b/jdk-1.8.0.281/jre/lib/amd64/libsctp.so new file mode 100755 index 0000000..e0464a3 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libsctp.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libsplashscreen.so b/jdk-1.8.0.281/jre/lib/amd64/libsplashscreen.so new file mode 100755 index 0000000..b93180c Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libsplashscreen.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libsunec.so b/jdk-1.8.0.281/jre/lib/amd64/libsunec.so new file mode 100755 index 0000000..5c60502 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libsunec.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libt2k.so b/jdk-1.8.0.281/jre/lib/amd64/libt2k.so new file mode 100755 index 0000000..87fc20f Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libt2k.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libunpack.so b/jdk-1.8.0.281/jre/lib/amd64/libunpack.so new file mode 100755 index 0000000..bb6fda4 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libunpack.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libverify.so b/jdk-1.8.0.281/jre/lib/amd64/libverify.so new file mode 100755 index 0000000..47afcda Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libverify.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/libzip.so b/jdk-1.8.0.281/jre/lib/amd64/libzip.so new file mode 100755 index 0000000..ed8e47d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/libzip.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/server/Xusage.txt b/jdk-1.8.0.281/jre/lib/amd64/server/Xusage.txt new file mode 100755 index 0000000..d24ada9 --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/amd64/server/Xusage.txt @@ -0,0 +1,24 @@ + -Xmixed mixed mode execution (default) + -Xint interpreted mode execution only + -Xbootclasspath: + set search path for bootstrap classes and resources + -Xbootclasspath/a: + append to end of bootstrap class path + -Xbootclasspath/p: + prepend in front of bootstrap class path + -Xnoclassgc disable class garbage collection + -Xincgc enable incremental garbage collection + -Xloggc: log GC status to a file with time stamps + -Xbatch disable background compilation + -Xms set initial Java heap size + -Xmx set maximum Java heap size + -Xss set java thread stack size + -Xprof output cpu profiling data + -Xfuture enable strictest checks, anticipating future default + -Xrs reduce use of OS signals by Java/VM (see documentation) + -Xcheck:jni perform additional checks for JNI functions + -Xshare:off do not attempt to use shared class data + -Xshare:auto use shared class data if possible (default) + -Xshare:on require using shared class data, otherwise fail. + +The -X options are non-standard and subject to change without notice. diff --git a/jdk-1.8.0.281/jre/lib/amd64/server/libjsig.so b/jdk-1.8.0.281/jre/lib/amd64/server/libjsig.so new file mode 100755 index 0000000..597c130 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/server/libjsig.so differ diff --git a/jdk-1.8.0.281/jre/lib/amd64/server/libjvm.so b/jdk-1.8.0.281/jre/lib/amd64/server/libjvm.so new file mode 100755 index 0000000..4ada4c8 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/amd64/server/libjvm.so differ diff --git a/jdk-1.8.0.281/jre/lib/calendars.properties b/jdk-1.8.0.281/jre/lib/calendars.properties new file mode 100755 index 0000000..6bf523f --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/calendars.properties @@ -0,0 +1,62 @@ +# Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# +# + +# +# Japanese imperial calendar +# +# Meiji since 1868-01-01 00:00:00 local time (Gregorian) +# Taisho since 1912-07-30 00:00:00 local time (Gregorian) +# Showa since 1926-12-25 00:00:00 local time (Gregorian) +# Heisei since 1989-01-08 00:00:00 local time (Gregorian) +# Reiwa since 2019-05-01 00:00:00 local time (Gregorian) +calendar.japanese.type: LocalGregorianCalendar +calendar.japanese.eras: \ + name=Meiji,abbr=M,since=-3218832000000; \ + name=Taisho,abbr=T,since=-1812153600000; \ + name=Showa,abbr=S,since=-1357603200000; \ + name=Heisei,abbr=H,since=600220800000; \ + name=Reiwa,abbr=R,since=1556668800000 + +# +# Taiwanese calendar +# Minguo since 1911-01-01 00:00:00 local time (Gregorian) +calendar.taiwanese.type: LocalGregorianCalendar +calendar.taiwanese.eras: \ + name=MinGuo,since=-1830384000000 + +# +# Thai Buddhist calendar +# Buddhist Era since -542-01-01 00:00:00 local time (Gregorian) +calendar.thai-buddhist.type: LocalGregorianCalendar +calendar.thai-buddhist.eras: \ + name=BuddhistEra,abbr=B.E.,since=-79302585600000 +calendar.thai-buddhist.year-boundary: \ + day1=4-1,since=-79302585600000; \ + day1=1-1,since=-915148800000 + +# +# Hijrah calendars +# +calendar.hijrah.Hijrah-umalqura: hijrah-config-umalqura.properties +calendar.hijrah.Hijrah-umalqura.type: islamic-umalqura diff --git a/jdk-1.8.0.281/jre/lib/charsets.jar b/jdk-1.8.0.281/jre/lib/charsets.jar new file mode 100755 index 0000000..b67d46e Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/charsets.jar differ diff --git a/jdk-1.8.0.281/jre/lib/classlist b/jdk-1.8.0.281/jre/lib/classlist new file mode 100755 index 0000000..2a3915c --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/classlist @@ -0,0 +1,2559 @@ +java/lang/Object +java/lang/String +java/io/Serializable +java/lang/Comparable +java/lang/CharSequence +java/lang/Class +java/lang/reflect/GenericDeclaration +java/lang/reflect/AnnotatedElement +java/lang/reflect/Type +java/lang/Cloneable +java/lang/ClassLoader +java/lang/System +java/lang/Throwable +java/lang/Error +java/lang/ThreadDeath +java/lang/Exception +java/lang/RuntimeException +java/lang/SecurityManager +java/security/ProtectionDomain +java/security/AccessControlContext +java/security/SecureClassLoader +java/lang/ClassNotFoundException +java/lang/ReflectiveOperationException +java/lang/NoClassDefFoundError +java/lang/LinkageError +java/lang/ClassCastException +java/lang/ArrayStoreException +java/lang/VirtualMachineError +java/lang/OutOfMemoryError +java/lang/StackOverflowError +java/lang/IllegalMonitorStateException +java/lang/ref/Reference +java/lang/ref/SoftReference +java/lang/ref/WeakReference +java/lang/ref/FinalReference +java/lang/ref/PhantomReference +sun/misc/Cleaner +java/lang/ref/Finalizer +java/lang/Thread +java/lang/Runnable +java/lang/ThreadGroup +java/lang/Thread$UncaughtExceptionHandler +java/util/Properties +java/util/Hashtable +java/util/Map +java/util/Dictionary +java/lang/reflect/AccessibleObject +java/lang/reflect/Field +java/lang/reflect/Member +java/lang/reflect/Parameter +java/lang/reflect/Method +java/lang/reflect/Executable +java/lang/reflect/Constructor +sun/reflect/MagicAccessorImpl +sun/reflect/MethodAccessorImpl +sun/reflect/MethodAccessor +sun/reflect/ConstructorAccessorImpl +sun/reflect/ConstructorAccessor +sun/reflect/DelegatingClassLoader +sun/reflect/ConstantPool +sun/reflect/UnsafeStaticFieldAccessorImpl +sun/reflect/UnsafeFieldAccessorImpl +sun/reflect/FieldAccessorImpl +sun/reflect/FieldAccessor +sun/reflect/CallerSensitive +java/lang/annotation/Annotation +java/lang/invoke/DirectMethodHandle +java/lang/invoke/MethodHandle +java/lang/invoke/MemberName +java/lang/invoke/MethodHandleNatives +java/lang/invoke/LambdaForm +java/lang/invoke/MethodType +java/lang/BootstrapMethodError +java/lang/invoke/CallSite +java/lang/invoke/ConstantCallSite +java/lang/invoke/MutableCallSite +java/lang/invoke/VolatileCallSite +java/lang/StringBuffer +java/lang/AbstractStringBuilder +java/lang/Appendable +java/lang/StringBuilder +sun/misc/Unsafe +java/io/ByteArrayInputStream +java/io/InputStream +java/io/Closeable +java/lang/AutoCloseable +java/io/File +java/net/URLClassLoader +java/net/URL +java/util/jar/Manifest +sun/misc/Launcher +sun/misc/Launcher$AppClassLoader +sun/misc/Launcher$ExtClassLoader +java/security/CodeSource +java/lang/StackTraceElement +java/nio/Buffer +java/lang/Boolean +java/lang/Character +java/lang/Float +java/lang/Number +java/lang/Double +java/lang/Byte +java/lang/Short +java/lang/Integer +java/lang/Long +java/lang/NullPointerException +java/lang/ArithmeticException +java/io/ObjectStreamField +java/lang/String$CaseInsensitiveComparator +java/util/Comparator +java/lang/RuntimePermission +java/security/BasicPermission +java/security/Permission +java/security/Guard +java/security/AccessController +java/lang/reflect/ReflectPermission +sun/reflect/ReflectionFactory$GetReflectionFactoryAction +java/security/PrivilegedAction +java/security/cert/Certificate +java/util/Vector +java/util/List +java/util/Collection +java/lang/Iterable +java/util/RandomAccess +java/util/AbstractList +java/util/AbstractCollection +java/util/Stack +sun/reflect/ReflectionFactory +java/lang/ref/Reference$Lock +java/lang/ref/Reference$ReferenceHandler +java/lang/ref/ReferenceQueue +java/lang/ref/ReferenceQueue$Null +java/lang/ref/ReferenceQueue$Lock +java/lang/ref/Finalizer$FinalizerThread +sun/misc/VM +java/util/Hashtable$Entry +java/util/Map$Entry +java/lang/Math +java/nio/charset/Charset +sun/nio/cs/StandardCharsets +sun/nio/cs/FastCharsetProvider +java/nio/charset/spi/CharsetProvider +sun/nio/cs/StandardCharsets$Aliases +sun/util/PreHashedMap +java/util/AbstractMap +sun/nio/cs/StandardCharsets$Classes +sun/nio/cs/StandardCharsets$Cache +java/lang/ThreadLocal +java/util/concurrent/atomic/AtomicInteger +java/lang/NoSuchMethodError +java/lang/IncompatibleClassChangeError +java/util/ArrayList +java/util/Collections +java/util/Collections$EmptySet +java/util/AbstractSet +java/util/Set +java/util/Collections$EmptyList +java/util/Collections$EmptyMap +java/util/Collections$UnmodifiableRandomAccessList +java/util/Collections$UnmodifiableList +java/util/Collections$UnmodifiableCollection +sun/reflect/Reflection +java/util/HashMap +java/util/HashMap$Node +java/lang/Class$3 +java/lang/Class$ReflectionData +java/lang/Class$Atomic +sun/reflect/generics/repository/ClassRepository +sun/reflect/generics/repository/GenericDeclRepository +sun/reflect/generics/repository/AbstractRepository +java/lang/Class$AnnotationData +sun/reflect/annotation/AnnotationType +java/lang/ClassValue$ClassValueMap +java/util/WeakHashMap +java/lang/reflect/Modifier +java/lang/reflect/ReflectAccess +sun/reflect/LangReflectAccess +java/util/Arrays +sun/nio/cs/UTF_8 +sun/nio/cs/Unicode +sun/nio/cs/HistoricallyNamedCharset +java/lang/Class$1 +sun/reflect/ReflectionFactory$1 +sun/reflect/NativeConstructorAccessorImpl +sun/reflect/DelegatingConstructorAccessorImpl +java/lang/StringCoding +java/lang/ThreadLocal$ThreadLocalMap +java/lang/ThreadLocal$ThreadLocalMap$Entry +java/lang/StringCoding$StringDecoder +sun/nio/cs/UTF_8$Decoder +sun/nio/cs/ArrayDecoder +java/nio/charset/CharsetDecoder +java/nio/charset/CodingErrorAction +java/util/Hashtable$EntrySet +java/util/Collections$SynchronizedSet +java/util/Collections$SynchronizedCollection +java/util/Objects +java/util/Hashtable$Enumerator +java/util/Enumeration +java/util/Iterator +java/lang/Runtime +sun/misc/Version +java/io/FileInputStream +java/io/FileDescriptor +java/io/FileDescriptor$1 +sun/misc/JavaIOFileDescriptorAccess +sun/misc/SharedSecrets +java/io/FileOutputStream +java/io/OutputStream +java/io/Flushable +java/io/BufferedInputStream +java/io/FilterInputStream +java/util/concurrent/atomic/AtomicReferenceFieldUpdater +java/util/concurrent/atomic/AtomicReferenceFieldUpdater$AtomicReferenceFieldUpdaterImpl +java/util/concurrent/atomic/AtomicReferenceFieldUpdater$AtomicReferenceFieldUpdaterImpl$1 +java/security/PrivilegedExceptionAction +sun/reflect/misc/ReflectUtil +java/io/PrintStream +java/io/FilterOutputStream +java/io/BufferedOutputStream +java/io/OutputStreamWriter +java/io/Writer +sun/nio/cs/StreamEncoder +sun/security/action/GetPropertyAction +sun/nio/cs/UTF_8$Encoder +sun/nio/cs/ArrayEncoder +java/nio/charset/CharsetEncoder +java/nio/ByteBuffer +java/nio/HeapByteBuffer +java/nio/Bits +java/nio/ByteOrder +java/nio/Bits$1 +sun/misc/JavaNioAccess +java/io/BufferedWriter +java/io/DefaultFileSystem +java/io/UnixFileSystem +java/io/FileSystem +java/io/ExpiringCache +java/io/ExpiringCache$1 +java/util/LinkedHashMap +java/io/File$PathStatus +java/lang/Enum +java/nio/file/Path +java/nio/file/Watchable +java/lang/StringCoding$StringEncoder +java/lang/ClassLoader$3 +java/io/ExpiringCache$Entry +java/util/LinkedHashMap$Entry +java/lang/ClassLoader$NativeLibrary +java/lang/Terminator +java/lang/Terminator$1 +sun/misc/SignalHandler +sun/misc/Signal +sun/misc/NativeSignalHandler +java/lang/Integer$IntegerCache +sun/misc/OSEnvironment +java/lang/System$2 +sun/misc/JavaLangAccess +java/lang/IllegalArgumentException +java/lang/Compiler +java/lang/Compiler$1 +sun/misc/Launcher$Factory +java/net/URLStreamHandlerFactory +sun/security/util/Debug +java/lang/ClassLoader$ParallelLoaders +java/util/WeakHashMap$Entry +java/util/Collections$SetFromMap +java/util/WeakHashMap$KeySet +java/net/URLClassLoader$7 +sun/misc/JavaNetAccess +java/util/StringTokenizer +sun/misc/Launcher$ExtClassLoader$1 +sun/misc/MetaIndex +java/io/BufferedReader +java/io/Reader +java/lang/Readable +java/io/FileReader +java/io/InputStreamReader +sun/nio/cs/StreamDecoder +java/nio/CharBuffer +java/nio/HeapCharBuffer +java/nio/charset/CoderResult +java/nio/charset/CoderResult$1 +java/nio/charset/CoderResult$Cache +java/nio/charset/CoderResult$2 +java/lang/reflect/Array +java/io/FileInputStream$1 +sun/net/www/ParseUtil +java/util/BitSet +java/util/Locale +java/util/Locale$Cache +sun/util/locale/LocaleObjectCache +java/util/concurrent/ConcurrentHashMap +java/util/concurrent/ConcurrentMap +java/util/concurrent/ConcurrentHashMap$Segment +java/util/concurrent/locks/ReentrantLock +java/util/concurrent/locks/Lock +java/util/concurrent/ConcurrentHashMap$Node +java/util/concurrent/ConcurrentHashMap$CounterCell +java/util/concurrent/ConcurrentHashMap$KeySetView +java/util/concurrent/ConcurrentHashMap$CollectionView +java/util/concurrent/ConcurrentHashMap$ValuesView +java/util/concurrent/ConcurrentHashMap$EntrySetView +sun/util/locale/BaseLocale +sun/util/locale/BaseLocale$Cache +sun/util/locale/BaseLocale$Key +sun/util/locale/LocaleObjectCache$CacheEntry +java/util/Locale$LocaleKey +sun/util/locale/LocaleUtils +java/lang/CharacterData +java/lang/CharacterDataLatin1 +java/net/Parts +sun/net/www/protocol/file/Handler +java/net/URLStreamHandler +java/util/HashMap$TreeNode +java/security/ProtectionDomain$JavaSecurityAccessImpl +sun/misc/JavaSecurityAccess +java/security/ProtectionDomain$2 +sun/misc/JavaSecurityProtectionDomainAccess +java/security/ProtectionDomain$Key +java/security/Principal +java/util/HashSet +sun/misc/URLClassPath +sun/net/www/protocol/jar/Handler +sun/misc/Launcher$AppClassLoader$1 +java/lang/SystemClassLoaderAction +java/lang/invoke/MethodHandleImpl +java/lang/invoke/MethodHandleImpl$1 +java/lang/invoke/MethodHandleImpl$2 +java/util/function/Function +java/lang/invoke/MethodHandleImpl$3 +java/lang/invoke/MethodHandleImpl$4 +java/lang/ClassValue +java/lang/ClassValue$Entry +java/lang/ClassValue$Identity +java/lang/ClassValue$Version +java/lang/invoke/MemberName$Factory +java/lang/invoke/MethodHandleStatics +java/lang/invoke/MethodHandleStatics$1 +sun/misc/PostVMInitHook +sun/usagetracker/UsageTrackerClient +java/util/concurrent/atomic/AtomicBoolean +sun/usagetracker/UsageTrackerClient$1 +sun/usagetracker/UsageTrackerClient$4 +sun/usagetracker/UsageTrackerClient$3 +java/io/FileOutputStream$1 +sun/launcher/LauncherHelper +java/net/URLClassLoader$1 +sun/net/util/URLUtil +sun/misc/URLClassPath$3 +sun/misc/URLClassPath$JarLoader +sun/misc/URLClassPath$Loader +java/util/zip/ZipFile +java/util/zip/ZipConstants +java/util/zip/ZipFile$1 +sun/misc/JavaUtilZipFileAccess +sun/misc/URLClassPath$JarLoader$1 +sun/misc/FileURLMapper +java/util/jar/JarFile +java/util/jar/JavaUtilJarAccessImpl +sun/misc/JavaUtilJarAccess +java/nio/charset/StandardCharsets +sun/nio/cs/US_ASCII +sun/nio/cs/ISO_8859_1 +sun/nio/cs/UTF_16BE +sun/nio/cs/UTF_16LE +sun/nio/cs/UTF_16 +java/util/ArrayDeque +java/util/Deque +java/util/Queue +java/util/zip/ZipCoder +sun/misc/PerfCounter +sun/misc/Perf$GetPerfAction +sun/misc/Perf +sun/misc/PerfCounter$CoreCounters +sun/nio/ch/DirectBuffer +java/nio/DirectByteBuffer +java/nio/MappedByteBuffer +java/nio/DirectLongBufferU +java/nio/LongBuffer +sun/misc/JarIndex +sun/misc/ExtensionDependency +java/util/zip/ZipEntry +java/util/jar/JarFile$JarFileEntry +java/util/jar/JarEntry +java/util/zip/ZipFile$ZipFileInputStream +java/util/zip/Inflater +java/util/zip/ZStreamRef +java/util/zip/ZipFile$ZipFileInflaterInputStream +java/util/zip/InflaterInputStream +sun/misc/IOUtils +sun/misc/URLClassPath$JarLoader$2 +sun/misc/Resource +sun/nio/ByteBuffered +java/security/Permissions +java/security/PermissionCollection +sun/net/www/protocol/file/FileURLConnection +sun/net/www/URLConnection +java/net/URLConnection +sun/net/www/MessageHeader +java/io/FilePermission +java/io/FilePermission$1 +java/io/FilePermissionCollection +java/security/AllPermission +java/security/UnresolvedPermission +java/security/BasicPermissionCollection +javax/swing/JLabel +javax/swing/SwingConstants +javax/accessibility/Accessible +javax/swing/JComponent +javax/swing/TransferHandler$HasGetTransferHandler +java/awt/Container +java/awt/Component +java/awt/image/ImageObserver +java/awt/MenuContainer +sun/launcher/LauncherHelper$FXHelper +java/lang/Class$MethodArray +java/lang/InterruptedException +javax/swing/JFrame +javax/swing/WindowConstants +javax/swing/RootPaneContainer +java/awt/Frame +java/awt/Window +java/util/concurrent/ConcurrentHashMap$ForwardingNode +java/awt/Graphics +java/lang/Void +sun/util/logging/PlatformLogger +sun/util/logging/PlatformLogger$Level +sun/util/logging/PlatformLogger$1 +sun/util/logging/PlatformLogger$DefaultLoggerProxy +sun/util/logging/PlatformLogger$LoggerProxy +sun/util/logging/PlatformLogger$JavaLoggerProxy +sun/util/logging/LoggingSupport +sun/util/logging/LoggingSupport$1 +java/util/logging/LoggingProxyImpl +sun/util/logging/LoggingProxy +sun/reflect/UnsafeFieldAccessorFactory +sun/reflect/UnsafeQualifiedStaticObjectFieldAccessorImpl +sun/reflect/UnsafeQualifiedStaticFieldAccessorImpl +java/util/HashMap$EntrySet +java/util/HashMap$EntryIterator +java/util/HashMap$HashIterator +sun/util/logging/LoggingSupport$2 +java/util/Date +sun/util/calendar/CalendarSystem +sun/util/calendar/Gregorian +sun/util/calendar/BaseCalendar +sun/util/calendar/AbstractCalendar +java/awt/Component$AWTTreeLock +java/awt/Toolkit +java/awt/Toolkit$4 +sun/awt/AWTAccessor$ToolkitAccessor +sun/awt/AWTAccessor +java/awt/Toolkit$5 +sun/util/CoreResourceBundleControl +java/util/ResourceBundle$Control +java/util/Arrays$ArrayList +java/util/ResourceBundle$Control$CandidateListCache +java/util/ResourceBundle +java/util/ResourceBundle$1 +java/util/spi/ResourceBundleControlProvider +java/util/ServiceLoader +java/util/ServiceLoader$LazyIterator +java/util/ServiceLoader$1 +java/util/LinkedHashMap$LinkedEntrySet +java/util/LinkedHashMap$LinkedEntryIterator +java/util/LinkedHashMap$LinkedHashIterator +sun/misc/Launcher$BootClassPathHolder +sun/misc/Launcher$BootClassPathHolder$1 +sun/misc/URLClassPath$2 +java/lang/ClassLoader$2 +sun/misc/URLClassPath$1 +java/net/URLClassLoader$3 +sun/misc/CompoundEnumeration +java/io/FileNotFoundException +java/io/IOException +java/security/PrivilegedActionException +java/net/URLClassLoader$3$1 +java/util/ResourceBundle$RBClassLoader +java/util/ResourceBundle$RBClassLoader$1 +java/util/ResourceBundle$CacheKey +java/util/ResourceBundle$LoaderReference +java/util/ResourceBundle$CacheKeyReference +java/util/ResourceBundle$SingleFormatControl +java/util/LinkedList +java/util/AbstractSequentialList +java/util/LinkedList$Node +sun/awt/resources/awt +java/util/ListResourceBundle +java/awt/Toolkit$3 +java/awt/GraphicsEnvironment +java/lang/invoke/LambdaMetafactory +java/lang/invoke/MethodHandles$Lookup +java/lang/invoke/MethodType$ConcurrentWeakInternSet +java/lang/invoke/MethodTypeForm +java/lang/invoke/Invokers +java/lang/invoke/MethodType$ConcurrentWeakInternSet$WeakEntry +java/lang/invoke/MethodHandles +sun/invoke/util/Wrapper +sun/invoke/util/Wrapper$Format +java/lang/Byte$ByteCache +java/lang/Short$ShortCache +java/lang/Character$CharacterCache +java/lang/Long$LongCache +sun/invoke/util/VerifyAccess +sun/invoke/util/ValueConversions +java/lang/NoSuchMethodException +java/lang/invoke/LambdaForm$BasicType +java/lang/invoke/LambdaForm$Name +java/lang/invoke/LambdaForm$NamedFunction +java/lang/invoke/SimpleMethodHandle +java/lang/invoke/BoundMethodHandle +java/lang/invoke/BoundMethodHandle$SpeciesData +java/lang/invoke/BoundMethodHandle$Factory +java/lang/invoke/BoundMethodHandle$Species_L +java/util/HashMap$Values +java/util/HashMap$ValueIterator +sun/invoke/util/BytecodeDescriptor +java/lang/invoke/DirectMethodHandle$Lazy +java/lang/InstantiationException +java/util/Collections$UnmodifiableCollection$1 +java/util/AbstractList$Itr +java/lang/invoke/InvokerBytecodeGenerator +jdk/internal/org/objectweb/asm/ClassWriter +jdk/internal/org/objectweb/asm/ClassVisitor +jdk/internal/org/objectweb/asm/ByteVector +jdk/internal/org/objectweb/asm/Item +jdk/internal/org/objectweb/asm/MethodWriter +jdk/internal/org/objectweb/asm/MethodVisitor +jdk/internal/org/objectweb/asm/Type +jdk/internal/org/objectweb/asm/Label +jdk/internal/org/objectweb/asm/Frame +jdk/internal/org/objectweb/asm/AnnotationWriter +jdk/internal/org/objectweb/asm/AnnotationVisitor +java/lang/invoke/MethodHandleImpl$Intrinsic +java/lang/invoke/InvokerBytecodeGenerator$2 +sun/invoke/util/VerifyType +sun/invoke/empty/Empty +java/lang/NoSuchFieldException +java/lang/invoke/InvokerBytecodeGenerator$CpPatch +java/lang/invoke/DirectMethodHandle$Accessor +java/util/ArrayList$Itr +java/util/RandomAccessSubList +java/util/SubList +java/util/SubList$1 +java/util/ListIterator +java/util/AbstractList$ListItr +java/lang/invoke/MethodHandleImpl$AsVarargsCollector +java/lang/invoke/DelegatingMethodHandle +java/lang/invoke/WrongMethodTypeException +java/lang/invoke/MethodHandleImpl$Lazy +java/lang/invoke/MethodHandleImpl$IntrinsicMethodHandle +java/lang/NoSuchFieldError +java/lang/IllegalAccessException +java/lang/invoke/LambdaFormEditor +java/lang/invoke/LambdaFormEditor$Transform$Kind +java/lang/invoke/LambdaFormEditor$Transform +java/lang/invoke/LambdaFormBuffer +jdk/internal/org/objectweb/asm/FieldWriter +jdk/internal/org/objectweb/asm/FieldVisitor +java/lang/invoke/InnerClassLambdaMetafactory +java/lang/invoke/AbstractValidatingLambdaMetafactory +java/util/PropertyPermission +java/security/AccessController$1 +sun/security/util/SecurityConstants +java/net/NetPermission +java/security/SecurityPermission +java/net/SocketPermission +sun/security/action/GetBooleanAction +java/security/AllPermissionCollection +java/lang/invoke/InfoFromMemberName +java/lang/invoke/MethodHandleInfo +java/lang/invoke/InnerClassLambdaMetafactory$ForwardingMethodGenerator +java/lang/invoke/TypeConvertingMethodAdapter +java/lang/invoke/InnerClassLambdaMetafactory$1 +java/lang/ProcessEnvironment +java/lang/ProcessEnvironment$Variable +java/lang/ProcessEnvironment$ExternalData +java/lang/ProcessEnvironment$Value +java/lang/ProcessEnvironment$StringEnvironment +java/util/Collections$UnmodifiableMap +java/awt/Toolkit$1 +java/awt/event/KeyEvent +java/awt/event/InputEvent +java/awt/event/ComponentEvent +java/awt/AWTEvent +java/util/EventObject +java/awt/AWTEvent$1 +sun/awt/AWTAccessor$AWTEventAccessor +java/awt/event/NativeLibLoader +java/awt/event/NativeLibLoader$1 +java/awt/event/InputEvent$1 +sun/awt/AWTAccessor$InputEventAccessor +java/awt/event/KeyEvent$1 +sun/awt/AWTAccessor$KeyEventAccessor +java/awt/Component$1 +sun/awt/AWTAccessor$ComponentAccessor +java/awt/Component$DummyRequestFocusController +sun/awt/RequestFocusController +java/awt/LayoutManager +java/awt/LightweightDispatcher +java/awt/event/AWTEventListener +java/util/EventListener +java/awt/Dimension +java/awt/geom/Dimension2D +java/awt/Container$1 +sun/awt/AWTAccessor$ContainerAccessor +javax/swing/JComponent$1 +java/awt/ComponentOrientation +java/awt/Component$3 +sun/awt/AppContext +java/util/IdentityHashMap +java/util/Collections$SynchronizedMap +sun/awt/AppContext$GetAppContextLock +sun/awt/AppContext$6 +sun/misc/JavaAWTAccess +sun/awt/AppContext$3 +sun/awt/AppContext$2 +sun/awt/SunToolkit +sun/awt/WindowClosingSupport +sun/awt/WindowClosingListener +sun/awt/ComponentFactory +sun/awt/InputMethodSupport +sun/awt/KeyboardFocusManagerPeerProvider +java/util/concurrent/locks/ReentrantLock$NonfairSync +java/util/concurrent/locks/ReentrantLock$Sync +java/util/concurrent/locks/AbstractQueuedSynchronizer +java/util/concurrent/locks/AbstractOwnableSynchronizer +java/util/concurrent/locks/AbstractQueuedSynchronizer$Node +java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject +java/util/concurrent/locks/Condition +sun/misc/SoftCache +sun/awt/AppContext$State +sun/awt/AppContext$1 +java/awt/EventQueue +java/awt/EventQueue$1 +java/awt/EventQueue$2 +sun/awt/AWTAccessor$EventQueueAccessor +java/awt/Queue +sun/awt/MostRecentKeyValue +sun/awt/PostEventQueue +javax/swing/event/EventListenerList +javax/swing/SwingUtilities +javax/swing/RepaintManager +javax/swing/RepaintManager$DisplayChangedHandler +sun/awt/DisplayChangedListener +javax/swing/RepaintManager$1 +sun/swing/SwingAccessor$RepaintManagerAccessor +sun/swing/SwingAccessor +sun/awt/X11GraphicsEnvironment +sun/java2d/SunGraphicsEnvironment +sun/awt/X11GraphicsEnvironment$1 +sun/awt/X11/XErrorHandlerUtil +sun/awt/X11/XlibWrapper +sun/java2d/UnixSurfaceManagerFactory +sun/java2d/SurfaceManagerFactory +sun/awt/SunDisplayChanger +sun/java2d/SunGraphicsEnvironment$1 +sun/misc/FloatingDecimal +sun/misc/FloatingDecimal$ExceptionalBinaryToASCIIBuffer +sun/misc/FloatingDecimal$BinaryToASCIIConverter +sun/misc/FloatingDecimal$BinaryToASCIIBuffer +sun/misc/FloatingDecimal$1 +sun/misc/FloatingDecimal$PreparedASCIIToBinaryBuffer +sun/misc/FloatingDecimal$ASCIIToBinaryConverter +java/lang/NumberFormatException +java/lang/StringIndexOutOfBoundsException +java/lang/IndexOutOfBoundsException +java/awt/Font +java/awt/Font$FontAccessImpl +sun/font/FontAccess +java/awt/geom/AffineTransform +sun/font/AttributeValues +sun/font/EAttribute +java/text/AttributedCharacterIterator$Attribute +java/lang/Class$4 +sun/reflect/NativeMethodAccessorImpl +sun/reflect/DelegatingMethodAccessorImpl +java/awt/font/TextAttribute +java/awt/Toolkit$2 +sun/awt/X11/XToolkit +sun/awt/UNIXToolkit +java/util/TreeMap +java/util/NavigableMap +java/util/SortedMap +java/awt/GraphicsDevice +sun/awt/X11GraphicsDevice +sun/awt/X11GraphicsConfig +sun/awt/image/SurfaceManager$ProxiedGraphicsConfig +java/awt/GraphicsConfiguration +java/awt/ImageCapabilities +sun/java2d/x11/X11SurfaceData +sun/java2d/x11/XSurfaceData +sun/java2d/SurfaceData +java/awt/Transparency +sun/java2d/DisposerTarget +sun/java2d/StateTrackable +sun/java2d/Surface +sun/java2d/InvalidPipeException +java/lang/IllegalStateException +sun/java2d/NullSurfaceData +sun/java2d/StateTrackable$State +sun/java2d/loops/SurfaceType +sun/awt/image/PixelConverter +sun/awt/image/PixelConverter$Xrgb +sun/awt/image/PixelConverter$Argb +sun/awt/image/PixelConverter$ArgbPre +sun/awt/image/PixelConverter$Xbgr +sun/awt/image/PixelConverter$Rgba +sun/awt/image/PixelConverter$RgbaPre +sun/awt/image/PixelConverter$Ushort565Rgb +sun/awt/image/PixelConverter$Ushort555Rgb +sun/awt/image/PixelConverter$Ushort555Rgbx +sun/awt/image/PixelConverter$Ushort4444Argb +sun/awt/image/PixelConverter$ByteGray +sun/awt/image/PixelConverter$UshortGray +sun/awt/image/PixelConverter$Rgbx +sun/awt/image/PixelConverter$Bgrx +sun/awt/image/PixelConverter$ArgbBm +java/awt/image/ColorModel +java/awt/image/ColorModel$1 +java/awt/image/DirectColorModel +java/awt/image/PackedColorModel +java/awt/color/ColorSpace +java/awt/color/ICC_Profile +sun/java2d/cmm/ProfileDeferralInfo +sun/java2d/cmm/ProfileDeferralMgr +java/awt/color/ICC_ProfileRGB +java/awt/color/ICC_Profile$1 +sun/java2d/cmm/ProfileActivator +java/awt/color/ICC_ColorSpace +sun/java2d/StateTrackableDelegate +sun/java2d/StateTrackableDelegate$2 +sun/java2d/pipe/NullPipe +sun/java2d/pipe/PixelDrawPipe +sun/java2d/pipe/PixelFillPipe +sun/java2d/pipe/ShapeDrawPipe +sun/java2d/pipe/TextPipe +sun/java2d/pipe/DrawImagePipe +java/awt/image/IndexColorModel +sun/java2d/pipe/LoopPipe +sun/java2d/pipe/ParallelogramPipe +sun/java2d/pipe/LoopBasedPipe +sun/java2d/pipe/RenderingEngine +sun/java2d/pipe/RenderingEngine$1 +sun/dc/DuctusRenderingEngine +sun/java2d/pipe/OutlineTextRenderer +sun/java2d/pipe/SolidTextRenderer +sun/java2d/pipe/GlyphListLoopPipe +sun/java2d/pipe/GlyphListPipe +sun/java2d/pipe/AATextRenderer +sun/java2d/pipe/LCDTextRenderer +sun/java2d/pipe/AlphaColorPipe +sun/java2d/pipe/CompositePipe +sun/java2d/SurfaceData$PixelToShapeLoopConverter +sun/java2d/pipe/PixelToShapeConverter +sun/java2d/SurfaceData$PixelToPgramLoopConverter +sun/java2d/pipe/PixelToParallelogramConverter +sun/java2d/pipe/TextRenderer +sun/java2d/pipe/SpanClipRenderer +sun/java2d/pipe/Region +sun/java2d/pipe/RegionIterator +sun/java2d/pipe/Region$ImmutableRegion +sun/java2d/pipe/AAShapePipe +sun/java2d/pipe/AlphaPaintPipe +sun/java2d/pipe/SpanShapeRenderer$Composite +sun/java2d/pipe/SpanShapeRenderer +sun/java2d/pipe/GeneralCompositePipe +sun/java2d/pipe/DrawImage +sun/java2d/loops/RenderCache +sun/java2d/loops/RenderCache$Entry +sun/java2d/loops/XORComposite +java/awt/Composite +sun/font/X11TextRenderer +sun/java2d/loops/GraphicsPrimitive +sun/java2d/x11/X11PMBlitLoops +sun/java2d/loops/Blit +sun/java2d/loops/GraphicsPrimitiveMgr +sun/java2d/loops/CompositeType +sun/java2d/SunGraphics2D +sun/awt/ConstrainableGraphics +sun/java2d/DestSurfaceProvider +java/awt/Graphics2D +java/awt/Color +java/awt/Paint +java/awt/AlphaComposite +java/awt/geom/Path2D +java/awt/Shape +java/awt/geom/Path2D$Float +sun/awt/SunHints +sun/java2d/loops/BlitBg +sun/java2d/loops/ScaledBlit +sun/java2d/loops/FillRect +sun/java2d/loops/FillSpans +sun/java2d/loops/FillParallelogram +sun/java2d/loops/DrawParallelogram +sun/java2d/loops/DrawLine +sun/java2d/loops/DrawRect +sun/java2d/loops/DrawPolygons +sun/java2d/loops/DrawPath +sun/java2d/loops/FillPath +sun/java2d/loops/MaskBlit +sun/java2d/loops/MaskFill +sun/java2d/loops/DrawGlyphList +sun/java2d/loops/DrawGlyphListAA +sun/java2d/loops/DrawGlyphListLCD +sun/java2d/loops/TransformHelper +java/awt/BasicStroke +java/awt/Stroke +sun/misc/PerformanceLogger +sun/misc/PerformanceLogger$TimeData +sun/java2d/pipe/ValidatePipe +sun/awt/SunHints$Key +java/awt/RenderingHints$Key +sun/awt/SunHints$Value +sun/awt/SunHints$LCDContrastKey +sun/java2d/loops/CustomComponent +sun/java2d/loops/GraphicsPrimitiveProxy +sun/java2d/loops/GeneralRenderer +sun/java2d/loops/GraphicsPrimitiveMgr$1 +sun/java2d/loops/GraphicsPrimitiveMgr$2 +sun/java2d/x11/X11PMBlitLoops$DelegateBlitLoop +sun/java2d/x11/X11PMBlitBgLoops +sun/java2d/x11/X11SurfaceData$LazyPipe +sun/awt/X11GraphicsConfig$X11GCDisposerRecord +sun/java2d/DisposerRecord +sun/java2d/Disposer +sun/java2d/Disposer$1 +sun/misc/ThreadGroupUtils +sun/awt/X11/XModifierKeymap +sun/awt/X11/XWrapperBase +sun/awt/X11/Native +sun/awt/X11/Native$1 +sun/awt/X11/XToolkit$3 +sun/awt/X11/XToolkit$4 +sun/awt/X11/XEventDispatcher +java/awt/Toolkit$DesktopPropertyChangeSupport +java/beans/PropertyChangeSupport +java/beans/PropertyChangeSupport$PropertyChangeListenerMap +java/beans/ChangeListenerMap +java/beans/PropertyChangeListener +sun/awt/SunToolkit$ModalityListenerList +sun/awt/ModalityListener +sun/font/FontConfigManager +sun/font/FontConfigManager$FontConfigInfo +sun/awt/X11/AwtScreenData +sun/awt/X11/XToolkit$1 +java/lang/invoke/DirectMethodHandle$Special +sun/awt/X11/XToolkit$2 +java/lang/ApplicationShutdownHooks +java/lang/ApplicationShutdownHooks$1 +java/lang/Shutdown +java/lang/Shutdown$Lock +sun/awt/X11/XWM +sun/awt/X11/XAtom +java/awt/Insets +sun/awt/X11/XWM$1 +sun/awt/X11/XErrorHandler$XBaseErrorHandler +sun/awt/X11/XErrorHandler +sun/awt/X11/XSetWindowAttributes +sun/awt/X11/XNETProtocol +sun/awt/X11/XStateProtocol +sun/awt/X11/XLayerProtocol +sun/awt/X11/XProtocol +sun/awt/X11/WindowPropertyGetter +sun/awt/X11/UnsafeXDisposerRecord +sun/awt/X11/XPropertyCache +sun/awt/X11/XWINProtocol +sun/awt/X11/XAtomList +java/awt/Rectangle +java/awt/geom/Rectangle2D +sun/awt/X11/XEvent +java/awt/geom/RectangularShape +javax/swing/RepaintManager$ProcessingRunnable +com/sun/java/swing/SwingUtilities3 +javax/swing/UIManager +javax/swing/UIManager$LookAndFeelInfo +sun/awt/OSInfo +sun/awt/OSInfo$WindowsVersion +sun/awt/OSInfo$1 +sun/awt/OSInfo$OSType +sun/swing/SwingUtilities2 +java/awt/font/FontRenderContext +java/awt/RenderingHints +sun/swing/StringUIClientPropertyKey +sun/swing/UIClientPropertyKey +sun/swing/SwingUtilities2$LSBCacheEntry +javax/swing/UIManager$LAFState +javax/swing/UIDefaults +javax/swing/MultiUIDefaults +javax/swing/UIManager$1 +javax/swing/plaf/metal/MetalLookAndFeel +javax/swing/plaf/basic/BasicLookAndFeel +javax/swing/LookAndFeel +sun/swing/DefaultLookup +javax/swing/plaf/metal/OceanTheme +javax/swing/plaf/metal/DefaultMetalTheme +javax/swing/plaf/metal/MetalTheme +javax/swing/plaf/ColorUIResource +javax/swing/plaf/UIResource +sun/swing/PrintColorUIResource +javax/swing/plaf/metal/DefaultMetalTheme$FontDelegate +javax/swing/plaf/FontUIResource +sun/swing/SwingLazyValue +javax/swing/UIDefaults$LazyValue +javax/swing/UIDefaults$ActiveValue +javax/swing/plaf/InsetsUIResource +javax/swing/plaf/BorderUIResource$EmptyBorderUIResource +javax/swing/border/EmptyBorder +javax/swing/border/AbstractBorder +javax/swing/border/Border +sun/swing/SwingUtilities2$2 +javax/swing/plaf/basic/BasicLookAndFeel$2 +javax/swing/plaf/DimensionUIResource +javax/swing/UIDefaults$LazyInputMap +javax/swing/plaf/metal/MetalLookAndFeel$FontActiveValue +sun/swing/SwingUtilities2$AATextInfo +sun/awt/HeadlessToolkit +sun/awt/X11/XAWTXSettings +sun/awt/X11/XMSelectionListener +sun/awt/XSettings +sun/awt/X11/XMSelection +sun/awt/X11/XMSelection$1 +sun/awt/X11/XMSelection$3 +sun/awt/X11/XErrorHandler$IgnoreBadWindowHandler +sun/awt/XSettings$Update +java/beans/PropertyChangeEvent +java/awt/Toolkit$DesktopPropertyChangeSupport$1 +java/util/IdentityHashMap$Values +java/util/IdentityHashMap$ValueIterator +java/util/IdentityHashMap$IdentityHashMapIterator +java/util/HashMap$KeySet +java/util/HashMap$KeyIterator +javax/swing/plaf/metal/MetalLookAndFeel$AATextListener +java/beans/PropertyChangeListenerProxy +java/util/EventListenerProxy +javax/swing/plaf/metal/OceanTheme$1 +javax/swing/plaf/metal/OceanTheme$2 +javax/swing/plaf/metal/OceanTheme$3 +javax/swing/plaf/metal/OceanTheme$4 +javax/swing/plaf/metal/OceanTheme$5 +javax/swing/plaf/metal/OceanTheme$6 +javax/swing/SwingPaintEventDispatcher +sun/awt/PaintEventDispatcher +java/awt/KeyboardFocusManager +java/awt/KeyEventDispatcher +java/awt/KeyEventPostProcessor +java/awt/KeyboardFocusManager$1 +sun/awt/AWTAccessor$KeyboardFocusManagerAccessor +java/awt/AWTKeyStroke +java/awt/AWTKeyStroke$1 +java/awt/DefaultKeyboardFocusManager +java/awt/DefaultKeyboardFocusManager$1 +sun/awt/AWTAccessor$DefaultKeyboardFocusManagerAccessor +java/awt/DefaultFocusTraversalPolicy +java/awt/ContainerOrderFocusTraversalPolicy +java/awt/FocusTraversalPolicy +java/util/Collections$UnmodifiableSet +sun/awt/X11/XKeyboardFocusManagerPeer +sun/awt/KeyboardFocusManagerPeerImpl +java/awt/peer/KeyboardFocusManagerPeer +javax/swing/UIManager$2 +javax/swing/JRootPane +javax/swing/UIDefaults$TextAndMnemonicHashMap +com/sun/swing/internal/plaf/metal/resources/metal +sun/util/ResourceBundleEnumeration +com/sun/swing/internal/plaf/basic/resources/basic +javax/swing/plaf/metal/MetalLabelUI +javax/swing/plaf/basic/BasicLabelUI +javax/swing/plaf/LabelUI +javax/swing/plaf/ComponentUI +sun/reflect/misc/MethodUtil +sun/reflect/misc/MethodUtil$1 +sun/net/www/protocol/jar/JarURLConnection +java/net/JarURLConnection +sun/net/www/protocol/jar/JarFileFactory +sun/net/www/protocol/jar/URLJarFile$URLJarFileCloseController +java/net/HttpURLConnection +sun/net/www/protocol/jar/URLJarFile +sun/net/www/protocol/jar/URLJarFile$URLJarFileEntry +sun/net/www/protocol/jar/JarURLConnection$JarURLInputStream +java/lang/UnsupportedOperationException +java/lang/reflect/InvocationTargetException +javax/swing/plaf/metal/DefaultMetalTheme$FontDelegate$1 +javax/swing/plaf/basic/BasicHTML +sun/awt/util/IdentityArrayList +java/awt/Window$1 +sun/awt/AWTAccessor$WindowAccessor +java/awt/Frame$1 +sun/awt/AWTAccessor$FrameAccessor +java/awt/Window$Type +java/awt/Cursor +java/awt/Cursor$1 +sun/awt/AWTAccessor$CursorAccessor +java/awt/BorderLayout +java/awt/LayoutManager2 +sun/awt/X11/XlibUtil +java/util/concurrent/locks/LockSupport +sun/nio/ch/Interruptible +java/awt/Dialog$ModalExclusionType +java/awt/Window$WindowDisposerRecord +javax/swing/JPanel +java/awt/FlowLayout +javax/swing/plaf/basic/BasicPanelUI +javax/swing/plaf/PanelUI +java/awt/Component$BaselineResizeBehavior +sun/swing/SwingLazyValue$1 +javax/swing/JLayeredPane +javax/swing/JRootPane$1 +javax/swing/ArrayTable +javax/swing/JRootPane$RootLayout +javax/swing/BufferStrategyPaintManager +javax/swing/RepaintManager$PaintManager +javax/swing/FocusManager +javax/swing/LayoutFocusTraversalPolicy +javax/swing/SortingFocusTraversalPolicy +javax/swing/InternalFrameFocusTraversalPolicy +javax/swing/SwingContainerOrderFocusTraversalPolicy +javax/swing/SortingFocusTraversalPolicy$1 +java/util/Spliterator$OfLong +java/util/Spliterator$OfPrimitive +java/util/Spliterator +java/util/Spliterator$OfInt +java/util/Spliterator$OfDouble +java/util/stream/IntStream +java/util/stream/BaseStream +java/util/stream/Stream +java/util/stream/DoubleStream +java/util/stream/LongStream +java/util/function/DoubleBinaryOperator +java/util/function/IntBinaryOperator +java/util/function/LongBinaryOperator +java/util/function/BinaryOperator +java/util/function/BiFunction +java/util/function/IntToDoubleFunction +java/util/function/IntFunction +java/util/function/IntToLongFunction +java/util/function/IntUnaryOperator +javax/swing/SwingDefaultFocusTraversalPolicy +javax/swing/LayoutComparator +javax/swing/plaf/metal/MetalRootPaneUI +javax/swing/plaf/basic/BasicRootPaneUI +javax/swing/plaf/RootPaneUI +javax/swing/plaf/basic/BasicRootPaneUI$RootPaneInputMap +javax/swing/plaf/ComponentInputMapUIResource +javax/swing/ComponentInputMap +javax/swing/InputMap +javax/swing/plaf/InputMapUIResource +javax/swing/KeyStroke +java/awt/VKCollection +sun/reflect/UnsafeQualifiedStaticIntegerFieldAccessorImpl +javax/swing/plaf/basic/LazyActionMap +javax/swing/plaf/ActionMapUIResource +javax/swing/ActionMap +sun/awt/X11/XFramePeer +java/awt/peer/FramePeer +java/awt/peer/WindowPeer +java/awt/peer/ContainerPeer +java/awt/peer/ComponentPeer +sun/awt/X11/XDecoratedPeer +sun/awt/X11/XWindowPeer +sun/awt/X11/XPanelPeer +java/awt/peer/PanelPeer +sun/awt/X11/XCanvasPeer +java/awt/peer/CanvasPeer +sun/awt/X11/XComponentPeer +java/awt/dnd/peer/DropTargetPeer +sun/java2d/BackBufferCapsProvider +sun/awt/X11/XWindow +sun/awt/X11ComponentPeer +sun/awt/X11/XBaseWindow +sun/awt/X11/XCreateWindowParams +sun/awt/X11/XBaseWindow$InitialiseState +sun/awt/X11/XBaseWindow$StateLock +sun/awt/X11/AwtGraphicsConfigData +sun/awt/X11/XVisualInfo +java/awt/SystemColor +sun/awt/AWTAccessor$SystemColorAccessor +sun/awt/X11/MotifColorUtilities +sun/awt/X11/XRepaintArea +sun/awt/RepaintArea +sun/awt/X11/XWindowAttributesData +sun/awt/X11/WindowDimensions +java/awt/Point +java/awt/geom/Point2D +java/util/TreeMap$Entry +sun/awt/X11/XSizeHints +sun/awt/X11/XRootWindow +sun/awt/X11/XRootWindow$LazyHolder +sun/nio/cs/ISO_8859_1$Encoder +sun/nio/cs/Surrogate$Parser +sun/nio/cs/Surrogate +sun/java2d/x11/X11SurfaceData$X11WindowSurfaceData +sun/awt/X11/XDropTargetEventProcessor +sun/java2d/loops/RenderLoops +sun/awt/X11/XDragSourceContextPeer +sun/java2d/loops/GraphicsPrimitiveMgr$PrimitiveSpec +sun/awt/X11/XDragSourceProtocolListener +java/util/Arrays$LegacyMergeSort +sun/awt/dnd/SunDragSourceContextPeer +java/awt/dnd/peer/DragSourceContextPeer +java/util/TimSort +sun/awt/X11/XAnyEvent +sun/awt/X11/XAwtState +sun/awt/X11/XBaseWindow$1 +sun/awt/X11/XPropertyEvent +sun/java2d/DefaultDisposerRecord +sun/java2d/SurfaceDataProxy +sun/awt/image/SurfaceManager$FlushableCacheData +sun/java2d/SurfaceDataProxy$1 +sun/java2d/StateTracker +sun/java2d/StateTracker$1 +sun/java2d/StateTracker$2 +sun/java2d/x11/X11Renderer +sun/awt/X11/XGlobalCursorManager +sun/awt/GlobalCursorManager +sun/awt/IconInfo +sun/awt/AWTIcon32_java_icon16_png +sun/awt/AWTIcon32_java_icon24_png +sun/awt/AWTIcon32_java_icon32_png +sun/awt/AWTIcon32_java_icon48_png +sun/awt/X11/XClientMessageEvent +sun/awt/X11/XContentWindow +sun/awt/X11/XFocusProxyWindow +sun/awt/X11/XWMHints +java/util/LinkedList$ListItr +sun/awt/AWTAutoShutdown +java/awt/peer/LightweightPeer +sun/awt/NullComponentPeer +java/awt/SplashScreen +java/awt/Dialog +java/awt/Dialog$ModalityType +sun/awt/X11/PropMwmHints +sun/awt/X11/XWindowPeer$4 +sun/awt/GlobalCursorManager$NativeUpdater +java/awt/event/WindowEvent +java/awt/EventQueue$5 +java/awt/EventDispatchThread +sun/awt/PeerEvent +java/awt/EventDispatchThread$1 +java/awt/Conditional +java/awt/event/InvocationEvent +java/awt/ActiveEvent +java/awt/EventDispatchThread$HierarchyEventFilter +java/awt/EventFilter +java/awt/event/PaintEvent +sun/awt/X11/XReparentEvent +java/awt/event/MouseEvent +java/awt/ModalEventFilter +sun/awt/EventQueueItem +sun/awt/EventQueueDelegate +java/awt/EventFilter$FilterAction +java/awt/EventQueue$3 +java/awt/EventQueue$4 +sun/awt/dnd/SunDropTargetEvent +sun/awt/X11/XConfigureEvent +java/awt/event/InputMethodEvent +java/awt/event/ActionEvent +java/awt/event/FocusEvent +java/util/Vector$Itr +java/awt/event/InvocationEvent$1 +sun/awt/X11/XWindowPeer$2 +sun/awt/AWTAccessor$InvocationEventAccessor +java/applet/Applet +java/awt/Panel +sun/awt/X11/XVisibilityEvent +sun/awt/X11/XExposeEvent +sun/awt/event/IgnorePaintEvent +sun/awt/X11/XTranslateCoordinates +sun/awt/X11/XFocusChangeEvent +java/awt/SequencedEvent +java/awt/SequencedEvent$1 +sun/awt/AWTAccessor$SequencedEventAccessor +sun/awt/X11/XComponentPeer$1 +java/awt/MenuComponent +java/awt/TrayIcon +java/util/IdentityHashMap$KeySet +java/util/IdentityHashMap$KeyIterator +javax/swing/RepaintManager$4 +java/awt/GraphicsCallback$PaintCallback +java/awt/GraphicsCallback +sun/awt/SunGraphicsCallback +javax/swing/BufferStrategyPaintManager$BufferInfo +java/awt/event/WindowListener +java/awt/event/ComponentAdapter +java/awt/event/ComponentListener +java/awt/AWTEventMulticaster +java/awt/event/ContainerListener +java/awt/event/FocusListener +java/awt/event/KeyListener +java/awt/event/MouseListener +java/awt/event/MouseMotionListener +java/awt/event/WindowFocusListener +java/awt/event/WindowStateListener +java/awt/event/ActionListener +java/awt/event/ItemListener +java/awt/event/AdjustmentListener +java/awt/event/TextListener +java/awt/event/InputMethodListener +java/awt/event/HierarchyListener +java/awt/event/HierarchyBoundsListener +java/awt/event/MouseWheelListener +java/awt/BufferCapabilities +java/awt/Component$BltSubRegionBufferStrategy +sun/awt/SubRegionShowable +java/awt/Component$BltBufferStrategy +java/awt/image/BufferStrategy +java/awt/image/VolatileImage +java/awt/Image +sun/awt/image/SunVolatileImage +java/awt/Image$1 +sun/awt/image/SurfaceManager$ImageAccessor +sun/awt/image/SurfaceManager +sun/awt/image/BufferedImageGraphicsConfig +sun/print/PrinterGraphicsConfig +sun/java2d/opengl/GLXGraphicsConfig +sun/java2d/opengl/OGLGraphicsConfig +sun/java2d/pipe/hw/AccelGraphicsConfig +sun/java2d/pipe/hw/BufferedContextProvider +sun/java2d/xr/XRGraphicsConfig +sun/java2d/x11/X11VolatileSurfaceManager +sun/awt/image/VolatileSurfaceManager +sun/java2d/x11/X11SurfaceData$X11PixmapSurfaceData +sun/font/FontDesignMetrics +java/awt/FontMetrics +sun/font/SunFontManager +sun/java2d/FontSupport +sun/font/FontManagerForSGE +sun/font/FontManager +sun/font/SunFontManager$TTFilter +java/io/FilenameFilter +sun/font/SunFontManager$T1Filter +sun/font/SunFontManager$1 +sun/font/FontManagerNativeLibrary +sun/font/FontManagerNativeLibrary$1 +sun/font/FontUtilities +sun/font/FontUtilities$1 +sun/font/TrueTypeFont +sun/font/FileFont +sun/font/PhysicalFont +sun/font/Font2D +sun/font/Type1Font +java/awt/geom/Point2D$Float +sun/font/StrikeMetrics +java/awt/geom/Rectangle2D$Float +java/awt/geom/GeneralPath +sun/font/CharToGlyphMapper +sun/font/PhysicalStrike +sun/font/FontStrike +sun/font/StrikeCache +sun/font/StrikeCache$1 +sun/font/GlyphList +sun/font/FontManagerFactory +sun/font/FontManagerFactory$1 +sun/awt/X11FontManager +sun/font/CompositeFont +sun/font/SunFontManager$2 +java/io/StreamTokenizer +sun/font/SunFontManager$FontRegistrationInfo +sun/awt/motif/MFontConfiguration +sun/awt/FontConfiguration +sun/awt/FontDescriptor +java/util/Properties$LineReader +sun/font/FcFontConfiguration +java/net/InetAddress +java/net/InetAddress$1 +java/net/InetAddress$InetAddressHolder +java/net/InetAddress$Cache +java/net/InetAddress$Cache$Type +java/net/InetAddressImplFactory +java/net/Inet4AddressImpl +java/net/InetAddressImpl +java/net/InetAddress$2 +sun/net/spi/nameservice/NameService +java/net/Inet4Address +java/net/Inet6Address +java/net/Inet6Address$Inet6AddressHolder +sun/net/InetAddressCachePolicy +sun/net/InetAddressCachePolicy$1 +java/security/Security +java/security/Security$1 +sun/net/InetAddressCachePolicy$2 +java/util/LinkedHashMap$LinkedKeySet +java/util/LinkedHashMap$LinkedKeyIterator +java/net/InetAddress$CacheEntry +sun/font/FontConfigManager$FcCompFont +sun/font/FontConfigManager$FontConfigFont +sun/font/CompositeFontDescriptor +sun/font/Font2DHandle +sun/font/FontFamily +sun/font/SunFontManager$3 +sun/font/FontDesignMetrics$MetricsKey +sun/font/FontStrikeDesc +sun/font/CompositeStrike +sun/font/FontStrikeDisposer +sun/java2d/Disposer$PollDisposable +sun/font/StrikeCache$SoftDisposerRef +sun/font/StrikeCache$DisposableStrike +sun/font/TrueTypeFont$TTDisposerRecord +sun/font/TrueTypeFont$1 +java/io/RandomAccessFile +java/io/DataOutput +java/io/DataInput +sun/nio/ch/FileChannelImpl +java/nio/channels/FileChannel +java/nio/channels/SeekableByteChannel +java/nio/channels/ByteChannel +java/nio/channels/ReadableByteChannel +java/nio/channels/Channel +java/nio/channels/WritableByteChannel +java/nio/channels/GatheringByteChannel +java/nio/channels/ScatteringByteChannel +java/nio/channels/spi/AbstractInterruptibleChannel +java/nio/channels/InterruptibleChannel +java/nio/file/attribute/FileAttribute +sun/nio/ch/IOUtil +sun/nio/ch/IOUtil$1 +sun/nio/ch/NativeThreadSet +sun/nio/ch/FileDispatcherImpl +sun/nio/ch/FileDispatcher +sun/nio/ch/NativeDispatcher +java/nio/channels/spi/AbstractInterruptibleChannel$1 +sun/nio/ch/NativeThread +sun/nio/ch/IOStatus +sun/nio/ch/Util +sun/nio/ch/Util$1 +sun/nio/ch/Util$BufferCache +java/nio/DirectByteBuffer$Deallocator +java/nio/ByteBufferAsIntBufferB +java/nio/IntBuffer +sun/font/TrueTypeFont$DirectoryEntry +java/nio/ByteBufferAsShortBufferB +java/nio/ShortBuffer +sun/nio/cs/UTF_16$Decoder +sun/nio/cs/UnicodeDecoder +sun/font/FileFontStrike +sun/font/FontScaler +sun/font/T2KFontScaler +sun/font/T2KFontScaler$1 +sun/font/TrueTypeGlyphMapper +sun/font/CMap +sun/font/CMap$NullCMapClass +sun/font/CMap$CMapFormat12 +sun/font/FontDesignMetrics$KeyReference +sun/font/CompositeGlyphMapper +java/awt/print/PrinterGraphics +java/awt/PrintGraphics +sun/java2d/loops/FontInfo +sun/awt/X11/XSystemTrayPeer +java/awt/peer/SystemTrayPeer +java/util/jar/Attributes +java/util/jar/Manifest$FastInputStream +java/util/jar/Attributes$Name +sun/misc/ASCIICaseInsensitiveComparator +java/util/jar/JarVerifier +java/security/CodeSigner +java/util/jar/JarVerifier$3 +java/io/ByteArrayOutputStream +java/lang/Package +sun/security/util/SignatureFileVerifier +sun/security/util/ManifestEntryVerifier +java/util/MissingResourceException +javax/swing/JDialog +javax/swing/text/JTextComponent +javax/swing/Scrollable +javax/swing/JTextArea +javax/swing/JScrollPane +javax/swing/ScrollPaneConstants +javax/swing/AbstractButton +java/awt/ItemSelectable +javax/swing/JButton +java/io/StringWriter +java/lang/SecurityException +javax/swing/JWindow +java/io/UnsupportedEncodingException +sun/misc/URLClassPath$FileLoader +java/lang/CloneNotSupportedException +java/lang/InternalError +java/net/UnknownHostException +java/net/Socket +java/net/SocketAddress +java/nio/channels/SocketChannel +java/nio/channels/NetworkChannel +java/nio/channels/spi/AbstractSelectableChannel +java/nio/channels/SelectableChannel +java/net/SocketException +java/net/SocketImplFactory +java/net/InetSocketAddress +java/net/InetSocketAddress$InetSocketAddressHolder +java/net/Proxy +java/net/SocketImpl +java/net/SocketOptions +java/net/SocksSocketImpl +java/net/SocksConsts +java/net/PlainSocketImpl +java/net/AbstractPlainSocketImpl +java/net/AbstractPlainSocketImpl$1 +sun/net/util/IPAddressUtil +java/net/SocksSocketImpl$3 +java/net/ProxySelector +sun/net/spi/DefaultProxySelector +sun/net/spi/DefaultProxySelector$1 +sun/net/NetProperties +sun/net/NetProperties$1 +java/net/URI +java/net/URI$Parser +sun/net/spi/DefaultProxySelector$NonProxyInfo +sun/net/spi/DefaultProxySelector$3 +java/net/Proxy$Type +sun/net/NetHooks +sun/net/sdp/SdpProvider +sun/net/NetHooks$Provider +java/net/ConnectException +java/net/MalformedURLException +java/lang/UnsatisfiedLinkError +javax/swing/UnsupportedLookAndFeelException +sun/misc/FloatingDecimal$ASCIIToBinaryBuffer +sun/misc/FDBigInteger +java/util/ResourceBundle$Control$1 +java/net/URLClassLoader$2 +java/util/PropertyResourceBundle +java/util/ResourceBundle$BundleReference +java/util/logging/Level +java/util/logging/Level$KnownLevel +java/util/logging/Logger +java/util/logging/Handler +java/util/logging/Logger$LoggerBundle +java/util/concurrent/CopyOnWriteArrayList +java/util/logging/LogManager +java/util/logging/LogManager$1 +java/util/logging/LogManager$SystemLoggerContext +java/util/logging/LogManager$LoggerContext +java/util/logging/LogManager$LogNode +java/util/logging/LoggingPermission +java/util/logging/LogManager$Cleaner +java/util/logging/LogManager$2 +java/util/logging/LogManager$3 +java/util/logging/LogManager$LoggerWeakRef +java/util/logging/LogManager$LoggerContext$1 +java/util/logging/LogManager$RootLogger +java/util/logging/LogManager$5 +java/util/logging/Logger$1 +sun/util/logging/resources/logging +javax/swing/Box +javax/swing/Box$Filler +javax/swing/Icon +javax/swing/BoxLayout +javax/swing/plaf/basic/BasicPopupMenuUI +javax/swing/plaf/PopupMenuUI +javax/swing/ImageIcon +javax/swing/ImageIcon$1 +javax/swing/ImageIcon$2 +javax/swing/ImageIcon$2$1 +java/awt/dnd/DropTarget +java/awt/dnd/DropTargetListener +javax/accessibility/AccessibleContext +sun/reflect/UnsafeObjectFieldAccessorImpl +java/awt/MediaTracker +sun/misc/SoftCache$ValueCell +sun/awt/image/URLImageSource +sun/awt/image/InputStreamImageSource +java/awt/image/ImageProducer +sun/awt/image/ImageFetchable +sun/awt/image/ToolkitImage +sun/awt/image/NativeLibLoader +sun/awt/image/NativeLibLoader$1 +javax/swing/ImageIcon$3 +java/awt/ImageMediaEntry +java/awt/MediaEntry +sun/awt/image/MultiResolutionToolkitImage +sun/awt/image/MultiResolutionImage +sun/awt/image/ImageRepresentation +java/awt/image/ImageConsumer +sun/awt/image/ImageWatched +sun/awt/image/ImageWatched$Link +sun/awt/image/ImageWatched$WeakLink +sun/awt/image/ImageConsumerQueue +sun/awt/image/ImageFetcher +sun/awt/image/FetcherInfo +sun/awt/image/ImageFetcher$1 +sun/net/ProgressMonitor +sun/net/DefaultProgressMeteringPolicy +sun/net/ProgressMeteringPolicy +sun/net/www/MimeTable +java/net/FileNameMap +sun/net/www/MimeTable$1 +sun/net/www/MimeTable$DefaultInstanceHolder +sun/net/www/MimeTable$DefaultInstanceHolder$1 +sun/net/www/MimeEntry +java/net/URLConnection$1 +java/text/SimpleDateFormat +java/text/DateFormat +java/text/Format +java/text/DateFormat$Field +java/text/Format$Field +java/util/TimeZone +sun/util/calendar/ZoneInfo +sun/util/calendar/ZoneInfoFile +sun/util/calendar/ZoneInfoFile$1 +java/io/DataInputStream +sun/util/calendar/ZoneInfoFile$ZoneOffsetTransitionRule +sun/util/calendar/ZoneInfoFile$Checksum +java/util/zip/CRC32 +java/util/zip/Checksum +java/util/TimeZone$1 +java/util/Calendar +sun/util/spi/CalendarProvider +java/util/spi/LocaleServiceProvider +sun/util/locale/provider/LocaleProviderAdapter +sun/util/locale/provider/JRELocaleProviderAdapter +sun/util/locale/provider/ResourceBundleBasedAdapter +sun/util/locale/provider/SPILocaleProviderAdapter +sun/util/locale/provider/AuxLocaleProviderAdapter +sun/util/locale/provider/AuxLocaleProviderAdapter$NullProvider +sun/util/locale/provider/LocaleProviderAdapter$Type +sun/util/locale/provider/LocaleProviderAdapter$1 +sun/util/locale/provider/CalendarProviderImpl +sun/util/locale/provider/AvailableLanguageTags +sun/util/locale/provider/LocaleDataMetaInfo +sun/util/locale/provider/JRELocaleProviderAdapter$1 +java/util/Calendar$Builder +java/util/GregorianCalendar +sun/util/locale/provider/CalendarDataUtility +java/util/spi/CalendarDataProvider +sun/util/locale/provider/LocaleServiceProviderPool +java/text/spi/BreakIteratorProvider +java/text/spi/CollatorProvider +java/text/spi/DateFormatProvider +java/text/spi/DateFormatSymbolsProvider +java/text/spi/DecimalFormatSymbolsProvider +java/text/spi/NumberFormatProvider +java/util/spi/CurrencyNameProvider +java/util/spi/LocaleNameProvider +java/util/spi/TimeZoneNameProvider +sun/util/locale/provider/CalendarDataProviderImpl +sun/util/locale/provider/SPILocaleProviderAdapter$1 +sun/util/locale/provider/CalendarDataUtility$CalendarWeekParameterGetter +sun/util/locale/provider/LocaleServiceProviderPool$LocalizedObjectGetter +sun/util/locale/provider/LocaleResources +sun/util/resources/LocaleData +sun/util/resources/LocaleData$1 +sun/util/resources/LocaleData$LocaleDataResourceBundleControl +sun/util/locale/LanguageTag +java/util/Collections$EmptyIterator +sun/util/resources/CalendarData +sun/util/resources/LocaleNamesBundle +sun/util/resources/OpenListResourceBundle +sun/util/resources/en/CalendarData_en +sun/util/locale/provider/LocaleResources$ResourceReference +sun/util/calendar/Gregorian$Date +sun/util/calendar/BaseCalendar$Date +sun/util/calendar/CalendarDate +sun/util/calendar/CalendarUtils +java/text/DateFormatSymbols +sun/util/locale/provider/DateFormatSymbolsProviderImpl +sun/text/resources/FormatData +sun/util/resources/ParallelListResourceBundle +java/util/concurrent/atomic/AtomicMarkableReference +java/util/concurrent/atomic/AtomicMarkableReference$Pair +sun/text/resources/en/FormatData_en +sun/text/resources/en/FormatData_en_US +sun/util/resources/ParallelListResourceBundle$KeySet +java/text/NumberFormat +sun/util/locale/provider/NumberFormatProviderImpl +java/text/DecimalFormatSymbols +sun/util/locale/provider/DecimalFormatSymbolsProviderImpl +java/util/Currency +java/util/Currency$1 +sun/util/locale/provider/CurrencyNameProviderImpl +java/util/Currency$CurrencyNameGetter +sun/util/resources/CurrencyNames +sun/util/resources/en/CurrencyNames_en_US +java/text/DecimalFormat +java/text/FieldPosition +java/text/DigitList +java/math/RoundingMode +java/text/DontCareFieldPosition +java/text/DontCareFieldPosition$1 +java/text/Format$FieldDelegate +sun/awt/image/GifImageDecoder +sun/awt/image/ImageDecoder +sun/awt/image/GifFrame +java/awt/image/Raster +java/awt/image/DataBufferByte +java/awt/image/DataBuffer +java/awt/image/DataBuffer$1 +sun/awt/image/SunWritableRaster$DataStealer +sun/awt/image/SunWritableRaster +java/awt/image/WritableRaster +java/awt/image/PixelInterleavedSampleModel +java/awt/image/ComponentSampleModel +java/awt/image/SampleModel +sun/awt/image/ByteInterleavedRaster +sun/awt/image/ByteComponentRaster +java/awt/image/BufferedImage +java/awt/image/WritableRenderedImage +java/awt/image/RenderedImage +java/awt/image/BufferedImage$1 +sun/awt/image/IntegerComponentRaster +sun/awt/image/BytePackedRaster +javax/swing/plaf/BorderUIResource +javax/swing/BorderFactory +javax/swing/border/BevelBorder +javax/swing/border/EtchedBorder +javax/swing/plaf/metal/MetalIconFactory +javax/swing/plaf/metal/MetalIconFactory$TreeFolderIcon +javax/swing/plaf/metal/MetalIconFactory$FolderIcon16 +java/util/zip/ZipInputStream +java/io/PushbackInputStream +java/util/zip/ZipUtils +java/io/RandomAccessFile$1 +java/lang/Thread$State +javax/swing/SwingUtilities$SharedOwnerFrame +sun/awt/X11/XWindowAttributes +javax/swing/border/LineBorder +javax/swing/SizeRequirements +java/util/ArrayList$ListItr +javax/swing/CellRendererPane +javax/swing/RepaintManager$3 +javax/swing/JRadioButton +javax/swing/JToggleButton +java/lang/ClassFormatError +java/io/ObjectInputStream +java/io/ObjectInput +java/io/ObjectStreamConstants +sun/awt/image/BufImgSurfaceManager +sun/awt/image/BufImgSurfaceData +sun/awt/image/BufImgSurfaceData$ICMColorData +sun/java2d/x11/X11SurfaceDataProxy +sun/java2d/x11/X11SurfaceDataProxy$Bitmask +sun/java2d/StateTrackableDelegate$1 +javax/swing/JTabbedPane +java/awt/geom/RectIterator +java/awt/geom/PathIterator +javax/swing/event/ChangeListener +java/awt/Polygon +javax/swing/event/MenuListener +javax/swing/DefaultSingleSelectionModel +javax/swing/SingleSelectionModel +javax/swing/JTabbedPane$ModelListener +javax/swing/plaf/metal/MetalTabbedPaneUI +javax/swing/plaf/basic/BasicTabbedPaneUI +javax/swing/plaf/TabbedPaneUI +javax/swing/plaf/metal/MetalTabbedPaneUI$TabbedPaneLayout +javax/swing/plaf/basic/BasicTabbedPaneUI$TabbedPaneLayout +javax/swing/plaf/basic/BasicTabbedPaneUI$TabbedPaneScrollLayout +javax/swing/plaf/basic/BasicTabbedPaneUI$Handler +sun/reflect/MethodAccessorGenerator +sun/reflect/AccessorGenerator +sun/reflect/ClassFileConstants +sun/reflect/ByteVectorFactory +sun/reflect/ByteVectorImpl +sun/reflect/ByteVector +sun/reflect/ClassFileAssembler +sun/reflect/UTF8 +sun/reflect/Label +sun/reflect/Label$PatchInfo +sun/reflect/MethodAccessorGenerator$1 +sun/reflect/ClassDefiner +sun/reflect/ClassDefiner$1 +sun/reflect/BootstrapConstructorAccessorImpl +javax/swing/JTextField +javax/swing/JViewport +java/awt/CardLayout +javax/swing/text/Document +javax/swing/text/JTextComponent$1 +sun/swing/SwingAccessor$JTextComponentAccessor +javax/swing/text/JTextComponent$4 +com/sun/beans/util/Cache +com/sun/beans/util/Cache$Kind +com/sun/beans/util/Cache$Kind$1 +com/sun/beans/util/Cache$Kind$2 +com/sun/beans/util/Cache$Kind$3 +com/sun/beans/util/Cache$CacheEntry +javax/swing/Action +javax/swing/JTextField$NotifyAction +javax/swing/text/TextAction +javax/swing/AbstractAction +java/lang/ArrayIndexOutOfBoundsException +javax/swing/DropMode +javax/swing/text/JTextComponent$MutableCaretEvent +javax/swing/event/CaretEvent +javax/swing/plaf/metal/MetalTextFieldUI +javax/swing/plaf/basic/BasicTextFieldUI +javax/swing/plaf/basic/BasicTextUI +javax/swing/text/ViewFactory +javax/swing/plaf/TextUI +javax/swing/plaf/basic/BasicTextUI$BasicCursor +javax/swing/text/DefaultEditorKit +javax/swing/text/EditorKit +javax/swing/text/DefaultEditorKit$InsertContentAction +javax/swing/text/DefaultEditorKit$DeletePrevCharAction +javax/swing/text/DefaultEditorKit$DeleteNextCharAction +javax/swing/text/DefaultEditorKit$ReadOnlyAction +javax/swing/text/DefaultEditorKit$DeleteWordAction +javax/swing/text/DefaultEditorKit$WritableAction +javax/swing/text/DefaultEditorKit$CutAction +javax/swing/text/DefaultEditorKit$CopyAction +javax/swing/text/DefaultEditorKit$PasteAction +javax/swing/text/DefaultEditorKit$VerticalPageAction +javax/swing/text/DefaultEditorKit$PageAction +javax/swing/text/DefaultEditorKit$InsertBreakAction +javax/swing/text/DefaultEditorKit$BeepAction +javax/swing/text/DefaultEditorKit$NextVisualPositionAction +javax/swing/text/DefaultEditorKit$BeginWordAction +javax/swing/text/DefaultEditorKit$EndWordAction +javax/swing/text/DefaultEditorKit$PreviousWordAction +javax/swing/text/DefaultEditorKit$NextWordAction +javax/swing/text/DefaultEditorKit$BeginLineAction +javax/swing/text/DefaultEditorKit$EndLineAction +javax/swing/text/DefaultEditorKit$BeginParagraphAction +javax/swing/text/DefaultEditorKit$EndParagraphAction +javax/swing/text/DefaultEditorKit$BeginAction +javax/swing/text/DefaultEditorKit$EndAction +javax/swing/text/DefaultEditorKit$DefaultKeyTypedAction +javax/swing/text/DefaultEditorKit$InsertTabAction +javax/swing/text/DefaultEditorKit$SelectWordAction +javax/swing/text/DefaultEditorKit$SelectLineAction +javax/swing/text/DefaultEditorKit$SelectParagraphAction +javax/swing/text/DefaultEditorKit$SelectAllAction +javax/swing/text/DefaultEditorKit$UnselectAction +javax/swing/text/DefaultEditorKit$ToggleComponentOrientationAction +javax/swing/text/DefaultEditorKit$DumpModelAction +javax/swing/plaf/basic/BasicTextUI$TextTransferHandler +javax/swing/TransferHandler +javax/swing/TransferHandler$TransferAction +sun/swing/UIAction +javax/swing/text/Position$Bias +javax/swing/plaf/basic/BasicTextUI$RootView +javax/swing/text/View +javax/swing/plaf/basic/BasicTextUI$UpdateHandler +javax/swing/event/DocumentListener +javax/swing/plaf/basic/BasicTextUI$DragListener +javax/swing/plaf/basic/DragRecognitionSupport$BeforeDrag +javax/swing/event/MouseInputAdapter +javax/swing/event/MouseInputListener +java/awt/event/MouseAdapter +javax/swing/plaf/metal/MetalBorders +javax/swing/plaf/BorderUIResource$CompoundBorderUIResource +javax/swing/border/CompoundBorder +javax/swing/plaf/metal/MetalBorders$TextFieldBorder +javax/swing/plaf/metal/MetalBorders$Flush3DBorder +javax/swing/plaf/basic/BasicBorders$MarginBorder +javax/swing/plaf/basic/BasicTextUI$BasicCaret +javax/swing/text/DefaultCaret +javax/swing/text/Caret +javax/swing/text/DefaultCaret$Handler +java/awt/datatransfer/ClipboardOwner +javax/swing/Timer +javax/swing/Timer$DoPostEvent +javax/swing/plaf/basic/BasicTextUI$BasicHighlighter +javax/swing/text/DefaultHighlighter +javax/swing/text/LayeredHighlighter +javax/swing/text/Highlighter +javax/swing/text/Highlighter$Highlight +javax/swing/text/DefaultHighlighter$DefaultHighlightPainter +javax/swing/text/LayeredHighlighter$LayerPainter +javax/swing/text/Highlighter$HighlightPainter +javax/swing/text/DefaultHighlighter$SafeDamager +javax/swing/ClientPropertyKey +javax/swing/ClientPropertyKey$1 +sun/awt/AWTAccessor$ClientPropertyKeyAccessor +javax/swing/TransferHandler$SwingDropTarget +java/awt/dnd/DropTargetContext +java/awt/datatransfer/SystemFlavorMap +java/awt/datatransfer/FlavorMap +java/awt/datatransfer/FlavorTable +java/awt/datatransfer/SystemFlavorMap$SoftCache +javax/swing/TransferHandler$DropHandler +javax/swing/TransferHandler$TransferSupport +javax/swing/text/PlainDocument +javax/swing/text/AbstractDocument +javax/swing/text/GapContent +javax/swing/text/AbstractDocument$Content +javax/swing/text/GapVector +javax/swing/text/GapContent$MarkVector +javax/swing/text/GapContent$MarkData +javax/swing/text/StyleContext +javax/swing/text/AbstractDocument$AttributeContext +javax/swing/text/StyleConstants +javax/swing/text/StyleConstants$CharacterConstants +javax/swing/text/AttributeSet$CharacterAttribute +javax/swing/text/StyleConstants$FontConstants +javax/swing/text/AttributeSet$FontAttribute +javax/swing/text/StyleConstants$ColorConstants +javax/swing/text/AttributeSet$ColorAttribute +javax/swing/text/StyleConstants$ParagraphConstants +javax/swing/text/AttributeSet$ParagraphAttribute +javax/swing/text/StyleContext$FontKey +javax/swing/text/SimpleAttributeSet +javax/swing/text/MutableAttributeSet +javax/swing/text/AttributeSet +javax/swing/text/SimpleAttributeSet$EmptyAttributeSet +javax/swing/text/StyleContext$NamedStyle +javax/swing/text/Style +java/util/Collections$EmptyEnumeration +javax/swing/text/StyleContext$SmallAttributeSet +java/util/Collections$3 +javax/swing/text/AbstractDocument$BidiRootElement +javax/swing/text/AbstractDocument$BranchElement +javax/swing/text/AbstractDocument$AbstractElement +javax/swing/text/Element +javax/swing/tree/TreeNode +javax/swing/text/AbstractDocument$1 +javax/swing/text/AbstractDocument$BidiElement +javax/swing/text/AbstractDocument$LeafElement +javax/swing/text/GapContent$StickyPosition +javax/swing/text/Position +javax/swing/text/StyleContext$KeyEnumeration +javax/swing/text/FieldView +javax/swing/text/PlainView +javax/swing/text/TabExpander +javax/swing/text/JTextComponent$DefaultKeymap +javax/swing/text/Keymap +javax/swing/text/JTextComponent$KeymapWrapper +javax/swing/text/JTextComponent$KeymapActionMap +javax/swing/plaf/basic/BasicTextUI$FocusAction +javax/swing/plaf/basic/BasicTextUI$TextActionWrapper +javax/swing/plaf/synth/SynthUI +javax/swing/plaf/synth/SynthConstants +javax/swing/JEditorPane +javax/swing/DefaultBoundedRangeModel +javax/swing/BoundedRangeModel +javax/swing/JTextField$ScrollRepainter +javax/swing/DefaultButtonModel +javax/swing/ButtonModel +javax/swing/AbstractButton$Handler +javax/swing/plaf/basic/BasicButtonUI +javax/swing/plaf/ButtonUI +javax/swing/plaf/metal/MetalBorders$ButtonBorder +javax/swing/plaf/basic/BasicButtonListener +javax/swing/event/AncestorListener +java/beans/VetoableChangeListener +javax/swing/plaf/metal/MetalComboBoxButton +javax/swing/plaf/basic/BasicArrowButton +javax/swing/plaf/metal/MetalScrollButton +sun/swing/ImageIconUIResource +javax/swing/GrayFilter +java/awt/image/RGBImageFilter +java/awt/image/ImageFilter +java/awt/image/FilteredImageSource +javax/swing/plaf/basic/BasicGraphicsUtils +javax/swing/ButtonGroup +org/w3c/dom/Node +org/xml/sax/SAXException +javax/xml/parsers/ParserConfigurationException +org/xml/sax/EntityResolver +java/security/NoSuchAlgorithmException +java/security/GeneralSecurityException +java/util/zip/GZIPInputStream +java/util/zip/DeflaterOutputStream +java/io/StringReader +org/xml/sax/InputSource +javax/xml/parsers/DocumentBuilderFactory +javax/xml/parsers/FactoryFinder +javax/xml/parsers/SecuritySupport +javax/xml/parsers/SecuritySupport$2 +javax/xml/parsers/SecuritySupport$5 +javax/xml/parsers/FactoryFinder$1 +javax/xml/parsers/DocumentBuilder +org/xml/sax/ErrorHandler +org/w3c/dom/Document +org/xml/sax/helpers/DefaultHandler +org/xml/sax/DTDHandler +org/xml/sax/ContentHandler +org/xml/sax/SAXNotRecognizedException +org/xml/sax/SAXNotSupportedException +org/xml/sax/Locator +org/xml/sax/SAXParseException +org/w3c/dom/NodeList +org/w3c/dom/events/EventTarget +org/w3c/dom/traversal/DocumentTraversal +org/w3c/dom/events/DocumentEvent +org/w3c/dom/ranges/DocumentRange +org/w3c/dom/Element +org/w3c/dom/CharacterData +org/w3c/dom/CDATASection +org/w3c/dom/Text +org/w3c/dom/Entity +org/xml/sax/AttributeList +org/w3c/dom/DOMException +org/w3c/dom/DocumentType +org/w3c/dom/Attr +org/w3c/dom/EntityReference +org/w3c/dom/DocumentFragment +org/w3c/dom/ProcessingInstruction +org/w3c/dom/Notation +org/w3c/dom/Comment +org/w3c/dom/events/EventException +org/w3c/dom/events/Event +org/w3c/dom/events/MutationEvent +org/w3c/dom/traversal/TreeWalker +org/w3c/dom/ranges/Range +org/w3c/dom/traversal/NodeIterator +org/w3c/dom/NamedNodeMap +java/awt/GridLayout +javax/swing/JToggleButton$ToggleButtonModel +javax/swing/plaf/metal/MetalRadioButtonUI +javax/swing/plaf/basic/BasicRadioButtonUI +javax/swing/plaf/basic/BasicToggleButtonUI +javax/swing/plaf/basic/BasicBorders +javax/swing/plaf/basic/BasicBorders$RadioButtonBorder +javax/swing/plaf/basic/BasicBorders$ButtonBorder +javax/swing/plaf/metal/MetalIconFactory$RadioButtonIcon +javax/swing/plaf/basic/BasicRadioButtonUI$KeyHandler +javax/swing/plaf/basic/BasicRadioButtonUI$SelectPreviousBtn +javax/swing/plaf/basic/BasicRadioButtonUI$SelectNextBtn +javax/swing/event/ChangeEvent +java/awt/event/ItemEvent +javax/swing/ToolTipManager +javax/swing/ToolTipManager$insideTimerAction +javax/swing/ToolTipManager$outsideTimerAction +javax/swing/ToolTipManager$stillInsideTimerAction +javax/swing/ToolTipManager$MoveBeforeEnterListener +java/awt/event/MouseMotionAdapter +javax/swing/ToolTipManager$AccessibilityKeyListener +java/awt/event/KeyAdapter +java/awt/CardLayout$Card +javax/swing/JComboBox +javax/swing/event/ListDataListener +javax/swing/JCheckBox +javax/swing/JPopupMenu +javax/swing/MenuElement +javax/swing/DefaultComboBoxModel +javax/swing/MutableComboBoxModel +javax/swing/ComboBoxModel +javax/swing/ListModel +javax/swing/AbstractListModel +javax/swing/JComboBox$1 +javax/swing/AncestorNotifier +javax/swing/plaf/metal/MetalComboBoxUI +javax/swing/plaf/basic/BasicComboBoxUI +javax/swing/plaf/ComboBoxUI +javax/swing/plaf/metal/MetalComboBoxUI$MetalComboBoxLayoutManager +javax/swing/plaf/basic/BasicComboBoxUI$ComboBoxLayoutManager +javax/swing/plaf/basic/BasicComboPopup +javax/swing/plaf/basic/ComboPopup +javax/swing/plaf/basic/BasicComboPopup$EmptyListModelClass +javax/swing/plaf/basic/BasicLookAndFeel$AWTEventHelper +java/awt/event/AWTEventListenerProxy +java/awt/Toolkit$SelectiveAWTEventListener +java/awt/Toolkit$ToolkitEventMulticaster +javax/swing/plaf/basic/BasicLookAndFeel$1 +javax/swing/plaf/basic/DefaultMenuLayout +javax/swing/plaf/metal/MetalBorders$PopupMenuBorder +javax/swing/plaf/basic/BasicPopupMenuUI$BasicPopupMenuListener +javax/swing/event/PopupMenuListener +javax/swing/plaf/basic/BasicPopupMenuUI$BasicMenuKeyListener +javax/swing/event/MenuKeyListener +javax/swing/plaf/basic/BasicPopupMenuUI$MouseGrabber +javax/swing/MenuSelectionManager +javax/swing/plaf/basic/BasicPopupMenuUI$MenuKeyboardHelper +javax/swing/plaf/basic/BasicPopupMenuUI$MenuKeyboardHelper$1 +java/awt/event/FocusAdapter +javax/swing/plaf/basic/BasicComboPopup$1 +javax/swing/JList +javax/swing/DefaultListSelectionModel +javax/swing/ListSelectionModel +javax/swing/plaf/basic/BasicListUI +javax/swing/plaf/ListUI +javax/swing/plaf/basic/BasicListUI$ListTransferHandler +javax/swing/DefaultListCellRenderer$UIResource +javax/swing/DefaultListCellRenderer +javax/swing/ListCellRenderer +javax/swing/plaf/basic/BasicListUI$Handler +javax/swing/event/ListSelectionListener +javax/swing/JMenu +javax/swing/JMenuItem +javax/swing/event/ListSelectionEvent +javax/swing/plaf/basic/BasicComboPopup$Handler +javax/swing/ScrollPaneLayout$UIResource +javax/swing/ScrollPaneLayout +javax/swing/ViewportLayout +javax/swing/plaf/basic/BasicViewportUI +javax/swing/plaf/ViewportUI +javax/swing/JScrollPane$ScrollBar +javax/swing/JScrollBar +java/awt/Adjustable +javax/swing/JScrollBar$ModelListener +javax/swing/plaf/metal/MetalScrollBarUI +javax/swing/plaf/basic/BasicScrollBarUI +javax/swing/plaf/ScrollBarUI +javax/swing/plaf/metal/MetalBumps +javax/swing/plaf/basic/BasicScrollBarUI$TrackListener +javax/swing/plaf/basic/BasicScrollBarUI$ArrowButtonListener +javax/swing/plaf/basic/BasicScrollBarUI$ModelListener +javax/swing/plaf/metal/MetalScrollBarUI$ScrollBarListener +javax/swing/plaf/basic/BasicScrollBarUI$PropertyChangeHandler +javax/swing/plaf/basic/BasicScrollBarUI$Handler +javax/swing/plaf/basic/BasicScrollBarUI$ScrollListener +javax/swing/JViewport$ViewListener +javax/swing/plaf/metal/MetalScrollPaneUI +javax/swing/plaf/basic/BasicScrollPaneUI +javax/swing/plaf/ScrollPaneUI +javax/swing/plaf/metal/MetalBorders$ScrollPaneBorder +javax/swing/plaf/basic/BasicScrollPaneUI$Handler +javax/swing/plaf/metal/MetalScrollPaneUI$1 +javax/swing/plaf/basic/BasicComboBoxRenderer$UIResource +javax/swing/plaf/basic/BasicComboBoxRenderer +javax/swing/plaf/metal/MetalComboBoxEditor$UIResource +javax/swing/plaf/metal/MetalComboBoxEditor +javax/swing/plaf/basic/BasicComboBoxEditor +javax/swing/ComboBoxEditor +javax/swing/plaf/basic/BasicComboBoxEditor$BorderlessTextField +javax/swing/plaf/basic/BasicComboBoxEditor$UIResource +javax/swing/text/Segment +java/text/CharacterIterator +javax/swing/plaf/metal/MetalComboBoxEditor$1 +javax/swing/plaf/metal/MetalComboBoxEditor$EditorBorder +javax/swing/JToolBar +javax/swing/plaf/metal/MetalComboBoxUI$MetalPropertyChangeListener +javax/swing/plaf/basic/BasicComboBoxUI$PropertyChangeHandler +javax/swing/plaf/basic/BasicComboBoxUI$Handler +javax/swing/plaf/metal/MetalComboBoxIcon +javax/swing/plaf/metal/MetalComboBoxButton$1 +javax/swing/plaf/basic/BasicComboBoxUI$DefaultKeySelectionManager +javax/swing/JComboBox$KeySelectionManager +javax/swing/plaf/metal/MetalCheckBoxUI +javax/swing/plaf/metal/MetalIconFactory$CheckBoxIcon +java/lang/ExceptionInInitializerError +com/sun/java/swing/plaf/windows/WindowsTabbedPaneUI +javax/swing/JProgressBar +javax/swing/JProgressBar$ModelListener +javax/swing/plaf/metal/MetalProgressBarUI +javax/swing/plaf/basic/BasicProgressBarUI +javax/swing/plaf/ProgressBarUI +javax/swing/plaf/BorderUIResource$LineBorderUIResource +javax/swing/plaf/basic/BasicProgressBarUI$Handler +javax/swing/JTable +javax/swing/event/TableModelListener +javax/swing/event/TableColumnModelListener +javax/swing/event/CellEditorListener +javax/swing/event/RowSorterListener +javax/swing/tree/TreeModel +javax/swing/table/JTableHeader +javax/swing/table/AbstractTableModel +javax/swing/table/TableModel +javax/swing/table/TableCellRenderer +javax/swing/event/TreeExpansionListener +javax/swing/table/DefaultTableCellRenderer +javax/swing/JCheckBoxMenuItem +javax/swing/JTree +javax/swing/tree/TreeSelectionModel +javax/swing/tree/DefaultTreeCellRenderer +javax/swing/tree/TreeCellRenderer +javax/swing/table/TableCellEditor +javax/swing/CellEditor +javax/swing/JToolTip +javax/swing/table/TableColumn +javax/swing/table/DefaultTableColumnModel +javax/swing/table/TableColumnModel +javax/swing/table/DefaultTableModel +javax/swing/event/TableModelEvent +sun/swing/table/DefaultTableCellHeaderRenderer +sun/swing/table/DefaultTableCellHeaderRenderer$EmptyIcon +javax/swing/plaf/basic/BasicTableHeaderUI +javax/swing/plaf/TableHeaderUI +javax/swing/plaf/basic/BasicTableHeaderUI$1 +javax/swing/plaf/basic/BasicTableHeaderUI$MouseInputHandler +javax/swing/DefaultCellEditor +javax/swing/tree/TreeCellEditor +javax/swing/AbstractCellEditor +javax/swing/plaf/basic/BasicTableUI +javax/swing/plaf/TableUI +javax/swing/plaf/basic/BasicTableUI$TableTransferHandler +javax/swing/plaf/basic/BasicTableUI$Handler +javax/swing/tree/DefaultTreeSelectionModel +javax/swing/tree/TreePath +javax/swing/plaf/metal/MetalTreeUI +javax/swing/plaf/basic/BasicTreeUI +javax/swing/plaf/TreeUI +javax/swing/plaf/basic/BasicTreeUI$Actions +javax/swing/plaf/basic/BasicTreeUI$TreeTransferHandler +javax/swing/plaf/metal/MetalTreeUI$LineListener +javax/swing/plaf/basic/BasicTreeUI$Handler +javax/swing/event/TreeModelListener +javax/swing/event/TreeSelectionListener +javax/swing/event/SwingPropertyChangeSupport +javax/swing/tree/VariableHeightLayoutCache +javax/swing/tree/AbstractLayoutCache +javax/swing/tree/RowMapper +javax/swing/plaf/basic/BasicTreeUI$NodeDimensionsHandler +javax/swing/tree/AbstractLayoutCache$NodeDimensions +javax/swing/JTree$TreeModelHandler +javax/swing/tree/VariableHeightLayoutCache$TreeStateNode +javax/swing/tree/DefaultMutableTreeNode +javax/swing/tree/MutableTreeNode +javax/swing/tree/DefaultMutableTreeNode$PreorderEnumeration +java/util/Vector$1 +javax/swing/event/TableColumnModelEvent +javax/swing/JPopupMenu$Separator +javax/swing/JSeparator +java/text/ParseException +java/text/NumberFormat$Field +javax/swing/text/GapContent$InsertUndo +javax/swing/undo/AbstractUndoableEdit +javax/swing/undo/UndoableEdit +javax/swing/text/AbstractDocument$DefaultDocumentEvent +javax/swing/event/DocumentEvent +javax/swing/undo/CompoundEdit +javax/swing/event/DocumentEvent$EventType +javax/swing/text/Utilities +javax/swing/text/SegmentCache +javax/swing/text/SegmentCache$CachedSegment +javax/swing/event/DocumentEvent$ElementChange +javax/swing/event/UndoableEditEvent +javax/swing/event/UndoableEditListener +java/awt/Canvas +java/util/Locale$Category +java/util/Locale$1 +javax/swing/filechooser/FileFilter +java/io/FileWriter +javax/swing/tree/DefaultTreeModel +javax/swing/tree/DefaultTreeCellEditor +javax/swing/tree/DefaultTreeCellEditor$1 +javax/swing/tree/DefaultTreeCellEditor$DefaultTextField +javax/swing/DefaultCellEditor$1 +javax/swing/DefaultCellEditor$EditorDelegate +javax/swing/tree/DefaultTreeCellEditor$EditorContainer +javax/swing/JTree$TreeSelectionRedirector +javax/swing/JMenuItem$MenuItemFocusListener +javax/swing/plaf/basic/BasicMenuItemUI +javax/swing/plaf/MenuItemUI +javax/swing/plaf/metal/MetalBorders$MenuItemBorder +javax/swing/plaf/metal/MetalIconFactory$MenuItemArrowIcon +sun/swing/MenuItemLayoutHelper +javax/swing/plaf/basic/BasicMenuItemUI$Handler +javax/swing/event/MenuDragMouseListener +javax/swing/event/TreeModelEvent +javax/swing/JSplitPane +javax/swing/plaf/metal/MetalSplitPaneUI +javax/swing/plaf/basic/BasicSplitPaneUI +javax/swing/plaf/SplitPaneUI +javax/swing/plaf/basic/BasicSplitPaneDivider +javax/swing/plaf/basic/BasicBorders$SplitPaneBorder +javax/swing/plaf/metal/MetalSplitPaneDivider +javax/swing/plaf/basic/BasicSplitPaneDivider$DividerLayout +javax/swing/plaf/basic/BasicSplitPaneDivider$MouseHandler +javax/swing/plaf/basic/BasicBorders$SplitPaneDividerBorder +javax/swing/plaf/basic/BasicSplitPaneUI$BasicHorizontalLayoutManager +javax/swing/plaf/basic/BasicSplitPaneUI$1 +javax/swing/plaf/basic/BasicSplitPaneUI$Handler +javax/swing/plaf/metal/MetalSplitPaneDivider$1 +javax/swing/plaf/basic/BasicSplitPaneDivider$OneTouchActionHandler +javax/swing/plaf/metal/MetalSplitPaneDivider$2 +javax/swing/border/TitledBorder +javax/swing/plaf/basic/BasicTextAreaUI +javax/swing/text/AbstractDocument$ElementEdit +java/util/Random +java/util/concurrent/atomic/AtomicLong +java/io/InterruptedIOException +java/net/NoRouteToHostException +java/net/BindException +javax/swing/tree/PathPlaceHolder +javax/swing/event/TreeSelectionEvent +javax/swing/JList$3 +javax/swing/JList$ListSelectionHandler +javax/swing/JSlider +javax/swing/JSlider$ModelListener +javax/swing/plaf/metal/MetalSliderUI +javax/swing/plaf/basic/BasicSliderUI +javax/swing/plaf/SliderUI +javax/swing/plaf/basic/BasicSliderUI$Actions +javax/swing/plaf/metal/MetalIconFactory$HorizontalSliderThumbIcon +javax/swing/plaf/metal/MetalIconFactory$VerticalSliderThumbIcon +javax/swing/plaf/basic/BasicSliderUI$TrackListener +javax/swing/plaf/basic/BasicSliderUI$Handler +javax/swing/plaf/basic/BasicSliderUI$ScrollListener +javax/swing/plaf/metal/MetalSliderUI$MetalPropertyListener +javax/swing/plaf/basic/BasicSliderUI$PropertyChangeHandler +java/util/concurrent/ConcurrentHashMap$KeyIterator +java/util/concurrent/ConcurrentHashMap$BaseIterator +java/util/concurrent/ConcurrentHashMap$Traverser +sun/font/Type1Font$1 +java/nio/channels/FileChannel$MapMode +sun/nio/ch/FileChannelImpl$Unmapper +sun/nio/ch/Util$4 +java/nio/DirectByteBufferR +sun/nio/cs/US_ASCII$Decoder +sun/font/SunFontManager$10 +java/util/concurrent/ConcurrentHashMap$ValueIterator +javax/swing/DefaultListModel +javax/swing/event/ListDataEvent +javax/sound/sampled/DataLine +javax/sound/sampled/Line +javax/sound/sampled/LineUnavailableException +javax/sound/sampled/UnsupportedAudioFileException +javax/sound/sampled/Line$Info +javax/sound/sampled/DataLine$Info +javax/sound/sampled/Control$Type +javax/sound/sampled/FloatControl$Type +javax/swing/JMenuBar +javax/swing/plaf/basic/BasicMenuBarUI +javax/swing/plaf/MenuBarUI +javax/swing/plaf/metal/MetalBorders$MenuBarBorder +javax/swing/plaf/basic/BasicMenuBarUI$Handler +javax/swing/KeyboardManager +javax/swing/JRadioButtonMenuItem +javax/swing/JMenu$MenuChangeListener +javax/swing/plaf/basic/BasicMenuUI +javax/swing/plaf/metal/MetalIconFactory$MenuArrowIcon +javax/swing/plaf/basic/BasicMenuUI$Handler +javax/swing/JMenuItem$AccessibleJMenuItem +javax/swing/AbstractButton$AccessibleAbstractButton +javax/accessibility/AccessibleAction +javax/accessibility/AccessibleValue +javax/accessibility/AccessibleText +javax/accessibility/AccessibleExtendedComponent +javax/accessibility/AccessibleComponent +javax/swing/JComponent$AccessibleJComponent +java/awt/Container$AccessibleAWTContainer +java/awt/Component$AccessibleAWTComponent +javax/accessibility/AccessibleContext$1 +sun/awt/AWTAccessor$AccessibleContextAccessor +javax/accessibility/AccessibleRelationSet +javax/swing/JMenu$WinListener +java/awt/event/WindowAdapter +javax/swing/plaf/metal/MetalPopupMenuSeparatorUI +javax/swing/plaf/metal/MetalSeparatorUI +javax/swing/plaf/basic/BasicSeparatorUI +javax/swing/plaf/SeparatorUI +javax/accessibility/AccessibleState +javax/accessibility/AccessibleBundle +javax/swing/plaf/basic/BasicCheckBoxMenuItemUI +javax/swing/plaf/metal/MetalIconFactory$CheckBoxMenuItemIcon +javax/swing/JCheckBoxMenuItem$AccessibleJCheckBoxMenuItem +javax/swing/plaf/basic/BasicRadioButtonMenuItemUI +javax/swing/plaf/metal/MetalIconFactory$RadioButtonMenuItemIcon +java/awt/event/ContainerEvent +sun/awt/image/ImageDecoder$1 +java/awt/im/InputContext +sun/awt/im/InputMethodContext +java/awt/im/spi/InputMethodContext +java/awt/im/InputMethodRequests +sun/awt/im/InputContext +sun/awt/im/InputMethodManager +sun/awt/im/ExecutableInputMethodManager +sun/awt/X11/XInputMethodDescriptor +sun/awt/X11InputMethodDescriptor +java/awt/im/spi/InputMethodDescriptor +sun/awt/im/InputMethodLocator +sun/awt/im/ExecutableInputMethodManager$3 +javax/swing/JTabbedPane$Page +java/net/DatagramSocket +java/net/MulticastSocket +java/net/DatagramPacket +java/net/DatagramPacket$1 +java/net/DefaultDatagramSocketImplFactory +java/net/PlainDatagramSocketImpl +java/net/AbstractPlainDatagramSocketImpl +java/net/DatagramSocketImpl +java/net/AbstractPlainDatagramSocketImpl$1 +java/net/NetworkInterface +java/net/NetworkInterface$1 +java/net/InterfaceAddress +java/net/DefaultInterface +java/net/DatagramSocket$1 +java/net/SocketOption +sun/net/ResourceManager +java/text/Collator +sun/util/locale/provider/CollatorProviderImpl +java/util/Collections$UnmodifiableList$1 +sun/text/resources/CollationData +java/text/RuleBasedCollator +java/text/RBCollationTables +java/net/ServerSocket +java/text/RBTableBuilder +java/text/RBCollationTables$BuildAPI +sun/text/IntHashtable +sun/text/UCompactIntArray +sun/text/normalizer/NormalizerImpl +sun/text/normalizer/ICUData +sun/text/normalizer/NormalizerDataReader +sun/text/normalizer/ICUBinary$Authenticate +sun/text/normalizer/ICUBinary +sun/text/normalizer/NormalizerImpl$FCDTrieImpl +sun/text/normalizer/Trie$DataManipulate +sun/text/normalizer/NormalizerImpl$NormTrieImpl +sun/text/normalizer/NormalizerImpl$AuxTrieImpl +sun/text/normalizer/IntTrie +sun/text/normalizer/Trie +sun/text/normalizer/CharTrie +sun/text/normalizer/CharTrie$FriendAgent +sun/text/normalizer/UnicodeSet +sun/text/normalizer/UnicodeMatcher +sun/text/normalizer/NormalizerImpl$DecomposeArgs +java/text/MergeCollation +java/text/PatternEntry$Parser +java/text/PatternEntry +java/text/EntryPair +sun/text/ComposedCharIter +sun/text/normalizer/UTF16 +sun/net/www/protocol/http/Handler +java/security/SignatureException +java/security/InvalidKeyException +java/security/KeyException +java/security/Signature +java/security/SignatureSpi +java/io/ObjectInputStream$BlockDataInputStream +java/io/ObjectInputStream$PeekInputStream +java/io/ObjectInputStream$HandleTable +java/io/ObjectInputStream$HandleTable$HandleList +java/io/ObjectInputStream$ValidationList +java/io/Bits +java/io/ObjectStreamClass +java/io/ObjectOutputStream +java/io/ObjectOutput +sun/security/provider/DSAPublicKey +java/security/interfaces/DSAPublicKey +java/security/interfaces/DSAKey +java/security/PublicKey +java/security/Key +sun/security/x509/X509Key +java/io/ObjectStreamClass$Caches +java/io/ObjectStreamClass$WeakClassKey +java/io/ObjectStreamClass$EntryFuture +java/lang/reflect/Proxy +java/lang/reflect/InvocationHandler +java/lang/reflect/WeakCache +java/lang/reflect/Proxy$KeyFactory +java/lang/reflect/Proxy$ProxyClassFactory +java/io/Externalizable +java/io/ObjectStreamClass$2 +java/util/ComparableTimSort +sun/security/x509/AlgorithmId +sun/security/util/DerEncoder +sun/reflect/SerializationConstructorAccessorImpl +sun/security/util/BitArray +sun/reflect/UnsafeQualifiedStaticLongFieldAccessorImpl +java/io/ObjectStreamClass$FieldReflectorKey +java/io/ObjectStreamClass$FieldReflector +java/io/ObjectStreamClass$1 +java/io/DataOutputStream +java/io/ObjectStreamClass$MemberSignature +java/io/ObjectStreamClass$3 +sun/security/util/DerOutputStream +java/io/ObjectStreamClass$4 +java/io/ObjectStreamClass$5 +sun/security/util/DerValue +java/security/MessageDigest +java/security/MessageDigestSpi +sun/security/jca/GetInstance +sun/security/jca/Providers +java/lang/InheritableThreadLocal +sun/security/jca/ProviderList +sun/security/jca/ProviderConfig +java/math/BigInteger +java/security/Provider +sun/security/jca/ProviderList$3 +sun/security/jca/ProviderList$1 +java/security/Provider$ServiceKey +java/security/Provider$EngineDescription +java/security/interfaces/DSAParams +sun/security/jca/ProviderList$2 +sun/security/jca/ProviderConfig$2 +java/io/ObjectStreamClass$ClassDataSlot +sun/security/provider/Sun +java/io/SerialCallbackContext +sun/security/provider/SunEntries +sun/security/provider/SunEntries$1 +sun/security/provider/NativePRNG +java/security/SecureRandomSpi +sun/security/provider/NativePRNG$Variant +sun/security/util/DerInputStream +sun/security/provider/NativePRNG$1 +sun/security/provider/NativePRNG$2 +sun/security/provider/NativePRNG$RandomIO +sun/security/util/DerInputBuffer +sun/security/provider/NativePRNG$Blocking +sun/security/provider/NativePRNG$NonBlocking +sun/security/util/ObjectIdentifier +java/security/Provider$Service +java/security/Provider$UString +sun/security/provider/SHA +sun/security/provider/DigestBase +sun/security/jca/GetInstance$Instance +java/security/MessageDigest$Delegate +sun/security/provider/ByteArrayAccess +java/io/ObjectOutputStream$BlockDataOutputStream +java/security/AlgorithmParameters +java/io/ObjectOutputStream$HandleTable +java/io/ObjectOutputStream$ReplaceTable +java/security/AlgorithmParametersSpi +sun/security/provider/DSAParameters +sun/security/util/ByteArrayLexOrder +sun/security/util/ByteArrayTagOrder +sun/security/util/DerIndefLenConverter +java/io/ObjectStreamClass$ExceptionInfo +java/io/ObjectInputStream$GetFieldImpl +java/io/ObjectInputStream$GetField +java/math/BigInteger$UnsafeHolder +sun/security/jca/ServiceId +sun/security/jca/ProviderList$ServiceList +sun/security/jca/ProviderList$ServiceList$1 +java/security/Signature$Delegate +java/util/ArrayList$SubList +java/util/ArrayList$SubList$1 +java/security/interfaces/DSAPrivateKey +java/security/PrivateKey +javax/security/auth/Destroyable +sun/security/provider/DSA$SHA1withDSA +sun/security/provider/DSA$LegacyDSA +sun/security/provider/DSA +java/security/spec/DSAParameterSpec +java/security/spec/AlgorithmParameterSpec +java/math/MutableBigInteger +java/math/SignedMutableBigInteger +javax/swing/TimerQueue +java/util/concurrent/DelayQueue +java/util/concurrent/BlockingQueue +java/util/AbstractQueue +java/util/PriorityQueue +javax/swing/TimerQueue$1 +javax/swing/TimerQueue$DelayedTimer +java/util/concurrent/Delayed +java/util/concurrent/TimeUnit +java/util/concurrent/TimeUnit$1 +java/util/concurrent/TimeUnit$2 +java/util/concurrent/TimeUnit$3 +java/util/concurrent/TimeUnit$4 +java/util/concurrent/TimeUnit$5 +java/util/concurrent/TimeUnit$6 +java/util/concurrent/TimeUnit$7 +java/awt/Window$1DisposeAction +java/awt/EventQueue$1AWTInvocationLock +sun/awt/X11/XUnmapEvent +java/awt/LightweightDispatcher$2 +java/awt/Component$FlipBufferStrategy +java/awt/SentEvent +sun/java2d/cmm/CMSManager +java/awt/image/DataBufferInt +java/awt/image/SinglePixelPackedSampleModel +sun/awt/image/IntegerInterleavedRaster +sun/awt/X11/XDropTargetRegistry +sun/awt/X11/XEmbeddedFramePeer +sun/awt/X11/XDragAndDropProtocols +sun/awt/X11/XDropTargetContextPeer +sun/awt/dnd/SunDropTargetContextPeer +java/awt/dnd/peer/DropTargetContextPeer +java/awt/datatransfer/Transferable +sun/awt/X11/XDropTargetContextPeer$XDropTargetProtocolListenerImpl +sun/awt/X11/XDropTargetProtocolListener +sun/awt/X11/XDnDDragSourceProtocol +sun/awt/X11/XDragSourceProtocol +sun/awt/X11/MotifDnDDragSourceProtocol +sun/awt/X11/XDnDDropTargetProtocol +sun/awt/X11/XDropTargetProtocol +sun/awt/X11/MotifDnDDropTargetProtocol +sun/awt/X11/XErrorHandler$VerifyChangePropertyHandler +sun/awt/X11/XDnDConstants +sun/awt/X11/XSelection +sun/awt/X11/XSelection$IncrementalTransferHandler +sun/awt/X11/XSelection$SelectionEventHandler +sun/awt/X11/MotifDnDConstants +javax/swing/JLayer +javax/swing/JInternalFrame +javax/swing/KeyboardManager$ComponentKeyStrokePair +sun/awt/EmbeddedFrame +sun/swing/MenuItemLayoutHelper$RectSize +javax/swing/JTable$2 +javax/swing/JTable$Resizable3 +javax/swing/JTable$Resizable2 +javax/swing/JTable$5 +javax/swing/event/AncestorEvent +java/awt/Label +sun/awt/X11/XLabelPeer +java/awt/peer/LabelPeer +sun/awt/TimedWindowEvent +java/awt/DefaultKeyboardFocusManager$DefaultKeyboardFocusManagerSentEvent +sun/awt/CausedFocusEvent$Cause +java/awt/KeyboardFocusManager$HeavyweightFocusRequest +java/awt/DefaultKeyboardFocusManager$TypeAheadMarker +java/awt/KeyboardFocusManager$LightweightFocusRequest +sun/awt/CausedFocusEvent +java/awt/KeyboardFocusManager$3 +sun/awt/X11/XInputMethod +sun/awt/X11InputMethod +sun/awt/im/InputMethodAdapter +java/awt/im/spi/InputMethod +java/awt/Event +java/net/Authenticator +java/lang/Throwable$WrappedPrintStream +java/lang/Throwable$PrintStreamOrWriter +sun/awt/image/PNGImageDecoder +sun/awt/image/PNGFilterInputStream +sun/util/locale/provider/TimeZoneNameUtility +sun/util/locale/provider/TimeZoneNameProviderImpl +sun/util/locale/provider/TimeZoneNameUtility$TimeZoneNameGetter +sun/util/resources/TimeZoneNames +sun/util/resources/TimeZoneNamesBundle +sun/util/resources/en/TimeZoneNames_en +sun/awt/image/OffScreenImage +java/lang/ProcessBuilder +java/lang/ProcessImpl +java/lang/UNIXProcess +java/lang/Process +java/lang/UNIXProcess$Platform +java/lang/UNIXProcess$LaunchMechanism +java/util/EnumSet +java/util/RegularEnumSet +sun/java2d/x11/X11SurfaceDataProxy$Opaque +java/lang/UNIXProcess$1 +java/util/concurrent/Executor +java/util/concurrent/ThreadFactory +java/util/concurrent/Executors +java/util/concurrent/ThreadPoolExecutor +java/util/concurrent/AbstractExecutorService +java/util/concurrent/ExecutorService +java/util/concurrent/ThreadPoolExecutor$AbortPolicy +java/util/concurrent/RejectedExecutionHandler +java/util/concurrent/SynchronousQueue +java/util/concurrent/SynchronousQueue$TransferStack +java/util/concurrent/SynchronousQueue$Transferer +java/util/concurrent/SynchronousQueue$TransferStack$SNode +java/lang/UNIXProcess$ProcessPipeOutputStream +java/lang/UNIXProcess$ProcessPipeInputStream +java/util/concurrent/ThreadPoolExecutor$Worker +java/lang/ProcessBuilder$NullOutputStream +java/io/FilterReader +sun/awt/X11/XClipboard +sun/awt/X11/OwnershipListener +sun/awt/datatransfer/SunClipboard +java/awt/datatransfer/Clipboard +java/io/EOFException +java/util/jar/JarFile$JarEntryIterator +java/util/zip/ZipFile$ZipEntryIterator +java/lang/IllegalAccessError +java/text/MessageFormat +java/text/MessageFormat$Field +java/util/Hashtable$ValueCollection +javax/swing/event/CaretListener +javax/swing/plaf/metal/MetalButtonUI +javax/swing/plaf/metal/MetalToggleButtonUI +javax/swing/plaf/metal/MetalBorders$ToggleButtonBorder +javax/swing/event/MenuEvent +javax/swing/border/MatteBorder +sun/font/StandardGlyphVector +java/awt/font/GlyphVector +sun/font/StandardGlyphVector$GlyphStrike +sun/font/CoreMetrics +sun/font/FontLineMetrics +java/awt/font/LineMetrics +javax/swing/JToolBar$DefaultToolBarLayout +javax/swing/plaf/metal/MetalToolBarUI +javax/swing/plaf/basic/BasicToolBarUI +javax/swing/plaf/ToolBarUI +javax/swing/plaf/metal/MetalBorders$ToolBarBorder +javax/swing/plaf/metal/MetalBorders$RolloverButtonBorder +javax/swing/plaf/metal/MetalBorders$RolloverMarginBorder +javax/swing/plaf/basic/BasicBorders$RolloverMarginBorder +javax/swing/plaf/metal/MetalToolBarUI$MetalDockingListener +javax/swing/plaf/basic/BasicToolBarUI$DockingListener +javax/swing/plaf/basic/BasicToolBarUI$Handler +javax/swing/JToolBar$Separator +javax/swing/plaf/basic/BasicToolBarSeparatorUI +java/awt/event/AdjustmentEvent +java/awt/MenuBar +sun/awt/X11/XErrorEvent +# eea35d9d56e0006e diff --git a/jdk-1.8.0.281/jre/lib/cmm/CIEXYZ.pf b/jdk-1.8.0.281/jre/lib/cmm/CIEXYZ.pf new file mode 100755 index 0000000..db3ba20 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/cmm/CIEXYZ.pf differ diff --git a/jdk-1.8.0.281/jre/lib/cmm/GRAY.pf b/jdk-1.8.0.281/jre/lib/cmm/GRAY.pf new file mode 100755 index 0000000..e31a4a7 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/cmm/GRAY.pf differ diff --git a/jdk-1.8.0.281/jre/lib/cmm/LINEAR_RGB.pf b/jdk-1.8.0.281/jre/lib/cmm/LINEAR_RGB.pf new file mode 100755 index 0000000..eadae04 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/cmm/LINEAR_RGB.pf differ diff --git a/jdk-1.8.0.281/jre/lib/cmm/PYCC.pf b/jdk-1.8.0.281/jre/lib/cmm/PYCC.pf new file mode 100755 index 0000000..1c49e0b Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/cmm/PYCC.pf differ diff --git a/jdk-1.8.0.281/jre/lib/cmm/sRGB.pf b/jdk-1.8.0.281/jre/lib/cmm/sRGB.pf new file mode 100755 index 0000000..7f9d18d Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/cmm/sRGB.pf differ diff --git a/jdk-1.8.0.281/jre/lib/content-types.properties b/jdk-1.8.0.281/jre/lib/content-types.properties new file mode 100755 index 0000000..559de96 --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/content-types.properties @@ -0,0 +1,280 @@ +#sun.net.www MIME content-types table +# +# Property fields: +# +# ::= 'description' '=' +# ::= 'file_extensions' '=' +# ::= 'icon' '=' +# ::= 'browser' | 'application' | 'save' | 'unknown' +# ::= 'application' '=' +# + +# +# The "we don't know anything about this data" type(s). +# Used internally to mark unrecognized types. +# +content/unknown: description=Unknown Content +unknown/unknown: description=Unknown Data Type + +# +# The template we should use for temporary files when launching an application +# to view a document of given type. +# +temp.file.template: /tmp/%s + +# +# The "real" types. +# +application/octet-stream: \ + description=Generic Binary Stream;\ + file_extensions=.saveme,.dump,.hqx,.arc,.o,.a,.bin,.exe,.z,.gz + +application/oda: \ + description=ODA Document;\ + file_extensions=.oda + +application/pdf: \ + description=Adobe PDF Format;\ + file_extensions=.pdf + +application/postscript: \ + description=Postscript File;\ + file_extensions=.eps,.ai,.ps;\ + icon=ps;\ + action=application;\ + application=imagetool %s + +application/x-dvi: \ + description=TeX DVI File;\ + file_extensions=.dvi;\ + action=application;\ + application=xdvi %s + +application/x-hdf: \ + description=Hierarchical Data Format;\ + file_extensions=.hdf;\ + action=save + +application/x-latex: \ + description=LaTeX Source;\ + file_extensions=.latex + +application/x-netcdf: \ + description=Unidata netCDF Data Format;\ + file_extensions=.nc,.cdf;\ + action=save + +application/x-tex: \ + description=TeX Source;\ + file_extensions=.tex + +application/x-texinfo: \ + description=Gnu Texinfo;\ + file_extensions=.texinfo,.texi + +application/x-troff: \ + description=Troff Source;\ + file_extensions=.t,.tr,.roff;\ + action=application;\ + application=xterm -title troff -e sh -c \"nroff %s | col | more -w\" + +application/x-troff-man: \ + description=Troff Manpage Source;\ + file_extensions=.man;\ + action=application;\ + application=xterm -title troff -e sh -c \"nroff -man %s | col | more -w\" + +application/x-troff-me: \ + description=Troff ME Macros;\ + file_extensions=.me;\ + action=application;\ + application=xterm -title troff -e sh -c \"nroff -me %s | col | more -w\" + +application/x-troff-ms: \ + description=Troff MS Macros;\ + file_extensions=.ms;\ + action=application;\ + application=xterm -title troff -e sh -c \"nroff -ms %s | col | more -w\" + +application/x-wais-source: \ + description=Wais Source;\ + file_extensions=.src,.wsrc + +application/zip: \ + description=Zip File;\ + file_extensions=.zip;\ + icon=zip;\ + action=save + +application/x-bcpio: \ + description=Old Binary CPIO Archive;\ + file_extensions=.bcpio; action=save + +application/x-cpio: \ + description=Unix CPIO Archive;\ + file_extensions=.cpio; action=save + +application/x-gtar: \ + description=Gnu Tar Archive;\ + file_extensions=.gtar;\ + icon=tar;\ + action=save + +application/x-shar: \ + description=Shell Archive;\ + file_extensions=.sh,.shar;\ + action=save + +application/x-sv4cpio: \ + description=SVR4 CPIO Archive;\ + file_extensions=.sv4cpio; action=save + +application/x-sv4crc: \ + description=SVR4 CPIO with CRC;\ + file_extensions=.sv4crc; action=save + +application/x-tar: \ + description=Tar Archive;\ + file_extensions=.tar;\ + icon=tar;\ + action=save + +application/x-ustar: \ + description=US Tar Archive;\ + file_extensions=.ustar;\ + action=save + +audio/basic: \ + description=Basic Audio;\ + file_extensions=.snd,.au;\ + icon=audio;\ + action=application;\ + application=audiotool %s + +audio/x-aiff: \ + description=Audio Interchange Format File;\ + file_extensions=.aifc,.aif,.aiff;\ + icon=aiff + +audio/x-wav: \ + description=Wav Audio;\ + file_extensions=.wav;\ + icon=wav + +image/gif: \ + description=GIF Image;\ + file_extensions=.gif;\ + icon=gif;\ + action=browser + +image/ief: \ + description=Image Exchange Format;\ + file_extensions=.ief + +image/jpeg: \ + description=JPEG Image;\ + file_extensions=.jfif,.jfif-tbnl,.jpe,.jpg,.jpeg;\ + icon=jpeg;\ + action=browser;\ + application=imagetool %s + +image/tiff: \ + description=TIFF Image;\ + file_extensions=.tif,.tiff;\ + icon=tiff + +image/vnd.fpx: \ + description=FlashPix Image;\ + file_extensions=.fpx,.fpix + +image/x-cmu-rast: \ + description=CMU Raster Image;\ + file_extensions=.ras + +image/x-portable-anymap: \ + description=PBM Anymap Format;\ + file_extensions=.pnm + +image/x-portable-bitmap: \ + description=PBM Bitmap Format;\ + file_extensions=.pbm + +image/x-portable-graymap: \ + description=PBM Graymap Format;\ + file_extensions=.pgm + +image/x-portable-pixmap: \ + description=PBM Pixmap Format;\ + file_extensions=.ppm + +image/x-rgb: \ + description=RGB Image;\ + file_extensions=.rgb + +image/x-xbitmap: \ + description=X Bitmap Image;\ + file_extensions=.xbm,.xpm + +image/x-xwindowdump: \ + description=X Window Dump Image;\ + file_extensions=.xwd + +image/png: \ + description=PNG Image;\ + file_extensions=.png;\ + icon=png;\ + action=browser + +image/bmp: \ + description=Bitmap Image;\ + file_extensions=.bmp; + +text/html: \ + description=HTML Document;\ + file_extensions=.htm,.html;\ + icon=html + +text/plain: \ + description=Plain Text;\ + file_extensions=.text,.c,.cc,.c++,.h,.pl,.txt,.java,.el;\ + icon=text;\ + action=browser + +text/tab-separated-values: \ + description=Tab Separated Values Text;\ + file_extensions=.tsv + +text/x-setext: \ + description=Structure Enhanced Text;\ + file_extensions=.etx + +video/mpeg: \ + description=MPEG Video Clip;\ + file_extensions=.mpg,.mpe,.mpeg;\ + icon=mpeg;\ + action=application;\ + application=mpeg_play %s + +video/quicktime: \ + description=QuickTime Video Clip;\ + file_extensions=.mov,.qt + +application/x-troff-msvideo: \ + description=AVI Video;\ + file_extensions=.avi;\ + icon=avi + +video/x-sgi-movie: \ + description=SGI Movie;\ + file_extensions=.movie,.mv + +message/rfc822: \ + description=Internet Email Message;\ + file_extensions=.mime + +application/xml: \ + description=XML document;\ + file_extensions=.xml + + + diff --git a/jdk-1.8.0.281/jre/lib/currency.data b/jdk-1.8.0.281/jre/lib/currency.data new file mode 100755 index 0000000..7968b48 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/currency.data differ diff --git a/jdk-1.8.0.281/jre/lib/deploy.jar b/jdk-1.8.0.281/jre/lib/deploy.jar new file mode 100755 index 0000000..77b9910 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/deploy.jar differ diff --git a/jdk-1.8.0.281/jre/lib/deploy/MixedCodeMainDialog.ui b/jdk-1.8.0.281/jre/lib/deploy/MixedCodeMainDialog.ui new file mode 100755 index 0000000..b3f3f40 --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/deploy/MixedCodeMainDialog.ui @@ -0,0 +1,154 @@ + + + Title + FALSE + FALSE + 500 + 225 + FALSE + + + + + + + + + + Header + 400 + TRUE + + + + + + 75 + 10 + + + + + + appLabel + + + + + + 75 + 45 + + + + + + appTitle + + + 170 + 45 + + + + + + mixcode_s.png + + + 10 + 10 + + + + + + cautionshield.icns + + + 10 + 170 + + + + + + message + 480 + true + + + 10 + 90 + + + + + + info + 150 + true + + + + + + 60 + 165 + + + + + + 90 + + + block + + + + + 275 + 170 + + + + + + 90 + + + dontblock + + + + + 380 + 170 + + + + + + + + help + + + + + + + + 55 + 198 + + + + + + + + + + diff --git a/jdk-1.8.0.281/jre/lib/deploy/MixedCodeMainDialogJs.ui b/jdk-1.8.0.281/jre/lib/deploy/MixedCodeMainDialogJs.ui new file mode 100755 index 0000000..2e0a0be --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/deploy/MixedCodeMainDialogJs.ui @@ -0,0 +1,210 @@ + + + Title + FALSE + FALSE + 505 + 255 + FALSE + + + + + + + + + + Header + 400 + TRUE + + + + + + 75 + 10 + + + + + + websitelabel + + + + + + 75 + 55 + + + + + + websiteText + + + 175 + 55 + + + + + + appLabel + + + + + + 75 + 80 + + + + + + appTitle + + + 175 + 80 + + + + + + publisherLabel + + + + + + 75 + 95 + + + + + + publisherText + + + 175 + 95 + + + + + + mixcode_s.png + + + 10 + 10 + + + + + + cautionshield.icns + + + 10 + 200 + + + + + + message + 480 + true + + + 10 + 120 + + + + + + always + + + 10 + 175 + + + + + + info + 150 + true + + + + + + 60 + 195 + + + + + + 90 + + + block + + + + + 275 + 205 + + + + + + 115 + + + dontblock + + + + + 375 + 205 + + + + + + + + help + + + + + + + + 55 + 215 + + + + + + + + + + diff --git a/jdk-1.8.0.281/jre/lib/deploy/cautionshield.icns b/jdk-1.8.0.281/jre/lib/deploy/cautionshield.icns new file mode 100755 index 0000000..d703fc9 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/deploy/cautionshield.icns differ diff --git a/jdk-1.8.0.281/jre/lib/deploy/java-icon.ico b/jdk-1.8.0.281/jre/lib/deploy/java-icon.ico new file mode 100755 index 0000000..f98f780 Binary files /dev/null and b/jdk-1.8.0.281/jre/lib/deploy/java-icon.ico differ diff --git a/jdk-1.8.0.281/jre/lib/deploy/messages.properties b/jdk-1.8.0.281/jre/lib/deploy/messages.properties new file mode 100755 index 0000000..408b2a8 --- /dev/null +++ b/jdk-1.8.0.281/jre/lib/deploy/messages.properties @@ -0,0 +1,57 @@ +# +# Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. +# + +error.internal.badmsg=internal error, unknown message +error.badinst.nojre=Bad installation. No JRE found in configuration file +error.launch.execv=Error encountered while invoking Java Web Start (execv) +error.launch.sysexec=Error encountered while invoking Java Web Start (SysExec) +error.listener.failed=Splash: sysCreateListenerSocket failed +error.accept.failed=Splash: accept failed +error.recv.failed=Splash: recv failed +error.invalid.port=Splash: didn't revive a valid port +error.read=Read past end of buffer +error.xmlparsing=XML Parsing error: wrong kind of token found +error.splash.exit=Java Web Start splash screen process exiting .....\n +# "Last WinSock Error" means the error message for the last operation that failed. +error.winsock=\tLast WinSock Error: +error.winsock.load=Couldn't load winsock.dll +error.winsock.start=WSAStartup failed +error.badinst.nohome=Bad installation: JAVAWS_HOME not set +error.splash.noimage=Splash: couldn't load splash screen image +error.splash.socket=Splash: server socket failed +error.splash.cmnd=Splash: unrecognized command +error.splash.port=Splash: port not specified +error.splash.send=Splash: send failed +error.splash.timer=Splash: couldn't create shutdown timer +error.splash.x11.open=Splash: Can't open X11 display +error.splash.x11.connect=Splash: X11 connection failed +# Javaws usage: '\' is a joining of two sentence,which are connected including +# the invisible character '\n'. +message.javaws.usage=\n\ +Usage:\tjavaws [run-options] \n\ + \tjavaws [control-options] \n\ + \n\ +where run-options include: \n\ + -verbose \tdisplay additional output \n\ + -offline \trun the application in offline mode \n\ + -system \trun the application from the system cache only\n\ + -Xnosplash \trun without showing a splash screen \n\ + -J

+# Be careful when changing jdkhome. +# There are two VisualVM launchers for Windows (32-bit and 64-bit) and +# installer points to one of those in the VisualVM application shortcut +# based on the Java version selected at installation time. +# +#visualvm_jdkhome="/path/to/jdk" + +# Additional module clusters: +# using ${path.separator} (';' on Windows or ':' on Unix): +# +#visualvm_extraclusters="/absolute/path/to/cluster1:/absolute/path/to/cluster2" diff --git a/jdk-1.8.0.281/lib/visualvm/platform/.lastModified b/jdk-1.8.0.281/lib/visualvm/platform/.lastModified new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/platform/VERSION.txt b/jdk-1.8.0.281/lib/visualvm/platform/VERSION.txt new file mode 100755 index 0000000..585f568 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/VERSION.txt @@ -0,0 +1,2 @@ +# cluster incompatible release version +19 diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-core.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-core.xml new file mode 100755 index 0000000..e4621f5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-core.xml @@ -0,0 +1,99 @@ + + + + + + + + + Xerces is now available only as an autoload module, not in classpath: http://libs.netbeans.org/#xerces + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Regexp is now available only as an autoload module compiled manually from libs/regexp in the release40 branch, not on classpath: http://libs.netbeans.org/#regexp + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-modules-options-api.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-modules-options-api.xml new file mode 100755 index 0000000..00a4b74 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-modules-options-api.xml @@ -0,0 +1,24 @@ + + + + + + + + + Major release version of module changed from 0 to 1 to signal stability; update your dependencies + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-modules-queries.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-modules-queries.xml new file mode 100755 index 0000000..303f7ee --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-netbeans-modules-queries.xml @@ -0,0 +1,21 @@ + + + + + + Major release version of module changed from 0 to 1 to signal stability; update your dependencies + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-execution.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-execution.xml new file mode 100755 index 0000000..e2a0dde --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-execution.xml @@ -0,0 +1,26 @@ + + + + + + + + + + Separation of Execution API: cf. http://www.netbeans.org/download/dev/javadoc/OpenAPIs/org/openide/doc-files/upgrade.html#4.0-execution + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-explorer.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-explorer.xml new file mode 100755 index 0000000..6c9ce7e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-explorer.xml @@ -0,0 +1,24 @@ + + + + + + + + #88769 Incompatible change due to removal of PropertySheetSettings + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-filesystems.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-filesystems.xml new file mode 100755 index 0000000..e3498f5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-filesystems.xml @@ -0,0 +1,24 @@ + + + + + + + + FileObject implements Lookup.Provider + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-loaders.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-loaders.xml new file mode 100755 index 0000000..3940369 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-loaders.xml @@ -0,0 +1,24 @@ + + + + + + + + No need for separate templates API. Merged into org.openide.loaders + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-modules.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-modules.xml new file mode 100755 index 0000000..76da495 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-modules.xml @@ -0,0 +1,42 @@ + + + + + + + + openide.jar split into smaller parts. See http://openide.netbeans.org/proposals/arch/modularize.html and use 'ant fix-dependencies' if your project is projectized. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-nodes.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-nodes.xml new file mode 100755 index 0000000..095797c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-nodes.xml @@ -0,0 +1,24 @@ + + + + + + + + SaveCookie extends Savable. To compile you need to include openide.awt on classpath. + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-text.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-text.xml new file mode 100755 index 0000000..14ab052 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-text.xml @@ -0,0 +1,24 @@ + + + + + + + + #88531 Remove SystemOption usage from PrintSettings + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-util.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-util.xml new file mode 100755 index 0000000..50093e7 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/ModuleAutoDeps/org-openide-util.xml @@ -0,0 +1,24 @@ + + + + + + + + #170056: Separate module for Lookup API + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-annotations-common.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-annotations-common.xml new file mode 100755 index 0000000..9905e12 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-annotations-common.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-api-annotations-common.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-progress.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-progress.xml new file mode 100755 index 0000000..722b790 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-progress.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-api-progress.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-search.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-search.xml new file mode 100755 index 0000000..198a79e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-search.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-api-search.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-visual.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-visual.xml new file mode 100755 index 0000000..429c79d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-api-visual.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-api-visual.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-execution.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-execution.xml new file mode 100755 index 0000000..1788b07 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-execution.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-core-execution.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-io-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-io-ui.xml new file mode 100755 index 0000000..8d5dc43 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-io-ui.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-core-io-ui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-multitabs.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-multitabs.xml new file mode 100755 index 0000000..f68e889 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-multitabs.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-core-multitabs.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-multiview.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-multiview.xml new file mode 100755 index 0000000..e64dfef --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-multiview.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-core-multiview.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-output2.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-output2.xml new file mode 100755 index 0000000..27f76ef --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-output2.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-core-output2.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-ui.xml new file mode 100755 index 0000000..83b2f53 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-ui.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-core-ui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-windows.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-windows.xml new file mode 100755 index 0000000..cf49629 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core-windows.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-core-windows.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core.xml new file mode 100755 index 0000000..6f60d4c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-core.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-core.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-lib-uihandler.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-lib-uihandler.xml new file mode 100755 index 0000000..7a8a225 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-lib-uihandler.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-lib-uihandler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-applemenu.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-applemenu.xml new file mode 100755 index 0000000..daefdc4 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-applemenu.xml @@ -0,0 +1,9 @@ + + + + false + true + modules/org-netbeans-modules-applemenu.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-cli.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-cli.xml new file mode 100755 index 0000000..7ed3230 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-cli.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-autoupdate-cli.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-services.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-services.xml new file mode 100755 index 0000000..f362b0e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-services.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-autoupdate-services.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-ui.xml new file mode 100755 index 0000000..2dd451a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-autoupdate-ui.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-autoupdate-ui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-core-kit.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-core-kit.xml new file mode 100755 index 0000000..c13b294 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-core-kit.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-core-kit.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-editor-mimelookup-impl.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-editor-mimelookup-impl.xml new file mode 100755 index 0000000..d91c6c0 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-editor-mimelookup-impl.xml @@ -0,0 +1,9 @@ + + + + false + true + modules/org-netbeans-modules-editor-mimelookup-impl.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-editor-mimelookup.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-editor-mimelookup.xml new file mode 100755 index 0000000..d880d28 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-editor-mimelookup.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-editor-mimelookup.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-favorites.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-favorites.xml new file mode 100755 index 0000000..f50bf82 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-favorites.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-favorites.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-javahelp.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-javahelp.xml new file mode 100755 index 0000000..7dc7a27 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-javahelp.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-javahelp.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring-fallback.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring-fallback.xml new file mode 100755 index 0000000..3447cb1 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring-fallback.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-keyring-fallback.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring-impl.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring-impl.xml new file mode 100755 index 0000000..106b56e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring-impl.xml @@ -0,0 +1,9 @@ + + + + false + true + modules/org-netbeans-modules-keyring-impl.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring.xml new file mode 100755 index 0000000..d6247d0 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-keyring.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-keyring.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-masterfs-nio2.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-masterfs-nio2.xml new file mode 100755 index 0000000..692cd19 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-masterfs-nio2.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-masterfs-nio2.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-masterfs.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-masterfs.xml new file mode 100755 index 0000000..8617bef --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-masterfs.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-masterfs.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-options-api.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-options-api.xml new file mode 100755 index 0000000..f899091 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-options-api.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-options-api.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-options-keymap.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-options-keymap.xml new file mode 100755 index 0000000..9895aeb --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-options-keymap.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-options-keymap.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-print.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-print.xml new file mode 100755 index 0000000..c72c4ea --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-print.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-print.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-progress-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-progress-ui.xml new file mode 100755 index 0000000..6b3fbb5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-progress-ui.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-progress-ui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-queries.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-queries.xml new file mode 100755 index 0000000..ad07474 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-queries.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-queries.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-sampler.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-sampler.xml new file mode 100755 index 0000000..6f318ea --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-sampler.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-sampler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-sendopts.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-sendopts.xml new file mode 100755 index 0000000..5c3fff5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-sendopts.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-sendopts.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-settings.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-settings.xml new file mode 100755 index 0000000..13cb306 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-settings.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-settings.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-spi-actions.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-spi-actions.xml new file mode 100755 index 0000000..4d850e3 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-spi-actions.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-spi-actions.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-templates.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-templates.xml new file mode 100755 index 0000000..dd5d0fa --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-templates.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-templates.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-uihandler.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-uihandler.xml new file mode 100755 index 0000000..41e5707 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-modules-uihandler.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-uihandler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-spi-quicksearch.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-spi-quicksearch.xml new file mode 100755 index 0000000..fbaf9d4 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-spi-quicksearch.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-spi-quicksearch.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-outline.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-outline.xml new file mode 100755 index 0000000..b8e54df --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-outline.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-swing-outline.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-plaf.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-plaf.xml new file mode 100755 index 0000000..ccc5b65 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-plaf.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-swing-plaf.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-tabcontrol.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-tabcontrol.xml new file mode 100755 index 0000000..00d4a7a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-netbeans-swing-tabcontrol.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-swing-tabcontrol.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-actions.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-actions.xml new file mode 100755 index 0000000..ff99ac1 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-actions.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-actions.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-awt.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-awt.xml new file mode 100755 index 0000000..ecfac0a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-awt.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-awt.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-compat.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-compat.xml new file mode 100755 index 0000000..f07d7e9 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-compat.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-compat.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-dialogs.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-dialogs.xml new file mode 100755 index 0000000..4da14d6 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-dialogs.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-dialogs.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-execution.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-execution.xml new file mode 100755 index 0000000..2d21d0e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-execution.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-execution.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-explorer.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-explorer.xml new file mode 100755 index 0000000..57dcf22 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-explorer.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-explorer.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-io.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-io.xml new file mode 100755 index 0000000..9ca37fc --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-io.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-io.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-loaders.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-loaders.xml new file mode 100755 index 0000000..3c75fd0 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-loaders.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-loaders.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-nodes.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-nodes.xml new file mode 100755 index 0000000..81860f2 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-nodes.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-nodes.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-options.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-options.xml new file mode 100755 index 0000000..75806bf --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-options.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-options.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-text.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-text.xml new file mode 100755 index 0000000..857ebe6 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-text.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-text.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-util-enumerations.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-util-enumerations.xml new file mode 100755 index 0000000..7ad07a0 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-util-enumerations.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-util-enumerations.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-windows.xml b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-windows.xml new file mode 100755 index 0000000..fce2109 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/config/Modules/org-openide-windows.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-openide-windows.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/core/core.jar b/jdk-1.8.0.281/lib/visualvm/platform/core/core.jar new file mode 100755 index 0000000..4f46309 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/core/core.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/core/locale/core_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/core_ja.jar new file mode 100755 index 0000000..226b351 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/core_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/core/locale/core_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/core_zh_CN.jar new file mode 100755 index 0000000..64694ee Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/core_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/core/locale/org-openide-filesystems_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/org-openide-filesystems_ja.jar new file mode 100755 index 0000000..f012c78 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/org-openide-filesystems_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/core/locale/org-openide-filesystems_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/org-openide-filesystems_zh_CN.jar new file mode 100755 index 0000000..960ffc5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/core/locale/org-openide-filesystems_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/core/org-openide-filesystems.jar b/jdk-1.8.0.281/lib/visualvm/platform/core/org-openide-filesystems.jar new file mode 100755 index 0000000..3ec1a2e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/core/org-openide-filesystems.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/boot.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/boot.jar new file mode 100755 index 0000000..afa6a3f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/boot.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/boot_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/boot_ja.jar new file mode 100755 index 0000000..f58bea4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/boot_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/boot_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/boot_zh_CN.jar new file mode 100755 index 0000000..6bb2522 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/boot_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-modules_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-modules_ja.jar new file mode 100755 index 0000000..380e2e8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-modules_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-modules_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-modules_zh_CN.jar new file mode 100755 index 0000000..7adcbc1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-modules_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util-lookup_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util-lookup_ja.jar new file mode 100755 index 0000000..f73f4b7 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util-lookup_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util-lookup_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util-lookup_zh_CN.jar new file mode 100755 index 0000000..ab412f4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util-lookup_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util_ja.jar new file mode 100755 index 0000000..f03f7b2 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util_zh_CN.jar new file mode 100755 index 0000000..f7c2047 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/locale/org-openide-util_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/nbexec b/jdk-1.8.0.281/lib/visualvm/platform/lib/nbexec new file mode 100755 index 0000000..a3e5bfb --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/lib/nbexec @@ -0,0 +1,463 @@ +#!/bin/sh +# Copyright (c) 1992, 2014, Oracle and/or its affiliates. All rights reserved. +# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. + + +PRG=$0 + + +resolve_symlink () { + file="$1" + while [ -h "$file" ]; do + ls=`ls -ld "$file"` + link=`expr "$ls" : '^.*-> \(.*\)$' 2>/dev/null` + if expr "$link" : '^/' 2> /dev/null >/dev/null; then + file="$link" + else + file=`dirname "$1"`"/$link" + fi + done + echo "$file" +} + +absolutize_path () { + oldpwd=`pwd` + cd "$1" + abspath=`pwd` + cd "${oldpwd}" + echo "$abspath" +} + +PRG=`resolve_symlink "$PRG"` +progdir=`dirname "$PRG"` +plathome=`absolutize_path "$progdir/.."` + +jargs=${jreflags} +jargs="$jargs -Dnetbeans.home=\"$plathome\"" + +args="" + +launcher_args="" + +prefixcp="" +postfixcp="" + +updater_class=org.netbeans.updater.UpdaterFrame + +# +# parse arguments +# + +parse_args() { +while [ $# -gt 0 ] ; do + case "$1" in + -h|-\?|-help|--help) cat >&2 < path to Java(TM) 2 SDK, Standard Edition + -J pass to JVM + + --cp:p prepend to classpath + --cp:a append to classpath +EOF + # go on and print IDE options as well + args="$args --help" + ;; + --nosplash) + nosplash="nosplash"; + args="$args --nosplash" + ;; + --jdkhome) shift; if [ $# -gt 0 ] ; then jdkhome=$1; fi + ;; + # this has to be here for purposes of updater.jar, but it should be + # better to handle this argument inside the java launcher part + --userdir) shift; if [ $# -gt 0 ] ; then userdir="$1"; fi + ;; + --cachedir) shift; if [ $# -gt 0 ] ; then cachedir="$1"; cachedirspecified="specified" ; fi + ;; + -cp|-cp:a|--cp|--cp:a) + shift; + if [ $# -gt 0 ] ; then + if [ ! -z "$postfixcp" ] ; then postfixcp="$postfixcp:" ; fi + postfixcp=$postfixcp$1; + fi + ;; + + -cp:p|--cp:p) + shift; + if [ $# -gt 0 ] ; then + if [ ! -z "$prefixcp" ] ; then prefixcp="$prefixcp:" ; fi + prefixcp=$prefixcp$1; + fi + ;; + --clusters) + shift; + if [ $# -gt 0 ] ; then + clusters="$1" + fi + ;; + -psn*) + shift; + ;; + -L*) lopt=`expr "X-$1" : 'X--L\(.*\)'`; launcher_args="$launcher_args '$lopt'";; + -J*) jopt=`expr "X-$1" : 'X--J\(.*\)'`; jargs="$jargs '$jopt'";; + *) args="$args \"$1\"" ;; + esac + shift +done +} # parse_args() + +# Process arguments given on the command line. +parse_args "$@" + +# +# check JDK +# + +if [ -z "$jdkhome" ] ; then + # try to find JDK + case "`uname`" in + Darwin*) + # read Java Preferences + if [ -x "/usr/libexec/java_home" ]; then + jdkhome=`/usr/libexec/java_home --version 1.7.0_10+ --failfast` + + # JDK1.7 Update 10 as a fallback + elif [ -f "/Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/bin/java" ] ; then + jdkhome="/Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home" + fi + + # JRE fallback + if [ ! -x "${jdkhome}/bin/java" -a -f "/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java" ] ; then + jdkhome="/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home" + fi + ;; + *) javac=`which javac` + if [ -z "$javac" ] ; then + java=`which java` + if [ ! -z "$java" ] ; then + java=`resolve_symlink "$java"` + jdkhome=`dirname $java`"/.." + fi + else + javac=`resolve_symlink "$javac"` + jdkhome=`dirname $javac`"/.." + fi + ;; + esac +fi + +if [ ! -x "${jdkhome}/bin/java" ] ; then + echo "Cannot find java. Please use the --jdkhome switch." >&2 + exit 2 +fi + +if [ -n "$launcher_args" ] ; then + case "`uname`" in + SunOS*) awk=nawk ;; + *) awk=awk ;; + esac + jdk_version=$("${jdkhome}/bin/java" -version 2>&1 | "/usr/bin/${awk}" -F '"' '/version/ {print substr($2, 1, 3)}') + if [ "$jdk_version" = "1.7" ] ; then + jargs="$jargs $launcher_args" + fi +fi + + +# Make sure native code libraries of jdk7 are found +# setting of the LD_LIBRARY_PATH is unnecessary on JDK8, and should be removed when only JDK8 is supported: +case "`uname`" in + SunOS*) + LD_LIBRARY_PATH=${jdkhome}/jre/lib/amd64/client:${jdkhome}/jre/lib/amd64/server:${jdkhome}/jre/lib/i386/client:${jdkhome}/jre/lib/i386/server:${LD_LIBRARY_PATH} + export LD_LIBRARY_PATH + ;; + *) + LD_LIBRARY_PATH=${jdkhome}/jre/lib/amd64:${jdkhome}/jre/lib/i386:${LD_LIBRARY_PATH} + export LD_LIBRARY_PATH + ;; +esac + +# fixes 225762: Can't open project from a folder with UTF-8 letters on Mac OS X +if [ `uname` = "Darwin" ] ; then + if [ x${LC_CTYPE} = x ] ; then + export LC_CTYPE=UTF-8; + fi +fi + +jargs="$jargs -XX:+HeapDumpOnOutOfMemoryError" +if [ -z "`echo $jargs | grep -- "-XX:HeapDumpPath="`" ] ; then + jargs="$jargs -XX:HeapDumpPath=\"${userdir}/var/log/heapdump.hprof\"" +fi +# rename old heap dump to .old +mv "${userdir}/var/log/heapdump.hprof" "${userdir}/var/log/heapdump.hprof.old" > /dev/null 2>&1 + +jargs_without_clusters="$jargs" +jargs="-Dnetbeans.dirs=\"${clusters}\" $jargs_without_clusters" + +if [ -z "$cachedirspecified" ]; then + cachedir="${userdir}/var/cache" +fi + +if [ `uname` != Darwin -a -z "$nosplash" -a -f "${cachedir}/splash.png" -a ! -f "${userdir}/lock" ]; then + jargs="$jargs -splash:\"${cachedir}/splash.png\"" +fi + +jdkhome=`absolutize_path "$jdkhome"` + +args="--userdir \"${userdir}\" $args" + +args="--cachedir \"${cachedir}\" $args" + +append_jars_to_cp() { + dir="$1" + subpath="$2" + for ex in jar zip ; do + if [ "`echo "${dir}"/*.$ex`" != "${dir}/*.$ex" ] ; then + for x in "${dir}"/*.$ex ; do + subx=`basename "$x"` + if [ -z "`echo "$paths" | egrep "$subpath$subx"`" ] ; then + if [ ! -z "$cp" ] ; then cp="$cp:" ; fi + cp="$cp$x" + if [ ! -z "$paths" ] ; then paths="$paths:" ; fi + paths="$paths$subpath$subx" + fi + done + fi + done +} + +construct_cp() { + cp="" + updatercp="" + paths="" + + build_cp "${userdir}" + build_cp "${plathome}" + + if [ -f "${userdir}/modules/ext/updater.jar" ] ; then + updatercp="${userdir}/modules/ext/updater.jar" + else + if [ -f "${plathome}/modules/ext/updater.jar" ] ; then + updatercp="${plathome}/modules/ext/updater.jar" + fi + fi + + # JDK tools + for x in "${jdkhome}/lib/dt.jar" "${jdkhome}/lib/tools.jar"; do + if [ -f "$x" ]; then + if [ ! -z "$cp" ] ; then cp="$cp:" ; fi + cp="${cp}$x" + fi + done + + # user-specified prefix and postfix CLASSPATH + + if [ ! -z "${prefixcp}" ] ; then + cp="${prefixcp}:$cp" + fi + + if [ ! -z "${postfixcp}" ] ; then + cp="$cp:${postfixcp}" + fi + + + # prepend IDE's classpath to updater's classpath + # (just xml-apis.jar and one XML parser would suffice) + if [ ! -z "$updatercp" ] ; then + updatercp=${cp}:${updatercp} + else + updatercp=${cp} + fi +} + +build_cp() { + base="$1" + append_jars_to_cp "${base}/lib/patches" "patches" + append_jars_to_cp "${base}/lib" "lib" + append_jars_to_cp "${base}/lib/locale" "locale" +} + +do_run_updater() { + eval "\"$jdkhome/bin/java\"" -classpath "\"${updatercp}\"" "$jargs" "-Dnetbeans.user=\"$userdir\"" $updater_class "$args" + construct_cp +} + +look_for_pre_runs() { + base="$1" + install_new_updater "$1" + dir="${base}/update/download" + if [ "`echo "${dir}"/*.nbm`" != "${dir}/*.nbm" -o "`echo "${dir}"/*.jar`" != "${dir}/*.jar" ] ; then + run_updater=yes + else + dir="${base}/update/deactivate" + if [ -f "${dir}/to_disable.txt" -o -f "${dir}/to_uninstall.txt" ] ; then + run_updater=yes + fi + fi +} + +look_for_post_runs() { + base="$1" + install_new_updater "$1" + dir="${base}/update/download" + if [ \! -f "${dir}/install_later.xml" ] && [ "`echo "${dir}"/*.nbm`" != "${dir}/*.nbm" -o "`echo "${dir}"/*.jar`" != "${dir}/*.jar" ] ; then + run_updater=yes + else + dir="${base}/update/deactivate" + if [ \! -f "${dir}/deactivate_later.txt" ] ; then + if [ -f "${dir}/to_disable.txt" -o -f "${dir}/to_uninstall.txt" ] ; then + run_updater=yes + fi + fi + fi +} + +look_for_new_clusters() { + base="$userdir" + dir="${base}/update/download" + newclusters="${dir}/netbeans.dirs" + if [ -f "${newclusters}" ] ; then + clusters=`cat "${newclusters}"` + jargs="-Dnetbeans.dirs=\"${clusters}\" $jargs_without_clusters" + rm -f "${newclusters}" + fi +} + +delete_new_clusters_file() { + base="$userdir" + dir="${base}/update/download" + newclusters="${dir}/netbeans.dirs" + if [ \! -f "${newclusters}" ] ; then + rm -f "${newclusters}" + fi +} + +install_new_updater() { + base="$1" + newUpdaterDir="${base}/update/new_updater" + if [ -d "${newUpdaterDir}" ]; then + mkdir -p "${base}/modules/ext/" + if [ -f "${newUpdaterDir}/updater.jar" ]; then + mv -f "${newUpdaterDir}/updater.jar" "${base}/modules/ext/" + fi + for i in "${newUpdaterDir}/locale/"updater_*.jar; do + if [ -f "$i" ]; then + mkdir -p "${base}/modules/ext/locale/" + mv -f "$i" "${base}/modules/ext/locale/" + fi + done + rmdir "${newUpdaterDir}" + fi +} + +if [ "$KDE_FULL_SESSION" = "true" ] ; then + jargs="-Dnetbeans.running.environment=kde $jargs" +else + if [ ! -z "$GNOME_DESKTOP_SESSION_ID" ] ; then + jargs="-Dnetbeans.running.environment=gnome $jargs" + fi +fi + +if [ ! -z "${DEFAULT_USERDIR_ROOT}" ] ; then + jargs="-Dnetbeans.default_userdir_root=\"${DEFAULT_USERDIR_ROOT}\" $jargs" + unset DEFAULT_USERDIR_ROOT +fi + +# http://java.sun.com/j2se/1.5.0/docs/guide/2d/flags.html#pixmaps +J2D_PIXMAPS=shared +export J2D_PIXMAPS + +# Check DISPLAY variable on non-Mac +if [ "no$DISPLAY" = "no" -a `uname` != Darwin ]; then + echo "$0: WARNING: environment variable DISPLAY is not set" +fi + + +# The Startup Notification Protocol Specification [1] +# recommends to unset the DESKTOP_STARTUP_ID environment variable +# to avoid possible reuse by some process started later by this +# process, e.g. when a browser will be launched by the NetBeans [2]. +# +# See: +# [1] http://standards.freedesktop.org/startup-notification-spec +# [2] http://netbeans.org/bugzilla/show_bug.cgi?id=76970 +if [ ! -z "$DESKTOP_STARTUP_ID" ] ; then + # Save a value for later using + NB_DESKTOP_STARTUP_ID="$DESKTOP_STARTUP_ID"; export NB_DESKTOP_STARTUP_ID + + unset DESKTOP_STARTUP_ID +fi + + +# +# main loop +# + +# clear to prevent loop from ending +restart="yes" +first_time_starting="yes" +restart_file="${userdir}/var/restart" + +while [ "$restart" ] ; do + + # + # build CLASSPATH + # + construct_cp + + # First check for pre-run updates. + if [ "$first_time_starting" ] ; then + run_updater="" + look_for_pre_runs "$plathome" + save="$IFS" + IFS=':' ; for oneCls in $clusters ; do + IFS="$save" + look_for_pre_runs "$oneCls" + done + IFS="$save" + look_for_pre_runs "$userdir" + if [ "$run_updater" ] ; then do_run_updater ; fi + # Do not check this after a restart, it makes no sense. + first_time_starting="" + fi + + # + # let's go + # + delete_new_clusters_file + rm -f "${restart_file}" + eval ${_NB_PROFILE_CMD} "\"${jdkhome}/bin/java\"" -Djdk.home="\"${jdkhome}\"" -classpath "\"$cp\"" \ + "$jargs" org.netbeans.Main "$args" '<&0' '&' + PID=$! + trap "kill $PID" EXIT + wait $PID + exitcode=$? + trap '' EXIT + look_for_new_clusters + # If we should update anything, do it and restart IDE. + run_updater="" + look_for_post_runs "$plathome" + + save="$IFS" + IFS=':' ; for oneCls in $clusters ; do + IFS="$save" + look_for_post_runs "$oneCls" + done + IFS="$save" + look_for_post_runs "$userdir" + if [ "$run_updater" ] ; then + do_run_updater + restart="yes" + else + if [ ! -f "${restart_file}" ] ; then + # will fall thru loop and exit + restart="" + fi + fi + +done + +# and we exit. +exit $exitcode diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-modules.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-modules.jar new file mode 100755 index 0000000..961ce06 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-modules.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-util-lookup.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-util-lookup.jar new file mode 100755 index 0000000..dea101f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-util-lookup.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-util.jar b/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-util.jar new file mode 100755 index 0000000..a2e1de4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/lib/org-openide-util.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/jhall-2.0_05.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/jhall-2.0_05.jar new file mode 100755 index 0000000..85965f5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/jhall-2.0_05.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/locale/updater_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/locale/updater_ja.jar new file mode 100755 index 0000000..9f4299e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/locale/updater_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/locale/updater_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/locale/updater_zh_CN.jar new file mode 100755 index 0000000..1e562c1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/locale/updater_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/updater.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/updater.jar new file mode 100755 index 0000000..0e3bc47 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/ext/updater.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-annotations-common_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-annotations-common_ja.jar new file mode 100755 index 0000000..0c12408 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-annotations-common_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-annotations-common_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-annotations-common_zh_CN.jar new file mode 100755 index 0000000..15d9ee3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-annotations-common_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-progress_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-progress_ja.jar new file mode 100755 index 0000000..7b3329b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-progress_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-progress_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-progress_zh_CN.jar new file mode 100755 index 0000000..e0100ee Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-progress_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-search_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-search_ja.jar new file mode 100755 index 0000000..b73866b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-search_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-search_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-search_zh_CN.jar new file mode 100755 index 0000000..386cf2e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-search_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-visual_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-visual_ja.jar new file mode 100755 index 0000000..b3d7622 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-visual_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-visual_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-visual_zh_CN.jar new file mode 100755 index 0000000..b27f9a8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-api-visual_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-execution_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-execution_ja.jar new file mode 100755 index 0000000..304e4a8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-execution_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-execution_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-execution_zh_CN.jar new file mode 100755 index 0000000..e74380a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-execution_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-io-ui_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-io-ui_ja.jar new file mode 100755 index 0000000..b8c3c52 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-io-ui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-io-ui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-io-ui_zh_CN.jar new file mode 100755 index 0000000..c51fdf2 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-io-ui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multitabs_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multitabs_ja.jar new file mode 100755 index 0000000..1e71cb6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multitabs_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multitabs_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multitabs_zh_CN.jar new file mode 100755 index 0000000..74649d0 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multitabs_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multiview_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multiview_ja.jar new file mode 100755 index 0000000..16b345e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multiview_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multiview_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multiview_zh_CN.jar new file mode 100755 index 0000000..d2cbcd6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-multiview_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-output2_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-output2_ja.jar new file mode 100755 index 0000000..d40e600 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-output2_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-output2_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-output2_zh_CN.jar new file mode 100755 index 0000000..a24650c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-output2_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-ui_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-ui_ja.jar new file mode 100755 index 0000000..53a4c59 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-ui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-ui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-ui_zh_CN.jar new file mode 100755 index 0000000..3b3627b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-ui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-windows_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-windows_ja.jar new file mode 100755 index 0000000..472de46 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-windows_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-windows_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-windows_zh_CN.jar new file mode 100755 index 0000000..e2bef94 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core-windows_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core_ja.jar new file mode 100755 index 0000000..fe5774b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core_zh_CN.jar new file mode 100755 index 0000000..a93eb37 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-core_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-lib-uihandler_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-lib-uihandler_ja.jar new file mode 100755 index 0000000..829a8f3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-lib-uihandler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-lib-uihandler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-lib-uihandler_zh_CN.jar new file mode 100755 index 0000000..3e607de Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-lib-uihandler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-applemenu_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-applemenu_ja.jar new file mode 100755 index 0000000..06c805b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-applemenu_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-applemenu_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-applemenu_zh_CN.jar new file mode 100755 index 0000000..97a88eb Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-applemenu_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-cli_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-cli_ja.jar new file mode 100755 index 0000000..39d8de8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-cli_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-cli_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-cli_zh_CN.jar new file mode 100755 index 0000000..4874d39 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-cli_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-services_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-services_ja.jar new file mode 100755 index 0000000..680443a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-services_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-services_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-services_zh_CN.jar new file mode 100755 index 0000000..05b0ba9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-services_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-ui_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-ui_ja.jar new file mode 100755 index 0000000..4296830 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-ui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-ui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-ui_zh_CN.jar new file mode 100755 index 0000000..5b9a3fc Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-autoupdate-ui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-core-kit_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-core-kit_ja.jar new file mode 100755 index 0000000..5a23a03 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-core-kit_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-core-kit_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-core-kit_zh_CN.jar new file mode 100755 index 0000000..70aad83 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-core-kit_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup-impl_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup-impl_ja.jar new file mode 100755 index 0000000..b1376ab Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup-impl_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup-impl_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup-impl_zh_CN.jar new file mode 100755 index 0000000..53f43c5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup-impl_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup_ja.jar new file mode 100755 index 0000000..2a1cab9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup_zh_CN.jar new file mode 100755 index 0000000..2e4a083 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-editor-mimelookup_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-favorites_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-favorites_ja.jar new file mode 100755 index 0000000..60fae22 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-favorites_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-favorites_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-favorites_zh_CN.jar new file mode 100755 index 0000000..840fe72 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-favorites_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-javahelp_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-javahelp_ja.jar new file mode 100755 index 0000000..5e05c11 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-javahelp_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-javahelp_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-javahelp_zh_CN.jar new file mode 100755 index 0000000..80bb131 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-javahelp_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-fallback_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-fallback_ja.jar new file mode 100755 index 0000000..8a4b2f9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-fallback_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-fallback_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-fallback_zh_CN.jar new file mode 100755 index 0000000..9fe0841 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-fallback_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-impl_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-impl_ja.jar new file mode 100755 index 0000000..0b85c77 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-impl_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-impl_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-impl_zh_CN.jar new file mode 100755 index 0000000..0cd25b3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring-impl_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring_ja.jar new file mode 100755 index 0000000..49e886d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring_zh_CN.jar new file mode 100755 index 0000000..5148323 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-keyring_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs-nio2_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs-nio2_ja.jar new file mode 100755 index 0000000..852afc8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs-nio2_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs-nio2_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs-nio2_zh_CN.jar new file mode 100755 index 0000000..9253e7a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs-nio2_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs_ja.jar new file mode 100755 index 0000000..6bd1a65 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs_zh_CN.jar new file mode 100755 index 0000000..67fde5d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-masterfs_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-api_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-api_ja.jar new file mode 100755 index 0000000..b00b870 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-api_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-api_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-api_zh_CN.jar new file mode 100755 index 0000000..c70bf4a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-api_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-keymap_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-keymap_ja.jar new file mode 100755 index 0000000..7ce3fa3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-keymap_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-keymap_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-keymap_zh_CN.jar new file mode 100755 index 0000000..d89ba26 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-options-keymap_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-print_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-print_ja.jar new file mode 100755 index 0000000..b805753 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-print_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-print_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-print_zh_CN.jar new file mode 100755 index 0000000..47d919a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-print_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-progress-ui_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-progress-ui_ja.jar new file mode 100755 index 0000000..8d17c55 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-progress-ui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-progress-ui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-progress-ui_zh_CN.jar new file mode 100755 index 0000000..49d9183 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-progress-ui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-queries_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-queries_ja.jar new file mode 100755 index 0000000..3858756 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-queries_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-queries_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-queries_zh_CN.jar new file mode 100755 index 0000000..1eca3ca Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-queries_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sampler_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sampler_ja.jar new file mode 100755 index 0000000..0b3df71 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sampler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sampler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sampler_zh_CN.jar new file mode 100755 index 0000000..ae73dd2 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sampler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sendopts_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sendopts_ja.jar new file mode 100755 index 0000000..b77d4f5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sendopts_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sendopts_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sendopts_zh_CN.jar new file mode 100755 index 0000000..ac43f0c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-sendopts_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-settings_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-settings_ja.jar new file mode 100755 index 0000000..7efebf1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-settings_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-settings_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-settings_zh_CN.jar new file mode 100755 index 0000000..1443ae3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-settings_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-spi-actions_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-spi-actions_ja.jar new file mode 100755 index 0000000..c55b8f3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-spi-actions_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-spi-actions_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-spi-actions_zh_CN.jar new file mode 100755 index 0000000..4184880 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-spi-actions_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-templates_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-templates_ja.jar new file mode 100755 index 0000000..998f7c4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-templates_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-templates_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-templates_zh_CN.jar new file mode 100755 index 0000000..f27411b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-templates_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-uihandler_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-uihandler_ja.jar new file mode 100755 index 0000000..922cd82 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-uihandler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-uihandler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-uihandler_zh_CN.jar new file mode 100755 index 0000000..03f6ecf Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-modules-uihandler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-spi-quicksearch_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-spi-quicksearch_ja.jar new file mode 100755 index 0000000..cad7cd9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-spi-quicksearch_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-spi-quicksearch_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-spi-quicksearch_zh_CN.jar new file mode 100755 index 0000000..0b0dbc6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-spi-quicksearch_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-outline_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-outline_ja.jar new file mode 100755 index 0000000..ddc5f21 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-outline_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-outline_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-outline_zh_CN.jar new file mode 100755 index 0000000..a703280 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-outline_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-plaf_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-plaf_ja.jar new file mode 100755 index 0000000..2199ab5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-plaf_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-plaf_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-plaf_zh_CN.jar new file mode 100755 index 0000000..4a6998c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-plaf_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-tabcontrol_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-tabcontrol_ja.jar new file mode 100755 index 0000000..57fde1f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-tabcontrol_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-tabcontrol_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-tabcontrol_zh_CN.jar new file mode 100755 index 0000000..e01931b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-netbeans-swing-tabcontrol_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-actions_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-actions_ja.jar new file mode 100755 index 0000000..c75275f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-actions_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-actions_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-actions_zh_CN.jar new file mode 100755 index 0000000..49ff678 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-actions_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-awt_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-awt_ja.jar new file mode 100755 index 0000000..7a1733d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-awt_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-awt_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-awt_zh_CN.jar new file mode 100755 index 0000000..83ce9e9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-awt_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-compat_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-compat_ja.jar new file mode 100755 index 0000000..7c27005 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-compat_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-compat_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-compat_zh_CN.jar new file mode 100755 index 0000000..b8d657d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-compat_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-dialogs_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-dialogs_ja.jar new file mode 100755 index 0000000..935ae46 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-dialogs_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-dialogs_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-dialogs_zh_CN.jar new file mode 100755 index 0000000..b83f31d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-dialogs_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-execution_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-execution_ja.jar new file mode 100755 index 0000000..20300bc Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-execution_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-execution_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-execution_zh_CN.jar new file mode 100755 index 0000000..28cf818 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-execution_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-explorer_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-explorer_ja.jar new file mode 100755 index 0000000..ec29cb1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-explorer_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-explorer_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-explorer_zh_CN.jar new file mode 100755 index 0000000..3cf3921 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-explorer_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-io_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-io_ja.jar new file mode 100755 index 0000000..f2e27d6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-io_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-io_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-io_zh_CN.jar new file mode 100755 index 0000000..edf56ae Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-io_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-loaders_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-loaders_ja.jar new file mode 100755 index 0000000..915f39a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-loaders_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-loaders_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-loaders_zh_CN.jar new file mode 100755 index 0000000..652d0de Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-loaders_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-nodes_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-nodes_ja.jar new file mode 100755 index 0000000..7b5ec3f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-nodes_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-nodes_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-nodes_zh_CN.jar new file mode 100755 index 0000000..49645b6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-nodes_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-options_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-options_ja.jar new file mode 100755 index 0000000..07ba183 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-options_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-options_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-options_zh_CN.jar new file mode 100755 index 0000000..2c87e99 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-options_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-text_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-text_ja.jar new file mode 100755 index 0000000..3c46417 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-text_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-text_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-text_zh_CN.jar new file mode 100755 index 0000000..5b24e12 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-text_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-util-enumerations_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-util-enumerations_ja.jar new file mode 100755 index 0000000..adc8479 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-util-enumerations_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-util-enumerations_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-util-enumerations_zh_CN.jar new file mode 100755 index 0000000..5c3cbdc Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-util-enumerations_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-windows_ja.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-windows_ja.jar new file mode 100755 index 0000000..5af200a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-windows_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-windows_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-windows_zh_CN.jar new file mode 100755 index 0000000..3f94c35 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/locale/org-openide-windows_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-annotations-common.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-annotations-common.jar new file mode 100755 index 0000000..a9e5af8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-annotations-common.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-progress.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-progress.jar new file mode 100755 index 0000000..1aa5aed Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-progress.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-search.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-search.jar new file mode 100755 index 0000000..7bda9e2 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-search.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-visual.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-visual.jar new file mode 100755 index 0000000..aaa581a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-api-visual.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-execution.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-execution.jar new file mode 100755 index 0000000..65db431 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-execution.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-io-ui.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-io-ui.jar new file mode 100755 index 0000000..7d1aa75 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-io-ui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-multitabs.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-multitabs.jar new file mode 100755 index 0000000..f8a8bc7 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-multitabs.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-multiview.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-multiview.jar new file mode 100755 index 0000000..69c6270 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-multiview.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-output2.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-output2.jar new file mode 100755 index 0000000..f9582ef Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-output2.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-ui.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-ui.jar new file mode 100755 index 0000000..5946079 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-ui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-windows.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-windows.jar new file mode 100755 index 0000000..a17d4c6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core-windows.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core.jar new file mode 100755 index 0000000..df9b4af Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-core.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-lib-uihandler.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-lib-uihandler.jar new file mode 100755 index 0000000..d31ffeb Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-lib-uihandler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-applemenu.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-applemenu.jar new file mode 100755 index 0000000..164fb1c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-applemenu.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-cli.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-cli.jar new file mode 100755 index 0000000..007fb39 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-cli.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-services.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-services.jar new file mode 100755 index 0000000..8579478 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-services.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-ui.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-ui.jar new file mode 100755 index 0000000..2bda162 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-autoupdate-ui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-core-kit.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-core-kit.jar new file mode 100755 index 0000000..80745cc Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-core-kit.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-editor-mimelookup-impl.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-editor-mimelookup-impl.jar new file mode 100755 index 0000000..160eb03 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-editor-mimelookup-impl.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-editor-mimelookup.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-editor-mimelookup.jar new file mode 100755 index 0000000..5fa7dce Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-editor-mimelookup.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-favorites.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-favorites.jar new file mode 100755 index 0000000..2adea09 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-favorites.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-javahelp.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-javahelp.jar new file mode 100755 index 0000000..d1cfcd5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-javahelp.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring-fallback.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring-fallback.jar new file mode 100755 index 0000000..07ca29d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring-fallback.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring-impl.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring-impl.jar new file mode 100755 index 0000000..eff2ca3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring-impl.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring.jar new file mode 100755 index 0000000..3627c95 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-keyring.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-masterfs-nio2.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-masterfs-nio2.jar new file mode 100755 index 0000000..2aceaad Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-masterfs-nio2.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-masterfs.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-masterfs.jar new file mode 100755 index 0000000..d02aa1f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-masterfs.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-options-api.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-options-api.jar new file mode 100755 index 0000000..6f2c63b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-options-api.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-options-keymap.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-options-keymap.jar new file mode 100755 index 0000000..a16295d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-options-keymap.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-print.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-print.jar new file mode 100755 index 0000000..71ffe3e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-print.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-progress-ui.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-progress-ui.jar new file mode 100755 index 0000000..e86c9bd Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-progress-ui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-queries.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-queries.jar new file mode 100755 index 0000000..48982f4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-queries.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-sampler.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-sampler.jar new file mode 100755 index 0000000..0c9d855 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-sampler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-sendopts.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-sendopts.jar new file mode 100755 index 0000000..3c7b2f8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-sendopts.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-settings.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-settings.jar new file mode 100755 index 0000000..e041356 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-settings.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-spi-actions.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-spi-actions.jar new file mode 100755 index 0000000..9730ccd Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-spi-actions.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-templates.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-templates.jar new file mode 100755 index 0000000..fc841c4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-templates.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-uihandler.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-uihandler.jar new file mode 100755 index 0000000..964df73 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-modules-uihandler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-spi-quicksearch.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-spi-quicksearch.jar new file mode 100755 index 0000000..5b20483 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-spi-quicksearch.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-outline.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-outline.jar new file mode 100755 index 0000000..008b3d8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-outline.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-plaf.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-plaf.jar new file mode 100755 index 0000000..6bd182b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-plaf.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-tabcontrol.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-tabcontrol.jar new file mode 100755 index 0000000..31bea3a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-netbeans-swing-tabcontrol.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-actions.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-actions.jar new file mode 100755 index 0000000..265c4be Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-actions.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-awt.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-awt.jar new file mode 100755 index 0000000..44313c8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-awt.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-compat.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-compat.jar new file mode 100755 index 0000000..036156b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-compat.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-dialogs.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-dialogs.jar new file mode 100755 index 0000000..2d11e6c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-dialogs.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-execution.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-execution.jar new file mode 100755 index 0000000..b17101b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-execution.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-explorer.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-explorer.jar new file mode 100755 index 0000000..74fdea9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-explorer.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-io.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-io.jar new file mode 100755 index 0000000..49f815b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-io.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-loaders.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-loaders.jar new file mode 100755 index 0000000..8e568ae Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-loaders.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-nodes.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-nodes.jar new file mode 100755 index 0000000..8adb79b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-nodes.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-options.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-options.jar new file mode 100755 index 0000000..dcaac1f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-options.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-text.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-text.jar new file mode 100755 index 0000000..9c0702e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-text.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-util-enumerations.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-util-enumerations.jar new file mode 100755 index 0000000..7206578 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-util-enumerations.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-windows.jar b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-windows.jar new file mode 100755 index 0000000..6751e42 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/platform/modules/org-openide-windows.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-annotations-common.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-annotations-common.xml new file mode 100755 index 0000000..e6d8647 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-annotations-common.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-progress.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-progress.xml new file mode 100755 index 0000000..98423eb --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-progress.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-search.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-search.xml new file mode 100755 index 0000000..e9fa18d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-search.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-visual.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-visual.xml new file mode 100755 index 0000000..ae7ca39 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-api-visual.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-bootstrap.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-bootstrap.xml new file mode 100755 index 0000000..127137b --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-bootstrap.xml @@ -0,0 +1,10 @@ + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-execution.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-execution.xml new file mode 100755 index 0000000..112af7d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-execution.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-io-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-io-ui.xml new file mode 100755 index 0000000..7cf6e61 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-io-ui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-multitabs.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-multitabs.xml new file mode 100755 index 0000000..85dd8da --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-multitabs.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-multiview.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-multiview.xml new file mode 100755 index 0000000..79122e1 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-multiview.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-output2.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-output2.xml new file mode 100755 index 0000000..779f33c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-output2.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-startup.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-startup.xml new file mode 100755 index 0000000..129133e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-startup.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-ui.xml new file mode 100755 index 0000000..48dae35 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-ui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-windows.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-windows.xml new file mode 100755 index 0000000..94c848a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core-windows.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core.xml new file mode 100755 index 0000000..3437a73 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-core.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-lib-uihandler.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-lib-uihandler.xml new file mode 100755 index 0000000..c71441e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-lib-uihandler.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-applemenu.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-applemenu.xml new file mode 100755 index 0000000..2d76272 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-applemenu.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-cli.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-cli.xml new file mode 100755 index 0000000..5e26ca2 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-cli.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-services.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-services.xml new file mode 100755 index 0000000..06a042f --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-services.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-ui.xml new file mode 100755 index 0000000..55bc0a5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-autoupdate-ui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-core-kit.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-core-kit.xml new file mode 100755 index 0000000..d338e46 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-core-kit.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-editor-mimelookup-impl.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-editor-mimelookup-impl.xml new file mode 100755 index 0000000..14ecb6d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-editor-mimelookup-impl.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-editor-mimelookup.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-editor-mimelookup.xml new file mode 100755 index 0000000..00d91e4 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-editor-mimelookup.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-favorites.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-favorites.xml new file mode 100755 index 0000000..47b0cc5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-favorites.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-javahelp.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-javahelp.xml new file mode 100755 index 0000000..c95b00c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-javahelp.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring-fallback.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring-fallback.xml new file mode 100755 index 0000000..300db1a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring-fallback.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring-impl.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring-impl.xml new file mode 100755 index 0000000..9c7d92e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring-impl.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring.xml new file mode 100755 index 0000000..fa20d95 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-keyring.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-masterfs-nio2.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-masterfs-nio2.xml new file mode 100755 index 0000000..a73a9ba --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-masterfs-nio2.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-masterfs.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-masterfs.xml new file mode 100755 index 0000000..7fa29b2 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-masterfs.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-options-api.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-options-api.xml new file mode 100755 index 0000000..e1eebb5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-options-api.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-options-keymap.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-options-keymap.xml new file mode 100755 index 0000000..6eb0c77 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-options-keymap.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-print.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-print.xml new file mode 100755 index 0000000..c636199 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-print.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-progress-ui.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-progress-ui.xml new file mode 100755 index 0000000..4e71d1e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-progress-ui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-queries.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-queries.xml new file mode 100755 index 0000000..afecf59 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-queries.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-sampler.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-sampler.xml new file mode 100755 index 0000000..e8c5e16 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-sampler.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-sendopts.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-sendopts.xml new file mode 100755 index 0000000..3b782c1 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-sendopts.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-settings.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-settings.xml new file mode 100755 index 0000000..03de3d5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-settings.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-spi-actions.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-spi-actions.xml new file mode 100755 index 0000000..70fc553 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-spi-actions.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-templates.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-templates.xml new file mode 100755 index 0000000..04b8096 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-templates.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-uihandler.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-uihandler.xml new file mode 100755 index 0000000..b798815 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-modules-uihandler.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-spi-quicksearch.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-spi-quicksearch.xml new file mode 100755 index 0000000..d1d8edc --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-spi-quicksearch.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-outline.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-outline.xml new file mode 100755 index 0000000..bc73dab --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-outline.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-plaf.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-plaf.xml new file mode 100755 index 0000000..5ac6430 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-plaf.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-tabcontrol.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-tabcontrol.xml new file mode 100755 index 0000000..d074134 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-netbeans-swing-tabcontrol.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-actions.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-actions.xml new file mode 100755 index 0000000..f845072 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-actions.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-awt.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-awt.xml new file mode 100755 index 0000000..06da76f --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-awt.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-compat.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-compat.xml new file mode 100755 index 0000000..3617619 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-compat.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-dialogs.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-dialogs.xml new file mode 100755 index 0000000..5bf9ea6 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-dialogs.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-execution.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-execution.xml new file mode 100755 index 0000000..928a91d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-execution.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-explorer.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-explorer.xml new file mode 100755 index 0000000..841b13c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-explorer.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-filesystems.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-filesystems.xml new file mode 100755 index 0000000..6dc3dbe --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-filesystems.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-io.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-io.xml new file mode 100755 index 0000000..b821916 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-io.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-loaders.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-loaders.xml new file mode 100755 index 0000000..f2bdbd4 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-loaders.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-modules.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-modules.xml new file mode 100755 index 0000000..a3d2576 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-modules.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-nodes.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-nodes.xml new file mode 100755 index 0000000..f288cf7 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-nodes.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-options.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-options.xml new file mode 100755 index 0000000..417203e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-options.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-text.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-text.xml new file mode 100755 index 0000000..ea4012d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-text.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util-enumerations.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util-enumerations.xml new file mode 100755 index 0000000..dba9d90 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util-enumerations.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util-lookup.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util-lookup.xml new file mode 100755 index 0000000..b37d719 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util-lookup.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util.xml new file mode 100755 index 0000000..6955f2b --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-util.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-windows.xml b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-windows.xml new file mode 100755 index 0000000..e8111be --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/platform/update_tracking/org-openide-windows.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/.lastModified b/jdk-1.8.0.281/lib/visualvm/profiler/.lastModified new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/VERSION.txt b/jdk-1.8.0.281/lib/visualvm/profiler/VERSION.txt new file mode 100755 index 0000000..a3c7381 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/VERSION.txt @@ -0,0 +1,2 @@ +# cluster incompatible release version +10 diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-charts.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-charts.xml new file mode 100755 index 0000000..fce5176 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-charts.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-lib-profiler-charts.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-common.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-common.xml new file mode 100755 index 0000000..c35a13c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-common.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-lib-profiler-common.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-ui.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-ui.xml new file mode 100755 index 0000000..e841a0f --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler-ui.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-lib-profiler-ui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler.xml new file mode 100755 index 0000000..3566085 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-lib-profiler.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-lib-profiler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-api.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-api.xml new file mode 100755 index 0000000..581c552 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-api.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler-api.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-attach.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-attach.xml new file mode 100755 index 0000000..122c009 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-attach.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler-attach.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-heapwalker.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-heapwalker.xml new file mode 100755 index 0000000..d41d76e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-heapwalker.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-profiler-heapwalker.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-oql.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-oql.xml new file mode 100755 index 0000000..921af9c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-oql.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler-oql.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-selector-api.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-selector-api.xml new file mode 100755 index 0000000..8ee1069 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-selector-api.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler-selector-api.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-selector-ui.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-selector-ui.xml new file mode 100755 index 0000000..18fac3a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-selector-ui.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler-selector-ui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-snaptracer.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-snaptracer.xml new file mode 100755 index 0000000..d18a6ba --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-snaptracer.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/org-netbeans-modules-profiler-snaptracer.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-utilities.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-utilities.xml new file mode 100755 index 0000000..0318741 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler-utilities.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler-utilities.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler.xml b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler.xml new file mode 100755 index 0000000..4d454dc --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/config/Modules/org-netbeans-modules-profiler.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/org-netbeans-modules-profiler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/lib/deployed/jdk15/linux-amd64/libprofilerinterface.so b/jdk-1.8.0.281/lib/visualvm/profiler/lib/deployed/jdk15/linux-amd64/libprofilerinterface.so new file mode 100755 index 0000000..1050d9a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/lib/deployed/jdk15/linux-amd64/libprofilerinterface.so differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so b/jdk-1.8.0.281/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so new file mode 100755 index 0000000..15169bd Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/lib/jfluid-server-15.jar b/jdk-1.8.0.281/lib/visualvm/profiler/lib/jfluid-server-15.jar new file mode 100755 index 0000000..611050c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/lib/jfluid-server-15.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/lib/jfluid-server.jar b/jdk-1.8.0.281/lib/visualvm/profiler/lib/jfluid-server.jar new file mode 100755 index 0000000..669679b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/lib/jfluid-server.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/lib/locale/jfluid-server_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/lib/locale/jfluid-server_ja.jar new file mode 100755 index 0000000..c3c19e4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/lib/locale/jfluid-server_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/lib/locale/jfluid-server_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/lib/locale/jfluid-server_zh_CN.jar new file mode 100755 index 0000000..debfd6e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/lib/locale/jfluid-server_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-charts_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-charts_ja.jar new file mode 100755 index 0000000..d1815da Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-charts_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-charts_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-charts_zh_CN.jar new file mode 100755 index 0000000..d5b59f9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-charts_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-common_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-common_ja.jar new file mode 100755 index 0000000..d3316ed Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-common_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-common_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-common_zh_CN.jar new file mode 100755 index 0000000..3e01405 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-common_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-ui_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-ui_ja.jar new file mode 100755 index 0000000..093df6e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-ui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-ui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-ui_zh_CN.jar new file mode 100755 index 0000000..f85b234 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler-ui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler_ja.jar new file mode 100755 index 0000000..1763fb7 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler_zh_CN.jar new file mode 100755 index 0000000..1a90dc5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-lib-profiler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-api_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-api_ja.jar new file mode 100755 index 0000000..5cb55a8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-api_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-api_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-api_zh_CN.jar new file mode 100755 index 0000000..e0450df Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-api_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-attach_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-attach_ja.jar new file mode 100755 index 0000000..70919aa Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-attach_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-attach_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-attach_zh_CN.jar new file mode 100755 index 0000000..f501038 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-attach_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-heapwalker_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-heapwalker_ja.jar new file mode 100755 index 0000000..9bd853c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-heapwalker_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-heapwalker_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-heapwalker_zh_CN.jar new file mode 100755 index 0000000..78b81fe Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-heapwalker_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-oql_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-oql_ja.jar new file mode 100755 index 0000000..1a775fa Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-oql_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-oql_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-oql_zh_CN.jar new file mode 100755 index 0000000..149e523 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-oql_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-api_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-api_ja.jar new file mode 100755 index 0000000..32bf8ba Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-api_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-api_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-api_zh_CN.jar new file mode 100755 index 0000000..538b7a7 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-api_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-ui_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-ui_ja.jar new file mode 100755 index 0000000..073e07e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-ui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-ui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-ui_zh_CN.jar new file mode 100755 index 0000000..7fcbf2e Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-selector-ui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-snaptracer_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-snaptracer_ja.jar new file mode 100755 index 0000000..a1fd54a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-snaptracer_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-snaptracer_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-snaptracer_zh_CN.jar new file mode 100755 index 0000000..71c351d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-snaptracer_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-utilities_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-utilities_ja.jar new file mode 100755 index 0000000..74758a4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-utilities_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-utilities_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-utilities_zh_CN.jar new file mode 100755 index 0000000..313eba3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler-utilities_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler_ja.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler_ja.jar new file mode 100755 index 0000000..2b1f3e9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler_zh_CN.jar new file mode 100755 index 0000000..392e103 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/locale/org-netbeans-modules-profiler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-charts.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-charts.jar new file mode 100755 index 0000000..d072151 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-charts.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-common.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-common.jar new file mode 100755 index 0000000..41bf141 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-common.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-ui.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-ui.jar new file mode 100755 index 0000000..07895b5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler-ui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler.jar new file mode 100755 index 0000000..958862c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-lib-profiler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-api.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-api.jar new file mode 100755 index 0000000..c7243f2 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-api.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-attach.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-attach.jar new file mode 100755 index 0000000..647d945 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-attach.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-heapwalker.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-heapwalker.jar new file mode 100755 index 0000000..c2739bf Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-heapwalker.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-oql.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-oql.jar new file mode 100755 index 0000000..9a84489 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-oql.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-selector-api.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-selector-api.jar new file mode 100755 index 0000000..066f5bd Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-selector-api.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-selector-ui.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-selector-ui.jar new file mode 100755 index 0000000..4f26b1c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-selector-ui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-snaptracer.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-snaptracer.jar new file mode 100755 index 0000000..343340d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-snaptracer.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-utilities.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-utilities.jar new file mode 100755 index 0000000..d081552 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler-utilities.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler.jar b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler.jar new file mode 100755 index 0000000..af21376 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/profiler/modules/org-netbeans-modules-profiler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-charts.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-charts.xml new file mode 100755 index 0000000..9c8a47e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-charts.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-common.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-common.xml new file mode 100755 index 0000000..adb6495 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-common.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-ui.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-ui.xml new file mode 100755 index 0000000..432f498 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler-ui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler.xml new file mode 100755 index 0000000..a94f7d7 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-lib-profiler.xml @@ -0,0 +1,36 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-api.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-api.xml new file mode 100755 index 0000000..ec93045 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-api.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-attach.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-attach.xml new file mode 100755 index 0000000..4d1a798 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-attach.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-heapwalker.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-heapwalker.xml new file mode 100755 index 0000000..bd19504 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-heapwalker.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-oql.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-oql.xml new file mode 100755 index 0000000..0674550 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-oql.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-selector-api.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-selector-api.xml new file mode 100755 index 0000000..c86a519 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-selector-api.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-selector-ui.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-selector-ui.xml new file mode 100755 index 0000000..35c2bef --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-selector-ui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-snaptracer.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-snaptracer.xml new file mode 100755 index 0000000..7d298e7 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-snaptracer.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-utilities.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-utilities.xml new file mode 100755 index 0000000..85d1f05 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler-utilities.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler.xml b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler.xml new file mode 100755 index 0000000..25dfcf5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/profiler/update_tracking/org-netbeans-modules-profiler.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/.lastModified b/jdk-1.8.0.281/lib/visualvm/visualvm/.lastModified new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-api-caching.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-api-caching.xml new file mode 100755 index 0000000..cadd69b --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-api-caching.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/com-sun-tools-visualvm-api-caching.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-application-views.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-application-views.xml new file mode 100755 index 0000000..fd07519 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-application-views.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-application-views.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-application.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-application.xml new file mode 100755 index 0000000..df8782e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-application.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-application.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-attach.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-attach.xml new file mode 100755 index 0000000..ffe3d90 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-attach.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-attach.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-charts.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-charts.xml new file mode 100755 index 0000000..5797ea8 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-charts.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-charts.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-core.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-core.xml new file mode 100755 index 0000000..55009fa --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-core.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-core.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-coredump.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-coredump.xml new file mode 100755 index 0000000..82cb0d9 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-coredump.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-coredump.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-heapdump.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-heapdump.xml new file mode 100755 index 0000000..b345d87 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-heapdump.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-heapdump.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host-remote.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host-remote.xml new file mode 100755 index 0000000..2d8fabc --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host-remote.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-host-remote.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host-views.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host-views.xml new file mode 100755 index 0000000..2342c09 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host-views.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-host-views.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host.xml new file mode 100755 index 0000000..65073b1 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-host.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-host.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jmx.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jmx.xml new file mode 100755 index 0000000..3252818 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jmx.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-jmx.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jvm.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jvm.xml new file mode 100755 index 0000000..c0c105c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jvm.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-jvm.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jvmstat.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jvmstat.xml new file mode 100755 index 0000000..5270af5 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-jvmstat.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-jvmstat.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-modules-appui.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-modules-appui.xml new file mode 100755 index 0000000..c4d2aca --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-modules-appui.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-modules-appui.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-profiler.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-profiler.xml new file mode 100755 index 0000000..b24e650 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-profiler.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-profiler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-profiling.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-profiling.xml new file mode 100755 index 0000000..dd5f1df --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-profiling.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/com-sun-tools-visualvm-profiling.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-sa.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-sa.xml new file mode 100755 index 0000000..c66c7cb --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-sa.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-sa.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-sampler.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-sampler.xml new file mode 100755 index 0000000..3db293d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-sampler.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-sampler.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-threaddump.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-threaddump.xml new file mode 100755 index 0000000..e88ebe7 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-threaddump.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-threaddump.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-tools.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-tools.xml new file mode 100755 index 0000000..72ac66c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-tools.xml @@ -0,0 +1,10 @@ + + + + false + false + true + modules/com-sun-tools-visualvm-tools.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-uisupport.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-uisupport.xml new file mode 100755 index 0000000..69befc1 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/com-sun-tools-visualvm-uisupport.xml @@ -0,0 +1,9 @@ + + + + true + false + modules/com-sun-tools-visualvm-uisupport.jar + false + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-api-visual.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-api-visual.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-core-execution.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-core-execution.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-core-io-ui.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-core-io-ui.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-core-output2.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-core-output2.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-lib-uihandler.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-lib-uihandler.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-core-kit.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-core-kit.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-favorites.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-favorites.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-options-keymap.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-options-keymap.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-print.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-print.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-spi-actions.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-spi-actions.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-templates.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-templates.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-uihandler.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-netbeans-modules-uihandler.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-compat.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-compat.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-execution.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-execution.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-options.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-options.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-util-enumerations.xml_hidden b/jdk-1.8.0.281/lib/visualvm/visualvm/config/Modules/org-openide-util-enumerations.xml_hidden new file mode 100755 index 0000000..e69de29 diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/core/com-sun-tools-visualvm-modules-startup.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/core/com-sun-tools-visualvm-modules-startup.jar new file mode 100755 index 0000000..c98e1b1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/core/com-sun-tools-visualvm-modules-startup.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/com-sun-tools-visualvm-modules-startup_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/com-sun-tools-visualvm-modules-startup_ja.jar new file mode 100755 index 0000000..833d489 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/com-sun-tools-visualvm-modules-startup_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/com-sun-tools-visualvm-modules-startup_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/com-sun-tools-visualvm-modules-startup_zh_CN.jar new file mode 100755 index 0000000..76689f7 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/com-sun-tools-visualvm-modules-startup_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/core_visualvm.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/core_visualvm.jar new file mode 100755 index 0000000..38ff5e4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/core/locale/core_visualvm.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-api-caching.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-api-caching.jar new file mode 100755 index 0000000..c069dc8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-api-caching.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-application-views.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-application-views.jar new file mode 100755 index 0000000..8a9008c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-application-views.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-application.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-application.jar new file mode 100755 index 0000000..38a4081 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-application.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-attach.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-attach.jar new file mode 100755 index 0000000..afb2ff3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-attach.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-charts.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-charts.jar new file mode 100755 index 0000000..df5406c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-charts.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-core.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-core.jar new file mode 100755 index 0000000..359355c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-core.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-coredump.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-coredump.jar new file mode 100755 index 0000000..7abb4df Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-coredump.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-heapdump.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-heapdump.jar new file mode 100755 index 0000000..f016c20 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-heapdump.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host-remote.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host-remote.jar new file mode 100755 index 0000000..b78f6d9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host-remote.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host-views.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host-views.jar new file mode 100755 index 0000000..b05efcf Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host-views.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host.jar new file mode 100755 index 0000000..84f46c5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-host.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jmx.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jmx.jar new file mode 100755 index 0000000..83482e6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jmx.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jvm.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jvm.jar new file mode 100755 index 0000000..d2569b1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jvm.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jvmstat.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jvmstat.jar new file mode 100755 index 0000000..6390b6f Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-jvmstat.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-modules-appui.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-modules-appui.jar new file mode 100755 index 0000000..901c9ee Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-modules-appui.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-profiler.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-profiler.jar new file mode 100755 index 0000000..8185394 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-profiler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-profiling.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-profiling.jar new file mode 100755 index 0000000..19b3248 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-profiling.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-sa.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-sa.jar new file mode 100755 index 0000000..ccdd29b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-sa.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-sampler.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-sampler.jar new file mode 100755 index 0000000..161e2b4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-sampler.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-threaddump.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-threaddump.jar new file mode 100755 index 0000000..bd2d19d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-threaddump.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-tools.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-tools.jar new file mode 100755 index 0000000..6fdd513 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-tools.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-uisupport.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-uisupport.jar new file mode 100755 index 0000000..8776c01 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/com-sun-tools-visualvm-uisupport.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-api-caching_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-api-caching_ja.jar new file mode 100755 index 0000000..2f48512 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-api-caching_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-api-caching_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-api-caching_zh_CN.jar new file mode 100755 index 0000000..8aa7601 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-api-caching_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application-views_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application-views_ja.jar new file mode 100755 index 0000000..d08e3dd Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application-views_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application-views_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application-views_zh_CN.jar new file mode 100755 index 0000000..5434b65 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application-views_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application_ja.jar new file mode 100755 index 0000000..6a4a934 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application_zh_CN.jar new file mode 100755 index 0000000..62ffc4b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-application_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-attach_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-attach_ja.jar new file mode 100755 index 0000000..739825b Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-attach_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-attach_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-attach_zh_CN.jar new file mode 100755 index 0000000..ae7d4e5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-attach_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-charts_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-charts_ja.jar new file mode 100755 index 0000000..1b4e5c4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-charts_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-charts_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-charts_zh_CN.jar new file mode 100755 index 0000000..ade18cc Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-charts_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-core_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-core_ja.jar new file mode 100755 index 0000000..eb24215 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-core_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-core_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-core_zh_CN.jar new file mode 100755 index 0000000..7a5a4b1 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-core_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-coredump_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-coredump_ja.jar new file mode 100755 index 0000000..056a41d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-coredump_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-coredump_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-coredump_zh_CN.jar new file mode 100755 index 0000000..1fa207a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-coredump_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-heapdump_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-heapdump_ja.jar new file mode 100755 index 0000000..1e406f5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-heapdump_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-heapdump_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-heapdump_zh_CN.jar new file mode 100755 index 0000000..79b4cf2 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-heapdump_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-remote_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-remote_ja.jar new file mode 100755 index 0000000..d388a83 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-remote_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-remote_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-remote_zh_CN.jar new file mode 100755 index 0000000..64295b0 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-remote_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-views_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-views_ja.jar new file mode 100755 index 0000000..2f5f7af Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-views_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-views_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-views_zh_CN.jar new file mode 100755 index 0000000..523ea5c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host-views_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host_ja.jar new file mode 100755 index 0000000..a17d18c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host_zh_CN.jar new file mode 100755 index 0000000..94465d6 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-host_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jmx_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jmx_ja.jar new file mode 100755 index 0000000..ccac244 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jmx_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jmx_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jmx_zh_CN.jar new file mode 100755 index 0000000..2764c47 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jmx_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvm_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvm_ja.jar new file mode 100755 index 0000000..b8de1e5 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvm_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvm_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvm_zh_CN.jar new file mode 100755 index 0000000..4fbbb3d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvm_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvmstat_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvmstat_ja.jar new file mode 100755 index 0000000..c9ec097 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvmstat_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvmstat_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvmstat_zh_CN.jar new file mode 100755 index 0000000..81d6617 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-jvmstat_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-modules-appui_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-modules-appui_ja.jar new file mode 100755 index 0000000..6692844 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-modules-appui_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-modules-appui_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-modules-appui_zh_CN.jar new file mode 100755 index 0000000..8fd00d0 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-modules-appui_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiler_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiler_ja.jar new file mode 100755 index 0000000..8bb2bb4 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiler_zh_CN.jar new file mode 100755 index 0000000..5fa8dc3 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiling_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiling_ja.jar new file mode 100755 index 0000000..e6fc76a Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiling_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiling_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiling_zh_CN.jar new file mode 100755 index 0000000..6451675 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-profiling_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sa_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sa_ja.jar new file mode 100755 index 0000000..18b6ae8 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sa_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sa_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sa_zh_CN.jar new file mode 100755 index 0000000..ac20e2c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sa_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sampler_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sampler_ja.jar new file mode 100755 index 0000000..bd85503 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sampler_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sampler_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sampler_zh_CN.jar new file mode 100755 index 0000000..51e43b9 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-sampler_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-threaddump_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-threaddump_ja.jar new file mode 100755 index 0000000..0efc0a7 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-threaddump_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-threaddump_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-threaddump_zh_CN.jar new file mode 100755 index 0000000..081c35c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-threaddump_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-tools_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-tools_ja.jar new file mode 100755 index 0000000..a0afd95 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-tools_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-tools_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-tools_zh_CN.jar new file mode 100755 index 0000000..73f779d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-tools_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-uisupport_ja.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-uisupport_ja.jar new file mode 100755 index 0000000..7338641 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-uisupport_ja.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-uisupport_zh_CN.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-uisupport_zh_CN.jar new file mode 100755 index 0000000..183d07c Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/com-sun-tools-visualvm-uisupport_zh_CN.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-core-windows_visualvm.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-core-windows_visualvm.jar new file mode 100755 index 0000000..c7afd3d Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-core-windows_visualvm.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-core_visualvm.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-core_visualvm.jar new file mode 100755 index 0000000..3270101 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-core_visualvm.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-modules-profiler_visualvm.jar b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-modules-profiler_visualvm.jar new file mode 100755 index 0000000..6a2aa25 Binary files /dev/null and b/jdk-1.8.0.281/lib/visualvm/visualvm/modules/locale/org-netbeans-modules-profiler_visualvm.jar differ diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-api-caching.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-api-caching.xml new file mode 100755 index 0000000..278c805 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-api-caching.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-application-views.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-application-views.xml new file mode 100755 index 0000000..f84ff58 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-application-views.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-application.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-application.xml new file mode 100755 index 0000000..d061cce --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-application.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-attach.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-attach.xml new file mode 100755 index 0000000..0203082 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-attach.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-charts.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-charts.xml new file mode 100755 index 0000000..3887713 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-charts.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-core.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-core.xml new file mode 100755 index 0000000..029741c --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-core.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-coredump.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-coredump.xml new file mode 100755 index 0000000..860faaf --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-coredump.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-heapdump.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-heapdump.xml new file mode 100755 index 0000000..c7cf8cb --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-heapdump.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host-remote.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host-remote.xml new file mode 100755 index 0000000..f04e700 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host-remote.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host-views.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host-views.xml new file mode 100755 index 0000000..bfcc6c4 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host-views.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host.xml new file mode 100755 index 0000000..73b04b4 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-host.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jmx.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jmx.xml new file mode 100755 index 0000000..4f86256 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jmx.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jvm.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jvm.xml new file mode 100755 index 0000000..3a5477e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jvm.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jvmstat.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jvmstat.xml new file mode 100755 index 0000000..60b19d8 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-jvmstat.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-modules-appui.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-modules-appui.xml new file mode 100755 index 0000000..aecb52e --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-modules-appui.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-modules-startup.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-modules-startup.xml new file mode 100755 index 0000000..38c01cf --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-modules-startup.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-profiler.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-profiler.xml new file mode 100755 index 0000000..139eb02 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-profiler.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-profiling.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-profiling.xml new file mode 100755 index 0000000..998f480 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-profiling.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-sa.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-sa.xml new file mode 100755 index 0000000..13ac811 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-sa.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-sampler.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-sampler.xml new file mode 100755 index 0000000..ada273d --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-sampler.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-threaddump.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-threaddump.xml new file mode 100755 index 0000000..09b34fe --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-threaddump.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-tools.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-tools.xml new file mode 100755 index 0000000..e55927a --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-tools.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-uisupport.xml b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-uisupport.xml new file mode 100755 index 0000000..bacf530 --- /dev/null +++ b/jdk-1.8.0.281/lib/visualvm/visualvm/update_tracking/com-sun-tools-visualvm-uisupport.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/jdk-1.8.0.281/man/ja/man1/appletviewer.1 b/jdk-1.8.0.281/man/ja/man1/appletviewer.1 new file mode 100755 index 0000000..381ac86 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/appletviewer.1 @@ -0,0 +1,88 @@ +'\" t +.\" Copyright (c) 1995, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: appletviewer +.\" Language: Japanese +.\" Date: 2013年11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "appletviewer" "1" "2013年11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +appletviewer \- Webブラウザの外側でアプレットを実行します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBappletviewer\fR [\fIoptions\fR] \fIurl\fR\&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +空白で区切られたコマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIurl\fR +.RS 4 +表示するドキュメントまたはリソースの場所。空白で区切られた複数のURLを指定できます。 +.RE +.SH "説明" +.PP +\fBappletviewer\fRコマンドは\fIurls\fRに指定されたドキュメントあるいはリソースと接続して、そのドキュメントが参照するそれぞれのアプレットを独自のウィンドウで表示します。urlsによって参照されたドキュメントが、\fBOBJECT\fR、\fBEMBED\fRまたは\fBAPPLET\fRタグでどのアプレットも参照していない場合、\fBappletviewer\fRコマンドは何も行いません。\fBappletviewer\fRコマンドでサポートされるHTMLタグの詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/appletviewertags\&.htmlにある +アプレット・ビューア・タグを参照してください。 +.PP +\fBappletviewer\fRコマンドは、RFC2396で定義されたエスケープ・メカニズムに従ってエンコードされたURLを必要とします。サポートされるのは、エンコードされたURLのみです。ただし、ファイル名については、RFC2396の仕様に従ってエンコードを解除しておく必要があります。 +.PP +\fB注意:\fR +The +\fBappletviewer\fRコマンドは開発専用です。詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/aboutCodeSamples\&.htmlにある +サンプル/テスト・アプリケーションおよびコードについてを参照してください。 +.SH "オプション" +.PP +\-debug +.RS 4 +\fBjdb\fRコマンドを使用してJavaデバッガでアプレット・ビューアを開始して、ドキュメント中のアプレットをデバッグします。 +.RE +.PP +\-encoding \fIencoding\-name\fR +.RS 4 +入力HTMLファイルのエンコーディング名を指定します。 +.RE +.PP +\-J\fIjavaoption\fR +.RS 4 +文字列\fBjavaoption\fRは、アプレット・ビューアを実行するJavaインタプリタに1つの引数として渡されます。引数にスペースを含めないでください。複数の引数は、すべてが接頭辞\fB\-J\fRで始まる必要があります。これは、コンパイラの実行環境またはメモリー使用の調整に有効です。 +.RE +.PP + +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/extcheck.1 b/jdk-1.8.0.281/man/ja/man1/extcheck.1 new file mode 100755 index 0000000..192e5a9 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/extcheck.1 @@ -0,0 +1,91 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: extcheck +.\" Language: Japanese +.\" Date: 2013年11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "extcheck" "1" "2013年11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +extcheck \- ターゲットのJavaアーカイブ(JAR)ファイルと現在インストールされている拡張機能のJARファイル間のバージョンの競合を検出します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBextcheck\fR [\fIoptions\fR] \fItargetfile\&.jar\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fItargetfile\&.jar\fR +.RS 4 +バージョンの競合を検出するために、現在インストールされている拡張機能JARファイルと比較するターゲットJARファイル。 +.RE +.SH "説明" +.PP +\fBextcheck\fRコマンドは、指定されたJARファイルのタイトルおよびバージョンがJava SE SDKにインストールされている拡張機能と競合していないかをチェックします。拡張機能をインストールする前に、このユーティリティを使用して、同じバージョンまたはより新しいバージョンの拡張機能がすでにインストールされていないかどうかを調べることができます。 +.PP +\fBextcheck\fRコマンドは、\fBtargetfile\&.jar\fRファイルのマニフェスト内のヘッダーSpecification\-titleおよびSpecification\-versionを、拡張機能ディレクトリ内に現在インストールされているすべてのJARファイル内の対応するヘッダーと比較します。デフォルトでは、拡張機能ディレクトリは、Oracle Solarisの場合は\fBjre/lib/ext\fR、Windowsの場合は\fB\ejre\elib\eext\fRです。\fBextcheck\fRコマンドは、\fBjava\&.lang\&.Package\&.isCompatibleWith\fRメソッドと同様の方法でバージョン番号を比較します。 +.PP +競合が検出されない場合、リターン・コードは0です。 +.PP +拡張機能ディレクトリ内のいずれかのJARファイルのマニフェストに、同一の\fBSpecification\-title\fR、および同一またはより新しい\fBSpecification\-version\fR番号がある場合は、ゼロでないエラー・コードが返されます。\fBtargetfile\&.jar\fRのマニフェスト・ファイルに\fBSpecification\-title\fRまたは\fBSpecification\-version\fR属性がない場合も、ゼロでないエラー・コードが返されます。 +.SH "オプション" +.PP +\-verbose +.RS 4 +拡張機能ディレクトリ内のJARファイルを、チェック時に一覧表示します。また、ターゲットJARファイルのマニフェストの属性、および競合するJARファイルについても報告します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machine (JVM)に\fIoption\fRを渡します。optionには、Java起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/idlj.1 b/jdk-1.8.0.281/man/ja/man1/idlj.1 new file mode 100755 index 0000000..bbd4b58 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/idlj.1 @@ -0,0 +1,529 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: idlj +.\" Language: Japanese +.\" Date: 2013年11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "idlj" "1" "2013年11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +idlj \- 指定されたインタフェース定義言語(IDL)ファイルに対してJavaバインディングを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj\fR [ \fIoptions\fR ] \fIidlfile\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。optionsの順番は任意ですが、\fBidlfile\fRよりも前に指定する必要があります。 +.RE +.PP +\fIidlfile\fR +.RS 4 +インタフェース定義言語(IDL)による定義が含まれるファイルの名前。 +.RE +.SH "説明" +.PP +IDL\-to\-Javaコンパイラは、指定されたIDLファイルに対してJavaバインディングを生成します。バインディングの詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.htmlにある +Java IDL: Java言語マッピングへのIDLを参照してください。 +.PP +IDL\-to\-Javaコンパイラの以前のリリースの中には、\fBidltojava\fRという名前だったものがあります。 +.SS "クライアント・バインディングおよびサーバー・バインディングの発行" +.PP +次の\fBidlj\fRコマンドは、クライアント側バインディングを含む\fBMy\&.idl\fRという名前のIDLファイルを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +前の構文は次と同等です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fclient My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、サーバー側バインディングを生成し、クライアント側バインディングおよびスケルトンを含めており、これらはすべて、POA (継承モデル)です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlg \-fserver My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +クライアント側とサーバー側の両方のバインディングを生成する場合は、次のコマンド(どれも等価)のうちの1つを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fclient \-fserver My\&.idl\fR +\fBidlj \-fall My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +サーバー側で可能なモデルは2つあります。移殖可能サーバント継承モデルとTieモデルです。Tie委譲モデルを参照してください。 +.PP +\fB移殖可能サーバント継承モデル\fR. デフォルトのサーバー側のモデルは、移殖可能サーバント継承モデルです。\fBMy\&.idl\fR内で\fBMy\fRインタフェースが定義されている場合は、\fBMyPOA\&.java\fRというファイルが生成されます。\fBMy\fRインタフェースの実装を提供する必要があり、\fBMy\fRインタフェースは\fBMyPOA\fRクラスから継承する必要があります。\fBMyPOA\&.java\fRは、http://docs\&.oracle\&.com/javase/8/docs/api/org/omg/PortableServer/Servant\&.htmlにある +\fBorg\&.omg\&.PortableServer\&.Servant\fRクラスを拡張するストリームベースのスケルトンです。 +.PP +\fBMy\fRインタフェースは、スケルトンが実装するIDLインタフェースに関連付けられている\fBcallHandler\fRインタフェースと操作インタフェースを実装します。 +.PP +ポータブル・オブジェクト・アダプタ(POA)の\fBPortableServer\fRモジュールは、ネイティブの\fBServant\fR型を定義します。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/POA\&.htmlにある +ポータブル・オブジェクト・アダプタ(POA)を参照してください。 +.PP +Javaプログラミング言語では、\fBServant\fR型はJavaの\fBorg\&.omg\&.PortableServer\&.Servant\fRクラスにマップされます。これは、すべてのPOAサーバント実装のベース・クラスとして機能し、アプリケーション・プログラマが呼び出すことのできるいくつかのメソッド、およびPOAによって呼び出され、サーバントの動作を制御するためにユーザーがオーバーライドできるメソッドを提供します。 +.PP +継承モデルのもう1つのオプションは、\fB\-oldImplBase\fRフラグを使用して、Java SE 1\&.4より前のリリースのJavaプログラミング言語と互換性のあるサーバー側バインディングを生成することです。\-\fBoldImplBase\fRフラグは非標準で、これらのAPIは非推奨です。このフラグを使用するのは、Java SE 1\&.3で記述された既存のサーバーとの互換性が必要な場合のみです。その場合、既存のmakeファイルを変更して、\fB\-oldImplBase\fRフラグを\fBidlj\fRコンパイラに追加する必要があります。それ以外の場合、POAベースのサーバー側マッピングが生成されます。後方互換性のあるサーバー側バインディングを生成するには、次を実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fclient \-fserver \-oldImplBase My\&.idl\fR +\fBidlj \-fall \-oldImplBase My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBMy\&.idl\fR内で\fBMy\fRインタフェースが定義されている場合は、\fB_MyImplBase\&.java\fRというファイルが生成されます。\fBMy\fRインタフェースの実装を提供する必要があり、\fBMy\fRインタフェースは\fB_MyImplBase\fRクラスから継承する必要があります。 +.PP +\fBTie委譲モデル\fR. もう1つのサーバー側モデルは、Tieモデルと呼ばれるものです。このサーバー側モデルは、委譲モデルです。Tieとスケルトンを同時に生成することはできないため、それらは別々に生成する必要があります。次のコマンドによって、Tieモデル用のバインディングが生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fall My\&.idl\fR +\fBidlj \-fallTIE My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBMy\fRインタフェースの場合、2番目のコマンドにより、\fBMyPOATie\&.java\fRが生成されます。\fBMyPOATie\fRクラスへのコンストラクタは、delegateを取ります。この例では、デフォルトのPOAモデルを使用しているため、コンストラクタにもPOAが必要です。delegateに対して実装を提供する必要がありますが、この実装は\fBMyOperations\fRインタフェースから継承する必要があるのみで、その他のクラスから継承する必要はありません。これをORBと一緒に使用するには、たとえば次のように\fBMyPOATie\fRクラス内で実装をラップする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBORB orb = ORB\&.init(args, System\&.getProperties());\fR +\fB \fR +\fB// Get reference to rootpoa & activate the POAManager\fR +\fBPOA rootpoa = (POA)orb\&.resolve_initial_references("RootPOA");\fR +\fBrootpoa\&.the_POAManager()\&.activate();\fR +\fB \fR +\fB// create servant and register it with the ORB\fR +\fBMyServant myDelegate = new MyServant();\fR +\fBmyDelegate\&.setORB(orb); \fR +\fB \fR +\fB// create a tie, with servant being the delegate\&.\fR +\fBMyPOATie tie = new MyPOATie(myDelegate, rootpoa);\fR +\fB \fR +\fB// obtain the objectRef for the tie\fR +\fBMy ref = tie\&._this(orb);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +他の実装から継承する必要がある場合、標準の継承モデルではなくTieモデルを使用することもできます。Javaの場合は、インタフェースの継承の個数に制限はありませんが、クラスの継承に使用できるスロットは1つのみです。継承モデルを使用した場合は、そのスロットが占有されます。Tieモデルを使用すると、そのスロットが使用されず、ユーザーが独自の目的で使用できます。この方法には、間接性のレベルが1つ導入されるという短所があります。メソッドを呼び出すときに、余分なメソッド呼出しが1回発生します。 +.PP +サーバー側の生成の場合、Java SE 1\&.4より前のバージョンのJava言語にマッピングするIDLのバージョンと互換性のある、Tieモデルのバインディングです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-oldImplBase \-fall My\&.idl\fR +\fBidlj \-oldImplBase \-fallTIE My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBMy\fRインタフェースの場合、これにより、\fBMy_Tie\&.java\fRが生成されます。\fBMy_Tie\fRクラスへのコンストラクタは、\fBimpl\fRオブジェクトを取ります。\fBimpl\fRに対して実装を提供する必要がありますが、その実装は\fBHelloOperations\fRインタフェースから継承する必要があるのみで、その他のクラスから継承する必要はありません。しかし、これをORBと一緒に使用するには、たとえば次のように\fBMy_Tie\fR内で実装をラップする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBORB orb = ORB\&.init(args, System\&.getProperties());\fR + +\fB// create servant and register it with the ORB\fR +\fBMyServant myDelegate = new MyServant();\fR +\fBmyDelegate\&.setORB(orb); \fR +\fB \fR +\fB// create a tie, with servant being the delegate\&.\fR +\fBMyPOATie tie = new MyPOATie(myDelegate);\fR +\fB \fR +\fB// obtain the objectRef for the tie\fR +\fBMy ref = tie\&._this(orb);\fR + +.fi +.if n \{\ +.RE +.\} +.SS "発行されたファイルの代替位置の指定" +.PP +発行されたファイルを現在のディレクトリ以外のディレクトリに置くには、\fBi\fR\fBdlj \-td /altdir My\&.idl\fRのコマンドでコンパイラを呼び出します。 +.PP + +\fBMy\fRインタフェースの場合、バインディングは、\fB\&./My\&.java\fRではなく、\fB/altdir/My\&.java\fRなどに発行されます。 +.SS "インクルード・ファイルの代替位置の指定" +.PP +\fBMy\&.idl\fRファイルが別の\fBidl\fRファイルである\fBMyOther\&.idl\fRをインクルードする場合、コンパイラでは、\fBMyOther\&.idl\fRファイルがローカル・ディレクトリに存在することを前提としています。たとえば、それが\fB/includes\fRにある場合は、次のようなコマンドでコンパイラを呼び出します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-i /includes My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +たとえば、\fB/moreIncludes\fRにある\fBAnother\&.idl\fRも\fBMy\&.idl\fRにインクルードされているのであれば、次のようなコマンドでコンパイラを呼び出します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-i /includes \-i /moreIncludes My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +このような形式の\fBinclude\fRは長くなるため、インクルード・ファイルを検索する場所をコンパイラに指示するための別の方法が用意されています。この方法は、環境変数の考え方と似ています。\fBCLASSPATH\fR変数に一覧表示されているディレクトリ内にidl\&.configという名前のファイルを作成します。その\fBidl\&.config\fRの中に、次のような形式の行を入れます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBincludes=/includes;/moreIncludes\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コンパイラは、このファイルを検索し、インクルード・リストを読み込みます。この例では、ディレクトリの間の区切り文字はセミコロン(;)になっています。この区切り文字は、プラットフォームによって異なります。Windowsプラットフォームではセミコロンを使用し、Solaris、LinuxおよびOS Xプラットフォームではコロンを使用します。 +.SS "インクルード・ファイルに対するバインディングの発行" +.PP +デフォルトでは、コマンド行に指定した\fBidl\fRファイルで定義されているインタフェースや構造体などについてのみ、Javaバインディングが生成されます。インクルードされたファイルで定義されている型については生成されません。たとえば、次の2つの\fBidl\fRファイルについて考えてみます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMy\&.idl file:\fR +\fB \fR +\fB#include \fR +\fBinterface My\fR +\fB{\fR +\fB};\fR +\fB \fR +\fBMyOther\&.idl file:\fR +\fB \fR +\fBinterface MyOther\fR +\fB{\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +デフォルトのルールに関して警告があります。グローバル・スコープに表示される\fB#include\fR文は、前述のとおりに処理されます。これらの\fB#include\fR文は、インポート文と見なすことができます。囲まれたスコープ内に表示される\fB#include\fR文は、本当の意味での\fB#include\fR文として処理されます。つまり、インクルードされたファイルにあるコードが、元のファイルにそのまま表示されているかのように処理され、それに対してJavaバインディングが発行されます。次はその例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMy\&.idl file:\fR +\fB \fR +\fB#include \fR +\fBinterface My\fR +\fB{\fR +\fB #include \fR +\fB};\fR +\fB \fR +\fBMyOther\&.idl file:\fR +\fB \fR +\fBinterface MyOther\fR +\fB{\fR +\fB};\fR +\fB \fR +\fBEmbedded\&.idl\fR +\fB \fR +\fBenum E {one, two, three};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB idlj My\&.idl \fRを実行して、Javaファイルの次のリストを生成します。インポート文とみなされる\fB#include\fRに定義されていたため、\fBMyOther\&.java\fRは生成されませんでした。ただし、本当の意味での\fB#include\fRで定義されていたため、\fBE\&.java\fRは生成されました。\fBEmbedded\&.idl\fRファイルが\fBMy\fRインタフェースのスコープ内にインクルードされているため、\fBMy\fRのスコープ内(つまり、\fBMyPackage\fR内)に生成されています。\fB\-emitAll\fRフラグを使用した場合、インクルードされたすべてのファイルにあるすべての型が発行されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\&./MyHolder\&.java\fR +\fB\&./MyHelper\&.java\fR +\fB\&./_MyStub\&.java\fR +\fB\&./MyPackage\fR +\fB\&./MyPackage/EHolder\&.java\fR +\fB\&./MyPackage/EHelper\&.java\fR +\fB\&./MyPackage/E\&.java\fR +\fB\&./My\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.SS "パッケージの接頭辞の挿入" +.PP +ABCという名前の会社のために作業していて、次のようなIDLファイルを構築したとしましょう。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBWidgets\&.idl file:\fR +\fB \fR +\fBmodule Widgets\fR +\fB{\fR +\fB interface W1 {\&.\&.\&.};\fR +\fB interface W2 {\&.\&.\&.};\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +IDL\-to\-Javaコンパイラを介してこのファイルを実行した場合、W1およびW2に対するJavaバインディングは、\fBWidgets\fRパッケージ内に格納されます。業界の慣例によると、会社のパッケージは、\fBcom\&.\fRという名前のパッケージ内に置くことになっています。この慣例に従うには、パッケージ名を\fBcom\&.abc\&.Widgets\fRにする必要があります。このパッケージ接頭辞をWidgetsモジュールに付加するには、次のコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-pkgPrefix Widgets com\&.abc Widgets\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +Widgets\&.idlをインクルードしているIDLファイルがある場合は、そのコマンドにも\fB\-pkgPrefix\fRフラグが必要です。このフラグを指定しないと、そのIDLファイルは、\fBcom\&.abc\&.Widgets\fRパッケージではなく、\fBWidgets\fRパッケージを検索することになります。 +.PP +接頭辞が必要なパッケージがいくつもある場合は、前述のidl\&.configファイルで接頭辞を指定するのが簡単です。各パッケージの接頭辞行は、\fBPkgPrefix\&.=\fRの形式にする必要があります。前述の例の行では、\fBPkgPrefix\&.Widgets=com\&.abc\fRになります。このオプションは、リポジトリIDには影響しません。 +.SS "コンパイル前のシンボルの定義" +.PP +コンパイル用のシンボルがIDLファイル内で定義されていない場合は、そのシンボルを定義する必要があります。これは、たとえば、バインディング内にデバッグ・コードを組み入れるときに使用します。コマンド\fBidlj \-d MYDEF My\&.idl \fRは、My\&.idl内に行\fB#define MYDEF\fRを配置した場合と同等になります。 +.SS "既存のバインディングの保持" +.PP +Javaバインディング・ファイルがすでに存在する場合は、\fB\-keep\fRフラグを指定すると、コンパイラによる上書きを回避できます。デフォルトでは、すでに存在するかどうかにかかわらず、すべてのファイルが生成されます。これらのファイルをカスタマイズした場合(ただし、それらの内容が正確であるとき以外はカスタマイズは避ける)、\fB\-keep\fRオプションは有用です。コマンド\fBidlj \-keep My\&.idl\fRは、すでに存在しないすべてのクライアント側バインディングを発行します。 +.SS "コンパイルの進捗状況の表示" +.PP +IDL\-to\-Javaコンパイラは、実行の各段階で状態メッセージを生成します。\fB\-v\fRオプションを使用して、\fBidlj \-v My\&.idl\fRのような冗長モードをアクティブ化します。 +.PP +デフォルトでは、コンパイラは冗長モードでは実行されません。 +.SS "バージョン情報の表示" +.PP +IDL\-to\-Javaコンパイラのビルド・バージョンを表示するには、コマンドライン\fBidlj \-version\fRで\fB\-version\fRオプションを指定します。 +.PP +バージョン情報は、コンパイラによって生成されたバインディング内にも書き込まれています。このオプションをコマンドラインに指定すると、それ以外のオプションを指定しても、すべて無視されます。 +.SH "オプション" +.PP +\-d \fIsymbol\fR +.RS 4 +このオプションは、IDLファイルに次のような行を追加した場合と等価です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#define \fR\fB\fIsymbol\fR\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-demitAll +.RS 4 +\fB#include\fRファイル内で定義されているものも含めて、すべての型を発行します。 +.RE +.PP +\-fside +.RS 4 +発行するバインディングを定義します。\fBside\fRパラメータには、\fBclient\fR、\fBserver\fR、\fBserverTIE\fR、\fBall\fRまたは\fBallTIE\fRを指定できます。\fB\-fserverTIE\fRまたは\fB\-fallTIE\fRオプションを指定すると、委譲モデル・スケルトンが発行されます。フラグを指定しない場合、\fB\-fclient\fRにデフォルト設定されます。 +.RE +.PP +\-i \fIinclude\-path\fR +.RS 4 +デフォルトでは、インクルード・ファイルは現在のディレクトリから検索されます。このオプションを指定すると、他のディレクトリを追加できます。 +.RE +.PP +\-i \fIkeep\fR +.RS 4 +生成されるファイルがすでに存在している場合は、そのファイルが上書きされません。デフォルトでは、上書きされます。 +.RE +.PP +\-noWarn +.RS 4 +警告メッセージを表示しないようにします。 +.RE +.PP +\-oldImplBase +.RS 4 +1\&.4より前のJDK ORBと互換性のあるスケルトンを生成します。デフォルトでは、POA継承モデルのサーバー側バインディングが生成されます。このオプションを指定すると、\fBImplBase\fR継承モデルのクラスであるサーバー側バインディングが生成されるので、以前のリリースのJavaプログラミング言語との後方互換性が得られます。 +.RE +.PP +\-pkgPrefix \fItype\fR \fIprefix\fR +.RS 4 +\fBtype\fRがファイル・スコープで検出された場合は、その型に対して生成されるすべてのファイルについて、生成されるJavaパッケージ名に\fBprefix\fRという接頭辞が付加されます。typeは、トップレベル・モジュールの単純名か、どのモジュールよりも外側で定義されたIDL型の単純名のどちらかです。 +.RE +.PP +\-pkgTranslate \fItype\fR \fIpackage\fR +.RS 4 +識別子の中にモジュール名typeが検出されると、生成されるJavaパッケージ内のすべてのファイルについて、識別子の中のその名前がpackageで置き換えられます。最初に\fBpkgPrefix\fRの変更が行われます。typeの値は、トップレベルのモジュールの単純名、またはすべてのモジュールの外部で定義されたIDL型の単純名で、完全なパッケージ名に正確に一致する必要があります。 +.sp +複数の変換が識別子に一致する場合、次の例に示すように、最も長い一致が選択されます。 +.sp +\fBコマンド\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpkgTranslate type pkg \-pkgTranslate type2\&.baz pkg2\&.fizz\fR + +.fi +.if n \{\ +.RE +.\} +\fB結果の変換\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtype => pkg\fR +\fBtype\&.ext => pkg\&.ext\fR +\fBtype\&.baz => pkg2\&.fizz\fR +\fBtype2\&.baz\&.pkg => pkg2\&.fizz\&.pkg\fR + +.fi +.if n \{\ +.RE +.\} +パッケージ名\fBorg\fR、\fBorg\fR\&.o\fBmg\fR、または\fBorg\&.omg\fRのサブパッケージは、変換できません。これらのパッケージ名を変換しようとすると、互換性のないコードが生成され、\fB\-pkgTranslate\fRの後の最初の引数としてそれらのパッケージを使用すると、エラーとして扱われます。 +.RE +.PP +\-skeletonName \fIxxx%yyy\fR +.RS 4 +\fBxxx%yyy\fRが、スケルトンに名前を付けるパターンとして使用されます。デフォルトは次のとおりです。\fBPOA\fRベース・クラスの場合は\fB%POA\fR +(\fB\-fserver\fRまたは\fB\-fall\fR)、\fBoldImplBase\fRクラスの場合は\fB_%ImplBase\fR +(\-\fBoldImplBase\fR)および(\fB\-fserver\fRまたは\fB\-fall\fR))。 +.RE +.PP +\-td \fIdir\fR +.RS 4 +出力ディレクトリとして、現在のディレクトリではなく、\fIdir\fRが使用されます。 +.RE +.PP +\-tieName \fIxxx%yyy\fR +.RS 4 +パターンに従って、\fBxxx%yyy\fRを使用します。デフォルトは次のとおりです。\fBPOA\fRベース・クラスの場合は\fB%POA\fR +(\fB\-fserverTieまたは\-fallTie\fR)、\fBoldImplBase\fR +tieクラスの場合は\fB_%Tie\fR +(\-\fBoldImplBase\fR)および(\fB\-fserverTie\fRまたは\fB\-fallTie\fR))。 +.RE +.PP +\-nowarn、\-verbose +.RS 4 +リリース情報を表示して終了します。 +.RE +.PP +\-version +.RS 4 +リリース情報を表示して終了します。 +.RE +.SH "制限事項" +.PP +グローバル・スコープ内のエスケープされた識別子は、IDLプリミティブ型の\fBObject\fRまたは\fBValueBase\fRと同じ綴りにしないでください。これは、シンボル表がこれらの識別子でプリロードされているためです。これらの再定義を許可すると、元の定義が上書きされます。これは、おそらく恒久的な制約です。 +.PP +\fBfixed\fRというIDL型はサポートされていません。 +.SH "既知の問題" +.PP +グローバル識別子についてインポートが生成されません。予期されないローカル\fBimpl\fRオブジェクトを呼び出すと、例外を受け取ります。しかし、その原因は、\fBServerDelegate\fR +DSIコード内の\fBNullPointerException\fRにあるようです。 +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jar.1 b/jdk-1.8.0.281/man/ja/man1/jar.1 new file mode 100755 index 0000000..f895305 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jar.1 @@ -0,0 +1,519 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jar +.\" Language: Japanese +.\" Date: 2013年11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jar" "1" "2013年11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jar \- Java Archive (JAR)ファイルを操作します。 +.SH "概要" +.PP +JARファイルの作成 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar c\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルの更新 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar u\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルの抽出 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar\fR \fBx\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルのコンテンツのリスト +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar\fR \fBt\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルへの索引の追加 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar\fR \fBi\fR \fIjarfile\fR [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.SH "説明" +.PP +\fBjar\fRコマンドは、ZIPおよびZLIB圧縮形式に基づく汎用のアーカイブおよび圧縮ツールです。ただし、\fBjar\fRコマンドは、主にいくつかのJavaアプレットやアプリケーションを単一のアーカイブにパッケージ化するように設計されました。アプレットやアプリケーションのコンポーネント(ファイル、イメージ、およびサウンド)が1つのアーカイブに結合されていると、Javaエージェント(ブラウザなど)は、それらのコンポーネントを1回のHTTPトランザクションでダウンロードすることができ、コンポーネントごとに新しい接続が不要になります。これにより、ダウンロード時間が大幅に短縮されます。また、\fBjar\fRコマンドはファイルの圧縮も行うため、ダウンロード時間がさらに短縮されます。また、\fBjar\fRコマンドによって、ファイル内の個々のエントリにアプレット作成者による署名を書き込めるため、配布元の認証が可能になります。JARファイルは、圧縮されているかどうかにかかわらず、クラス・パスのエントリとして使用できます。 +.PP +\fBjar\fRコマンドの構文は、\fBtar\fRコマンドの構文に似ています。必須の\fI操作の引数\fRの1つで定義された複数の操作モードがあります。他の引数は、操作の動作を変更する\fIオプション\fR、または操作を実行するために必要な\fIオペランド\fRを使用します。 +.SH "操作の引数" +.PP +\fBjar\fRコマンドを使用する場合は、次の操作の引数のいずれかを指定して実行される操作を選択する必要があります。コマンド行で他の1文字のオプションと混在させることができますが、通常、操作の引数は指定される最初の引数です。 +.PP +c +.RS 4 +新しいJARアーカイブを作成します。 +.RE +.PP +i +.RS 4 +JARアーカイブの索引情報を生成します。 +.RE +.PP +t +.RS 4 +JARアーカイブのコンテンツをリストします。 +.RE +.PP +u +.RS 4 +JARアーカイブを更新します。 +.RE +.PP +x +.RS 4 +JARアーカイブからファイルを抽出します。 +.RE +.SH "オプション" +.PP +次のオプションを使用して、JARファイルを作成、更新、抽出または表示する方法をカスタマイズします。 +.PP +e +.RS 4 +\fIentrypoint\fRオペランドで指定されるクラスを、実行可能JARファイルにバンドルされるスタンドアロンJavaアプリケーションのエントリ・ポイントに設定します。このオプションを使用すると、マニフェスト・ファイル内の\fBMain\-Class\fR属性値が作成またはオーバーライドされます。\fBe\fRオプションは、JARファイルの作成時(\fBc\fR)または更新時(\fBu\fR)に使用できます。 +.sp +たとえば、次のコマンドでは、\fBMain\&.jar\fRアーカイブが\fBMain\&.class\fRファイルとともに作成されますが、その際、マニフェスト内の\fBMain\-Class\fR属性値は\fBMain\fRに設定されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar cfe Main\&.jar Main Main\&.class\fR + +.fi +.if n \{\ +.RE +.\} +Java Runtime Environment (JRE)は、次のコマンドを実行して、このアプリケーションを直接呼び出すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-jar Main\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +あるパッケージ内にエントリ・ポイントのクラス名が含まれている場合、ドット(\&.)またはスラッシュ(/)のいずれかを区切り文字として使用できます。たとえば、\fBMain\&.class\fRが\fBmydir\fRという名前のパッケージに含まれている場合、エントリ・ポイントは次のいずれかの方法で指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar \-cfe Main\&.jar mydir/Main mydir/Main\&.class\fR +\fBjar \-cfe Main\&.jar mydir\&.Main mydir/Main\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fB注記\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +注意 +特定のマニフェストにも\fBMain\-Class\fR属性が含まれている場合に\fBm\fRオプションと\fBe\fRオプションの両方を同時に指定すると、\fBMain\-Class\fRの指定があいまいになります。このあいまいさによってエラーが発生し、\fBjar\fRコマンドの作成や更新の操作が終了します。 +T} +.TE +.sp 1 +.sp .5v +.RE +.RE +.PP +f +.RS 4 +\fIjarfile\fRオペランドで指定されたファイルを、作成(\fBc\fR)、更新(\fBu\fR)、抽出(\fBx\fR)または表示(\fBt\fR)されるJARファイルの名前に設定します。\fBf\fRオプションおよび\fIjarfile\fRオペランドを省略すると、\fBjar\fRコマンドに、\fBstdin\fRからのJARファイル名を受け入れるか(\fBx\fRおよび\fBt\fRの場合)、JARファイルを\fBstdout\fRに送信すること(\fBc\fRおよび\fBu\fRの場合)が指示されます。 +.RE +.PP +m +.RS 4 +(\fBMETA\-INF/MANIFEST\&.MF\fRのアーカイブにある) +\fBjar\fRコマンドのマニフェスト・ファイルの\fBmanifest\fRオペランドで指定されたファイルから、属性の名前と値のペアを含めます。\fBjar\fRコマンドは、同じ名前のエントリがすでに存在する場合を除き、属性の名前と値をJARファイルに追加します。同じ名前のエントリがすでに存在する場合、\fBjar\fRコマンドは属性の値を更新します。\fBm\fRオプションは、JARファイルの作成時(\fBc\fR)または更新時(\fBu\fR)に使用できます。 +.sp +デフォルトのマニフェスト・ファイルには含まれないマニフェストに、特別な目的の名前\-値の属性ペアを追加できます。たとえば、ベンダー情報、リリース情報、パッケージ・シーリングを指定する属性、またはJARにバンドルされたアプリケーションを実行可能にするための属性を追加できます。\fBm\fRオプションの使用例は、http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.htmlにある +プログラムのパッケージ化に関する項を参照してください。 +.RE +.PP +M +.RS 4 +マニフェスト・ファイル・エントリを作成しない(\fBc\fRおよび\fBu\fRの場合)か、またはマニフェスト・ファイル・エントリが存在する場合は削除します(\fBu\fRの場合)。\fBM\fRオプションは、JARファイルの作成時(\fBc\fR)または更新時(\fBu\fR)に使用できます。 +.RE +.PP +n +.RS 4 +JARファイルの作成(\fBc\fR)時に、このオプションは、コンテンツがpack200(1)コマンドのパックおよびアンパック操作の影響を受けないようにアーカイブを正規化します。この正規化を使用しない場合、署名付きJARの署名は無効になります。 +.RE +.PP +v +.RS 4 +詳細な出力を標準出力に生成します。例を参照してください。 +.RE +.PP +0 +.RS 4 +(ゼロ) ZIP圧縮を使用しないでJARファイルを作成(\fBc\fR)または更新(\fBu\fR)します。 +.RE +.PP +\-C \fIdir\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、このオプションは\fIfile\fRオペランドで指定されたファイルの処理中にディレクトリを一時的に変更します。この操作は、\fBtar\fRユーティリティの\fB\-C\fRオプションと同様になることを目的としています。たとえば、次のコマンドによって、\fBclasses\fRディレクトリに変更され、そのディレクトリから\fBmy\&.jar\fRに\fBBar\&.class\fRファイルが追加されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar uf my\&.jar \-C classes Bar\&.class\fR + +.fi +.if n \{\ +.RE +.\} +次のコマンドでは、\fBclasses\fRディレクトリに移動し、classesディレクトリ内のすべてのファイルを\fBmy\&.jar\fRに追加します(JARファイルには\fBclasses\fRディレクトリを作成しません)。次に元のディレクトリに戻ってから、\fBbin\fRディレクトリに移動し、\fBXyz\&.class\fRを\fBmy\&.jar\fRに追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar uf my\&.jar \-C classes \&. \-C bin Xyz\&.class\fR + +.fi +.if n \{\ +.RE +.\} +\fBclasses\fRに\fBbar1\fRファイルと\fBbar2\fRファイルが含まれている場合、前述のコマンドを実行した後、JARファイルには次のものが含まれます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% \fR\fB\fBjar tf my\&.jar\fR\fR +\fBMETA\-INF/\fR +\fBMETA\-INF/MANIFEST\&.MF\fR +\fBbar1\fR +\fBbar2\fR +\fBXyz\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定したJVMオプションを、JREがJARファイルを実行する際に使用するように設定します。JVMオプションは、java(1)コマンドのリファレンス・ページで説明されています。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。 +.RE +.SH "オペランド" +.PP +次のオペランドは、\fBjar\fRコマンドで認識されます。 +.PP +\fIfile\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、\fIfile\fRオペランドは、アーカイブに追加する必要のあるファイルまたはディレクトリのパスと名前を定義します。JARファイルの抽出(\fBx\fR)またはコンテンツのリスト(\fBt\fR)時に、\fIfile\fRオペランドは抽出またはリストするファイルのパスと名前を定義します。少なくとも1つの有効なファイルまたはディレクトリを指定する必要があります。複数の\fIfile\fRオペランドを空白で区切ります。\fIentrypoint\fR、\fIjarfile\fRまたは\fImanifest\fRオペランドが使用される場合は、その後に\fIfile\fRオペランドを指定する必要があります。 +.RE +.PP +\fIentrypoint\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、\fIentrypoint\fRオペランドは、実行可能JARファイルにバンドルされているスタンドアロンJavaアプリケーションのエントリ・ポイントとなるクラスの名前を定義します。\fBe\fRオプションが存在する場合は\fIentrypoint\fRオペランドを指定する必要があります。 +.RE +.PP +\fIjarfile\fR +.RS 4 +作成(\fBc\fR)、更新(\fBu\fR)、抽出(\fBx\fR)または表示(\fBt\fR)するファイルの名前を定義します。\fBf\fRオプションが存在する場合は\fIjarfile\fRオペランドを指定する必要があります。\fBf\fRオプションおよび\fIjarfile\fRオペランドを省略すると、\fBjar\fRコマンドに、\fBstdin\fRからのJARファイル名を受け入れるか(\fBx\fRおよび\fBt\fRの場合)、JARファイルを\fBstdout\fRに送信すること(\fBc\fRおよび\fBu\fRの場合)が指示されます。 +.sp +JARファイルを索引付け(\fBi\fR)する場合は、\fBf\fRオプションを指定しないで\fIjarfile\fRオペランドを指定します。 +.RE +.PP +\fImanifest\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、\fImanifest\fRオペランドはJARファイルの\fBMANIFEST\&.MF\fRに含める属性の名前と値を持つ既存のマニフェスト・ファイルを定義します。\fBf\fRオプションが存在する場合は\fImanifest\fRオペランドを指定する必要があります。 +.RE +.PP +\fI@arg\-file\fR +.RS 4 +\fBjar\fRコマンドを短縮または簡素化するには、別のテキスト・ファイル内の引数を指定し、接頭辞としてアットマーク(@)を付けて\fBjar\fRコマンドに渡すことができます。\fBjar\fRコマンドは、アットマーク文字で始まる引数を見つけると、そのファイルの内容を展開して引数リストに挿入します。 +.sp +引数ファイルには、\fBjar\fRコマンドのオプションと引数(引数ファイルをサポートしない起動ツールに渡される\fB\-J\fRオプションを除く)を含めることができます。ファイル内の引数は、空白または改行文字で区切ることができます。引数ファイル内のファイル名は、\fBjar\fRコマンドを実行できる現在のディレクトリに対して相対的であり、引数ファイルの場所に対しては相対的ではありません。通常はオペレーティング・システム・シェルによって展開されるアスタリスク(*)などのワイルドカードは展開されません。 +.sp +次の例は、\fBfind\fRコマンドによる現在のディレクトリ出力からのファイル名で\fBclasses\&.list\fRファイルを作成する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBfind \&. \-name \*(Aq*\&.class\*(Aq \-print > classes\&.list\fR + +.fi +.if n \{\ +.RE +.\} +\fBjar\fRコマンドを実行し、\fI@arg\-file\fR構文を使用して\fBclasses\&.list\fRファイルを渡すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar cf my\&.jar @classes\&.list\fR + +.fi +.if n \{\ +.RE +.\} +引数ファイルはパスを指定できますが、相対パスが記述された引数ファイル内のすべてのファイル名は、渡されたパスに対して相対的ではなく、\fBjar\fRコマンドの現在の作業ディレクトリに相対的となります。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar @dir/classes\&.list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "注意" +.PP +\fBe\fR、\fBf\fRおよび\fBm\fRオプションは、\fIentrypoint\fR、\fIjarfile\fRおよび\fImanifest\fRオペランドと同じ順序でコマンド行に出現する必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar cmef myManifestFile MyMainClass myFile\&.jar *\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.SH "例" +.PP +\fB例 1 \fR冗長な出力による現在のディレクトリからのすべてのファイルの追加 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% ls\fR +\fB1\&.au Animator\&.class monkey\&.jpg\fR +\fB2\&.au Wave\&.class spacemusic\&.au\fR +\fB3\&.au at_work\&.gif\fR + +\fB% jar cvf bundle\&.jar *\fR +\fBadded manifest\fR +\fBadding: 1\&.au(in = 2324) (out= 67)(deflated 97%)\fR +\fBadding: 2\&.au(in = 6970) (out= 90)(deflated 98%)\fR +\fBadding: 3\&.au(in = 11616) (out= 108)(deflated 99%)\fR +\fBadding: Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fR +\fBadding: Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fR +\fBadding: at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fR +\fBadding: monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fR +\fBadding: spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRサブディレクトリからのファイルの追加 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% ls \-F\fR +\fBaudio/ classes/ images/\fR +\fB% jar cvf bundle\&.jar audio classes images\fR +\fBadded manifest\fR +\fBadding: audio/(in = 0) (out= 0)(stored 0%)\fR +\fBadding: audio/1\&.au(in = 2324) (out= 67)(deflated 97%)\fR +\fBadding: audio/2\&.au(in = 6970) (out= 90)(deflated 98%)\fR +\fBadding: audio/3\&.au(in = 11616) (out= 108)(deflated 99%)\fR +\fBadding: audio/spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fR +\fBadding: classes/(in = 0) (out= 0)(stored 0%)\fR +\fBadding: classes/Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fR +\fBadding: classes/Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fR +\fBadding: images/(in = 0) (out= 0)(stored 0%)\fR +\fBadding: images/monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fR +\fBadding: images/at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fR + +\fB% ls \-F\fR +\fBaudio/ bundle\&.jar classes/ images/\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRJARのコンテンツのリスト +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% jar tf bundle\&.jar\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMETA\-INF/\fR +\fBMETA\-INF/MANIFEST\&.MF\fR +\fBaudio/1\&.au\fR +\fBaudio/2\&.au\fR +\fBaudio/3\&.au\fR +\fBaudio/spacemusic\&.au\fR +\fBclasses/Animator\&.class\fR +\fBclasses/Wave\&.class\fR +\fBimages/monkey\&.jpg\fR +\fBimages/at_work\&.gif\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fR索引の追加 +.RS 4 +株式取引のアプリケーションの相互依存クラスを、\fBmain\&.jar\fR、\fBbuy\&.jar\fRおよび\fBsell\&.jar\fRの3つのJARファイルに分割する場合、\fBi\fRオプションを使用します。\fBmain\&.jar\fRマニフェスト内の\fBClass\-Path\fR属性を指定する場合、\fBi\fRオプションを使用して、アプリケーションのクラス・ロードの速度を向上できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBClass\-Path: buy\&.jar sell\&.jar\fR +\fBjar i main\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +\fBINDEX\&.LIST\fRファイルが\fBMETA\-INF\fRディレクトリに挿入されます。これにより、アプリケーションのクラス・ローダーによってクラスまたはリソースの検索が行われるときに、指定したJARファイルがダウンロードされるようになります。 +.sp +アプリケーションのクラス・ローダーは、このファイルに格納されている情報を使用して、効率的にクラスをロードします。ディレクトリをコピーするには、最初に\fBdir1\fR内のファイルを\fBstdout\fRに圧縮してから、\fBstdin\fRから\fBdir2\fRにパイプラインを作成して抽出します(\fB\-f\fRオプションは両方の\fBjar\fRコマンドで省略します)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB(cd dir1; jar c \&.) | (cd dir2; jar x)\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +pack200(1)\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.htmlにある +JavaチュートリアルのJARに関する項 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jarsigner.1 b/jdk-1.8.0.281/man/ja/man1/jarsigner.1 new file mode 100755 index 0000000..2f8b163 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jarsigner.1 @@ -0,0 +1,1078 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jarsigner +.\" Language: Japanese +.\" Date: 2013年11月21日 +.\" SectDesc: セキュリティ・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jarsigner" "1" "2013年11月21日" "JDK 8" "セキュリティ・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jarsigner \- Javaアーカイブ(JAR)ファイルに対して署名および検証を行います。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner\fR [ \fIoptions\fR ] \fIjar\-file\fR \fIalias\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner\fR \fB\-verify\fR [ \fIoptions\fR ] \fIjar\-file\fR [\fIalias \&.\&.\&.\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\-verify +.RS 4 +\fB\-verify\fRオプションでは、JARファイル名の後に0個以上のキーストア別名を指定できます。\fB\-verify\fRオプションが指定された場合、\fBjarsigner\fRコマンドでは、JARファイル内の各署名付きエンティティの検証に使用される証明書が、いずれかのキーストア別名に一致することをチェックします。別名は、\fB\-keystore\fRで指定されたキーストア内またはデフォルトのキーストア内に定義されます。 +.sp +\fB\-strict\fRオプションも指定した場合、\fBjarsigner\fRコマンドにより重大な警告が検出されると、メッセージ「jarが検証されました。署名者エラー」が表示されます。 +.RE +.PP +\fIjar\-file\fR +.RS 4 +署名されるJARファイル。 +.sp +\fB\-strict\fRオプションも指定した場合、\fBjarsigner\fRコマンドにより重大な警告が検出されると、メッセージ「jarは署名されました \- 署名者エラーがあります。」というメッセージが表示されます。 +.RE +.PP +\fIalias\fR +.RS 4 +別名は、\fB\-keystore\fRで指定されたキーストア内またはデフォルトのキーストア内に定義されます。 +.RE +.SH "説明" +.PP +\fBjarsigner\fRツールには、次の2つの目的があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javaアーカイブ(JAR)ファイルに署名する目的。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +署名付きJARファイルの署名と整合性を検証する目的。 +.RE +.PP +JAR機能を使用すると、クラス・ファイル、イメージ、サウンドおよびその他のデジタル・データを単一のファイルにパッケージ化できるので、ファイルを迅速かつ容易に配布できます。\fBjar\fRという名前のツールを使用して、開発者はJARファイルを作成できます。(技術的な観点から言えば、すべてのZIPファイルもJARファイルとみなすことができます。ただし、\fBjar\fRコマンドによって作成されたJARファイル、または\fBjarsigner\fRコマンドによって処理されたJARファイルには、\fBMETA\-INF/MANIFEST\&.MF\fRファイルも含まれています。) +.PP +デジタル署名は、なんらかのデータ(署名の対象となるデータ)、およびエンティティ(人、会社など)の秘密鍵から計算されるビットの文字列です。手書きの署名同様、デジタル署名には多くの利点があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +署名の生成に使用された秘密鍵に対応する公開鍵を使用する計算によって、それが本物であることを検証できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +秘密鍵が他人に知られない限り、デジタル署名の偽造は不可能です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +これは、署名が付いたデータの機能であり、他のデータの署名となるように要求できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +署名付きデータは変更できません。データが変更された場合、署名によって本物であると検証できません。 +.RE +.PP +ファイルに対してエンティティの署名を生成するには、まず、エンティティは、そのエンティティに関連する公開鍵/秘密鍵のペアと、公開鍵を認証する1つ以上の証明書を持つ必要があります。証明書とは、あるエンティティからのデジタル署名付きの文書で、別のエンティティの公開鍵が特定の値を持つことを示しています。 +.PP +\fBjarsigner\fRコマンドは、キーストアからの鍵と証明書情報を使用して、JARファイルのデジタル署名を生成します。キーストアは、秘密鍵、および対応する公開鍵を認証する、秘密鍵に関連したX\&.509証明書チェーンのデータベースです。\fBkeytool\fRコマンドを使用して、キーストアを作成および管理します。 +.PP +\fBjarsigner\fRコマンドでは、エンティティの秘密鍵を使用して署名を生成します。署名付きJARファイルには、特に、ファイルへの署名に使用する秘密鍵に対応する公開鍵のキーストアからの証明書のコピーが含まれます。\fBjarsigner\fRコマンドでは、内部(署名ブロック・ファイル内)の証明書を使用して、署名付きJARファイルのデジタル署名を検証できます。 +.PP +\fBjarsigner\fRコマンドでは、署名証明書の有効期間中にJARファイルが署名されたされたかどうかをシステムやデプロイヤ(Java Plug\-inを含む)がチェックできる、タイムスタンプを含む署名を生成できます。さらに、APIを使用すると、アプリケーションでタイムスタンプ情報を取得できます。 +.PP +現時点では、\fBjarsigner\fRコマンドでは、\fBjar\fRコマンドまたはZIPファイルによって作成されたJARファイルのみに署名できます。JARファイルはZIPファイルと同じですが、JARファイルには\fBMETA\-INF/MANIFEST\&.MF\fRファイルも含まれている点が異なります。\fBMETA\-INF/MANIFEST\&.MF\fRファイルは、\fBjarsigner\fRコマンドによってZIPファイルに署名する際に作成されます。 +.PP +デフォルトの\fBjarsigner\fRコマンドの動作では、JARまたはZIPファイルに署名します。\fB\-verify\fRオプションを使用して、署名付きJARファイルを検証します。 +.PP +\fBjarsigner\fRコマンドは、署名または検証の後に署名者の証明書の検証も試行します。検証エラーまたはその他の問題が発生すると、コマンドにより警告メッセージが生成されます。\fB\-strict\fRオプションを指定した場合、コマンドにより重大な警告がエラーとして処理されます。エラーと警告を参照してください。 +.SS "キーストアの別名" +.PP +キーストアのすべてのエンティティは、一意の別名を使用してアクセスされます。 +.PP +\fBjarsigner\fRコマンドを使用してJARファイルに署名するときは、署名の生成に必要な秘密鍵を含むキーストア・エントリの別名を指定する必要があります。たとえば、次のコマンドでは、\fBworking\fRディレクトリの\fBmystore\fRという名前のキーストアに含まれる別名\fBduke\fRに関連付けられた秘密鍵を使用して、\fBMyJARFile\&.jar\fRという名前のJARファイルに署名します。出力ファイルは指定されていないため、\fBMyJARFile\&.jar\fRは署名付きのJARファイルによって上書きされます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore \-storepass \fR +\fB \-keypass MyJARFile\&.jar duke\fR + +.fi +.if n \{\ +.RE +.\} +.PP +キーストアはパスワードで保護されているので、ストアのパスワードを指定する必要があります。コマンド行で指定しないと、入力を求められます。同様に、秘密鍵もキーストア内でパスワードによって保護されているため、秘密鍵のパスワードを指定する必要があります。コマンド行でパスワードを指定していない場合、または指定したパスワートが保存されているパスワードと同じではない場合は、パスワードの入力を求められます。 +.SS "キーストアの場所" +.PP +\fBjarsigner\fRコマンドには、使用するキーストアのURLを指定する\fB\-keystore\fRオプションがあります。キーストアはデフォルトで、\fBuser\&.home\fRシステム・プロパティで決まるユーザーのホーム・ディレクトリの\fB\&.keystore\fRという名前のファイル内に格納されます。 +.PP +Oracle Solarisシステムの場合、\fBuser\&.home\fRは、ユーザーのホーム・ディレクトリにデフォルト設定されます。 +.PP +\fB\-keystore\fRオプションからの入力ストリームは、\fBKeyStore\&.load\fRメソッドに渡されます。URLとして\fBNONE\fRが指定されている場合は、nullのストリームが\fBKeyStore\&.load\fRメソッドに渡されます。\fBNONE\fRは、\fBKeyStore\fRクラスがファイルベースではない場合、たとえば、ハードウェア・トークン・デバイスに置かれている場合に指定します。 +.SS "キーストアの実装" +.PP +\fBjava\&.security package\fRで提供されている\fBKeyStore\fRクラスは、キーストア内の情報へのアクセスおよび情報の変更を行うための、明確に定義された多くのインタフェースを提供します。複数の異なる固定実装を指定することができ、各実装は特定のタイプのキーストアを対象とします。 +.PP +現在、キーストアの実装を使用する2つのコマンド行ツール(\fBkeytool\fRと\fBjarsigner\fR)、およびポリシー・ツールという名前の1つのGUIベースのツールがあります。\fBKeyStore\fRクラスは公開されているため、JDKユーザーは、それを使用する他のセキュリティ・アプリケーションを書き込むことができます。 +.PP +Oracleが提供する組込みのデフォルトの実装があります。これは、JKSという名前の独自のキーストア・タイプ(形式)を使用するもので、キーストアをファイルとして実装しています。組込みの実装では、各秘密鍵は個別のパスワードによって保護され、キーストア全体の整合性は(秘密鍵とは別の)パスワードによって保護されます。 +.PP +キーストアの実装はプロバイダベースで、つまり、\fBKeyStore\fRクラスにより提供されるアプリケーション・インタフェースは、サービス・プロバイダ・インタフェース(SPI)に関して実装されます。対応する\fBKeystoreSpi\fR抽象クラスがあり、これも\fBjava\&.security package\fRに含まれています。このクラスが、プロバイダが実装する必要のあるサービス・プロバイダ・インタフェースのメソッドを定義しています。ここで、プロバイダとは、Java Security APIによってアクセス可能なサービスのサブセットに対し、その固定実装を提供するパッケージまたはパッケージの集合のことです。キーストアの実装を提供するには、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/HowToImplAProvider\&.htmlにある +Java暗号化アーキテクチャのプロバイダの実装方法で説明しているように、クライアントはプロバイダを実装し、\fBKeystoreSpi\fRサブクラスの実装を提供する必要があります。 +.PP +アプリケーションでは、\fBKeyStore\fRクラスの\fBgetInstance\fRファクトリ・メソッドを使用して、様々なプロバイダから異なるタイプのキーストアの実装を選択できます。キーストアのタイプは、キーストア情報の格納形式とデータ形式を定義するとともに、キーストア内の秘密鍵とキーストア自体の整合性を保護するために使用されるアルゴリズムを定義します。異なるタイプのキーストアの実装には、互換性はありません。 +.PP +\fBjarsigner\fRおよび\fBpolicytool\fRコマンドは、URLを使用して指定できる任意の場所からファイルベースのキーストアを読み取ることができます。また、これらのコマンドは、Windows上のMSCAPIおよびすべてのプラットフォーム上のPKCS11で提供されるような非ファイルベースのキーストアを読み取ることができます。 +.PP +\fBjarsigner\fRコマンドおよび\fBkeytool\fRコマンドの場合、\fB\-storetype\fRオプションを使用して、コマンド行でキーストアのタイプを指定できます。ポリシー・ツールの場合、\fB「キーストア」\fRメニューの\fB「編集」\fRコマンドを使用して、キーストアのタイプを指定できます。 +.PP +ユーザーがキーストアのタイプを明示的に指定しなかった場合、セキュリティ・プロパティ・ファイルで指定された\fBkeystore\&.type\fRプロパティの値に基づいて、ツールによってキーストアの実装が選択されます。このセキュリティ・プロパティ・ファイルは\fBjava\&.security\fRと呼ばれ、JDKセキュリティ・プロパティ・ディレクトリ\fBjava\&.home/lib/security\fR内に存在しています。ここで、\fBjava\&.home\fRは実行時環境のディレクトリです。\fBjre\fRディレクトリは、JDKまたはJava Runtime Environment (JRE)の最上位のディレクトリにあります。 +.PP +各ツールは、\fBkeystore\&.type\fRの値を取得し、そのタイプのキーストアを実装しているプロバイダが見つかるまで、インストールされているすべてのプロバイダを調べます。目的のプロバイダが見つかると、そのプロバイダからのキーストアの実装を使用します。 +.PP +\fBKeyStore\fRクラスに定義されているstaticメソッド\fBgetDefaultType\fRを使用すると、アプリケーションやアプレットから\fBkeystore\&.type\fRプロパティの値を取得できます。次のコードの行では、\fBkeystore\&.type property\fRで指定された、デフォルトのキーストア・タイプのインスタンスを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBKeyStore keyStore = KeyStore\&.getInstance(KeyStore\&.getDefaultType());\fR + +.fi +.if n \{\ +.RE +.\} +.PP +デフォルトのキーストア・タイプは、\fBjks\fR +(Oracleが提供する独自のタイプのキーストアの実装)です。これは、セキュリティ・プロパティ・ファイル内の次の行によって指定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=jks\fR + +.fi +.if n \{\ +.RE +.\} +.PP +キーストアのタイプの指定では、大文字と小文字は区別されません。たとえば、\fBJKS\fRは\fBjks\fRと同じになります。 +.PP +ツールでデフォルト以外のキーストアの実装を使用するには、その行を変更して別のキーストアのタイプを指定します。たとえば、\fBpkcs12\fRと呼ばれるキーストアのタイプのキーストアの実装を提供するプロバイダ・パッケージがある場合、行を次のように変更します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=pkcs12\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB注意:\fR +PKCS 11プロバイダ・パッケージを使用する場合、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/p11guide\&.htmlにある +Java PKCS #11リファレンス・ガイドの「KeyTool」および「JarSigner」を参照してください。 +.SS "サポートされるアルゴリズム" +.PP +デフォルトで、\fBjarsigner\fRコマンドでは次のいずれかのアルゴリズムを使用してJARファイルに署名します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHA1ダイジェスト・アルゴリズムを使用したデジタル署名アルゴリズム(DSA) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHA256ダイジェスト・アルゴリズムを使用したRSAアルゴリズム。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHA256と楕円曲線デジタル署名アルゴリズム(ECDSA)を使用した楕円曲線(EC)暗号方式アルゴリズム +.RE +.PP +署名者の公開鍵と秘密鍵がDSA鍵である場合、\fBjarsigner\fRは\fBSHA1withDSA\fRアルゴリズムを使用してJARファイルに署名します。署名者の鍵がRSA鍵である場合、\fBjarsigner\fRは\fBSHA256withRSA\fRアルゴリズムを使用してJARファイルに署名しようとします。署名者の鍵がEC鍵である場合、\fBjarsigner\fRは\fBSHA256withECDSA\fRアルゴリズムを使用してJARファイルに署名します。 +.PP +これらのデフォルトの署名アルゴリズムは、\fB\-sigalg\fRオプションを使用してオーバーライドできます。 +.SS "署名付きJARファイル" +.PP +\fBjarsigner\fRコマンドを使用してJARファイルに署名する場合、出力される署名付きJARファイルは入力JARファイルと同じですが、次の2つの追加ファイルがMETA\-INFディレクトリに置かれる点が異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\&.SF\fR拡張子の付いた署名ファイル +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\&.DSA\fR、\fB\&.RSA\fRまたは\fB\&.EC\fR拡張子の付いた署名ブロック・ファイル +.RE +.PP +これら2つのファイルのベース・ファイル名は、\fB\-sigFile\fRオプションの値から作成されます。たとえば、オプションが\fB\-sigFile MKSIGN\fRの場合、ファイルは\fBMKSIGN\&.SF\fRおよび\fBMKSIGN\&.DSA\fRという名前になります。 +.PP +コマンドラインで\fB\-sigfile\fRオプションを指定しなかった場合、\fB\&.SF\fRファイルと\fB\&.DSA\fRファイルのベース・ファイル名は、コマンドラインで指定された別名の先頭の8文字をすべて大文字に変換したものになります。別名が8文字未満の場合は、別名がそのまま使用されます。別名に、署名ファイル名で使用できない文字が含まれている場合、ファイル名の作成時に、該当する文字が下線(_)文字に変換されます。有効な文字は、アルファベット、数字、下線およびハイフンです。 +.PP +署名ファイル +.PP +署名ファイル(\fB\&.SF\fRファイル)は、\fBjarsigner\fRコマンドを使用してファイルに署名する際にJARファイルに常に含まれるマニフェスト・ファイルと似ています。JARファイルに含まれているソース・ファイルごとに、\fB\&.SF\fRファイルには、マニフェスト・ファイルにあるような、次に示す3つの行があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ファイル名 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ダイジェスト・アルゴリズム(SHA)の名前 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHAダイジェストの値 +.RE +.PP +マニフェスト・ファイルでは、各ソース・ファイルのSHAダイジェストの値は、ソース・ファイルのバイナリ・データのダイジェスト(ハッシュ)になります。\fB\&.SF\fRファイルでは、指定されたソース・ファイルのダイジェストの値は、ソース・ファイルのマニフェスト・ファイル内のその3行のハッシュになります。 +.PP +署名ファイルには、デフォルトで、マニフェスト・ファイル全体のハッシュが格納されたヘッダーが含まれています。ヘッダーにはマニフェスト・ヘッダーのハッシュも含まれています。ヘッダーが存在すると、検証の最適化が有効になります。JARファイルの検証を参照してください。 +.PP +署名ブロック・ファイル +.PP +\fB\&.SF\fRファイルには署名が付けられ、署名は署名ブロック・ファイルに置かれます。このファイルには、署名に使用された秘密鍵に対応する公開鍵を認証するキーストアからの証明書または証明書チェーンも、内部でエンコードされて含まれています。ファイルの拡張子は、使用されるダイジェスト・アルゴリズムに応じて、\fB\&.DSA\fR、\fB\&.RSA\fRまたは\fB\&.EC\fRになります。 +.SS "署名タイムスタンプ" +.PP +\fBjarsigner\fRコマンドでは、JARファイルの署名時に署名タイムスタンプを生成および保存できます。さらに、\fBjarsigner\fRは代替署名機構をサポートします。この動作は省略可能で、署名時に次の各オプションによって制御されます。オプションを参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-tsa \fR\fB\fIurl\fR\fR +\fB\-tsacert \fR\fB\fIalias\fR\fR +\fB\-altsigner \fR\fB\fIclass\fR\fR +\fB\-altsignerpath \fR\fB\fIclasspathlist\fR\fR +\fB\-tsapolicyid \fR\fB\fIpolicyid\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SS "JARファイルの検証" +.PP +JARファイルの検証が成功するのは、署名が有効であり、かつ署名の生成以降にJARファイル内のどのファイルも変更されていない場合です。JARファイルの検証は、次の手順で行われます。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +\fB\&.SF\fRファイルの署名を検証します。 +.sp +検証では、各署名ブロック(\fB\&.DSA\fR)ファイルに格納された署名が、証明書(または証明書チェーン)も\fB\&.DSA\fRファイルに示される公開鍵に対応する秘密鍵を使用して生成されたことを確認します。また、署名が対応する署名(\fB\&.SF\fR)ファイルの有効な署名であることが確認され、それにより、\fB\&.SF\fRファイルが改ざんされていないことも確認されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +\fB\&.SF\fRファイル内の各エントリに示されるダイジェストを、マニフェスト内の対応する各セクションと突きあわせて検証します。 +.sp +\fB\&.SF\fRファイルには、マニフェスト・ファイル全体のハッシュが格納されたヘッダーがデフォルトで含まれています。ヘッダーが存在する場合、検証では、ヘッダー内のハッシュがマニフェスト・ファイルのハッシュと一致するかどうかを確認するためにチェックできます。一致する場合、検証は次の手順に進みます。 +.sp +一致しない場合、\fB\&.SF\fRファイル内の各ソース・ファイル情報セクションのハッシュが、マニフェスト・ファイル内の対応するセクションのハッシュと一致することを確認するために、あまり最適化されていない検証が必要になります。署名ファイルを参照してください。 +.sp +\fB\&.SF\fRファイルのヘッダーに格納されたマニフェスト・ファイルのハッシュが、現在のマニフェスト・ファイルのハッシュに一致しない理由の1つは、署名および\fB\&.SF\fRファイルの生成後に、(\fBjar\fRツールを使用して)1つ以上のファイルがJARファイルに追加されたことです。\fBjar\fRツールを使用してファイルを追加した場合、新しいファイル用のセクションが追加されることにより、マニフェスト・ファイルは変更されますが、\fB\&.SF\fRファイルは変更されません。検証がまだ成功しているとみなされるのは、署名の生成以降にJARファイル内のどのファイルも変更されていない場合です。これが発生するのは、\fB\&.SF\fRファイルのヘッダー以外のセクションのハッシュが、マニフェスト・ファイル内の対応するセクションのハッシュと一致する場合です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +\fB\&.SF\fRファイル内にエントリを持つJARファイル内の各ファイルを読み取ります。読取り中にファイルのダイジェストを計算し、結果をマニフェスト・セクション内のこのファイルのダイジェストと比較します。ダイジェストは同じである必要があり、そうでない場合は検証が失敗します。 +.sp +検証プロセス中になんらかの重大な検証エラーが発生した場合、そのプロセスは停止され、セキュリティ例外がスローされます。\fBjarsigner\fRコマンドでは、例外を捕捉および表示します。 +.RE +.PP +\fB注意:\fR +追加の警告(または、\fB\-strict\fRオプションを指定した場合はエラー)はすべて読む必要があります。同様に、証明が信頼できるかを決定するために、(\fB\-verbose\fRおよび\fB\-certs\fRオプションを指定して)証明書の内容も読む必要があります。 +.SS "1つのJARファイルを対象とする複数の署名" +.PP +次のように、\fBjarsigner\fRコマンドをファイルで複数回実行し、実行のたびに異なるユーザーの別名を指定することによって、1つのJARファイルに複数のユーザーの署名を付けることができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner myBundle\&.jar susan\fR +\fBjarsigner myBundle\&.jar kevin\fR + +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルが複数回署名されている場合、そのJARファイルには、複数の\fB\&.SF\fRファイルと\fB\&.DSA\fRファイルが含まれており、1回の署名に対して1つのペアとなります。前述の例では、出力JARファイルには、次の名前のファイルが含まれています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBSUSAN\&.SF\fR +\fBSUSAN\&.DSA\fR +\fBKEVIN\&.SF\fR +\fBKEVIN\&.DSA\fR +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +次の各項では、様々な\fBjarsigner\fRオプションについて説明します。次の標準に注意してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +どのオプション名にも先頭にマイナス記号(\-)が付きます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションは任意の順序で指定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +イタリックまたは下線付きの項目(オプションの値)の実際の値は、指定する必要があります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-storepass\fR、\fB\-keypass\fR、\fB\-sigfile\fR、\fB\-sigalg\fR、\fB\-digestalg\fR、\fB\-signedjar\fRおよびTSA関連のオプションを使用できるのは、JARファイルに署名する場合のみです。署名付きJARファイルを検証する場合ではありません。\fB\-keystore \fRオプションは、JARファイルの署名および検証に関連します。また、別名は、JARファイルの署名および検証時に指定します。 +.RE +.PP +\-keystore \fIurl\fR +.RS 4 +キーストアの場所を示すURLを指定します。これにより、\fBuser\&.home\fRシステム・プロパティで決定されたユーザーのホーム・ディレクトリ内のファイル\fB\&.keystore\fRにデフォルト設定されます。 +.sp +キーストアは署名時には必要です。デフォルトのキーストアが存在しない場合、またはデフォルト以外のキーストアを使用する場合は、キーストアを明示的に指定する必要があります。 +.sp +検証するときはキーストアは必要ありません。ただし、キーストアが指定されているか、あるいはデフォルトのキーストアが存在していて、さらに\fB\-verbose\fRオプションも指定されていた場合、JARファイルの検証に使用される証明書がそのキーストアに1つでも含まれているかどうかに関する追加情報が出力されます。 +.sp +\fB\-keystore\fR引数には、URLではなくファイル名とパスを指定でき、この場合、ファイル: URLと同じように処理されます。たとえば、次にように指定すると同等になります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-keystore \fR\fB\fIfilePathAndName\fR\fR +\fB\-keystore file:\fR\fB\fIfilePathAndName\fR\fR + +.fi +.if n \{\ +.RE +.\} +(JREの\fB$JAVA_HOME/lib/security directory\fRにある) +\fBjava\&.security\fRセキュリティ・プロパティ・ファイル内でSun PKCS #11プロバイダが構成された場合、\fBkeytool\fRおよび\fBjarsigner\fRツールはPKCS#11トークンに基づいて動作できます。次のオプションを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-keystore NONE\fR +\fB\-storetype PKCS11\fR + +.fi +.if n \{\ +.RE +.\} +たとえば、次のコマンドは、構成されたPKCS#11トークンの内容を一覧表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-keystore NONE \-storetype PKCS11 \-list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-storetype \fIstoretype\fR +.RS 4 +インスタンスを生成するキーストアのタイプを指定します。デフォルトのキーストア・タイプは、セキュリティ・プロパティ・ファイル内の\fBkeystore\&.type\fRプロパティの値で指定されたタイプです。この値は、\fBjava\&.security\&.KeyStore\fRのstatic +\fBgetDefaultType\fRメソッドによって返されます。 +.sp +\fB\-storepass\fRオプションを使用して、PCKS #11トークンのPINを指定することもできます。何も指定しない場合、\fBkeytool\fRおよび\fBjarsigner\fRコマンドによって、トークンPINの指定を求められます。トークンに保護された認証パス(専用のPINパッドや生体読取り機など)がある場合、\fB\-protected\fRオプションを指定する必要がありますが、パスワード・オプションは指定できません。 +.RE +.PP +\-storepass[:env | :file] \fIargument\fR +.RS 4 +キーストアにアクセスするのに必要なパスワードを指定します。これが必要なのは、JARファイルに署名を付けるときのみです(検証するときには不要です)。その場合、\fB\-storepass\fRオプションをコマンド行で指定しないと、パスワードの入力を求められます。 +.sp +修飾子\fBenv\fRまたは\fBfile\fRが指定されていない場合、パスワードの値は\fIargument\fRになります。それ以外の場合、パスワードは次のようにして取得されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBenv\fR: +\fBargument\fRという名前の環境変数からパスワードを取得します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBfile\fR: +\fBargument\fRという名前のファイルからパスワードを取得します。 +.RE +.sp +\fB注意:\fR +テストを目的とする場合またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。 +.RE +.PP +\-keypass [:env | :file] \fIargument\fR +.RS 4 +コマンド行で指定された別名に対応するキーストア・エントリの秘密鍵を保護するのに使用するパスワードを指定します。\fBjarsigner\fRを使用してJARファイルに署名を付けるときは、パスワードが必要です。コマンド行でパスワードが指定されておらず、必要なパスワードがストアのパスワードと異なる場合は、パスワードの入力を求められます。 +.sp +修飾子\fBenv\fRまたは\fBfile\fRが指定されていない場合、パスワードの値は\fBargument\fRになります。それ以外の場合、パスワードは次のようにして取得されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBenv\fR: +\fBargument\fRという名前の環境変数からパスワードを取得します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBfile\fR: +\fBargument\fRという名前のファイルからパスワードを取得します。 +.RE +.sp +\fB注意:\fR +テストを目的とする場合またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。 +.RE +.PP +\-sigfile \fIfile\fR +.RS 4 +生成された\fB\&.SF\fRファイルおよび\fB\&.DSA\fRファイルに使用するベース・ファイル名を指定します。たとえば、ファイルが\fBDUKESIGN\fRの場合、生成される\fB\&.SF\fRおよび\fB\&.DSA\fRファイルは、\fBDUKESIGN\&.SF\fRおよび\fBDUKESIGN\&.DSA\fRという名前で、署名付きJARファイルの\fBMETA\-INF\fRディレクトリに格納されます。 +.sp +ファイル内の文字は、セット\fBa\-zA\-Z0\-9_\-\fRから指定される必要があります。アルファベット、数字、下線およびハイフン文字のみを使用できます。\fB\&.SF\fRおよび\fB\&.DSA\fRのファイル名では、小文字はすべて大文字に変換されます。 +.sp +コマンド行で\fB\-sigfile\fRオプションを指定しなかった場合、\fB\&.SF\fRファイルと\fB\&.DSA\fRファイルのベース・ファイル名は、コマンド行で指定された別名の先頭の8文字をすべて大文字に変換したものになります。別名が8文字未満の場合は、別名がそのまま使用されます。別名に、署名ファイル名で無効な文字が含まれている場合、ファイル名を作成するために、該当する文字が下線(_)文字に変換されます。 +.RE +.PP +\-sigalg \fIalgorithm\fR +.RS 4 +JARファイルの署名に使用する署名アルゴリズムの名前を指定します。 +.sp +標準的な署名アルゴリズム名のリストは、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppAにある +Java Cryptography Architecture (JCA)リファレンス・ガイドの「付録A: 標準名」を参照してください。 +.sp +このアルゴリズムには、JARファイルの署名に使用する秘密鍵との互換性が必要です。このオプションを指定しない場合、秘密鍵のタイプに応じて、\fBSHA1withDSA\fR、\fBSHA256withRSA\fRまたは\fBSHA256withECDSA\fRが使用されます。指定されたアルゴリズムの実装を提供するプロバイダが静的にインストールされているか、\fB\-providerClass\fRオプションを使用してそのようなプロバイダをユーザーが指定する必要があります。そうでない場合、コマンドは失敗します。 +.RE +.PP +\-digestalg \fIalgorithm\fR +.RS 4 +JARファイルのエントリをダイジェストする際に使用するメッセージ・ダイジェスト・アルゴリズムの名前を指定します。 +.sp +標準的なメッセージ・ダイジェスト・アルゴリズム名のリストは、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppAにある +Java Cryptography Architecture (JCA)リファレンス・ガイドの「付録A: 標準名」を参照してください。 +.sp +このオプションを指定しない場合、\fBSHA256\fRが使用されます。指定されたアルゴリズムの実装を提供するプロバイダが静的にインストールされているか、\fB\-providerClass\fRオプションを使用してそのようなプロバイダをユーザーが指定する必要があります。そうでない場合、コマンドは失敗します。 +.RE +.PP +\-certs +.RS 4 +コマンド行で、\fB\-certs\fRオプションを\fB\-verify\fRおよび\fB\-verbose\fRオプションとともに指定した場合、JARファイルの各署名者の証明書情報が出力に含まれます。この情報には、署名者の公開鍵を証明する証明書(\fB\&.DSA\fRファイルに格納)のタイプの名前が含まれ、証明書がX\&.509証明書(\fBjava\&.security\&.cert\&.X509Certificate\fRのインスタンス)の場合、署名者の識別名が含まれます。 +.sp +キーストアの確認も行われます。コマンド行でキーストアの値が指定されていない場合、デフォルトのキーストア・ファイル(ある場合)がチェックされます。署名者の公開鍵の証明書がキーストア内のエントリと一致する場合、その署名者のキーストアのエントリの別名が丸カッコ内に表示されます。 +.RE +.PP +\-certchain \fIfile\fR +.RS 4 +コマンド行で指定した別名によって表されるキーストア・エントリの秘密鍵に関連付けられた証明書チェーンが完全ではない場合に、使用する証明書チェーンを指定します。これは、証明書チェーン全体を保持するのに十分な領域がないハードウェア・トークン上にキーストアが格納されている場合に発生します。このファイルは一連の連結されたX\&.509証明書、PKCS#7形式の単一データ・ブロックのいずれかとなり、そのエンコーディング形式はバイナリ・エンコーディング形式、Internet RFC 1421標準で規定される印刷可能エンコーディング形式(Base64エンコーディングとも呼ばれる)のいずれかになります。インターネットRFC 1421証明書符号化規格およびhttp://tools\&.ietf\&.org/html/rfc1421を参照してください。 +.RE +.PP +\-verbose +.RS 4 +コマンド行で\fB\-verbose\fRオプションを指定した場合、冗長モードで動作し、このモードでは、\fBjarsigner\fRは、JARの署名または検証の進行状況に関する追加情報を出力します。 +.RE +.PP +\-internalsf +.RS 4 +以前は、JARファイルの署名時に生成された\fB\&.DSA\fR +(署名ブロック)ファイルに、生成された\fB\&.SF\fRファイル(署名ファイル)のエンコードされた完全なコピーが含まれていました。 この動作は変更されました。出力JARファイル全体のサイズを小さくするために、デフォルトでは\fB\&.DSA\fRファイルには\fB\&.SF\fRファイルのコピーが含まれないようになっています。コマンド行で\fB\-internalsf\fRを指定した場合、以前と同じように動作します。このオプションは、テストを行う場合に便利です。実際には、\fB\-internalsf\fRオプションは、オーバーヘッドが大きくなるため、使用しないでください。 +.RE +.PP +\-sectionsonly +.RS 4 +コマンド行で\fB\-sectionsonly\fRオプションを指定した場合、JARファイルの署名時に生成される\fB\&.SF\fRファイル(署名ファイル)には、マニフェスト・ファイル全体のハッシュを含むヘッダーは含まれません。これに含まれるのは、JARファイル内の各ソース・ファイルに関連する情報およびハッシュのみです。署名ファイルを参照してください。 +.sp +デフォルトでは、最適化のために、このヘッダーが追加されます。ヘッダーが存在する場合、JARファイルを検証するたびに、検証では、まずヘッダー内のハッシュがマニフェスト・ファイル全体のハッシュと一致するかどうかを確認するためにチェックできます。一致する場合、検証は次の手順に進みます。一致しない場合、\fB\&.SF\fRファイル内の各ソース・ファイル情報セクションのハッシュが、マニフェスト・ファイル内の対応するセクションのハッシュと一致するという、あまり最適化されていない検証を実行する必要があります。JARファイルの検証を参照してください。 +.sp +\fB\-sectionsonly\fRオプションは、主にテスト用に使用されます。これを使用するとオーバーヘッドが大きくなるため、テスト用以外では使用しないでください。 +.RE +.PP +\-protected +.RS 4 +\fBtrue\fRまたは\fBfalse\fRのいずれかの値を指定できます。専用PINリーダーなどの保護された認証パスによってパスワードを指定する必要がある場合、\fBtrue\fRを指定します。 +.RE +.PP +\-providerClass \fIprovider\-class\-name\fR +.RS 4 +暗号化サービス・プロバイダが\fBjava\&.security\fRセキュリティ・プロパティ・ファイルに指定されていないときは、そのマスター・クラス・ファイルの名前を指定するときに使用されます。 +.sp +\fB\-providerArg ConfigFilePath\fRオプションとともに使用し、\fBkeytool\fRおよび\fBjarsigner\fRツールは、プロバイダを動的にインストールし、トークン構成ファイルへのパスに\fIConfigFilePath\fRを使用します。次の例は、Oracle PKCS #11プロバイダがセキュリティ・プロパティ・ファイルに構成されていなかった場合に\fBPKCS #11\fRキーストアを一覧表示するコマンドを示しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore NONE \-storetype PKCS11 \e\fR +\fB \-providerClass sun\&.security\&.pkcs11\&.SunPKCS11 \e\fR +\fB \-providerArg /mydir1/mydir2/token\&.config \e\fR +\fB \-list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-providerName \fIproviderName\fR +.RS 4 +\fBjava\&.security\fRセキュリティ・プロパティ・ファイル内で2つ以上のプロバイダが構成された場合、\fB\-providerName\fRオプションを使用して、特定のプロバイダ・インスタンスを対象にすることができます。このオプションの引数は、プロバイダの名前です。 +.sp +Oracle PKCS #11プロバイダの場合、\fIproviderName\fRは\fBSunPKCS11\-\fR\fITokenName\fRという形式になります。ここで、構成属性の表で詳細に説明されているように、\fITokenName\fRは、プロバイダ・インスタンスが構成された名前の接尾辞です。たとえば、次のコマンドは、名前接尾辞\fBSmartCard\fRの\fBPKCS #11\fRキーストア・プロバイダ・インスタンスの内容を一覧表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore NONE \-storetype PKCS11 \e\fR +\fB \-providerName SunPKCS11\-SmartCard \e\fR +\fB \-list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\fIjavaoption\fR +.RS 4 +指定された\fIjavaoption\fR文字列をJavaインタプリタに直接渡します。\fBjarsigner\fRコマンドは、インタプリタに対するラッパーです。このオプションには、空白を含めることはできません。このオプションは、実行環境またはメモリー使用を調整する場合に便利です。指定できるインタプリタ・オプションを一覧表示するには、コマンドラインで\fBjava \-h\fRまたは\fBjava \-X\fRと入力してください。 +.RE +.PP +\-tsa \fIurl\fR +.RS 4 +\fB\-tsa http://example\&.tsa\&.url\fRがJARファイルの署名時にコマンド行にある場合、署名のタイムスタンプが生成されます。URL +\fBhttp://example\&.tsa\&.url\fRは、Time Stamping Authority (TSA)の場所を特定し、\fB\-tsacert\fRオプションを指定して検出されたURLをオーバーライドします。\fB\-tsa\fRオプションでは、TSAの公開鍵証明書をキーストアに配置する必要はありません。 +.sp +タイムスタンプを生成するために、\fBjarsigner\fRは、RFC 3161で定義されているタイムスタンプ・プロトコル(TSP)を使用してTSAと通信します。成功すると、TSAによって返されたタイムスタンプ・トークンは、署名ブロック・ファイルの署名とともに保存されます。 +.RE +.PP +\-tsacert \fIalias\fR +.RS 4 +\fB\-tsacert alias\fRがJARファイルの署名時にコマンド行にある場合、署名のタイムスタンプが生成されます。別名は、キーストア内の有効なTSAの公開鍵証明書を特定します。エントリの証明書で、TSAの場所を特定するURLを含むSubject Information Access拡張機能が確認されます。 +.sp +\fB\-tsacert\fRオプションを使用する場合は、TSAの公開鍵証明書がキーストアに配置されている必要があります。 +.RE +.PP +\-tsapolicyid \fIpolicyid\fR +.RS 4 +TSAサーバーに送信するポリシーIDを識別するオブジェクト識別子(OID)を指定します。このオプションを指定しない場合、ポリシーIDは送信されず、TSAサーバーはデフォルトのポリシーIDを選択します。 +.sp +オブジェクト識別子は、ITU Telecommunication Standardization Sector (ITU\-T)標準であるX\&.696によって定義されます。これらの識別子は、通常、\fB1\&.2\&.3\&.4\fRなどの、負ではない数字のピリオド区切りのセットです。 +.RE +.PP +\-altsigner \fIclass\fR +.RS 4 +このオプションは、代替署名メカニズムを指定します。完全修飾クラス名は、\fBcom\&.sun\&.jarsigner\&.ContentSigner\fR抽象クラスを拡張するクラス・ファイルを識別します。このクラス・ファイルへのパスは、\fB\-altsignerpath\fRオプションによって定義されます。\fB\-altsigner\fRオプションを使用した場合、\fBjarsigner\fRコマンドでは、指定されたクラスによって提供される署名メカニズムを使用します。それ以外の場合、\fBjarsigner\fRコマンドはデフォルトの署名メカニズムを使用します。 +.sp +たとえば、\fBcom\&.sun\&.sun\&.jarsigner\&.AuthSigner\fRという名前のクラスが提供する署名メカニズムを使用するには、jarsignerのオプション\fB\-altsigner com\&.sun\&.jarsigner\&.AuthSigner\fRを使用します。 +.RE +.PP +\-altsignerpath \fIclasspathlist\fR +.RS 4 +クラス・ファイルおよびそれが依存するJARファイルへのパスを指定します。\fB\-altsigner\fRオプションを使用して、クラス・ファイル名を指定します。クラス・ファイルがJARファイル内にある場合、このオプションでは、そのJARファイルへのパスを指定します。 +.sp +絶対パスまたは現在のディレクトリへの相対パスを指定できます。\fIclasspathlist\fRに複数のパスやJARファイルが含まれる場合、それらを、Oracle Solarisの場合はコロン(:)で、Windowsの場合はセミコロン(;)で、それぞれ区切ります。目的のクラスがすでに検索パス内にある場合は、このオプションは不要です。 +.sp +次の例では、クラス・ファイルを含むJARファイルへのパスを指定する方法を示します。JARファイル名を含めます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-altsignerpath /home/user/lib/authsigner\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、クラス・ファイルを含むJARファイルへのパスを指定する方法を示します。JARファイル名を省略します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-altsignerpath /home/user/classes/com/sun/tools/jarsigner/\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-strict +.RS 4 +署名または検証処理中に、コマンドにより警告メッセージが発行される場合があります。このオプションを指定すると、コマンドにより検出された重大な警告メッセージがツールの終了コードに反映されます。エラーと警告を参照してください。 +.RE +.PP +\-verbose \fIsuboptions\fR +.RS 4 +検証処理の場合、\fB\-verbose\fRオプションには、表示する情報の量を決定するサブオプションを指定します。\fB\-certs\fRオプションも指定した場合、デフォルト・モード(またはサブオプション\fBall\fR)では、エントリが処理されるたびに各エントリが表示され、その後にJARファイルの各署名者の証明書情報も表示されます。\fB\-certs\fRおよび\fB\-verbose:grouped\fRサブオプションを指定した場合、同じ署名者情報を持つエントリが、その証明書情報とともに、グループ化されて表示されます。\fB\-certs\fRおよび\fB\-verbose:summary\fRサブオプションを指定した場合、同じ署名者情報を持つエントリが、その証明書情報とともに、グループ化されて表示されます。各エントリの詳細は、\fI1つのエントリ(以上)\fRにまとめられて表示されます。例を参照してください。 +.RE +.SH "エラーと警告" +.PP +署名または検証プロセス中に、\fBjarsigner\fRコマンドで、様々なエラーまたは警告が発行される可能性があります。 +.PP +障害がある場合、\fBjarsigner\fRコマンドはコード1で終了します。障害はないが、1つ以上の重大な警告がある場合、\fB\-strict\fRオプションが指定されて\fBいない\fR場合は、\fBjarsigner\fRコマンドはコード0で終了し、\fB\-strict\fRが指定されている場合は警告コードのOR値で終了します。情報警告のみがある、または警告がまったくない場合、コマンドは常にコード0で終了します。 +.PP +たとえば、エントリの署名に使用される証明書が期限切れで、ファイルの署名を許可しないKeyUsage拡張機能を使用している場合、\fB\-strict\fRオプションが指定されていると、\fBjarsigner\fRコマンドはコード12 (=4+8)で終了します。 +.PP +\fB注意:\fR +Solaris、LinuxおよびOS Xでは0から255までの値のみが有効のため、終了コードは再利用されます。 +.PP +次のセクションでは、\fBjarsigner\fRコマンドにより発行できるエラーおよび警告の名前、コード、説明を記述します。 +.SS "障害" +.PP +コマンド行解析エラー、JARファイルに署名する鍵ペアを検索できない、または署名付きJARファイルの検証失敗など(限定されません)、\fBjarsigner\fRコマンドの失敗理由。 +.PP +failure +.RS 4 +コード1。署名または検証が失敗します。 +.RE +.SS "重大な警告" +.PP +\fB注意:\fR +\fB\-strict\fRオプションを指定した場合、重大な警告はエラーとして報告されます。 +.PP +JARファイルの署名に使用する証明書にエラーがある、または署名付きJARファイルに他の問題があるなど、\fBjarsigner\fRコマンドが重大な警告を発行する理由。 +.PP +hasExpiredCert +.RS 4 +コード4。このjarには、署名者証明書が期限切れのエントリが含まれています。 +.RE +.PP +notYetValidCert +.RS 4 +コード4。このjarには、署名者証明書がまだ有効になっていないエントリが含まれています。 +.RE +.PP +chainNotValidated +.RS 4 +コード4。このjarには、証明書チェーンが検証されていないエントリが含まれています。 +.RE +.PP +badKeyUsage +.RS 4 +コード8。このJARには、署名者証明書のKeyUsage拡張機能がコード署名を許可しないエントリが含まれています。 +.RE +.PP +badExtendedKeyUsage +.RS 4 +コード8。このjarには、署名者証明書のExtendedKeyUsage拡張機能がコード署名を許可しないエントリが含まれています。 +.RE +.PP +badNetscapeCertType +.RS 4 +コード8。このjarには、署名者証明書のNetscapeCertType拡張機能がコード署名を許可しないエントリが含まれています。 +.RE +.PP +hasUnsignedEntry +.RS 4 +コード16。このjarには、整合性チェックをしていない未署名のエントリが含まれています。 +.RE +.PP +notSignedByAlias +.RS 4 +コード32。このjarには、指定された別名によって署名されていない署名済エントリが含まれています。 +.RE +.PP +aliasNotInStore +.RS 4 +コード32。このjarには、このキーストア内の別名によって署名されていない署名済エントリが含まれます。 +.RE +.SS "情報警告" +.PP +情報警告には、エラーではないが不適切とみなされるものが含まれます。コードはありません。 +.PP +hasExpiringCert +.RS 4 +このjarには、署名者証明書が6か月以内に期限切れとなるエントリが含まれています。 +.RE +.PP +noTimestamp +.RS 4 +このjarには、タイムスタンプを含まない署名が含まれています。タイムスタンプなしでは、署名者証明書の有効期限(\fBYYYY\-MM\-DD\fR)後または将来の取消日後、ユーザーはこのJARファイルを検証できない場合があります。 +.RE +.SH "例" +.SS "JARファイルの署名" +.PP +次のコマンドを使用して、キーストア別名が\fBworking\fRディレクトリの\fBmystore\fRという名前のキーストアにある\fBjane\fRであるユーザーの秘密鍵でbundle\&.jarに署名し、署名付きJARファイルに\fBsbundle\&.jar\fRという名前を付けます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore\fR +\fB \-storepass \fR +\fB \-keypass \fR +\fB \-signedjar sbundle\&.jar bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.PP +前述のコマンドでは\fB\-sigfile\fRが指定されていないため、署名付きJARファイルに格納される生成された\fB\&.SF\fRファイルおよび\fB\&.DSA\fRファイルの名前は、別名に基づいたデフォルトの名前になります。これらは、名前付きの\fBJANE\&.SF\fRおよび\fBJANE\&.DSA\fRです。 +.PP +ストアのパスワードおよび秘密鍵のパスワードを求められる場合、前述のコマンドを短縮して、次のことを実行できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore\fR +\fB \-signedjar sbundle\&.jar bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.PP +キーストアがデフォルトのキーストア(ホーム・ディレクトリ内の\&.keystore)である場合、次に示すように、キーストアを指定する必要がありません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-signedjar sbundle\&.jar bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.PP +入力JARファイル(bundle\&.jar)を署名付きJARファイルで上書きする場合、次のように\fB\-signedjar\fRオプションを指定する必要はありません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.SS "署名付きJARファイルの検証" +.PP +署名付きJARファイルを検証して、署名が有効でJARファイルが改ざんされなかったことを確認するには、次のようなコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-verify sbundle\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.PP +検証が成功すると、\fBjar verified\fRが表示されます。有効でない場合は、エラー・メッセージが表示されます。\fB\-verbose\fRオプションを使用すると、詳細情報を取得できます。\fBjarsigner\fRを\fB\-verbose\fRオプションとともに使用するサンプルを、次に示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-verify \-verbose sbundle\&.jar\fR +\fB \fR +\fB 198 Fri Sep 26 16:14:06 PDT 1997 META\-INF/MANIFEST\&.MF\fR +\fB 199 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.SF\fR +\fB 1013 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.DSA\fR +\fB smk 2752 Fri Sep 26 16:12:30 PDT 1997 AclEx\&.class\fR +\fB smk 849 Fri Sep 26 16:12:46 PDT 1997 test\&.class\fR +\fB \fR +\fB s = signature was verified\fR +\fB m = entry is listed in manifest\fR +\fB k = at least one certificate was found in keystore\fR +\fB \fR +\fB jar verified\&.\fR + +.fi +.if n \{\ +.RE +.\} +.SS "証明書情報を使用した検証" +.PP +\fB\-certs\fRオプションを\fB\-verify\fRおよび\fB\-verbose\fRオプションとともに指定した場合、JARファイルの各署名者の証明書情報が出力に含まれます。この情報には、証明書タイプ、署名者の識別名情報(X\&.509証明書の場合)が含まれ、丸カッコ内には、JARファイルの公開鍵証明書がキーストア・エントリの公開鍵証明書に一致する場合の署名者のキーストア別名が含まれます。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore \-verify \-verbose \-certs myTest\&.jar\fR +\fB \fR +\fB 198 Fri Sep 26 16:14:06 PDT 1997 META\-INF/MANIFEST\&.MF\fR +\fB 199 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.SF\fR +\fB 1013 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.DSA\fR +\fB 208 Fri Sep 26 16:23:30 PDT 1997 META\-INF/JAVATEST\&.SF\fR +\fB 1087 Fri Sep 26 16:23:30 PDT 1997 META\-INF/JAVATEST\&.DSA\fR +\fB smk 2752 Fri Sep 26 16:12:30 PDT 1997 Tst\&.class\fR +\fB \fR +\fB X\&.509, CN=Test Group, OU=Java Software, O=Oracle, L=CUP, S=CA, C=US (javatest)\fR +\fB X\&.509, CN=Jane Smith, OU=Java Software, O=Oracle, L=cup, S=ca, C=us (jane)\fR +\fB \fR +\fB s = signature was verified\fR +\fB m = entry is listed in manifest\fR +\fB k = at least one certificate was found in keystore\fR +\fB \fR +\fB jar verified\&.\fR + +.fi +.if n \{\ +.RE +.\} +.PP +署名者の証明書がX\&.509証明書ではない場合、識別名情報は表示されません。その場合には、証明書のタイプと別名のみが表示されます。たとえば、証明書がPGP証明書で、別名が\fBbob\fRである場合、\fBPGP, (bob)\fRを取得します。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +keytool(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/security/index\&.htmlにある +「コース: Java SEのセキュリティ機能」 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/java.1 b/jdk-1.8.0.281/man/ja/man1/java.1 new file mode 100755 index 0000000..682a21f --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/java.1 @@ -0,0 +1,3117 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: java +.\" Language: Japanese +.\" Date: 2015年3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "java" "1" "2015年3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +java \- Javaアプリケーションを起動します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\fR [\fIoptions\fR] \fIclassname\fR [\fIargs\fR] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\fR [\fIoptions\fR] \fB\-jar\fR \fIfilename\fR [\fIargs\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +空白で区切られたコマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclassname\fR +.RS 4 +起動するクラスの名前。 +.RE +.PP +\fIfilename\fR +.RS 4 +呼び出されるJavaアーカイブ(JAR)ファイルの名前。\fB\-jar\fRオプションと一緒にのみ使用します。 +.RE +.PP +\fIargs\fR +.RS 4 +空白で区切られた\fBmain()\fRメソッドに渡される引数。 +.RE +.SH "説明" +.PP +\fBjava\fRコマンドはJavaアプリケーションを開始します。Java Runtime Environment (JRE)を起動した後、指定したクラスをロードし、そのクラスの\fBmain()\fRメソッドを呼び出すことにより、これを行います。このメソッドは、\fIpublic\fRおよび\fIstatic\fRとして宣言する必要があります。また、値は返せません。さらに、\fBString\fR配列をパラメータとして指定できる必要があります。メソッド宣言は次の形式を含みます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static void main(String[] args)\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjava\fRコマンドを使用して、\fBmain()\fRメソッドがあるか\fBjavafx\&.application\&.Application\fRを拡張するクラスをロードすることで、JavaFXアプリケーションを起動できます。後者の場合、起動ツールは\fBApplication\fRクラスのインスタンスを構成し、その\fBinit()\fRメソッドをコールし、\fBstart(javafx\&.stage\&.Stage)\fRメソッドをコールします。 +.PP +デフォルトでは、\fBjava\fRコマンドのオプションではない最初の引数は、呼び出されるクラスの完全修飾名です。\fB\-jar\fRオプションを指定した場合、その引数は、アプリケーションのクラス・ファイルとリソース・ファイルを含むJARファイルの名前になります。起動クラスは、ソース・コードの\fBMain\-Class\fRマニフェスト・ヘッダーによって指定される必要があります。 +.PP +JREは、ブートストラップ・クラス・パス、インストール済拡張機能およびユーザーのクラス・パスの3箇所から、起動クラス(およびアプリケーションで使用されている他のクラス)を検索します。 +.PP +クラス・ファイル名またはJARファイル名の後の引数は、\fBmain()\fRメソッドに渡されます。 +.SH "オプション" +.PP +\fBjava\fRコマンドは、次のカテゴリに分類できる広範なオプションをサポートしています。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +標準オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非標準オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なランタイム・オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なJITコンパイラ・オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なサービスアビリティ・オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なガベージ・コレクション・オプション +.RE +.PP +標準のオプションは、Java Virtual Machine (JVM)のすべての実装でサポートすることが保証されます。これらは、JREのバージョンの確認、クラス・パスの設定、冗長な出力の有効化などの一般的なアクションに使用されます。 +.PP +標準以外のオプションは、Java HotSpot仮想マシンに固有の汎用オプションであるため、すべてのJVM実装でサポートされることは保証されず、変更される可能性があります。これらのオプションは\fB\-X\fRで開始します。 +.PP +拡張オプションは、不用意に使用しないことをお薦めします。これらは、特定のシステム要件を持つことが多く、システム構成パラメータへの特権アクセスが必要な場合があるJava HotSpot仮想マシン操作の特定の領域を調整するために使用される開発者オプションです。これらは、すべてのJVM実装でサポートされることは保証されず、変更される可能性があります。拡張オプションは\fB\-XX\fRで始まります。 +.PP +最新リリースで非推奨または削除されるオプションを追跡するために、ドキュメントの最後に非推奨で削除されたオプションという名前のセクションがあります。 +.PP +ブール・オプションは、デフォルトで無効になっている機能を有効にしたり、デフォルトで有効になっている機能を無効にするために使用されます。このようなオプションは、パラメータを必要としません。ブール値\fB\-XX\fRオプションは、プラス記号(\fB\-XX:+\fR\fIOptionName\fR)を使用して有効にし、マイナス記号(\fB\-XX:\-\fR\fIOptionName\fR)を使用して無効にします。 +.PP +引数が必要なオプションの場合、引数は、オプション名を空白、コロン(:)または等号(=)で区切ったものになるか、あるいは引数がオプションの後に直接続く場合もあります(正確な構文は各オプションによって異なります)。サイズをバイト単位で指定するよう求められている場合、接尾辞を使用しないか、あるいはキロバイト(KB)には接尾辞\fBk\fRまたは\fBK\fR、メガバイト(MB)には接尾辞\fBm\fRまたは\fBM\fR、ギガバイト(GB)には接尾辞\fBg\fRまたは\fBG\fRを使用します。たとえば、サイズを8GBに設定するには、\fB8g\fR、\fB8192m\fR、\fB8388608k\fRまたは\fB8589934592\fRのいずれかを引数として指定できます。パーセントの指定が必要な場合は、0から1の数値を使用します(たとえば、25%の場合は\fB0\&.25\fRを指定します)。 +.SS "標準オプション" +.PP +これらは、JVMのすべての実装でサポートされる最も一般的に使用されるオプションです。 +.PP +\-agentlib:\fIlibname\fR[=\fIoptions\fR] +.RS 4 +指定したネイティブ・エージェント・ライブラリをロードします。ライブラリ名の後に、ライブラリに固有のオプションのカンマ区切りリストを使用できます。 +.sp +オプション\fB\-agentlib:foo\fRを指定した場合、JVMは、\fBLD_LIBRARY_PATH\fRシステム変数(OS Xでは、この変数は\fBDYLD_LIBRARY_PATH\fRになります)で指定された場所に\fBlibfoo\&.so\fRという名前のライブラリをロードしようとします。 +.sp +次の例では、スタックの深さ3で、20ミリ秒ごとにヒープ・プロファイリング・ツール(HPROF)ライブラリをロードして、サンプルのCPU情報を取得する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-agentlib:hprof=cpu=samples,interval=20,depth=3\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、メイン・クラスのロード前にJVMを一時停止して、Javaデバッグ・ワイヤ・プロトコル(JDWP)ライブラリをロードして、ポート8000でのソケット接続用にリスニングする方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-agentlib:jdwp=transport=dt_socket,server=y,address=8000\fR + +.fi +.if n \{\ +.RE +.\} +ネイティブ・エージェント・ライブラリの詳細は、次を参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/api/java/lang/instrument/package\-summary\&.htmlにある\fBjava\&.lang\&.instrument\fRパッケージの説明 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/platform/jvmti/jvmti\&.html#startingにあるJVMツール・インタフェース・ガイドのエージェントのコマンド行オプションに関する項 +.RE +.RE +.PP +\-agentpath:\fIpathname\fR[=\fIoptions\fR] +.RS 4 +絶対パス名で指定されたネイティブ・エージェント・ライブラリをロードします。このオプションは\fB\-agentlib\fRと同等ですが、ライブラリのフル・パスおよびファイル名を使用します。 +.RE +.PP +\-client +.RS 4 +Java HotSpot Client VMを選択します。64ビット・バージョンのJava SE Development Kit (JDK)では、現在、このオプションは無視され、かわりにServer JVMが使用されます。 +.sp +デフォルトのJVM選択は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/server\-class\&.htmlにある +サーバークラス・マシンの検出を参照してください。 +.RE +.PP +\-D\fIproperty\fR=\fIvalue\fR +.RS 4 +システム・プロパティの値を設定します。\fIproperty\fR変数は、プロパティの名前を表す、空白のない文字列です。\fIvalue\fR変数は、プロパティの値を表す文字列です。\fIvalue\fRが空白を含む文字列の場合、それを引用符で囲みます(例: +\fB\-Dfoo="foo bar"\fR)。 +.RE +.PP +\-d32 +.RS 4 +アプリケーションを32ビット環境で実行します。32ビット環境がインストールされていないかサポートされていない場合は、エラーが報告されます。デフォルトでは、64ビット・システムが使用されている場合を除き、アプリケーションは32ビット環境で実行されます。 +.RE +.PP +\-d64 +.RS 4 +アプリケーションを64ビット環境で実行します。64ビット環境がインストールされていないかサポートされていない場合は、エラーが報告されます。デフォルトでは、64ビット・システムが使用されている場合を除き、アプリケーションは32ビット環境で実行されます。 +.sp +現在のところ、Java HotSpot Server VMのみが64ビットの操作をサポートしているため、\fB\-d64\fR使用時には\fB\-server\fRオプションが暗黙的に使用されます。\fB\-d64\fR使用時には、\fB\-client\fRオプションは無視されます。この仕様は、将来のリリースでは変更になる可能性があります。 +.RE +.PP +\-disableassertions[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.br +\-da[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.RS 4 +アサーションを無効にします。デフォルトでは、アサーションはすべてのパッケージおよびクラスで無効になっています。 +.sp +引数なしの\fB\-disableassertions\fR +(\fB\-da\fR)を指定すると、すべてのパッケージおよびクラスでアサーションが無効になります。\fB\&.\&.\&.\fRで終わる\fIpackagename\fR引数を指定すると、指定したパッケージとそのサブパッケージ内でアサーションが無効になります。引数として\fB\&.\&.\&.\fRのみを指定すると、現在の作業ディレクトリにある名前のないパッケージ内でアサーションが無効になります。\fIclassname\fR引数を指定すると、切替えによって、指定したクラス内でアサーションが無効になります。 +.sp +\fB\-disableassertions\fR +(\fB\-da\fR)オプションは、すべてのクラス・ローダーおよびシステム・クラスに適用されます(システム・クラスにはクラス・ローダーはありません)。このルールには1つ例外があります。オプションの引数が指定されていない場合は、システム・クラスに適用されません。これにより、システム・クラスを除くすべてのクラスでアサーションを簡単に無効にすることができます。\fB\-disablesystemassertions\fRオプションを使用すると、すべてのシステム・クラスでアサーションを無効にすることができます。 +.sp +特定のパッケージやクラスでアサーションを明示的に有効にするには、\fB\-enableassertions\fR +(\fB\-ea\fR)オプションを使用します。両方のオプションを同時に使用できます。たとえば、パッケージ\fBcom\&.wombat\&.fruitbat\fR +(およびそのサブパッケージ)ではアサーションを有効にして、クラス\fBcom\&.wombat\&.fruitbat\&.Brickbat\fRではアサーションを無効にして、\fBMyClass\fRアプリケーションを実行するには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-ea:com\&.wombat\&.fruitbat\&.\&.\&. \-da:com\&.wombat\&.fruitbat\&.Brickbat MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-disablesystemassertions +.br +\-dsa +.RS 4 +すべてのシステム・クラス内でアサーションを無効にします。 +.RE +.PP +\-enableassertions[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.br +\-ea[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.RS 4 +アサーションを有効にします。デフォルトでは、アサーションはすべてのパッケージおよびクラスで無効になっています。 +.sp +引数なしの\fB\-enableassertions\fR +(\fB\-ea\fR)を指定すると、すべてのパッケージおよびクラスでアサーションが有効になります。\fB\&.\&.\&.\fRで終わる\fIpackagename\fR引数を指定すると、指定したパッケージとそのサブパッケージ内でアサーションが有効になります。引数として\fB\&.\&.\&.\fRのみを指定すると、現在の作業ディレクトリにある名前のないパッケージ内でアサーションが有効になります。\fIclassname\fR引数を指定すると、切替えによって、指定したクラス内でアサーションが有効になります。 +.sp +\fB\-enableassertions\fR +(\fB\-ea\fR)オプションは、すべてのクラス・ローダーおよびシステム・クラスに適用されます(システム・クラスにはクラス・ローダーはありません)。このルールには1つ例外があります。オプションの引数が指定されていない場合は、システム・クラスに適用されません。これにより、システム・クラスを除くすべてのクラスでアサーションを簡単に有効にすることができます。\fB\-enablesystemassertions\fRオプションは、すべてのシステム・クラスでアサーションを有効にする別のスイッチを提供します。 +.sp +特定のパッケージやクラスでアサーションを明示的に無効にするには、\fB\-disableassertions\fR +(\fB\-da\fR)オプションを使用します。単一コマンドにこれらのスイッチのインスタンスを複数指定した場合は、指定したスイッチが順番に処理されてからクラスがロードされます。たとえば、パッケージ\fBcom\&.wombat\&.fruitbat\fR +(およびそのサブパッケージ)でのみアサーションを有効にして、クラス\fBcom\&.wombat\&.fruitbat\&.Brickbat\fRではアサーションを無効にして、\fBMyClass\fRアプリケーションを実行するには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-ea:com\&.wombat\&.fruitbat\&.\&.\&. \-da:com\&.wombat\&.fruitbat\&.Brickbat MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-enablesystemassertions +.br +\-esa +.RS 4 +すべてのシステム・クラス内でアサーションを有効にします。 +.RE +.PP +\-help +.br +\-? +.RS 4 +実際にJVMを実行せずに、\fBjava\fRコマンドの使用状況情報を表示します。 +.RE +.PP +\-jar \fIfilename\fR +.RS 4 +JARファイルにカプセル化されたプログラムを実行します。\fIfilename\fR引数は、使用するアプリケーションの開始点として機能する\fBpublic static void main(String[] args)\fRメソッドを定義する、\fBMain\-Class:\fR\fIclassname\fRという形式の1行を含むマニフェストを持つJARファイルの名前です。 +.sp +\fB\-jar\fRオプションを使用すると、指定したJARファイルがすべてのユーザー・クラスのソースになり、クラス・パスの他の設定は無視されます。 +.sp +JARファイルの詳細は、次のリソースを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jar/index\&.htmlにあるJavaアーカイブ(JAR)ファイルのガイド +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.htmlにある +「レッスン: JARファイルのプログラムのパッケージ化」 +.RE +.RE +.PP +\-javaagent:\fIjarpath\fR[=\fIoptions\fR] +.RS 4 +指定したJavaプログラミング言語エージェントをロードします。Javaアプリケーションのインストゥルメントの詳細は、http://docs\&.oracle\&.com/javase/8/docs/api/java/lang/instrument/package\-summary\&.htmlにあるJava APIドキュメントの\fBjava\&.lang\&.instrument\fRパッケージの説明を参照してください。 +.RE +.PP +\-jre\-restrict\-search +.RS 4 +ユーザー・プライベートなJREをバージョン検索に含めます。 +.RE +.PP +\-no\-jre\-restrict\-search +.RS 4 +ユーザー・プライベートなJREをバージョン検索から除外します。 +.RE +.PP +\-server +.RS 4 +Java HotSpot Server VMを選択します。64ビット・バージョンのJDKでは、Server VMのみをサポートしているため、その場合、このオプションは暗黙的です。 +.sp +デフォルトのJVM選択は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/server\-class\&.htmlにある +サーバークラス・マシンの検出を参照してください。 +.RE +.PP +\-showversion +.RS 4 +バージョン情報を表示し、アプリケーションの実行を続行します。このオプションは\fB\-version\fRオプションと同等ですが、\-versionはバージョン情報の表示後にJVMに終了を指示する点が異なります。 +.RE +.PP +\-splash:\fIimgname\fR +.RS 4 +\fIimgname\fRで指定されたイメージを含むスプラッシュ画面を表示します。たとえば、アプリケーションの起動時に\fBimages\fRディレクトリの\fBsplash\&.gif\fRファイルを表示するには、次のオプションを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-splash:images/splash\&.gif\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-verbose:class +.RS 4 +ロードされた各クラスに関する情報を表示します。 +.RE +.PP +\-verbose:gc +.RS 4 +各ガベージ・コレクション(GC)イベントに関する情報を表示します。 +.RE +.PP +\-verbose:jni +.RS 4 +ネイティブ・メソッドの使用およびその他のJava Native Interface (JNI)アクティビティに関する情報を表示します。 +.RE +.PP +\-version +.RS 4 +バージョン情報を表示してから終了します。このオプションは\fB\-showversion\fRオプションと同等ですが、\-showversionはバージョン情報の表示後にJVMに終了を指示しない点が異なります。 +.RE +.PP +\-version:\fIrelease\fR +.RS 4 +アプリケーションの実行に使用するリリース・バージョンを指定します。コールされた\fBjava\fRコマンドのバージョンがこの指定内容を満たさず、かつ適切な実装がシステム上で見つかった場合には、その適切な実装が使用されます。 +.sp +\fIrelease\fR引数は、正確なバージョン文字列、または空白で区切られたバージョン文字列とバージョン範囲のリストを指定します。\fIバージョン文字列\fRは、次の形式で、開発者のバージョン番号を指定します: +\fB1\&.\fR\fIx\fR\fB\&.0_\fR\fIu\fR +(\fIx\fRはメジャー・バージョン番号、\fIu\fRは更新バージョン番号です)。\fIバージョン範囲\fRは、このバージョン以降を指定するにはバージョン文字列の後にプラス記号(\fB+\fR)を続けたもの、または一致する接頭辞を含む任意のバージョン文字列を指定するには一部のバージョン文字列の後にアスタリスク(\fB*\fR)を続けたもので構成されます。論理\fIOR\fRの組合せには空白、2つのバージョンの文字列/範囲の論理\fIAND\fRの組合せにはアンパサンド(\fB&\fR)を使用して、バージョン文字列とバージョン範囲を組み合せることができます。たとえば、クラスまたはJARファイルの実行にJRE 6u13 (1\&.6\&.0_13)または6u10 (1\&.6\&.0_10)以降の任意のJRE 6のいずれかを必要とする場合、次を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-version:"1\&.6\&.0_13 1\&.6* & 1\&.6\&.0_10+"\fR + +.fi +.if n \{\ +.RE +.\} +引用符が必要なのは、\fIrelease\fRパラメータに空白がある場合のみです。 +.sp +JARファイルの場合は、バージョン要件をコマンド行に指定するよりも、JARファイルのマニフェスト内に指定することが推奨されています。 +.RE +.SS "非標準オプション" +.PP +これらのオプションは、Java HotSpot仮想マシンに固有の汎用オプションです。 +.PP +\-X +.RS 4 +使用可能なすべての\fB\-X\fRオプションのヘルプを表示します。 +.RE +.PP +\-Xbatch +.RS 4 +バックグラウンド・コンパイルを無効にします。デフォルトでは、JVMでは、バックグラウンド・コンパイルが終了するまで、メソッドをバックグラウンド・タスクとしてコンパイルし、インタプリタ・モードでメソッドを実行します。\fB\-Xbatch\fRフラグを指定すると、バックグラウンド・コンパイルが無効になり、すべてのメソッドのコンパイルが完了するまでフォアグラウンド・タスクとして処理されます。 +.sp +このオプションは\fB\-XX:\-BackgroundCompilation\fRと同等です。 +.RE +.PP +\-Xbootclasspath:\fIpath\fR +.RS 4 +ブート・クラス・ファイルを検索するディレクトリ、JARファイルおよびZIPアーカイブの、コロン(:)で区切られたリストを指定します。これらは、JDKに含まれるブート・クラス・ファイルのかわりに使用されます。 +.sp +JREバイナリ・コード・ライセンスに違反するため、\fBrt\&.jar\fRでクラスをオーバーライドする目的で、このオプションを使用するアプリケーションをデプロイしないでください。 +.RE +.PP +\-Xbootclasspath/a:\fIpath\fR +.RS 4 +デフォルトのブートストラップ・クラス・パスの最後に追加するディレクトリ、JARファイルおよびZIPアーカイブの、コロン(:)で区切られたリストを指定します。 +.sp +JREバイナリ・コード・ライセンスに違反するため、\fBrt\&.jar\fRでクラスをオーバーライドする目的で、このオプションを使用するアプリケーションをデプロイしないでください。 +.RE +.PP +\-Xbootclasspath/p:\fIpath\fR +.RS 4 +デフォルトのブートストラップ・クラス・パスの先頭に追加するディレクトリ、JARファイルおよびZIPアーカイブの、コロン(:)で区切られたリストを指定します。 +.sp +JREバイナリ・コード・ライセンスに違反するため、\fBrt\&.jar\fRでクラスをオーバーライドする目的で、このオプションを使用するアプリケーションをデプロイしないでください。 +.RE +.PP +\-Xcheck:jni +.RS 4 +Java Native Interface (JNI)機能に対して追加チェックを行います。具体的には、これは、JNIリクエストを処理する前に、JNI関数に渡されるパラメータと実行環境のデータを検証します。無効なデータが見つかった場合は、ネイティブ・コードに問題があることを示しているため、JVMはリカバリ不能なエラーを発生して終了します。このオプションを使用すると、パフォーマンス低下が予想されます。 +.RE +.PP +\-Xcomp +.RS 4 +最初の呼出しでメソッドのコンパイルを強制的に実行します。デフォルトでは、クライアントVM(\fB\-client\fR)は1,000の解釈されたメソッド呼出しを実行し、サーバーVM(\fB\-server\fR)は10,000の解釈されたメソッド呼出しを実行して、効率的なコンパイルのための情報を収集します。\fB\-Xcomp\fRオプションを指定すると、解釈されたメソッド呼出しが無効になり、効率を犠牲にしてコンパイルのパフォーマンスが向上します。 +.sp +\fB\-XX:CompileThreshold\fRオプションを使用して、コンパイルの前に、解釈されたメソッド呼出しの数を変更することもできます。 +.RE +.PP +\-Xdebug +.RS 4 +何も行いません。後方互換性のために用意されています。 +.RE +.PP +\-Xdiag +.RS 4 +追加の診断メッセージを表示します。 +.RE +.PP +\-Xfuture +.RS 4 +クラス・ファイル形式の仕様への準拠を強化する、厳密なクラス・ファイル形式のチェックが有効になります。将来のリリースでは、より厳密なチェックがデフォルトになるため、新しいコードを開発するときには、開発者はこのフラグを使用することをお薦めします。 +.RE +.PP +\-Xint +.RS 4 +インタプリタ専用モードでアプリケーションを実行します。ネイティブ・コードへのコンパイルは無効になり、すべてのバイトコードがインタプリタによって実行されます。ジャスト・イン・タイム(JIT)コンパイラが提供するパフォーマンス上の利点は、このモードでは実現されません。 +.RE +.PP +\-Xinternalversion +.RS 4 +\fB\-version\fRオプションより詳細なJVMバージョン情報を表示してから終了します。 +.RE +.PP +\-Xloggc:\fIfilename\fR +.RS 4 +詳細なGCイベント情報をロギング用にリダイレクトするファイルを設定します。このファイルに書き込まれる情報は、記録された各イベントの前に行われる最初のGCイベント以降に経過した時間を指定した\fB\-verbose:gc\fRの出力と類似しています。\fB\-Xloggc\fRオプションは\fB\-verbose:gc\fRをオーバーライドします(これらの両方が同じ\fBjava\fRコマンドで指定された場合)。 +.sp +例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xloggc:garbage\-collection\&.log\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-Xmaxjitcodesize=\fIsize\fR +.RS 4 +JITコンパイルされたコードの最大コード・キャッシュ・サイズ(バイト単位)を指定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、この値は48MBに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmaxjitcodesize=48m\fR + +.fi +.if n \{\ +.RE +.\} +このオプションは\fB\-XX:ReservedCodeCacheSize\fRと同等です。 +.RE +.PP +\-Xmixed +.RS 4 +ネイティブ・コードにコンパイルされたホット・メソッドを除き、インタプリタによってすべてのバイトコードを実行します。 +.RE +.PP +\-Xmn\fIsize\fR +.RS 4 +若い世代(ナーサリ)のヒープの初期サイズおよび最大サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。 +.sp +ヒープの若い世代リージョンは新しいオブジェクトに使用されます。GCは、他のリージョンよりこのリージョンで、より頻繁に実行されます。若い世代のサイズが小さすぎる場合、多数のマイナー・ガベージ・コレクションが実行されます。サイズが大きすぎる場合、フル・ガベージ・コレクションのみが実行されますが、完了までに時間がかかることがあります。若い世代のサイズは、全体のヒープ・サイズの半分から4分の1の間にしておくことをお薦めします。 +.sp +次の例では、若い世代の初期サイズおよび最大サイズを様々な単位を使用して256MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmn256m\fR +\fB\-Xmn262144k\fR +\fB\-Xmn268435456\fR + +.fi +.if n \{\ +.RE +.\} +若い世代のヒープの初期サイズと最大サイズの両方を設定する\fB\-Xmn\fRオプションのかわりに、初期サイズの設定には\fB\-XX:NewSize\fRを、最大サイズの設定には\fB\-XX:MaxNewSize\fRを使用できます。 +.RE +.PP +\-Xms\fIsize\fR +.RS 4 +ヒープの初期サイズ(バイト単位)を設定します。指定する値は、1MBより大きい1024の倍数にする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。 +.sp +次の例では、割り当てられたメモリーのサイズを様々な単位を使用して6MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xms6291456\fR +\fB\-Xms6144k\fR +\fB\-Xms6m\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを設定しない場合、初期サイズは、古い世代と若い世代に割り当てられたサイズの合計として設定されます。若い世代のヒープの初期サイズは、\fB\-Xmn\fRオプションまたは\fB\-XX:NewSize\fRオプションを使用して設定できます。 +.RE +.PP +\-Xmx\fIsize\fR +.RS 4 +メモリー割当てプールの最大サイズ(バイト単位)を指定します。指定する値は、2MBより大きい1024の倍数にする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は、実行時にシステム構成に基づいて選択されます。サーバー・デプロイメントでは、\fB\-Xms\fRおよび\fB\-Xmx\fRは通常同じ値に設定されます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.htmlの\fIJava SE HotSpot仮想マシンのガベージ・コレクション・チューニング・ガイド\fRのエルゴノミクスに関する項を参照してください。 +.sp +次の例では、割り当てられたメモリーの許可される最大サイズを様々な単位を使用して80MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmx83886080\fR +\fB\-Xmx81920k\fR +\fB\-Xmx80m\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-Xmx\fRオプションは\fB\-XX:MaxHeapSize\fRと同等です。 +.RE +.PP +\-Xnoclassgc +.RS 4 +クラスのガベージ・コレクション(GC)を無効にします。これにより、GC時間を節約でき、アプリケーション実行中の中断が短縮されます。 +.sp +起動時に\fB\-Xnoclassgc\fRを指定すると、アプリケーション内のクラス・オブジェクトは、GCの間はそのまま残り、常にライブであるとみなされます。これにより、より多くのメモリーが永久に占有されることになり、注意して使用しないと、メモリー不足の例外がスローされます。 +.RE +.PP +\-Xprof +.RS 4 +実行中のプログラムをプロファイルし、プロファイリング・データを標準出力に送信します。このオプションは、プログラム開発用のユーティリティとして提供されています。本番稼働システムでの使用を目的としたものではありません。 +.RE +.PP +\-Xrs +.RS 4 +JVMによるオペレーティング・システム・シグナルの使用を減らします。 +.sp +シャットダウン・フックは、JVMが突然終了した場合でも、シャットダウン時にユーザー・クリーンアップ・コード(データベース接続のクローズなど)を実行することによって、Javaアプリケーションのシャットダウンを順番に有効にします。 +.sp +JVMは、予期しない終了のシャットダウン・フックを実装するためにシグナルをキャッチします。JVMは、\fBSIGHUP\fR、\fBSIGINT\fRおよび\fBSIGTERM\fRを使用して、シャットダウン・フックの実行を開始します。 +.sp +JVMは、デバッグの目的でスレッド・スタックをダンプするという機能を実現するために、同様のメカニズムを使用します。JVMは、スレッド・ダンプを実行するために\fBSIGQUIT\fRを使用します。 +.sp +JVMを埋め込んでいるアプリケーションは、\fBSIGINT\fRや\fBSIGTERM\fRなどのシグナルを頻繁にトラップする必要があり、その結果、JVMのシグナル・ハンドラと衝突する可能性があります。\fB\-Xrs\fRオプションは、この問題に対処するために使用できます。\fB\-Xrs\fRが使用されている場合、\fBSIGINT\fR、\fBSIGTERM\fR、\fBSIGHUP\fRおよび\fBSIGQUIT\fRのシグナル・マスクはJVMによって変更されず、これらのシグナルのシグナル・ハンドラはインストールされません。 +.sp +\fB\-Xrs\fRを指定すると、次の2つの結果が生じます: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSIGQUIT\fRによるスレッド・ダンプは使用できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +シャットダウン・フック処理の実行は、JVMが終了しようとしている時点で\fBSystem\&.exit()\fRを呼び出すなどして、ユーザー・コード側で行う必要があります。 +.RE +.RE +.PP +\-Xshare:\fImode\fR +.RS 4 +クラス・データ共有モードを設定します。このオプションで使用可能な\fImode\fR引数は次のとおりです。 +.PP +auto +.RS 4 +可能な場合、共有クラスのデータを使用します。これは、Java HotSpot 32\-Bit Client VMの場合のデフォルト値です。 +.RE +.PP +on +.RS 4 +クラス・データ共有の使用が必要です。クラス・データ共有を使用できない場合、エラー・メッセージを出力して終了します。 +.RE +.PP +off +.RS 4 +共有クラス・データを使用しません。これは、Java HotSpot 32\-Bit Server VM、Java HotSpot 64\-Bit Client VMおよびJava HotSpot 64\-Bit Server VMの場合のデフォルト値です。 +.RE +.PP +dump +.RS 4 +クラス・データ共有アーカイブを手動で生成します。 +.RE +.RE +.PP +\-XshowSettings:\fIcategory\fR +.RS 4 +設定を表示して続行します。このオプションで使用可能な\fIcategory\fR引数は次のとおりです。 +.PP +all +.RS 4 +設定のすべてのカテゴリを表示します。これがデフォルト値です。 +.RE +.PP +locale +.RS 4 +ロケールに関連する設定を表示します。 +.RE +.PP +properties +.RS 4 +システム・プロパティに関連する設定を表示します。 +.RE +.PP +vm +.RS 4 +JVMの設定を表示します。 +.RE +.RE +.PP +\-Xss\fIsize\fR +.RS 4 +スレッドのスタック・サイズ(バイト単位)を設定します。KBを示す場合は文字\fBk\fRまたは\fBK\fR、MBを示す場合は文字\fBm\fRまたは\fBM\fR、GBを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値はプラットフォームによって異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/ARM (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OS X (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Windows: 仮想メモリーによって異なります。 +.RE +.sp +次の例では、スレッド・スタック・サイズを異なる単位で1024KBに設定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xss1m\fR +\fB\-Xss1024k\fR +\fB\-Xss1048576\fR + +.fi +.if n \{\ +.RE +.\} +このオプションは\fB\-XX:ThreadStackSize\fRと同等です。 +.RE +.PP +\-Xusealtsigs +.RS 4 +JVM内部シグナルの\fBSIGUSR1\fRおよび\fBSIGUSR2\fRのかわりに、代替シグナルを使用します。このオプションは\fB\-XX:+UseAltSigs\fRと同等です。 +.RE +.PP +\-Xverify:\fImode\fR +.RS 4 +バイトコード・ベリファイアのモードを設定します。バイトコードの検証は一部の問題のトラブルシューティングに役立ちますが、実行中のアプリケーションへのオーバーヘッドを増大させます。このオプションで使用可能な\fImode\fR引数は次のとおりです。 +.PP +なし +.RS 4 +バイトコードを検証しません。これにより、起動時間が短縮され、Javaによって提供される保護も軽減されます。 +.RE +.PP +remote +.RS 4 +ブートストラップ・クラス・ローダーでロードされていないこれらのクラスを検証します。これは、\fB\-Xverify\fRオプションを指定しない場合のデフォルトの動作です。 +.RE +.PP +all +.RS 4 +すべてのクラスを検証します。 +.RE +.RE +.SS "高度なランタイム・オプション" +.PP +これらのオプションは、Java HotSpot VMの実行時の動作を制御します。 +.PP +\-XX:+DisableAttachMechanism +.RS 4 +JVMにツールをアタッチするメカニズムを無効にするオプションを有効にします。デフォルトでは、このオプションは無効になっており、これは、アタッチ・メカニズムを有効にすると、\fBjcmd\fR、\fBjstack\fR、\fBjmap\fR、\fBjinfo\fRなどのツールを使用できることを意味します。 +.RE +.PP +\-XX:ErrorFile=\fIfilename\fR +.RS 4 +リカバリ不能なエラーが発生した場合にエラー・データが書き込まれるパスおよびファイル名を指定します。デフォルトでは、このファイルは、現在の作業ディレクトリに作成され、名前は\fBhs_err_pid\fR\fIpid\fR\fB\&.log\fR +(\fIpid\fRはエラーの原因となったプロセスの識別子)になります。次の例では、デフォルトのログ・ファイルを設定する方法を示します(プロセスの識別子は\fB%p\fRとして指定されます)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ErrorFile=\&./hs_err_pid%p\&.log\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、エラー・ログを\fB/var/log/java/java_error\&.log\fRに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ErrorFile=/var/log/java/java_error\&.log\fR + +.fi +.if n \{\ +.RE +.\} +(領域不足、権限の問題または別の問題により)指定したディレクトリにファイルを作成できない場合、ファイルはオペレーティング・システムの一時ディレクトリに作成されます。一時ディレクトリは\fB/tmp\fRです。 +.RE +.PP +\-XX:+FailOverToOldVerifier +.RS 4 +新しいタイプ・チェッカが失敗した場合の、古いベリファイアへの自動フェイルオーバーを有効にします。デフォルトでは、このオプションは無効になっており、最近のバイトコード・バージョンを使用したクラスには、これは無視されます(つまり、無効として処理されます)。古いバージョンのバイトコードを使用したクラスには、これを有効化できます。 +.RE +.PP +\-XX:+FlightRecorder +.RS 4 +アプリケーションの実行中に、Java Flight Recorder (JFR)の使用を有効にします。これは商用機能で、\fB\-XX:+UnlockCommercialFeatures\fRオプションを次のように指定することも必要になります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-XX:+UnlockCommercialFeatures \-XX:+FlightRecorder\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:FlightRecorderOptions=\fIparameter\fR=\fIvalue\fR +.RS 4 +JFRの動作を制御するパラメータを設定します。このオプションを使用できるのは、JFRが有効な場合(\fB\-XX:+FlightRecorder\fRオプションが指定されている場合)のみです。 +.sp +次のリストには、使用可能なすべてのJFRパラメータが含まれます。 +.PP +defaultrecording={true|false} +.RS 4 +記録が連続的なバックグラウンド記録か、または限定された時間に対して実行されるかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(記録は限定された時間に対して実行される)に設定されています。記録を連続的に実行するには、パラメータを\fBtrue\fRに設定します。 +.RE +.PP +disk={true|false} +.RS 4 +JFRでディスクに連続記録を書き込む必要があるかどうかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(ディスクへの連続記録は無効)に設定されています。これを有効にするには、パラメータを\fBtrue\fRに設定し、\fBdefaultrecording=true\fRも設定します。 +.RE +.PP +dumponexit={true|false} +.RS 4 +JVMが制御された方式で終了したときに、JFRデータのダンプ・ファイルを生成するかどうかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(終了時にダンプ・ファイルは生成されない)に設定されています。これを有効にするには、パラメータを\fBtrue\fRに設定し、\fBdefaultrecording=true\fRも設定します。 +.sp +ダンプ・ファイルは、\fBdumponexitpath\fRパラメータによって指定された場所に書き込まれます。 +.RE +.PP +dumponexitpath=\fIpath\fR +.RS 4 +\fBdumponexit=true\fRパラメータを設定した場合、JVMが制御された方式で終了したときに、作成されるJFRデータを含むダンプ・ファイルのパスおよび名前を指定します。パスの設定は、\fBdefaultrecording=true\fRも設定した場合のみ有効になります。 +.sp +指定したパスがディレクトリである場合、JVMは、作成の日付および時間を示すファイル名を割り当てます。指定したパスにすでに存在するファイルのファイル名が含まれる場合、指定したファイル名に日付およびタイム・スタンプを追加して新しいファイルが作成されます。 +.RE +.PP +globalbuffersize=\fIsize\fR +.RS 4 +データ保存に使用する総プライマリ・メモリー量(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、サイズは462848バイトに設定されています。 +.RE +.PP +loglevel={quiet|error|warning|info|debug|trace} +.RS 4 +JFRによってログ・ファイルに書き込まれるデータの量を指定します。デフォルトでは、\fBinfo\fRに設定されています。 +.RE +.PP +maxage=\fItime\fR +.RS 4 +デフォルト記録のディスク・データの最大保持時間を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB30s\fRという指定は30秒を意味します)。デフォルトでは、最大保持時間は15分(\fB15m\fR)に設定されています。 +.sp +このパラメータは、\fBdisk=true\fRパラメータが設定されている場合にのみ有効です。 +.RE +.PP +maxchunksize=\fIsize\fR +.RS 4 +記録内のデータ・チャンクの最大サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、データ・チャンクの最大サイズは12MBに設定されています。 +.RE +.PP +maxsize=\fIsize\fR +.RS 4 +デフォルト記録のディスク・データの最大保持サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、ディスク・データの最大サイズは制限されず、このパラメータは0に設定されています。 +.sp +このパラメータは、\fBdisk=true\fRパラメータが設定されている場合にのみ有効です。 +.RE +.PP +repository=\fIpath\fR +.RS 4 +一時ディスク記憶域のリポジトリ(ディレクトリ)を指定します。デフォルトでは、システムの一時ディレクトリが使用されます。 +.RE +.PP +samplethreads={true|false} +.RS 4 +スレッドのサンプリングを有効化するかどうかを指定します。スレッドのサンプリングは、このパラメータでサンプリング・イベントが有効になっている場合に発生します。デフォルトでは、このパラメータは有効になります。 +.RE +.PP +settings=\fIpath\fR +.RS 4 +イベント設定ファイル(タイプはJFC)のパスと名前を指定します。デフォルトでは、\fBJAVA_HOME/jre/lib/jfr\fRにある\fBdefault\&.jfc\fRファイルが使用されます。 +.RE +.PP +stackdepth=\fIdepth\fR +.RS 4 +JFRによるスタック・トレースのスタックの深さ。デフォルトでは、深さは64メソッド呼出しに設定されています。最大は2048で、最小は1です。 +.RE +.PP +threadbuffersize=\fIsize\fR +.RS 4 +スレッドごとのローカル・バッファ・サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。このパラメータの値が高いと、競合することなく、より多くのデータを収集してグローバル記憶域にフラッシュすることができます。スレッドが多い環境ではアプリケーションのフットプリントも増加します。デフォルトでは、ローカル・バッファ・サイズは5KBに設定されています。 +.RE +.sp +カンマで区切って、複数のパラメータの値を指定できます。たとえば、ディスクに連続記録を書き込み、データ・チャンクの最大サイズを10MBに設定するようにJFRに指示するには、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:FlightRecorderOptions=defaultrecording=true,disk=true,maxchunksize=10M\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:LargePageSizeInBytes=\fIsize\fR +.RS 4 +Solarisでは、Javaヒープに使用されるラージ・ページの最大サイズ(バイト単位)を設定します。\fIsize\fR引数は、2の累乗(2、4、8、16、\&.\&.\&.)である必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、サイズは0に設定され、これは、JVMではラージ・ページのサイズが自動的に選択されていることを意味します。 +.sp +次の例では、ラージ・ページのサイズを4メガバイト(MB)に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:LargePageSizeInBytes=4m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxDirectMemorySize=\fIsize\fR +.RS 4 +新規I/O (\fBjava\&.nio\fRパッケージ)の直接バッファ割当ての最大合計サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、サイズは0に設定され、これは、JVMではNIOの直接バッファ割当てのサイズが自動的に選択されていることを意味します。 +.sp +次の例では、NIOサイズを異なる単位で1024KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxDirectMemorySize=1m\fR +\fB\-XX:MaxDirectMemorySize=1024k\fR +\fB\-XX:MaxDirectMemorySize=1048576\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NativeMemoryTracking=\fImode\fR +.RS 4 +JVMのネイティブ・メモリー使用状況のトラッキングのモードを指定します。このオプションで使用可能な\fImode\fR引数は次のとおりです。 +.PP +off +.RS 4 +JVMのネイティブ・メモリー使用状況を追跡しません。これは、\fB\-XX:NativeMemoryTracking\fRオプションを指定しない場合のデフォルトの動作です。 +.RE +.PP +summary +.RS 4 +JVMサブシステム(Javaヒープ、クラス、コード、スレッドなど)によるメモリー使用状況のみ追跡します。 +.RE +.PP +detail +.RS 4 +JVMサブシステムによるメモリー使用状況のトラッキングに加えて、個々の\fBCallSite\fR +(個々の仮想メモリー・リージョンおよびそのコミット済リージョン)によるメモリー使用状況を追跡します。 +.RE +.RE +.PP +\-XX:ObjectAlignmentInBytes=\fIalignment\fR +.RS 4 +Javaオブジェクトのメモリー配置を設定します(バイト単位)。デフォルトでは、値が8バイトに設定されます。指定される値は、2の累乗にして8から256(両端を含む)の範囲内にする必要があります。このオプションにより、大きいJavaヒープ・サイズで圧縮ポインタを使用できます。 +.sp +バイト単位のヒープ・サイズ制限は次のように計算されます: +.sp +\fB4GB * ObjectAlignmentInBytes\fR +.sp +注意: 配置の値が増えると、オブジェクト間の未使用の領域も増えます。結果として、大きいヒープ・サイズで圧縮ポインタを使用するメリットがわからない可能性があります。 +.RE +.PP +\-XX:OnError=\fIstring\fR +.RS 4 +リカバリ不能なエラーが発生したときに実行する、カスタム・コマンドまたは一連のセミコロン区切りのコマンドを設定します。文字列に空白が含まれている場合は、引用符で囲む必要があります。 +.sp +次の例では、\fB\-XX:OnError\fRオプションを使用してコア・イメージを作成するために\fBgcore\fRコマンドを実行する方法、およびリカバリ不能なエラーの場合にデバッガを起動してプロセスに接続する方法を示します(\fB%p\fRは現在のプロセスを指定します)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:OnError="gcore %p;dbx \- %p"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:OnOutOfMemoryError=\fIstring\fR +.RS 4 +\fBOutOfMemoryError\fR例外が最初にスローされたときに実行する、カスタム・コマンドまたは一連のセミコロン区切りのコマンドを設定します。文字列に空白が含まれている場合は、引用符で囲む必要があります。コマンド文字列の例は、\fB\-XX:OnError\fRオプションの説明を参照してください。 +.RE +.PP +\-XX:+PerfDataSaveToFile +.RS 4 +有効な場合、Javaアプリケーションの終了時にjstat(1)バイナリ・データを保存します。このバイナリ・データは\fBhsperfdata_\fR\fI\fRという名前のファイルに保存されます。\fI\fRは、実行したJavaアプリケーションのプロセス識別子です。次のように\fBjstat\fRを使用して、このファイルに含まれるパフォーマンス・データを表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-class file:///\fR\fB\fI\fR\fR\fB/hsperfdata_\fR\fB\fI\fR\fR +\fBjstat \-gc file:///\fR\fB\fI\fR\fR\fB/hsperfdata_\fR\fB\fI\fR\fR +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+PrintCommandLineFlags +.RS 4 +コマンド行に表示された、人間工学的に選択したJVMフラグの印刷を有効にします。これは、ヒープ領域サイズや選択されたガベージ・コレクタなど、JVMによって設定されたエルゴノミック値を確認する場合に役立ちます。デフォルトでは、このオプションは無効であり、フラグは印刷されません。 +.RE +.PP +\-XX:+PrintNMTStatistics +.RS 4 +ネイティブ・メモリーのトラッキングが有効な場合に、JVMの終了時に収集されたネイティブ・メモリーのトラッキング・データの印刷を有効にします(\fB\-XX:NativeMemoryTracking\fRを参照してください)。デフォルトでは、このオプションは無効であり、ネイティブ・メモリーのトラッキング・データは印刷されません。 +.RE +.PP +\-XX:+RelaxAccessControlCheck +.RS 4 +ベリファイア内のアクセス制御チェックの量を減らします。デフォルトでは、このオプションは無効になっており、最近のバイトコード・バージョンを使用したクラスには、これは無視されます(つまり、無効として処理されます)。古いバージョンのバイトコードを使用したクラスには、これを有効化できます。 +.RE +.PP +\-XX:+ResourceManagement +.RS 4 +アプリケーションの実行中にリソース管理の使用を有効にします。 +.sp +これは商用機能で、\fB\-XX:+UnlockCommercialFeatures\fRオプションを次のように指定することも必要になります。 +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-XX:+ResourceManagement\fR +.RE +.PP +\-XX:ResourceManagementSampleInterval=\fIvalue\fR (ミリ秒) +.RS 4 +ミリ秒単位でリソース管理測定のサンプリング間隔を制御するパラメータを設定します。 +.sp +リソース管理が有効な場合のみ(つまり、\fB\-XX:+ResourceManagement\fRオプションが指定されている場合)、このオプションを使用できます。 +.RE +.PP +\-XX:+ShowMessageBoxOnError +.RS 4 +JVMでリカバリ不能なエラーが発生した場合、ダイアログ・ボックスの表示を有効にします。これにより、JVMにデバッガを接続してエラーの原因を調査できるように、JVMを終了しないようにして、プロセスをアクティブなままにします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:StartFlightRecording=\fIparameter\fR=\fIvalue\fR +.RS 4 +JavaアプリケーションのJFR記録を開始します。このオプションは、実行中に記録を開始する\fBJFR\&.start\fR診断コマンドと同等です。JFR記録の開始時に、次のパラメータを設定できます。 +.PP +compress={true|false} +.RS 4 +\fBgzip\fRファイル圧縮ユーティリティを使用して、ディスクでJFR記録ログ・ファイル(タイプはJFR)を圧縮するかどうかを指定します。このパラメータは、\fBfilename\fRパラメータが指定されている場合のみ有効です。デフォルトでは、\fBfalse\fR +(記録を圧縮しない)に設定されています。圧縮を有効にするには、パラメータを\fBtrue\fRに設定します。 +.RE +.PP +defaultrecording={true|false} +.RS 4 +記録が連続的なバックグラウンド記録か、または限定された時間に対して実行されるかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(記録は限定された時間に対して実行される)に設定されています。記録を連続的に実行するには、パラメータを\fBtrue\fRに設定します。 +.RE +.PP +delay=\fItime\fR +.RS 4 +Javaアプリケーションの起動時間と記録開始との間の遅延を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB10m\fRという指定は10分を意味します)。デフォルトでは、遅延は存在せず、このパラメータは0に設定されています。 +.RE +.PP +duration=\fItime\fR +.RS 4 +記録の期間を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB5h\fRという指定は5時間を意味します)。デフォルトでは、期間は制限されず、このパラメータは0に設定されています。 +.RE +.PP +filename=\fIpath\fR +.RS 4 +JFR記録ログ・ファイルのパスと名前を指定します。 +.RE +.PP +name=\fIidentifier\fR +.RS 4 +JFR記録の識別子を指定します。デフォルトでは、\fBRecording x\fRに設定されています。 +.RE +.PP +maxage=\fItime\fR +.RS 4 +デフォルト記録のディスク・データの最大保持時間を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB30s\fRという指定は30秒を意味します)。デフォルトでは、最大保持時間は15分(\fB15m\fR)に設定されています。 +.RE +.PP +maxsize=\fIsize\fR +.RS 4 +デフォルト記録のディスク・データの最大保持サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、ディスク・データの最大サイズは制限されず、このパラメータは0に設定されています。 +.RE +.PP +settings=\fIpath\fR +.RS 4 +イベント設定ファイル(タイプはJFC)のパスと名前を指定します。デフォルトでは、\fBJAVA_HOME/jre/lib/jfr\fRにある\fBdefault\&.jfc\fRファイルが使用されます。 +.RE +.sp +カンマで区切って、複数のパラメータの値を指定できます。たとえば、記録を現在の作業ディレクトリのtest\&.jfrに保存し、ログ・ファイルを圧縮するようJFRに指示するには、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:StartFlightRecording=filename=test\&.jfr,compress=true\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:ThreadStackSize=\fIsize\fR +.RS 4 +スレッドのスタック・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値はプラットフォームによって異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/ARM (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OS X (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Windows: 仮想メモリーによって異なります。 +.RE +.sp +次の例では、スレッド・スタック・サイズを異なる単位で1024KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ThreadStackSize=1m\fR +\fB\-XX:ThreadStackSize=1024k\fR +\fB\-XX:ThreadStackSize=1048576\fR + +.fi +.if n \{\ +.RE +.\} +このオプションは\fB\-Xss\fRと同等です。 +.RE +.PP +\-XX:+TraceClassLoading +.RS 4 +クラスがロードされるときのクラスのトレースを有効にします。デフォルトでは、このオプションは無効であり、クラスはトレースされません。 +.RE +.PP +\-XX:+TraceClassLoadingPreorder +.RS 4 +クラスが参照される順序で、ロードされたすべてのクラスのトレースを有効にします。デフォルトでは、このオプションは無効であり、クラスはトレースされません。 +.RE +.PP +\-XX:+TraceClassResolution +.RS 4 +定数プールの解決のトレースを有効にします。デフォルトでは、このオプションは無効であり、定数プールの解決はトレースされません。 +.RE +.PP +\-XX:+TraceClassUnloading +.RS 4 +クラスがアンロードされるときのクラスのトレースを有効にします。デフォルトでは、このオプションは無効であり、クラスはトレースされません。 +.RE +.PP +\-XX:+TraceLoaderConstraints +.RS 4 +ローダー制約の記録のトレースを有効にします。デフォルトでは、このオプションは無効であり、ローダー制約の記録は追跡されません。 +.RE +.PP +\-XX:+UnlockCommercialFeatures +.RS 4 +商用機能の使用を有効にします。商用機能は、http://www\&.oracle\&.com/technetwork/java/javase/terms/products/index\&.htmlにある\fIJava SE製品\fRページで定義されているように、Oracle Java SE AdvancedまたはOracle Java SE Suiteパッケージに付属しています。 +.sp +デフォルトでは、このオプションは無効であり、JVMは商用機能なしで実行されます。JVMプロセスが有効化された後、そのプロセスの使用を無効にすることはできません。 +.RE +.PP +\-XX:+UseAltSigs +.RS 4 +JVM内部シグナルの\fBSIGUSR1\fRおよび\fBSIGUSR2\fRのかわりに、代替シグナルの使用を有効にします。デフォルトでは、このオプションは無効であり、代替シグナルは使用されません。このオプションは\fB\-Xusealtsigs\fRと同等です。 +.RE +.PP +\-XX:\-UseBiasedLocking +.RS 4 +バイアス・ロックの使用を無効にします。かなりの量の非競合の同期化がある一部のアプリケーションは、このフラグを有効にすると大幅な高速化が実現しますが、特定のパターンのロックがあるアプリケーションは、速度が低下することがあります。バイアス・ロックの方法の詳細は、http://www\&.oracle\&.com/technetwork/java/tuning\-139912\&.html#section4\&.2\&.5にあるJavaチューニングのホワイト・ペーパーの例を参照してください。 +.sp +デフォルトでは、このオプションは有効になっています。 +.RE +.PP +\-XX:\-UseCompressedOops +.RS 4 +圧縮されたポインタの使用を無効にします。デフォルトではこのオプションが有効であり、Javaヒープ・サイズが32GBより小さい場合に圧縮ポインタが使用されます。このオプションを有効にすると、オブジェクト参照は、64ビットのポインタではなく32ビットのオフセットとして表され、これにより、32GBより小さいJavaヒープ・サイズのアプリケーションの実行時に、通常、パフォーマンスが向上します。このオプションは、64ビットのJVMでのみ機能します。 +.sp +Javaヒープ・サイズが32GBより大きい場合にも圧縮ポインタを使用できます。\fB\-XX:ObjectAlignmentInBytes\fRオプションを参照してください。 +.RE +.PP +\-XX:+UseHugeTLBFS +.RS 4 +Linux用のこのオプションは、\fB\-XX:+UseLargePages\fRを指定するのと同じです。このオプションは、デフォルトでは無効になっています。このオプションは、メモリーの予約時にすべてのラージ・ページを事前に割り当てます。そのため、JVMはラージ・ページ・メモリー領域を動的に拡張または縮小できません。この動作を行う場合は、\fB\-XX:UseTransparentHugePages\fRを参照してください。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+UseLargePages +.RS 4 +ラージ・ページのメモリーの使用を有効にします。デフォルトでは、このオプションは無効であり、ラージ・ページのメモリーは使用されません。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+UseMembar +.RS 4 +スレッドの状態の遷移でメンバーの発行を有効にします。このオプションは、有効になっているARMサーバーを除くすべてのプラットフォーム上で、デフォルトでは無効になっています。(ARMサーバーでこのオプションを無効にしないことをお薦めします。) +.RE +.PP +\-XX:+UsePerfData +.RS 4 +\fBperfdata\fR機能を有効にします。このオプションはデフォルトで有効になっており、JVMのモニタリングおよびパフォーマンス・テストが可能になります。これを無効にすると、\fBhsperfdata_userid\fRディレクトリの作成を抑制します。\fBperfdata\fR機能を無効にするには、\fB\-XX:\-UsePerfData\fRを指定します。 +.RE +.PP +\-XX:+UseTransparentHugePages +.RS 4 +Linuxでは、動的に拡張または縮小できるラージ・ページの使用を有効化してください。このオプションは、デフォルトでは無効になっています。OSが他のページを移動してヒュージ・ページを作成するため、透過的ヒュージ・ページでパフォーマンスの問題が検出される場合があります。このオプションは試験的に使用できます。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+AllowUserSignalHandlers +.RS 4 +アプリケーションによるシグナル・ハンドラのインストールを有効にします。デフォルトでは、このオプションは無効であり、アプリケーションはシグナル・ハンドラをインストールすることは許可されていません。 +.RE +.SS "高度なJITコンパイラ・オプション" +.PP +これらのオプションは、Java HotSpot VMで実行される動的なjust\-in\-time (JIT)コンパイラを制御します。 +.PP +\-XX:+AggressiveOpts +.RS 4 +積極的なパフォーマンス最適化機能の使用を有効にします。これは今後のリリースでデフォルトになる予定です。デフォルトでは、このオプションは無効であり、試験的なパフォーマンス機能は使用されません。 +.RE +.PP +\-XX:AllocateInstancePrefetchLines=\fIlines\fR +.RS 4 +インスタンス割当てポインタの前にプリフェッチする行数を設定します。デフォルトでは、プリフェッチする行数は1に設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocateInstancePrefetchLines=1\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchDistance=\fIsize\fR +.RS 4 +オブジェクト割当てのプリフェッチ距離のサイズ(バイト単位)を設定します。新規オブジェクトの値で書き込もうとするメモリーは、最後に割り当てられたオブジェクトのアドレスから、この距離までプリフェッチされます。各Javaスレッドには独自の割当てポイントがあります。 +.sp +負の値は、プリフェッチ距離はプラットフォームに基づいて選択されることを示します。正の値は、プリフェッチするバイト数です。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は\-1に設定されています。 +.sp +次の例では、プリフェッチ距離を1024バイトに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchDistance=1024\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchInstr=\fIinstruction\fR +.RS 4 +割当てポインタの前にプリフェッチするプリフェッチ命令を設定します。Java HotSpot Server VMのみが、このオプションをサポートしています。使用可能な値は0から3までです。値の背後にある実際の命令は、プラットフォームによって異なります。デフォルトでは、プリフェッチ命令は0に設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchInstr=0\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchLines=\fIlines\fR +.RS 4 +コンパイルされたコードで生成されるプリフェッチ命令を使用して、最後のオブジェクト割当て後にロードするキャッシュ行数を設定します。最後に割り当てられたオブジェクトがインスタンスの場合は、デフォルト値は1になり、配列の場合は3になります。 +.sp +次の例では、ロードされるキャッシュ行数を5に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchLines=5\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchStepSize=\fIsize\fR +.RS 4 +順次プリフェッチ命令のステップ・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、ステップ・サイズは16バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchStepSize=16\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchStyle=\fIstyle\fR +.RS 4 +プリフェッチ命令に生成されるコード・スタイルを設定します。\fIstyle\fR引数は、0から3までの整数です。 +.PP +0 +.RS 4 +プリフェッチ命令を生成しません。 +.RE +.PP +1 +.RS 4 +各割当ての後で、プリフェッチ命令を実行します。これはデフォルトのパラメータです。 +.RE +.PP +2 +.RS 4 +スレッド・ローカルな割当てブロック(TLAB)ウォーターマーク・ポインタを使用して、プリフェッチ命令を実行するタイミングを決定します。 +.RE +.PP +3 +.RS 4 +割当てプリフェッチ用のSPARCでBIS命令を使用します。 +.RE +.sp +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+BackgroundCompilation +.RS 4 +バックグラウンド・コンパイルを有効にします。このオプションはデフォルトで有効になっています。バックグラウンド・コンパイルを無効にするには、\fB\-XX:\-BackgroundCompilation\fRを指定します(これは\fB\-Xbatch\fRを指定するのと同等です)。 +.RE +.PP +\-XX:CICompilerCount=\fIthreads\fR +.RS 4 +コンパイルに使用するコンパイラ・スレッドの数を設定します。デフォルトでは、スレッド数は、サーバーJVMの場合は2、クライアントJVMの場合は1に設定されており、層コンパイルが使用されている場合、コア数に合せて増減します。次の例では、スレッドの数を2に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CICompilerCount=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CodeCacheMinimumFreeSpace=\fIsize\fR +.RS 4 +コンパイルに必要な最小空き領域(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。最小空き領域より少ない領域しか残っていない場合、コンパイルは停止します。デフォルトでは、このオプションは500KBに設定されています。次の例では、最小空き領域を1024MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CodeCacheMinimumFreeSpace=1024m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CompileCommand=\fIcommand\fR,\fImethod\fR[,\fIoption\fR] +.RS 4 +メソッドで実行するコマンドを指定します。たとえば、コンパイル元から\fBString\fRクラスの\fBindexOf()\fRメソッドを実行するには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,java/lang/String\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +スラッシュ(\fB/\fR)で区切られたすべてのパッケージおよびサブパッケージを含む、完全クラス名を指定します。切取りと貼付けの操作を容易にするために、\fB\-XX:+PrintCompilation\fRオプションおよび\fB\-XX:+LogCompilation\fRオプションによって生成されるメソッド名の形式を使用することもできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,java\&.lang\&.String::indexOf\fR + +.fi +.if n \{\ +.RE +.\} +署名なしでメソッドを指定すると、コマンドは指定した名前を持つすべてのメソッドに適用されます。ただし、クラス・ファイル形式でメソッドの署名を指定することもできます。この場合、引数を引用符で囲む必要があり、囲まないと、シェルによりセミコロンがコマンドの終了として扱われます。たとえば、コンパイル元から\fBString\fRクラスの\fBindexOf(String)\fRメソッドのみ除外するには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand="exclude,java/lang/String\&.indexOf,(Ljava/lang/String;)I"\fR + +.fi +.if n \{\ +.RE +.\} +また、クラス名およびメソッド名にワイルドカードとしてアスタリスク(*)を使用できます。たとえば、コンパイル元からすべてのクラスのすべての\fBindexOf()\fRメソッドを除外するには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,*\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +カンマとピリオドは空白の別名で、これにより、シェルを介してコンパイラ・コマンドを渡すことが容易になります。引数を引用符で囲むことで、空白をセパレータとして使用して\fB\-XX:CompileCommand\fRに引数を渡すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand="exclude java/lang/String indexOf"\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-XX:CompileCommand\fRオプションを使用してコマンド行で渡されたコマンドを解析した後に、JITコンパイラは\fB\&.hotspot_compiler\fRファイルからコマンドを読み取ります。このファイルにコマンドを追加するか、または\fB\-XX:CompileCommandFile\fRオプションを使用して別のファイルを指定することができます。 +.sp +複数のコマンドを追加するには、\fB\-XX:CompileCommand\fRオプションを複数回指定するか、または改行セパレータ(\fB\en\fR)を使用して各引数を区切ります。次のコマンドを使用できます。 +.PP +break +.RS 4 +指定したメソッドのコンパイルの最初に停止するために、JVMのデバッグ時のブレークポイントを設定します。 +.RE +.PP +compileonly +.RS 4 +指定したメソッドを除いたすべてのメソッドを、コンパイルから除外します。別の方法として、\fB\-XX:CompileOnly\fRオプションを使用して複数のメソッドを指定できます。 +.RE +.PP +dontinline +.RS 4 +指定したメソッドをインライン化しないようにします。 +.RE +.PP +exclude +.RS 4 +指定したメソッドをコンパイルから除外します。 +.RE +.PP +help +.RS 4 +\fB\-XX:CompileCommand\fRオプションのヘルプ・メッセージを印刷します。 +.RE +.PP +inline +.RS 4 +指定したメソッドをインライン化しようとします。 +.RE +.PP +log +.RS 4 +指定したメソッドを除くすべてのメソッドに対して、(\fB\-XX:+LogCompilation\fRオプションを使用して)コンパイル・ロギングを除外します。デフォルトでは、コンパイルされたすべてのメソッドにロギングが実行されます。 +.RE +.PP +option +.RS 4 +このコマンドは、最後の引数(\fIoption\fR)のかわりに、指定したメソッドにJITコンパイル・オプションを渡すために使用できます。コンパイル・オプションは、メソッド名の後の末尾に設定されます。たとえば、\fBStringBuffer\fRクラスの\fBappend()\fRメソッドに対して\fBBlockLayoutByFrequency\fRオプションを有効にするには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=option,java/lang/StringBuffer\&.append,BlockLayoutByFrequency\fR + +.fi +.if n \{\ +.RE +.\} +カンマまたは空白で区切って、複数のコンパイル・オプションを指定できます。 +.RE +.PP +print +.RS 4 +指定したメソッドのコンパイル後に生成されたアセンブラ・コードを出力します。 +.RE +.PP +quiet +.RS 4 +コンパイル・コマンドを出力しません。デフォルトでは、\fB\-XX:CompileCommand\fRオプションを使用して指定したコマンドが出力されます。たとえば、\fBString\fRクラスの\fBindexOf()\fRメソッドのコンパイルから除外する場合、次が標準出力に出力されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompilerOracle: exclude java/lang/String\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +他の\fB\-XX:CompileCommand\fRオプションの前に\fB\-XX:CompileCommand=quiet\fRオプションを指定することによって、これを抑制できます。 +.RE +.RE +.PP +\-XX:CompileCommandFile=\fIfilename\fR +.RS 4 +JITコンパイラ・コマンドの読取り元のファイルを設定します。デフォルトでは、JITコンパイラによって実行されるコマンドを格納するために、\fB\&.hotspot_compiler\fRファイルが使用されます。 +.sp +コマンド・ファイルの各行は、コマンドが使用されるコマンド、クラス名およびメソッド名を表します。たとえば、次の行は、\fBString\fRクラスの\fBtoString()\fRメソッドに対してアセンブリ・コードを出力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBprint java/lang/String toString\fR + +.fi +.if n \{\ +.RE +.\} +メソッドで実行するJITコンパイラのコマンドの指定の詳細は、\fB\-XX:CompileCommand\fRオプションを参照してください。 +.RE +.PP +\-XX:CompileOnly=\fImethods\fR +.RS 4 +コンパイルを制限する(カンマで区切られた)メソッドのリストを設定します。指定したメソッドのみがコンパイルされます。完全クラス名(パッケージおよびサブパッケージを含む)で各メソッドを指定します。たとえば、\fBString\fRクラスの\fBlength()\fRメソッドおよび\fBList\fRクラスの\fBsize()\fRメソッドのみをコンパイルするには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java/lang/String\&.length,java/util/List\&.size\fR + +.fi +.if n \{\ +.RE +.\} +スラッシュ(\fB/\fR)で区切られたすべてのパッケージおよびサブパッケージを含む、完全クラス名を指定します。切取りと貼付けの操作を容易にするために、\fB\-XX:+PrintCompilation\fRオプションおよび\fB\-XX:+LogCompilation\fRオプションによって生成されるメソッド名の形式を使用することもできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java\&.lang\&.String::length,java\&.util\&.List::size\fR + +.fi +.if n \{\ +.RE +.\} +ワイルドカードはサポートされていませんが、クラス名またはパッケージ名だけを指定してクラスまたはパッケージのすべてのメソッドをコンパイルすることも、メソッドだけを指定して任意のクラスのこの名前を持つメソッドをコンパイルすることもできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java/lang/String\fR +\fB\-XX:CompileOnly=java/lang\fR +\fB\-XX:CompileOnly=\&.length\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CompileThreshold=\fIinvocations\fR +.RS 4 +コンパイル前に解釈されたメソッド呼出しの数を設定します。デフォルトでは、サーバーJVMでは、JITコンパイラは、10,000の解釈されたメソッド呼出しを実行して、効率的なコンパイルのための情報を収集します。クライアントJVMの場合、デフォルト設定は1,500呼出しです。層コンパイルが有効な場合、このオプションは無視されます。オプション\fB\-XX:+TieredCompilation\fRを参照してください。次の例では、解釈されたメソッド呼出しの数を5,000に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileThreshold=5000\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-Xcomp\fRオプションを指定して、コンパイルの前に、Javaメソッドの解釈を完全に無効にすることができます。 +.RE +.PP +\-XX:+DoEscapeAnalysis +.RS 4 +エスケープ分析の使用を有効にします。このオプションはデフォルトで有効になっています。エスケープ分析の使用を無効にするには、\fB\-XX:\-DoEscapeAnalysis\fRを指定します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:InitialCodeCacheSize=\fIsize\fR +.RS 4 +初期コード・キャッシュ・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は500KBに設定されています。初期コード・キャッシュ・サイズをシステムの最小メモリー・ページ・サイズより小さくしないでください。次の例では、初期コード・キャッシュ・サイズを32KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialCodeCacheSize=32k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+Inline +.RS 4 +メソッドのインライン化を有効にします。このオプションは、パフォーマンスを向上させるためにデフォルトで有効になっています。メソッドのインライン化を無効にするには、\fB\-XX:\-Inline\fRを指定します。 +.RE +.PP +\-XX:InlineSmallCode=\fIsize\fR +.RS 4 +インライン化が必要なコンパイルされたメソッドの最大コード・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。指定したサイズより小さいサイズのコンパイルされたメソッドのみが、インライン化されます。デフォルトでは、最大コード・サイズは1000バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InlineSmallCode=1000\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+LogCompilation +.RS 4 +現在の作業ディレクトリにある\fBhotspot\&.log\fRという名前のファイルへのコンパイル・アクティビティのロギングを有効にします。\fB\-XX:LogFile\fRオプションを使用して、異なるログ・ファイル・パスと名前を指定できます。 +.sp +デフォルトでは、このオプションは無効であり、コンパイル・アクティビティは記録されません。\fB\-XX:+LogCompilation\fRオプションは、診断JVMオプションのロックを解除する\fB\-XX:UnlockDiagnosticVMOptions\fRオプションとともに使用する必要があります。 +.sp +\fB\-XX:+PrintCompilation\fRオプションを使用して、メソッドをコンパイルするたびに、コンソールに出力されたメッセージを含む詳細な診断出力を有効化できます。 +.RE +.PP +\-XX:MaxInlineSize=\fIsize\fR +.RS 4 +インライン化するメソッドの最大バイトコード・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、最大バイトコード・サイズは35バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxInlineSize=35\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxNodeLimit=\fInodes\fR +.RS 4 +単一のメソッドのコンパイル時に使用されるノードの最大数を設定します。デフォルトでは、ノードの最大数は65,000に設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxNodeLimit=65000\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxTrivialSize=\fIsize\fR +.RS 4 +インライン化する単純メソッドの最大バイトコード・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、単純メソッドの最大バイトコード・サイズは6バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxTrivialSize=6\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+OptimizeStringConcat +.RS 4 +\fBString\fR連結操作の最適化を有効にします。このオプションはデフォルトで有効になっています。\fBString\fR連結操作の最適化を無効にするには、\fB\-XX:\-OptimizeStringConcat\fRを指定します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+PrintAssembly +.RS 4 +外部の\fBdisassembler\&.so\fRライブラリを使用して、バイトコード化されたネイティブのメソッドのアセンブリ・コードの出力を有効にします。これにより、生成されたコードを表示することができ、パフォーマンスの問題の診断に役立ちます。 +.sp +デフォルトでは、このオプションは無効であり、アセンブリ・コードは印刷されません。\fB\-XX:+PrintAssembly\fRオプションは、診断JVMオプションのロックを解除する\fB\-XX:UnlockDiagnosticVMOptions\fRオプションとともに使用する必要があります。 +.RE +.PP +\-XX:+PrintCompilation +.RS 4 +メソッドをコンパイルするたびに、コンソールにメッセージを出力することによって、JVMからの詳細な診断出力を有効にします。これにより、実際にコンパイルされるメソッドを確認できます。デフォルトでは、このオプションは無効であり、診断出力は印刷されません。 +.sp +\fB\-XX:+LogCompilation\fRオプションを使用して、コンパイル・アクティビティをファイルに記録することもできます。 +.RE +.PP +\-XX:+PrintInlining +.RS 4 +インライン化の決定内容の出力を有効にします。これにより、インライン化されるメソッドを確認できます。 +.sp +デフォルトでは、このオプションは無効であり、インライン化情報は出力されません。\fB\-XX:+PrintInlining\fRオプションは、診断JVMオプションのロックを解除する\fB\-XX:+UnlockDiagnosticVMOptions\fRオプションとともに使用する必要があります。 +.RE +.PP +\-XX:ReservedCodeCacheSize=\fIsize\fR +.RS 4 +JITコンパイルされたコードの最大コード・キャッシュ・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。このオプションは2GBの制限があります。そうでない場合は、エラーが生成されます。最大コード・キャッシュ・サイズを初期コード・キャッシュ・サイズより小さくしないでください。\fB\-XX:InitialCodeCacheSize\fRオプションを参照してください。このオプションは\fB\-Xmaxjitcodesize\fRと同等です。 +.RE +.PP +\-XX:RTMAbortRatio=\fIabort_ratio\fR +.RS 4 +RTM中止率は、すべての実行済RTMトランザクションに対するパーセンテージ(%)として指定されます。中止されたトランザクション数がこの率を超えた場合、コンパイルされたコードが非最適化されます。この率は、\fB\-XX:+UseRTMDeopt\fRオプションが有効な場合に使用されます。このオプションのデフォルト値は50です。つまり、すべてのトランザクションの50%が中止された場合、コンパイルされたコードが非最適化されます。 +.RE +.PP +\-XX:RTMRetryCount=\fInumber_of_retries\fR +.RS 4 +中止またはビジーの場合、RTMロック・コードは、標準のロック・メカニズムにフォールバックする前にこのオプションによって指定された回数再試行されます。このオプションのデフォルト値は5です。\fB\-XX:UseRTMLocking\fRオプションを有効化する必要があります。 +.RE +.PP +\-XX:+TieredCompilation +.RS 4 +層コンパイルの使用を有効にします。デフォルトでは、このオプションは有効になっています。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+UseAES +.RS 4 +Intel、AMDおよびSPARCハードウェアに対して、ハードウェアベースのAES組込みを有効化します。Intel Westmere (2010以降)、AMD Bulldozer (2011以降)およびSPARC (T4以降)が、サポートされているハードウェアです。UseAESは、UseAESIntrinsicsとともに使用します。 +.RE +.PP +\-XX:+UseAESIntrinsics +.RS 4 +UseAESとUseAESIntrinsicsフラグはデフォルトで有効化されており、Java HotSpot Server VM 32ビットおよび64ビットに対してのみサポートされています。ハードウェアベースのAES組込みを無効化するには、\fB\-XX:\-UseAES \-XX:\-UseAESIntrinsics\fRを指定します。たとえば、ハードウェアAESを有効化するには、次のフラグを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:+UseAES \-XX:+UseAESIntrinsics\fR + +.fi +.if n \{\ +.RE +.\} +32ビットおよび64ビットに対してUseAESおよびUseAESIntrinsicsフラグをサポートするには、\fB\-server\fRオプションを使用してJava HotSpot Server VMを選択します。これらのフラグは、クライアントVMではサポートされていません。 +.RE +.PP +\-XX:+UseCodeCacheFlushing +.RS 4 +コンパイラをシャットダウンする前に、コード・キャッシュのフラッシュを有効にします。このオプションはデフォルトで有効になっています。コンパイラをシャットダウンする前にコード・キャッシュのフラッシュを無効にするには\fB\-XX:\-UseCodeCacheFlushing\fRを指定します。 +.RE +.PP +\-XX:+UseCondCardMark +.RS 4 +カード表の更新前に、カードがすでにマークされているかどうかのチェックを有効にします。このオプションは、デフォルトでは無効になっており、複数のソケットを持つマシン上でのみ使用する必要があります。これにより、同時操作にかなり依存しているJavaアプリケーションのパフォーマンスが向上します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+UseRTMDeopt +.RS 4 +中止率に応じて、RTMロックを自動調整します。この率は、\fB\-XX:RTMAbortRatio\fRオプションによって指定されます。中止されたトランザクション数が中止率を超えた場合、ロックを含むメソッドがすべてのロックで標準のロックとして非最適化および再コンパイルされます。このオプションは、デフォルトでは無効になっています。\fB\-XX:+UseRTMLocking\fRオプションを有効化する必要があります。 +.RE +.PP +\-XX:+UseRTMLocking +.RS 4 +フォールバック・ハンドラとして標準のロック・メカニズムを使用して、展開されたすべてのロックに対してRestricted Transactional Memory (RTM)ロック・コードを生成します。このオプションは、デフォルトでは無効になっています。RTMに関連するオプションは、Transactional Synchronization Extensions (TSX)をサポートするx86 CPU上のJava HotSpot Server VMに対してのみ使用可能です。 +.sp +RTMは、x86命令セット拡張でマルチスレッド・アプリケーションの作成を容易にするIntelのTSXの一部です。RTMでは、新しい命令 +\fBXBEGIN\fR、\fBXABORT\fR、\fBXEND\fRおよび\fBXTEST\fRが導入されています。\fBXBEGIN\fRおよび\fBXEND\fR命令は、トランザクションとして実行するための命令セットを囲みます。トランザクションの実行時に競合が見つからなかった場合、メモリーとレジスタの変更が、\fBXEND\fR命令で同時にコミットされます。\fBXABORT\fR命令ではトランザクションを明示的に中止でき、\fBXEND\fR命令では命令セットがトランザクション内で実行中かどうかを確認できます。 +.sp +トランザクションのロックは、別のスレッドが同じトランザクションにアクセスしようとしたときに展開されます。したがって、そのトランザクションへのアクセスを最初にリクエストしなかったスレッドはブロックされます。RTMでは、トランザクションが中止または失敗した場合のために、フォールバックの操作セットを指定する必要があります。RTMロックとは、TSXのシステムに委譲されているロックです。 +.sp +RTMにより、重要なリージョンにおいて衝突が少なく競合度の高いロックのパフォーマンスが向上されます(これは、複数のスレッドによって同時にアクセスできないコードです)。また、RTMにより、粗粒度ロックのパフォーマンスも向上されますが、一般的にマルチスレッド・アプリケーションでのパフォーマンスはよくありません。(粗粒度ロックとは、ロックの取得および解放のオーバーヘッドを最小化するために長い期間ロックを保持する戦略であり、一方、細粒度ロックとは必要な場合のみロックし可能なかぎり早期にロック解除することで最大限の並行処理の達成を試みる戦略です。)さらに、異なるスレッドによって使用されている軽度な競合ロックの場合、RTMにより、誤ったキャッシュ・ライン共有(キャッシュ・ライン・ピンポンとも呼ばれる)を削減できます。これは、異なるプロセッサからの複数のスレッドが異なるリソースにアクセスしている場合に発生しますが、リソースは同じキャッシュ・ラインを共有します。結果として、プロセッサは他のプロセッサのキャッシュ・ラインを繰り返し無効にし、これにより、キャッシュではなくメイン・メモリーからの読取りが強制されます。 +.RE +.PP +\-XX:+UseSHA +.RS 4 +SPARCハードウェアのSHA暗号化ハッシュ関数のハードウェアベースの組込みを有効にします。\fBUseSHA\fRは、\fBUseSHA1Intrinsics\fR、\fBUseSHA256Intrinsics\fRおよび\fBUseSHA512Intrinsics\fRオプションと組み合せて使用します。 +.sp +\fBUseSHA\fRおよび\fBUseSHA*Intrinsics\fRフラグはデフォルトで有効であり、SPARC T4以上のJava HotSpot Server VM 64ビットでのみサポートされます。 +.sp +SHA操作に対して\fBsun\&.security\&.provider\&.Sun\fRプロバイダを使用する場合のみ、この機能を適用できます。 +.sp +すべてのハードウェアベースのSHA組込みを無効化するには、\fB\-XX:\-UseSHA\fRを指定してください。特定のSHA組込みのみ無効化するには、適切な対応するオプションを使用してください。たとえば、\fB\-XX:\-UseSHA256Intrinsics\fRなどです。 +.RE +.PP +\-XX:+UseSHA1Intrinsics +.RS 4 +SHA\-1暗号化ハッシュ関数の組込みを有効にします。 +.RE +.PP +\-XX:+UseSHA256Intrinsics +.RS 4 +SHA\-224およびSHA\-256暗号化ハッシュ関数の組込みを有効にします。 +.RE +.PP +\-XX:+UseSHA512Intrinsics +.RS 4 +SHA\-384およびSHA\-512暗号化ハッシュ関数の組込みを有効にします。 +.RE +.PP +\-XX:+UseSuperWord +.RS 4 +スカラー演算のスーパーワード演算への変換を有効にします。このオプションはデフォルトで有効になっています。スカラー演算のスーパーワード演算への変換を無効にするには、\fB\-XX:\-UseSuperWord\fRを指定します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.SS "高度なサービスアビリティ・オプション" +.PP +これらのオプションは、システム情報を収集し、詳細なデバッグを実行する機能を提供します。 +.PP +\-XX:+ExtendedDTraceProbes +.RS 4 +パフォーマンスに影響を与える追加の\fBdtrace\fRツール・プローブを有効にします。デフォルトでは、このオプションは無効になっており、\fBdtrace\fRは標準プローブのみを実行します。 +.RE +.PP +\-XX:+HeapDumpOnOutOfMemory +.RS 4 +\fBjava\&.lang\&.OutOfMemoryError\fR例外がスローされた場合に、ヒープ・プロファイラ(HPROF)を使用して、現在のディレクトリ内のファイルへのJavaヒープのダンプを有効にします。\fB\-XX:HeapDumpPath\fRオプションを使用して、ヒープ・ダンプ・ファイルのパスおよび名前を明示的に設定できます。デフォルトでは、このオプションは無効であり、\fBOutOfMemoryError\fR例外がスローされた場合にヒープはダンプされません。 +.RE +.PP +\-XX:HeapDumpPath=\fIpath\fR +.RS 4 +\fB\-XX:+HeapDumpOnOutOfMemoryError\fRオプションが設定されている場合、ヒープ・プロファイラ(HPROF)が提供するヒープ・ダンプを書き込むパスおよびファイル名を設定します。デフォルトでは、このファイルは、現在の作業ディレクトリに作成され、名前は\fBjava_pid\fR\fIpid\fR\fB\&.hprof\fR +(\fIpid\fRはエラーの原因となったプロセスの識別子)になります。次の例では、デフォルトのファイルを明示的に設定する方法を示します(\fB%p\fRは現在のプロセスの識別子を表します)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:HeapDumpPath=\&./java_pid%p\&.hprof\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、ヒープ・ダンプ・ファイルを\fB/var/log/java/java_heapdump\&.hprof\fRに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:HeapDumpPath=/var/log/java/java_heapdump\&.hprof\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:LogFile=\fIpath\fR +.RS 4 +ログ・データが書き込まれるパスおよびファイル名を設定します。デフォルトでは、ファイルは現在の作業ディレクトリに作成され、名前は\fBhotspot\&.log\fRです。 +.sp +次の例では、ログ・ファイルを\fB/var/log/java/hotspot\&.log\fRに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:LogFile=/var/log/java/hotspot\&.log\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+PrintClassHistogram +.RS 4 +\fB[Control]+[C]\fRイベント(\fBSIGTERM\fR)後にクラス・インスタンスのヒストグラムの印刷を有効にします。デフォルトでは、このオプションは無効です。 +.sp +このオプションを設定すると、\fBjmap \-histo\fRコマンド、または\fBjcmd \fR\fIpid\fR\fB GC\&.class_histogram\fRコマンド(\fIpid\fRは現在のJavaプロセスの識別子)を実行する場合と同じになります。 +.RE +.PP +\-XX:+PrintConcurrentLocks +.RS 4 +印刷を有効にします ロック(次の後) \- イベント。デフォルトでは、このオプションは無効です。 +.sp +\fB[Control]+[C]\fRイベント(\fBSIGTERM\fR)後に\fBjava\&.util\&.concurrent\fRロックの印刷を有効にします。デフォルトでは、このオプションは無効です。 +.sp +このオプションを設定すると、\fBjstack \-l\fRコマンド、または\fBjcmd \fR\fIpid\fR\fB Thread\&.print \-l\fRコマンド(\fIpid\fRは現在のJavaプロセスの識別子)を実行する場合と同じになります。 +.RE +.PP +\-XX:+UnlockDiagnosticVMOptions +.RS 4 +JVMの診断を目的としたオプションをアンロックします。デフォルトでは、このオプションは無効であり、診断オプションは使用できません。 +.RE +.SS "高度なガベージ・コレクション・オプション" +.PP +これらのオプションは、ガベージ・コレクション(GC)がJava HotSpot VMによってどのように実行されるかを制御します。 +.PP +\-XX:+AggressiveHeap +.RS 4 +Javaヒープの最適化を有効にします。これにより、コンピュータの構成(RAMおよびCPU)に基づいて、様々なパラメータが、メモリー割当てが集中した長時間実行ジョブに最適になるように設定されます。デフォルトでは、このオプションは無効であり、ヒープは最適化されません。 +.RE +.PP +\-XX:+AlwaysPreTouch +.RS 4 +JVMの初期化中にJavaヒープ上のすべてのページのタッチを有効にします。これにより、\fBmain()\fRメソッドの入力前に、すべてのページがメモリーに取得されます。このオプションは、物理メモリーにマップされたすべての仮想メモリーを含む長時間実行のシステムをシミュレートするテストで使用できます。デフォルトでは、このオプションは無効になっており、JVMヒープ領域がいっぱいになると、すべてのページがコミットされます。 +.RE +.PP +\-XX:+CMSClassUnloadingEnabled +.RS 4 +並行マークスイープ(CMS)ガベージ・コレクタを使用する場合に、アンロードするクラスを有効にします。このオプションはデフォルトで有効になっています。CMSガベージ・コレクタのクラス・アンロードを無効にするには、\fB\-XX:\-CMSClassUnloadingEnabled\fRを指定します。 +.RE +.PP +\-XX:CMSExpAvgFactor=\fIpercent\fR +.RS 4 +並行コレクション統計の指数平均を計算する際に、現在のサンプルを重み付けするために使用される時間の割合(0から100まで)を設定します。デフォルトでは、指数平均係数は25%に設定されています。次の例では、係数を15%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSExpAvgFactor=15\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CMSInitiatingOccupancyFraction=\fIpercent\fR +.RS 4 +CMS収集サイクルを開始する古い世代の占有率(0から100まで)を設定します。デフォルト値は\-1に設定されています。負の値(デフォルトを含む)は、\fB\-XX:CMSTriggerRatio\fRが開始占有率の値を定義するために使用されることを意味します。 +.sp +次の例では、占有率を20%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSInitiatingOccupancyFraction=20\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+CMSScavengeBeforeRemark +.RS 4 +CMSコメント・ステップの前にスカベンジの試行を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:CMSTriggerRatio=\fIpercent\fR +.RS 4 +CMS収集サイクルが開始する前に割り当てられる\fB\-XX:MinHeapFreeRatio\fRによって指定される値の割合(0から100まで)を設定します。デフォルト値は80%に設定されています。 +.sp +次の例では、占有率を75%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSTriggerRatio=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:ConcGCThreads=\fIthreads\fR +.RS 4 +並行GCに使用されるスレッドの数を設定します。デフォルト値は、JVMに使用できるCPUの数によって異なります。 +.sp +たとえば、並行GCのスレッド数を2に設定するには、次のオプションを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ConcGCThreads=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+DisableExplicitGC +.RS 4 +\fBSystem\&.gc()\fRの呼出しの処理を無効にするオプションを有効にします。このオプションはデフォルトで無効になっており、これは\fBSystem\&.gc()\fRへの呼出しが処理されることを意味します。\fBSystem\&.gc()\fRの呼出しの処理が無効になっている場合、JVMは必要に応じてGCを実行します。 +.RE +.PP +\-XX:+ExplicitGCInvokesConcurrent +.RS 4 +\fBSystem\&.gc()\fRリクエストを使用することによって、並行GCの呼出しを有効にします。このオプションはデフォルトで無効になっており、\fB\-XX:+UseConcMarkSweepGC\fRオプションとともに使用する場合のみ、有効にすることができます。 +.RE +.PP +\-XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses +.RS 4 +\fBSystem\&.gc()\fRリクエストを使用し、並行GCサイクル中にクラスをアンロードすることによって、並行GCの呼出しを有効にします。このオプションはデフォルトで無効になっており、\fB\-XX:+UseConcMarkSweepGC\fRオプションとともに使用する場合のみ、有効にすることができます。 +.RE +.PP +\-XX:G1HeapRegionSize=\fIsize\fR +.RS 4 +ガベージファースト(G1)コレクタを使用する際にJavaヒープを細分化するリージョンのサイズを設定します。値には、1MBから32MBまでを指定できます。デフォルトのリージョン・サイズは、ヒープ・サイズに基づいて人間工学的に決定されます。 +.sp +次の例では、細分化されたサイズを16MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:G1HeapRegionSize=16m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+G1PrintHeapRegions +.RS 4 +割り当てられたリージョンおよびG1コレクタによって再要求されたものに関する情報の印刷を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:G1ReservePercent=\fIpercent\fR +.RS 4 +G1コレクタの昇格が失敗する可能性を減らすためのfalseの上限として予約されたヒープの割合(0から50まで)を設定します。デフォルトでは、このオプションは10%に設定されています。 +.sp +次の例では、予約されたヒープを20%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:G1ReservePercent=20\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:InitialHeapSize=\fIsize\fR +.RS 4 +メモリー割当てプールの初期サイズ(バイト単位)を設定します。指定する値は、0、または1MBより大きい1024の倍数のいずれかにする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は、実行時にシステム構成に基づいて選択されます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.htmlの\fIJava SE HotSpot仮想マシンのガベージ・コレクション・チューニング・ガイド\fRのエルゴノミクスに関する項を参照してください。 +.sp +次の例では、割り当てられたメモリーのサイズを様々な単位を使用して6MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialHeapSize=6291456\fR +\fB\-XX:InitialHeapSize=6144k\fR +\fB\-XX:InitialHeapSize=6m\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを0に設定した場合、初期サイズは、古い世代と若い世代に割り当てられたサイズの合計として設定されます。若い世代のヒープのサイズは、\fB\-XX:NewSize\fRオプションを使用して設定できます。 +.RE +.PP +\-XX:InitialSurvivorRatio=\fIratio\fR +.RS 4 +スループット・ガベージ・コレクタが使用するサバイバ領域の初期比を設定します(\fB\-XX:+UseParallelGC\fRおよび/または\fB\-XX:+UseParallelOldGC\fRオプションによって有効になります)。\fB\-XX:+UseParallelGC\fRオプションおよび\fB\-XX:+UseParallelOldGC\fRオプションを使用することによって、スループット・ガベージ・コレクタで適応サイズ指定をデフォルトで有効にします。初期値から始めて、アプリケーションの動作に従って、サバイバ領域がサイズ変更されます。(\fB\-XX:\-UseAdaptiveSizePolicy\fRオプションを使用して)適応サイズ指定を無効にした場合、\fB\-XX:SurvivorRatio\fRオプションを使用して、アプリケーションの実行全体のサバイバ領域のサイズを設定する必要があります。 +.sp +次の式を使用して、若い世代のサイズ(Y)およびサバイバ領域の初期比(R)に基づいて、サバイバ領域の初期サイズ(S)を計算できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBS=Y/(R+2)\fR + +.fi +.if n \{\ +.RE +.\} +等式内の2は、2つのサバイバ領域を示します。サバイバ領域の初期比に指定する値を大きくすると、サバイバ領域の初期サイズは小さくなります。 +.sp +デフォルトでは、サバイバ領域の初期比は8に設定されています。若い世代の領域サイズのデフォルト値(2MB)を使用した場合、サバイバ領域の初期サイズは0\&.2MBになります。 +.sp +次の例では、サバイバ領域の初期比を4に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialSurvivorRatio=4\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:InitiatingHeapOccupancyPercent=\fIpercent\fR +.RS 4 +並行GCサイクルを開始するヒープ占有率(0から100まで)を設定します。これは、1つの世代のみ(たとえばG1ガベージ・コレクタなど)ではなく、ヒープ全体の占有に基づいて並行GCサイクルをトリガーするガベージ・コレクタによって使用されます。 +.sp +デフォルトでは、開始値は45%に設定されています。値0は、GCサイクルが停止しないことを意味します。次の例では、開始ヒープ占有率を75%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitiatingHeapOccupancyPercent=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxGCPauseMillis=\fItime\fR +.RS 4 +最大GC休止時間(ミリ秒単位)のターゲットを設定します。これはソフト・ゴールのため、JVMは実現のために最善の努力をします。デフォルトでは、休止時間の最大値はありません。 +.sp +次の例では、最大ターゲット休止時間を500ミリ秒に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxGCPauseMillis=500\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxHeapSize=\fIsize\fR +.RS 4 +メモリー割当てプールの最大サイズ(バイト単位)を設定します。指定する値は、2MBより大きい1024の倍数にする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は、実行時にシステム構成に基づいて選択されます。サーバー・デプロイメントでは、\fB\-XX:InitialHeapSize\fRおよび\fB\-XX:MaxHeapSize\fRは通常同じ値に設定されます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.htmlの\fIJava SE HotSpot仮想マシンのガベージ・コレクション・チューニング・ガイド\fRのエルゴノミクスに関する項を参照してください。 +.sp +次の例では、割り当てられたメモリーの許可される最大サイズを様々な単位を使用して80MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxHeapSize=83886080\fR +\fB\-XX:MaxHeapSize=81920k\fR +\fB\-XX:MaxHeapSize=80m\fR + +.fi +.if n \{\ +.RE +.\} +Oracle Solaris 7およびOracle Solaris 8 SPARCプラットフォームの場合のこの値の上限は、およそ4,000MBからオーバーヘッドの量を引いたものです。Oracle Solaris 2\&.6およびx86プラットフォームの場合の上限は、およそ2,000MBからオーバーヘッドの量を引いたものです。Linuxプラットフォームの場合の上限は、およそ2,000MBからオーバーヘッドの量を引いたものです。 +.sp +\fB\-XX:MaxHeapSize\fRオプションは\fB\-Xmx\fRと同等です。 +.RE +.PP +\-XX:MaxHeapFreeRatio=\fIpercent\fR +.RS 4 +GCイベント後の空きヒープ領域の許可されている最大の割合(0から100まで)を設定します。空きヒープ領域がこの値を超えて拡大した場合、そのヒープは縮小します。デフォルトでは、この値は70%に設定されています。 +.sp +次の例では、空きヒープの最大比率を75%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxHeapFreeRatio=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxMetaspaceSize=\fIsize\fR +.RS 4 +クラス・メタデータに割り当てることができるネイティブ・メモリーの最大量を設定します。デフォルトでは、このサイズは制限されていません。アプリケーションのメタデータの量は、アプリケーション自体、他の実行中アプリケーション、およびシステムで使用可能なメモリーの量によって異なります。 +.sp +次の例では、クラス・メタデータの最大サイズを256MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxMetaspaceSize=256m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxNewSize=\fIsize\fR +.RS 4 +若い世代(ナーサリ)のヒープの最大サイズ(バイト単位)を設定します。デフォルト値は人間工学的に設定されます。 +.RE +.PP +\-XX:MaxTenuringThreshold=\fIthreshold\fR +.RS 4 +適応GCサイズ指定で使用する最大殿堂入りしきい値を設定します。最大値は15です。デフォルト値は、パラレル(スループット)コレクタの場合は15、CMSコレクタの場合は6です。 +.sp +次の例では、最大殿堂入りしきい値を10に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxTenuringThreshold=10\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MetaspaceSize=\fIsize\fR +.RS 4 +最初に超えたときにガベージ・コレクションをトリガーする、割り当てられたクラス・メタデータ領域のサイズを設定します。このガベージ・コレクションのしきい値は、使用されるメタデータの量によって増加または減少します。デフォルトのサイズはプラットフォームによって異なります。 +.RE +.PP +\-XX:MinHeapFreeRatio=\fIpercent\fR +.RS 4 +GCイベント後の空きヒープ領域の許可されている最小の割合(0から100まで)を設定します。空きヒープ領域がこの値を下回った場合、そのヒープは拡大します。デフォルトでは、この値は40%に設定されています。 +.sp +次の例では、空きヒープの最小比率を25%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MinHeapFreeRatio=25\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NewRatio=\fIratio\fR +.RS 4 +若い世代のサイズと古い世代のサイズとの比率を設定します。デフォルトでは、このオプションは2に設定されています。次の例では、若い/古いの比率を1に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:NewRatio=1\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NewSize=\fIsize\fR +.RS 4 +若い世代(ナーサリ)のヒープの初期サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。 +.sp +ヒープの若い世代リージョンは新しいオブジェクトに使用されます。GCは、他のリージョンよりこのリージョンで、より頻繁に実行されます。若い世代のサイズが小さすぎる場合、多数のマイナーGCが実行されます。サイズが大きすぎる場合、フルGCのみが実行されますが、完了までに時間がかかることがあります。若い世代のサイズは、全体のヒープ・サイズの半分から4分の1の間にしておくことをお薦めします。 +.sp +次の例では、若い世代の初期サイズを様々な単位を使用して256MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:NewSize=256m\fR +\fB\-XX:NewSize=262144k\fR +\fB\-XX:NewSize=268435456\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-XX:NewSize\fRオプションは\fB\-Xmn\fRと同等です。 +.RE +.PP +\-XX:ParallelGCThreads=\fIthreads\fR +.RS 4 +若い世代と古い世代でパラレル・ガベージ・コレクションに使用するスレッドの数を設定します。デフォルト値は、JVMに使用できるCPUの数によって異なります。 +.sp +たとえば、パラレルGCのスレッド数を2に設定するには、次のオプションを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ParallelGCThreads=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+ParallelRefProcEnabled +.RS 4 +パラレル参照処理を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintAdaptiveSizePolicy +.RS 4 +適応世代サイズ指定に関する情報の出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGC +.RS 4 +GCごとのメッセージの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCApplicationConcurrentTime +.RS 4 +最後の休止(たとえばGC休止など)以降に経過した時間の出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCApplicationStoppedTime +.RS 4 +休止(たとえばGC休止など)が継続した時間の出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCDateStamps +.RS 4 +GCごとの日付スタンプの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCDetails +.RS 4 +GCごとの詳細メッセージの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCTaskTimeStamps +.RS 4 +個々のGCワーカー・スレッド・タスクごとのタイムスタンプの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCTimeStamps +.RS 4 +GCごとのタイムスタンプの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintStringDeduplicationStatistics +.RS 4 +詳細な重複除外統計を印刷します。デフォルトでは、このオプションは無効です。\fB\-XX:+UseStringDeduplication\fRオプションを参照してください。 +.RE +.PP +\-XX:+PrintTenuringDistribution +.RS 4 +殿堂入り期間情報の出力を有効にします。次に、出力の例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBDesired survivor size 48286924 bytes, new threshold 10 (max 10)\fR +\fB\- age 1: 28992024 bytes, 28992024 total\fR +\fB\- age 2: 1366864 bytes, 30358888 total\fR +\fB\- age 3: 1425912 bytes, 31784800 total\fR +\fB\&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +期間1オブジェクトは、最も若いサバイバです(前のスカベンジの後に作成され、最新のスカベンジで存続し、Eden領域からサバイバ領域に移動しました)。期間2オブジェクトは、2つのスカベンジで存続します(2番目のスカベンジ中に、あるサバイバ領域から次の領域にコピーされました)。このように続きます。 +.sp +前述の例では、28,992,024バイトが1つのスカベンジで存続し、Eden領域からサバイバ領域にコピーされました。1,366,864バイトは期間2オブジェクトなどにより占有されています。各行の3番目の値は、期間n以下のオブジェクトの累積サイズです。 +.sp +デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+ScavengeBeforeFullGC +.RS 4 +それぞれのフルGCの前に若い世代のGCを有効にします。このオプションはデフォルトで有効になっています。フルGCの前に若い世代のスカベンジを行うと、古い世代領域から若い世代領域へのアクセスが可能なオブジェクトの数を減らすことができるため、これを無効に\fIしない\fRことをお薦めします。各フルGCの前に若い世代のGCを無効にするには、\fB\-XX:\-ScavengeBeforeFullGC\fRを指定します。 +.RE +.PP +\-XX:SoftRefLRUPolicyMSPerMB=\fItime\fR +.RS 4 +ソフト・アクセスが可能なオブジェクトが最後に参照されてからヒープ上でアクティブなままになっている時間(ミリ秒単位)を設定します。デフォルト値は、ヒープ内の空きメガバイト当たりで1秒の存続期間です。\fB\-XX:SoftRefLRUPolicyMSPerMB\fRオプションは、現在のヒープ・サイズ(Java HotSpot Client VM用)または最大可能ヒープ・サイズ(Java HotSpot Server VM用)の1メガバイト当たりのミリ秒を表す整数値を受け入れます。この違いは、Client VMは、ヒープを大きくするのではなく、ソフト参照をフラッシュする傾向があるのに対し、Server VMは、ソフト参照をフラッシュするのではなく、ヒープを大きくする傾向があることを意味します。後者の場合、\fB\-Xmx\fRオプションの値は、ソフト参照がどのくらい迅速にガベージ・コレクションされるかに重要な影響を及ぼします。 +.sp +次の例では、値を2\&.5秒に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:SoftRefLRUPolicyMSPerMB=2500\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:StringDeduplicationAgeThreshold=\fIthreshold\fR +.RS 4 +指定した期間に到達しつつある\fBString\fRオブジェクトは、重複除外の候補とみなされます。オブジェクトの期間は、オブジェクトがガベージ・コレクションで存続した回数の測定値です。これは、殿堂入りと呼ばれる場合もあります。\fB\-XX:+PrintTenuringDistribution\fRオプションを参照してください。この期間に到達する前に古いヒープ・リージョンに昇格された\fBString\fRオブジェクトは、常に重複除外の候補とみなされます。このオプションのデフォルト値は\fB3\fRです。\fB\-XX:+UseStringDeduplication\fRオプションを参照してください。 +.RE +.PP +\-XX:SurvivorRatio=\fIratio\fR +.RS 4 +Eden領域のサイズとサバイバ領域のサイズとの比率を設定します。デフォルトでは、このオプションは8に設定されています。次の例では、Eden/サバイバ領域の比率を4に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:SurvivorRatio=4\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:TargetSurvivorRatio=\fIpercent\fR +.RS 4 +若いガベージ・コレクションの後に使用されるサバイバ領域の目的の割合(0から100まで)を設定します。デフォルトでは、このオプションは50%に設定されています。 +.sp +次の例では、ターゲットのサバイバ領域の比率を30%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:TargetSurvivorRatio=30\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:TLABSize=\fIsize\fR +.RS 4 +スレッド・ローカルな割当てバッファ(TLAB)の初期サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。このオプションが0に設定されている場合、JVMでは初期サイズが自動的に選択されます。 +.sp +次の例では、TLABの初期サイズを512KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:TLABSize=512k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+UseAdaptiveSizePolicy +.RS 4 +適応世代サイズ指定の使用を有効にします。このオプションはデフォルトで有効になっています。適応世代サイズ指定を無効にするには、\fB\-XX:\-UseAdaptiveSizePolicy\fRを指定し、メモリー割当てプールのサイズを明示的に設定します(\fB\-XX:SurvivorRatio\fRオプションを参考にしてください)。 +.RE +.PP +\-XX:+UseCMSInitiatingOccupancyOnly +.RS 4 +CMSコレクタの開始のための唯一の基準としての占有値の使用を有効にします。デフォルトでは、このオプションは無効になっており、他の基準が使用されます。 +.RE +.PP +\-XX:+UseConcMarkSweepGC +.RS 4 +古い世代へのCMSガベージ・コレクタの使用を有効にします。アプリケーションの待機時間の要件を、スループット(\fB\-XX:+UseParallelGC\fR)ガベージ・コレクタによって満たすことができない場合、CMSガベージ・コレクタを使用することをお薦めします。G1ガベージ・コレクタ(\fB\-XX:+UseG1GC\fR)は別の代替となります。 +.sp +デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。このオプションが有効な場合、\fB\-XX:+UseParNewGC\fRオプションは自動的に設定され、無効化しない必要がありますが、理由はJDK 8では\fB\-XX:+UseConcMarkSweepGC \-XX:\-UseParNewGC\fRオプションの組合せが非推奨であるためです。 +.RE +.PP +\-XX:+UseG1GC +.RS 4 +ガベージファースト(G1)・ガベージ・コレクタの使用を有効にします。これはサーバー形式のガベージ・コレクタで、大量のRAMを持つマルチプロセッサ・マシンを対象としています。高い確率でGC休止時間の目標を達成し、同時に適切なスループットも維持します。G1コレクタは、GC待機時間の限定された要件(安定した予測可能な0\&.5秒未満の休止時間)を持つ、大きいヒープ(約6GB以上のサイズ)が必要なアプリケーションに推奨されます。 +.sp +デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。 +.RE +.PP +\-XX:+UseGCOverheadLimit +.RS 4 +\fBOutOfMemoryError\fR例外がスローされるまでに、GCでJVMによって要した時間の割合を制限するポリシーの使用を有効にします。デフォルトでは、このオプションは有効になっており、ガベージ・コレクションに合計時間の98%より多く費やされ、ヒープのリカバリが2%未満である場合、パラレルGCによって\fBOutOfMemoryError\fRがスローされます。ヒープが小さい場合、この機能は、アプリケーションが長期間ほとんどまたはまったく進捗なく実行している状態を回避するために使用できます。このオプションを無効にするには、\fB\-XX:\-UseGCOverheadLimit\fRを指定します。 +.RE +.PP +\-XX:+UseNUMA +.RS 4 +アプリケーションで短い待機時間のメモリーの使用を増加させることで、不均一なメモリー・アーキテクチャ(NUMA)を使用したマシン上のアプリケーションのパフォーマンス最適化を有効にします。デフォルトでは、このオプションは無効になっており、NUMAに対する最適化は行われません。このオプションは、パラレル・ガベージ・コレクタ(\fB\-XX:+UseParallelGC\fR)が使用されている場合のみ使用可能です。 +.RE +.PP +\-XX:+UseParallelGC +.RS 4 +複数のプロセッサを利用してアプリケーションのパフォーマンスを向上させる、パラレル・スカベンジ・ガベージ・コレクタ(スループット・コレクタとも呼ばれる)の使用を有効にします。 +.sp +デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。これを有効にした場合、明示的に無効にしないかぎり、\fB\-XX:+UseParallelOldGC\fRオプションが自動的に有効になります。 +.RE +.PP +\-XX:+UseParallelOldGC +.RS 4 +フルGCへのパラレル・ガベージ・コレクタの使用を有効にします。デフォルトでは、このオプションは無効です。これを有効にすると、\fB\-XX:+UseParallelGC\fRオプションが自動的に有効になります。 +.RE +.PP +\-XX:+UseParNewGC +.RS 4 +若い世代でのコレクションへのパラレル・スレッドの使用を有効にします。デフォルトでは、このオプションは無効です。\fB\-XX:+UseConcMarkSweepGC\fRオプションを設定すると、これは自動的に有効になります。JDK 8では、\fB\-XX:+UseConcMarkSweepGC\fRオプションを指定せずに\fB\-XX:+UseParNewGC\fRオプションを使用することは非推奨です。 +.RE +.PP +\-XX:+UseSerialGC +.RS 4 +シリアル・ガベージ・コレクタの使用を有効にします。ガベージ・コレクションから特別な機能を必要としない、小規模で単純なアプリケーションの場合には、これは一般に最適な選択です。デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。 +.RE +.PP +\-XX:+UseSHM +.RS 4 +Linuxでは、JVMで共有メモリーを使用してラージ・ページを設定できるようにします。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+UseStringDeduplication +.RS 4 +文字列の重複除外を有効化します。デフォルトでは、このオプションは無効です。このオプションを使用するには、ガベージファースト(G1)・ガベージ・コレクタを有効にする必要があります。\fB\-XX:+UseG1GC\fRオプションを参照してください。 +.sp +多くの\fBString\fRオブジェクトが同じであるということから、\fIString deduplication\fRにより、Javaヒープ上の\fBString\fRオブジェクトのメモリー・フットプリントが削減されます。各\fBString\fRオブジェクトが独自の文字配列をポイントするのではなく、同一の\fBString\fRオブジェクトは同じ文字配列をポイントし共有できます。 +.RE +.PP +\-XX:+UseTLAB +.RS 4 +若い世代の領域でのスレッド・ローカルな割当てブロック(TLAB)の使用を有効にします。このオプションはデフォルトで有効になっています。TLABの使用を無効にするには、\fB\-XX:\-UseTLAB\fRを指定します。 +.RE +.SS "非推奨で削除されたオプション" +.PP +これらのオプションは、以前のリリースには含まれていましたが、以降は不要とみなされています。 +.PP +\-Xincgc +.RS 4 +インクリメンタル・ガベージ・コレクションを有効にします。このオプションはJDK 8では非推奨で、それに代わるものはありません。 +.RE +.PP +\-Xrun\fIlibname\fR +.RS 4 +指定したデバッグ/プロファイリングのライブラリをロードします。このオプションは、\fB\-agentlib\fRオプションに取って代わられました。 +.RE +.PP +\-XX:CMSIncrementalDutyCycle=\fIpercent\fR +.RS 4 +並行コレクタの実行が許可されているマイナー・コレクション間の時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:CMSIncrementalDutyCycleMin=\fIpercent\fR +.RS 4 +\fB\-XX:+CMSIncrementalPacing\fRが有効な場合にデューティ・サイクルの下限であるマイナー・コレクション間の時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:+CMSIncrementalMode +.RS 4 +CMSコレクタの増分モードを有効にします。\fBCMSIncremental\fRで始まるその他のオプションとともに、このオプションはJDK 8では非推奨となり、それに代わるものはありません +.RE +.PP +\-XX:CMSIncrementalOffset=\fIpercent\fR +.RS 4 +増分モードのデューティ・サイクルをマイナー・コレクション間で期間内に右に移動する時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:+CMSIncrementalPacing +.RS 4 +JVMの実行中に収集された統計に基づいて、増分モードのデューティ・サイクルの自動調整を有効にします。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:CMSIncrementalSafetyFactor=\fIpercent\fR +.RS 4 +デューティ・サイクルを計算する際に、保守を追加するために使用される時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:CMSInitiatingPermOccupancyFraction=\fIpercent\fR +.RS 4 +GCを開始する永久世代占有率(0から100まで)を設定します。このオプションはJDK 8では非推奨で、それに代わるものはありません。 +.RE +.PP +\-XX:MaxPermSize=\fIsize\fR +.RS 4 +永久世代領域の最大サイズ(バイト単位)を設定します。このオプションは、JDK 8で非推奨になり、\fB\-XX:MaxMetaspaceSize\fRオプションに取って代わられました。 +.RE +.PP +\-XX:PermSize=\fIsize\fR +.RS 4 +超えた場合にはガベージ・コレクションをトリガーする、永久世代に割り当てられた領域(バイト単位)を設定します。このオプションは、JDK 8で非推奨になり、\fB\-XX:MetaspaceSize\fRオプションに取って代わられました。 +.RE +.PP +\-XX:+UseSplitVerifier +.RS 4 +検証プロセスの分割を有効にします。デフォルトでは、このオプションは以前のリリースでは有効になっており、検証は、タイプ参照(コンパイラによって実行)と、タイプ・チェック(JVMランタイムによって実行)の2つのフェーズに分割されていました。このオプションはJDK 8で非推奨となり、検証はデフォルトで分割され、無効にする方法はありません。 +.RE +.PP +\-XX:+UseStringCache +.RS 4 +一般に割り当てられた文字列のキャッシングを有効にします。このオプションはJDK 8から削除され、それに代わるものはありません。 +.RE +.SH "パフォーマンス・チューニングの例" +.PP +次の例では、スループットの最適化またはレスポンス時間の短縮化のいずれかを行うための、試験的なチューニング・フラグの使用方法を示します。 +.PP +\fB例 1 \fRスループットを向上するためのチューニング +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-d64 \-server \-XX:+AggressiveOpts \-XX:+UseLargePages \-Xmn10g \-Xms26g \-Xmx26g\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRレスポンス時間を速くするためのチューニング +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-d64 \-XX:+UseG1GC \-Xms26g Xmx26g \-XX:MaxGCPauseMillis=500 \-XX:+PrintGCTimeStamp\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "ラージ・ページ" +.PP +ヒュージ・ページとも呼ばれるラージ・ページは、標準のメモリー・ページ・サイズ(プロセッサおよびオペレーティング・システムによって異なります)よりはるかに大きいメモリー・ページです。ラージ・ページは、プロセッサのTranslation\-Lookaside Bufferを最適化します。 +.PP +Translation\-Lookaside Buffer (TLB)は、最近使用された仮想から物理へのアドレス変換を保持するページ変換キャッシュです。TLBは、少ないシステム・リソースです。プロセッサが複数のメモリー・アクセスが必要な場合のある階層ページ表から読み取る必要があるため、TLBミスは負荷がかかる可能性があります。大きいメモリー・ページ・サイズを使用して、単一のTLBエントリで大きいメモリー範囲を表すことができます。TLB不足が少なくなり、メモリー集約型のアプリケーションのパフォーマンスが向上する可能性があります。 +.PP +ただし、ラージ・ページのページ・メモリーは、システムのパフォーマンスに悪影響を与える場合があります。たとえば、大量のメモリーがアプリケーションで確保される場合、通常メモリー不足や他のアプリケーションの過剰なページングが発生し、システム全体が遅くなる可能性があります。また、長時間稼働しているシステムは、過剰な断片化が発生する可能性があります。これにより、十分な大きさのページ・メモリーを予約できない可能性があります。これが発生した場合、OSまたはJVMのいずれかが通常のページの使用に戻ります。 +.SS "ラージ・ページのサポート" +.PP +SolarisおよびLinuxは、ラージ・ページをサポートします。 +.sp +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBSolaris\fR +.RS 4 +.PP +Solaris 9以上には、Multiple Page Size Support(MPSS)が含まれています。追加の構成は必要ありません。http://www\&.oracle\&.com/technetwork/server\-storage/solaris10/overview/solaris9\-features\-scalability\-135663\&.htmlを参照してください。 +.RE +.sp +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBLinux\fR +.RS 4 +.PP +2\&.6カーネルは、ラージ・ページをサポートします。一部のベンダーは、2\&.4ベースのリリースのコードをバックポートしています。システムがラージ・ページ・メモリーをサポートしているかどうかを確認するには、次を試行してください: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# cat /proc/meminfo | grep Huge\fR +\fBHugePages_Total: 0\fR +\fBHugePages_Free: 0\fR +\fBHugepagesize: 2048 kB\fR + +.fi +.if n \{\ +.RE +.\} +.PP +出力に3つの"Huge"変数が示されている場合、システムはラージ・ページ・メモリーをサポートしていますが、構成する必要があります。コマンドが何も出力しない場合、システムはラージ・ページをサポートしていません。ラージ・ページ・メモリーを使用するシステムを構成するには、\fBroot\fRとしてログインして、次の手順を実行してください: +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +オプション\fB\-XX:+UseSHM\fR(\fB\-XX:+UseHugeTLBFS\fRのかわり)を使用する場合、\fBSHMMAX\fR値を増やしてください。Javaヒープ・サイズより大きくする必要があります。4GB以下の物理RAMを使用したシステムで、次によりすべてのメモリーが共有可能になります: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# echo 4294967295 > /proc/sys/kernel/shmmax\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +オプション\fB\-XX:+UseSHM\fRまたは\fB\-XX:+UseHugeTLBFS\fRを使用する場合、ラージ・ページの数を指定してください。次の例では、4GBシステムの3GBがラージ・ページに予約されます(2048KBのラージ・ページ・サイズを仮定する場合、3GB = 3 * 1024MB = 3072MB = 3072 * 1024KB = 3145728KB and 3145728KB / 2048KB = 1536): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# echo 1536 > /proc/sys/vm/nr_hugepages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fB注記\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +注意 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +システムを再起動した後に\fB/proc\fRに含まれる値がリセットされるので注意してください。そのため、初期化スクリプト(\fBrc\&.local\fRや\fBsysctl\&.conf\fRなど)で設定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OSカーネル・パラメータ\fB/proc/sys/kernel/shmmax\fRまたは\fB/proc/sys/vm/nr_hugepages\fRを構成(またはサイズ変更)する場合、JavaプロセスがJavaヒープ以外の領域に対してラージ・ページを割り当てることがあります。これらの手順を使用して、次の領域に対してラージ・ページを割り当てることができます: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javaヒープ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Permanent世代 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コード・キャッシュ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パラレルGCのマーキング・ビットマップ・データ構造 +.RE +.sp +その結果、Javaヒープのサイズに\fBnr_hugepages\fRパラメータを構成すると、領域のサイズが非常に大きいためにJVMがPermanent世代およびラージ・ページのコード・キャッシュ領域の割当てに失敗する場合があります。 +.RE +T} +.TE +.sp 1 +.sp .5v +.RE +.RE +.SH "終了ステータス" +.PP +通常、次の終了値が起動ツールから返されるのは、起動元が不正な引数で呼び出されたか、深刻なエラーが発生したか、あるいはJVMにより例外がスローされた場合です。ただし、Javaアプリケーションは、API呼出し\fBSystem\&.exit(exitValue)\fRを使用して任意の値を返すことを選択することもできます。値は次のとおりです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB0\fR: 正常終了 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB>0\fR: エラー発生 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javac.1 b/jdk-1.8.0.281/man/ja/man1/javac.1 new file mode 100755 index 0000000..8b2a0b6 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javac.1 @@ -0,0 +1,1557 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javac +.\" Language: Japanese +.\" Date: 2015年3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javac" "1" "2015年3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javac \- Javaクラスおよびインタフェースの定義を読み取り、バイトコードおよびクラス・ファイルにコンパイルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac\fR [ \fIoptions\fR ] [ \fIsourcefiles\fR ] [ \fIclasses\fR] [ \fI@argfiles\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +引数を指定する順序は任意です。 +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIsourcefiles\fR +.RS 4 +コンパイルされる1つ以上のソース・ファイル(\fBMyClass\&.java\fRなど)。 +.RE +.PP +\fIclasses\fR +.RS 4 +注釈の処理対象となる1つ以上のクラス(\fBMyPackage\&.MyClass\fRなど)。 +.RE +.PP +\fI@argfiles\fR +.RS 4 +オプションとソース・ファイルを一覧表示する1つ以上のファイル。このファイルの中では\fB\-J\fRオプションは指定できません。コマンド行引数ファイルを参照してください。 +.RE +.SH "説明" +.PP +\fBjavac\fRコマンドは、Javaプログラミング言語で記述されたクラスとインタフェースの定義を読み取り、バイトコードのクラス・ファイルにコンパイルします。\fBjavac\fRコマンドでは、Javaソース・ファイルおよびクラス内の注釈の処理もできます。 +.PP +ソース・コードのファイル名を\fBjavac\fRに渡すには、2つの方法があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ソース・ファイルの数が少ない場合は、ファイル名をコマンドラインで指定します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ソース・ファイルの数が多い場合は、ファイル内のファイル名を空白または改行で区切って指定します。\fBjavac\fRコマンドで、リスト・ファイル名の先頭にアットマーク(@)を使用します。 +.RE +.PP +ソース・コードのファイル名は\&.java拡張子を、クラスのファイル名は\&.class拡張子を持っている必要があります。また、ソース・ファイルとクラス・ファイルのどちらも、該当するクラスに対応するルート名を持っている必要があります。たとえば、\fBMyClass\fRという名前のクラスは、\fBMyClass\&.java\fRという名前のソース・ファイルに記述されます。このソース・ファイルは、\fBMyClass\&.class\fRという名前のバイトコード・クラス・ファイルにコンパイルされます。 +.PP +内部クラスが定義されていると、追加のクラス・ファイルが生成されます。これらのクラス・ファイルの名前は、\fBMyClass$MyInnerClass\&.class\fRのように、内部クラス名と外部クラス名を組み合せたものになります。 +.PP +ソース・ファイルは、パッケージ・ツリーを反映したディレクトリ・ツリーに配置します。たとえば、すべてのソース・ファイルが\fB/workspace\fRにある場合、\fBcom\&.mysoft\&.mypack\&.MyClass\fRのソース・コードを、\fB/workspace/com/mysoft/mypack/MyClass\&.java\fRに格納します。 +.PP +デフォルトでは、コンパイラは、各クラス・ファイルを対応するソース・ファイルと同じディレクトリに格納します。\fB\-d\fRオプションを使用して、別の出力先ディレクトリを指定できます。 +.SH "オプション" +.PP +コンパイラには、現在の開発環境でサポートされる標準オプションのセットがあります。これ以外の非標準オプションは、現在の仮想マシンおよびコンパイラの実装に固有のオプションで、将来、変更される可能性があります。非標準オプションは、\fB\-X\fRオプションで始まります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クロスコンパイル・オプションも参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非標準オプションも参照してください +.RE +.SS "標準オプション" +.PP +\-A\fIkey\fR[\fI=value\fR] +.RS 4 +注釈プロセッサに渡すオプションを指定します。これらのオプションは、\fBjavac\fRが直接解釈するのではなく、それぞれのプロセッサで使用できるようになります。\fBkey\fRの値は、1つまたは複数の識別子をドット(\&.)で区切る必要があります。 +.RE +.PP +\-cp \fIpath\fR or \-classpath \fIpath\fR +.RS 4 +ユーザー・クラス・ファイル、および(オプションで)注釈プロセッサとソース・ファイルを検索する場所を指定します。このクラス・パスは\fBCLASSPATH\fR環境変数のユーザー・クラス・パスをオーバーライドします。\fBCLASSPATH\fR、\fB\-cp\fR、\fB\-classpath\fRのいずれも指定されていない場合、ユーザーの\fIクラス・パス\fRは、現在のディレクトリになります。クラス・パスの設定 を参照してください。 +.sp +\fB\-sourcepath\fRオプションが指定されていない場合、ソース・ファイルもユーザー・クラス・パスから検索されます。 +.sp +\fB\-processorpath\fRオプションが指定されていない場合、注釈プロセッサもクラス・パスから検索されます。 +.RE +.PP +\-Djava\&.ext\&.dirs=\fIdirectories\fR +.RS 4 +インストール済拡張機能の位置をオーバーライドします。 +.RE +.PP +\-Djava\&.endorsed\&.dirs=\fIdirectories\fR +.RS 4 +承認された標準パスの位置をオーバーライドします。 +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +クラス・ファイルの出力先ディレクトリを設定します。そのディレクトリは\fBjavac\fRでは作成されないため、すでに存在している必要があります。クラスがパッケージの一部である場合、\fBjavac\fRは、パッケージ名を反映したサブディレクトリ内にクラス・ファイルを格納し、必要に応じてディレクトリを作成します。 +.sp +\fB\-d\fR +\fB/home/myclasses\fRと指定し、クラスの名前が\fBcom\&.mypackage\&.MyClass\fRである場合、クラス・ファイルは\fB/home/myclasses/com/mypackage/MyClass\&.class\fRになります。 +.sp +\fI\-d\fRオプションが指定されなかった場合、\fBjavac\fRは、各クラス・ファイルを、その生成元となるソース・ファイルと同じディレクトリ内に格納します。 +.sp +\fB注意:\fR +\fI\-d\fRオプションによって指定されたディレクトリは、ユーザー・クラス・パスに自動的に追加されません。 +.RE +.PP +\-deprecation +.RS 4 +非推奨のメンバーまたはクラスが使用またはオーバーライドされるたびに、説明を表示します。\fB\-deprecation\fRオプションが指定されていない場合、\fBjavac\fRは、非推奨のメンバーまたはクラスを使用またはオーバーライドしているソース・ファイルのサマリーを表示します。\fB\-deprecation\fRオプションは、\fB\-Xlint:deprecation\fRの省略表記です。 +.RE +.PP +\-encoding \fIencoding\fR +.RS 4 +ソース・ファイルのエンコーディング名(EUC\-JPやUTF\-8など)を設定します。\fB\-encoding\fRオプションが指定されていない場合は、プラットフォームのデフォルト・コンバータが使用されます。 +.RE +.PP +\-endorseddirs \fIdirectories\fR +.RS 4 +承認された標準パスの位置をオーバーライドします。 +.RE +.PP +\-extdirs \fIdirectories\fR +.RS 4 +\fBext\fRディレクトリの位置をオーバーライドします。directories変数には、コロンで区切ったディレクトリのリストを指定します。指定したディレクトリ内の各JARファイルから、クラス・ファイルが検索されます。検出されたすべてのJARファイルは、クラス・パスの一部になります。 +.sp +クロスコンパイル(異なるJavaプラットフォームに実装されたブートストラップ・クラスや拡張機能クラスに対してコンパイルを行う)を実行する場合、このオプションには拡張機能クラスを含むディレクトリを指定します。詳細はクロスコンパイル・オプションを参照してください。 +.RE +.PP +\-g +.RS 4 +ローカル変数を含むすべてのデバッグ情報を生成します。デフォルトでは、行番号およびソース・ファイル情報のみが生成されます。 +.RE +.PP +\-g:none +.RS 4 +デバッグ情報を生成しません。 +.RE +.PP +\-g:[\fIkeyword list\fR] +.RS 4 +カンマで区切られたキーワード・リストにより指定された、特定の種類のデバッグ情報のみを生成します。次のキーワードが有効です。 +.PP +source +.RS 4 +ソース・ファイルのデバッグ情報。 +.RE +.PP +lines +.RS 4 +行番号のデバッグ情報。 +.RE +.PP +vars +.RS 4 +ローカル変数のデバッグ情報。 +.RE +.RE +.PP +\-help +.RS 4 +標準オプションの概要を出力します。 +.RE +.PP +\-implicit:[\fIclass, none\fR] +.RS 4 +暗黙的にロードされたソース・ファイルに対するクラス・ファイルの生成を制御します。クラス・ファイルを自動生成するには、\fB\-implicit:class\fRを使用します。クラス・ファイルの生成を抑制するには、\fB\-implicit:none\fRを使用します。このオプションが指定されなかった場合のデフォルト動作は、クラス・ファイルの自動生成になります。その場合、そのようなクラス・ファイルが生成された時に注釈処理も実行されると、コンパイラから警告が発行されます。\fB\-implicit\fRオプションが明示的に設定された場合、警告は発行されません。型の検索を参照してください。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machine (JVM)に\fBoption\fRを渡します。optionには、Java起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.sp +\fB注意:\fR +\fICLASSPATH\fR、\fB\-classpath\fR、\fB\-bootclasspath\fRおよび\fB\-extdirs\fRオプションは、\fBjavac\fRの実行に使用されるクラスを指定しません。これらのオプションおよび変数を使用してコンパイラの実装をカスタマイズしようとすると、リスクが高く、多くの場合、必要な処理が実行されません。コンパイラの実装をカスタマイズする必要がある場合、\fB\-J\fRオプションを使用して、基礎となるJava起動ツールにオプションを渡します。 +.RE +.PP +\-nowarn +.RS 4 +警告メッセージを無効にします。このオプションは、\fB\-Xlint:none\fRオプションと同じように動作します。 +.RE +.PP +\-parameters +.RS 4 +リフレクションAPIのメソッド\fBjava\&.lang\&.reflect\&.Executable\&.getParameters\fRが取得できるように、生成されるクラス・ファイル内のコンストラクタとメソッドの仮パラメータ名を格納します。 +.RE +.PP +\-proc: [\fInone\fR, \fIonly\fR] +.RS 4 +注釈処理およびコンパイルを実行するかを制御します。\fB\-proc:none\fRは、注釈処理なしでコンパイルが実行されることを意味します。\fB\-proc:only\fRは、注釈処理のみが実行され、後続のコンパイルはまったく実行されないことを意味します。 +.RE +.PP +\-processor \fIclass1\fR [,\fIclass2\fR,\fIclass3\fR\&.\&.\&.] +.RS 4 +実行する注釈プロセッサの名前。これを指定した場合、デフォルトの検索処理は省略されます。 +.RE +.PP +\-processorpath \fIpath\fR +.RS 4 +注釈プロセッサを検索する場所を指定します。このオプションが使用されない場合、クラス・パスのプロセッサが検索されます。 +.RE +.PP +\-s \fIdir\fR +.RS 4 +生成されたソース・ファイルの格納先となるディレクトリを指定します。そのディレクトリは\fBjavac\fRでは作成されないため、すでに存在している必要があります。クラスがパッケージの一部である場合、コンパイラは、パッケージ名を反映したサブディレクトリ内にソース・ファイルを格納し、必要に応じてディレクトリを作成します。 +.sp +\fB\-s /home/mysrc\fRと指定し、クラスの名前が\fBcom\&.mypackage\&.MyClass\fRである場合、ソース・ファイルは\fB/home/mysrc/com/mypackage/MyClass\&.java\fRに格納されます。 +.RE +.PP +\-source \fIrelease\fR +.RS 4 +受け付けるソース・コードのバージョンを指定します。\fBrelease\fRには次の値を指定できます。 +.PP +1\&.3 +.RS 4 +このコンパイラでは、Java SE 1\&.3以降に導入されたアサーション、総称または他の言語機能をサポートしません。 +.RE +.PP +1\&.4 +.RS 4 +Java SE 1\&.4で導入された、アサーションを含むコードを受け付けます。 +.RE +.PP +1\&.5 +.RS 4 +Java SE 5で導入された総称および他の言語機能を含んだコードを受け付けます。 +.RE +.PP +5 +.RS 4 +1\&.5と同義です。 +.RE +.PP +1\&.6 +.RS 4 +Java SE 6では言語に対する変更は導入されませんでした。しかし、ソース・ファイル内のエンコーディング・エラーが、Java Platform, Standard Editionの以前のリリースような警告ではなく、エラーとして報告されるようになりました。 +.RE +.PP +6 +.RS 4 +1\&.6と同義です。 +.RE +.PP +1\&.7 +.RS 4 +Java SE 7で導入された機能を含むコードを受け付けます。 +.RE +.PP +7 +.RS 4 +1\&.7と同義です。 +.RE +.PP +1\&.8 +.RS 4 +これがデフォルト値です。Java SE 8で導入された機能を含むコードを受け付けます。 +.RE +.PP +8 +.RS 4 +1\&.8と同義です。 +.RE +.RE +.PP +\-sourcepath \fIsourcepath\fR +.RS 4 +クラスまたはインタフェースの定義を検索するソース・コード・パスを指定します。ユーザー・クラス・パスと同様に、ソース・パスのエントリは、Oracle Solarisではコロン(:)で、Windowsではセミコロンで区切り、ここには、ディレクトリ、JARアーカイブまたはZIPアーカイブを指定できます。パッケージを使用している場合は、ディレクトリまたはアーカイブ内のローカル・パス名がパッケージ名を反映している必要があります。 +.sp +\fB注意:\fR +ソース・ファイルも見つかった場合、クラス・パスにより見つかったクラスは再コンパイルされる可能性があります。型の検索を参照してください。 +.RE +.PP +\-verbose +.RS 4 +ロードされるクラスおよびコンパイルされるソース・ファイルごとの情報が出力される、詳細出力を使用します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-werror +.RS 4 +警告が発生した場合にコンパイルを終了します。 +.RE +.PP +\-X +.RS 4 +非標準オプションに関する情報を表示して終了します。 +.RE +.SS "クロスコンパイル・オプション" +.PP +デフォルトでは、クラスのコンパイルは、\fBjavac\fRが添付されているプラットフォームのブートストラップ・クラスおよび拡張機能クラスに対して行われます。ただし、\fBjavac\fRは、異なるJavaプラットフォームに実装されたブートストラップ・クラスおよび拡張機能クラスに対してコンパイルを行うクロスコンパイルもサポートしています。クロスコンパイルを行う場合は、\fB\-bootclasspath\fRおよび\fB\-extdirs\fRオプションを使用することが重要です。 +.PP +\-target \fIversion\fR +.RS 4 +仮想マシンの指定されたリリースを対象とするクラス・ファイルを生成します。クラス・ファイルは、指定されたターゲット以降のリリースでは動作しますが、それより前のリリースのJVMでは動作しません。有効なターゲットは、1\&.1、1\&.2、1\&.3、1\&.4、1\&.5 (5も可)、1\&.6 (6も可)、1\&.7 (7も可)および1\&.8 (8も可)です。 +.sp +\fB\-target\fRオプションのデフォルトは、\fB\-source\fRオプションの値によって異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが指定されていない場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.2の場合、\fB\-target\fRオプションの値は1\&.4です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.3の場合、\fB\-target\fRオプションの値は1\&.4です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.5の場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.6の場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.7の場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションの他のすべての値の場合、\fB\-target\fRオプションの値は、\fB\-source\fRオプションの値になります。 +.RE +.RE +.PP +\-bootclasspath \fIbootclasspath\fR +.RS 4 +指定された一連のブート・クラスに対してクロスコンパイルを行います。ユーザー・クラス・パスと同様に、ブート・クラス・パスのエントリはコロン(:)で区切り、ここには、ディレクトリ、JARアーカイブまたはZIPアーカイブを指定できます。 +.RE +.SS "コンパクト・プロファイル・オプション" +.PP +JDK 8以降から、\fBjavac\fRコンパイラはコンパクト・プロファイルをサポートします。コンパクト・プロファイルを使用すると、Javaプラットフォーム全体を必要としないアプリケーションは、デプロイ可能で、小さいフットプリントで実行できます。コンパクト・プロファイル機能は、アプリケーション・ストアからのアプリケーションのダウンロード時間を短縮するのに使用できます。この機能は、JREをバンドルするJavaアプリケーションの、よりコンパクトなデプロイメントに役立ちます。この機能は、小さいデバイスでも役立ちます。 +.PP +サポートされているプロファイル値は、\fBcompact1\fR、\fBcompact2\fRおよび\fBcompact3\fRです。これらは、追加のレイヤーです。大きい番号の各コンパクト・プロファイルには、小さい番号の名前のプロファイル内のすべてのAPIが含まれます。 +.PP +\-profile +.RS 4 +コンパクト・プロファイルを使用する場合、このオプションは、コンパイル時にプロファイル名を指定します。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-profile compact1 Hello\&.java\fR + +.fi +.if n \{\ +.RE +.\} +javacは、指定されたプロファイルにない任意のJava SE APIを使用するソース・コードをコンパイルしません。これは、そのようなソース・コードをコンパイルしようとすることによって生じるエラー・メッセージの例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd jdk1\&.8\&.0/bin\fR +\fB\&./javac \-profile compact1 Paint\&.java\fR +\fBPaint\&.java:5: error: Applet is not available in profile \*(Aqcompact1\*(Aq\fR +\fBimport java\&.applet\&.Applet;\fR + +.fi +.if n \{\ +.RE +.\} +この例では、\fBApplet\fRクラスを使用しないようにソースを変更することによって、エラーを修正できます。\-profileオプションを指定せずにコンパイルすることによって、エラーを修正することもできます。コンパイルは、Java SE APIの完全なセットに対して実行されます。(どのコンパクト・プロファイルにも、\fBApplet\fRクラスは含まれていません。) +.sp +コンパクト・プロファイルを使用してコンパイルするための別の方法として、\fB\-bootclasspath\fRオプションを使用して、プロファイルのイメージを指定する\fBrt\&.jar\fRファイルへのパスを指定します。かわりに\fB\-profile\fRオプションを使用すると、プロファイル・イメージは、コンパイル時にシステム上に存在する必要がありません。これは、クロスコンパイル時に役立ちます。 +.RE +.SS "非標準オプション" +.PP +\-Xbootclasspath/p:\fIpath\fR +.RS 4 +ブートストラップ・クラス・パスに接尾辞を追加します。 +.RE +.PP +\-Xbootclasspath/a:\fIpath\fR +.RS 4 +ブートストラップ・クラス・パスに接頭辞を追加します。 +.RE +.PP +\-Xbootclasspath/:\fIpath\fR +.RS 4 +ブートストラップ・クラス・ファイルの位置をオーバーライドします。 +.RE +.PP +\-Xdoclint:[\-]\fIgroup\fR [\fI/access\fR] +.RS 4 +\fIgroup\fRの値が\fBaccessibility\fR、\fBsyntax\fR、\fBreference\fR、\fBhtml\fRまたは\fBmissing\fRのいずれかである特定のチェック・グループを有効または無効にします。これらのチェック・グループの詳細は、\fBjavadoc\fRコマンドの\fB\-Xdoclint\fRオプションを参照してください。\fB\-Xdoclint\fRオプションは、\fBjavac\fRコマンドではデフォルトで無効になります。 +.sp +変数\fIaccess\fRは、\fB\-Xdoclint\fRオプションがチェックするクラスとメンバーの最小の可視性レベルを指定します。\fBpublic\fR、\fBprotected\fR、\fBpackage\fRおよび\fBprivate\fRの値(可視性の高い順)の1つを持つことができます。たとえば、次のオプションは、(protected、package、publicを含む) protected以上のアクセス・レベルを持つクラスおよびメンバーを(すべてのチェック・グループで)チェックします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xdoclint:all/protected\fR + +.fi +.if n \{\ +.RE +.\} +次のオプションは、package以上のアクセス権(packageおよびpublicを含む)を持つクラスおよびメンバーに対するHTMLエラーをチェックしないことを除き、すべてのアクセス・レベルに対してすべてのチェック・グループを有効にします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xdoclint:all,\-html/package\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-Xdoclint:none +.RS 4 +すべてのチェック・グループを無効にします。 +.RE +.PP +\-Xdoclint:all[\fI/access\fR] +.RS 4 +すべてのチェック・グループを有効にします。 +.RE +.PP +\-Xlint +.RS 4 +推奨されるすべての警告を有効にします。このリリースでは、利用可能なすべての警告を有効にすることをお薦めします。 +.RE +.PP +\-Xlint:all +.RS 4 +推奨されるすべての警告を有効にします。このリリースでは、利用可能なすべての警告を有効にすることをお薦めします。 +.RE +.PP +\-Xlint:none +.RS 4 +すべての警告を無効にします。 +.RE +.PP +\-Xlint:\fIname\fR +.RS 4 +警告名を無効にします。このオプションで無効にできる警告のリストは、\-Xlintオプションを使用した警告の有効化または無効化を参照してください。 +.RE +.PP +\-Xlint:\fI\-name\fR +.RS 4 +警告名を無効にします。このオプションで無効にできる警告のリストを取得するには、\-Xlintオプションを使用した警告の有効化または無効化\-Xlint\fBオプションを使用した\fRを参照してください。 +.RE +.PP +\-Xmaxerrs \fInumber\fR +.RS 4 +印刷するエラーの最大数を設定します。 +.RE +.PP +\-Xmaxwarns \fInumber\fR +.RS 4 +印刷する警告の最大数を設定します。 +.RE +.PP +\-Xstdout \fIfilename\fR +.RS 4 +コンパイラのメッセージを、指定されたファイルに送信します。デフォルトでは、コンパイラのメッセージは\fBSystem\&.err\fRに送られます。 +.RE +.PP +\-Xprefer:[\fInewer,source\fR] +.RS 4 +ある型に対してソース・ファイルとクラス・ファイルの両方が見つかった場合、そのどちらのファイルを読み取るかを指定します。(型の検索を参照してください)。\fB\-Xprefer:newer\fRオプションを使用した場合、ある型に対するソース・ファイルとクラス・ファイルのうち新しい方が読み取られます(デフォルト)。\fB\-Xprefer:source\fRオプションを使用した場合、ソース・ファイルが読み取られます。\fBSOURCE\fRの保存ポリシーを使用して宣言された注釈に任意の注釈プロセッサがアクセスできるようにする場合は、\fB\-Xprefer:source\fRを使用してください。 +.RE +.PP +\-Xpkginfo:[\fIalways\fR,\fIlegacy\fR,\fInonempty\fR] +.RS 4 +javacがpackage\-info\&.javaファイルから\fBpackage\-info\&.class\fRファイルを生成するかどうかを制御します。このオプションで使用可能なmode引数は次のとおりです。 +.PP +always +.RS 4 +すべての\fBpackage\-info\&.java\fRファイルの\fBpackage\-info\&.class\fRファイルを常に生成します。このオプションは、各\fB\&.java\fRファイルに対応する\fB\&.class\fRファイルがあることを確認するAntなどのビルド・システムを使用する場合に役立つことがあります。 +.RE +.PP +legacy +.RS 4 +package\-info\&.javaに注釈が含まれる場合にのみ\fBpackage\-info\&.class\fRファイルを生成します。package\-info\&.javaにコメントのみ含まれる場合に\fBpackage\-info\&.class\fRファイルを生成しません。 +.sp +\fB注意:\fR +\fBpackage\-info\&.class\fRファイルは生成できますが、package\-info\&.javaファイル内のすべての注釈に\fBRetentionPolicy\&.SOURCE\fRがある場合は空になります。 +.RE +.PP +nonempty +.RS 4 +package\-info\&.javaに\fBRetentionPolicy\&.CLASS\fRまたは\fBRetentionPolicy\&.RUNTIME\fRとともに注釈が含まれる場合にのみ\fBpackage\-info\&.class\fRファイルを生成します。 +.RE +.RE +.PP +\-Xprint +.RS 4 +デバッグ目的で指定した型のテキスト表示を出力します。注釈処理もコンパイルも実行されません。出力形式は変更される可能性があります。 +.RE +.PP +\-XprintProcessorInfo +.RS 4 +ある特定のプロセッサが処理を依頼されている注釈に関する情報を出力します。 +.RE +.PP +\-XprintRounds +.RS 4 +初回および後続の注釈処理ラウンドに関する情報を出力します。 +.RE +.SH "-XLINTオプションを使用した警告の有効化または無効化" +.PP +\fB\-Xlint:name\fRオプションを使用して警告\fIname\fRを有効にします。ここで、\fBname\fRは次の警告名のいずれかになります。\fB\-Xlint:\-name:\fRオプションを使用して、警告を無効化できます。 +.PP +cast +.RS 4 +不要で冗長なキャストについて警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBString s = (String) "Hello!"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +classfile +.RS 4 +クラス・ファイルの内容に関連した問題について警告します。 +.RE +.PP +deprecation +.RS 4 +非推奨の項目の使用について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\&.util\&.Date myDate = new java\&.util\&.Date();\fR +\fBint currentDay = myDate\&.getDay();\fR + +.fi +.if n \{\ +.RE +.\} +メソッド\fBjava\&.util\&.Date\&.getDay\fRはJDK 1\&.1以降は推奨されていません。 +.RE +.PP +dep\-ann +.RS 4 +\fB@deprecated\fR +Javadocコメントでドキュメント化されているが、\fB@Deprecated\fR注釈が付いていない項目について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @deprecated As of Java SE 7, replaced by {@link #newMethod()}\fR +\fB */\fR +\fBpublic static void deprecatedMethood() { }\fR +\fBpublic static void newMethod() { }\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +divzero +.RS 4 +定整数0で除算されることについて警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBint divideByZero = 42 / 0;\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +empty +.RS 4 +\fBif \fR文以降が空の文であることについて警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBclass E {\fR +\fB void m() {\fR +\fB if (true) ;\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +fallthrough +.RS 4 +fall\-throughケースのswitchブロックをチェックし、検出されたものに対して警告メッセージを表示します。Fall\-throughケースは、switchブロック内の最後のケースを除くケースです。このコードにはbreak文は含まれません。コードの実行をそのケースから次のケースへ移動します。たとえば、このswitchブロック内のcase 1ラベルに続くコードは、break文で終わっていません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBswitch (x) {\fR +\fBcase 1:\fR +\fB System\&.out\&.println("1");\fR +\fB // No break statement here\&.\fR +\fBcase 2:\fR +\fB System\&.out\&.println("2");\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +このコードのコンパイル時に\fB\-Xlint:fallthrough\fRオプションが使用されていた場合、コンパイラは、問題になっているケースの行番号とともに、caseにfall\-throughする可能性があることを示す警告を発行します。 +.RE +.PP +finally +.RS 4 +正常に完了できない\fBfinally\fR句について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static int m() {\fR +\fB try {\fR +\fB throw new NullPointerException();\fR +\fB } catch (NullPointerException(); {\fR +\fB System\&.err\&.println("Caught NullPointerException\&.");\fR +\fB return 1;\fR +\fB } finally {\fR +\fB return 0;\fR +\fB }\fR +\fB }\fR + +.fi +.if n \{\ +.RE +.\} +この例では、コンパイラは\fBfinally\fRブロックに関する警告を生成します。\fBint\fRメソッドが呼び出されると、値0が返されます。\fBfinally\fRブロックは、\fBtry\fRブロックが終了すると実行されます。この例では、制御が\fBcatch\fRブロックに移された場合、\fBint\fRメソッドは終了します。ただし、\fBfinally\fRブロックは実行される必要があるため、制御がメソッドの外部に移されていても、このブロックは実行されます。 +.RE +.PP +options +.RS 4 +コマンド行オプションの使用に関する問題について警告します。クロスコンパイル・オプションを参照してください。 +.RE +.PP +overrides +.RS 4 +メソッドのオーバーライドに関する問題について警告します。たとえば、次の2つのクラスがあるとします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class ClassWithVarargsMethod {\fR +\fB void varargsMethod(String\&.\&.\&. s) { }\fR +\fB}\fR + +\fBpublic class ClassWithOverridingMethod extends ClassWithVarargsMethod {\fR +\fB @Override\fR +\fB void varargsMethod(String[] s) { }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは、次のような警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [override] varargsMethod(String[]) in ClassWithOverridingMethod \fR +\fBoverrides varargsMethod(String\&.\&.\&.) in ClassWithVarargsMethod; overriding\fR +\fBmethod is missing \*(Aq\&.\&.\&.\*(Aq\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは、\fBvarargs\fRメソッドを検出すると、\fBvarargs\fRの仮パラメータを配列に変換します。メソッド\fBClassWithVarargsMethod\&.varargsMethod\fRでは、コンパイラは\fBvarargs\fRの仮パラメータ\fBString\&.\&.\&. s\fRを仮パラメータ\fBString[] s\fRに変換します。これは、メソッド\fBClassWithOverridingMethod\&.varargsMethod\fRの仮パラメータに対応する配列です。その結果、この例ではコンパイルが行われます。 +.RE +.PP +path +.RS 4 +コマンドラインでの無効なパス要素と存在しないパス・ディレクトリについて警告します(クラス・パス、ソース・パスなどのパス関連)。このような警告を\fB@SuppressWarnings\fR注釈で抑制することはできません。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-Xlint:path \-classpath /nonexistentpath Example\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +processing +.RS 4 +注釈処理に関する問題について警告します。コンパイラがこの警告を生成するのは、注釈を含むクラスがあるときに、使用している注釈プロセッサでそのタイプの例外を処理できない場合です。たとえば、単純な注釈プロセッサを次に示します。 +.sp +\fBソース・ファイルAnnocProc\&.java\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.util\&.*;\fR +\fBimport javax\&.annotation\&.processing\&.*;\fR +\fBimport javax\&.lang\&.model\&.*;\fR +\fBimport\&.javaz\&.lang\&.model\&.element\&.*;\fR + +\fB@SupportedAnnotationTypes("NotAnno")\fR +\fBpublic class AnnoProc extends AbstractProcessor {\fR +\fB public boolean process(Set elems, RoundEnvironment renv){\fR +\fB return true;\fR +\fB }\fR + +\fB public SourceVersion getSupportedSourceVersion() {\fR +\fB return SourceVersion\&.latest();\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +\fBソース・ファイルAnnosWithoutProcessors\&.java\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB@interface Anno { }\fR +\fB \fR +\fB@Anno\fR +\fBclass AnnosWithoutProcessors { }\fR + +.fi +.if n \{\ +.RE +.\} +次のコマンドは、注釈プロセッサ\fBAnnoProc\fRをコンパイルし、この注釈プロセッサをソース・ファイル\fBAnnosWithoutProcessors\&.java\fRに対して実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac AnnoProc\&.java\fR +\fBjavac \-cp \&. \-Xlint:processing \-processor AnnoProc \-proc:only AnnosWithoutProcessors\&.java\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラがソース・ファイル\fBAnnosWithoutProcessors\&.java\fRに対して注釈プロセッサを実行すると、次の警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [processing] No processor claimed any of these annotations: Anno\fR +\fB \fR +.fi +.if n \{\ +.RE +.\} +この問題を解決するために、クラス\fBAnnosWithoutProcessors\fRで定義および使用される注釈の名前を、\fBAnno\fRから\fBNotAnno\fRに変更できます。 +.RE +.PP +rawtypes +.RS 4 +raw型に対する未検査操作について警告します。次の文では、\fBrawtypes\fR警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBvoid countElements(List l) { \&.\&.\&. }\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、\fBrawtypes\fR警告は生成されません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBvoid countElements(List l) { \&.\&.\&. }\fR + +.fi +.if n \{\ +.RE +.\} +\fBList\fRはraw型です。ただし、\fBList\fRは、アンバウンド形式のワイルドカードのパラメータ化された型です。\fBList\fRはパラメータ化されたインタフェースであるため、常にその型引数を指定します。この例では、\fBList\fRの仮引数はアンバウンド形式のワイルドカード(\fB?\fR)を使用してその仮型パラメータとして指定されます。つまり、\fBcountElements\fRメソッドは\fBList\fRインタフェースのどのインスタンス化も受け付けることができます。 +.RE +.PP +Serial +.RS 4 +直列化可能クラスに\fBserialVersionUID\fR定義がないことを警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class PersistentTime implements Serializable\fR +\fB{\fR +\fB private Date time;\fR +\fB \fR +\fB public PersistentTime() {\fR +\fB time = Calendar\&.getInstance()\&.getTime();\fR +\fB }\fR +\fB \fR +\fB public Date getTime() {\fR +\fB return time;\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは次の警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [serial] serializable class PersistentTime has no definition of\fR +\fBserialVersionUID\fR + +.fi +.if n \{\ +.RE +.\} +直列化可能クラスが\fBserialVersionUID\fRという名前のフィールドを明示的に宣言しない場合、直列化ランタイム環境では、「Javaオブジェクト直列化仕様」で説明されているように、クラスの様々な側面に基づいて、クラスの\fBserialVersionUID\fRのデフォルト値を計算します。ただし、すべての直列化可能クラスが\fBserialVersionUID\fR値を明示的に宣言することを強くお薦めします。 これは、\fBserialVersionUID\fR値を計算するデフォルトのプロセスが、コンパイラの実装によって異なる可能性のあるクラスの詳細にきわめて影響を受けやすく、その結果、直列化復元中に予期しない\fBInvalidClassExceptions\fRが発生する可能性があるためです。Javaコンパイラの実装が異なっても\fBserialVersionUID\fR値の一貫性を確保にするには、直列化可能クラスが\fBserialVersionUID\fR値を明示的に宣言する必要があります。 +.RE +.PP +static +.RS 4 +staticの使用に関する問題について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBclass XLintStatic {\fR +\fB static void m1() { }\fR +\fB void m2() { this\&.m1(); }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは次の警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [static] static method should be qualified by type name, \fR +\fBXLintStatic, instead of by an expression\fR + +.fi +.if n \{\ +.RE +.\} +この問題を解決するために、次のように\fBstatic\fRメソッド\fBm1\fRを呼び出すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBXLintStatic\&.m1();\fR + +.fi +.if n \{\ +.RE +.\} +あるいは、\fBstatic\fRキーワードをメソッド\fBm1\fRの宣言から削除することもできます。 +.RE +.PP +try +.RS 4 +try\-with\-resources文を含む、\fBtry\fRブロックの使用に関する問題について警告します。たとえば、\fBtry\fRブロックで宣言されたリソース\fBac\fRが使用されないために、次の文に対して警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtry ( AutoCloseable ac = getResource() ) { // do nothing}\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +unchecked +.RS 4 +Java言語仕様で指定されている未検査変換警告の詳細を示します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBList l = new ArrayList();\fR +\fBList ls = l; // unchecked warning\fR + +.fi +.if n \{\ +.RE +.\} +型の削除中、型\fBArrayList\fRおよび\fBList\fRは、それぞれ\fBArrayList\fRおよび\fBList\fRになります。 +.sp +\fBls\fRコマンドには、パラメータ化された型\fBList\fRが指定されています。\fBl\fRによって参照される\fBList\fRが\fBls\fRに割り当てられた場合、コンパイラは未検査警告を生成します。コンパイル時に、コンパイラおよびJVMは、\fBl\fRが\fBList\fR型を参照するかどうかを判別できません。この場合、\fBl\fRは、\fBList\fR型を参照しません。その結果、ヒープ汚染が発生します。 +.sp +ヒープ汚染状態が発生するのは、\fBList\fRオブジェクト\fBl\fR +(そのstatic型は\fBList\fR)が別の\fBList\fRオブジェクト\fBls\fR +(異なるstatic型\fBList\fRを持つ)に代入される場合です。しかし、コンパイラではこの代入をいまだに許可しています。総称をサポートしないJava SEのリリースとの後方互換性を確保するために、この代入を許可する必要があります。型の削除のため、\fBList\fRおよび\fBList\fRは、両方\fBList\fRになります。その結果、コンパイラはオブジェクト\fBl\fR +(\fBList\fRというraw型を持つ)をオブジェクト\fBls\fRに代入することを許可します。 +.RE +.PP +varargs +.RS 4 +可変引数(\fBvarargs\fR)メソッド、特に非具象化可能引数を含むものの使用が安全でないことを警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class ArrayBuilder {\fR +\fB public static void addToList (List listArg, T\&.\&.\&. elements) {\fR +\fB for (T x : elements) {\fR +\fB listArg\&.add(x);\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +\fB注意:\fR +非具象化可能型は、型情報が実行時に完全に使用不可能な型です。 +.sp +コンパイラは、メソッド\fBArrayBuilder\&.addToList\fRの定義に関する次の警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [varargs] Possible heap pollution from parameterized vararg type T\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは、varargsメソッドを検出すると、\fBvarargs\fRの仮パラメータを配列に変換します。しかし、Javaプログラミング言語では、パラメータ化された型の配列の作成を許可していません。メソッド\fBArrayBuilder\&.addToList\fRでは、コンパイラは\fBvarargs\fRの仮パラメータ\fBT\&.\&.\&.\fR要素を仮パラメータ\fBT[]\fR要素(配列)に変換します。しかし、型消去により、コンパイラは\fBvarargs\fRの仮パラメータを\fBObject[]\fR要素に変換します。その結果、ヒープ汚染が発生する可能性があります。 +.RE +.SH "コマンド行引数ファイル" +.PP +\fBjavac\fRコマンドを短くしたり簡潔にしたりするために、\fBjavac\fRコマンドに対する引数(\fB\-J\fRオプションを除く)を含む1つ以上のファイルを指定することができます。これにより、どのオペレーティング・システム上でも、任意の長さの\fBjavac\fRコマンドを作成できます。 +.PP +引数ファイルには、\fBjavac\fRのオプションとソース・ファイル名を自由に組み合せて記述できます。ファイル内の引数は、空白または改行文字で区切ることができます。ファイル名に埋め込まれた空白がある場合、ファイル名全体を二重引用符で囲みます。 +.PP +引数ファイル内のファイル名は、引数ファイルの位置ではなく、現在のディレクトリに相対的となります。これらのリストでは、ワイルドカード(*)は使用できません(たとえば、\fB*\&.java\fRとは指定できません)。アットマーク(@)を使用したファイルの再帰的な解釈はサポートされていません。また、\fB\-J\fRオプションもサポートされていません。このオプションは起動ツールに渡されますが、起動ツールでは引数ファイルをサポートしていないからです。 +.PP +\fBjavac\fRコマンドを実行するときに、各引数ファイルのパスと名前の先頭にアットマーク(@)文字を付けて渡します。\fBjavac\fRコマンドは、アットマーク(@)で始まる引数を見つけると、そのファイルの内容を展開して引数リストに挿入します。 +.PP +\fB例 1 \fR単一の引数ファイル +.RS 4 +\fBargfile\fRという名前の単一の引数ファイルを使用して、すべての\fBjavac\fR引数を格納する場合は、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac @argfile\fR + +.fi +.if n \{\ +.RE +.\} +この引数ファイルには、例2で示されている両方のファイルの内容を入れることができます。 +.RE +.PP +\fB例 2 \fR2つの引数ファイル +.RS 4 +\fBjavac\fRオプション用とソース・ファイル名用に、2つの引数ファイルを作成できます。次のリストには、行の継続文字はありません。 +.sp +次を含むoptionsという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-d classes\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-g\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-sourcepath /java/pubs/ws/1\&.3/src/share/classes\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf + +.fi +.if n \{\ +.RE +.\} +次を含むclassesという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMyClass1\&.java\fR +\fBMyClass2\&.java\fR +\fBMyClass3\&.java\fR + +.fi +.if n \{\ +.RE +.\} +それから、次のように\fBjavac\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac @options @classes\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRパスを使用した引数ファイル +.RS 4 +引数ファイルはパスを指定できますが、ファイル内のすべてのファイル名は、(\fBpath1\fRや\fBpath2\fRではなく)次のように現在の作業ディレクトリに相対的となります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac @path1/options @path2/classes\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "注釈処理" +.PP +\fBjavac\fRコマンドが注釈処理を直接サポートしているため、独立した注釈処理コマンドである\fBapt\fRを使用する必要がなくなりました。 +.PP +注釈プロセッサのAPIは、\fBjavax\&.annotation\&.processing\fRおよび\fBjavax\&.lang\&.model\fRパッケージとそのサブパッケージ内に定義されています。 +.SS "注釈処理を行う方法" +.PP +\fB\-proc:none\fRオプションによって注釈処理が無効化されない限り、コンパイラは使用可能なすべての注釈プロセッサを検索します。検索パスは、\fB\-processorpath\fRオプションを使用して指定できます。パスを指定しない場合、ユーザー・クラス・パスが使用されます。プロセッサの検索は、検索パス上の\fBMETA\-INF/services/javax\&.annotation\&.processing\fR\&.Processorという名前のサービス・プロバイダ構成ファイルに基づいて行われます。このようなファイルには、使用するすべての注釈プロセッサの名前を、1行に1つずつ含めてください。また、別の方法として、\fB\-processor\fRオプションを使用してプロセッサを明示的に指定することもできます。 +.PP +コンパイラは、コマンドラインのソース・ファイルやクラスを走査することで、どのような注釈が存在しているかを確認し終わると、プロセッサに対して問合せを行い、それらのプロセッサがどの注釈を処理できるのかを確認します。一致するものが見つかった場合、そのプロセッサが呼び出されます。各プロセッサは、自身が処理する注釈を要求できます。その場合、それらの注釈に対する別のプロセッサを見つける試みは行われません。すべての注釈が要求されると、コンパイラはそれ以上プロセッサの検索を行いません。 +.PP +いずれかのプロセッサによって新しいソース・ファイルが生成されると、注釈処理の2回目のラウンドが開始されます。新しく生成されたすべてのソース・ファイルがスキャンされ、前回と同様に注釈が処理されます。以前のラウンドで呼び出されたプロセッサはすべて、後続のどのラウンドでも呼び出されます。これが、新しいソース・ファイルが生成されなくなるまで続きます。 +.PP +あるラウンドで新しいソース・ファイルが生成されなかった場合、注釈プロセッサがあと1回のみ呼び出され、残りの処理を実行する機会が与えられます。最後に、\fB\-proc:only\fRオプションが使用されないかぎり、コンパイラは、元のソース・ファイルと生成されたすべてのソース・ファイルをコンパイルします。 +.SS "暗黙的にロードされたソース・ファイル" +.PP +コンパイラは、一連のソース・ファイルをコンパイルする際に、別のソース・ファイルを暗黙的にロードすることが必要な場合があります。型の検索を参照してください。そのようなファイルは、現時点では注釈処理の対象になりません。デフォルトでは、注釈処理が実行され、かつ暗黙的にロードされた任意のソース・ファイルがコンパイルされた場合、コンパイラは警告を発行します。\fB\-implicit\fRオプションでは、警告を抑制する方法が提供されます。 +.SH "型の検索" +.PP +ソース・ファイルをコンパイルするために、コンパイラは通常、型に関する情報を必要としますが、その型の定義はコマンド行で指定したソース・ファイルにありません。コンパイラは、ソース・ファイルで使用されているクラスまたはインタフェース、拡張されているクラスまたはインタフェース、あるいは実装されているクラスまたはインタフェースすべてについて、型の情報を必要とします。これには、ソース・ファイルで明示的には言及されていなくても、継承を通じて情報を提供するクラスとインタフェースも含まれます。 +.PP +たとえば、サブクラス\fBjava\&.applet\&.Applet\fRを作成すると、\fBアプレット\fRの祖先のクラス(\fBjava\&.awt\&.Panel\fR、\fBjava\&.awt\&.Container\fR、\fBjava\&.awt\&.Component\fRおよび\fBjava\&.lang\&.Object\fR)を使用していることにもなります。 +.PP +コンパイラは、型の情報が必要になると、その型を定義しているソース・ファイルまたはクラス・ファイルを検索します。まず、ブートストラップ・クラスと拡張機能クラスを検索し、続いてユーザー・クラス・パス(デフォルトでは現在のディレクトリ)を検索します。ユーザー・クラス・パスは、\fBCLASSPATH\fR環境変数を設定して定義するか、または\fB\-classpath\fRオプションを使用して定義します。 +.PP +\fB\-sourcepath\fRオプションが設定されている場合、コンパイラは、指定されたパスからソース・ファイルを検索します。それ以外の場合、コンパイラは、ユーザー・クラス・パスからクラス・ファイルとソース・ファイルの両方を検索します。 +.PP +\fB\-bootclasspath\fRオプションおよび\fB\-extdirs\fRオプションを使用して、別のブートストラップ・クラスや拡張機能クラスを指定できます。クロスコンパイル・オプションを参照してください。 +.PP +型の検索に成功したときに得られる結果は、クラス・ファイル、ソース・ファイル、またはその両方である場合があります。両方が見つかった場合、そのどちらを使用するかを\fB\-Xprefer\fRオプションでコンパイラに指示できます。\fBnewer\fRが指定された場合、コンパイラは2つのファイルのうち新しい方を使用します。\fBsource\fRが指定された場合、コンパイラはソース・ファイルを使用します。デフォルトは\fBnewer\fRです。 +.PP +型の検索自体によって、または\fB\-Xprefer\fRオプションが設定された結果として必要な型のソース・ファイルが見つかった場合、コンパイラはそのソース・ファイルを読み取り、必要な情報を取得します。デフォルトでは、コンパイラはソース・ファイルのコンパイルも行います。\fB\-implicit\fRオプションを使用してその動作を指定できます。\fBnone\fRが指定された場合、ソース・ファイルに対してクラス・ファイルは生成されません。\fBclass\fRが指定された場合、ソース・ファイルに対してクラス・ファイルが生成されます。 +.PP +コンパイラは、注釈処理が完了するまで、ある型情報の必要性を認識しない場合があります。型情報がソース・ファイル内に見つかり、かつ\fB\-implicit\fRオプションが指定されていない場合、コンパイラによって、そのファイルが注釈処理の対象とならずにコンパイルされることが警告されます。この警告を無効にするには、(そのファイルが注釈処理の対象となるように)そのファイルをコマンド行に指定するか、あるいはそのようなソース・ファイルに対してクラス・ファイルを生成する必要があるかどうかを\fB\-implicit\fRオプションを使用して指定します。 +.SH "プログラマティック・インタフェース" +.PP +\fBjavac\fRコマンドは、\fBjavax\&.tools\fRパッケージ内のクラスとインタフェースによって定義される新しいJava Compiler APIをサポートします。 +.SS "例" +.PP +コマンドライン引数を指定するようにコンパイルするには、次の構文を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBJavaCompiler javac = ToolProvider\&.getSystemJavaCompiler();\fR + +.fi +.if n \{\ +.RE +.\} +.PP +例では、診断を標準出力ストリームに書き込み、コマンド行からの呼出し時に\fBjavac\fRが指定する終了コードを返します。 +.PP +\fBjavax\&.tools\&.JavaCompiler\fRインタフェースの他のメソッドを使用すると、診断の処理やファイルの読取り元/書込み先の制御などを行うことができます。 +.SS "旧式のインタフェース" +.PP +\fB注意:\fR +このAPIは、後方互換性のためにのみ保持されています。すべての新しいコードは、新しいJava Compiler APIを使用する必要があります。 +.PP +次のように、\fBcom\&.sun\&.tools\&.javac\&.Main\fRクラスには、プログラムからコンパイラを呼び出すためのstaticメソッドが2つ用意されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static int compile(String[] args);\fR +\fBpublic static int compile(String[] args, PrintWriter out);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBargs\fRパラメータは、通常コンパイラに渡される任意のコマンド行引数を表しています。 +.PP +\fBout\fRパラメータは、コンパイラの診断出力の宛先を示します。 +.PP +\fBreturn\fR値は、\fBjavac\fRの\fBexit\fR値と同じです。 +.PP +\fB注意:\fR +名前が\fBcom\&.sun\&.tools\&.javac\fRで始まるパッケージ(\fBcom\&.sun\&.tools\&.javac\fRのサブパッケージ)で検出される他のすべてのクラスおよびメソッドは、完全に内部用であり、いつでも変更される可能性があります。 +.SH "例" +.PP +\fB例 1 \fR簡単なプログラムのコンパイル +.RS 4 +この例では、greetingsディレクトリで\fBHello\&.java\fRソース・ファイルをコンパイルする方法を示しています。\fBHello\&.java\fRで定義されたクラスは、\fBgreetings\&.Hello\fRと呼ばれます。greetingsディレクトリは、ソース・ファイルとクラス・ファイルの両方があるパッケージ・ディレクトリで、現在のディレクトリのすぐ下にあります。これにより、デフォルトのユーザー・クラス・パスを使用できるようになります。また、\fB\-d\fRオプションを使用して別の出力先ディレクトリを指定する必要もありません。 +.sp +\fBHello\&.java\fR内のソース・コードは次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpackage greetings;\fR +\fB \fR +\fBpublic class Hello {\fR +\fB public static void main(String[] args) {\fR +\fB for (int i=0; i < args\&.length; i++) {\fR +\fB System\&.out\&.println("Hello " + args[i]);\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +greetings\&.Helloのコンパイル: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac greetings/Hello\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\&.Hello\fRの実行: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava greetings\&.Hello World Universe Everyone\fR +\fBHello World\fR +\fBHello Universe\fR +\fBHello Everyone\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fR複数のソース・ファイルのコンパイル +.RS 4 +この例では、\fBgreetings\fRパッケージのソース・ファイル\fBAloha\&.java\fR、\fBGutenTag\&.java\fR、\fBHello\&.java\fRおよび\fBHi\&.java\fRをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% javac greetings/*\&.java\fR +\fB% ls greetings\fR +\fBAloha\&.class GutenTag\&.class Hello\&.class Hi\&.class\fR +\fBAloha\&.java GutenTag\&.java Hello\&.java Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRユーザー・クラス・パスの指定 +.RS 4 +前述の例のソース・ファイルのうち1つを変更した後に、そのファイルを再コンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpwd\fR +\fB/examples\fR +\fBjavac greetings/Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\&.Hi\fRは\fBgreetings\fRパッケージ内の他のクラスを参照しているため、コンパイラはこれらの他のクラスを探す必要があります。デフォルトのユーザー・クラス・パスはパッケージ・ディレクトリを含むディレクトリであるため、前述の例は動作します。現在のディレクトリを気にせずにこのファイルを再コンパイルする場合、\fBCLASSPATH\fRを設定して、ユーザー・クラス・パスに例のディレクトリを追加します。この例では、\fB\-classpath\fRオプションを使用しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-classpath /examples /examples/greetings/Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\&.Hi\fRを変更してバナー・ユーティリティを使用するようにした場合、 そのユーティリティもユーザー・クラス・パスを通じてアクセスできるようになっている必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-classpath /examples:/lib/Banners\&.jar \e\fR +\fB /examples/greetings/Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\fRパッケージでクラスを実行するには、プログラムは\fBgreetings\fRパッケージ、および\fBgreetings\fRクラスが使用するクラスにアクセスする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-classpath /examples:/lib/Banners\&.jar greetings\&.Hi\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fRソース・ファイルとクラス・ファイルの分離 +.RS 4 +次の例では、\fBjavac\fRを使用して、JVM 1\&.7上で実行するコードをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 \-target 1\&.7 \-bootclasspath jdk1\&.7\&.0/lib/rt\&.jar \e \fR +\fB\-extdirs "" OldCode\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-source 1\&.7\fRオプションにより、\fBOldCode\&.java\fRのコンパイルにはリリース1\&.7(または7)のJavaプログラミング言語が使用されます。\fB\-target 1\&.7\fRオプションにより、JVM 1\&.7と互換性のあるクラス・ファイルが生成されます。ほとんどの場合、\fB\-target\fRオプションの値は\fB\-source\fRオプションの値になります。この例では、\fB\-target\fRオプションを省略できます。 +.sp +\fB\-bootclasspath\fRオプションを使用して、適切なバージョンのブートストラップ・クラス(\fBrt\&.jar\fRライブラリ)を指定する必要があります。指定しない場合は、コンパイラによって次の警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 OldCode\&.java\fR +\fBwarning: [options] bootstrap class path not set in conjunction with \fR +\fB\-source 1\&.7\fR + +.fi +.if n \{\ +.RE +.\} +適切なバージョンのブートストラップ・クラスを指定しない場合、コンパイラは古い言語仕様(この例では、バージョン1\&.7のJavaプログラミング言語)を新しいブートストラップ・クラスと組み合せて使用します。その結果、存在しないメソッドへの参照が含まれていることがあるため、クラス・ファイルが古いプラットフォーム(この場合はJava SE 7)で動作しない可能性があります。 +.RE +.PP +\fB例 5 \fRクロス・コンパイル +.RS 4 +この例では、\fBjavac\fRを使用して、JVM 1\&.7上で実行するコードをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 \-target 1\&.7 \-bootclasspath jdk1\&.7\&.0/lib/rt\&.jar \e\fR +\fB \-extdirs "" OldCode\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fB \-source 1\&.7\fRオプションにより、OldCode\&.javaのコンパイルにはリリース1\&.7(または7)のJavaプログラミング言語が使用されます。\fB\-target 1\&.7\fRオプションにより、JVM 1\&.7と互換性のあるクラス・ファイルが生成されます。 +.sp +\fB\-bootclasspath\fRオプションを使用して、適切なバージョンのブートストラップ・クラス(\fBrt\&.jar\fRライブラリ)を指定する必要があります。指定しない場合は、コンパイラによって次の警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 OldCode\&.java\fR +\fBwarning: [options] bootstrap class path not set in conjunction with \-source 1\&.7\fR + +.fi +.if n \{\ +.RE +.\} +適切なバージョンのブートストラップ・クラスを指定しない場合、コンパイラは古い言語仕様を新しいブートストラップ・クラスと組み合せて使用します。この組合せは、存在しないメソッドへの参照が含まれていることがあるため、クラス・ファイルが古いプラットフォーム(この場合はJava SE 7)で動作しない可能性があります。この例では、コンパイラはJavaプログラミング言語のリリース1\&.7を使用します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javadoc.1 b/jdk-1.8.0.281/man/ja/man1/javadoc.1 new file mode 100755 index 0000000..4a1edd5 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javadoc.1 @@ -0,0 +1,4657 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javadoc +.\" Language: Japanese +.\" Date: 2015年3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javadoc" "1" "2015年3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javadoc \- Javaソース・ファイルから、APIドキュメントのHTMLページを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc\fR {\fIpackages\fR|\fIsource\-files\fR} [\fIoptions\fR] [\fI@argfiles\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIpackages\fR +.RS 4 +\fBjava\&.lang java\&.lang\&.reflect java\&.awt\fRなど、空白で区切ってドキュメント化するパッケージの名前。サブパッケージもドキュメント化する場合は、\fB\-subpackages\fRオプションを使用してパッケージを指定します。 +.sp +デフォルトでは、\fBjavadoc\fRは、現在のディレクトリおよびサブディレクトリで指定されたパッケージを探します。\fB\-sourcepath\fRオプションを使用して、パッケージを探すディレクトリのリストを指定します。 +.RE +.PP +\fIsource\-files\fR +.RS 4 +\fBClass\&.java Object\&.java Button\&.java\fRのように空白で区切った、ドキュメント化するJavaソース・ファイルの名前。デフォルトでは、\fBjavadoc\fRは、現在のディレクトリで指定されたクラスを探します。ただし、\fB/home/src/java/awt/Graphics*\&.java\fRのように、クラス・ファイルのフルパスを指定し、ワイルドカード文字を使用できます。現在のディレクトリからの相対パスも指定できます。 +.RE +.PP +\fIoptions\fR +.RS 4 +空白で区切られたコマンド行オプション。オプションを参照してください。 +.RE +.PP +\fI@argfiles\fR +.RS 4 +\fBjavadoc\fRコマンド・オプション、パッケージ名およびソース・ファイル名のリストを任意の順序で含むファイルの名前。 +.RE +.SH "説明" +.PP +\fBjavadoc\fRコマンドは、一連のJavaソース・ファイルにある宣言およびドキュメンテーション・コメントを解析し、デフォルトでは、publicクラス、protectedクラス、ネストされたクラス(匿名の内部クラスは除く)、インタフェース、コンストラクタ、メソッド、およびフィールドについて記述した一連のHTMLページを生成します。\fBjavadoc\fRコマンドは、APIドキュメントの生成や、一連のソース・ファイルの実装ドキュメントの生成に使用できます。 +.PP +\fBjavadoc\fRコマンドは、パッケージ全体、個々のソース・ファイル、またはその両方に対して実行できます。パッケージ全体のドキュメント化を行うには、\fB\-subpackages\fRオプションを使用してディレクトリおよびそのサブディレクトリを再帰的にたどるか、パッケージ名の明示的なリストを渡します。個々のソース・ファイルをドキュメント化するには、Javaソース・ファイル名のリストを渡します。簡単な例を参照してください。 +.SS "ソース・ファイルの処理" +.PP +\fBjavadoc\fRコマンドは、ソースで終わるファイル、およびソース・ファイルで説明しているその他のファイルを処理します。個々のソース・ファイル名を渡して\fBjavadoc\fRを実行する場合、どのソース・ファイルを処理するかを正確に指定できます。ただし、多くの開発者はこの方法では作業しません。パッケージ名を渡すほうが簡単だからです。ソース・ファイル名を明示的に指定しなくても、\fBjavadoc\fRコマンドは3つの方法で実行できます。パッケージ名を渡し、\fB\-subpackages\fRオプションを使用するか、またはソース・ファイル名にワイルドカードを使用することができます。これらの場合、\fBjavadoc\fRコマンドがソース・ファイルの処理を行うのは、そのファイルが次のすべての要件を満たす場合のみです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ファイル名の接頭辞(\fB\&.java\fRを削除)が有効なクラス名である。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ソース・ツリーのルートからの相対的なパス名が、区切り文字をドットに変換すると、有効なパッケージ名になる。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ文に有効なパッケージ名が含まれている。 +.RE +.PP +リンクの処理 +.PP +処理の実行中に、\fBjavadoc\fRコマンドは、その実行でドキュメント化されるパッケージ、クラス、およびメンバーの名前に対して、相互参照リンクを追加します。リンクは、次の場所に表示されます。@タグの説明については、javadocタグを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +宣言(戻り値の型、引数の型、フィールドの型)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB@see\fRタグから生成された\fI「関連項目」\fRセクション。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB{@link}\fRタグから生成されたインライン・テキスト。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB@throws\fRタグから生成された例外の名前。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +インタフェースのメンバーに対する\fI「定義」\fRリンクと、クラスのメンバーに対する\fI「オーバーライド」\fRリンク。メソッド・コメントの継承を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ、クラス、およびメンバーをリストしているサマリー表。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージおよびクラスの継承ツリー。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +索引。 +.RE +.PP +コマンド行で指定しなかったクラスについての既存のテキスト(別に生成したテキスト)に対してリンクを追加するには、\fB\-link\fRおよび\fB\-linkoffline\fRオプションを利用できます。 +.PP +処理の詳細 +.PP +\fBjavadoc\fRコマンドは実行するたびに1つの完全なドキュメントを生成します。前の実行の結果を変更または直接取り込む、増分ビルドを行いません。ただし、\fBjavadoc\fRコマンドは、他の実行の結果にリンクできます。 +.PP +\fBjavadoc\fRコマンドの実装にはJavaコンパイラが必要で、Javaコンパイラに依存しています。\fBjavadoc\fRコマンドは\fBjavac\fRコマンドの一部を呼び出し、宣言をコンパイルして、メンバーの実装を無視します。\fBjavadoc\fRコマンドは、クラス階層を含むクラスの豊富な内部表現とクラスの「使用」関係を構築し、HTMLを生成します。さらに、J\fBjavadoc\fRコマンドは、ソース・コードのドキュメンテーション・コメントから、ユーザーの提供したドキュメントも取得します。ドキュメンテーション・コメントを参照してください。 +.PP +\fBjavadoc\fRコマンドは、メソッド本体を持たない純粋なスタブ・ファイルであるソース・ファイルに対して実行できます。したがって、APIの実装前の設計の早い段階で、ドキュメンテーション・コメントを記述して\fBjavadoc\fRコメントを実行できます。 +.PP +コンパイラに依存することによって、HTML出力は、実際の実装に正確に対応します。実際の実装は、明示的なソース・コードにではなく、暗黙のソース・コードに依存する場合があります。たとえば、\fBjavadoc\fRコマンドは、コンパイル済クラス・ファイルには存在するがソース・コードには存在しないデフォルト・コンストラクタをドキュメント化します。 +.PP +多くの場合、\fBjavadoc\fRコマンドでは、ソース・ファイルのコードが不完全またはエラーを含んでいる場合でもドキュメントを生成できます。すべてのデバッグやトラブルシューティングを完了する前にドキュメントを生成できます。\fBjavadoc\fRコマンドはドキュメンテーション・コメントの基本的なチェックを行います。 +.PP +\fBjavadoc\fRコマンドは、ドキュメントの内部構造を構築する際、参照クラスをすべてロードします。このため、 +\fBjavadoc\fRコマンドは、ブートストラップ・クラス、拡張機能、またはユーザー・クラスにかかわらず、すべての参照クラスを検索できる必要があります。クラスの検出方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html)を参照してください +.PP +通常、作成するクラスは、拡張クラスとして、または\fBjavadoc\fRコマンドのクラス・パスでロードされる必要があります。 +.SS "Javadocのドックレット" +.PP +\fBjavadoc\fRコマンドの出力の内容と形式は、ドックレットを使用してカスタマイズできます。\fBjavadoc\fRコマンドには、標準ドックレットと呼ばれるデフォルトの組込みドックレットがあります。標準ドックレットは、HTML形式のAPIドキュメントを生成します。標準ドックレットを修正またはサブクラスを作成することや、HTML、XML、MIF、RTFなどの好みの出力形式を生成する独自のドックレットを記述することも可能です。 +.PP +\fB\-doclet\fRオプションでカスタム・ドックレットが指定されていない場合、\fBjavadoc\fRコマンドは、デフォルトの標準ドックレットを使用します。\fBjavadoc\fRコマンドには、使用されているドックレットに関係なく使用できるいくつかのオプションがあります。標準ドックレットでは、これらの他に、いくつかのコマンド行オプションが追加されます。オプションを参照してください。 +.SH "ソース・ファイル" +.PP +\fBjavadoc\fRコマンドは、次のタイプのソース・ファイルから出力を生成します。そのファイルは、クラスのJava言語ソース・ファイル(\fB\&.java\fR)、パッケージ・コメント・ファイル、概要コメント・ファイル、およびその他の未処理のファイルです。ここでは、ドキュメント化しないがソース・ツリーに存在する場合があるテスト・ファイルやテンプレート・ファイルについても説明します。 +.SS "クラスのソース・ファイル" +.PP +それぞれのクラスまたはインタフェース、およびそのメンバーは、独自のドキュメンテーション・コメントを持つことができ、それをソース・ファイル内に保持します。ドキュメンテーション・コメントを参照してください。 +.SS "パッケージ・コメント・ファイル" +.PP +それぞれのパッケージは、独自のドキュメンテーション・コメントを持つことができ、それを専用のソース・ファイルに保持します。その内容は、\fBjavadoc\fRコマンドによって生成されるパッケージのサマリー・ページに組み込まれます。このコメントには、通常、そのパッケージ全体に当てはまるドキュメントを記述します。 +.PP +パッケージ・コメント・ファイルを作成するには、次のいずれかのファイルにコメントを格納できます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackage\-info\&.java\fRファイルには、パッケージ宣言、パッケージ注釈、パッケージ・コメント、およびJavadocタグを格納できます。このファイルが優先されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackage\&.html\fRファイルには、パッケージ・コメントとJavadocタグのみを格納できます。パッケージ注釈は格納できません。 +.RE +.PP +各パッケージは、\fBpackage\&.html\fRファイルまたは\fBpackage\-info\&.java\fRファイルのいずれかを1つ持つことができますが、その両方を持つことはできません。このどちらかのファイルをソース・ファイルとともに、ソース・ツリー内のそのパッケージ・ディレクトリ内に配置してください。 +.PP +package\-info\&.javaファイル +.PP +\fBpackage\-info\&.java\fRファイルには、次の構造のパッケージ・コメントを含めることができます。コメントは、パッケージ宣言の前に配置されます。 +.PP +\fB注意:\fR +コメント区切り文字である\fB/**\fRおよび\fB*/\fRが存在する必要がありますが、中間の行の先頭のアスタリスクは省略可能です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * Provides the classes necessary to create an \fR +\fB * applet and the classes an applet uses \fR +\fB * to communicate with its applet context\&.\fR +\fB *

\fR +\fB * The applet framework involves two entities:\fR +\fB * the applet and the applet context\&.\fR +\fB * An applet is an embeddable window (see the\fR +\fB * {@link java\&.awt\&.Panel} class) with a few extra\fR +\fB * methods that the applet context can use to \fR +\fB * initialize, start, and stop the applet\&.\fR +\fB *\fR +\fB * @since 1\&.0\fR +\fB * @see java\&.awt\fR +\fB */\fR +\fBpackage java\&.lang\&.applet;\fR + +.fi +.if n \{\ +.RE +.\} +.PP +package\&.htmlファイル +.PP +\fBpackage\&.html\fRファイルには、次の構造のパッケージ・コメントを含めることができます。コメントは、\fB\fR要素に配置されます。 +.PP +ファイル: +\fBjava/applet/package\&.html\fR +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\fR +\fB\fR +\fBProvides the classes necessary to create an applet and the \fR +\fBclasses an applet uses to communicate with its applet context\&.\fR +\fB

\fR +\fBThe applet framework involves two entities: the applet\fR +\fBand the applet context\&. An applet is an embeddable\fR +\fBwindow (see the {@link java\&.awt\&.Panel} class) with a\fR +\fBfew extra methods that the applet context can use to\fR +\fBinitialize, start, and stop the applet\&. \fR + +\fB@since 1\&.0 \fR +\fB@see java\&.awt\fR +\fB\fR +\fB\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBpackage\&.html\fRファイルは通常のHTMLファイルであり、パッケージ宣言を含んでいません。パッケージ・コメント・ファイルの内容はHTMLで記述しますが、例外が1つあります。このドキュメンテーション・コメントには、コメント区切り文字である\fB/**\fRと\fB*/\fR、または行頭のアスタリスクを含めない、という点です。コメントを書く場合は、最初の文をパッケージのサマリーとし、\fB\fRタグと最初の文の間にタイトルやその他のテキストを含めないようにします。パッケージ・タグを含めることができます。すべてのブロック・タグは、主説明の後に配置する必要があります。\fB@see\fRタグをパッケージ・コメント・ファイルに追加する場合には、完全修飾名を使用する必要があります。 +.PP +コメント・ファイルの処理 +.PP +\fBjavadoc\fRコメントを実行すると、パッケージ・コメント・ファイルが検索されます。パッケージ・コメント・ファイルが見つかった場合は、\fBjavadoc\fRコマンドは次の手順を実行します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +処理できるようにコメントをコピーします。package\&.htmlの場合、\fBjavadoc\fRコマンドは、\fB\fRと\fB\fR +HTMLタグ間ですべてのコンテンツをコピーします。\fB\fRタグ、ソース・ファイルの著作権文または他の情報を配置する\fB<head>\fRセクションを含めることができますが、これらは生成されたドキュメントに表示されません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ・タグを処理します。パッケージ・タグを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +処理したテキストを生成されたパッケージのサマリー・ページの下部に挿入します。Javaプラットフォーム、Standard Edition API仕様の概要 +(http://docs\&.oracle\&.com/javase/8/docs/api/overview\-summary\&.html)を参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージのサマリー・ページの先頭に、パッケージ・コメントの最初の文をコピーします。さらに、\fBjavadoc\fRコマンドは、概要ページのパッケージ・リストに、パッケージ名とパッケージ・コメントの最初の文を追加します。Javaプラットフォーム、Standard Edition API仕様の概要 +(http://docs\&.oracle\&.com/javase/8/docs/api/overview\-summary\&.html)を参照してください +.sp +文の終わりは、クラスやメンバーの主説明の最初の文の終わりと同じルールによって判断されます。 +.RE +.SS "概要コメント・ファイル" +.PP +ドキュメント化する各アプリケーションまたはパッケージ・セットは、独自の概要ドキュメンテーション・コメントを持つことができ、それは専用のソース・ファイルに保持されます。その内容は、\fBjavadoc\fRコマンドによって生成される概要ページに組み込まれます。このコメントには、通常、アプリケーションまたはパッケージ・セット全体に当てはまるドキュメントを記述します。 +.PP +このファイルにはoverview\&.htmlなどの名前を付けることができ、どこに配置してもかまいません。一般的な場所は、ソース・ツリーの最上部です。 +.PP +たとえば、\fBjava\&.applet\fRパッケージのソース・ファイルが/home/user/src/java/appletディレクトリに格納されている場合、概要コメント・ファイルは/home/user/src/overview\&.htmlに作成できます。 +.PP +異なるパッケージのセットに対して\fBjavadoc\fRコマンドを複数回実行する場合は、同じ1つのソース・ファイルのセットに対して複数の概要コメント・ファイルを作成できます。たとえば、内部ドキュメント用に\fB\-private\fRを指定して\fBjavadoc\fRコマンドを1回実行した後、公開ドキュメント用にそのオプションを指定しないで再度実行することができます。この場合、各概要コメント・ファイルの1文目で、そのドキュメントを公開用または内部用として記述できます。 +.PP +概要コメント・ファイルの内容は、HTMLで記述された1つの大きなドキュメンテーション・コメントです。最初の文はアプリケーションまたはパッケージのセットのサマリーとします。\fB<body>\fRタグと最初の文の間にタイトルやその他のテキストを含めないようにします。{\fB@link}\fRなどのインライン・タグを除くすべてのタグは、主説明の後に配置する必要があります。\fB@see\fRタグを追加する場合には、完全修飾名を使用する必要があります。 +.PP +\fBjavadoc\fRコマンドの実行時に、\fB\-overview\fRオプションを使用して概要コメント・ファイル名を指定します。このファイルは、パッケージ・コメント・ファイルと同じように処理されます。\fBjavadoc\fRコマンドは次の手順を実行します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB<body>\fRと\fB</body>\fRタグ間で、処理するすべてのコンテンツをコピーします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +概要タグがあれば処理します。概要タグを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +処理したテキストを生成された概要ページの下部に挿入します。JavaプラットフォームStandard Edition API仕様の概要 +(http://docs\&.oracle\&.com/javase/8/docs/api/overview\-summary\&.html)を参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +概要サマリー・ページの先頭に、概要コメントの最初の文をコピーします。 +.RE +.SS "未処理のファイル" +.PP +ソース・ファイルには、\fBjavadoc\fRコマンドによって宛先ディレクトリにコピーされる、任意のファイルを含めることができます。このようなファイルには、通常、グラフィック・ファイル、サンプルのJavaソースおよびクラス・ファイル、一般的なJavaソース・ファイルのドキュメンテーション・コメントの影響を受けない多くの内容を含む独立したHTMLファイルなどがあります。 +.PP +未処理のファイルを含めるには、doc\-filesというディレクトリにファイルを配置します。doc\-filesディレクトリは、ソース・ファイルを含む任意のパッケージ・ディレクトリのサブディレクトリになることができます。doc\-filesサブディレクトリは、パッケージごとに1つ用意できます。 +.PP +たとえば、ボタンのイメージを\fBjava\&.awt\&.Button\fRクラスのドキュメントに含める場合には、そのイメージ・ファイルを/home/user/src/java/awt/doc\-files/ディレクトリに置きます。doc\-filesディレクトリを/home/user/src/java/doc\-filesに置かないでください。javaはパッケージではないからです。ソース・ファイルを含めることもできません。 +.PP +\fBjavadoc\fRコマンドはファイルを参照しないので、未処理のファイルへのすべてのリンクは、コードに含まれている必要があります。\fBjavadoc\fRコマンドはディレクトリとそのすべての内容を宛先にコピーします。次の例では、Button\&.javaドキュメンテーション・コメントのリンクがどのように見えるかを示しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This button looks like this: \fR +\fB * <img src="doc\-files/Button\&.gif">\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.SS "テストおよびテンプレート・ファイル" +.PP +ソース・ツリーのテストおよびテンプレート・ファイルを、ソース・ファイルが存在するディレクトリまたはサブディレクトリと同じディレクトリに格納できます。テストおよびテンプレート・ファイルが処理されるのを防ぐには、\fBjavadoc\fRコマンドを実行し、明示的に個別のソース・ファイル名を渡します。 +.PP +テスト・ファイルは、有効な、コンパイル可能なソース・ファイルです。テンプレート・ファイルは、有効な、互換性のあるソース・ファイルではありませんが、多くの場合、\fB\&.java\fR接尾辞を持っています。 +.PP +テスト・ファイル +.PP +テスト・ファイルを、名前なしパッケージや、ソース・ファイルが存在するパッケージとは別のパッケージに属するようにする場合、テスト・ファイルをソース・ファイルの下のサブディレクトリに配置し、そのディレクトリに無効な名前を付けます。テスト・ファイルをソースと同じディレクトリに配置し、パッケージ名を示すコマンド行引数を指定して\fBjavadoc\fRコマンドを呼び出すと、テスト・ファイルは警告またはエラーを引き起こします。ファイルが無効な名前を持つサブディレクトリ内に存在する場合、テスト・ファイル・ディレクトリはスキップされ、エラーまたは警告は発行されません。たとえば、ソース・ファイルのテスト・ファイルをcom\&.package1に追加するには、無効なパッケージ名のサブディレクトリに配置します。次のディレクトリ名にはハイフンが含まれているため無効です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcom/package1/test\-files/\fR + +.fi +.if n \{\ +.RE +.\} +.PP +テスト・ファイルにドキュメンテーション・コメントが含まれる場合、\fBjavadoc\fRコマンドの個別の実行で、ワイルドカードを含んだテスト・ソース・ファイル名(\fBcom/package1/test\-files/*\&.java\fRなど)を渡して、テスト・ファイルのドキュメントを生成するように設定できます。 +.PP +テンプレート・ファイル +.PP +テンプレート・ファイルをソース・ディレクトリに配置するが、\fBjavadoc\fRコマンドを実行するときにエラーを生成しない場合、ファイルに\fBBuffer\-Template\&.java\fRなどの無効な名前を付けて、処理させないようにします。\fBjavadoc\fRコマンドは、接尾辞の\fB\&.java\fRが削除されると有効なクラス名になる名前を持つソース・ファイルのみを処理します。 +.SH "生成されるファイル" +.PP +デフォルトでは、\fBjavadoc\fRコマンドは、HTML形式のドキュメントを生成する標準ドックレットを使用します。標準ドックレットは、ここで説明する、基本内容ページ、相互参照ページ、サポート・ページを生成します。各HTMLページは個別のファイルに対応します。\fBjavadoc\fRコマンドは、2つのタイプのファイルを生成します。最初のタイプには、クラスおよびインタフェースに応じた名前が付けられます。2番目のタイプには、最初のタイプのファイルとの競合を防ぐために、ハイフンが含まれます(package\-summary\&.htmlなど)。 +.SS "基本内容ページ" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +記載されているクラスまたはインタフェースごとに1つのクラスまたはインタフェース・ページ(classname\&.html)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +記載されているパッケージごとに1つのパッケージ・ページ(package\-summary\&.html)。\fBjavadoc\fRコマンドは、ソース・ツリーのパッケージ・ディレクトリ内にあるpackage\&.htmlまたはpackage\-info\&.javaという名前のファイル内のHTMLテキストをすべて組み入れます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージのセット全体に対して1つの概要ページ(overview\-summary\&.html)。概要ページは、生成ドキュメントの先頭ページになります。\fBjavadoc\fRコマンドは、\fB\-overview\fRオプションで指定されたファイル内のHTMLテキストをすべて組み入れます。概要ページが作成されるのは、\fBjavadoc\fRコマンドに複数のパッケージ名を渡した場合のみです。HTMLフレームおよびオプションを参照してください。 +.RE +.SS "相互参照ページ" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージのセット全体に対して1つのクラス階層ページ(overview\-tree\&.html)。階層ページを表示するには、ナビゲーション・バーの「概要」をクリックしてから、「階層ツリー」をクリックします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージごとに1つのクラス階層ページ(package\-tree\&.html)。階層ページを表示するには、特定のパッケージ、クラス、またはインタフェースのページに移動し、「階層ツリー」をクリックしてそのパッケージの階層を表示します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージごとに1つの使用ページ(package\-use\&.html)と、クラスおよびインタフェースごとに1つずつの使用ページ(class\-use/classname\&.html)。使用ページでは、指定したクラス、インタフェース、またはパッケージの一部を使用しているパッケージ、クラス、メソッド、コンストラクタ、およびフィールドについて記述されます。たとえば、クラスまたはインタフェースAを例にすると、その使用ページには、Aのサブクラス、Aとして宣言されたフィールド、Aを返すメソッド、A型のパラメータを持つメソッドおよびコンストラクタが組み込まれます。使用ページを表示するには、パッケージ、クラス、またはインタフェースに移動し、ナビゲーション・バーの「使用」リンクをクリックします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +すべての非推奨APIとその推奨する代替をリストする非推奨APIページ(deprecated\-list\&.html)。非推奨APIは将来の実装で削除される可能性があるので使用しないでください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +定数フィールドの値用の定数フィールド値ページ(constant\-values\&.html)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +直列化された形式ページ(serialized\-form\&.html)。フィールドおよびメソッドの説明を含む、直列化可能かつ外部化可能なクラスに関する情報用のページです。このページ内の情報は、APIを使用する開発者ではなく、再実装者に必要な情報です。直列化された形式ページへアクセスするには、直列化されたクラスに移動して、そのクラス・コメントにある「関連項目」セクションで「直列化された形式」をクリックします。標準ドックレットは直列化された形式ページを生成します。このページには、Serializableを実装するすべてのクラス(publicまたは非public)が、その\fBreadObject\fRや\fBwriteObject\fRメソッド、直列化されたフィールド、および\fB@serial\fR、\fB@serialField\fR、\fB@serialData\fRタグからのドキュメンテーション・コメントとともにリストされます。直列化可能なpublicクラスを除外するには、そのクラス(またはそのパッケージ)を\fB@serial\fR +excludeでマークします。直列化可能なpackage\-privateクラスを含めるには、そのクラス(またはそのパッケージ)を\fB@serial\fR +includeでマークします。リリース1\&.4では、\fB\-private\fRオプションを指定せずに\fBjavadoc\fRコマンドを実行することにより、publicクラスおよびprivateクラスの完全に直列化された形式を生成できます。オプションを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +索引ページ(\fBindex\-*\&.html\fR)。すべてのクラス名、インタフェース名、コンストラクタ名、フィールド名、およびメソッド名がアルファベット順に並んでいます。索引ページは、Unicodeを扱えるように国際化されています。1つのファイルとして生成することも、先頭文字(英語の場合A\(enZ)ごとに別々のファイルとして生成することもできます。 +.RE +.SS "サポート・ページ" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ヘルプ・ページ(help\-doc\&.html)。ナビゲーション・バーや前述の各ページに関する説明が記載されています。デフォルトのヘルプ・ファイルを独自のカスタム・ヘルプ・ファイルでオーバーライドするには、\fB\-helpfile\fRを使用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +表示用のHTMLフレームを作成する1つのindex\&.htmlファイル。フレーム付きの先頭ページを表示するにはこのファイルをロードします。index\&.htmlファイルには、テキスト・コンテンツは含まれていません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +複数のフレーム・ファイル(\fB*\-frame\&.html\fR)。パッケージ、クラス、およびインタフェースのリストが含まれています。フレーム・ファイルはHTMLフレームを表示します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ・リスト・ファイル(package\-list)。\fB\-link\fRおよび\fB\-linkoffline\fRオプションで使用されます。パッケージ・リスト・ファイルはテキスト・ファイルであり、どのリンクからもアクセスできません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +スタイルシート・ファイル(stylesheet\&.css)。生成されるページの一部の要素について色、フォント・ファミリ、フォント・サイズ、フォント・スタイル、および配置を制御します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +doc\-filesディレクトリ。宛先ディレクトリにコピーするイメージ、サンプル・コード、ソース・コードなどのファイルが格納されます。これらのファイルは、\fBjavadoc\fRコマンドによって処理されません。このディレクトリは、ソース・ツリーの中に存在する場合にのみ処理されます。 +.RE +.PP +オプションを参照してください。 +.SS "HTMLフレーム" +.PP +\fBjavadoc\fRコマンドは、コマンドに渡された値に基づき、最小限必要な数(2または3)のフレームを生成します。\fBjavadoc\fRコマンドに引数として1つのパッケージ名または1つのパッケージに含まれるソース・ファイルを渡す場合は、パッケージのリストが省略されます。そのかわりに、\fBjavadoc\fRコマンドは左側の列に1つのフレームを作成し、クラスのリストを表示します。複数のパッケージ名を渡した場合は、\fBjavadoc\fRコマンドは、すべてのパッケージをリストする第3のフレームと概要ページ(overview\-summary\&.html)を作成します。フレームを省略するには、「フレームなし」リンクをクリックするか、overview\-summary\&.htmlページからページ・セットを表示します。 +.SS "生成されるファイルの構造" +.PP +生成されるクラス・ファイルおよびインタフェース・ファイルは、Javaソース・ファイルおよびクラス・ファイルと同じディレクトリ階層に編成されます。1つのサブパッケージにつき1つのディレクトリ、という構造になります。 +.PP +たとえば、\fBjava\&.applet\&.Applet\fRクラス用に生成されるドキュメントは、java/applet/Applet\&.htmlに格納されます。 +.PP +生成先ディレクトリの名前が\fBapidocs\fRだとすると、\fBjava\&.applet\fRパッケージのファイルの構造は、次のとおりです。前述のように、\fIframe\fRという語を名前に含むファイルは、すべて左上または左下のフレームに表示されます。それ以外のHTMLファイルは、すべて右側のフレームに表示されます。 +.PP +ディレクトリは太字です。アスタリスク(*)は、\fBjavadoc\fRコマンドへの引数がパッケージ名ではなくソース・ファイル名である場合に省略されるファイルおよびディレクトリを示しています。引数がソース・ファイル名の場合、空のパッケージ・リストが作成されます。doc\-filesディレクトリは、ソース・ツリー内に存在する場合にのみ、生成先に作成されます。生成されるファイルを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBapidocs\fR: 最上位レベル・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +index\&.html: HTMLフレームを設定する初期ページ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +*overview\-summary\&.html: パッケージ・リストとサマリー +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +overview\-tree\&.html: すべてのパッケージのクラス階層 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +deprecated\-list\&.html: すべてのパッケージの非推奨API +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +constant\-values\&.html: すべてのパッケージの静的フィールド値 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +serialized\-form\&.html: すべてのパッケージの直列化されたフォーム +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +*overview\-frame\&.html: 左上のフレームに表示するすべてのパッケージ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +allclasses\-frame\&.html: 左下のフレームに表示するすべてのクラス +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +help\-doc\&.html: Javadocページの編成に関するヘルプ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +index\-all\&.html: +\fB\-splitindex\fRオプションなしで作成されたデフォルトの索引 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBindex\-files\fR: +\fB\-splitindex\fRオプションを指定して作成されたディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +index\-<number>\&.html: +\fB\-splitindex\fRオプションを指定して作成された索引ファイル +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-list: 外部参照を解決するためのパッケージ名 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +stylesheet\&.css: フォント、色、位置などを定義します +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjava\fR: パッケージ・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBapplet\fR: サブパッケージ・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Applet\&.html: +\fBApplet\fRクラス・ページ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +AppletContext\&.html: +\fBAppletContext\fRインタフェース +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +AppletStub\&.html: +\fBAppletStub\fRインタフェース +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +AudioClip\&.html: +\fBAudioClip\fRインタフェース +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-summary\&.html: クラスとサマリー +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-frame\&.html: 左下のフレームに表示するパッケージ・クラス +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-tree\&.html: このパッケージのクラス階層 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-use\&.html: このパッケージが使用される場所 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdoc\-files\fR: イメージおよびサンプル・ファイルのディレクトリ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBclass\-use\fR: イメージおよびサンプル・ファイルの場所 +.sp +\- Applet\&.html: Appletクラスの使用 +.sp +\- AppletContext\&.html: +\fBAppletContext\fRインタフェースの使用 +.sp +\- AppletStub\&.html: +\fBAppletStub\fRインタフェースの使用 +.sp +\- AudioClip\&.html: +\fBAudioClip\fRインタフェースの使用 +.RE +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBsrc\-html\fR: ソース・コード・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjava\fR: パッケージ・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBapplet\fR: サブパッケージ・ディレクトリ +.sp +\- Applet\&.html: Appletソース・コード +.sp +\- AppletContext\&.html: +\fBAppletContext\fRソース・コード +.sp +\- AppletStub\&.html: +\fBAppletStub\fRソース・コード +.sp +\- AudioClip\&.html: +\fBAudioClip\fRソース・コード +.RE +.RE +.RE +.SS "生成されるAPI宣言" +.PP +\fBjavadoc\fRコマンドは、それぞれのクラス、インタフェース、フィールド、コンストラクタ、およびメソッドの記述の最初に、そのAPI用の宣言を生成します。たとえば、\fBBoolean\fRクラスの宣言は、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic final class Boolean\fR +\fBextends Object\fR +\fBimplements Serializable\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBBoolean\&.valueOf\fRメソッドの宣言は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static Boolean valueOf(String s)\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavadoc\fRコマンドは、修飾子\fBpublic\fR、\fBprotected\fR、\fBprivate\fR、\fBabstract\fR、\fBfinal\fR、\fBstatic\fR、\fBtransient\fR、および\fBvolatile\fRを含めることができますが、\fBsynchronized\fRおよび\fBnative\fRはできません。\fBsynchronized\fRおよび\fBnative\fR修飾子は、実装の詳細とみなされているため、API仕様には含まれません。 +.PP +APIでは、並行性セマンティクスについて、キーワード\fBsynchronized\fRに依存するのではなく、コメントの主説明としてドキュメント化する必要があります。たとえば、「1つのenumerationを複数のスレッドから並行して使用することはできない」のように記述します。ドキュメントには、これらのセマンティクスを実現する方法を記述しないでください。たとえば、\fBHashtable\fRオプションはスレッドセーフである必要がありますが、「エクスポートされるすべてのメソッドを同期化してそれを実現する」のように指定する根拠はありません。より高度な並行性のために、バケット・レベルで内部的に同期化する権限を保有しておくことをお薦めします。 +.SH "ドキュメンテーション・コメント" +.PP +このセクションでは、ソース・コードのコメントとコメントの継承について説明します。 +.SS "ソース・コード・コメント" +.PP +ソース・コードの任意のクラス、インタフェース、メソッド、コンストラクタ、またはフィールドの宣言の前に、ドキュメンテーション・コメントを記述することができます。各パッケージにもドキュメンテーション・コメントを作成できます。構文は若干異なりますが、概要にもドキュメンテーション・コメントを作成できます。ドキュメンテーション・コメントは、\fB/**\fRと、終わりを表す\fB*/\fRの間にある文字から構成されます。先頭のアスタリスクは各行で使用でき、次の項で詳しく説明します。コメントのテキストは、複数行にわたって記述できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This is the typical format of a simple documentation comment\fR +\fB * that spans two lines\&.\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +スペースを節約するには、コメントを1行に入れます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/** This comment takes up only one line\&. */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コメントの配置 +.PP +ドキュメンテーション・コメントは、クラス、インタフェース、コンストラクタ、メソッド、またはフィールド宣言の直前に配置される場合にのみ認識されます。メソッドの本体に置かれているドキュメンテーション・コメントは無視されます。\fBjavadoc\fRコマンドは、宣言文ごとに1つのドキュメンテーション・コメントしか認識しません。タグを使用できる場所を参照してください。 +.PP +よくある間違いは、クラス・コメントとクラス宣言の間に\fBimport\fR文を置いてしまうことです。\fBjavadoc\fRコマンドはクラス・コメントを無視するので、\fBimport\fR文をこの場所に配置しないでください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This is the class comment for the class Whatever\&.\fR +\fB */\fR +\fB \fR +\fBimport com\&.example; // MISTAKE \- Important not to put import statement here\fR +\fB \fR +\fBpublic class Whatever{ }\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コメントのパーツ +.PP +ドキュメンテーション・コメントには、主説明とその後に続くタグ・セクションが含まれます。主説明は、開始区切り文字\fB/**\fRで始まり、タグ・セクションまで続きます。タグ・セクションは、先頭文字が\fB@\fRの行で定義される最初のブロック・タグから始まります(先頭のアスタリスク、空白文字、先頭の区切り文字\fB/**\fRは除く)。主説明を記述せず、タグ・セクションのみのコメントを記述することもできます。主説明は、タグ・セクション以降に続けることはできません。タグの引数は、複数行にわたって記述できます。タグの数に制限はありません。何回も記述できるタグと、1回しか記述できないタグがあります。たとえば、次の\fB@see\fRタグからタグ・セクションは始まります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This sentence holds the main description for this documentation comment\&.\fR +\fB * @see java\&.lang\&.Object\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ブロックおよびインライン・タグ +.PP +タグは、\fBjavadoc\fRコマンドが処理するドキュメンテーション・コメント内の特殊なキーワードです。タグには2つのタイプがあります。1つは\fB@tag\fRタグのように表記されるブロック・タグ(スタンドアロン・タグとも呼ばれる)、もう1つは\fB{@tag}\fRタグのように中カッコで囲んで表記されるインライン・タグです。ブロック・タグが解釈されるには、行頭のアスタリスク、空白文字、区切り文字(\fB/**\fR)を除いて、行の先頭に置く必要があります。これは、\fB@\fR文字をテキスト内の別の場所で使用しても、タグの開始として解釈されないことを意味しています。\fB@\fR文字を使用して行を開始しても、それが解釈されないようにするには、HTMLエンティティ\fB@\fRを使用します。それぞれのブロック・タグには、関連付けられたテキストがあります。このテキストは、タグの後から、次のタグの前、またはドキュメンテーション・コメントの最後までの間に記述されたテキストです(タグまたはコメント区切り文字を除く)。この関連テキストは、複数行にわたって記述できます。インライン・タグは、テキストを記述できる場所であればどこにでも置くことができ、解釈されます。次の例にはブロック・タグ\fB@deprecated\fRとインライン・タグ\fB{@link}\fRが含まれています。javadocタグを参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @deprecated As of JDK 1\&.1, replaced by {@link #setBounds(int,int,int,int)}\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +HTMLでのコメントの記述 +.PP +テキストはHTMLエンティティとHTMLタグを使用してHTMLで記述される必要があります。使用するブラウザがサポートする任意のHTMLのバージョンを使用できます。標準ドックレットは、カスケーディング・スタイル・シートおよびフレームを含め、ドキュメンテーション・コメント以外の部分でHTML 3\&.2に準拠したコードを生成します。フレーム・セットのため、生成されたファイルにはHTML 4\&.0が推奨されます。 +.PP +たとえば、より小さい記号(<)およびより大きい記号(>)のエンティティは、\fB<\fRおよび\fB>\fRと記述する必要があります。同様に、アンパサンド(&)は\fB&\fRと記述する必要があります。次の例では、太字のHTMLタグ\fB<b>\fRを使用しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This is a <b>doc</b> comment\&.\fR +\fB * @see java\&.lang\&.Object\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +先頭のアスタリスク +.PP +\fBjavadoc\fRコマンドによるドキュメンテーション・コメントの解析時に、各行の先頭にあるアスタリスク(*)文字は破棄されます。最初のアスタリスク(*)文字より前にある空白やタブも破棄されます。行頭のアスタリスクを省略した場合、インデントを保持したままでサンプル・コードを\fB<PRE>\fRタグ内のドキュメンテーション・コメントに直接貼り付けられるように、先頭の空白文字は削除されなくなります。ブラウザは、空白文字をタブよりも一律に解釈します。インデントの起点は(区切り文字\fB/**\fRまたは\fB<PRE>\fRタグではなく)左マージンになります。 +.PP +最初の文 +.PP +各ドキュメンテーション・コメントの最初の文は、宣言されているエンティティに関する簡潔かつ完全なサマリー文である必要があります。この文は、空白、タブ、または行終了文字が続く最初のピリオド、または最初のブロック・タグがある位置で終わります。最初の文は、\fBjavadoc\fRコマンドによってHTMLページの先頭にあるメンバーのサマリーの部分にコピーされます。 +.PP +複数フィールドの宣言 +.PP +Javaプラットフォームでは、1つの文で複数のフィールドを宣言できます。ただし、この文には、1つのドキュメンテーション・コメントしか記述できません。そのコメントが、すべてのフィールドに対してコピーされます。フィールドごとにドキュメンテーション・コメントを記述する必要がある場合は、各フィールドを別々の文で宣言する必要があります。たとえば、次のドキュメンテーション・コメントは、1つの宣言として記述すると不適切です。この場合は、宣言を2つに分けることをお薦めします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/** \fR +\fB * The horizontal and vertical distances of point (x,y)\fR +\fB */\fR +\fBpublic int x, y; // Avoid this \fR +\fB \fR +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavadoc\fRコマンドは、上のコードから次のようなドキュメントを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic int x\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The horizontal and vertical distances of point (x, y)\&. +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic int y\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The horizontal and vertical distances of point (x, y)\&. +.PP +ヘッダー・タグの使用 +.PP +メンバーに対してドキュメンテーション・コメントを記述するときには、\fB<H1>\fRおよび\fB<H2>\fRなどのHTML見出しタグを使用しないことをお薦めします。\fBjavadoc\fRコマンドは、完全な構造化ドキュメントを作成するので、このような構造化タグが使用されていると、生成ドキュメントの形式が悪影響を受けることがあります。ただし、クラスやパッケージのコメントでは、これらの見出しを使用して独自の構造を指定してかまいません。 +.SS "メソッド・コメントの継承" +.PP +\fBjavadoc\fRコマンドでは、クラスおよびインタフェースでメソッド・コメントを継承して、欠落したテキストを入力したり、明示的にメソッド・コメントを継承することができます。コンストラクタ、フィールド、およびネストされたクラスは、ドキュメンテーション・コメントを継承しません。 +.PP +\fB注意:\fR +ドキュメンテーション・コメントをコピーに利用するには、継承したメソッドのソース・ファイルが\fB\-sourcepath\fRオプションで指定したパスのみに置かれている必要があります。コマンド行で、クラスもパッケージも渡す必要はありません。この点はリリース1\&.3\&.\fIn\fR以前とは対照的です。これまでは、クラスがドキュメント化されるクラスであることが必要でした。 +.PP +欠落テキストの入力 +.PP +主説明、または\fB@return\fR、\fB@param\fR、\fB@throws\fRタグがメソッド・コメントから欠落している場合、\fBjavadoc\fRコマンドは、対応する主説明またはタグ・コメントを、それがオーバーライドまたは実装しているメソッド(ある場合)からコピーします。メソッド・コメントの継承を参照してください。 +.PP +特定のパラメータの\fB@param\fRタグが見つからない場合、そのパラメータのコメントが、上位の継承階層のメソッドからコピーされます。特定の例外の\fB@throws\fRタグが見つからない場合、その例外が宣言されている場合にかぎり、\fB@throws\fRタグがコピーされます。 +.PP +この動作はリリース1\&.3以前の動作とは対照的です。これまでのバージョンでは、主説明またはタグが存在すれば、コメントは一切継承されませんでした。 +.PP +javadocタグおよびオプションを参照してください。 +.PP +明示的な継承 +.PP +\fB{@inheritDoc}\fRインライン・タグをメソッドの主説明または\fB@return\fR、\fB@param\fR、\fB@throws\fRタグ・コメントに挿入します。対応する継承された主説明またはタグ・コメントは、その場所にコピーされます。 +.SS "クラスおよびインタフェースの継承" +.PP +コメントの継承は、クラスおよびインタフェースからの継承の、考えられるすべての場合に発生します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラスのメソッドがスーパークラスのメソッドをオーバーライドしている場合 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +インタフェースのメソッドがスーパーインタフェースのメソッドをオーバーライドしている場合 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラスのメソッドがインタフェースのメソッドを実装している場合 +.RE +.PP +最初の2つのケースでは、\fBjavadoc\fRコマンドは、オーバーライドしているメソッドのドキュメント内に\fI「オーバーライド」\fRという小見出しを生成します。コメントが継承されているかどうかにかかわらず、オーバーライドされているメソッドへのリンクが含まれます。 +.PP +3つ目のケース(特定のクラスのメソッドがインタフェースのメソッドを実装している場合)では、\fBjavadoc\fRコマンドは、オーバーライドしているメソッドのドキュメント内に\fI「定義」\fRという小見出しを生成します。コメントが継承されているかどうかにかかわらず、実装されているメソッドへのリンクが含まれます。 +.SS "メソッド・コメントのアルゴリズム" +.PP +メソッドにドキュメンテーション・コメントがない、または\fB{@inheritDoc}\fRタグがある場合、\fBjavadoc\fRコマンドは次のアルゴリズムを使用して適用できるコメントを検索します。アルゴリズムは、最も特定される適用可能なドキュメンテーション・コメントを探し、スーパークラスよりもインタフェースを優先するように設計されています。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +直接に実装されている(または、拡張されている)インタフェースを、メソッドの宣言で\fBimplements\fR(または\fBextends\fR)という語の後に出現する順序で、1つずつ調べます。このメソッドについて最初に見つかったドキュメンテーション・コメントを採用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +手順1でドキュメンテーション・コメントが見つからなかった場合は、直接実装されている(または、拡張されている)インタフェースのそれぞれに対して、このアルゴリズム全体を再帰的に適用します(その際の順序は、手順1でインタフェースを調べたときの順序と同じ)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +手順2でドキュメンテーション・コメントが見つからなかった場合で、このクラスが\fBObject\fR以外のクラスであるが、インタフェースではない場合は、次のように処理します。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +スーパークラスにこのメソッドについてのドキュメンテーション・コメントが記述されている場合は、そのコメントを採用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +手順3aでドキュメンテーション・コメントが見つからなかった場合は、スーパークラスに対して、このアルゴリズム全体を再帰的に適用します。 +.RE +.RE +.SH "JAVADOCタグ" +.PP +\fBjavadoc\fRコマンドは、Javaのドキュメンテーション・コメント内に埋め込まれた特別なタグを解析します。\fBjavadoc\fRタグを使用すると、完全な整形式のAPIをソース・コードから自動的に生成できます。タグはアットマーク記号(\fB@\fR)で始まり、大文字と小文字が区別されます。これらのタグは、表示されているとおりに大文字と小文字を使用して入力する必要があります。タグは、行の先頭(先頭の空白文字と省略可能なアスタリスクの後)に置く必要があります。そうしないと、テキストとして扱われます。慣例として、同じ名前のタグは1箇所にまとめます。たとえば、\fB@see\fRタグが複数ある場合は、すべて同じ場所にまとめて配置します。詳細は、タグを使用できる場所を参照してください。 +.PP +タグには、次のタイプがあります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ブロック・タグ: ブロック・タグは主説明に続くタグ・セクション内にのみ配置します。ブロック・タグは、\fI@tag\fRの形式をとります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +インライン・タグ: インライン・タグは主説明内またはブロック・タグのコメント内の任意の場所に配置します。インライン・タグは\fI{@tag}\fRのように中カッコで囲みます。 +.RE +.PP +カスタム・タグについては、\-tag tagname:Xaoptcmf:"taghead"を参照してください。タグを使用できる場所も参照してください。 +.SS "タグの説明" +.PP +@author \fIname\-text\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fB\-author\fRオプションが使用されている場合、指定した名前のテキストの作成者エントリを生成されるドキュメントに追加します。1つのドキュメンテーション・コメントに複数の\fB@author\fRタグを含めることができます。1つの\fB@author\fRタグに1つの名前を指定することも、複数の名前を指定することもできます。前者の場合は、\fBjavadoc\fRコマンドによって名前と名前の間にカンマ(,)と空白文字が挿入されます。後者の場合は、テキスト全体が解析されることなく、生成ドキュメントにコピーされます。したがって、カンマではなく、各言語に対応した名前区切り文字を使用する必要があるときに、1行に複数の名前を指定できます。JavadocツールでのDocコメントの記述方法の@authorに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@author)を参照してください。 +.RE +.PP +{@code \fItext\fR} +.RS 4 +JDK 1\&.5で導入 +.sp +\fB<code>{@literal}</code>\fRと同じです。 +.sp +テキストをHTMLマークアップまたはネストされたJavadocタグとして解釈せずに、textをコード・フォントで表示します。これにより、ドキュメンテーション・コメントでは、パラメータの型(\fB<Object>\fR)、不等号(\fB3 < 4\fR)、矢印(\fB<\-\fR)などで、通常の山カッコ(<および>)をHTMLエンティティ(\fB<\fRおよび\fB>\fR)のかわりに使用できます。たとえば、ドキュメンテーション・コメント・テキスト\fB{@code A<B>C}\fRは、\fBA<B>C\fRとして変更されずに生成されたHTMLページに表示されます。つまり、\fB<B>\fRが太字として解釈されず、そのフォントはコード・フォントになります。コード・フォントなしで同じ機能を実現するには、\fB{@literal}\fRタグを使用します。 +.RE +.PP +@deprecated \fIdeprecated\-text\fR +.RS 4 +JDK 1\&.0で導入 +.sp +このAPIは動作し続けますが、このAPIを使用しないことを薦めるコメントを追加します。\fBjavadoc\fRコマンドは、\fBdeprecated\-text\fRを主説明の前に移動してイタリックにし、その前に太字の警告「推奨されていません。」を追加します。このタグは、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、およびフィールドで有効です。 +.sp +非推奨テキストの最初の文では、そのAPIが推奨されなくなった時期と、代替として使用するAPIをユーザーに提示する必要があります。\fBjavadoc\fRコマンドは、この最初の文を、サマリー・セクションと索引にコピーします。その後の文で非推奨になった理由を説明することもできます。代替APIを指し示す\fB{@link}\fRタグ(Javadoc 1\&.2以降の場合)を含める必要があります。 +.sp +\fI@deprecated annotation\fRタグを使用してプログラム要素を非推奨にします。APIを非推奨にする方法と時期 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation\&.html)を参照してください。 +.sp +JavadocツールでのDocコメントの記述方法の@deprecatedに関する項 + +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@deprecated)も参照してください。 +.RE +.PP +{@docRoot} +.RS 4 +JDK 1\&.3で導入 +.sp +生成されるページからの、生成ドキュメントの(生成先)ルート・ディレクトリへの相対パスを表します。このタグは、著作権のページや会社のロゴなど、生成されるすべてのページから参照するファイルを組み込むときに便利です。通常は、各ページの最下部から著作権のページにリンクします。 +.sp +この\fB{@docRoot}\fRタグは、コマンド行でもドキュメンテーション・コメント内でも使用できます。このタグは、任意のタグ(\fB@return\fR、\fB@param\fRおよび\fB@deprecated\fRタグなど)のテキスト部分を含む、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、およびフィールドで有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド行で、header、footerまたはbottomが定義されている場合、\fBjavadoc \-bottom \*(Aq<a href="{@docRoot}/copyright\&.html">Copyright</a>\*(Aq\fRとなります。 +.sp +\fB{@docRoot}\fRタグをmakefile内でこのように利用する場合、一部の\fBmakefile\fRプログラムでは、中カッコ\fB{}\fR文字を特別にエスケープする必要があります。たとえば、Inprise MAKEバージョン5\&.2をWindows上で実行する場合は、\fB{{@docRoot}}\fRのように、中カッコを二重にする必要があります。\fB\-bottom\fRオプションなどのオプションへの引数を囲むのに、二重(一重ではなく)引用符も必要です(\fBhref\fR引数を囲む引用符は省略)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ドキュメンテーション・コメントでは +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * See the <a href="{@docRoot}/copyright\&.html">Copyright</a>\&.\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +このタグが必要な理由は、生成ドキュメントが、サブパッケージと同じ深さを持つ階層構造のディレクトリに格納されるからです。式: +\fB<a href="{@docRoot}/copyright\&.html">\fRは、\fBjava/lang/Object\&.java\fRの場合\fB<a href="\&.\&./\&.\&./copyright\&.html">\fRに、\fBjava/lang/ref/Reference\&.java\fRの場合\fB<a href="\&.\&./\&.\&./\&.\&./copyright\&.html">\fRに解決されます。 +.RE +.RE +.PP +@exception \fIclass\-name description\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fB@throws\fRタグと同じです。@throws class\-name descriptionを参照してください。 +.RE +.PP +{@inheritDoc} +.RS 4 +JDK 1\&.4で導入 +.sp +最も近い継承可能なクラスまたは実装可能なインタフェースから、このタグの位置にある現在のドキュメンテーション・コメントに、ドキュメントを継承(コピー)します。これにより、より汎用的なコメントを継承ツリーの上位に記述し、コピーしたテキストを使用して記述することができます。 +.sp +このタグは、ドキュメンテーション・コメントの次の位置でのみ有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +メソッドの主説明ブロック内。この場合、主説明は、上位階層のクラスまたはインタフェースからコピーされます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +メソッドの\fB@return\fR、\fB@param\fR、\fB@throws\fRタグのテキスト引数内。この場合、タグ・テキストは、上位階層の対応するタグからコピーされます。 +.RE +.sp +継承階層でコメントを見つける方法に関する説明は、メソッド・コメントの継承を参照してください。このタグが見つからない場合、コメントは、この項で説明するルールに応じて、自動的に継承されるかどうかが決まります。 +.RE +.PP +{@link \fIpackage\&.class#member label\fR} +.RS 4 +JDK 1\&.2で導入 +.sp +表示テキストlabelとともにインライン・リンクを挿入します。labelは、参照クラスの指定されたパッケージ、クラス、またはメンバーの名前のドキュメントを指し示します。このタグは、\fB@return\fR、\fB@param\fRおよび\fB@deprecated\fRタグなどの任意のタグのテキスト部分を含む、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、およびフィールドで有効です。JavadocツールでのDocコメントの記述方法の@linkに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#{@link)を参照してください。 +.sp +このタグは\fB@see\fRタグに似ています。どちらのタグも、\fBpackage\&.class#member\fRと\fBlabel\fRの参照方法と、有効な構文が同じです。主な違いは、\fB{@link}\fRタグでは、「関連項目」セクションにリンクが配置されるかわりに、インライン・リンクが生成されるという点です。インライン・テキストの他の部分と区別するために、\fB{@link}\fRタグの最初と最後に中カッコを記述します。ラベル内で右中カッコ(\fB}\fR)を使用する必要がある場合、HTMLエンティティ記法\fB}\fRを使用します。 +.sp +1つ文の中で使用できる\fB{@link}\fRタグの数に制限はありません。このタグは、ドキュメンテーション・コメントの主説明部分、または\fB@deprecated\fR、\fB@return\fR、\fB@param\fRタグなどの任意のタグのテキスト部分で使用できます。 +.sp +たとえば、次のコメントでは\fBgetComponentAt(int,int)\fRメソッドを参照しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBUse the {@link #getComponentAt(int, int) getComponentAt} method\&.\fR + +.fi +.if n \{\ +.RE +.\} +標準ドックレットでは、このコードから次のHTMLが生成されます(このコメントが同じパッケージの別のクラスを参照している場合)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBUse the <a href="Component\&.html#getComponentAt(int, int)">getComponentAt</a> method\&.\fR + +.fi +.if n \{\ +.RE +.\} +前の行は、次のようにWebページに表示されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBUse the getComponentAt method\&.\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +{@linkplain \fIpackage\&.class#member label\fR} +.RS 4 +JDK 1\&.4で導入 +.sp +\fB{@link}\fRタグと同じ動作をしますが、リンク・ラベルがコード・フォントではなくプレーン・テキストで表示される点が異なります。ラベルがプレーン・テキストで記述されていると便利です。たとえば、「\fBRefer to {@linkplain add() the overridden method}\fR\&.」は「Refer to the overridden method」と表示されます。 +.RE +.PP +{@literal \fItext\fR} +.RS 4 +JDK 1\&.5で導入 +.sp +テキストをHTMLマークアップまたはネストされたJavadocタグとして解釈せずに、textを表示します。これにより、ドキュメンテーション・コメントでは、パラメータの型(\fB<Object>\fR)、不等号(\fB3 < 4\fR)、矢印(<\-)などで、山カッコ(\fB<および>\fR)をHTMLエンティティ(\fB<\fRおよび\fB>\fR)のかわりに使用できます。たとえば、ドキュメンテーション・コメント・テキスト\fB{@literal A<B>C}\fRは、\fBA<B>C\fRとしてブラウザの生成されたHTMLページで変更されずに表示されます。\fB<B>\fRは太字として解釈されません(コード・フォントになりません)。コード・フォントで同じ機能を実現するには、\fB{@code}\fRタグを使用します。 +.RE +.PP +@param \fIparameter\-name description\fR +.RS 4 +JDK 1\&.0で導入 +.sp +「パラメータ」セクションに、指定された\fBparameter\-name\fRの後に指定されたdescriptionを続けてパラメータを追加します。ドキュメンテーション・コメントを記述するときには、descriptionを複数行にわたって記述することもできます。このタグは、メソッド、コンストラクタ、またはクラスのドキュメンテーション・コメント内でのみ有効です。JavadocツールでのDocコメントの記述方法の@paramに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@param)を参照してください。 +.sp +\fBparameter\-name\fRは、メソッドまたはコンストラクタでのパラメータの名前か、クラス、メソッドまたはコンストラクタの型パラメータの名前になります。山カッコでこのパラメータ名を囲み、型パラメータを使用することを指定します。 +.sp +クラスの型パラメータの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @param <E> Type of element stored in a list\fR +\fB */\fR +\fBpublic interface List<E> extends Collection<E> {\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +メソッドの型パラメータの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @param string the string to be converted\fR +\fB * @param type the type to convert the string to\fR +\fB * @param <T> the type of the element\fR +\fB * @param <V> the value of the element\fR +\fB */\fR +\fB<T, V extends T> V convert(String string, Class<T> type) {\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +@return \fIdescription\fR +.RS 4 +JDK 1\&.0で導入 +.sp +「戻り値」セクションを追加して、descriptionのテキストを書き込みます。このテキストでは、戻り値の型と、取り得る値の範囲について記述する必要があります。このタグは、メソッドのドキュメンテーション・コメントでのみ有効です。JavadocツールでのDocコメントの記述方法の@returnに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@return)を参照してください。 +.RE +.PP +@see \fIreference\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fI「関連項目」\fR見出しを追加して、referenceを指すリンク、またはテキスト・エントリを書き込みます。1つのドキュメンテーション・コメントには任意の数の\fB@see\fRタグを含めることができますが、それらはすべて同じ見出しの下にグループ化されます。\fB@see\fRタグには、3つのタイプの形式があります。この形式が最も一般的です。このタグは、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、またはフィールドで有効です。パッケージ、クラス、またはメンバーに対するインライン・リンクを文中に挿入する方法は、\fB{@link}\fRを参照してください。 +.sp +\fB形式1\fR。@see +\fBstring\fRタグ形式は、\fIstring\fRのテキスト・エントリを追加します。リンクは生成されません。stringは、書籍またはURLではアクセスできない情報の参照先です。\fBjavadoc\fRコマンドは、最初の文字として二重引用符(")を検索して、この形式を前述の形式と区別します。たとえば、\fB@see "The Java Programming Language"\fRは次のテキストを生成します。 +.sp +\fB関連項目\fR: +.sp +"The Java Programming Language" +.sp +\fB形式2\fR。\fB@see <a href="URL#value">label</a>\fRフォームは、\fBURL#value\fRで定義されているようにリンクを追加します。\fBURL#value\fRパラメータは、相対URLまたは絶対URLです。\fBjavadoc\fRコマンドは、最初の文字として「より小さい」記号(\fB<\fR)を検索して、この形式を他の形式と区別します。たとえば、\fB@see <a href="spec\&.html#section">Java Spec</a>\fRは、次のリンクを生成します: +.sp +\fB関連項目\fR: +.sp +Java Spec +.sp +\fB形式3\fR。\fB@see package\&.class#member label\fR形式は、表示テキスト・ラベルとともにリンクを追加します。このラベルは参照されているJava言語の指定された名前のドキュメントを指し示します。ラベルはオプションです。ラベルを省略した場合は、表示テキストのかわりに、名前が適切に短縮されて表示されます。\fB\-noqualifier\fRオプションを使用すると、この表示テキストからパッケージ名が全体的に削除されます。ラベルは、自動生成される表示テキストとは異なる表示テキストにする場合に使用します。「名前が表示される方法」を参照してください。 +.sp +Java SE 1\&.2だけは、ラベルではなく名前が\fB<code>\fR +HTMLタグ内に自動的に表示されます。Java SE 1\&.2\&.2からは、ラベルを使用するかしないかにかかわらず、\fB<code>\fRタグは常に表示テキストを囲む形で含まれます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackage\&.class#member\fRには、参照されている任意の有効なプログラム要素の名前を指定します。つまり、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、またはフィールドの名前です。ただし、メンバー名の前の文字は、シャープ記号(\fB#\fR)にする必要があります。classは、任意のトップレベルまたはネストされたクラスか、インタフェースを表します。memberは、任意のコンストラクタ、メソッドまたはフィールドを表します(ネストされたクラスまたはインタフェースではありません)。この名前が、ドキュメント化されるクラスに含まれている場合、\fBjavadoc\fRコマンドは、その名前へのリンクを作成します。外部参照クラスへのリンクを作成するには、\fB\-link\fRオプションを使用します。参照クラスに属していない名前のドキュメントを参照するには、他の2つの\fB@see\fRタグ形式のどちらかを使用します。「名前の指定」を参照してください。 +.sp +\fB注意:\fR +外部参照クラスは、コマンド行で\fBjavadoc\fRコマンドに渡されないクラスです。生成ドキュメント内で外部参照クラスにリンクしている箇所は、外部参照または外部リンクと呼ばれます。たとえば、\fBjava\&.awt package\fRに対してのみ\fBjavadoc\fRコマンドを実行した場合、\fBObject\fRなどの\fBjava\&.lang\fR内のすべてのクラスが外部参照クラスになります。\fB\-link\fRおよび\fB\-linkoffline\fRオプションを使用して、外部参照クラスへリンクします。外部参照クラスのソース・コメントは\fBjavadoc\fRコマンドの実行には使用できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBlabel\fRは、省略可能なテキストで、リンクのラベルとして表示されます。ラベルには空白を含めることができます。\fBlabel\fRを省略すると、\fBpackage\&.class\&.member\fRが、現在のクラスおよびパッケージに応じて適切に短縮されて表示されます。「名前が表示される方法」を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +空白文字が、\fBpackage\&.class#member\fRと\fBlabel\fRの間の区切り文字になります。カッコの内側の空白文字はラベルの先頭とは解釈されないため、メソッドのパラメータ間に空白文字を入れてもかまいません。 +.RE +.sp +この例では、\fB@see\fRタグ(\fBCharacter\fRクラス内)が、\fBString\fRクラスのequalsメソッドを参照しています。タグには、名前\fBString#equals(Object)\fRとラベル\fBequals\fRの両方の引数が含まれています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @see String#equals(Object) equals\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +標準ドックレットは、次のようなHTMLを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<dl>\fR +\fB<dt><b>See Also:</b>\fR +\fB<dd><a href="\&.\&./\&.\&./java/lang/String#equals(java\&.lang\&.Object)"><code>equals<code></a>\fR +\fB</dl>\fR + +.fi +.if n \{\ +.RE +.\} +前述のコードは、ブラウザに次のように表示され、ラベルは表示リンク・テキストになっています。 +.sp +\fB関連項目\fR: +.sp +equals +.RE +.PP +名前の指定 +.PP +この\fBpackage\&.class#member\fRという名前は、\fBjava\&.lang\&.String#toUpperCase()\fRのような完全修飾名にすることも、\fBString#toUpperCase()\fRや\fB#toUpperCase()\fRのような非完全修飾名にすることもできます。名前が完全修飾より短い場合は、\fBjavadoc\fRコマンドは、標準のJavaコンパイラの検索順序を使用して探します。「@seeタグの検索順序」を参照してください。名前は、メソッド引数の間など、カッコ内のスペースを含めることができます。部分的に修飾した短い名前を指定することの利点は、入力する文字数が減ることや、ソース・コードが読みやすくなることです。次のリストに様々な形式の名前を示します。ここで、\fBClass\fRにはクラスまたはインタフェースを、Typeにはクラス、インタフェース、配列、またはプリミティブを、methodにはメソッドまたはコンストラクタを、それぞれ指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\fBTypical forms for\fR\fR\fB\fB @see package\&.class#member\fR\fR\fB \fR +\fB\fBReferencing a member of the current class\fR\fR +\fB@see #field\fR +\fB@see #method(Type, Type,\&.\&.\&.)\fR +\fB@see #method(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see #constructor(Type, Type,\&.\&.\&.)\fR +\fB@see #constructor(Type argname, Type argname,\&.\&.\&.) \fR + +\fB\fBReferencing another class in the current or imported packages\fR\fR +\fB@see Class#field\fR +\fB@see Class#method(Type, Type,\&.\&.\&.)\fR +\fB@see Class#method(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see Class#constructor(Type, Type,\&.\&.\&.)\fR +\fB@see Class#constructor(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see Class\&.NestedClass\fR +\fB@see Class \fR + +\fB\fBReferencing an element in another package (fully qualified)\fR\fR +\fB@see package\&.Class#field\fR +\fB@see package\&.Class#method(Type, Type,\&.\&.\&.)\fR +\fB@see package\&.Class#method(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see package\&.Class#constructor(Type, Type,\&.\&.\&.)\fR +\fB@see package\&.Class#constructor(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see package\&.Class\&.NestedClass\fR +\fB@see package\&.Class\fR +\fB@see package\fR + +.fi +.if n \{\ +.RE +.\} +.PP +前のリストに関するメモ: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +最初のタイプの形式(パッケージとクラスを省略)の場合、\fBjavadoc\fRコマンドは、現在のクラスの階層のみを検索します。つまり、現在のクラスかインタフェース、そのスーパークラスかスーパーインタフェース、またはその外側を囲んでいるクラスかインタフェースからメンバーを検索します(検索項目1\(en3)。現在のパッケージの他の部分や、他のパッケージは検索しません(検索項目4\(en5)。「@seeタグの検索順序」を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +メソッドまたはコンストラクタの入力時に、\fBgetValue\fRのようにカッコなしの名前を使用した場合、同じ名前のフィールドが存在していなければ、\fBjavadoc\fRコマンドはそのメソッドへのリンクを作成します。このメソッドがオーバーロードされている場合、\fBjavadoc\fRコマンドは、検索で最初に見つかったメソッドにリンクします。結果は前もって特定できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ネストされたクラスは、すべての形式について、\fBouter\&.inner\fRとして指定する必要があります。単純に\fBinner\fRとはしないでください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +すでに述べたように、クラスとメンバーとの間の区切り文字としては、ドット(\fB\&.\fR)ではなくシャープ記号(\fB#\fR)を使用します。このように指定すると、\fBjavadoc\fRコマンドは、あいまいさを解決できます。ドットは、クラス、ネストされたクラス、パッケージ、およびサブパッケージを区切るためにも使用されるからです。ただし、\fBjavadoc\fRコマンドでは、あいまいさがなければドットは正しく解析されますが、警告は表示されます。 +.RE +.PP +@seeタグの検索順序 +.PP +\fBjavadoc\fRコマンドは、ソース・ファイル、パッケージ・ファイル、概要ファイルに表示される\fB@see\fRタグを処理します。後者の2つのファイルでは、完全修飾の名前を\fB@see\fRタグに指定する必要があります。ソース・ファイルでは、完全修飾の名前、または部分修飾の名前を指定できます。 +.PP +次に、\fB@see\fRタグの検索順序を示します。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +現在のクラスまたはインタフェース。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +外側を囲んでいるクラスとインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +スーパークラスとスーパーインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +現在のパッケージ。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 5.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 5." 4.2 +.\} +インポートされているパッケージ、クラス、およびインタフェース(\fBimport\fR文の順序に従って検索)。 +.RE +.PP +\fBjavadoc\fRコマンドは、各クラスについて項目1\-3を再帰的に適用しながら、一致する名前が見つかるまで検索を続けます。つまり、まず現在のクラスを検索し、次にその外側を囲んでいるクラスEを検索した後、Eのスーパークラスを検索してから、Eを囲んでいるクラスを検索します。項目4と5では、\fBjavadoc\fRコマンドが1つのパッケージ内のクラスまたはインタフェースを検索する順序は決まっていません(その順序は、個々のコンパイラによって異なります)。項目5では、\fBjavadoc\fRコマンドは、\fIjava\&.lang\fRを検索します。このパッケージは、すべてのプログラムに自動的にインポートされるからです。 +.PP +\fBjavadoc\fRコマンドは、完全修飾でないソース・ファイルで\fB@see\fRタグを見つけると、Javaコンパイラと同じ順序で指定された名前を検索します(ただし、\fBjavadoc\fRコマンドは、特定の名前空間のあいまいさを検出しません。これは、ソース・コードにこれらのエラーが存在していないことを前提としているためです)。この検索順序は、Java言語仕様で正式に定義されています。\fBjavadoc\fRコマンドは、関連するクラスとパッケージ、およびインポートされたクラスとパッケージのすべてからその名前を検索します。具体的には、次の順序で検索します。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +現在のクラスまたはインタフェース。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +外側を囲んでいるクラスとインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +スーパークラスとスーパーインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +現在のパッケージ。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 5.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 5." 4.2 +.\} +インポートされているパッケージ、クラス、およびインタフェース(\fBimport\fR文の順序に従って検索)。 +.RE +.PP +\fBjavadoc\fRコマンドは、必ずしもサブクラスを検索するとは限りません。また、実行中に他のパッケージのドキュメントが生成される場合でも、他のパッケージを検索しません。たとえば、\fB@see\fRタグが\fBjava\&.awt\&.event\&.KeyEvent\fRクラス内に含まれていて、\fBjava\&.awt package\fR内のある名前を参照していても、そのクラスがインポートしないかぎり\fBjavadoc\fRコマンドはそのパッケージを検索しません。 +.PP +名前が表示される方法 +.PP +\fBlabel\fRを省略すると、\fBpackage\&.class\&.member\fRが表示されます。一般に、これは現在のクラスおよびパッケージに応じて適切に短縮されます。短縮されるとは、\fBjavadoc\fRコマンドにより必要最小限の名前のみが表示されるということです。たとえば、\fBString\&.toUpperCase()\fRメソッドに、同じクラスのメンバーへの参照と他のクラスのメンバーへの参照が含まれている場合、クラス名が表示されるのは後者のケースのみです(次のリストを参照)。パッケージ名を全体的に削除するには、\fB\-noqualifier\fRオプションを使用します。 +.RS 4 +\fB参照のタイプ\fR: \fB@see\fRタグは同じクラス、同じパッケージのメンバーを参照します +.RE +.RS 4 +\fB例\fR: \fB@see String#toLowerCase()\fR +.RE +.RS 4 +\fB表示\fR: \fBtoLowerCase()\fR \- パッケージおよびクラス名を省略します +.RE +.RS 4 +.RE +.RS 4 +\fB参照のタイプ\fR: \fB@see\fRタグは別のクラス、同じパッケージのメンバーを参照します +.RE +.RS 4 +\fB例\fR: \fB@see Character#toLowerCase(char)\fR +.RE +.RS 4 +\fB表示\fR: \fBCharacter\&.toLowerCase(char)\fR \- パッケージ名を省略し、クラス名を含みます +.RE +.RS 4 +.RE +.RS 4 +\fB参照のタイプ\fR: \fB@see\fRタグは異なるクラス、異なるパッケージのメンバーを参照します +.RE +.RS 4 +\fB例\fR: \fB@see java\&.io\&.File#exists()\fR +.RE +.RS 4 +\fB表示\fR: \fBjava\&.io\&.File\&.exists()\fR \- パッケージおよびクラス名を含みます +.RE +.RS 4 +.RE +.PP +@seeタグの例 +.PP +右側のコメントは、\fB@see\fRタグが\fBjava\&.applet\&.Applet\fRなどの別のパッケージのクラス内にある場合に、名前がどのように表示されるかを示しています。JavadocツールでのDocコメントの記述方法の@seeに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@see)を参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB See also:\fR +\fB@see java\&.lang\&.String // String \fR +\fB@see java\&.lang\&.String The String class // The String class \fR +\fB@see String // String \fR +\fB@see String#equals(Object) // String\&.equals(Object) \fR +\fB@see String#equals // String\&.equals(java\&.lang\&.Object) \fR +\fB@see java\&.lang\&.Object#wait(long) // java\&.lang\&.Object\&.wait(long) \fR +\fB@see Character#MAX_RADIX // Character\&.MAX_RADIX \fR +\fB@see <a href="spec\&.html">Java Spec</a> // Java Spec \fR +\fB@see "The Java Programming Language" // "The Java Programming Language" \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB注意:\fR +\fB@se\fR\fBe\fRタグを拡張してドキュメント化されないクラスにリンクするには、\fB\-link\fRオプションを使用します。 +.PP +@serial \fIfield\-description\fR | include | exclude +.RS 4 +JDK 1\&.2で導入 +.sp +デフォルトの直列化可能フィールドのドキュメンテーション・コメントで使用します。クラスの直列化可能なフィールドおよびデータの文書化 +(http://docs\&.oracle\&.com/javase/8/docs/platform/serialization/spec/serial\-arch\&.html#5251)を参照してください +.sp +Oracleの直列化された形式の仕様にクラスを含める基準 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/serialized\-criteria\-137781\&.html)も参照してください +.sp +\fBfield\-description\fR(省略可能)では、フィールドの意味を説明し、取り得る値のリストを示す必要があります。必要な場合は、複数の行に渡って説明を記述できます。標準ドックレットは、この情報を、直列化された形式ページに追加します。相互参照ページを参照してください。 +.sp +クラスを直列化した後に直列化可能フィールドをクラスに追加した場合、主説明に、追加したバージョンを識別する文を追加する必要があります。 +.sp +\fBinclude\fRおよび\fBexclude\fR引数は、直列化された形式ページにクラスまたはパッケージを含めるか除外するかを示します。次のように機能します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSerializable\fRを実装しているpublicまたはprotectedクラスは、そのクラス(またはそのクラスが属するパッケージ)が\fB@serial exclude\fRタグでマークされていないかぎり、含められます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSerializable\fRを実装しているprivateまたはpackage\-privateクラスは、そのクラス(またはそのクラスが属するパッケージ)が\fB@serial include\fRタグでマークされていないかぎり、除外されます。 +.RE +.sp +たとえば、\fBjavax\&.swing\fRパッケージはpackage\&.htmlまたはpackage\-info\&.java内で\fB@serial\fR +\fBexclude\fRタグでマークされています。publicクラス\fBjava\&.security\&.BasicPermission\fRは\fB@serial exclude\fRタグでマークされています。package\-privateクラス\fBjava\&.util\&.PropertyPermissionCollection\fRは\fB@serial include\fRタグでマークされています。 +.sp +クラス・レベルの\fB@serial\fRタグはパッケージ・レベルの\fB@serial\fRタグをオーバーライドします。 +.RE +.PP +@serialData \fIdata\-description\fR +.RS 4 +JDK 1\&.2で導入 +.sp +データの説明値を使用して、直列化された形式でのデータの型と順序をドキュメント化します。このデータには、\fBwriteObject\fRメソッドによって書き込まれる省略可能なデータ、および\fBExternalizable\&.writeExternal\fRメソッドによって書き込まれるすべてのデータ(ベース・クラスを含む)が含まれます。 +.sp +\fB@serialData\fRタグは、\fBwriteObject\fR、\fBreadObject\fR、\fBwriteExternal\fR、\fBreadExternal\fR、\fBwriteReplace\fRおよび\fBreadResolve\fRメソッドのドキュメンテーション・コメントで使用できます。 +.RE +.PP +@serialField \fIfield\-name\fR \fIfield\-type\fR \fIfield\-description\fR +.RS 4 +JDK 1\&.2で導入 +.sp +\fBSerializable\fRクラスの\fBserialPersistentFields\fRメンバーの\fBObjectStreamField\fRコンポーネントをドキュメント化します。\fBObjectStreamField\fRコンポーネントごとに1つの\fB@serialField\fRタグを使用します。 +.RE +.PP +@since \fIsince\-text\fR +.RS 4 +JDK 1\&.1で導入 +.sp +生成ドキュメントに、指定された\fBsince\-text\fRの値の\fI「導入されたバージョン」\fR見出しを追加します。このテキストには、特別な内部構造はありません。このタグは、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、またはフィールドで有効です。このタグは、特定の変更または機能が、\fBsince\-text\fRの値によって指定されたソフトウェア・リリース以降、存在していることを意味します。たとえば、\fB@since 1\&.5\fRです。 +.sp +Javaプラットフォームのソース・コードの場合、\fB@since\fRタグは、JavaプラットフォームAPI仕様のバージョンを示します。ソース・コードがリファレンス実装に追加された時期を示すとは限りません。複数の\fB@since\fRタグを使用でき、複数の\fB@author\fRタグのように扱われます。プログラム要素が複数のAPIで使用される場合、複数のタグを使用できます。 +.RE +.PP +@throws \fIclass\-name\fR \fIdescription\fR +.RS 4 +JDK 1\&.2で導入 +.sp +\fB@exception\fRタグと同じ動作をします。JavadocツールでのDocコメントの記述方法の@throwsに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@exception)を参照してください +.sp +\fB@throws\fRタグは、生成ドキュメントに\fIThrows\fR小見出しを追加して、\fBclass\-name\fRおよび\fBdescription\fRテキストを書き込みます。\fIclass\-name\fRは、そのメソッドからスローされる可能性のある例外の名前です。このタグは、メソッド、コンストラクタのドキュメンテーション・コメント内でのみ有効です。このクラスが完全指定の名前で記述されていない場合、\fBjavadoc\fRコマンドは、検索順序に従ってクラスを探します。複数の\fB@throws\fRタグを、同じ例外または違う例外の指定したドキュメンテーション・コメントで使用できます。「@seeタグの検索順序」を参照してください。 +.sp +すべてのチェック済例外がドキュメント化されるようにするために、\fB@throws\fRタグがthrows節内の例外用に存在しない場合は、\fB@throws\fRタグでドキュメント化されたかのように、\fBjavadoc\fRコマンドによって例外がHTML出力に説明なしで追加されます。 +.sp +オーバーライドされるメソッド内で例外が明示的に宣言されている場合のみ、\fB@throws\fRのドキュメントがそのメソッドからサブクラスにコピーされます。インタフェース・メソッドから実装メソッドにコピーされる場合も同様です。\fB{@inheritDoc}\fRタグを使用して、\fB@throws\fRタグがドキュメンテーションを継承するように強制できます。 +.RE +.PP +{@value \fIpackage\&.class#field\fR} +.RS 4 +JDK 1\&.4で導入 +.sp +定数の値を表示します。\fB{@value}\fRタグが静的フィールドのドキュメンテーション・コメントで引数なしで使用されている場合、その定数の値を表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * The value of this constant is {@value}\&.\fR +\fB */\fR +\fBpublic static final String SCRIPT_START = "<script>"\fR + +.fi +.if n \{\ +.RE +.\} +任意のドキュメンテーション・コメント内で引数\fBpackage\&.class#field\fRありで使用された場合、\fB{@value}\fRタグは指定された定数の値を表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * Evaluates the script starting with {@value #SCRIPT_START}\&.\fR +\fB */\fR +\fBpublic String evalScript(String script) {}\fR + +.fi +.if n \{\ +.RE +.\} +引数\fBpackage\&.class#field\fRは、\fB@see\fRタグ引数と同一の形式になります。ただし、メンバーは静的フィールドである必要があります。 +.sp +これらの定数の値は「定数フィールド値」 +(http://docs\&.oracle\&.com/javase/8/docs/api/constant\-values\&.html)にも表示されます +.RE +.PP +@version \fIversion\-text\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fB\-version\fRオプションが使用されている場合、生成ドキュメントに\fI「バージョン」\fR小見出しを追加して、指定された\fBversion\-text\fRの値を書き込みます。このタグはこのコードが含まれるソフトウェアの現在のリリース番号を保持するためのものであるのに対し、\fB@since\fRタグは、このコードが導入されたリリース番号を保持します。\fBversion\-text\fRの値には、特別な内部構造はありません。JavadocツールでのDocコメントの記述方法の@versionに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@version)を参照してください +.sp +1つのドキュメンテーション・コメントに複数の\fB@version\fRタグを含めることができます。必要に応じて、1つの\fB@version\fRタグに1つのリリース番号を指定することも、複数のリリース番号を指定することもできます。前者の場合は、\fBjavadoc\fRコマンドによって名前と名前の間にカンマ(,)と空白文字が挿入されます。後者の場合は、テキスト全体が解析されることなく、生成ドキュメントにコピーされます。したがって、カンマではなく、各言語に対応した名前区切り文字を使用する必要があるときに、1行に複数の名前を指定できます。 +.RE +.SH "タグを使用できる場所" +.PP +ここでは、タグを使用できる場所について説明します。次のタグがすべてのドキュメンテーション・コメントで使用できます。\fB@see\fR、\fB@since\fR、\fB@deprecated\fR、\fB{@link}\fR、\fB{@linkplain}\fRおよび\fB{@docroot}\fR。 +.SS "概要タグ" +.PP +概要タグは、概要ページのドキュメンテーション・コメントで使用できるタグです(このドキュメンテーション・コメントは、通常overview\&.htmlという名前のソース・ファイル内にあります)。他のドキュメンテーション・コメントの場合と同様に、これらのタグは、主説明の後で使用する必要があります。 +.PP +\fB注意:\fR +Java SE 1\&.2では、概要ドキュメント内の\fB{@link}\fRタグにbugがあります。テキストは正しく表示されますが、リンクが設定されません。現在のところ、\fB{@docRoot}\fRタグは、概要ドキュメント内では機能しません。 +.PP +概要タグは、次のとおりです。 +.PP +@see reference || @since since\-text || @serialField field\-name field\-type field\-description || @author name\-text || @version version\-text || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.SS "パッケージ・タグ" +.PP +パッケージ・タグは、パッケージのドキュメンテーション・コメントで使用できるタグで、ドキュメンテーション・コメントはpackage\&.htmlまたはpackage\-info\&.javaという名前のソース・ファイル内にあります。ここで使用できる\fB@serial\fRタグは、\fBinclude\fRまたは\fBexclude\fR引数を指定したもののみです。 +.PP +パッケージ・タグは、次のとおりです。 +.PP +@see reference || @since since\-text || @serial field\-description | include | exclude || @author name\-text || @version version\-text || {@linkplain package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.SS "クラスおよびインタフェース・タグ" +.PP +次に、クラスまたはインタフェースのドキュメンテーション・コメントで使用できるタグを示します。\fB@serial\fRタグは、\fBinclude\fRまたは\fBexclude\fR引数を指定して、クラスまたはインタフェースのドキュメンテーション内でのみ使用できます。 +.PP +@see reference || @since since\-text || @deprecated deprecated\-text || @serial field\-description | include | exclude || @author name\-text || @version version\-text || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.PP +クラス・コメントの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * A class representing a window on the screen\&.\fR +\fB * For example:\fR +\fB * <pre>\fR +\fB * Window win = new Window(parent);\fR +\fB * win\&.show();\fR +\fB * </pre>\fR +\fB *\fR +\fB * @author Sami Shaio\fR +\fB * @version 1\&.13, 06/08/06\fR +\fB * @see java\&.awt\&.BaseWindow\fR +\fB * @see java\&.awt\&.Button\fR +\fB */\fR +\fBclass Window extends BaseWindow {\fR +\fB \&.\&.\&.\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SS "フィールド・タグ" +.PP +これらのタグは、フィールドに表示できます。 +.PP +@see reference || @since since\-text || @deprecated deprecated\-text || @serial field\-description | include | exclude || @serialField field\-name field\-type field\-description || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || {@value package\&.class#field} +.PP +フィールド・コメントの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB /**\fR +\fB * The X\-coordinate of the component\&.\fR +\fB *\fR +\fB * @see #getLocation()\fR +\fB */\fR +\fB int x = 1263732;\fR + +.fi +.if n \{\ +.RE +.\} +.SS "コンストラクタとメソッド・タグ" +.PP +次に、コンストラクタまたはメソッドのドキュメンテーション・コメントで使用できるタグを示します。ただし、\fB@return\fRはコンストラクタでは使用できず、 +\fB{@inheritDoc}\fRには制限があります。 +.PP +@see reference || @since since\-text || @deprecated deprecated\-text || @param parameter\-name description || @return description || @throws class\-name description || @exception class\-name description || @serialData data\-description || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@inheritDoc} || {@docRoot} +.PP +\fB注意:\fR +\fB@serialData\fRタグは、\fBwriteObject\fR、\fBreadObject\fR、\fBwriteExternal\fR、\fBreadExternal\fR、\fBwriteReplace\fRおよび\fBreadResolve\fRメソッドのドキュメンテーション・コメントでのみ使用できます。 +.PP +メソッド・コメントの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * Returns the character at the specified index\&. An index \fR +\fB * ranges from <code>0</code> to <code>length() \- 1</code>\fR +\fB *\fR +\fB * @param index the index of the desired character\&.\fR +\fB * @return the desired character\&.\fR +\fB * @exception StringIndexOutOfRangeException \fR +\fB * if the index is not in the range <code>0</code> \fR +\fB * to <code>length()\-1</code>\fR +\fB * @see java\&.lang\&.Character#charValue()\fR +\fB */\fR +\fB public char charAt(int index) {\fR +\fB \&.\&.\&.\fR +\fB }\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\fBjavadoc\fRコマンドは、ドックレットを使用して出力を決定します。\fBjavadoc\fRコマンドは、\fB\-doclet\fRオプションでカスタム・ドックレットが指定されている場合以外は、デフォルトの標準ドックレットを使用します。\fBjavadoc\fRコマンドには、任意のドックレットとともに使用できるコマンド行オプションがあります。これらのオプションについては、Javadocオプションで説明します。標準ドックレットでは、この他に、いくつかの追加のコマンド行オプションが提供されます。これらのオプションについては、標準ドックレットのオプションで説明します。どのオプション名も、大文字と小文字が区別されません。ただし、オプションの引数では、大文字と小文字が区別されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javadocオプションも参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +標準ドックレットのオプションも参照してください +.RE +.PP +オプションは次のとおりです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-1\&.1 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-author +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-bootclasspath classpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-bottom text +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-breakiterator +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-charset name +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-classpath classpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-d directory +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-docencoding name +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-docfilesubdirs +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-doclet class +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-docletpath classpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-doctitle title +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-encoding +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-exclude packagename1:packagename2:\&.\&.\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-excludedocfilessubdir name1:name2 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-extdirs dirist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-footer footer +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-group groupheading packagepattern:packagepattern +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-header header +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-help +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-helpfile path\efilename +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-Jflag +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-javafx +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-keywords +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-link extdocURL +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-linkoffline extdocURL packagelistLoc +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-linksource +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-locale language_country_variant +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nocomment +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nodeprecated +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nodeprecatedlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nohelp +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-noindex +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nonavbar +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-noqualifier all | packagename1:packagename2\&.\&.\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nosince +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-notimestamp +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-notree +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-overview path/filename +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-package +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-private +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-protected +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-public +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-quiet +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-serialwarn +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-source release +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-sourcepath sourcepathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-sourcetab tablength +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-splitindex +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-stylesheet path/filename +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-tag tagname:Xaoptcmf:"taghead" +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-subpackages package1:package2:\&.\&.\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-taglet class +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-tagletpath tagletpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-title title +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-top +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-use +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-verbose +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-version +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-windowtitle title +.RE +.PP +次のオプションは、すべてのドックレットに使用可能なコアのJavadocオプションです。標準ドックレットでは、ドックレットの他の部分を提供します。\fB\-bootclasspath\fR、\fB\-breakiterator\fR、\fB\-classpath\fR、\fB\-doclet\fR、\fB\-docletpath\fR、\fB\-encoding\fR、\-\fBexclude\fR、\fB\-extdirs\fR、\fB\-help\fR、\fB\-locale\fR、\fB\-\fR\fBoverview\fR、\fB\-package\fR、\fB\-private\fR、\fB\-protected\fR、\fB\-public\fR、\fB\-quiet\fR、\fB\-source\fR、\fB\-sourcepath\fR、\fB\-subpackages\fRおよび\fB\-verbose\fR。 +.SS "Javadocオプション" +.PP +\-overview \fIpath/filename \fR +.RS 4 + +\fBjavadoc\fRコマンドに対して、\fIpath/filename \fRで指定されたソース・ファイルから概要ドキュメント用のテキストを取得し、そのテキストを概要ページ(overview\-summary\&.html)に配置するように指定します。\fIpath/filename\fRは、現在のディレクトリからの相対パスです。 +.sp +\fBfilename\fRの値で任意の名前を使用し、pathで任意の配置先を指定できますが、通常はoverview\&.htmlという名前を付け、ソース・ツリー内の最上位パッケージ・ディレクトリを含むディレクトリに配置します。この場所に配置すると、パッケージをドキュメント化するときにpathを指定する必要がなくなります。これは、\fB\-sourcepath\fRオプションによってこのファイルが指し示されるからです。 +.sp +たとえば、\fBjava\&.lang\fRパッケージのソース・ツリーが/src/classes/java/lang/の場合、概要ファイルを/src/classes/overview\&.htmlに配置できます +.sp +実際の例を参照してください。 +.sp +\fIpath/filename\fRで指定するファイルについては、概要コメント・ファイルを参照してください。 +.sp +「概要」ページが作成されるのは、\fBjavadoc\fRコマンドに複数のパッケージ名を渡した場合のみです。詳細は、HTMLフレームを参照してください。「概要」ページのタイトルは、\fB\-doctitle\fRによって設定されます。 +.RE +.PP +\-Xdoclint:(all|none|[\-]\fI<group>\fR) +.RS 4 +不正な参照、アクセシビリティの欠落およびJavadocコメントの不足の警告をレポートし、無効なJavadoc構文および不足しているHTMLタグのエラーをレポートします。 +.sp +このオプションにより、\fBjavadoc\fRコマンドは生成された出力に含まれるすべてのドキュメント・コメントをチェックします。通常どおり、標準オプション\fB\-public\fR、\fB\-protected\fR、\fB\-package\fRおよび\fB\-private\fRで生成された出力に含む項目を選択できます。 +.sp +\fB\-Xdoclint\fRが有効になっている場合は、\fBjavac\fRコマンドと同様にメッセージで問題がレポートされます。\fBjavadoc\fRコマンドは、メッセージ、ソース・ファイルのコピーおよびエラーが検出された正確な位置を指すキャレットを出力します。メッセージは、重大度、および生成されたドキュメントがバリデータを使用して実行された場合にエラーが発生する可能性に応じて、警告またはエラーになります。たとえば、不正な参照またはJavadocコメントの欠落は、\fBjavadoc\fRコマンドが無効なHTMLを生成する原因にならないため、これらの問題は警告としてレポートされます。構文エラーまたはHTML終了タグの欠落は、\fBjavadoc\fRコマンドが無効なHTMLを生成する原因になるため、これらの問題はエラーとしてレポートされます。 +.sp +デフォルトでは、\fB\-Xdoclint\fRオプションは有効になっています。オプション\fB\-Xdoclint:none\fRで無効にします。 +.sp +\fB\-Xdoclint\fRオプションでレポートされる内容は次のオプションで変更します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint none\fR: +\fB\-Xdoclint\fRオプションを無効にします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint \fR\fIgroup\fR: +\fIgroup\fRチェックを有効にします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint all\fR: すべてのチェック・グループを有効にします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint all,\fR\fI\-group\fR: +\fIgroup\fRチェック以外のすべてを有効にします。 +.RE +.sp +変数\fIgroup\fRは次のいずれかの値を持ちます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBaccessibility\fR: アクセシビリティ・チェッカで検出する問題をチェックします(たとえば、\fB<table>\fRタグで指定されるno captionまたはsummary属性)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBhtml\fR: インライン要素へのブロック要素の挿入や終了タグを必要とする要素を終了しないなど、上位レベルHTMLの問題を検出します。ルールは、HTML 4\&.01仕様から導出されます。このタイプのチェックは、\fBjavadoc\fRコマンドを有効にして、ブラウザが受け入れる可能性のあるHTMLの問題を検出します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmissing\fR: 欠落しているJavadocコメントまたはタグをチェックします(たとえば、欠落しているコメントやクラス、または欠落している\fB@return\fRタグやメソッド上の同様のタグ)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBreference\fR: JavadocタグのJava API要素の参照に関連する問題をチェックします(たとえば、\fB@see\fRで見つからない項目、または\fB@param\fRの後の不正な名前)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBsyntax\fR: エスケープされていない山カッコ(\fB<\fRおよび\fB>\fR)やアンパサンド(\fB&\fR)、無効なJavadocタグなどの下位レベルの問題を確認します。 +.RE +.sp +\fB\-Xdoclint\fRオプションを複数回指定して、複数のカテゴリのエラーと警告をチェックするオプションを有効にできます。または、前のオプションを使用して、複数のエラーおよび警告カテゴリを指定できます。たとえば、次のコマンドのいずれかを使用して、\fIfilename\fRファイル内のHTML、構文およびアクセシビリティの問題をチェックします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-Xdoclint:html \-Xdoclint:syntax \-Xdoclint:accessibility \fR\fB\fIfilename\fR\fR +\fBjavadoc \-Xdoclint:html,syntax,accessibility \fR\fB\fIfilename\fR\fR + +.fi +.if n \{\ +.RE +.\} +\fB注意:\fR +\fBjavadoc\fRコマンドでは、これらのチェックの完全性は保証されません。具体的には、完全なHTMLコンプライアンス・チェッカではありません。\-\fBXdoclint\fRオプションの目的は、\fBjavadoc\fRコマンドを有効にして一般的なエラーの大半をレポートすることです。 +.sp +\fBjavadoc\fRコマンドは、無効な入力の修正を試行せず、レポートのみ行います。 +.RE +.PP +\-public +.RS 4 +publicクラスおよびメンバーのみ表示します。 +.RE +.PP +\-protected +.RS 4 +protectedおよびpublicのクラスとメンバーのみを表示します。これがデフォルトです。 +.RE +.PP +\-package +.RS 4 +package、protected、およびpublicのクラスとメンバーのみ表示します。 +.RE +.PP +\-private +.RS 4 +すべてのクラスとメンバーを表示します。 +.RE +.PP +\-help +.RS 4 +オンライン・ヘルプを表示します。\fBjavadoc\fRと\fBドックレット\fRのコマンド行オプションがリストされます。 +.RE +.PP +\-doclet \fIclass\fR +.RS 4 +ドキュメントの生成に使用するドックレットを起動するためのクラス・ファイルを指定します。完全修飾名を使用します。このドックレットにより、出力の内容と形式が定義されます。\fB\-doclet\fRオプションが使用されていない場合、\fBjavadoc\fRコマンドは、標準ドックレットを使用してデフォルトのHTML形式を生成します。このクラスには\fBstart(Root)\fRメソッドが含まれている必要があります。この起動クラスへのパスは\fB\-docletpath\fRオプションによって定義されます。ドックレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html)を参照してください +.RE +.PP +\-docletpath \fIclasspathlist\fR +.RS 4 +\fB\-doclet\fRオプションで指定されたドックレット開始クラス・ファイル、およびそのクラスが依存するすべてのJARファイルへのパスを指定します。開始クラス・ファイルがJARファイル内にある場合、このオプションでJARファイルへのパスを指定します。絶対パスまたは現在のディレクトリからの相対パスを指定できます。\fBclasspathlist\fRに複数のパスやJARファイルが含まれる場合には、それらをSolarisの場合はコロン(:)で、Windowsの場合はセミコロン(;)でそれぞれ区切ります。目的のドックレット開始クラスがすでに検索パス内にある場合は、このオプションは不要です。ドックレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html)を参照してください +.RE +.PP +\-1\&.1 +.RS 4 +Javadoc 1\&.4から削除され、代替はありません。このオプションは、Javadoc 1\&.1によって生成されるのと同じ外見と機能を持つドキュメントを作成するためのものでした(ネストされたクラスはサポートされていません)。このオプションが必要な場合は、Javadoc 1\&.2または1\&.3をかわりに使用してください。 +.RE +.PP +\-source \fIrelease\fR +.RS 4 +受け付けるソース・コードのリリースを指定します。\fBrelease\fRパラメータには次の値を指定できます。\fBjavac\fRコマンドでコードをコンパイルするときに使用する値に対応する\fBリリース\fRの値を使用します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBリリース値: 1\&.5\fR。\fBjavadoc\fRコマンドは、JDK 1\&.5で導入された総称および他の言語機能を含むコードを受け付けます。\fB\-source\fRオプションが使用されなかった場合のコンパイラのデフォルト動作は、1\&.5のものになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBリリース値: 1\&.4\fR。\fBjavadoc\fRコマンドは、JDK 1\&.4で導入されたアサーションを含むコードを受け付けます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBリリース値: 1\&.3\fR。\fBjavadoc\fRコマンドは、JDK 1\&.3以降に導入されたアサーション、総称、または他の言語機能をサポートしません。 +.RE +.RE +.PP +\-sourcepath \fIsourcepathlist\fR +.RS 4 +パッケージ名または\fB\-subpackages\fRオプションを\fBjavadoc\fRコマンドに渡すときに、ソース・ファイルを見つけるための検索パスを指定します。 +.sp +複数のパスはコロン(:)で区切ります。 +.sp +\fBjavadoc\fRコマンドは、指定されたパス以下のすべてのサブディレクトリを検索します。このオプションを使用して、ドキュメント化されるソース・ファイルの位置のみでなく、それ自体はドキュメント化されないがドキュメント化されるソース・ファイルから継承されたコメントを持つソース・ファイルの位置も確認できます。 +.sp +\fB\-sourcepath\fRオプションを使用できるのは、\fBjavadoc\fRコマンドにパッケージ名を渡す場合のみです。\fBjavadoc\fRコマンドに渡されるソース・ファイルは検索されません。ソース・ファイルを特定するには、そのディレクトリに移動するか、「1つ以上のクラスのドキュメント化」に示すように各ファイルの前にパスを含めます。\fB\-sourcepath\fRが省略された場合、\fBjavadoc\fRコマンドは、クラス・パスを使用してソース・ファイルを検索します(\fB\-classpath\fRを参照)。デフォルトの\fB\-sourcepath\fRは、クラス・パスの値です。\fB\-classpath\fRを省略してパッケージ名を\fBjavadoc\fRコマンドに渡すと、\fBjavadoc\fRコマンドは現在のディレクトリ(およびそのサブディレクトリ)からソース・ファイルを検索します。 +.sp +\fBsourcepathlist\fRには、ドキュメント化するパッケージのソース・ツリーのルート・ディレクトリを設定します。 +.sp +たとえば、\fBcom\&.mypackage\fRという名前のパッケージをドキュメント化する場合に、そのソース・ファイルが/home/user/src/com/mypackage/*\&.javaにあるとします。ソース・パスをcom\emypackageが含まれるディレクトリ/home/user/srcに指定してから、次のように、パッケージ名を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user/src/ com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +ソース・パスの値とパッケージ名を連結して、ドットをスラッシュ(/)に変更すると、次のように、パッケージのフルパスになります。 +.sp +/home/user/src/com/mypackage +.sp +2つのソース・パスを設定するには、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user1/src:/home/user2/src com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-classpath \fIclasspathlist\fR +.RS 4 +\fBjavadoc\fRコマンドが参照クラスの検索を行うときに使用するパスを指定します。参照クラスとは、ドキュメント化されるクラスと、それらのクラスによって参照されるすべてのクラスのことです。 +.sp +複数のパスはコロン(:)で区切ります。 +.sp +\fBjavadoc\fRコマンドは、指定されたパス以下のすべてのサブディレクトリを検索します。\fBclasspathlist\fRの値を指定するときは、クラス・パスのドキュメントにある指示に従ってください。 +.sp +\fB\-sourcepath\fRが省略された場合、\fBjavadoc\fRコマンドは\fB\-classpath\fRを使用して、ソース・ファイルおよびクラス・ファイルを検索します(後方互換性のため)。ソース・ファイルとクラス・ファイルを別々のパスから検索する必要がある場合は、\fB\-sourcepath\fRと\fB\-classpath\fRの両方を使用します。 +.sp +たとえば、\fBcom\&.mypackage\fRをドキュメント化する場合に、そのソース・ファイルがディレクトリ/home/user/src/com/mypackageにあり、このパッケージが/home/user/lib内のライブラリに依存しているとき、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user/lib \-classpath /home/user/src com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +他のツールと同様に、\fB\-classpath\fRが指定されていない場合、\fBCLASSPATH\fR環境変数が設定されていれば、\fBjavadoc\fRコマンドはその環境変数を使用します。どちらも設定されていない場合、\fBjavadoc\fRコマンドは現在のディレクトリからクラスを検索します。 +.sp +\fBjavadoc\fRコマンドが\fB\-classpath\fRを使用してユーザー・クラスを検索する方法についての、拡張機能クラスやブートストラップ・クラスに関連した詳細は、クラスの検索方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html)を参照してください。 +.sp +*のベース名を含むクラス・パス要素は、\fB\&.jar\fRまたは\fB\&.JAR\fRを拡張子に持つディレクトリ内のすべてのファイルのリストを指定するのと同等とみなされます。 +.sp +たとえば、ディレクトリ\fBmydir\fRに\fBa\&.jar\fRと\fBb\&.JA\fRRが含まれている場合、クラス・パス要素\fBfoo/*\fRは\fBA\&.jar:b\&.JAR\fRに展開されますが、JARファイルの順番は未指定となります。非表示のファイルを含む、指定したディレクトリ内のすべてのJARファイルがリストに含まれます。*からなるクラス・パス・エントリは、現在のディレクトリ内のすべてのJARファイルのリストに展開されます。\fBCLASSPATH\fR環境変数も同様に展開されます。クラス・パスのワイルドカードの展開は、Java Virtual Machine (JVM)の開始前に行われます。Javaプログラムは、System\&.getenv(\fB"CLASSPATH"\fR)の呼び出しによってなど、環境を問い合せる場合を除き、展開されていないワイルドカードを参照しません。 +.RE +.PP +\-subpackages \fIpackage1:package2:\&.\&.\&.\fR +.RS 4 +ソース・ファイルから指定されたパッケージおよびそのサブパッケージ内に再帰的にドキュメントを生成します。このオプションは、ソース・コードに新しいサブパッケージを追加する際に便利です。新しいサブパッケージが自動的に組み込まれるからです。各package引数は、任意の最上位サブパッケージ(\fBjava\fRなど)または完全修飾パッケージ(\fBjavax\&.swing\fRなど)になります。ソース・ファイルを含める必要はありません。引数は、すべてのオペレーティング・システムで、コロンで区切られます。ワイルドカードは使用できません。パッケージの検索場所を指定するには、\fB\-sourcepath\fRを使用します。このオプションでは、ソース・ツリー内に存在するがパッケージに含まれないソース・ファイルを処理しません。ソース・ファイルの処理を参照してください。 +.sp +たとえば、次のコマンドは、\fBjava\fRおよび\fBjavax\&.swing\fRという名前のパッケージとこれらのサブパッケージ全部のドキュメントを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d docs \-sourcepath /home/user/src \-subpackages java:javax\&.swing \fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-exclude \fIpackagename1:packagename2:\&.\&.\&.\fR +.RS 4 +指定されたパッケージとそのサブパッケージを\fB\-subpackages\fRによって作成されたリストから無条件に除外します。過去または将来の\fB\-subpackages\fRオプションの指定によって組み込まれるパッケージも除外の対象となります。 +.sp +次の例では、\fBjava\&.io\fR、\fBjava\&.util\fR、\fBjava\&.math\fRなどは組み込まれますが、\fBjava\&.net\fRと\fBjava\&.lang\fRをルートに持つパッケージは除外されます。\fBjava\&.lang\fRのサブパッケージである\fBjava\&.lang\&.ref\fRが除外される点に注意してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user/src \-subpackages java \-exclude \fR +\fB java\&.net:java\&.lang\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-bootclasspath \fIclasspathlist\fR +.RS 4 +ブート・クラスが存在するパスを指定します。ブート・クラスとは、通常、Javaプラットフォーム・クラスのことです。\fBbootclasspath\fRは、\fBjavadoc\fRコマンドがソース・ファイルとクラス・ファイルを探すときに使用する検索パスの一部です。詳細は、クラスの検出方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html)を参照してください +.sp +\fBclasspathlist\fRパラメータ内のディレクトリは、セミコロン(;)で区切る(Windowsの場合)か、コロン(:)で区切ります(Oracle Solarisの場合)。 +.RE +.PP +\-extdirs \fIdirist\fR +.RS 4 +拡張機能クラスが存在するディレクトリを指定します。拡張機能クラスとは、Java拡張機能機構を使用するすべてのクラスです。\fBextdirs\fRオプションは、\fBjavadoc\fRコマンドがソース・ファイルとクラス・ファイルを探すときに使用する検索パスの一部です。詳細は、\fB\-classpath\fRオプションを参照してください。\fBdirlist\fR内のディレクトリは、セミコロン(;)で区切る(Windowsの場合)か、コロン(:)で区切ります(Oracle Solarisの場合)。 +.RE +.PP +\-verbose +.RS 4 +\fBjavadoc\fRコマンドの実行中に詳細なメッセージを表示します。\fBverbose\fRオプションを指定しないと、ソース・ファイルのロード時、ドキュメントの生成時(ソース・ファイルごとに1つのメッセージ)、およびソート時にメッセージが表示されます。verboseオプションを指定すると、各Javaソース・ファイルの解析に要した時間(ミリ秒単位)を示す追加のメッセージが表示されます。 +.RE +.PP +\-quiet +.RS 4 +メッセージを抑制し、警告とエラーのみが表示されるようにして、これらを確認しやすくします。\fBversion\fR文字列も抑止します。 +.RE +.PP +\-breakiterator +.RS 4 +英語の場合、パッケージ、クラスまたはメンバーの主説明の最初の文の終わりを判断する際に、\fBjava\&.text\&.BreakIterator\fRの国際化された文境界を使用します。他のすべてのロケールは、英語言語というロケール固有のアルゴリズムではなく、すでに\fBBreakIterator\fRクラスを使用しています。最初の文は、パッケージ、クラス、またはメンバーのサマリーにコピーされ、アルファベット順の索引にコピーされます。JDK 1\&.2以降、\fBBreakIterator\fRクラスは、英語を除くすべての言語の文の終わりを判断するために、すでに使用されています。したがって、\fB\-breakiterator\fRオプションは、1\&.2以降では英文以外には効果がありません。英文には、次のような独自のデフォルトのアルゴリズムがあります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +英文のデフォルトの文区切りアルゴリズム。空白文字またはHTMLブロック・タグ(\fB<P>\fRなど)が続くピリオドで停止します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +breakiterator文区切りアルゴリズム。次の語が大文字で始まる場合、空白文字が続くピリオド、疑問符、または感嘆符で停止します。このアルゴリズムでは「The serial no\&. is valid」など、ほとんどの省略表記が処理されますが、「Mr\&. Smith」は処理されません。\fB\-breakiterator\fRオプションでは、HTMLタグや、数字または記号で始まる文では停止しません。HTMLタグに埋め込まれている場合でも、アルゴリズムは「\&.\&./filename」の最後のピリオドで停止します。 +.RE +.sp +Java SE 1\&.5では\fB\-breakiterator\fR警告メッセージが削除され、デフォルトの文区切りアルゴリズムは変更されていません。ソース・コードを変更せず、SE 1\&.4\&.xでの\fB\-breakiterator\fRオプションの警告を除去していない場合でも、何もする必要はありません。Java SE 1\&.5\&.0からは警告は消滅しています。 +.RE +.PP +\-locale \fIlanguage_country_variant\fR +.RS 4 +\fBjavadoc\fRコマンドがドキュメントを生成するときに使用するロケールを指定します。この引数は、\fBj\fR\fBava\&.util\&.Locale\fRドキュメントで説明しているように、\fBen_US\fR +(英語、米国)または\fBen_US_WIN\fR +(Windowsバリアント)などのロケールの名前です。 +.sp +\fB注意:\fR +\fB\-locale\fRオプションは、標準ドックレットが提供するすべてのオプション、またはその他の任意のドックレットが提供するすべてのオプションより前(左側)に指定する必要があります。そうしないと、ナビゲーション・バーが英語で表示されます。このコマンド行オプションのみ、指定する順序に依存します。標準ドックレットのオプションを参照してください。 +.sp +ロケールを指定すると、指定したロケールのリソース・ファイルが\fBjavadoc\fRコマンドによって選択されて、メッセージ(ナビゲーション・バー、リストと表の見出し、ヘルプ・ファイルの目次、stylesheet\&.cssのコメントなどの文字列)のために使用されます。また、アルファベット順にソートされるリストのソート順、および最初の文の終わりを判断するための文の区切り文字も、指定したロケールによって決まります。\fB\-locale\fRオプションは、ドキュメント化されるクラスのソース・ファイル内で指定されているドキュメンテーション・コメントのテキストのロケールを決定するものではありません。 +.RE +.PP +\-encoding +.RS 4 +ソース・ファイルのエンコーディングの名前(\fBEUCJIS/SJIS\fRなど)を指定します。このオプションが指定されていない場合は、プラットフォームのデフォルト・コンバータが使用されます。およびオプションも参照してください。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjavadoc\fRコマンドを実行するJava Runtime Environment (JRE)に、\fBflag\fRを直接渡します。たとえば、生成ドキュメントを処理するためにシステムで32MBのメモリーを確保しておく必要がある場合は、\fB\-Xmx\fRオプションを次のように呼び出します。\fBjavadoc \-J\-Xmx32m \-J\-Xms32m com\&.mypackage\fR。\fB\-Xms\fRは省略可能で、これは初期メモリーのサイズを設定するのみのオプションで、必要なメモリーの最小量がわかっている場合に便利です。 +.sp +\fBJ\fRと\fBflag\fRの間に空白文字はありません。 +.sp +使用している\fBjavadoc\fRコマンドのバージョンを確認するには\fB\-version\fRオプションを使用します。出力ストリームには標準ドックレットのバージョン番号が含まれます。Javadocコマンドの実行を参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-J\-version\fR +\fBjava version "1\&.7\&.0_09"\fR +\fBJava(TM) SE Runtime Environment (build 1\&.7\&.0_09\-b05)\fR +\fBJava HotSpot(TM) 64\-Bit Server VM (build 23\&.5\-b02, mixed mode)\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-javafx +.RS 4 +標準ドックレットに対してJavaFX拡張機能を使用して、HTMLドキュメントを生成します。生成されたドキュメントには、標準Javaドックレットで生成された他のサマリー・セクションに加えて「プロパティのサマリー」セクションが含まれています。リストされたプロパティは、各プロパティのgetterおよびsetterメソッドのセクションにリンクされます。 +.sp +getterおよびsetterメソッドに対して明示的に記載されているドキュメント・コメントがない場合、プロパティ・メソッドのドキュメント・コメントがこれらのメソッドに対して生成されたドキュメントに自動的にコピーされます。このオプションは、プロパティのデフォルト値を記述できる新しい\fB@defaultValue\fRタグも追加します。 +.sp +例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-javafx MyClass\&.java \-d testdir\fR +.fi +.if n \{\ +.RE +.\} +.RE +.SS "標準ドックレットのオプション" +.PP +\-d \fIdirectory\fR +.RS 4 +\fBjavadoc\fRコマンドが生成されたHTMLファイルを保存する生成先ディレクトリを指定します。\fB\-d\fRオプションを省略すると、ファイルは現在のディレクトリに保存されます。\fBdirectory\fRの値には、絶対ディレクトリ、または現在の作業ディレクトリからの相対ディレクトリを指定できます。Java SE 1\&.4では、\fBjavadoc\fRコマンドを実行すると生成先ディレクトリが自動的に作成されます。 +.sp +たとえば、次の例では、\fBcom\&.mypackage\fRパッケージのドキュメントが生成され、その結果が/user/doc/ディレクトリに保存されます。\fBjavadoc \-d \fR\fB/user/doc/ \fR\fBcom\&.mypackage\fR +.RE +.PP +\-use +.RS 4 +ドキュメント化されるクラスおよびパッケージごとに1つの「使用」ページを組み込みます。このページには、その特定のクラスまたはパッケージのAPIを使用しているパッケージ、クラス、メソッド、コンストラクタ、およびフィールドが記述されます。たとえば、クラスCを例にとると、クラスCを使用しているものとしては、Cのサブクラス、Cとして宣言されているフィールド、Cを返すメソッド、および型Cのパラメータを持つメソッドとコンストラクタがあります。たとえば、\fBString\fR型用の「使用」ページを表示できます。\fBjava\&.awt\&.Font\fRクラスの\fBgetName\fRメソッドは\fBString\fR型を戻すので、\fBgetName\fRメソッドは\fBString\fRを使用し、\fBgetName\fRメソッドが\fBString\fR用の「使用」ページに表示されます。これは実装ではなくAPIの使用のみをドキュメント化します。メソッドがその実装で\fBString\fRを使用するが、引数として文字列を取らない、または文字列を返さない場合、それは\fBString\fRの使用とはみなされません。生成された「使用」ページにアクセスするには、クラスまたはパッケージに移動し、ナビゲーション・バーの\fBリンクの使用\fRをクリックします。 +.RE +.PP +\-version +.RS 4 +生成ドキュメントに、@versionのテキストを組み込みます。このテキストは、デフォルトでは省略されます。使用している\fBjavadoc\fRコマンドのバージョンを確認するには\fB\-J\-version\fRオプションを使用します。 +.RE +.PP +\-author +.RS 4 +生成ドキュメントに、\fB@author\fRのテキストを組み込みます。 +.RE +.PP +\-splitindex +.RS 4 +索引ファイルをアルファベットごとに複数のファイルに分割し、文字ごとに1つのファイルと、アルファベット以外の記号で始まる索引エントリ用に1つのファイルを作成します。 +.RE +.PP +\-windowtitle \fItitle\fR +.RS 4 +HTMLの\fB<title>\fRタグに配置するタイトルを指定します。\fBtitle\fRタグに指定したテキストは、ウィンドウのタイトルや、このページに対して作成されたブラウザのブックマーク(お気に入り)に表示されます。このタイトルにはHTMLタグを含めないでください。タイトルにHTMLタグが含まれていると、ブラウザがタグを正しく解釈できません。\fBtitle\fRタグ内の内部の二重引用符はエスケープ文字を使用してマークします。\fB\-windowtitle\fRオプションを省略すると、\fBjavadoc\fRコマンドは、\fB\-windowtitle\fRオプションのかわりに、\fB\-doctitle\fRオプションの値を使用します。たとえば、\fBjavadoc \-windowtitle "Java SE Platform" com\&.mypackage\fRです。 +.RE +.PP +\-doctitle \fItitle\fR +.RS 4 +概要サマリー・ファイルの最上部の近くに配置するタイトルを指定します。\fBtitle\fRタグに指定したテキストは中央揃えになり、レベル1の見出しとして、上部ナビゲーション・バーのすぐ下に置かれます。\fBtitle\fRタグにはHTMLタグおよび空白文字を含めることができますが、その場合、タイトルを引用符で囲む必要があります。\fBtitle\fRタグの内部で引用符を使用する場合は、エスケープする必要があります。たとえば、\fBjavadoc \-header "<b>Java Platform </b><br>v1\&.4" com\&.mypackage\&.\fRとなります。 +.RE +.PP +\-title \fItitle\fR +.RS 4 +すでに存在しません。Javadoc 1\&.2のベータ版にしか存在していませんでした。このオプションは、\fB\-doctitle\fRという名前に変更されました。名前を変更した理由は、このオプションが、ウィンドウのタイトルではなくドキュメントのタイトルを定義することを明確にするためです。 +.RE +.PP +\-header \fIheader\fR +.RS 4 +各出力ファイルの最上部に配置するヘッダー・テキストを指定します。ヘッダーは、ナビゲーション・バーの右上に配置されます。\fBheader\fRにはHTMLタグおよび空白文字を含めることができますが、その場合、\fBheader\fRを引用符で囲む必要があります。ヘッダー内部の引用符にはエスケープ文字を使用します。たとえば、\fBjavadoc \-header "<b>Java Platform </b><br>v1\&.4" com\&.mypackage\&.\fRとなります。 +.RE +.PP +\-footer \fIfooter\fR +.RS 4 +各出力ファイルの最下部に配置するフッター・テキストを指定します。\fIfooter\fRの値は、ナビゲーション・バーの右下に配置されます。\fBfooter\fRにはHTMLタグおよび空白文字を含めることができますが、その場合、\fBfooter\fRを引用符で囲む必要があります。フッター内部の引用符にはエスケープ文字を使用します。 +.RE +.PP +\-top +.RS 4 +各出力ファイルの最上部に配置するテキストを指定します。 +.RE +.PP +\-bottom \fItext\fR +.RS 4 +各出力ファイルの最下部に配置するテキストを指定します。このテキストは、下部ナビゲーション・バーより下の、ページの最下部に配置されます。テキストにはHTMLタグおよび空白文字を含めることができますが、その場合、テキストを引用符で囲む必要があります。テキスト内部の引用符にはエスケープ文字を使用します。 +.RE +.PP +\-link \fIextdocURL\fR +.RS 4 +既存のJavadocにより生成された外部参照クラスのドキュメントへのリンクを作成します。\fIextdocURL\fR引数は、リンク先として指定する、Javadocにより生成された外部ドキュメントを含むディレクトリの絶対URLまたは相対URLです。指定した\fBjavadoc\fRコマンドの実行で、複数の\fB\-link\fRオプションを指定して複数のドキュメントへのリンクを作成できます。 +.sp +このディレクトリ内にpackage\-listファイルが存在する必要があります(存在しない場合は、\fB\-linkoffline\fRオプションを使用します)。\fBjavadoc\fRコマンドは、package\-listファイルからパッケージ名を読み取った後、そのURLでこれらのパッケージにリンクします。\fBjavadoc\fRコマンドの実行時に、\fBextdocURL\fRの値が、作成された\fB<A HREF>\fRリンク内にコピーされます。したがって、\fBextdocURL\fRはファイルではなくディレクトリへのURLである必要があります。\fIextdocURL\fRに絶対リンクを使用すると、ユーザーのドキュメントを任意のWebサイト上のドキュメントにリンクできます。相対位置へリンクするのみの場合は相対リンクを使用できます。相対リンクを使用する場合、渡す値は宛先ディレクトリから、リンクされているパッケージを含むディレクトリへである必要があります(\fB\-d\fRオプションで指定)。絶対リンクを指定する場合、通常、HTTPリンクを使用します。ただし、Webサーバーを持たないファイル・システムにリンクする場合は、ファイル・リンクを使用できます。生成されたドキュメンテーションにアクセスする全員が同じファイル・システムを共有する場合にのみファイル・リンクを使用します。どの場合も、どのオペレーティング・システムでも、URLが絶対または相対のいずれでも、また\fBh\fR\fBttp:\fRまたは\fBf\fR\fBile:\fRのいずれでも、URLメモ: Uniform Resource Locators +(http://www\&.ietf\&.org/rfc/rfc1738\&.txt)に指定されているとおり、区切り文字としてスラッシュを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-link http://<host>/<directory>/<directory>/\&.\&.\&./<name>\fR +\fB\-link file://<host>/<directory>/<directory>/\&.\&.\&./<name>\fR +\fB\-link <directory>/<directory>/\&.\&.\&./<name>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-linkofflineおよび\-linkオプションの違い +.PP +次の場合に、\fB\-link\fRオプションを使用します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +外部APIドキュメントへの相対パスを使用する場合。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +外部APIドキュメントへの絶対URLを使用する場合(そのURLに接続し、読取りを行うことがシェルによって許可されている場合)。 +.RE +.PP +外部APIドキュメントへの絶対URLを使用する場合(そのURLに接続し、読取りを行うことがシェルによって許可されていない場合)は\fB\-linkoffline\fRオプションを使用します。このような状況は、ファイアウォールの内側からファイアウォールの外側にあるドキュメントにリンクしようとする場合に発生します。 +.PP +\fB例 1 \fR外部ドキュメントへの絶対リンク +.RS 4 +http://docs\&.oracle\&.com/javase/8/docs/api/index\&.htmlに示すような、\fBjava\&.lang\fR、\fBjava\&.io\fRおよびその他のJavaプラットフォーム・パッケージにリンクする場合、次のコマンドを使用します +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-link http://docs\&.oracle\&.com/javase/8/docs/api/ com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +このコマンドは、Java SEプラットフォーム・パッケージへのリンク持つ\fBcom\&.mypackage\fRパッケージのドキュメントを生成します。生成ドキュメントには、たとえばクラス\fBtrees\fR内の\fBObject\fRクラスへのリンクが含まれています。\fB\-sourcepath\fRや\fB\-d\fRなどの他のオプションは表示されません。 +.RE +.PP +\fB例 2 \fR外部ドキュメントへの相対リンク +.RS 4 +この例では、2つのパッケージがあり、そのドキュメントは\fBjavadoc\fRコマンドを複数回実行した結果生成されたものです。さらに、これらのドキュメントは相対パスで分割されています。パッケージは、APIである\fBcom\&.apipackage\fRと、SPI(サービス・プロバイダ・インタフェース)であるc\fBom\&.spipackage\fRです。ドキュメントの格納先は、docs/api/com/apipackageとdocs/spi/com/spipackageです。APIパッケージのドキュメントはすでに生成されていて、docsが現在のディレクトリである場合、APIドキュメントへのリンクを持つSPIパッケージをドキュメント化するには、次のコマンドを実行します。\fBjavadoc \-d \&./spi \-link \&.\&./api com\&.spipackage\fR +.sp +\fB\-link\fRオプションは、宛先ディレクトリ(docs/spi)からの相対パスです。 +.RE +.PP +注意 +.PP +\fB\-link\fRオプションを使用すると、コードからは参照されていても、今回の\fBjavadoc\fRの実行ではドキュメント化されないクラスにリンクできるようになります。リンクから有効なページに移動できるようにするには、それらのHTMLページがある場所を調べ、その場所を\fBextdocURL\fRに指定する必要があります。これにより、サードパーティのドキュメンテーションがjava\&.*ドキュメンテーション( +http://docs\&.oracle\&.com)へリンクすることができます。\fBjavadoc\fRコマンドで、現在の実行で生成しているドキュメンテーション内のAPIへのリンクのみを作成する場合には、\fB\-link\fRオプションを省略します。\fB\-link\fRオプションを指定しないと、\fBjavadoc\fRコマンドは外部参照のためのドキュメンテーションへのリンクを作成しません。ドキュメンテーションが存在するのかどうか、またはどこに存在するのかがわからないからです。\fB\-link\fRオプションでは、生成ドキュメンテーション内の複数の場所にリンクを作成できます。ソース・ファイルの処理を参照してください。もう1つの用途は、パッケージ・セットの間にクロスリンクを作成することです。一方のパッケージ・セットに対して\fBjavadoc\fRコマンドを実行した後、他方のパッケージ・セットに対して\fBjavadoc\fRコマンドを再度実行すると、両セット間に双方向のリンクを作成できます。 +.PP +クラスの参照方法 +.PP +表示される外部参照クラスへのリンクの場合(およびそのテキスト・ラベルだけではなく)、クラスは次の方法で参照される必要があります。メソッドの本体でクラスを参照するのみでは十分ではありません。\fBimport\fR文、宣言のいずれかで参照する必要があります。次に、クラス\fBjava\&.io\&.File\fRを参照する方法の例を示します。 +.PP +すべてのタイプのimport文の場合。ワイルドカードによるインポート、名前による明示的なインポート、または\fBjava\&.lang\&.*\fRに対する自動インポート。 +.PP +Java SE 1\&.3\&.\fIn\fRおよび1\&.2\&.\fIn\fRでは、名前による明示的なインポートのみ機能します。ワイルドカードによる\fBimport\fR文も、\fBimport java\&.lang\&.*\fRの自動インポートも機能しません。 +.PP +宣言の場合: +\fBvoid mymethod(File f) {}\fR +.PP +参照は、メソッド、コンストラクタ、フィールド、クラスまたはインタフェースの戻り型またはパラメータ・タイプ、あるいは実装、拡張またはスロー文にあります。 +.PP +重要な結果として、\fB\-link\fRオプションを使用しても、この制限のために誤って表示されないリンクが多数発生する可能性があります。テキストはハイパーテキスト・リンクが付けられずに表示されます。リンクが表示する警告から、これらのリンクを認識できます。クラスを正しく参照し、それによってリンクを追加するための最も簡単な方法はそのクラスをインポートすることです。 +.PP +パッケージ・リスト +.PP +\fB\-link\fRオプションには、\fBjavadoc\fRコマンドによって生成されるpackage\-listという名前のファイルが、\fB\-link\fRオプションに指定したURLに存在していることが必要です。package\-listファイルは、その場所にあるドキュメント化されたパッケージの名前のリストが入った単純なテキスト・ファイルです。前述の例では、\fBjavadoc\fRコマンドは、指定したURLでpackage\-listという名前のファイルを検索し、パッケージ名を読み取って、そのURLでこれらのパッケージにリンクします。 +.PP +たとえば、Java SE APIのパッケージ・リストは +http://docs\&.oracle\&.com/javase/8/docs/api/package\-listにあります。 +.PP +このパッケージ・リストは次のような内容で始まっています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\&.applet\fR +\fBjava\&.awt\fR +\fBjava\&.awt\&.color\fR +\fBjava\&.awt\&.datatransfer\fR +\fBjava\&.awt\&.dnd\fR +\fBjava\&.awt\&.event\fR +\fBjava\&.awt\&.font\fR +\fBand so on \&.\&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB\-link\fRオプションを指定せずに\fBjavadoc\fRを実行した場合、外部参照クラスに属する名前を見つけると、その名前をリンクなしで出力します。一方、\fB\-link\fRオプションを指定した場合、\fBjavadoc\fRコマンドは、指定された\fIextdocURL\fRの場所にあるpackage\-listファイルでそのパッケージ名を検索します。パッケージ名が見つかると、\fIextdocURL\fRが名前の前に付加されます。 +.PP +すべてのリンクが正しく機能するためには、外部参照のすべてのドキュメントが、指定したURLに存在する必要があります。\fBjavadoc\fRコマンドは、指定されたpackage\-listが存在するかどうかのみをチェックし、これらのページが存在するかどうかはチェックしません。 +.PP +複数のリンク +.PP +複数の\fB\-link\fRオプションを指定すると、任意の数の外部生成ドキュメントへのリンクを作成できます。Javadoc 1\&.2には、複数の\fB\-link\fRオプションを指定できないという既知の不具合があります。これはJavadoc 1\&.2\&.2で修正されました。リンクする外部ドキュメントごとに、次のように別々のリンク・オプションを指定します。\fBjavadoc \-link extdocURL1 \-link extdocURL2 \&.\&.\&. \-link extdocURLn com\&.mypackage\fR +\fIextdocURL1\fR、\fIextdocURL2\fR、\&.\fB\&.\&. extdocURLn\fRは、それぞれ外部ドキュメントのルートを指し、各ルートには、package\-listという名前のファイルが入っています。 +.PP +クロスリンク +.PP +以前に作成された複数のドキュメントをクロスリンクする場合、ブートストラップが必要になることがあります。どのドキュメントについてもpackage\-listが存在していない場合は、最初のドキュメントに対して\fBjavadoc\fRコマンドを実行する時点で、2番目のドキュメントのpackage\-listはまだ存在していません。したがって、外部リンクを作成するには、2番目のドキュメントを生成した後で、最初のドキュメントを生成しなおす必要があります。 +.PP +この場合、最初のドキュメント生成の目的は、package\-listを作成することです(パッケージ名を把握している場合は手動で作成してもかまいません)。次に、2番目のドキュメントとその外部リンクを生成します。必要な外部のpackage\-listファイルが存在しない場合は、\fBjavadoc\fRコマンドから警告が出力されます。 +.PP +\-linkoffline \fIextdocURL packagelistLoc\fR +.RS 4 +このオプションは\fB\-link\fRオプションのバリエーションです。両方とも、Javadocにより生成された外部参照クラスのドキュメントへのリンクを作成します。\fBjavadoc\fRコマンドがWeb接続を使用してドキュメントにアクセスできないとき、Web上のドキュメントにリンクするには、\fB\-link\fRo\fBffline\fRオプションを使用します。外部ドキュメントのpackage\-listファイルにアクセスできないとき、またはこのファイルが\fBextdocURL\fRで指定された場所には存在せず、\fBpackageListLoc\fRで指定できる別の場所(通常ローカル)に存在するとき、\fB\-linkoffline\fRオプションを使用します。\fBextdocURL\fRにWorld Wide Web上でしかアクセスできない場合は、\fB\-linkoffline\fRオプションを指定することにより、ドキュメントの生成時に\fBjavadoc\fRコマンドがWebに接続する必要があるという制約がなくなります。もう1つの用途は、ドキュメントを更新するための回避策として使用することです。パッケージのセット全体に対して\fBjavadoc\fRコマンドを実行した後、変更した一部のパッケージに対してのみ\fBjavadoc\fRコマンドを再度実行して、更新されたファイルを、オリジナルのセットに挿入できるようにします。次に例を示します。\fB\-linkoffline\fRオプションは引数を2つ取ります。第1引数は\fB<a href>\fRリンクに組み込まれる文字列を指定し、第2引数はpackage\-listの検索場所を\fB\-linkoffline\fRに伝えます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBextdocURL\fRの値は、リンク先として指定する、Javadocにより生成された外部ドキュメントを含むディレクトリの絶対URLまたは相対URLです。相対URLの場合、値は、生成先ディレクトリ(\fB\-d\fRオプションで指定)からリンク先となるパッケージのルートへの相対パスにする必要があります。詳細は、\fB\-link\fRオプションの\fIextdocURL\fRを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackagelistLoc\fRの値は、外部ドキュメントのpackage\-listファイルを含むディレクトリへのパスまたはURLです。これは、URL (http:またはfile:)でもファイル・パスでもかまいません。また、絶対パスと相対パスのどちらでもかまいません。相対パスの場合は、\fBjavadoc\fRコマンドが実行される現在のディレクトリからの相対パスとして指定します。package\-listファイル名を含めないでください。 +.sp +指定した\fBjavadoc\fRコマンドの実行で、複数の\fB\-link\fRオプションを指定できます。Javadoc 1\&.2\&.2より前では、\fB\-linkfile\fRオプションは1回しか指定できませんでした。 +.RE +.RE +.PP +外部ドキュメントへの絶対リンク +.PP +http://docs\&.oracle\&.com/javase/8/docs/api/index\&.htmlに示すような、\fBjava\&.lang\fR、 +\fBjava\&.io\fRおよびその他のJava SEパッケージにリンクする必要がある場合があります。 +.PP +ただし、シェルにはWebアクセス権がありません。この場合、次を行います。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +ブラウザでpackage\-listファイルを開きます(http://docs\&.oracle\&.com/javase/8/docs/api/package\-list) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +ファイルをローカル・ディレクトリに保存し、このローカル・コピーを第2引数\fBpackagelistLoc\fRで指定します。この例では、パッケージ・リスト・ファイルはカレント・ディレクトリ(\&.)に保存されています。 +.RE +.PP +次のコマンドは、Java SEプラットフォーム・パッケージへのリンクを持つc\fBom\&.mypackage\fRパッケージのドキュメントを生成します。生成ドキュメントには、たとえばクラス\fBtrees\fR内の\fBObject\fRクラスへのリンクが含まれています。\fB\-sourcepath\fRなど、他の必要なオプションは表示されません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-linkoffline http://docs\&.oracle\&.com/javase/8/docs/api/ \&. com\&.mypackage \fR + +.fi +.if n \{\ +.RE +.\} +.PP +外部ドキュメントへの相対リンク +.PP +\fB\-linkoffline\fRを相対パスとともに使用することはあまりありません。理由は単純で、通常は\fB\-link\fRで間に合うからです。\fB\-linkoffline\fRオプションを使用する場合、通常、package\-listファイルはローカルで、相対リンクを使用する場合はリンク先のファイルもローカルなので、通常は\fB\-linkoffline\fRオプションの2つの引数に、異なるパスを指定する必要はありません。2つの引数が同一の場合、\fB\-link\fRオプションを使用できます。 +.PP +package\-listファイルの手動での作成 +.PP +package\-listファイルがまだ存在しなくても、ドキュメントのリンク先のパッケージ名がわかっている場合は、このファイルのコピーを手動で作成し、\fBpackagelistLoc\fRでそのパスを指定することができます。\fBcom\&.apipackage\fRが最初に生成された時点で\fBcom\&.spipackage\fRのパッケージ・リストが存在しないという前出のケースが一例として挙げられます。この方法は、パッケージ名はわかっているものの、まだ公開されていない、新しい外部ドキュメントにリンクするドキュメントを生成する必要がある場合に便利です。また、package\-listファイルが生成されないJavadoc 1\&.0または1\&.1で生成されたパッケージ用にpackage\-listファイルを作成する場合にも、この方法が使用できます。同様に、2つの企業が未公開のpackage\-listファイルを共有できるため、クロスリンクを設定したドキュメントを同時にリリースすることも可能になります。 +.PP +複数ドキュメントへのリンク +.PP +参照先の生成ドキュメントごとに1回、\fB\-linkoffline\fRオプションを含めることができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-linkoffline extdocURL1 packagelistLoc1 \-linkoffline extdocURL2\fR +\fBpackagelistLoc2 \&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ドキュメントの更新 +.PP +プロジェクトに何十または何百のパッケージが含まれる場合にも、\fB\-linkoffline\fRオプションを使用できます。ソース・ツリー全体ですでに\fBjavadoc\fRコマンドを実行したことがある場合、ドキュメンテーション・コメントにわずかな変更を迅速に加え、ソース・ツリーの一部で\fBjavadoc\fRコマンドを再実行することができます。2回目の実行は、ドキュメンテーション・コメントを変更し、宣言は変更しない場合にのみ正しく処理されることに注意してください。ソース・コードに対して宣言を追加、削除、または変更した場合は、索引、パッケージ・ツリー、継承されるメンバーのリスト、使用ページなどの場所で、リンクが壊れることがあります。 +.PP +まず、この新しい小規模な実行で使用する、新しい生成先ディレクトリ(updateなど)を作成します。この例では、元の生成先ディレクトリの名前はhtmlです。最も単純な例では、htmlディレクトリの親ディレクトリに移動します。\fB\-linkoffline\fRオプションの第1引数にカレント・ディレクトリ(\&.)を設定し、第2引数にpackage\-listが検索されるhtmlへの相対パスを設定し、更新するパッケージのパッケージ名のみを渡します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d update \-linkoffline \&. html com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavadoc\fRコマンドの終了後、update/com/package内の生成されたクラスのページをコピーし(概要や索引は除く)、html/com/package内の元のファイルに上書きします。 +.PP +\-linksource +.RS 4 +各ソース・ファイル(行番号付き)のHTMLバージョンを作成し、標準HTMLドキュメントからソース・ファイルへのリンクを追加します。リンクは、ソース・ファイル内に宣言されているクラス、インタフェース、コンストラクタ、メソッド、フィールドに対して作成されます。デフォルト・コンストラクタ、生成されたクラスなどに対しては作成されません。 +.sp +このオプションは、\fB\-public\fR、\fB\-package\fR、\fB\-protected\fRおよび\fB\-private\fRの各オプションとは関係なく、非公開のクラス、フィールド、非公開のメソッドの本体をはじめとする組み込まれたソース・ファイル内のすべての非公開実装の詳細を公開します。\fB\-private\fRオプションもあわせて指定しないかぎり、非公開のクラスやインタフェースの一部には、リンクを介してアクセスできないことがあります。 +.sp +各リンクは、その宣言内の識別子名の上に作成されます。たとえば、\fBButton\fRクラスのソース・コードへのリンクは、\fBButton\fRという語の上に作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class Button extends Component implements Accessible\fR + +.fi +.if n \{\ +.RE +.\} +\fBButton\fRクラスの\fBgetLabel\fRメソッドのソース・コードへのリンクは、\fBgetLabel\fRという語の上に作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic String getLabel()\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-group groupheading \fIpackagepattern:packagepattern\fR +.RS 4 +概要ページの複数のパッケージを、指定したグループに分けて、グループごとに表を作成します。各グループは、それぞれ別の\fB\-group\fRオプションで指定します。グループは、コマンド行で指定された順序でページに表示されます。パッケージは、グループ内でアルファベット順になっています。指定した\fB\-group\fRオプションでは、\fBpackagepattern\fR式のリストに一致するパッケージが、見出しとして\fIgroupheading\fRを持つ1つの表に表示されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBgroupheading\fRには、任意のテキストを指定でき、空白を含めることができます。指定したテキストは、グループの表見出しになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackagepattern\fRの値には、任意のパッケージ名の先頭部分とそれに続く1つのアスタリスク(*)で任意のパッケージ名を指定できます。アスタリスクは使用できる唯一のワイルドカードで、任意の文字に一致する、という意味です。1つのグループには、コロン(:)で区切って複数のパターンを含めることができます。パターンまたはパターン・リストでアスタリスクを使用する場合、パターン・リストは\fB"java\&.lang*:java\&.util"\fRのように引用符で囲む必要があります。 +.RE +.sp +\fB\-group\fRオプションを指定しない場合は、見出し\fIPackages\fRおよび適切な小見出しを持つ1つのグループに配置されます。小見出しにすべてのドキュメント化されるパッケージ(すべてのグループ)が含まれるわけではない場合、残りのパッケージは「その他のパッケージ」というサブ見出しを持つ独立したグループに入れられます。 +.sp +たとえば、次の\fBjavadoc\fRコマンドでは、3つのドキュメント化されたパッケージが\fI「コア」\fR、\fI「拡張」\fRおよび\fI「その他のパッケージ」\fRに分けられます。\fBjava\&.lang*\fRでは、最後のドット(\&.)を指定していません。\fBjava\&.lang\&.*\fRのようにドットを入れると、\fB java\&.lang\fRパッケージは除外されることになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-group "Core Packages" "java\&.lang*:java\&.util"\fR +\fB \-group "Extension Packages" "javax\&.*"\fR +\fB java\&.lang java\&.lang\&.reflect java\&.util javax\&.servlet java\&.new\fR + +.fi +.if n \{\ +.RE +.\} +\fBコア・パッケージ\fR +.sp +\fBjava\&.lang\fR +.sp +\fBjava\&.lang\&.reflect\fR +.sp +\fBjava\&.util\fR +.sp +\fB拡張機能パッケージ\fR +.sp +\fBjavax\&.servlet\fR +.sp +\fBOther Packages\fR +.sp +\fBjava\&.new\fR +.RE +.PP +\-nodeprecated +.RS 4 +推奨されないAPIをドキュメントに生成しないようにします。このオプションを指定すると、\fB\-nodeprecatedlist\fRオプションを指定した場合と同じ効果があり、ドキュメントの他の部分全体でも、推奨されないAPIが生成されません。このオプションは、コードを記述しているとき、推奨されないコードによって気を散らされたくない場合に便利です。 +.RE +.PP +\-nodeprecatedlist +.RS 4 +推奨されないAPIのリストを含むファイル(deprecated\-list\&.html)、およびナビゲーション・バーのそのページへのリンクが生成されないようにします。\fBjavadoc\fRコマンドでは、引き続き、ドキュメントの他の部分では、推奨されないAPIが生成されます。このオプションは、推奨されないAPIがソース・コードに含まれておらず、ナビゲーション・バーをすっきりと見せる場合に便利です。 +.RE +.PP +\-nosince +.RS 4 +生成ドキュメントから、\fB@since\fRタグに関連付けられた\fB「導入されたバージョン」\fRセクションを省略します。 +.RE +.PP +\-notree +.RS 4 +生成ドキュメントから、クラスおよびインタフェースの階層ページを省略します。これらのページには、ナビゲーション・バーの「階層ツリー」ボタンからアクセスできます。デフォルトでは、階層が生成されます。 +.RE +.PP +\-noindex +.RS 4 +生成ドキュメントから、索引を省略します。デフォルトでは、索引が生成されます。 +.RE +.PP +\-nohelp +.RS 4 +出力の各ページの最上部と最下部にあるナビゲーション・バーから「ヘルプ」リンクを省略します。 +.RE +.PP +\-nonavbar +.RS 4 +通常、生成されるページの最上部と最下部に表示されるナビゲーション・バー、ヘッダー、およびフッターを生成しないようにします。\fB\-nonavbar\fRオプションは\fB\-bottom\fRオプションに影響を与えません。\fB\-nonavbar\fRオプションは、印刷するためにのみファイルをPostScriptやPDFに変換する場合など、内容のみが重要で、ナビゲーションの必要がない場合に便利です。 +.RE +.PP +\-helpfile \fIpath\efilename\fR +.RS 4 +最上部および最下部のナビゲーション・バーの「ヘルプ」リンクのリンク先となる代替ヘルプ・ファイルpath\efilenameのパスを指定します。このオプションが指定されていないと、\fBjavadoc\fRコマンドは、\fBjavadoc\fRコマンド内でハードコードされているヘルプ・ファイルhelp\-doc\&.htmlを自動作成します。このオプションを使用すると、デフォルトをオーバーライドできます。ファイル名にはどんな名前でも指定でき、help\-doc\&.htmlに限定されません。\fBjavadoc\fRコマンドは、次の例のように、ナビゲーション・バー内のリンクを必要に応じて調整します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-helpfile /home/user/myhelp\&.html java\&.awt\&.\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-stylesheet \fIpath/filename \fR +.RS 4 +代替HTMLスタイルシート・ファイルのパスを指定します。このオプションが指定されていないと、\fBjavadoc\fRコマンドは、\fBjavadoc\fRコマンド内でハードコードされているスタイルシート・ファイルstylesheet\&.cssを自動作成します。このオプションを使用すると、デフォルトをオーバーライドできます。ファイル名にはどんな名前でも指定でき、stylesheet\&.cssに限定されません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-stylesheet file /home/user/mystylesheet\&.css com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-serialwarn +.RS 4 +\fB@serial\fRタグがない場合は、コンパイル時に警告を生成します。デフォルトでは、Javadoc 1\&.2\&.2以降では、直列化の警告は生成されません。以前のリリースとは逆の動作です。このオプションを使用すると、直列化の警告が表示されるので、デフォルトの直列化可能フィールドと\fBwriteExternal\fRメソッドを適切にドキュメント化するのに役立ちます。 +.RE +.PP +\-charset \fIname\fR +.RS 4 +このドキュメント用のHTML文字セットを指定します。この名前は、IANA RegistryのCharacter Sets +(http://www\&.iana\&.org/assignments/character\-sets)に示された、優先MIME名である必要があります。 +.sp +たとえば、\fBjavadoc \-charset "iso\-8859\-1" mypackage\fRは次の行を生成された各ページのヘッダーに挿入します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<META http\-equiv="Content\-Type" content="text/html; charset=ISO\-8859\-1">\fR + +.fi +.if n \{\ +.RE +.\} +この\fBMETA\fRタグは、HTML標準(4197265および4137321)のHTML Document Representation +(http://www\&.w3\&.org/TR/REC\-html40/charset\&.html#h\-5\&.2\&.2)に記載されています。 +.sp +およびオプションも参照してください。 +.RE +.PP +\-docencoding \fIname\fR +.RS 4 +生成されるHTMLファイルのエンコーディングを指定します。この名前は、IANA RegistryのCharacter Sets +(http://www\&.iana\&.org/assignments/character\-sets)に示された、優先MIME名である必要があります。 +.sp +\fB\-docencoding\fRオプションを省略し、\fB\-encoding\fRオプションを使用すると、生成されたHTMLファイルの暗号化は\fB\-encoding\fRオプションで特定されます。例: +\fBjavadoc \-docencoding "iso\-8859\-1" mypackage\fRおよびオプションも参照してください。 +.RE +.PP +\-keywords +.RS 4 +HTMLキーワード<META>タグを、クラスごとに生成されるファイルに追加します。これらのタグは、<META>タグを検索するサーチ・エンジンがページを見つける場合に役立ちます。インターネット全体を検索する検索エンジンのほとんどは<META>タグを参照しません。ページが誤用している可能性があるからです。自身のWebサイトへの検索を制限する、企業により提供される検索エンジンは、<META>タグを参照することで恩恵を受けることができます。<META>タグには、クラスの完全修飾名と、フィールドおよびメソッドの修飾されていない名前が含まれます。コンストラクタは、クラス名と同じであるため含まれません。たとえば、クラス\fBString\fRは次のキーワードで開始します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<META NAME="keywords" CONTENT="java\&.lang\&.String class">\fR +\fB<META NAME="keywords" CONTENT="CASE_INSENSITIVE_ORDER">\fR +\fB<META NAME="keywords" CONTENT="length()">\fR +\fB<META NAME="keywords" CONTENT="charAt()">\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-tag \fItagname\fR:Xaoptcmf:"\fItaghead\fR" +.RS 4 +\fBjavadoc\fRコマンドがドキュメンテーション・コメント内の引数を1つ取る単純なカスタム・ブロック・タグ\fB@tagname\fRを解釈できるようにします。これにより、\fBjavadoc\fRコマンドはタグ名のスペルチェックを行うことができるので、ソース・コード内に存在するすべてのカスタム・タグについて、\fB\-tag\fRオプションを組み込むことが重要です。今回の実行では出力されないタグは、\fBX\fRを付けて無効にします。\fB\-tag\fRオプションは、タグの見出し\fItaghead\fRを太字で出力します。その次の行には、このオプションの1つの引数で指定したテキストが続きます。ブロック・タグと同様、この引数のテキストにはインライン・タグを含めることができます。このインライン・タグも解釈されます。出力は、引数を1つ取る標準のタグ(\fB@return\fRや\fB@author\fRなど)の出力とよく似ています。\fItaghead\fRの値を省略すると、\fBtagname\fRが見出しとして表示されます。 +.sp +\fBタグの配置\fR: +\fBXaoptcmf\fR引数により、ソース・コード内でタグを配置できる場所が決まり、タグを無効にできるかどうか(\fBX\fRを使用して)が決まります。タグの配置位置を制限しない場合は\fBa\fRを指定します。それ以外の文字の組合せも可能です。 +.sp +\fBX\fR +(タグの無効化) +.sp +\fBa\fR +(すべて) +.sp +\fBo\fR +(概要) +.sp +\fBp\fR +(パッケージ) +.sp +\fBt\fR +(タイプ、つまりクラスとインタフェース) +.sp +\fBc\fR +(コンストラクタ) +.sp +\fBm\fR +(メソッド) +.sp +\fBf\fR +(フィールド) +.sp +\fBシングル・タグの例\fR: ソース・コード内の任意の位置で使用できるタグのタグ・オプションの例を示します。\fB\-tag todo:a:"To Do:"\fR +.sp +\fB@todo\fRタグをコンストラクタ、メソッドおよびフィールドとのみ使用する場合、\fB\-tag todo:cmf:"To Do:"\fRを使用します。 +.sp +最後のコロン(:)は、パラメータ区切り文字ではなく、見出しテキストの一部になっています。\fB@todo\fRタグを含む、ソース・コード用のいずれかのタグ・オプションを使用します。たとえば、\fB@todo The documentation for this method needs work\fRです。 +.sp +\fBタグ名内のコロン\fR: タグ名内でコロンを使用する場合はバックスラッシュを使用してエスケープします。次のドキュメンテーション・コメントには、\fB\-tag ejb\e\e:bean:a:"EJB Bean:"\fRオプションを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @ejb:bean\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +\fBタグ名のスペルチェック\fR: 一部の開発者が必ずしも出力しないカスタム・タグをソース・コード内に配置することがあります。この場合、ソース・コード内のすべてのタグをリストし、出力するタグを有効にし、出力しないタグを無効にする必要があります。\fBX\fRを指定するとタグは無効になります。指定しないと、タグは有効になります。これにより、\fBjavadoc\fRコマンドは、検出したタグが入力ミスなどによる不明タグであるかどうかを特定できます。このような場合に、\fBjavadoc\fRコマンドから警告が出力されます。すでに配置されている値に\fBX\fRを追加できます。こうしておけば、\fBX\fRを削除するのみでタグを有効にすることができます。たとえば、\fB@todo\fRタグを出力で抑制する場合、\fB\-tag todo:Xcmf:"To Do:"\fRを使用します。さらに簡単にする場合、\fB\-tag todo:X\fRを使用します。構文\fB\-tag todo:X\fRは、\fB@todo\fRタグがタグレットで定義されていても機能します。 +.sp +\fBタグの順序\fR: +\fB\-ta\fR\fBg\fRおよび\fB\-taglet\fRオプションの順序によって、タグの出力順が決まります。カスタム・タグと標準タグを組み合せて使用することもできます。標準タグのタグ・オプションは、順序を決定するためだけのプレースホルダです。標準タグの名前のみを取ります。標準タグの小見出しは変更できません。これを次の例に示します。\fB\-tag\fRオプションを指定しないと、\fB\-tagle\fR\fBt\fRオプションの位置により、順序が決まります。タグが両方とも存在する場合、コマンドラインの最後にある方がその順序を決定します。これは、タグやタグレットがコマンドラインに指定された順番に処理されるためです。たとえば、\fB\-taglet\fRおよび\fB\-tag\fRオプションが名前\fBtodo\fR値を持つ場合、コマンドラインに最後に指定されたものが順序を決定します。 +.sp +\fBタグの完全セットの例\fR: この例では、出力のParametersとThrowsの間にTo Doを挿入します。\fBX\fRを使用して、\fB@example\fRタグが、ソース・コード内の今回の実行では出力されないタグであることも指定します。\fB@argfile\fRタグを使用する場合は、次のように、引数ファイル内の別々の行にタグを配置できます(行の継続を示す文字は不要)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-tag param\fR +\fB\-tag return\fR +\fB\-tag todo:a:"To Do:"\fR +\fB\-tag throws\fR +\fB\-tag see\fR +\fB\-tag example:X\fR + +.fi +.if n \{\ +.RE +.\} +\fBjavadoc\fRコマンドがドキュメンテーション・コメントを解析する際に検索されたタグのうち、標準タグでも、\fB\-tag\fRや\fB\-taglet\fRオプションで渡されたタグでもないものはすべて不明タグとみなされ、警告がスローされます。 +.sp +標準タグは、最初、デフォルトの順序でリスト内に内部的に格納されます。\fB\-tag\fRオプションを使用すると、それらのタグはこのリストに追加されます。標準タグは、デフォルトの位置から移動されます。そのため、標準タグの\fB\-tag\fRオプションを省略すると、それはデフォルトの位置に配置されたままになります。 +.sp +\fB競合の回避\fR: 固有の名前空間を作成するには、パッケージに使用されている\fBcom\&.mycompany\&.todo\fRという名前のように、ドットで区切られた名前を使用します。Oracleは、今後も名前にドットを含まない標準タグを作成します。ユーザーが作成したタグは、Oracleが定義する同じ名前のタグの動作をオーバーライドします。\fB@todo\fRという名前のタグまたはタグレットをユーザーが作成した場合、その後にOracleが同じ名前の標準タグを作成しても、そのタグまたはタグレットは常にユーザーが定義したのと同じ動作を保持します。 +.sp +\fB注釈vs\&. Javadocタグ\fR: 一般に、追加する必要のあるマークアップが、ドキュメントに影響を与えたりドキュメントを生成したりするためのものである場合、そのマークアップはJavadocタグにします。それ以外の場合は注釈にします。JavadocツールでのDocコメントの記述方法のカスタム・タグと注釈に関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#annotations)を参照してください。 +.sp +\fB\-taglet\fRオプションを使用して、より複雑なブロック・タグやカスタム・インライン・タグも作成できます。 +.RE +.PP +\-taglet \fIclass\fR +.RS 4 +そのタグのドキュメントの生成に使用するドックレットを起動するためのクラス・ファイルを指定します。\fBclass\fR値の完全修飾名を使用します。このタグレットは、カスタム・タグのテキスト引数の数も定義します。タグレットは、これらの引数を受け付け、処理し、出力を生成します。タグレットの例を使用した豊富なドキュメントについては、タグレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/taglet/overview\&.html)を参照してください。 +.sp +タグレットは、ブロックタグまたはインライン・タグで便利です。タグレットは任意の数の引数をとることができます。また、テキストを太字にする、箇条書きを作成する、テキストをファイルに書き出す、その他のプロセスを開始するなどのカスタム動作を実装できます。タグレットで指定できるのは、タグの配置場所と配置形式のみです。その他のすべての決定は、ドックレットによって行われます。タグレットを使用しても、包含クラスのリストからクラス名を削除するなどの処理は実行できません。ただし、タグのテキストをファイルに出力したり、別のプロセスをトリガーするなどの副作用は得られます。タグレットへのパスを指定するには、\fB\-tagletpath\fRオプションを使用します。次に、生成されるページのParametersとThrowsの間にTo Doタグレットを挿入する例を示します。または、\fB\-taglet\fRオプションをその\fB\-tag\fRオプションのかわりに使用することができますが、読み取りが困難になる可能性があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-taglet com\&.sun\&.tools\&.doclets\&.ToDoTaglet\fR +\fB\-tagletpath /home/taglets \fR +\fB\-tag return\fR +\fB\-tag param\fR +\fB\-tag todo\fR +\fB\-tag throws\fR +\fB\-tag see\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-tagletpath \fItagletpathlist\fR +.RS 4 +tagletクラス・ファイルを検索するための検索パスを指定します。\fBtagletpathlist\fRには、コロン(:)で区切って複数のパスを含めることができます。\fBjavadoc\fRコマンドは、指定されたパス以下のすべてのサブディレクトリを検索します。 +.RE +.PP +\-docfilesubdirs +.RS 4 +doc\-filesディレクトリのディープ・コピーを有効にします。宛先には、サブディレクトリとそのすべて内容が再帰的にコピーされます。たとえば、ディレクトリoc\-files/example/imagesとその内容がすべてコピーされます。ここでも、サブディレクトリを除外する指定が可能です。 +.RE +.PP +\-excludedocfilessubdir \fIname1:name2\fR +.RS 4 +指定された名前のdoc\-filesサブディレクトリをすべて除外します。これにより、SCCSとその他のソース・コード制御サブディレクトリのコピーを防ぎます。 +.RE +.PP +\-noqualifier all | \fIpackagename1\fR:\fIpackagename2\&.\&.\&.\fR +.RS 4 +出力されるクラス名から修飾パッケージ名を省略します。\fB\-noqualifier\fRオプションの引数は、\fBall\fR(すべてのパッケージ修飾子を省略)、または修飾子として削除するパッケージのコロン区切りリスト(ワイルドカードも可)、のいずれかとなります。クラスまたはインタフェース名が表示される位置からパッケージ名が削除されます。ソース・ファイルの処理を参照してください。 +.sp +次の例では、すべてのパッケージ修飾子を省略します。\fB\-noqualifier all\fR +.sp +次の例では、\fBjava\&.lang\fRおよび\fBjava\&.io\fRパッケージ修飾子を省略します: +\fB\-noqualifier java\&.lang:java\&.io\fR。 +.sp +次の例では、\fBjava\fRで始まるパッケージ修飾子および\fBcom\&.sun\fRサブパッケージを省略しますが、\fBjavax\fRは省略しません。\fB\-noqualifier java\&.*:com\&.sun\&.*\fR +.sp +パッケージ修飾子が前述の動作に従って表示される場合、名前は適切に短縮されます。「名前が表示される方法」を参照してください。このルールは、\fB\-noqualifier\fRオプションを使用するかどうかにかかわらず有効です。 +.RE +.PP +\-notimestamp +.RS 4 +タイムスタンプが抑制されます。各ページの先頭近くにある、生成されたHTML内のHTMLコメントでタイムスタンプが隠されます。\fB\-notimestamp\fRオプションは、\fBjavadoc\fRコマンドを2つのソース・ベースで実行し、それらの間の差分\fBdiff\fRを取得する場合に役立ちます。タイムスタンプによる\fBdiff\fRの発生を防ぐからです(そうでないとすべてのページで\fBdiff\fRになります)。タイムスタンプには\fBjavadoc\fRコマンドのリリース番号が含まれ、現在では、\fB<!\-\- Generated by javadoc (build 1\&.5\&.0_01) on Thu Apr 02 14:04:52 IST 2009 \-\->\fRのように表示されます。 +.RE +.PP +\-nocomment +.RS 4 +主説明およびすべてのタグを含むコメント本文全体を抑制し、宣言のみを生成します。このオプションにより、元は異なる目的のためだったソース・ファイルを再利用し、新しいプロジェクトの早い段階でスケルトンHTMLドキュメントを作成できるようになります。 +.RE +.PP +\-sourcetab \fItablength\fR +.RS 4 +ソース内で各タブが使用する空白文字の数を指定します。 +.RE +.SH "コマンドライン引数ファイル" +.PP +\fBjavadoc\fRコマンドを短くしたり簡潔にしたりするために、\fBjavadoc\fRコマンドに対する引数(\fB\-J\fRオプションを除く)が入った1つ以上のファイルを指定することができます。このことを利用すれば、どのオペレーティング・システム上でも、任意の長さの\fBjavadoc\fRコマンドを作成できます。 +.PP +引数ファイルには、\fBjavac\fRのオプションとソース・ファイル名を自由に組み合せて記述できます。ファイル内の各引数は、スペースまたは改行で区切ります。ファイル名に埋め込まれた空白がある場合、ファイル名全体を二重引用符で囲みます。 +.PP +引数ファイル内のファイル名は、引数ファイルの位置ではなく、現在のディレクトリに相対的となります。これらのリストでは、ワイルドカード(\fB*\fR)は使用できません。たとえば、*\&.javaとは指定できません。アットマーク(@)を使用して、ファイルを再帰的に解釈することはできません。また、\fB\-J\fRオプションもサポートされていません。このオプションは起動ツールに渡されますが、起動ツールでは引数ファイルをサポートしていないからです。 +.PP +\fBjavadoc\fRを実行するときに、各引数ファイルのパスとファイル名の先頭に@文字を付けて渡します。\fBjavadoc\fRコマンドは、アットマーク(@)文字で始まる引数を見つけると、そのファイルの内容を展開して引数リストに挿入します。 +.PP +\fB例 1 \fR単一の引数ファイル +.RS 4 +\fBargfile\fRという名前の1つの引数ファイルを使用して、すべての\fBjavadoc\fRコマンド引数を保持できます。\fBjavadoc @argfile\fR次の例に示すように、この引数ファイルには両方のファイルの内容が含まれています。 +.RE +.PP +\fB例 2 \fR2つの引数ファイル +.RS 4 +次のように、2つの引数ファイルを作成できます。\fBjavadoc\fRコマンドのオプション用に1つ、パッケージ名またはソース・ファイル名用に1つです。次のリストでは行継続文字を使用していません。 +.sp +次の内容を含む、optionsという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-d docs\-filelist \fR +\fB\-use \fR +\fB\-splitindex\fR +\fB\-windowtitle \*(AqJava SE 7 API Specification\*(Aq\fR +\fB\-doctitle \*(AqJava SE 7 API Specification\*(Aq\fR +\fB\-header \*(Aq<b>Java(TM) SE 7</b>\*(Aq\fR +\fB\-bottom \*(AqCopyright © 1993\-2011 Oracle and/or its affiliates\&. All rights reserved\&.\*(Aq\fR +\fB\-group "Core Packages" "java\&.*"\fR +\fB\-overview /java/pubs/ws/1\&.7\&.0/src/share/classes/overview\-core\&.html\fR +\fB\-sourcepath /java/pubs/ws/1\&.7\&.0/src/share/classes\fR + +.fi +.if n \{\ +.RE +.\} +次の内容を含む、packagesという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcom\&.mypackage1\fR +\fBcom\&.mypackage2\fR +\fBcom\&.mypackage3\fR + +.fi +.if n \{\ +.RE +.\} +次のように、\fBjavadoc\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc @options @packages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRパスを使用した引数ファイル +.RS 4 +引数ファイルはパスを指定できますが、ファイル内のすべてのファイル名は、(\fBpath1\fRや\fBpath2\fRではなく)次のように現在の作業ディレクトリに相対的となります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc @path1/options @path2/packages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fRオプション引数 +.RS 4 +次に、\fBjavadoc\fRコマンドのオプションに対する引数を引数ファイルに格納する例を示します。長い引数を指定できるので、\fB\-bottom\fRオプションを使用します。次のようなテキスト引数を含む、bottomという名前のファイルを作成できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<font size="\-1">\fR +\fB <a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fR +\fB Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&. <br/>\fR +\fB Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fR +\fB Other names may be trademarks of their respective owners\&.</font>\fR + +.fi +.if n \{\ +.RE +.\} +\fBjavadoc\fRコマンドを次のように実行します。\fB javadoc \-bottom @bottom @packages\fR +.sp +\fB\-bottom\fRオプションを引数ファイルの最初に含めて、次のように\fBjavadoc\fRコマンドを実行することもできます。\fBjavadoc @bottom @packages\fR +.RE +.SH "JAVADOCコマンドの実行" +.PP +\fBjavadoc\fRコマンドのリリース番号は\fBjavadoc \-J\-version\fRオプションで特定できます。出力ストリームには標準ドックレットのリリース番号が含まれます。\fB\-quiet\fRオプションで無効にできます。 +.PP +Java言語で記述されたプログラムから\fBjavadoc\fRコマンドを起動するには公開プログラマティック・インタフェースを使用します。このインタフェースは\fBcom\&.sun\&.tools\&.javadoc\&.Main\fRにあります(また\fBjavadoc\fRコマンドは再入可能です)。詳細は、標準ドックレット +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/standard\-doclet\&.html#runningprogrammatically)を参照してください。 +.PP +次の手順では、標準HTMLドックレットを呼び出します。カスタム・ドックレットを呼び出すには、\fB\-doclet\fRおよび\fB\-docletpath\fRオプションを使用しますドックレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html)を参照してください +.SS "簡単な例" +.PP +\fBjavadoc\fRコマンドは、パッケージ全体に対して実行することも、個々のソース・ファイルに対して実行することもできます。各パッケージ名は、それぞれのパッケージ名に対応するディレクトリ名を持ちます。 +.PP +次の例では、ソース・ファイルは/home/src/java/awt/*\&.javaにあります。生成先ディレクトリは/home/htmlです。 +.PP +1つ以上のパッケージのドキュメント化 +.PP +パッケージをドキュメント化するには、そのパッケージのソース・ファイルを、そのパッケージと同じ名前のディレクトリ内に格納する必要があります。 +.PP +パッケージ名が(\fBjava\&.awt\&.color\fRのようにドットで区切られた)複数の識別子から構成されている場合、後続の各識別子が下位のサブディレクトリ(ava/awt/colorなど)に対応している必要があります。 +.PP +1つのパッケージのための複数のソース・ファイルを、異なる場所にあるそのような2つのディレクトリ・ツリーに分けて格納することもできます。ただし、その場合は\fB\-sourcepath\fRによってその両方の場所を指定する必要があります。たとえば、src1/java/awt/colorとsrc2/java/awt/color。 +.PP +ディレクトリの変更(\fBcd\fRコマンドを使用)または\fB\-sourcepath\fRオプションにより、\fBjavadoc\fRコマンドを実行できます。次の例で両方の選択肢を示します。 +.PP +\fB例 1 \fR1つ以上のパッケージから再帰的に実行 +.RS 4 +この例では\fBjavadoc\fRコマンドが任意のディレクトリから実行できるように、\fB\-sourcepath\fRを使用し、再帰的処理のために\fB\-subpackages\fR(1\&.4の新オプション)を使用します。これは、javaディレクトリのサブパッケージをたどりますが、\fBjava\&.net\fRと\fBjava\&.lang\fRをルートに持つパッケージは除外されます。\fBjava\&.lang\fRのサブパッケージである\fBjava\&.lang\&.ref\fRが除外される点に注意してください。また、他のパッケージ・ツリーを下方にたどるには、\fBjava:javax:org\&.xml\&.sax\fRのように、それらのパッケージの名前を\fB\-subpackages\fRの引数に追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src \-subpackages java \-exclude\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRルートへの移動および明示的なパッケージの実行 +.RS 4 +完全修飾されたパッケージの親ディレクトリに移動します。次に、ドキュメント化する1つ以上のパッケージの名前を指定して\fBjavadoc\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd /home/src/\fR +\fBjavadoc \-d /home/html java\&.awt java\&.awt\&.event\fR + +.fi +.if n \{\ +.RE +.\} +また、他のパッケージ・ツリーを下方にたどるには、j\fBava:javax:org\&.xml\&.sax\fRのように、それらのパッケージの名前を\fB\-subpackages\fRの引数に追加します。 +.RE +.PP +\fB例 3 \fR1つのツリーの明示的なパッケージの任意のディレクトリから実行 +.RS 4 +この場合、現在のディレクトリがどこかは問題ではありません。\fBjavadoc\fRコマンドを実行し、最上位パッケージの親ディレクトリを指定して\fB\-sourcepath\fRオプションを使用します。ドキュメント化する1つ以上のパッケージの名前を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src java\&.awt java\&.awt\&.event\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fR複数のツリーの明示的なパッケージの任意のディレクトリから実行 +.RS 4 +\fBjavadoc\fRコマンドを実行し、各ツリーのルートへのパスのコロン区切りリストを指定して\fB\-sourcepath\fRオプションを使用します。ドキュメント化する1つ以上のパッケージの名前を指定します。指定したパッケージのすべてのソース・ファイルが、1つのルート・ディレクトリの下に存在する必要はありませんが、ソース・パスで指定された場所のどこかで見つかる必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src1:/home/src2 java\&.awt java\&.awt\&.event\fR + +.fi +.if n \{\ +.RE +.\} +すべてのケースでj\fBava\&.awt\fRおよび\fBjava\&.awt\&.even\fRtパッケージ内の\fBpublic\fRおよび\fBprotected\fRクラスとインタフェースについて、HTML形式のドキュメントが生成され、指定された生成先ディレクトリにHTMLファイルが保存されます。2つ以上のパッケージが生成されているので、ドキュメントは、パッケージのリスト、クラスのリスト、およびメインのクラス・ページという3つのHTMLフレームを持つことになります。 +.RE +.PP +1つ以上のクラスのドキュメント化 +.PP +また、1つ以上のソース・ファイルを渡して、\fBjavadoc\fRコマンドを実行することもできます。\fBjavadoc\fRは、次の2つの方法のいずれかで実行できます。1つはディレクトリを変更する方法(\fBcd\fRを使用)、もう1つはソース・ファイルへのパスを完全に指定する方法です。相対パスは、現在のディレクトリを起点とします。ソース・ファイルを渡すときは、\fB\-sourcepath\fRオプションは無視されます。アスタリスク(*)のようなコマンドライン・ワイルドカードを使用すると、クラスのグループを指定できます。 +.PP +\fB例 1 \fRソース・ディレクトリに変更 +.RS 4 +ソースを保持するディレクトリに変更します。次に、ドキュメント化する1つ以上のソース・ファイルの名前を指定して\fBjavadoc\fRコマンドを実行します。 +.sp +この例では、\fBButton\fRクラスと\fBCanvas\fRクラス、および名前が\fBGraphics\fRで始まるクラスについて、HTML形式のドキュメントが生成されます。パッケージ名ではなくソース・ファイルが\fBjavadoc\fRコマンドに引数として渡されているので、ドキュメントは、クラスのリストとメイン・ページという2つのフレームを持つことになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd /home/src/java/awt\fR +\fBjavadoc \-d /home/html Button\&.java Canvas\&.java Graphics*\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRパッケージのルート・ディレクトリに変更 +.RS 4 +これは、同じルートからの別のサブパッケージの個々のソース・ファイルをドキュメント化するのに役立ちます。パッケージのルート・ディレクトリに移り、各ソース・ファイルを、ルートからのパスとともに指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd /home/src/\fR +\fBjavadoc \-d /home/html java/awt/Button\&.java java/applet/Applet\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fR任意のディレクトリからのファイルのドキュメント化 +.RS 4 +この場合、現在のディレクトリがどこかは問題ではありません。ドキュメント化するソース・ファイルへの絶対パス(または現在のディレクトリからの相対パス)を指定して\fBjavadoc\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html /home/src/java/awt/Button\&.java\fR +\fB/home/src/java/awt/Graphics*\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +パッケージおよびクラスのドキュメント化 +.PP +パッケージ全体と個々のクラスを同時に指定してドキュメント化することもできます。次に、前述の2つの例を組み合せた例を示します。\fB\-sourcepath\fRオプションは、パッケージへのパスに対しては使用できますが、個々のクラスへのパスに対しては使用できません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src java\&.awt\fR +\fB/home/src/java/applet/Applet\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.SS "実際の例" +.PP +次のコマンドラインおよび\fBmakefile\fRバージョンの\fBjavadoc\fRコマンドをJavaプラットフォームAPIで実行します。Java SE 1\&.2で約1500個のpublicおよびprotectedクラスのドキュメントを生成するには、180MBのメモリーを使用します。どちらの例もオプションの引数で絶対パスが使用されているため、任意のディレクトリから同じ\fBjavadoc\fRコマンドを実行できます。 +.PP +コマンドラインの例 +.PP +次のコマンドは、一部のシェルに対して長すぎる可能性があります。この制限を回避するには、コマンドライン引数ファイルを使用します。または、シェル・スクリプトを記述します。 +.PP +この例では、\fBpackages\fRは処理するパッケージを含む名前で、\fBjava\&.applet\fR +\fBjava\&.lang\fRなどです。各オプションの、一重引用符で囲まれた引数の内側には、改行文字を挿入できません。たとえば、この例をコピー・アンド・ペーストする場合は、\fB\-bottom\fRオプションから改行文字を削除してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /java/jdk/src/share/classes \e\fR +\fB\-overview /java/jdk/src/share/classes/overview\&.html \e\fR +\fB\-d /java/jdk/build/api \e\fR +\fB\-use \e\fR +\fB\-splitIndex \e\fR +\fB\-windowtitle \*(AqJava Platform, Standard Edition 7 API Specification\*(Aq \e\fR +\fB\-doctitle \*(AqJava Platform, Standard Edition 7 API Specification\*(Aq \e\fR +\fB\-header \*(Aq<b>Java(TM) SE 7</b>\*(Aq \e\fR +\fB\-bottom \*(Aq<font size="\-1">\fR +\fB<a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fR +\fBCopyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&.<br/>\fR +\fBOracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fR +\fBOther names may be trademarks of their respective owners\&.</font>\*(Aq \e\fR +\fB\-group "Core Packages" "java\&.*:com\&.sun\&.java\&.*:org\&.omg\&.*" \e\fR +\fB\-group "Extension Packages" "javax\&.*" \e\fR +\fB\-J\-Xmx180m \e \fR +\fB@packages\fR + +.fi +.if n \{\ +.RE +.\} +.PP +プログラマティック・インタフェース +.PP +Javadoc Access APIでは、新しいプロセスを実行しなくても、JavadocツールをJavaアプリケーションから直接起動できます。 +.PP +たとえば、次の文はコマンド\fBjavadoc \-d /home/html \-sourcepath /home/src \-subpackages java \-exclude java\&.net:java\&.lang com\&.example\fRと同等です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport javax\&.tools\&.DocumentationTool;\fR +\fBimport javax\&.tools\&.ToolProvider;\fR + +\fBpublic class JavaAccessSample{\fR +\fB public static void main(String[] args){\fR +\fB DocumentationTool javadoc = ToolProvider\&.getSystemDocumentationTool();\fR +\fB int rc = javadoc\&.run( null, null, null,\fR +\fB "\-d", "/home/html",\fR +\fB "\-sourcepath", "home/src",\fR +\fB "\-subpackages", "java",\fR +\fB "\-exclude", "java\&.net:java\&.lang",\fR +\fB "com\&.example");\fR +\fB }\fR +\fB }\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBrun\fRメソッドの最初の3つの引数は、入力、標準出力、および標準エラー・ストリームを指定します。\fBNull\fRは\fBSystem\&.in\fR、\fBSystem\&.out\fRおよび\fBSystem\&.err\fRそれぞれのデフォルト値です。 +.SS "makefileの例" +.PP +ここでは、GNU +\fBmakefile\fRの例を示します。\fBmakefile\fRの引数は、一重引用符で囲みます。Windows +\fBmakefile\fRの例については、Javadoc FAQの\fBmakefiles\fRのセクション +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137483\&.html#makefiles)を参照してください +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath $(SRCDIR) \e /* Sets path for source files */\fR +\fB \-overview $(SRCDIR)/overview\&.html \e /* Sets file for overview text */\fR +\fB \-d /java/jdk/build/api \e /* Sets destination directory */\fR +\fB \-use \e /* Adds "Use" files */\fR +\fB \-splitIndex \e /* Splits index A\-Z */\fR +\fB \-windowtitle $(WINDOWTITLE) \e /* Adds a window title */\fR +\fB \-doctitle $(DOCTITLE) \e /* Adds a doc title */\fR +\fB \-header $(HEADER) \e /* Adds running header text */\fR +\fB \-bottom $(BOTTOM) \e /* Adds text at bottom */\fR +\fB \-group $(GROUPCORE) \e /* 1st subhead on overview page */\fR +\fB \-group $(GROUPEXT) \e /* 2nd subhead on overview page */\fR +\fB \-J\-Xmx180m \e /* Sets memory to 180MB */\fR +\fB java\&.lang java\&.lang\&.reflect \e /* Sets packages to document */\fR +\fB java\&.util java\&.io java\&.net \e\fR +\fB java\&.applet\fR +\fB \fR +\fBWINDOWTITLE = \*(AqJava(TM) SE 7 API Specification\*(Aq\fR +\fBDOCTITLE = \*(AqJava(TM) Platform Standard Edition 7 API Specification\*(Aq\fR +\fBHEADER = \*(Aq<b>Java(TM) SE 7</font>\*(Aq\fR +\fBBOTTOM = \*(Aq<font size="\-1">\fR +\fB <a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fR +\fB Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&.<br/>\fR +\fB Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fR +\fB Other names may be trademarks of their respective owners\&.</font>\*(Aq\fR +\fBGROUPCORE = \*(Aq"Core Packages" "java\&.*:com\&.sun\&.java\&.*:org\&.omg\&.*"\*(Aq\fR +\fBGROUPEXT = \*(Aq"Extension Packages" "javax\&.*"\*(Aq\fR +\fBSRCDIR = \*(Aq/java/jdk/1\&.7\&.0/src/share/classes\*(Aq\fR + +.fi +.if n \{\ +.RE +.\} +.SS "注意" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-windowtitle\fRオプションを省略すると、\fBjavadoc\fRコマンドによってドキュメント・タイトルがウィンドウ・タイトルにコピーされます。\fB\-windowtitle\fRオプションのテキストは、\fB\-doctitle\fRオプションと同じですが、HTMLタグは含まれません。これは、HTMLタグが、ウィンドウ・タイトル内にそのままのテキストとして表示されるのを防ぐためです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-footer\fRオプションを省略すると、\fBjavadoc\fRコマンドによってヘッダー・テキストがフッターにコピーされます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +この例では必要ありませんが、\fB\-classpath\fRと\fB\-link\fRも重要なオプションです。 +.RE +.SH "一般的なトラブルシューティング" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjavadoc\fRコマンドは有効なクラス名を含むファイルのみを読み取ります。\fBjavadoc\fRコマンドがファイルの内容を正しく読み取っていない場合は、クラス名が有効であることを確認します。ソース・ファイルの処理を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +一般的なbugおよびトラブルシューティングのヒントについては、Javadoc FAQ +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137483\&.html)を参照してください。 +.RE +.SH "エラーと警告" +.PP +エラーおよび警告メッセージには、ファイル名と宣言行(ドキュメンテーション・コメント内の特定の行ではない)の行番号が含まれます。 +.PP +たとえば、メッセージ\fB「エラー: Class1\&.javaを読み込めません」\fRは、\fBjavadoc\fRコマンドが\fBClass1\&.jav\fR\fBa\fRを現在のディレクトリにロードしようとしていることを意味します。クラス名はそのパス(絶対または相対)で表示されます。 +.SH "環境" +.PP +CLASSPATH +.RS 4 +\fBCLASSPATH\fRは、\fBjavadoc\fRコマンドがユーザー・クラス・ファイルの検出に使用するパスを提供する環境変数です。この環境変数は、\fB\-classpath\fRオプションによってオーバーライドされます。ディレクトリはセミコロン(Windowsの場合)またはコロン(Oracle Solarisの場合)で区切ります。 +.sp +\fBWindowsの例\fR: +\fB\&.;C:\eclasses;C:\ehome\ejava\eclasses\fR +.sp +\fBOracle Solarisの例\fR: +\fB\&.:/home/classes:/usr/local/java/classes\fR +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.SH "関連ドキュメント" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javadocテクノロジ +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/index\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラスの検出方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JavadocツールでのDocコメントの記述方法 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +URLメモ、Uniform Resource Locators +(http://www\&.ietf\&.org/rfc/rfc1738\&.txt) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +HTML標準、HTML Document Representation (4197265および4137321) +(http://www\&.w3\&.org/TR/REC\-html40/charset\&.html#h\-5\&.2\&.2) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javafxpackager.1 b/jdk-1.8.0.281/man/ja/man1/javafxpackager.1 new file mode 100755 index 0000000..93b2be0 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javafxpackager.1 @@ -0,0 +1,937 @@ +'\" t +.\" Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javafxpackager +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javafxpackager" "1" "2015å¹´3月3日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javafxpackager \- \fB注意:\fR このツールの名前は\fBjavapackager\fRに変更されています。\fBjavafxpackager\&.exe\fRファイルは、将来のリリースで削除される可能性があります。\fBjavapackager\fRを使用するように、スクリプトを更新してください。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager\fR \fIcommand\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommand\fR +.RS 4 +実行する必要のあるタスク。 +.RE +.PP +options +.RS 4 +空白で区切られた1つ以上のコマンド・オプション。 +.RE +.SH "コマンド" +.PP +次のいずれかのコマンドを指定できます。コマンドの後に、そのオプションを指定します。 +.PP +\-createbss +.RS 4 +CSSファイルをバイナリ形式に変換します。 +.RE +.PP +\-createjar +.RS 4 +他のパラメータに従ってJARアーカイブを作成します。 +.RE +.PP +\-deploy +.RS 4 +再配布用のアプリケーション・パッケージを組み立てます。デプロイ・タスクでは、デフォルトでベース・アプリケーション・パッケージが生成されますが、指定すれば自己完結型アプリケーション・パッケージも生成できます。 +.RE +.PP +\-makeall +.RS 4 +1つの呼出しで、ほとんどの引数が事前定義されたコンパイル、\fBcreatejar\fRおよび\fBdeploy\fRステップを実行し、すべての該当する自己完結型アプリケーション・パッケージの生成を試行します。ソース・ファイルは\fBsrc\fRというフォルダに配置する必要があり、生成されるファイル(JAR、JNLP、HTMLおよび自己完結型アプリケーション・パッケージ)は\fBdist\fRというフォルダに出力されます。このコマンドでは最小限の構成のみが可能で、可能な限り自動化されています。 +.RE +.PP +\-signjar +.RS 4 +指定した証明書でJARファイルに署名します。 +.RE +.SH "CREATEBSSコマンドのオプション" +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "CREATEJARコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +\fB<fx:argument>\fR要素としてJNLPファイルに挿入される名前なし引数。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-manifestAttrs \fImanifest\-attributes\fR +.RS 4 +追加のマニフェスト属性の名前と値のリスト。構文: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1=value1,name2=value2,name3=value3"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-nocss2bin +.RS 4 +パッケージャはJARにコピーする前にCSSファイルをバイナリ形式に変換しません。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "DEPLOYコマンドのオプション" +.PP +\-allpermissions +.RS 4 +指定した場合、JNLPファイル内のすべてのセキュリティ権限がアプリケーションに必要になります。 +.RE +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +JNLPファイルの\fB<fx:argument>\fR要素に挿入される名前なし引数。 +.RE +.PP +\-B\fIbundler\-argument=value\fR +.RS 4 +自己完結型アプリケーションのパッケージ化に使用するバンドラへの情報を指定します。各バンドラの引数の詳細は、自己完結型アプリケーション・バンドラの引数を参照してください。 +.RE +.PP +\-callbacks +.RS 4 +生成後のHTMLでのユーザー・コールバック方式を指定します。形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1:value1,name2:value2,\&.\&.\&."\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-description \fIdescription\fR +.RS 4 +アプリケーションの説明。 +.RE +.PP +\-embedCertificates +.RS 4 +指定した場合、証明書がJNLPファイルに埋め込まれます。 +.RE +.PP +\-embedjnlp +.RS 4 +指定した場合、JNLPファイルがHTMLドキュメントに埋め込まれます。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-htmlparamfile \fIfile\fR +.RS 4 +生成されるアプリケーションをブラウザで実行する場合のパラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-isExtension +.RS 4 +指定した場合、\fBsrcfiles\fRは拡張ファイルとして処理されます。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-native \fItype\fR +.RS 4 +自己完結型アプリケーション・バンドルを生成します(可能な場合)。\fB\-B\fRオプションを使用して、使用されているバンドラへの引数を指定します。\fItype\fRを指定すると、このタイプのバンドルのみが作成されます。タイプを指定しない場合、\fBall\fRが使用されます。 +.sp +\fItype\fRには、次の値が有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBall\fR: 実行されているプラットフォームのインストーラをすべて実行し、そのアプリケーションのディスク・イメージを作成します。\fItype\fRが指定されていない場合、この値が使用されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBinstaller\fR: 実行されているプラットフォームのインストーラをすべて実行します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBimage\fR: アプリケーションのディスク・イメージを作成します。OS Xでは、イメージは\fB\&.app\fRファイルです。Linuxでは、イメージはインストールされるディレクトリです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdmg\fR: OS X用のDMGファイルを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpkg\fR: OS X用の\fB\&.pkg\fRパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmac\&.appStore\fR: Mac App Store用のパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBrpm\fR: Linux用のRPMパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdeb\fR: Linux用のDebianパッケージを生成します。 +.RE +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-templateId +.RS 4 +テンプレート処理を行うアプリケーションのアプリケーションID。 +.RE +.PP +\-templateInFilename +.RS 4 +HTMLテンプレート・ファイルの名前。プレースホルダの形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#XXXX\&.YYYY(APPID)#\fR + +.fi +.if n \{\ +.RE +.\} +APPIDはアプリケーションの識別子であり、XXXは次のいずれかです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.URL\fR +.sp +Deployment Toolkitのdtjava\&.jsの場所。デフォルトでは、この場所は次のとおりです。 +.sp +http://java\&.com/js/dtjava\&.js +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.CODE\fR +.sp +Deployment Toolkitのdtjava\&.jsを含めるスクリプト要素。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.DYNAMIC\fR +.sp +特定のプレースホルダにアプリケーションを埋め込むコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.ONLOAD\fR +.sp +\fBonload\fRフックを使用してWebページにアプリケーションを埋め込むために必要なすべてのコード(dtjava\&.jsのインクルードを除く)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.LAUNCH\&.CODE\fR +.sp +アプリケーションの起動に必要なコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.RE +.PP +\-templateOutFilename +.RS 4 +テンプレートから生成されるHTMLファイルの名前。 +.RE +.PP +\-title \fItitle\fR +.RS 4 +アプリケーションのタイトル。 +.RE +.PP +\-vendor \fIvendor\fR +.RS 4 +アプリケーションのベンダー。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.PP +\-updatemode \fIupdate\-mode\fR +.RS 4 +JNLPファイルの更新モードを設定します。 +.RE +.SH "MAKEALLコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.SH "SIGNJARコマンドのオプション" +.PP +\-alias +.RS 4 +キーの別名。 +.RE +.PP +\-keyPass +.RS 4 +キーを復元するためのパスワード。 +.RE +.PP +\-keyStore \fIfile\fR +.RS 4 +キーストア・ファイル名。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +署名するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-storePass +.RS 4 +キーストアの整合性を確認したり、ロックを解除するためのパスワード。 +.RE +.PP +\-storeType +.RS 4 +キーストアのタイプ。デフォルト値は"jks"です。 +.RE +.SH "自己完結型アプリケーション・バンドラの引数" +.PP +自己完結型アプリケーションの作成に使用されるバンドラの引数を指定するには、\fB\-deploy\fRコマンドの\fB\-B\fRオプションを使用します。各バンドラ・タイプに、独自の引数セットがあります。 +.SS "一般的なバンドラ引数" +.PP +appVersion=\fIversion\fR +.RS 4 +アプリケーション・パッケージのバージョン。一部のバンドラでは、バージョン文字列の形式が制限されます。 +.RE +.PP +classPath=\fIpath\fR +.RS 4 +アセンブルされたアプリケーション・ディレクトリへの相対的なクラス・パス。一般的に、パスはJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +icon=\fIpath\fR +.RS 4 +起動ツールおよびその他の支援ツールに使用されるデフォルト・アイコンの場所。OS Xの場合、形式は\fB\&.icns\fRである必要があります。Linuxの場合、形式は\fB\&.png\fRである必要があります。 +.RE +.PP +identifier=\fIvalue\fR +.RS 4 +\fBmac\&.CFBundleIdentifier\fRなど、他のプラットフォーム固有の値に使用されるデフォルト値。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +jvmOptions=\fIoption\fR +.RS 4 +アプリケーションの実行時にJVMに渡されるオプション。\fBjava\fRコマンドに有効なオプションを使用できます。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmOptions=\-Xmx128m \-BjvmOptions=\-Xms128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +jvmProperties=\fIproperty\fR=\fIvalue\fR +.RS 4 +アプリケーションの実行時にVMに渡されるJavaシステム・プロパティ。\fBjava\fRコマンドの\fB\-D\fRオプションに有効なプロパティを使用できます。プロパティ名とそのプロパティの値の両方を指定します。複数のプロパティを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmProperties=apiUserName=example \-BjvmProperties=apiKey=abcdef1234567890\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +mainJar=\fIfilename\fR +.RS 4 +アプリケーションのメイン・クラスを含むJARファイルの名前。一般的に、ファイル名はJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +preferencesID=\fInode\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプションを確認するために調べるプリファレンス・ノード。指定したノードは、オプション\fB\-Dapp\&.preferences\&.id\fRとして実行時にアプリケーションに渡されます。この引数は、\fBuserJVMOptions\fR引数とともに使用されます。 +.RE +.PP +runtime=\fIpath\fR +.RS 4 +パッケージ・バンドルに含めるJREまたはJDKの場所。JDKまたはJREのルート・フォルダへのファイル・パスを指定します。システム・デフォルトJREを使用するには、次の例に示すようにパスを指定しないでください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Bruntime=\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +userJvmOptions=\fIoption\fR=\fIvalue\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプション。\fBjava\fRコマンドに有効なオプションを使用できます。オプション名とそのオプションの値の両方を指定します。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BuserJvmOptions=\-Xmx=128m \-BuserJvmOptions=\-Xms=128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SS "OS Xアプリケーション・バンドラ引数" +.PP +mac\&.category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。カテゴリは、Apple Developer Webサイトにあるカテゴリ・リスト内に含まれている必要があります。 +.RE +.PP +mac\&.CFBundleIdentifier=\fIvalue\fR +.RS 4 +\fBCFBundleIdentifier\fRの情報plistに格納されている値。この値は、グローバルに一意である必要があり、文字、数字、ドットおよびダッシュのみを含む必要があります。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +mac\&.CFBundleName=\fIname\fR +.RS 4 +OS Xメニュー・バーに表示されるアプリケーションの名前。16文字未満の名前をお薦めします。デフォルトは名前属性です。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-app=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.bundle\-id\-signing\-prefix=\fIprefix\fR +.RS 4 +plistまたは既存の署名がないバイナリがバンドル内に見つかった場合に署名済バイナリに適用される接頭辞。 +.RE +.SS "OS X DMG (ディスク・イメージ)バンドラ引数" +.PP +ディスク・イメージがマウント可能になる前に、OS X DMGインストーラは、\fBlicenseFile\fRによって指定されているライセンス・ファイル(指定されている場合)を表示します。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +systemWide=\fIboolean\fR +.RS 4 +使用対象のドラッグしてインストールするターゲットを示すフラグ。アプリケーション・フォルダを表示するには、\fBtrue\fRに設定します。デスクトップ・フォルダを表示するには、\fBfalse\fRに設定します。デフォルトは\fBtrue\fRです。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.dmg\&.simple=\fIboolean\fR +.RS 4 +AppleScriptコードの実行に依存するDMGカスタマイズ手順をスキップするかどうかを示すフラグ。\fBtrue\fRに設定して、手順をスキップします。\fBtrue\fRに設定されている場合、ディスク・ウィンドウにバックグラウンド・イメージがないため、アイコンが所定の位置に移動しません。\fBsystemWide\fR引数も\fBtrue\fRに設定されている場合、ルート・アプリケーション・フォルダのシンボリック・リンクがDMGファイルに追加されます。\fBsystemWide\fR引数が\fBfalse\fRに設定されている場合、アプリケーションのみがDMGファイルに追加され、デスクトップのリンクは追加されません。 +.RE +.SS "OS X PKGバンドラ引数" +.PP +OS X PKGインストーラは、ウィザードを示し、\fBlicenseFile\fRによって指定されているライセンス・ファイルをウィザード内のページに表示します。ユーザーはアプリケーションをインストールする前に条件に同意する必要があります。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-installer=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.SS "Mac App Storeバンドラ引数" +.PP +mac\&.app\-store\-entitlements=\fIpath\fR +.RS 4 +アプリケーションが動作する資格を含むファイルの場所。ファイルは、Appleによって指定されている形式である必要があります。ファイルへのパスは、絶対条件で指定することも、\fBjavapackager\fRの呼出しに対して相対的に指定することもできます。資格を指定しない場合、アプリケーションは、通常のアプレット・サンドボックスよりもより厳しいサンドボックスで動作し、ネットワーク・ソケットおよびすべてのファイルへのアクセスが拒否されます。 +.RE +.PP +mac\&.signing\-key\-app=\fIkey\fR +.RS 4 +Mac App Storeのアプリケーション署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.signing\-key\-pkg=\fIkey\fR +.RS 4 +Mac App Storeのインストーラ署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.SS "Linux Debianバンドラ引数" +.PP +\fBlicenseFile\fRによって指定されているライセンス・ファイルは、すべてのケースにおいてユーザーに示されませんが、ファイルはアプリケーション・メタデータに含まれています。 +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +copyright=\fIstring\fR +.RS 4 +アプリケーションのコピーライト文字列。この引数は、Debianメタデータで使用されます。 +.RE +.PP +email=\fIaddress\fR +.RS 4 +DebianのMaintainerフィールドで使用される電子メール・アドレスです。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。この引数は、DebianのMaintainerフィールドで使用されます。 +.RE +.SS "Linux RPMバンドラ引数" +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。 +.RE +.SH "非推奨オプション" +.PP +次のオプションは、パッケージ化ツールで使用されておらず、存在していても無視されます。 +.PP +\-runtimeversion \fIversion\fR +.RS 4 +必要なJavaFXランタイムのバージョン。非推奨。 +.RE +.PP +\-noembedlauncher +.RS 4 +指定した場合、パッケージャはJARファイルにJavaFX起動クラスを追加しません。非推奨。 +.RE +.SH "注意" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +タスク・コマンドとともに\fB\-v \fRオプションを使用すれば、詳細な出力が有効になります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-srcdir\fRオプションをコマンドで使用できる場合は、複数回使用できます。\fB\-srcfiles\fRオプションを指定すると、引数に指定されたファイル名が、その前に指定されている\fBsrcdir\fRオプションで指定された場所で検索されます。\fB\-srcdir\fRが\fB\-srcfiles\fRの前に指定されていない場合は、\fBjavapackager\fRコマンドが実行されるディレクトリが使用されます。 +.RE +.SH "例" +.PP +\fB例 1 \fR\-createjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-createjar \-appclass package\&.ClassName\fR +\fB \-srcdir classes \-outdir out \-outfile outjar \-v\fR + +.fi +.if n \{\ +.RE +.\} +\fBclasses\fRディレクトリの内容を\fBoutjar\&.jar\fRにパッケージ化して、アプリケーション・クラスを\fBpackage\&.ClassName\fRに設定します。 +.RE +.PP +\fB例 2 \fR\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fR +\fB \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fR + +.fi +.if n \{\ +.RE +.\} +\fBoutfile\&.jnlp\fRおよび対応する\fBoutfile\&.html\fRファイルをアプリケーション\fBAppName\fRの\fBoutdir\fRに生成します。これは\fBpackage\&.ClassName\fRで開始し、34 x 43ピクセルのサイズです。 +.RE +.PP +\fB例 3 \fR\-makeallコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fR +\fB\-height 600\fR + +.fi +.if n \{\ +.RE +.\} +コンパイルを含むすべてのパッケージ化作業(\fBcreatejar\fRおよび\fBdeploy\fR)を実行します。 +.RE +.PP +\fB例 4 \fR\-signjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fR +\fB\-alias duke \-keypass **** \-srcdir dist\fR + +.fi +.if n \{\ +.RE +.\} +\fBdist\fRディレクトリにあるすべてのJARファイルに署名し、alias、\fBkeyStore\fRおよび\fBstorePass\fRを指定して証明書を添付し、署名されたJARファイルを\fBdist\fRディレクトリに戻します。 +.RE +.PP +\fB例 5 \fRバンドラ引数を伴う\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-native deb \-Bcategory=Education \-BjvmOptions=\-Xmx128m \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB \-BjvmOptions=\-Xms128m \-outdir packages \-outfile BrickBreaker \-srcdir dist \fR +\fB \-srcfiles BrickBreaker\&.jar \-appclass brickbreaker\&.Main \-name BrickBreaker \fR +\fB \-title "BrickBreaker demo"\fR + +.fi +.if n \{\ +.RE +.\} +自己完結型アプリケーションとしてBrickBreakerアプリケーションを実行するためのネイティブLinux Debianパッケージを生成します。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javah.1 b/jdk-1.8.0.281/man/ja/man1/javah.1 new file mode 100755 index 0000000..f358e9b --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javah.1 @@ -0,0 +1,203 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javah +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javah" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javah \- JavaクラスからCヘッダーとソース・ファイルを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavah\fR [ \fIoptions\fR ] f\fIully\-qualified\-class\-name \&.\&.\&.\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIfully\-qualified\-class\-name\fR +.RS 4 +Cヘッダーとソース・ファイルに変換されるクラスの完全修飾された場所。 +.RE +.SH "説明" +.PP +\fBjavah\fRコマンドは、ネイティブ・メソッドを実装するために必要なCヘッダーとソース・ファイルを生成します。作成されたヘッダーとソース・ファイルは、ネイティブ・ソース・コードからオブジェクトのインスタンス変数を参照するためにCプログラムによって使用されます。\fB\&.h\fRファイルは、対応するクラスと一致する配置を持つ\fBstruct\fR定義を含みます。\fBstruct\fRのフィールドは、クラスのインスタンス変数に対応します。 +.PP +ヘッダー・ファイルとその中で宣言される構造体の名前はクラスの名前から派生します。\fBjavah\fRコマンドに渡されるクラスがパッケージの中にある場合、パッケージ名はヘッダー・ファイル名と構造体名の両方の先頭に付加されます。下線(_)が名前の区切り文字として使用されます。 +.PP +デフォルトでは\fBjavah\fRコマンドは、コマンド行にリストされる各クラスのヘッダー・ファイルを作成し、現在のディレクトリにファイルを置きます。ソース・ファイルを作成するには、\fB\-stubs\fRオプションを使用してください。1つのファイルの中に、リストされたすべてのクラスの結果を連結するには、\fB\-o\fRオプションを使用してください。 +.PP +Java Native Interface (JNI)はヘッダー情報またはスタブ・ファイルを必要としません。\fBjavah\fRコマンドは引き続きJNI形式のネイティブ・メソッドに必要なネイティブ・メソッド関数プロトタイプの生成に使用できます。\fBjavah\fRコマンドはデフォルトでJNI形式の出力を生成し、その結果を\fB\&.h\fRファイルに格納します。 +.SH "オプション" +.PP +\-o \fIoutputfile\fR +.RS 4 +コマンドラインにリストされたすべてのクラスに対して、結果のヘッダーまたはソース・ファイルを連結して出力ファイルに格納します。\fB\-o\fRまたは\fB\-d\fRのどちらかのみ使用できます。 +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +\fBjavah\fRがヘッダー・ファイルまたはスタブ・ファイルを保存する、ディレクトリを設定します。\fB\-d\fRまたは\fB\-o\fRのどちらかのみ使用できます。 +.RE +.PP +\-stubs +.RS 4 +\fBjavah\fRコマンドが、Javaオブジェクト・ファイルからC宣言を生成します。 +.RE +.PP +\-verbose +.RS 4 +詳細出力を指定し、作成ファイルの状態に関するメッセージを、\fBjavah\fRコマンドが\fB標準出力\fRに出力します。 +.RE +.PP +\-help +.RS 4 +\fBjavah\fRの使用方法についてのヘルプ・メッセージを出力します。 +.RE +.PP +\-version +.RS 4 +\fBjavah\fRコマンドのリリース情報を出力します。 +.RE +.PP +\-jni +.RS 4 +JNI形式のネイティブ・メソッド機能プロトタイプを含む出力ファイルを、\fBjavah\fRコマンドが作成します。これは標準出力であるため、\fB\-jni\fRの使用はオプションです。 +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +クラスを探すために\fBjavah\fRコマンドが使用するパスを指定します。デフォルトまたは\fBCLASSPATH\fR環境変数の設定をオーバーライドします。ディレクトリはOracle Solarisの場合はコロンで、Windowsの場合はセミコロンで区切られます。パスの一般的な形式は次のようになります。 +.sp +\fBOracle Solaris\fRの場合: +.sp +\&.:\fIyour\-path\fR +.sp +例: +\fB\&.:/home/avh/classes:/usr/local/java/classes\fR +.sp +\fBWindows\fRの場合: +.sp +\&.;\fIyour\-path\fR +.sp +例: +\fB\&.;C:\eusers\edac\eclasses;C:\etools\ejava\eclasses\fR +.sp +便宜上、*のベース名を含むクラス・パス要素は、\fB\&.jar\fRまたは\fB\&.JAR\fRを拡張子に持つディレクトリ内のすべてのファイルのリストを指定するのと同等とみなされます。 +.sp +たとえば、ディレクトリ\fBmydir\fRに\fBa\&.jar\fRと\fBb\&.JAR\fRが含まれている場合、クラス・パス要素\fBmydir/*\fRは\fBA\fR\fB\&.jar:b\&.JAR\fRに展開されますが、JARファイルの順番は未指定となります。このリストには、隠しファイルも含め、指定されたディレクトリ内のすべてのJARファイルが含まれます。*からなるクラス・パス・エントリは、現在のディレクトリ内のすべてのJARファイルのリストに展開されます。\fBCLASSPATH\fR環境変数も、定義時には同様に展開されます。クラス・パスのワイルドカードの展開は、Java Virtual Machine (JVM)の開始前に行われます。Javaプログラムは、環境を問い合せる場合を除き、展開されていないワイルドカードを参照しません。たとえば、\fBSystem\&.getenv("CLASSPATH")\fRをコールして問い合せる場合です。 +.RE +.PP +\-bootclasspath \fIpath\fR +.RS 4 +ブートストラップ・クラスをロードするパスを指定します。ブートストラップ・クラスは、デフォルトでは\fBjre\elib\ert\&.jar\fRおよび他のいくつかのJARファイルにある、コアJavaプラットフォームを実装するクラスです。 +.RE +.PP +\-old +.RS 4 +古いJDK 1\&.0形式のヘッダー・ファイルを生成するように指定します。 +.RE +.PP +\-force +.RS 4 +出力ファイルが常に書き込まれるように指定します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javap.1 b/jdk-1.8.0.281/man/ja/man1/javap.1 new file mode 100755 index 0000000..5fa61dc --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javap.1 @@ -0,0 +1,348 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javap +.\" Language: Japanese +.\" Date: 2014å¹´8月8日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javap" "1" "2014å¹´8月8日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javap \- 1つ以上のクラス・ファイルを逆アセンブルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavap\fR [\fIoptions\fR] \fIclassfile\fR\&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclassfile\fR +.RS 4 +注釈の処理対象となる、空白で区切った1つ以上のクラス(DocFooter\&.classなど)。クラス・パスで検出できるクラスを、ファイル名またはURL(\fBfile:///home/user/myproject/src/DocFooter\&.class\fRなど)で指定できます。 +.RE +.SH "説明" +.PP +\fBjavap\fRコマンドは、1つまたは複数のクラス・ファイルを逆アセンブルします。その出力は指定するオプションにより異なります。オプションを指定しない場合、\fBjavap\fRコマンドは、そのパッケージ、渡されたクラスのprotectedおよびpublicのフィールドとメソッドを出力します。\fBjavap\fRコマンドはその出力を\fB標準出力\fRに表示します。 +.SH "オプション" +.PP +\-help +.br +\-\-help +.br +\-? +.RS 4 +\fBjavap\fRコマンドについてのヘルプ・メッセージを出力します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-l +.RS 4 +行番号とローカル変数表を出力します。 +.RE +.PP +\-public +.RS 4 +publicクラスおよびメンバーのみ表示します。 +.RE +.PP +\-protected +.RS 4 +protectedおよびpublicのクラスとメンバーのみを表示します。 +.RE +.PP +\-private +.br +\-p +.RS 4 +すべてのクラスとメンバーを表示します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定されたオプションをJVMに渡します。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavap \-J\-version\fR +\fBjavap \-J\-Djava\&.security\&.manager \-J\-Djava\&.security\&.policy=MyPolicy MyClassName\fR + +.fi +.if n \{\ +.RE +.\} +JVMオプションの詳細は、コマンドのマニュアルを参照してください。 +.RE +.PP +\-s +.RS 4 +内部の型シグニチャを出力します。 +.RE +.PP +\-sysinfo +.RS 4 +処理中のクラスのシステム情報(パス、サイズ、日付、MD5ハッシュ)を表示します。 +.RE +.PP +\-constants +.RS 4 +\fBstatic final\fR定数を表示します。 +.RE +.PP +\-c +.RS 4 +クラスの各メソッドのために逆アセンブルされるコード、すなわちJavaバイトコードからなる命令を表示します。 +.RE +.PP +\-verbose +.RS 4 +メソッドのスタック・サイズ、localsとargumentsの数を出力します。 +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +クラスを探すために\fBjavap\fRコマンドが使用するパスを指定します。デフォルトまたは\fBCLASSPATH\fR環境変数の設定を上書きします。 +.RE +.PP +\-bootclasspath \fIpath\fR +.RS 4 +ブートストラップ・クラスをロードするパスを指定します。ブートストラップ・クラスは、デフォルトでは\fBjre/lib/rt\&.jar\fRおよび他のいくつかのJARファイルにある、コアJavaプラットフォームを実装するクラスです。 +.RE +.PP +\-extdir \fIdirs\fR +.RS 4 +インストールされた拡張機能を検索する場所をオーバーライドします。拡張機能のデフォルト位置は\fBjava\&.ext\&.dirs\fRです。 +.RE +.SH "例" +.PP +次の\fBDocFooter\fRクラスをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.awt\&.*;\fR +\fBimport java\&.applet\&.*;\fR +\fB \fR +\fBpublic class DocFooter extends Applet {\fR +\fB String date;\fR +\fB String email;\fR +\fB \fR +\fB public void init() {\fR +\fB resize(500,100);\fR +\fB date = getParameter("LAST_UPDATED");\fR +\fB email = getParameter("EMAIL");\fR +\fB }\fR +\fB \fR +\fB public void paint(Graphics g) {\fR +\fB g\&.drawString(date + " by ",100, 15);\fR +\fB g\&.drawString(email,290,15);\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavap DocFooter\&.class\fRコマンドからの出力は次を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompiled from "DocFooter\&.java"\fR +\fBpublic class DocFooter extends java\&.applet\&.Applet {\fR +\fB java\&.lang\&.String date;\fR +\fB java\&.lang\&.String email;\fR +\fB public DocFooter();\fR +\fB public void init();\fR +\fB public void paint(java\&.awt\&.Graphics);\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavap \-c DocFooter\&.class\fRコマンドからの出力は次を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompiled from "DocFooter\&.java"\fR +\fBpublic class DocFooter extends java\&.applet\&.Applet {\fR +\fB java\&.lang\&.String date;\fR +\fB java\&.lang\&.String email;\fR + +\fB public DocFooter();\fR +\fB Code:\fR +\fB 0: aload_0 \fR +\fB 1: invokespecial #1 // Method\fR +\fBjava/applet/Applet\&."<init>":()V\fR +\fB 4: return \fR + +\fB public void init();\fR +\fB Code:\fR +\fB 0: aload_0 \fR +\fB 1: sipush 500\fR +\fB 4: bipush 100\fR +\fB 6: invokevirtual #2 // Method resize:(II)V\fR +\fB 9: aload_0 \fR +\fB 10: aload_0 \fR +\fB 11: ldc #3 // String LAST_UPDATED\fR +\fB 13: invokevirtual #4 // Method\fR +\fB getParameter:(Ljava/lang/String;)Ljava/lang/String;\fR +\fB 16: putfield #5 // Field date:Ljava/lang/String;\fR +\fB 19: aload_0 \fR +\fB 20: aload_0 \fR +\fB 21: ldc #6 // String EMAIL\fR +\fB 23: invokevirtual #4 // Method\fR +\fB getParameter:(Ljava/lang/String;)Ljava/lang/String;\fR +\fB 26: putfield #7 // Field email:Ljava/lang/String;\fR +\fB 29: return \fR + +\fB public void paint(java\&.awt\&.Graphics);\fR +\fB Code:\fR +\fB 0: aload_1 \fR +\fB 1: new #8 // class java/lang/StringBuilder\fR +\fB 4: dup \fR +\fB 5: invokespecial #9 // Method\fR +\fB java/lang/StringBuilder\&."<init>":()V\fR +\fB 8: aload_0 \fR +\fB 9: getfield #5 // Field date:Ljava/lang/String;\fR +\fB 12: invokevirtual #10 // Method\fR +\fB java/lang/StringBuilder\&.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;\fR +\fB 15: ldc #11 // String by \fR +\fB 17: invokevirtual #10 // Method\fR +\fB java/lang/StringBuilder\&.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;\fR +\fB 20: invokevirtual #12 // Method\fR +\fB java/lang/StringBuilder\&.toString:()Ljava/lang/String;\fR +\fB 23: bipush 100\fR +\fB 25: bipush 15\fR +\fB 27: invokevirtual #13 // Method\fR +\fB java/awt/Graphics\&.drawString:(Ljava/lang/String;II)V\fR +\fB 30: aload_1 \fR +\fB 31: aload_0 \fR +\fB 32: getfield #7 // Field email:Ljava/lang/String;\fR +\fB 35: sipush 290\fR +\fB 38: bipush 15\fR +\fB 40: invokevirtual #13 // Method\fR +\fBjava/awt/Graphics\&.drawString:(Ljava/lang/String;II)V\fR +\fB 43: return \fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdeps(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javapackager.1 b/jdk-1.8.0.281/man/ja/man1/javapackager.1 new file mode 100755 index 0000000..47b10bb --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javapackager.1 @@ -0,0 +1,937 @@ +'\" t +.\" Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javapackager +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javapackager" "1" "2015å¹´3月3日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javapackager \- JavaおよびJavaFXアプリケーションのパッケージ化と署名に関連するタスクを実行します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager\fR \fIcommand\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommand\fR +.RS 4 +実行する必要のあるタスク。 +.RE +.PP +options +.RS 4 +空白で区切られた1つ以上のコマンド・オプション。 +.RE +.SH "コマンド" +.PP +次のいずれかのコマンドを指定できます。コマンドの後に、そのオプションを指定します。 +.PP +\-createbss +.RS 4 +CSSファイルをバイナリ形式に変換します。 +.RE +.PP +\-createjar +.RS 4 +他のパラメータに従ってJARアーカイブを作成します。 +.RE +.PP +\-deploy +.RS 4 +再配布用のアプリケーション・パッケージを組み立てます。デプロイ・タスクでは、デフォルトでベース・アプリケーション・パッケージが生成されますが、指定すれば自己完結型アプリケーション・パッケージも生成できます。 +.RE +.PP +\-makeall +.RS 4 +1つの呼出しで、ほとんどの引数が事前定義されたコンパイル、\fBcreatejar\fRおよび\fBdeploy\fRステップを実行し、すべての該当する自己完結型アプリケーション・パッケージの生成を試行します。ソース・ファイルは\fBsrc\fRというフォルダに配置する必要があり、生成されるファイル(JAR、JNLP、HTMLおよび自己完結型アプリケーション・パッケージ)は\fBdist\fRというフォルダに出力されます。このコマンドでは最小限の構成のみが可能で、可能な限り自動化されています。 +.RE +.PP +\-signjar +.RS 4 +指定した証明書でJARファイルに署名します。 +.RE +.SH "CREATEBSSコマンドのオプション" +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "CREATEJARコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +\fB<fx:argument>\fR要素としてJNLPファイルに挿入される名前なし引数。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-manifestAttrs \fImanifest\-attributes\fR +.RS 4 +追加のマニフェスト属性の名前と値のリスト。構文: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1=value1,name2=value2,name3=value3"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-nocss2bin +.RS 4 +パッケージャはJARにコピーする前にCSSファイルをバイナリ形式に変換しません。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "DEPLOYコマンドのオプション" +.PP +\-allpermissions +.RS 4 +指定した場合、JNLPファイル内のすべてのセキュリティ権限がアプリケーションに必要になります。 +.RE +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +JNLPファイルの\fB<fx:argument>\fR要素に挿入される名前なし引数。 +.RE +.PP +\-B\fIbundler\-argument=value\fR +.RS 4 +自己完結型アプリケーションのパッケージ化に使用するバンドラへの情報を指定します。各バンドラの引数の詳細は、自己完結型アプリケーション・バンドラの引数を参照してください。 +.RE +.PP +\-callbacks +.RS 4 +生成後のHTMLでのユーザー・コールバック方式を指定します。形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1:value1,name2:value2,\&.\&.\&."\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-description \fIdescription\fR +.RS 4 +アプリケーションの説明。 +.RE +.PP +\-embedCertificates +.RS 4 +指定した場合、証明書がJNLPファイルに埋め込まれます。 +.RE +.PP +\-embedjnlp +.RS 4 +指定した場合、JNLPファイルがHTMLドキュメントに埋め込まれます。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-htmlparamfile \fIfile\fR +.RS 4 +生成されるアプリケーションをブラウザで実行する場合のパラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-isExtension +.RS 4 +指定した場合、\fBsrcfiles\fRは拡張ファイルとして処理されます。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-native \fItype\fR +.RS 4 +自己完結型アプリケーション・バンドルを生成します(可能な場合)。\fB\-B\fRオプションを使用して、使用されているバンドラへの引数を指定します。\fItype\fRを指定すると、このタイプのバンドルのみが作成されます。タイプを指定しない場合、\fBall\fRが使用されます。 +.sp +\fItype\fRには、次の値が有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBall\fR: 実行されているプラットフォームのインストーラをすべて実行し、そのアプリケーションのディスク・イメージを作成します。\fItype\fRが指定されていない場合、この値が使用されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBinstaller\fR: 実行されているプラットフォームのインストーラをすべて実行します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBimage\fR: アプリケーションのディスク・イメージを作成します。OS Xでは、イメージは\fB\&.app\fRファイルです。Linuxでは、イメージはインストールされるディレクトリです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdmg\fR: OS X用のDMGファイルを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpkg\fR: OS X用の\fB\&.pkg\fRパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmac\&.appStore\fR: Mac App Store用のパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBrpm\fR: Linux用のRPMパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdeb\fR: Linux用のDebianパッケージを生成します。 +.RE +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-templateId +.RS 4 +テンプレート処理を行うアプリケーションのアプリケーションID。 +.RE +.PP +\-templateInFilename +.RS 4 +HTMLテンプレート・ファイルの名前。プレースホルダの形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#XXXX\&.YYYY(APPID)#\fR + +.fi +.if n \{\ +.RE +.\} +APPIDはアプリケーションの識別子であり、XXXは次のいずれかです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.URL\fR +.sp +Deployment Toolkitのdtjava\&.jsの場所。デフォルトでは、この場所は次のとおりです。 +.sp +http://java\&.com/js/dtjava\&.js +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.CODE\fR +.sp +Deployment Toolkitのdtjava\&.jsを含めるスクリプト要素。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.DYNAMIC\fR +.sp +特定のプレースホルダにアプリケーションを埋め込むコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.ONLOAD\fR +.sp +\fBonload\fRフックを使用してWebページにアプリケーションを埋め込むために必要なすべてのコード(dtjava\&.jsのインクルードを除く)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.LAUNCH\&.CODE\fR +.sp +アプリケーションの起動に必要なコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.RE +.PP +\-templateOutFilename +.RS 4 +テンプレートから生成されるHTMLファイルの名前。 +.RE +.PP +\-title \fItitle\fR +.RS 4 +アプリケーションのタイトル。 +.RE +.PP +\-vendor \fIvendor\fR +.RS 4 +アプリケーションのベンダー。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.PP +\-updatemode \fIupdate\-mode\fR +.RS 4 +JNLPファイルの更新モードを設定します。 +.RE +.SH "MAKEALLコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.SH "SIGNJARコマンドのオプション" +.PP +\-alias +.RS 4 +キーの別名。 +.RE +.PP +\-keyPass +.RS 4 +キーを復元するためのパスワード。 +.RE +.PP +\-keyStore \fIfile\fR +.RS 4 +キーストア・ファイル名。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +署名するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-storePass +.RS 4 +キーストアの整合性を確認したり、ロックを解除するためのパスワード。 +.RE +.PP +\-storeType +.RS 4 +キーストアのタイプ。デフォルト値は"jks"です。 +.RE +.SH "自己完結型アプリケーション・バンドラの引数" +.PP +自己完結型アプリケーションの作成に使用されるバンドラの引数を指定するには、\fB\-deploy\fRコマンドの\fB\-B\fRオプションを使用します。各バンドラ・タイプに、独自の引数セットがあります。 +.SS "一般的なバンドラ引数" +.PP +appVersion=\fIversion\fR +.RS 4 +アプリケーション・パッケージのバージョン。一部のバンドラでは、バージョン文字列の形式が制限されます。 +.RE +.PP +classPath=\fIpath\fR +.RS 4 +アセンブルされたアプリケーション・ディレクトリへの相対的なクラス・パス。一般的に、パスはJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +icon=\fIpath\fR +.RS 4 +起動ツールおよびその他の支援ツールに使用されるデフォルト・アイコンの場所。OS Xの場合、形式は\fB\&.icns\fRである必要があります。Linuxの場合、形式は\fB\&.png\fRである必要があります。 +.RE +.PP +identifier=\fIvalue\fR +.RS 4 +\fBmac\&.CFBundleIdentifier\fRなど、他のプラットフォーム固有の値に使用されるデフォルト値。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +jvmOptions=\fIoption\fR +.RS 4 +アプリケーションの実行時にJVMに渡されるオプション。\fBjava\fRコマンドに有効なオプションを使用できます。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmOptions=\-Xmx128m \-BjvmOptions=\-Xms128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +jvmProperties=\fIproperty\fR=\fIvalue\fR +.RS 4 +アプリケーションの実行時にVMに渡されるJavaシステム・プロパティ。\fBjava\fRコマンドの\fB\-D\fRオプションに有効なプロパティを使用できます。プロパティ名とそのプロパティの値の両方を指定します。複数のプロパティを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmProperties=apiUserName=example \-BjvmProperties=apiKey=abcdef1234567890\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +mainJar=\fIfilename\fR +.RS 4 +アプリケーションのメイン・クラスを含むJARファイルの名前。一般的に、ファイル名はJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +preferencesID=\fInode\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプションを確認するために調べるプリファレンス・ノード。指定したノードは、オプション\fB\-Dapp\&.preferences\&.id\fRとして実行時にアプリケーションに渡されます。この引数は、\fBuserJVMOptions\fR引数とともに使用されます。 +.RE +.PP +runtime=\fIpath\fR +.RS 4 +パッケージ・バンドルに含めるJREまたはJDKの場所。JDKまたはJREのルート・フォルダへのファイル・パスを指定します。システム・デフォルトJREを使用するには、次の例に示すようにパスを指定しないでください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Bruntime=\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +userJvmOptions=\fIoption\fR=\fIvalue\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプション。\fBjava\fRコマンドに有効なオプションを使用できます。オプション名とそのオプションの値の両方を指定します。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BuserJvmOptions=\-Xmx=128m \-BuserJvmOptions=\-Xms=128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SS "OS Xアプリケーション・バンドラ引数" +.PP +mac\&.category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。カテゴリは、Apple Developer Webサイトにあるカテゴリ・リスト内に含まれている必要があります。 +.RE +.PP +mac\&.CFBundleIdentifier=\fIvalue\fR +.RS 4 +\fBCFBundleIdentifier\fRの情報plistに格納されている値。この値は、グローバルに一意である必要があり、文字、数字、ドットおよびダッシュのみを含む必要があります。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +mac\&.CFBundleName=\fIname\fR +.RS 4 +OS Xメニュー・バーに表示されるアプリケーションの名前。16文字未満の名前をお薦めします。デフォルトは名前属性です。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-app=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.bundle\-id\-signing\-prefix=\fIprefix\fR +.RS 4 +plistまたは既存の署名がないバイナリがバンドル内に見つかった場合に署名済バイナリに適用される接頭辞。 +.RE +.SS "OS X DMG (ディスク・イメージ)バンドラ引数" +.PP +ディスク・イメージがマウント可能になる前に、OS X DMGインストーラは、\fBlicenseFile\fRによって指定されているライセンス・ファイル(指定されている場合)を表示します。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +systemWide=\fIboolean\fR +.RS 4 +使用対象のドラッグしてインストールするターゲットを示すフラグ。アプリケーション・フォルダを表示するには、\fBtrue\fRに設定します。デスクトップ・フォルダを表示するには、\fBfalse\fRに設定します。デフォルトは\fBtrue\fRです。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.dmg\&.simple=\fIboolean\fR +.RS 4 +AppleScriptコードの実行に依存するDMGカスタマイズ手順をスキップするかどうかを示すフラグ。\fBtrue\fRに設定して、手順をスキップします。\fBtrue\fRに設定されている場合、ディスク・ウィンドウにバックグラウンド・イメージがないため、アイコンが所定の位置に移動しません。\fBsystemWide\fR引数も\fBtrue\fRに設定されている場合、ルート・アプリケーション・フォルダのシンボリック・リンクがDMGファイルに追加されます。\fBsystemWide\fR引数が\fBfalse\fRに設定されている場合、アプリケーションのみがDMGファイルに追加され、デスクトップのリンクは追加されません。 +.RE +.SS "OS X PKGバンドラ引数" +.PP +OS X PKGインストーラは、ウィザードを示し、\fBlicenseFile\fRによって指定されているライセンス・ファイルをウィザード内のページに表示します。ユーザーはアプリケーションをインストールする前に条件に同意する必要があります。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-installer=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.SS "Mac App Storeバンドラ引数" +.PP +mac\&.app\-store\-entitlements=\fIpath\fR +.RS 4 +アプリケーションが動作する資格を含むファイルの場所。ファイルは、Appleによって指定されている形式である必要があります。ファイルへのパスは、絶対条件で指定することも、\fBjavapackager\fRの呼出しに対して相対的に指定することもできます。資格を指定しない場合、アプリケーションは、通常のアプレット・サンドボックスよりもより厳しいサンドボックスで動作し、ネットワーク・ソケットおよびすべてのファイルへのアクセスが拒否されます。 +.RE +.PP +mac\&.signing\-key\-app=\fIkey\fR +.RS 4 +Mac App Storeのアプリケーション署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.signing\-key\-pkg=\fIkey\fR +.RS 4 +Mac App Storeのインストーラ署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。このバージョンが既存のアプリケーションのアップグレードである場合、値は以前のバージョン番号より大きくする必要があります。 +.RE +.SS "Linux Debianバンドラ引数" +.PP +\fBlicenseFile\fRによって指定されているライセンス・ファイルは、すべてのケースにおいてユーザーに示されませんが、ファイルはアプリケーション・メタデータに含まれています。 +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +copyright=\fIstring\fR +.RS 4 +アプリケーションのコピーライト文字列。この引数は、Debianメタデータで使用されます。 +.RE +.PP +email=\fIaddress\fR +.RS 4 +DebianのMaintainerフィールドで使用される電子メール・アドレスです。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。この引数は、DebianのMaintainerフィールドで使用されます。 +.RE +.SS "Linux RPMバンドラ引数" +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。 +.RE +.SH "非推奨オプション" +.PP +次のオプションは、パッケージ化ツールで使用されておらず、存在していても無視されます。 +.PP +\-runtimeversion \fIversion\fR +.RS 4 +必要なJavaFXランタイムのバージョン。非推奨。 +.RE +.PP +\-noembedlauncher +.RS 4 +指定した場合、パッケージャはJARファイルにJavaFX起動クラスを追加しません。非推奨。 +.RE +.SH "注意" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +タスク・コマンドとともに\fB\-v \fRオプションを使用すれば、詳細な出力が有効になります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-srcdir\fRオプションをコマンドで使用できる場合は、複数回使用できます。\fB\-srcfiles\fRオプションを指定すると、引数に指定されたファイル名が、その前に指定されている\fBsrcdir\fRオプションで指定された場所で検索されます。\fB\-srcdir\fRが\fB\-srcfiles\fRの前に指定されていない場合は、\fBjavapackager\fRコマンドが実行されるディレクトリが使用されます。 +.RE +.SH "例" +.PP +\fB例 1 \fR\-createjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-createjar \-appclass package\&.ClassName\fR +\fB \-srcdir classes \-outdir out \-outfile outjar \-v\fR + +.fi +.if n \{\ +.RE +.\} +\fBclasses\fRディレクトリの内容を\fBoutjar\&.jar\fRにパッケージ化して、アプリケーション・クラスを\fBpackage\&.ClassName\fRに設定します。 +.RE +.PP +\fB例 2 \fR\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fR +\fB \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fR + +.fi +.if n \{\ +.RE +.\} +\fBoutfile\&.jnlp\fRおよび対応する\fBoutfile\&.html\fRファイルをアプリケーション\fBAppName\fRの\fBoutdir\fRに生成します。これは\fBpackage\&.ClassName\fRで開始し、34 x 43ピクセルのサイズです。 +.RE +.PP +\fB例 3 \fR\-makeallコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fR +\fB\-height 600\fR + +.fi +.if n \{\ +.RE +.\} +コンパイルを含むすべてのパッケージ化作業(\fBcreatejar\fRおよび\fBdeploy\fR)を実行します。 +.RE +.PP +\fB例 4 \fR\-signjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fR +\fB\-alias duke \-keypass **** \-srcdir dist\fR + +.fi +.if n \{\ +.RE +.\} +\fBdist\fRディレクトリにあるすべてのJARファイルに署名し、alias、\fBkeyStore\fRおよび\fBstorePass\fRを指定して証明書を添付し、署名されたJARファイルを\fBdist\fRディレクトリに戻します。 +.RE +.PP +\fB例 5 \fRバンドラ引数を伴う\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-native deb \-Bcategory=Education \-BjvmOptions=\-Xmx128m \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB \-BjvmOptions=\-Xms128m \-outdir packages \-outfile BrickBreaker \-srcdir dist \fR +\fB \-srcfiles BrickBreaker\&.jar \-appclass brickbreaker\&.Main \-name BrickBreaker \fR +\fB \-title "BrickBreaker demo"\fR + +.fi +.if n \{\ +.RE +.\} +自己完結型アプリケーションとしてBrickBreakerアプリケーションを実行するためのネイティブLinux Debianパッケージを生成します。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/javaws.1 b/jdk-1.8.0.281/man/ja/man1/javaws.1 new file mode 100755 index 0000000..9442992 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/javaws.1 @@ -0,0 +1,215 @@ +'\" t +.\" Copyright (c) 2003, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javaws +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Web Startツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javaws" "1" "2013å¹´11月21日" "JDK 8" "Java Web Startツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javaws \- Java Web Startを起動します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavaws\fR [ \fIrun\-options\fR ] \fIjnlp\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavaws\fR [ \fIcontrol\-options\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIrun\-options\fR +.RS 4 +コマンド行\fB実行オプション\fR。\fB実行オプション\fRは任意の順序で指定できます。実行オプションを参照してください。 +.RE +.PP +\fIjnlp\fR +.RS 4 +JNLP (Java Network Launching Protocol)ファイルのパスまたはURL (Uniform Resource Locator)のどちらか。 +.RE +.PP +\fI制御オプション\fR +.RS 4 +コマンド行\fB制御オプション\fR。\fB制御オプション\fRは任意の順序で指定できます。制御オプションを参照してください。 +.RE +.SH "説明" +.PP +\fB注意:\fR +\fBjavaws\fRコマンドは、Oracle Solarisでは使用できません。 +.PP +\fBjavaws\fRコマンドは、JNLPのリファレンス実装であるJava Web Startを起動します。Java Web Startは、ネットワーク上で動作するJavaアプリケーションおよびアプレットを起動します。 +.PP +JNLPファイルが指定されると、\fBjavaws\fRコマンドはJNLPファイルで指定したJavaアプリケーションまたはアプレットを起動します。 +.PP +\fBjavaws\fR起動ツールには、現在のリリースでサポートされている1組のオプションがあります。ただし、これらのオプションは将来のリリースでは削除される可能性があります。 +.SH "実行オプション" +.PP +\-offline +.RS 4 +Java Web Startをオフライン・モードで実行します。 +.RE +.PP +\-Xnosplash +.RS 4 +初期スプラッシュ画面を表示しません。 +.RE +.PP +\-open \fIarguments\fR +.RS 4 +このオプションを指定すると、JNLPファイル内の引数が\fB\-open\fR +\fBarguments\fRに置き換わります。 +.RE +.PP +\-print \fIarguments\fR +.RS 4 +このオプションを指定すると、JNLPファイル内の引数が\fB\-print\fR +\fBarguments\fRに置き換わります。 +.RE +.PP +\-online +.RS 4 +オンライン・モードを使用します。これは、デフォルトの動作です。 +.RE +.PP +\-wait +.RS 4 +\fBjavaws\fRプロセスは、アプリケーションが終了するまで終了しません。Windowsプラットフォーム上では、このオプションは説明したとおりに機能しません。 +.RE +.PP +\-verbose +.RS 4 +追加の出力を表示します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineにoptionを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.PP +\-system +.RS 4 +アプリケーションをシステム・キャッシュのみから実行します。 +.RE +.SH "制御オプション" +.PP +\-viewer +.RS 4 +Javaコントロール・パネルでキャッシュ・ビューアを表示します。 +.RE +.PP +\-clearcache +.RS 4 +インストールされていないすべてのアプリケーションをキャッシュから削除します。 +.RE +.PP +\-userConfig \fIproperty\-name\fR +.RS 4 +指定されたデプロイメント・プロパティをクリアします。 +.RE +.PP +\-userConfig \fIproperty\-name property\-value\fR +.RS 4 +指定されたデプロイメント・プロパティを指定された値に設定します。 +.RE +.PP +\-uninstall +.RS 4 +キャッシュからすべてのアプリケーションを削除します。 +.RE +.PP +\-uninstall \fIjnlp\fR +.RS 4 +キャッシュからアプリケーションを削除します。 +.RE +.PP +\-print \fIimport\-options \fRjnlp +.RS 4 +キャッシュにアプリケーションをインポートします。 +.RE +.SH "インポート・オプション" +.PP +\-silent +.RS 4 +サイレント・モードでインポートします(ユーザー・インタフェースは表示されません)。 +.RE +.PP +\-system +.RS 4 +システム・キャッシュにアプリケーションをインポートします。 +.RE +.PP +\-codebase \fIurl\fR +.RS 4 +指定したコードベースからリソースを取得します。 +.RE +.PP +\-shortcut +.RS 4 +ユーザーがプロンプトを受け入れればショートカットをインストールします。このオプションは、 +\fB\-silent\fRオプションも使用しないと効果がありません。 +.RE +.PP +\-association +.RS 4 +ユーザーがプロンプトを受け入れればアソシエーションをインストールします。このオプションは、 +\fB\-silent\fRオプションも使用しないと効果がありません。 +.RE +.PP +\fB注意:\fR\fBjavaws \-shortcut \-uninstall\fR +.SH "ファイル" +.PP +ユーザーおよびシステム・キャッシュならびにdeployment\&.propertiesファイルの詳細は、デプロイメント構成ファイルおよびプロパティ +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jweb/jcp/properties\&.html)を参照してください +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java Web Start +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javaws/index\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jcmd.1 b/jdk-1.8.0.281/man/ja/man1/jcmd.1 new file mode 100755 index 0000000..6fea90d --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jcmd.1 @@ -0,0 +1,139 @@ +'\" t +.\" Copyright (c) 2012, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jcmd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jcmd" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jcmd \- 実行中のJava Virtual Machine (JVM)に診断コマンド・リクエストを送信します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR [\fB\-l\fR|\fB\-h\fR|\fB\-help\fR] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fBPerfCounter\&.print\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fB\-f\fR \fIfilename\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fIcommand\fR[ \fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.SH "説明" +.PP +\fBjcmd\fRユーティリティは、JVMに診断コマンド・リクエストを送信するために使用されます。これはJVMが稼働しているのと同じマシンで使用し、JVMの起動に使用したものと同じ有効ユーザーおよびグループ識別子を持っている必要があります。 +.PP +\fB注意:\fR +リモート・マシンから、または別の識別子で診断コマンドを起動するには、\fBcom\&.sun\&.management\&.DiagnosticCommandMBean\fRインタフェースを使用できます。\fBDiagnosticCommandMBean\fRインタフェースの詳細は、http://docs\&.oracle\&.com/javase/8/docs/jre/api/management/extension/com/sun/management/DiagnosticCommandMBean\&.htmlにあるAPIドキュメントを参照してください。 +.PP +\fBjcmd\fRを引数なしまたは\fB\- l\fRオプションを指定して実行した場合は、実行中のJavaプロセス識別子のリストが、メイン・クラスおよびプロセスの起動に使用されたコマンド行引数とともに出力されます。\fB\-h\fRまたは\fB\-help\fRオプションを指定して\fBjcmd\fRを実行すると、ツールのヘルプ・メッセージが出力されます。 +.PP +プロセス識別子(\fIpid\fR)またはメイン・クラス(\fImain\-class\fR)を最初の引数として指定した場合、\fBjcmd\fRは、識別子を指定した場合はJavaプロセスに、メイン・クラスの名前を指定した場合はすべてのJavaプロセスに診断コマンド・リクエストを送信します。プロセス識別子として\fB0\fRを指定して、すべての使用可能なJavaプロセスに診断コマンド・リクエストを送信することもできます。診断コマンド・リクエストとして、次のいずれかを使用します。 +.PP +Perfcounter\&.print +.RS 4 +指定したJavaプロセスで使用可能なパフォーマンス・カウンタが出力されます。パフォーマンス・カウンタのリストはJavaプロセスによって異なる場合があります。 +.RE +.PP +\-f \fIfilename\fR +.RS 4 +診断コマンドを読み取り、指定したJavaプロセスに送信するファイルの名前。\fB\-f\fRオプションでのみ使用します。ファイル内の各コマンドは、1行で記述する必要があります。番号記号(\fB#\fR)で始まる行は無視されます。すべての行が読み取られるか、\fBstop\fRキーワードを含む行が読み取られると、ファイルの処理が終了します。 +.RE +.PP +\fIcommand\fR [\fIarguments\fR] +.RS 4 +指定されたJavaプロセスに送信するコマンド。指定したプロセスで使用できる診断コマンドのリストは、このプロセスに対して\fBhelp\fRコマンドを送信すれば表示されます。各診断コマンドに独自の引数セットがあります。コマンドの説明、構文および使用可能な引数のリストを表示するには、\fBhelp\fRコマンドの引数としてコマンド名を使用します。 +.sp +\fB注意:\fR +引数にスペースが含まれている場合は、一重引用符または二重引用符(\fB\*(Aq\fRまたは\fB"\fR)で囲む必要があります。加えて、オペレーティング・システム・シェルが引用符を処理しないように、バックスラッシュ(\fB\e\fR)で一重引用符または二重引用符をエスケープする必要があります。または、これらの引数を一重引用符で囲んでから、二重引用符で囲むこともできます(または二重引用符で囲んでから、一重引用符で囲む)。 +.RE +.SH "オプション" +.PP +各オプションは互いに排他的です。 +.PP +\-f \fIfilename\fR +.RS 4 +指定されたファイルからコマンドを読み取ります。このオプションは、最初の引数としてプロセス識別子またはメイン・クラスを指定する場合にのみ使用できます。ファイル内の各コマンドは、1行で記述する必要があります。番号記号(\fB#\fR)で始まる行は無視されます。すべての行が読み取られるか、\fBstop\fRキーワードを含む行が読み取られると、ファイルの処理が終了します。 +.RE +.PP +\-h +.br +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-l +.RS 4 +実行中のJavaプロセス識別子のリストをメイン・クラスおよびコマンド行引数とともに出力します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jconsole.1 b/jdk-1.8.0.281/man/ja/man1/jconsole.1 new file mode 100755 index 0000000..e43a76a --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jconsole.1 @@ -0,0 +1,139 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jconsole +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaトラブルシューティング、プロファイリング、モニタリングおよび管理ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jconsole" "1" "2013å¹´11月21日" "JDK 8" "Javaトラブルシューティング、プロファイリング、モニタリン" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jconsole \- Javaアプリケーションを監視および管理するためのグラフィカル・コンソールを開始します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjconsole\fR [ \fIoptions\fR ] [ connection \&.\&.\&. ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +connection = \fIpid\fR | \fIhost\fR:\fIport\fR | \fIjmxURL\fR +.RS 4 +\fBpid\fR値はローカルのJava Virtual Machine (JVM)のプロセスIDです。JVMは\fBjconsole\fRコマンドを実行しているユーザーIDと同じユーザーIDで実行する必要があります。\fBhost:port\fR値はJVMが動作しているホスト・システムの名前と、JVMが開始したときにシステム・プロパティ\fBcom\&.sun\&.management\&.jmxremote\&.port\fRで指定したポート番号です。\fBjmxUrl\fR値は、JMXServiceURLで記述されている、接続されるJMXエージェントのアドレスです。 +.sp +\fBconnection\fRパラメータの詳細は、JMXテクノロジを使用したモニタリングおよび管理 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/agent\&.html)を参照してください +.sp +\fBJMXServiceURL\fRクラスの説明( +http://docs\&.oracle\&.com/javase/8/docs/api/javax/management/remote/JMXServiceURL\&.html)も参照してください +.RE +.SH "説明" +.PP +\fBjconsole\fRコマンドは、ローカル・マシンまたはリモート・マシン上のJavaアプリケーションと仮想マシンの監視と管理を行うグラフィカル・コンソール・ツールを起動します。 +.PP +Windows上では、\fBjconsole\fRコマンドはコンソール・ウィンドウと関連付けられていません。ただし、\fBjconsole\fRコマンドが失敗すると、エラー情報を示すダイアログ・ボックスが表示されます。 +.SH "オプション" +.PP +\-interval\fI=n\fR +.RS 4 +更新間隔を\fIn\fR秒に設定します(デフォルトは4秒)。 +.RE +.PP +\-notile +.RS 4 +最初にウィンドウをタイリングしません(複数接続の場合)。 +.RE +.PP +\-pluginpath \fIplugins\fR +.RS 4 +\fBJConsole\fRプラグインを検索するディレクトリまたはJARファイルのリストを指定します。\fIplugins\fRパスには\fBMETA\-INF/services/com\&.sun\&.tools\&.jconsole\&.JConsolePlugin\fRという名前のプロバイダ構成ファイルを含んでいる必要があり、これにはプラグインごとに1行が含まれています。その行は\fBcom\&.sun\&.tools\&.jconsole\&.JConsolePlugin\fRクラスを実装しているクラスの完全修飾クラス名を指定します。 +.RE +.PP +\-version +.RS 4 +リリース情報を表示して終了します。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjconsole\fRコマンドを実行したJVMに\fBflag\fRを渡します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JConsoleの使用 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/jconsole\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JMXテクノロジを使用したモニタリングおよび管理 + +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/agent\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBJMXServiceURL\fRクラスの説明( +http://docs\&.oracle\&.com/javase/8/docs/api/javax/management/remote/JMXServiceURL\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jdb.1 b/jdk-1.8.0.281/man/ja/man1/jdb.1 new file mode 100755 index 0000000..a989b83 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jdb.1 @@ -0,0 +1,370 @@ +'\" t +.\" Copyright (c) 1995, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jdb +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jdb" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jdb \- Javaプラットフォーム・プログラムのbugを検出および修正します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdb\fR [\fIoptions\fR] [\fIclassname\fR] [\fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclass\fRname +.RS 4 +デバッグするメイン・クラスの名前。 +.RE +.PP +\fIarguments\fR +.RS 4 +classの\fBmain()\fRメソッドに渡す引数。 +.RE +.SH "説明" +.PP +Javaデバッガ(JDB)は、Javaクラス用の簡単なコマンド行デバッガです。\fBjdb\fRコマンドとそのオプションはJDBを呼び出します。\fBjdb\fRコマンドは、JDBA (Java Platform Debugger Architecture)を視覚的に実行し、ローカルまたはリモートのJava Virtual Machine (JVM)の検査とデバッグを行うことができます。Java Platform Debugger Architecture (JDBA) +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jpda/index\&.html)を参照してください。 +.SS "JDBセッションの開始" +.PP +JDBセッションを開始するには様々な方法があります。最も頻繁に使用されるのは、デバッグするアプリケーションのメイン・クラスを使用して、JDBから新しいJVMを起動する方法です。コマンド行で、\fBjava\fRコマンドのかわりに\fBjdb\fRコマンドを入力します。たとえば、アプリケーションのメイン・クラスが\fBMyClass\fRの場合は、JDB環境でデバッグするときに次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdb MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この方法で起動すると、\fBjdb\fRコマンドは、指定されたパラメータを使用して2つ目のJVMを呼び出します。次に、指定されたクラスをロードして、クラスの最初の命令を実行する前にJVMを停止させます。 +.PP +\fBjdb\fRコマンドのもう1つの使用方法は、すでに実行中のJVMにjdbを接続することです。\fBjdb\fRコマンドが接続するVMを、その実行中に起動するための構文を次に示します。これは、インプロセス・デバッグ用ライブラリをロードし、接続の種類を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-agentlib:jdwp=transport=dt_socket,server=y,suspend=n MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコマンドを使用して、\fBjdb\fRコマンドをJVMに接続できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdb \-attach 8000\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この場合、\fBjdb\fRコマンドは新しいJVMを起動するかわりに既存のJVMに接続されるため、\fBjdb\fRコマンド行に\fBMyClass\fR引数は指定しません。 +.PP +デバッガをJVMに接続するには他にも様々な方法があり、すべて\fBjdb\fRコマンドでサポートされています。接続オプションについては、Java Platform Debugger Architectureのドキュメントを参照してください。 +.SS "基本jdbコマンド" +.PP +基本的な\fBjdb\fRコマンドの一覧を示します。JDBがサポートするコマンドはこれ以外にもあり、それらは\fB\-help\fRオプションを使用して表示できます。 +.PP +helpまたは? +.RS 4 +\fBhelp\fRまたは\fB?\fRコマンドは、認識されたコマンドのリストに簡潔な説明を付けて表示します。 +.RE +.PP +run +.RS 4 +JDBを起動してブレークポイントを設定したあとに、\fBrun\fRコマンドを使用して、デバッグするアプリケーションの実行を開始できます。\fBrun\fRコマンドは、既存のVMに接続している場合とは異なり、デバッグするアプリケーションが\fBjdb\fRから起動したときにのみ使用できます。 +.RE +.PP +cont +.RS 4 +ブレークポイント、例外、またはステップ実行の後で、デバッグするアプリケーションの実行を継続します。 +.RE +.PP +print +.RS 4 +Javaオブジェクトおよびプリミティブ値を表示します。プリミティブ型の変数またはフィールドの場合には、実際の値が出力されます。オブジェクトの場合には、短い説明が出力されます。オブジェクトの詳細を取得する方法を探すには、dumpコマンドを参照してください。 +.sp +\fB注意:\fR +ローカル変数を表示するには、含んでいるクラスが\fBjavac \-g\fRオプションを使用してコンパイルされている必要があります。 +.sp +\fBprint\fRコマンドは、次に示すような、メソッド呼出しを使用したものなど、多くの簡単なJava式をサポートします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBprint MyClass\&.myStaticField\fR +\fBprint myObj\&.myInstanceField\fR +\fBprint i + j + k (i, j, k are primities and either fields or local variables)\fR +\fBprint myObj\&.myMethod() (if myMethod returns a non\-null)\fR +\fBprint new java\&.lang\&.String("Hello")\&.length()\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +dump +.RS 4 +プリミティブ値の場合、\fBdump\fRコマンドは\fBprint\fRコマンドと同一です。オブジェクトの場合、\fBdump\fRコマンドでは、オブジェクト内に定義されている各フィールドの現在の値が出力されます。staticフィールドとinstanceフィールドが出力されます。\fBdump\fRコマンドでは、\fBprint\fRコマンドと同じ式がサポートされます。 +.RE +.PP +threads +.RS 4 +現在実行中のスレッドを一覧表示します。スレッドごとに、名前と現在の状態、および他のコマンドに使用できるインデックスが出力されます。この例では、スレッド・インデックスは4であり、スレッドは\fBjava\&.lang\&.Thread\fRのインスタンスで、スレッドの名前は\fBmain\fRであり、現在実行中です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB4\&. (java\&.lang\&.Thread)0x1 main running\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +thread +.RS 4 +現在のスレッドにするスレッドを選択します。多くの\fBjdb\fRコマンドは、現在のスレッドの設定に基づいて実行されます。スレッドは、threadsコマンドで説明したスレッド・インデックスとともに指定します。 +.RE +.PP +where +.RS 4 +引数を指定しないで\fBwhere\fRコマンドを実行すると、現在のスレッドのスタックがダンプされます。\fBwhere\fR +\fBall\fRコマンドは、現在のスレッド・グループにあるスレッドのスタックをすべてダンプします。\fBwhere\fR +\fBthreadindex\fRコマンドは、指定されたスレッドのスタックをダンプします。 +.sp +現在のスレッドが(ブレークポイントか\fBsuspend\fRコマンドによって)中断している場合は、ローカル変数とフィールドは\fBprint\fRコマンドと\fBdump\fRコマンドで表示できます。\fBup\fRコマンドと\fBdown\fRコマンドで、どのスタック・フレームを現在のスタック・フレームにするかを選ぶことができます。 +.RE +.SS "ブレークポイント" +.PP +ブレークポイントは、行番号またはメソッドの最初の命令でJDBに設定できます。次に例を示します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド\fBstop at MyClass:22\fRは、\fBMyClass\fRが含まれるソース・ファイルの22行目の最初の命令にブレークポイントを設定します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド\fBstop in java\&.lang\&.String\&.length\fRは、メソッド\fBjava\&.lang\&.String\&.length\fRの先頭にブレークポイントを設定します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド\fBstop in MyClass\&.<clinit>\fRは、\fB<clinit>\fRを使用して、\fBMyClass\fRの静的初期化コードを特定します。 +.RE +.PP +メソッドがオーバーロードされている場合には、メソッドの引数の型も指定して、ブレークポイントに対して適切なメソッドが選択されるようにする必要があります。たとえば、\fBMyClass\&.myMethod(int,java\&.lang\&.String)\fRまたは\fBMyClass\&.myMethod()\fRと指定します。 +.PP +\fBclear\fRコマンドは、\fBclear MyClass:45\fRのような構文を使用してブレークポイントを削除します。\fBclear\fRを使用するか、引数を指定しないで\fBstop\fRコマンドを使用すると、現在設定されているすべてのブレークポイントが表示されます。\fBcont\fRコマンドは実行を継続します。 +.SS "ステップ実行" +.PP +\fBstep\fRコマンドは、現在のスタック・フレームまたは呼び出されたメソッド内で、次の行を実行します。\fBnext\fRコマンドは、現在のスタック・フレームの次の行を実行します。 +.SS "例外" +.PP +スローしているスレッドの呼出しスタック上のどこにも\fBcatch\fR文がない場合に例外が発生すると、JVMは通常、例外トレースを出力して終了します。ただし、JDB環境で実行している場合は、違反のスロー時にJDBに制御が戻ります。次に、\fBjdb\fRコマンドを使用して例外の原因を診断します。 +.PP +たとえば、\fBcatch java\&.io\&.FileNotFoundException\fRまたは\fBcatch\fR +\fBmypackage\&.BigTroubleException\fRのように\fBcatch\fRコマンドを使用すると、デバッグされたアプリケーションは、他の例外がスローされたときに停止します。例外が特定のクラスまたはサブクラスのインスタンスの場合は、アプリケーションは例外がスローされた場所で停止します。 +.PP +\fBignore\fRコマンドを使用すると、以前の\fBcatch\fRコマンドの効果が無効になります。\fBignore\fRコマンドでは、デバッグされるJVMは特定の例外を無視せず、デバッガのみを無視します。 +.SH "オプション" +.PP +コマンド行で\fBjava\fRコマンドのかわりに\fBjdb\fRコマンドを使用する場合、\fBjdb\fRコマンドは、\fB\-D\fR、\fB\-classpath\fR、\fB\-X\fRなど、\fBjava\fRコマンドと同じ数のオプションを受け入れます。\fBjdb\fRコマンドは、その他に次のリストにあるオプションを受け入れます。 +.PP +デバッグを行うJVMにデバッガを接続するための代替機構を提供するために、その他のオプションがサポートされています。これらの接続の代替に関する詳細なドキュメントは、Java Platform Debugger Architecture (JPDA) +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jpda/index\&.html)を参照してください +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.PP +\-sourcepath \fIdir1:dir2: \&. \&. \&.\fR +.RS 4 +指定されたパスを使用して、ソース・ファイルを検索します。このオプションが指定されていない場合は、デフォルト・パスのドット(\&.)が使用されます。 +.RE +.PP +\-attach \fIaddress\fR +.RS 4 +デフォルトの接続機構を使用して、実行中のJVMにデバッガを接続します。 +.RE +.PP +\-listen \fIaddress\fR +.RS 4 +実行中のJVMが標準のコネクタを使用して指定されたアドレスに接続するのを待機します。 +.RE +.PP +\-launch +.RS 4 +デバッグするアプリケーションをJDBの起動後ただちに起動します。\fB\-launch\fRオプションにより、\fBrun\fRコマンドが必要なくなります。デバッグするアプリケーションは、起動後、初期アプリケーション・クラスがロードされる直前に停止します。その時点で、必要なブレークポイントを設定し、\fBcont\fRコマンドを使用して実行を継続できます。 +.RE +.PP +\-listconnectors +.RS 4 +このJVMで利用できるコネクタを一覧表示します。 +.RE +.PP +\-connect connector\-name:\fIname1=value1\fR +.RS 4 +一覧表示された引数の値と指定のコネクタを使用してターゲットJVMに接続します。 +.RE +.PP +\-dbgtrace [\fIflags\fR] +.RS 4 +\fBjdb\fRコマンドのデバッグの情報を出力します。 +.RE +.PP +\-tclient +.RS 4 +Java HotSpot VMクライアント内でアプリケーションを実行します。 +.RE +.PP +\-tserver +.RS 4 +Java HotSpot VMサーバー内でアプリケーションを実行します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +JVMに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "デバッグ対象のプロセスに転送されるオプション" +.PP +\-v \-verbose[:\fIclass\fR|gc|jni] +.RS 4 +冗長モードにします。 +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +システム・プロパティを設定します。 +.RE +.PP +\-classpath \fIdir\fR +.RS 4 +クラスを検索するための、コロンで区切って指定されたディレクトリのリスト。 +.RE +.PP +\-X\fIoption\fR +.RS 4 +非標準ターゲットJVMオプションです。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jdeps.1 b/jdk-1.8.0.281/man/ja/man1/jdeps.1 new file mode 100755 index 0000000..b290ae2 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jdeps.1 @@ -0,0 +1,375 @@ +'\" t +.\" Copyright (c) 2013, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jdeps +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jdeps" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jdeps \- Javaクラス依存性アナライザ。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdeps\fR [\fIoptions\fR] \fIclasses\fR \&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclasses\fR +.RS 4 +分析するクラスの名前。クラス・パスで検出できるクラスを、ファイル名、ディレクトリまたはJARファイルで指定できます。 +.RE +.SH "説明" +.PP +\fBjdeps\fRコマンドは、Javaクラス・ファイルのパッケージレベルまたはクラスレベルの依存性を示します。入力クラスには、\fB\&.class\fRファイルのパス名、ディレクトリ、JARファイル、またはすべてのクラス・ファイルを分析するための完全修飾クラス名を指定できます。オプションにより出力が決定します。デフォルトでは、\fBjdeps\fRはシステム出力に依存関係を出力します。DOT言語で依存関係を生成できます(\fB\-dotoutput\fRオプションを参照)。 +.SH "オプション" +.PP +\-dotoutput <\fIdir\fR> +.RS 4 +DOTファイル出力の宛先ディレクトリ。指定した場合、\fBjdeps\fRは<\fIarchive\-file\-name\fR>\&.dotという名前の分析済アーカイブごとに依存関係をリストする1つのdotファイルを生成し、アーカイブ間の依存関係をリストするsummary\&.dotという名前のサマリー・ファイルも生成します。 +.RE +.PP +\-s +.br +\-summary +.RS 4 +依存関係のサマリーのみを出力します。 +.RE +.PP +\-v +.br +\-verbose +.RS 4 +すべてのクラスレベルの依存関係を出力します。 +.RE +.PP +\-verbose:package +.RS 4 +同じアーカイブ内の依存関係を除き、パッケージレベルの依存関係を出力します。 +.RE +.PP +\-verbose:class +.RS 4 +同じアーカイブ内の依存関係を除き、クラスレベルの依存関係を出力します。 +.RE +.PP +\-cp <\fIpath\fR> +.br +\-classpath <\fIpath\fR> +.RS 4 +クラス・ファイルの検索場所を指定します。 +.sp +クラス・パスの設定 も参照してください。 +.RE +.PP +\-p <\fIpkg name\fR> +.br +\-package <\fIpkg name\fR> +.RS 4 +指定したパッケージの依存関係を検出します。異なるパッケージに対してこのオプションを複数回指定できます。\fB\-p\fRオプションと\fB\-e\fRオプションを同時に指定することはできません。 +.RE +.PP +\-e <\fIregex\fR> +.br +\-regex <\fIregex\fR> +.RS 4 +指定した正規表現パターンと一致するパッケージの依存関係を検出します。\fB\-p\fRオプションと\fB\-e\fRオプションを同時に指定することはできません。 +.RE +.PP +\-include <\fIregex\fR> +.RS 4 +分析をパターンに一致するクラスに制限します。このオプションは、分析するクラスのリストをフィルタします。依存関係にパターンを適用する\fB\-p\fRおよび\fB\-e\fRとともに使用できます。 +.RE +.PP +\-jdkinternals +.RS 4 +JDKの内部APIのクラスレベルの依存関係を検出します。デフォルトでは、\fB\-include\fRオプションを指定しないかぎり、\fB\-classpath\fRオプションおよび入力ファイルに指定されたすべてのクラスを分析します。このオプションは、\fB\-p\fRオプション、\fB\-e\fRオプションおよび\fB\-s\fRオプションとともに使用できません。 +.sp +\fB警告\fR: JDKの内部APIは、今後のリリースでアクセスできなくなる可能性があります。 +.RE +.PP +\-P +.br +\-profile +.RS 4 +パッケージを含むプロファイルまたはファイルを表示します。 +.RE +.PP +\-apionly +.RS 4 +フィールド・タイプ、メソッド・パラメータ・タイプ、戻りタイプ、チェックされた例外タイプを含むパブリック・クラスの\fBpublic\fRおよび\fBprotected\fRメンバーの署名からの依存関係など、分析をAPIに制限します。 +.RE +.PP +\-R +.br +\-recursive +.RS 4 +すべての依存関係を再帰的に走査します。 +.RE +.PP +\-version +.RS 4 +バージョン情報を出力します。 +.RE +.PP +\-h +.br +\-? +.br +\-help +.RS 4 +\fBjdeps\fRに関するヘルプ・メッセージを出力します。 +.RE +.SH "例" +.PP +Notepad\&.jarの依存関係の分析。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps demo/jfc/Notepad/Notepad\&.jar\fR +\fB \fR +\fBdemo/jfc/Notepad/Notepad\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB <unnamed> (Notepad\&.jar)\fR +\fB \-> java\&.awt \fR +\fB \-> java\&.awt\&.event \fR +\fB \-> java\&.beans \fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.net \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.logging \fR +\fB \-> javax\&.swing \fR +\fB \-> javax\&.swing\&.border \fR +\fB \-> javax\&.swing\&.event \fR +\fB \-> javax\&.swing\&.text \fR +\fB \-> javax\&.swing\&.tree \fR +\fB \-> javax\&.swing\&.undo \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\-Pまたは\-profileオプションを使用して、メモ帳が依存するプロファイルを表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-profile demo/jfc/Notepad/Notepad\&.jar \fR +\fBdemo/jfc/Notepad/Notepad\&.jar \-> /usr/java/jre/lib/rt\&.jar (Full JRE)\fR +\fB <unnamed> (Notepad\&.jar)\fR +\fB \-> java\&.awt Full JRE\fR +\fB \-> java\&.awt\&.event Full JRE\fR +\fB \-> java\&.beans Full JRE\fR +\fB \-> java\&.io compact1\fR +\fB \-> java\&.lang compact1\fR +\fB \-> java\&.net compact1\fR +\fB \-> java\&.util compact1\fR +\fB \-> java\&.util\&.logging compact1\fR +\fB \-> javax\&.swing Full JRE\fR +\fB \-> javax\&.swing\&.border Full JRE\fR +\fB \-> javax\&.swing\&.event Full JRE\fR +\fB \-> javax\&.swing\&.text Full JRE\fR +\fB \-> javax\&.swing\&.tree Full JRE\fR +\fB \-> javax\&.swing\&.undo Full JRE\fR + +.fi +.if n \{\ +.RE +.\} +.PP +tools\&.jarファイル内の\fBcom\&.sun\&.tools\&.jdeps\&.Main\fRクラスなど、特定のクラスパス内の特定のクラスの直接依存関係の分析。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fR +\fBlib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB com\&.sun\&.tools\&.jdeps (tools\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB\-verbose:class\fRオプションを使用して、クラスレベル依存関係を検索するか\fB\-v\fRまたは\fB\-verbose\fRオプションを使用して同じJARファイルからの依存関係を含めます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-verbose:class \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fR +\fB \fR +\fBlib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB com\&.sun\&.tools\&.jdeps\&.Main (tools\&.jar)\fR +\fB \-> java\&.io\&.PrintWriter \fR +\fB \-> java\&.lang\&.Exception \fR +\fB \-> java\&.lang\&.Object \fR +\fB \-> java\&.lang\&.String \fR +\fB \-> java\&.lang\&.System \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB\-R\fRまたは\fB\-recursive\fRオプションを使用して、\fBcom\&.sun\&.tools\&.jdeps\&.Main\fRクラスの推移的な依存関係を分析します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-R \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fR +\fBlib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB com\&.sun\&.tools\&.classfile (tools\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.lang\&.reflect \fR +\fB \-> java\&.nio\&.charset \fR +\fB \-> java\&.nio\&.file \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.regex \fR +\fB com\&.sun\&.tools\&.jdeps (tools\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.nio\&.file \fR +\fB \-> java\&.nio\&.file\&.attribute \fR +\fB \-> java\&.text \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.jar \fR +\fB \-> java\&.util\&.regex \fR +\fB \-> java\&.util\&.zip \fR +\fB/usr/java/jre/lib/jce\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB javax\&.crypto (jce\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.lang\&.reflect \fR +\fB \-> java\&.net \fR +\fB \-> java\&.nio \fR +\fB \-> java\&.security \fR +\fB \-> java\&.security\&.cert \fR +\fB \-> java\&.security\&.spec \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.concurrent \fR +\fB \-> java\&.util\&.jar \fR +\fB \-> java\&.util\&.regex \fR +\fB \-> java\&.util\&.zip \fR +\fB \-> javax\&.security\&.auth \fR +\fB \-> sun\&.security\&.jca JDK internal API (rt\&.jar)\fR +\fB \-> sun\&.security\&.util JDK internal API (rt\&.jar)\fR +\fB javax\&.crypto\&.spec (jce\&.jar)\fR +\fB \-> java\&.lang \fR +\fB \-> java\&.security\&.spec \fR +\fB \-> java\&.util \fR +\fB/usr/java/jre/lib/rt\&.jar \-> /usr/java/jre/lib/jce\&.jar\fR +\fB java\&.security (rt\&.jar)\fR +\fB \-> javax\&.crypto\fR + +.fi +.if n \{\ +.RE +.\} +.PP +メモ帳デモの依存関係のdotファイルを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-dotoutput dot demo/jfc/Notepad/Notepad\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjdeps\fRは、\fB\-dotoutput\fRオプションで指定されたdotディレクトリに<\fIfilename\fR>\&.dotという名前のdotファイルを特定のJARファイルごとに作成し、JARファイル間の依存関係をリストするsummary\&.dotという名前のサマリー・ファイルも作成します +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ cat dot/Notepad\&.jar\&.dot \fR +\fBdigraph "Notepad\&.jar" {\fR +\fB // Path: demo/jfc/Notepad/Notepad\&.jar\fR +\fB "<unnamed>" \-> "java\&.awt";\fR +\fB "<unnamed>" \-> "java\&.awt\&.event";\fR +\fB "<unnamed>" \-> "java\&.beans";\fR +\fB "<unnamed>" \-> "java\&.io";\fR +\fB "<unnamed>" \-> "java\&.lang";\fR +\fB "<unnamed>" \-> "java\&.net";\fR +\fB "<unnamed>" \-> "java\&.util";\fR +\fB "<unnamed>" \-> "java\&.util\&.logging";\fR +\fB "<unnamed>" \-> "javax\&.swing";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.border";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.event";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.text";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.tree";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.undo";\fR +\fB}\fR +\fB \fR +\fB$ cat dot/summary\&.dot\fR +\fBdigraph "summary" {\fR +\fB "Notepad\&.jar" \-> "rt\&.jar";\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jhat.1 b/jdk-1.8.0.281/man/ja/man1/jhat.1 new file mode 100755 index 0000000..114fd33 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jhat.1 @@ -0,0 +1,197 @@ +'\" t +.\" Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jhat +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jhat" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jhat \- Javaヒープを分析します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjhat\fR [ \fIoptions\fR ] \fIheap\-dump\-file\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIheap\-dump\-file\fR +.RS 4 +ブラウズ対象となるJavaバイナリ・ヒープ・ダンプ・ファイル。複数のヒープ・ダンプを含むダンプ・ファイルの場合、\fBmyfile\&.hprof#3\fRのようにファイル名の後に\fB#<number>\fRを付加することで、ファイル内の特定のダンプを指定できます。 +.RE +.SH "説明" +.PP +\fBjhat\fRコマンドはJavaヒープ・ダンプ・ファイルを解析し、Webサーバーを開始します。\fBjhat\fRコマンドを使用して、お気に入りのブラウザでヒープ・ダンプを参照できます。\fBjhat\fRコマンドは、既知のクラス\fBMyClass\fRのすべてのインスタンスを表示するなどの事前設計済の問合せやObject Query Language (OQL)をサポートします。ヒープ・ダンプの問合せを除き、OQLはSQLに似ています。OQLのヘルプには、\fBjhat\fRコマンドによって表示されるOQLヘルプ・ページからアクセスできます。デフォルト・ポートを使用する場合、OQLのヘルプはhttp://localhost:7000/oqlhelp/で利用可能です。 +.PP +Javaのヒープ・ダンプを生成するには、次のいくつかの方法があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjmap \-dump\fRオプションを使用して実行時にヒープ・ダンプを取得します。jmap(1)を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjconsole\fRオプションを使用して\fBHotSpotDiagnosticMXBean\fR経由で実行時にヒープ・ダンプを取得します。jconsole(1)および\fBHotSpotDiagnosticMXBean\fRのインタフェースの説明( +http://docs\&.oracle\&.com/javase/8/docs/jre/api/management/extension/com/sun/management/HotSpotDiagnosticMXBean\&.html)を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ヒープ・ダンプは、\fB\-XX:+HeapDumpOnOutOfMemoryError\fR +Java Virtual Machine (JVM)オプションを指定することで、\fBOutOfMemoryError\fRがスローされたときに生成されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBhprof\fRコマンドを使用します。HPROF: Heap/CPUプロファイリング・ツール +(http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/hprof\&.html)を参照してください +.RE +.SH "オプション" +.PP +\-stack false|true +.RS 4 +オブジェクト割当呼出しスタックの追跡を無効にします。ヒープ・ダンプ内で割当サイト情報が使用できない場合、このフラグを\fBfalse\fRに設定する必要があります。デフォルトは\fBtrue\fRです。 +.RE +.PP +\-refs false|true +.RS 4 +オブジェクトへの参照の追跡を無効にします。デフォルトは\fBtrue\fRです。デフォルトでは、ヒープ内のすべてのオブジェクトについて、バックポインタ(指定されたオブジェクトをポイントしているオブジェクト。参照者または受信参照とも呼ばれる)が計算されます。 +.RE +.PP +\-port \fIport\-number\fR +.RS 4 +\fBjhat\fRのHTTPサーバーのポートを設定します。デフォルトは7000です。 +.RE +.PP +\-exclude \fIexclude\-file\fR +.RS 4 +到達可能なオブジェクトの問合せから除外する必要があるデータ・メンバーの一覧を含むファイルを指定します。たとえば、このファイルに\fBjava\&.lang\&.String\&.value\fRが含まれていた場合、特定のオブジェクト\fBo\fRから到達可能なオブジェクトのリストを計算する際に、\fBjava\&.lang\&.String\&.value\fRフィールドに関連する参照パスが考慮されなくなります。 +.RE +.PP +\-baseline \fIexclude\-file\fR +.RS 4 +ベースラインとなるヒープ・ダンプを指定します。両方のヒープ・ダンプ内で同じオブジェクトIDを持つオブジェクトは新規ではないとしてマークされます。他のオブジェクトは新規としてマークされます。これは、異なる2つのヒープ・ダンプを比較する際に役立ちます。 +.RE +.PP +\-debug \fIint\fR +.RS 4 +このツールのデバッグ・レベルを設定します。レベル0はデバッグ出力がないことを意味します。より大きな値を設定すると、より冗長なモードになります。 +.RE +.PP +\-version +.RS 4 +リリース番号をレポートして終了します +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjhat\fRコマンドを実行しているJava Virtual Machineに\fBflag\fRを渡します。たとえば、512Mバイトの最大ヒープ・サイズを使用するには、\fB\-J\-Xmx512m\fRとします。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jmap(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jconsole(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +HPROF: Heap/CPUプロファイリング・ツール +(http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/hprof\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jinfo.1 b/jdk-1.8.0.281/man/ja/man1/jinfo.1 new file mode 100755 index 0000000..97af9e2 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jinfo.1 @@ -0,0 +1,169 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jinfo +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jinfo" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jinfo \- 構成情報を生成します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjinfo\fR [ \fIoption\fR ] \fIpid\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjinfo\fR [ \fIoption \fR] \fIexecutable core\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjinfo\fR [ \fIoption \fR] \fI[ servier\-id ] remote\-hostname\-or\-IP\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIオプション\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIpid\fR +.RS 4 +構成情報が出力されるプロセスID。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +構成情報が出力されるコア・ファイル。 +.RE +.PP +\fIremote\-hostname\-or\-IP\fR +.RS 4 +リモート・デバッグ・サーバーの\fBホスト名\fRまたは\fBIP\fRアドレス。jsadebugd(1)を参照してください。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のリモート・ホストで実行している場合の、オプション固有のID。 +.RE +.SH "説明" +.PP +\fBjinfo\fRコマンドは、指定されたJavaプロセスやコア・ファイルまたはリモート・デバッグ・サーバーのJava構成情報を出力します。構成情報には、Javaシステム・プロパティとJava仮想マシン(JVM)のコマンドライン・フラグが含まれています。指定されたプロセスが64ビットJVM上で実行されている場合、\fB\-J\-d64\fRオプションを指定する必要がある場合があります。次に例を示します。\fBjinfo\fR +\fB\-J\-d64 \-sysprops pid\fR。 +.PP +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。\fBdbgeng\&.dll\fRが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。\fBPATH\fR環境変数には、ターゲット・プロセスによって使用されるjvm\&.dllの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。たとえば、\fBset PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fRです。 +.SH "オプション" +.PP +no\-option +.RS 4 +コマンド行フラグを、システム・プロパティ名と値のペアとともに出力します。 +.RE +.PP +\-flag \fIname\fR +.RS 4 +指定されたコマンドライン・フラグの名前と値を出力します。 +.RE +.PP +\-flag \fI[+|\-]name\fR +.RS 4 +指定されたブール型のコマンドライン・フラグを有効または無効にします。 +.RE +.PP +\-flag \fIname=value\fR +.RS 4 +指定されたコマンドライン・フラグを指定された値に設定します。 +.RE +.PP +\-flags +.RS 4 +JVMに渡されるコマンドライン・フラグを出力します。 +.RE +.PP +\-sysprops +.RS 4 +Javaシステム・プロパティを名前と値のペアとして出力します。 +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jjs.1 b/jdk-1.8.0.281/man/ja/man1/jjs.1 new file mode 100755 index 0000000..b461c49 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jjs.1 @@ -0,0 +1,415 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jjs +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jjs" "1" "2015å¹´3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jjs \- Nashornエンジンを呼び出します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\fBjjs\fR\fR\fB [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIscript\-files\fR\fR\fB] [\-\- \fR\fB\fIarguments\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +空白文字で区切られた、\fBjjs\fRコマンドの1つ以上のオプション。詳細は、オプションを参照してください。 +.RE +.PP +\fIscript\-files\fR +.RS 4 +空白文字で区切られた、Nashornを使用して解釈する1つ以上のスクリプト・ファイル。ファイルが指定されない場合は、対話型シェルが起動されます。 +.RE +.PP +\fIarguments\fR +.RS 4 +二重ハイフン・マーカー(\fB\-\-\fR)の後のすべての値が、引数としてスクリプトまたは対話型シェルに渡されます。これらの値には\fBarguments\fRプロパティを使用してアクセスできます(Example 3を参照してください)。 +.RE +.SH "説明" +.PP +\fBjjs\fRコマンド行ツールを使用してNashornエンジンを呼び出します。これを使用して、1つまたは複数のスクリプト・ファイルを解釈したり、対話型シェルを実行することができます。 +.SH "オプション" +.PP +\fBjjs\fRコマンドのオプションはスクリプトがNashornによって解釈される条件を制御します。 +.PP +\-ccs=\fIsize\fR +.br +\-\-class\-cache\-size=\fIsize\fR +.RS 4 +クラス・キャッシュ・サイズをバイト単位で設定します。キロバイト(KB)を示すために\fBk\fRまたは\fBK\fRの文字を追加し、メガバイト(MB)を示すために\fBm\fRまたは\fBM\fRの文字を追加し、ギガバイト(GB)を示すために\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、クラス・キャッシュ・サイズは50バイトに設定されます。次の例は、1024バイト(1 KB)に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-css=100\fR +\fB\-css=1k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-co +.br +\-\-compile\-only +.RS 4 +スクリプトを実行せずにコンパイルします。 +.RE +.PP +\-cp \fIpath\fR +.br +\-classpath \fIpath\fR +.RS 4 +サポートするクラスへのパスを指定します。複数のパスを設定するには、このオプションを繰り返すか、または各パスをコロン(:)で区切ります。 +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +プロパティ名に値を割り当てることで、スクリプトに渡すシステム・プロパティを設定します。次の例で、対話型モードでNashornを呼び出して、\fBmyValue\fRを\fBmyKey\fRという名前のプロパティに割り当てる方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-DmyKey=myValue\fR\fR +\fBjjs> \fR\fB\fBjava\&.lang\&.System\&.getProperty("myKey")\fR\fR +\fBmyValue\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを繰り返し使用すると、複数のプロパティを設定できます。 +.RE +.PP +\-d=\fIpath\fR +.br +\-\-dump\-debug\-dir=\fIpath\fR +.RS 4 +クラス・ファイルをダンプするディレクトリへのパスを指定します。 +.RE +.PP +\-\-debug\-lines +.RS 4 +クラス・ファイル内の行番号表を生成します。デフォルトでは、このオプションは有効になっています。無効にするには\fB\-\-debug\-lines=false\fRを指定します。 +.RE +.PP +\-\-debug\-locals +.RS 4 +クラス・ファイル内のローカル変数を生成します。 +.RE +.PP +\-doe +.br +\-\-dump\-on\-error +.RS 4 +エラーが発生したときに、フル・スタック・トレースを提供します。デフォルトでは、簡単なエラー・メッセージのみが出力されます。 +.RE +.PP +\-\-early\-lvalue\-error +.RS 4 +無効な左辺値式が早期エラーとして(つまり、コードが解析されるときに)報告されます。デフォルトでは、このオプションは有効になっています。無効にするには\fB\-\-early\-lvalue\-error=false\fRを指定します。無効な場合、無効な左辺値式はコードが実行されるまで報告されません。 +.RE +.PP +\-\-empty\-statements +.RS 4 +空の文をJavaの抽象構文ツリーに保存します。 +.RE +.PP +\-fv +.br +\-\-fullversion +.RS 4 +完全なNashornバージョン文字列を出力します。 +.RE +.PP +\-\-function\-statement\-error +.RS 4 +関数の宣言が文として使用されるとエラー・メッセージが出力されます。 +.RE +.PP +\-\-function\-statement\-warning +.RS 4 +関数の宣言が文として使用されると警告メッセージが出力されます。 +.RE +.PP +\-fx +.RS 4 +スクリプトをJavaFXアプリケーションとして起動します。 +.RE +.PP +\-h +.br +\-help +.RS 4 +オプションのリストとその説明を出力します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定した\fBjava\fR起動オプションをJVMに渡します。次の例で、対話型モードでNashornを呼び出して、JVMによって使用される最大メモリーを4 GBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-J\-Xmx4g\fR\fR +\fBjjs> \fR\fB\fBjava\&.lang\&.Runtime\&.getRuntime()\&.maxMemory()\fR\fR +\fB3817799680\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを繰り返し使用すると、複数の\fBjava\fRコマンド・オプションを渡すことができます。 +.RE +.PP +\-\-language=[es5] +.RS 4 +ECMAScript言語バージョンを指定します。デフォルトのバージョンはES5です。 +.RE +.PP +\-\-lazy\-compilation +.RS 4 +レイジー・コード生成戦略(つまり、スクリプト全体が一度にコンパイルされない)を有効にします。このオプションは試験的なものです。 +.RE +.PP +\-\-loader\-per\-compile +.RS 4 +コンパイルごとに新しいクラス・ローダーを作成します。デフォルトでは、このオプションは有効になっています。無効にするには\fB\-\-loader\-per\-compile=false\fRを指定します。 +.RE +.PP +\-\-log=\fIsubsystem\fR:\fIlevel\fR +.RS 4 +指定されたサブシステムに対して、特定のレベルでロギングを実行します。カンマで区切って複数のサブシステムのロギング・レベルを指定できます。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-\-log=fields:finest,codegen:info\fR +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-\-optimistic\-types=[true|false] +.RS 4 +再コンパイルの最適化を解除してオプティミスティック・タイプ仮定を有効または無効にします。オプティミスティック・タイプを使用した実行によって最終的な速度が向上しますが、ウォームアップ時間が増える場合があります。 +.RE +.PP +\-\-package=\fIname\fR +.RS 4 +生成されたクラス・ファイルを追加するパッケージを指定します。 +.RE +.PP +\-\-parse\-only +.RS 4 +コンパイルせずにコードを解析します。 +.RE +.PP +\-\-print\-ast +.RS 4 +抽象構文ツリーを出力します。 +.RE +.PP +\-\-print\-code +.RS 4 +バイトコードを出力します。 +.RE +.PP +\-\-print\-lower\-ast +.RS 4 +掘り下げた抽象構文ツリーを出力します。 +.RE +.PP +\-\-print\-lower\-parse +.RS 4 +掘り下げた解析ツリーを出力します。 +.RE +.PP +\-\-print\-no\-newline +.RS 4 +その他の\fB\-\-print*\fRオプションで強制的に1行で出力します。 +.RE +.PP +\-\-print\-parse +.RS 4 +解析ツリーを出力します。 +.RE +.PP +\-\-print\-symbols +.RS 4 +記号表を出力します。 +.RE +.PP +\-pcs +.br +\-\-profile\-callsites +.RS 4 +呼び出しサイトのプロファイル・データをダンプします。 +.RE +.PP +\-scripting +.RS 4 +シェルのスクリプト機能を有効にします。 +.RE +.PP +\-\-stderr=\fIfilename\fR|\fIstream\fR|\fItty\fR +.RS 4 +標準エラー・ストリームを指定したファイル、ストリーム(たとえば\fBstdout\fR)に、またはテキスト端末にリダイレクトします。 +.RE +.PP +\-\-stdout=\fIfilename\fR|\fIstream\fR|\fItty\fR +.RS 4 +標準出力ストリームを指定したファイル、ストリーム(たとえば\fBstderr\fR)に、またはテキスト端末にリダイレクトします。 +.RE +.PP +\-strict +.RS 4 +標準(ECMAScript Edition 5\&.1)への準拠を強化するstrictモードを有効にし、これにより共通のコーディング・エラーを簡単に検出できるようになります。 +.RE +.PP +\-t=\fIzone\fR +.br +\-timezone=\fIzone\fR +.RS 4 +スクリプトの実行に対し指定したタイムゾーンを設定します。OSで設定されたタイムゾーンをオーバーライドし、\fBDate\fRオブジェクトで使用されます。 +.RE +.PP +\-tcs=\fIparameter\fR +.br +\-\-trace\-callsites=\fIparameter\fR +.RS 4 +呼出しサイトのトレースのモードを有効にします。使用可能なパラメータは、次のとおりです。 +.PP +miss +.RS 4 +呼出しサイトのミスをトレースします。 +.RE +.PP +enterexit +.RS 4 +呼出しサイトへの出入りをトレースします。 +.RE +.PP +objects +.RS 4 +オブジェクトのプロパティを出力します。 +.RE +.RE +.PP +\-\-verify\-code +.RS 4 +バイトコードを実行する前に検証します。 +.RE +.PP +\-v +.br +\-version +.RS 4 +Nashornバージョン文字列を出力します。 +.RE +.PP +\-xhelp +.RS 4 +コマンドライン・オプションの拡張ヘルプを出力します。 +.RE +.SH "例" +.PP +\fB例 1 \fRNashornを使用したスクリプトの実行 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjjs script\&.js\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fR対話型モードでのNashornの実行 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs\fR\fR +\fBjjs> \fR\fB\fBprintln("Hello, World!")\fR\fR +\fBHello, World!\fR +\fBjjs> \fR\fB\fBquit()\fR\fR +\fB>>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRNashornへの引数の渡し +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-\- a b c\fR\fR +\fBjjs> \fR\fB\fBarguments\&.join(", ")\fR\fR +\fBa, b, c\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "関連項目" +.PP +\fBjrunscript\fR +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jmap.1 b/jdk-1.8.0.281/man/ja/man1/jmap.1 new file mode 100755 index 0000000..4d558e6 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jmap.1 @@ -0,0 +1,192 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jmap +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jmap" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jmap \- プロセスやコア・ファイルまたはリモート・デバッグ・サーバーの、共用オブジェクト・メモリー・マップまたはヒープ・メモリーの詳細を出力します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjmap\fR [ \fIoptions\fR ] \fIpid\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjmap\fR [ \fIoptions\fR ] \fIexecutable\fR \fIcore\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjmap\fR [ \fIoptions\fR ] [ \fIpid\fR ] \fIserver\-id\fR@ ] \fIremote\-hostname\-or\-IP\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIpid\fR +.RS 4 +出力するメモリー・マップのプロセスID。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +出力するメモリー・マップのコア・ファイル。 +.RE +.PP +\fIremote\-hostname\-or\-IP\fR +.RS 4 +リモート・デバッグ・サーバーの\fBホスト名\fRまたは\fBIP\fRアドレス。jsadebugd(1)を参照してください。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のリモート・ホストで実行している場合の、オプション固有のID。 +.RE +.SH "説明" +.PP +\fBjmap\fRコマンドは、指定されたプロセスやコア・ファイルまたはリモート・デバッグ・サーバーの、共用オブジェクト・メモリー・マップまたはヒープ・メモリーの詳細を出力します。指定されたプロセスが64ビットJava Virtual Machine (JVM)上で実行されている場合、\fB\-J\-d64\fRオプションを指定する必要がある場合があります。次に例を示します。\fBjmap\fR +\fB\-J\-d64 \-heap pid\fR。 +.PP +\fB注意:\fR +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。\fBdbgeng\&.dll\fRファイルが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。\fBPATH\fR環境変数には、ターゲット・プロセスによって使用される\fBjvm\&.dll\fRの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。次に例を示します。\fBset PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR。 +.SH "オプション" +.PP +<no option> +.RS 4 +オプションを使用しない場合、\fBjmap\fRコマンドは共用オブジェクト・マッピングを出力します。ターゲットJVMにロードされた共用オブジェクトごとに、開始アドレス、マッピングのサイズおよび共用オブジェクト・ファイルのフルパスが出力されます。この動作は、Oracle Solaris +\fBpmap\fRユーティリティと類似しています。 +.RE +.PP +\-dump:[live,] format=b, file=\fIfilename\fR +.RS 4 +Javaヒープを\fBhprof\fRバイナリ形式で\fBfilename\fRにダンプします。\fBlive\fRサブオプションはオプションですが、指定した場合、ヒープ内のアクティブなオブジェクトのみがダンプされます。ヒープ・ダンプを参照するには、jhat(1)コマンドを使用して生成されたファイルを読み取ります。 +.RE +.PP +\-finalizerinfo +.RS 4 +ファイナライズを待っているオブジェクトに関する情報を出力します。 +.RE +.PP +\-heap +.RS 4 +使用されているガベージ・コレクションのヒープ・サマリー、ヘッダー構成、および世代関連のヒープ使用状況を出力します。さらに、internされた文字列の数とサイズも出力されます。 +.RE +.PP +\-histo[:live] +.RS 4 +ヒープのヒストグラムを出力します。Javaクラスごとに、オブジェクトの数、バイト単位でのメモリー・サイズ、および完全修飾クラス名が出力されます。JVMの内部クラス名はアスタリスク(*)の接頭辞を付けて出力されます。\fBlive\fRサブオプションが指定された場合、アクティブなオブジェクトのみがカウントされます。 +.RE +.PP +\-clstats +.RS 4 +Javaヒープの、クラス・ローダー関連の統計データを出力します。クラス・ローダーごとに、その名前、状態、アドレス、親クラス・ローダー、およびクラス・ローダーがロードしたクラスの数とサイズが出力されます。 +.RE +.PP +\-F +.RS 4 +強制します。PIDが応答しないときに、このオプションを\fBjmap \-dump\fRまたは\fBjmap \-histo\fRオプションとともに使用します。このモードでは、\fBlive\fRサブオプションはサポートされません。 +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjmap\fRコマンドを実行しているJava Virtual Machineに\fBflag\fRを渡します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jhat(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jps.1 b/jdk-1.8.0.281/man/ja/man1/jps.1 new file mode 100755 index 0000000..76a96ec --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jps.1 @@ -0,0 +1,251 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jps +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: モニタリング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jps" "1" "2013å¹´11月21日" "JDK 8" "モニタリング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jps \- ターゲット・システム上で計測されたJava仮想マシン(JVM)を一覧表示します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps\fR [ \fIoptions\fR ] [ \fIhostid\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIhostid\fR +.RS 4 +プロセス・レポートを生成するホストの識別子。\fBhostid\fRには、通信プロトコル、ポート番号、実装に固有な他のデータを指定したオプション・コンポーネントを含めることができます。ホスト識別子を参照してください。 +.RE +.SH "説明" +.PP +\fBjps\fRコマンドは、ターゲット・システム上で計測されたJava HotSpot VMを一覧表示します。このコマンドで表示できるレポート情報は、アクセス権を持ったJVMに関するものに限定されます。 +.PP +\fBhostid\fRを指定せずに\fBjps\fRコマンドを実行した場合、ローカル・ホストで計測されたJVMが検索されます。\fBhostid\fRを指定して起動した場合、指定されたプロトコルとポートを使用して、指定されたホスト上のJVMを検索します。\fBjstatd\fRプロセスがターゲット・ホスト上で実行されていると想定されます。 +.PP +\fBjps\fRコマンドは、ターゲット・システムで計測された各JVMについて、ローカルVM識別子、つまり\fBlvmid\fRをレポートします。\fBlvmid\fRは、一般的にはJVMプロセスに対するオペレーティング・システムのプロセス識別子ですが、必ずしもそうであるとは限りません。オプションを指定しない場合、\fBjps\fRによって、各Javaアプリケーションの\fBlvmid\fRが一覧表示され、それぞれにアプリケーションのクラス名またはJARファイル名が簡単な形式で示されます。この簡単な形式のクラス名とJARファイル名では、クラスのパッケージ情報またはJARファイル・パス情報が省略されています。 +.PP +\fBjps\fRコマンドは、Java起動ツールを使用してmainメソッドに渡されるクラス名と引数を検索します。独自の起動ツールを使用してターゲットJVMを起動した場合は、\fBmain\fRメソッドに渡されるクラス名またはJARファイル名と引数は利用できません。この場合、\fBjps\fRコマンドは、\fBmain\fRメソッドに渡されるクラス名またはJARファイル名と引数に対して、文字列\fBUnknown\fRを出力します。 +.PP +\fBjps\fRコマンドで生成されるJVMのリストは、このコマンドを実行するプリンシパルに与えられたアクセス権に基づき、制限される場合があります。このコマンドは、オペレーティング・システム独自のアクセス制御機構による決定に基づいて、プリンシパルにアクセス権が与えられているJVMのみを一覧表示します。 +.SH "オプション" +.PP +\fBjps\fRコマンドでは、コマンドの出力を変更するオプションが多数サポートされています。将来、これらのオプションは、変更または廃止される可能性があります。 +.PP +\-q +.RS 4 +クラス名、JARファイル名、および\fBmain\fRメソッドに渡された引数の出力を抑制し、ローカルVM識別子の一覧のみを生成します。 +.RE +.PP +\-m +.RS 4 +\fBmain\fRメソッドに渡される引数を出力します。この出力は、組み込まれているJVMに対して\fBnull\fRになることもあります。 +.RE +.PP +\-l +.RS 4 +アプリケーションの\fBmain\fRクラスのフル・パッケージ名、またはアプリケーションのJARファイルへのフルパス名を出力します。 +.RE +.PP +\-v +.RS 4 +JVMに渡される引数を表示します。 +.RE +.PP +\-V +.RS 4 +クラス名、JARファイル名、およびmaiメソッドに渡された引数の出力を抑制し、ローカルVM識別子の一覧のみを生成します。 +.RE +.PP +\-J\fBoption\fR +.RS 4 +JVMに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されている\fBオプション\fRを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "ホスト識別子" +.PP +ホスト識別子、つまり\fBhostid\fRは、ターゲット・システムを示す文字列です。\fBhostid\fR文字列の構文は、URIの構文に対応しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][[//]hostname][:port][/servername]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fIprotocol\fR +.RS 4 +通信プロトコルです。\fBprotocol\fRが省略され、\fBhostname\fRが指定されていない場合、デフォルトのプロトコルが、プラットフォーム固有の最適化されたローカル・プロトコルになります。プロトコルが省略され、ホスト名が指定されている場合は、デフォルト・プロトコルは\fBrmi\fRになります。 +.RE +.PP +hostname +.RS 4 +ターゲット・ホストを示すホスト名またはIPアドレスです。\fBhostname\fRパラメータが省略されている場合は、ターゲット・ホストはローカル・ホストになります。 +.RE +.PP +port +.RS 4 +リモート・サーバーと通信するためのデフォルト・ポートです。\fBhostname\fRパラメータが省略されているか、\fBprotocol\fRパラメータが、最適化されたローカル・プロトコルを指定している場合、\fBport\fRパラメータは無視されます。それ以外の場合、\fBport\fRパラメータの扱いは、実装によって異なります。デフォルトの +\fBrmi\fRプロトコルの場合、\fBport\fRパラメータは、リモート・ホスト上のrmiregistryのポート番号を示します。\fBport\fRパラメータが省略されているか、\fBprotocol\fRパラメータが\fBrmi\fRを示している場合、デフォルトのrmiregistryポート(1099)が使用されます。 +.RE +.PP +servername +.RS 4 +このパラメータの扱いは、実装によって異なります。最適化されたローカル・プロトコルの場合、このフィールドは無視されます。\fBrmi\fRプロトコルの場合、このパラメータは、リモート・ホスト上のRMIリモート・オブジェクトの名前を示す文字列になります。詳細は、\fBjstatd\fRコマンドの\fB\-n\fRオプションを参照してください。 +.RE +.SH "出力フォーマット" +.PP +\fBjps\fRコマンドの出力は、次のパターンに従います。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBlvmid [ [ classname | JARfilename | "Unknown"] [ arg* ] [ jvmarg* ] ]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +すべての出力トークンは空白文字で区切られます。\fBarg\fR値の中で空白を使用すると、実際の定位置パラメータに引数をマッピングしようとするときに、あいまいになります。 +.PP +\fB注意:\fR +将来のリリースでこの形式は変更される可能性があるため、\fBjps\fRの出力を解析するスクリプトは作成しないことをお薦めします。\fBjps\fR出力を解析するスクリプトを作成すると、このツールの将来のリリースで、作成したスクリプトの変更が必要になる可能性があります。 +.SH "例" +.PP +この項では、\fBjps\fRコマンドの例を示します。 +.PP +ローカル・ホスト上で計測されたJVMを一覧表示する場合: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps\fR +\fB18027 Java2Demo\&.JAR\fR +\fB18032 jps\fR +\fB18005 jstat\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、リモート・ホスト上で計測されたJVMを一覧表示します。この例では、\fBjstat\fRサーバーと、その内部RMIレジストリまたは別の外部rmiregistryプロセスのいずれかが、リモート・ホストのデフォルト・ポート(ポート1099)で実行されていると想定しています。また、ローカル・ホストが、リモート・ホストへの有効なアクセス権を持っていることも想定しています。この例には、\fB\-l\fRオプションも含まれ、クラス名またはJARファイル名を詳細な形式で出力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps \-l remote\&.domain\fR +\fB3002 /opt/jdk1\&.7\&.0/demo/jfc/Java2D/Java2Demo\&.JAR\fR +\fB2857 sun\&.tools\&.jstatd\&.jstatd\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、RMIレジストリにデフォルトではないポートを使用して、リモート・ホスト上で計測されたJVMを一覧表示します。この例では、内部RMIレジストリがポート2002にバインドされた\fBjstatd\fRサーバーが、リモート・ホスト上で実行されていると想定しています。また、\fB\-m\fRオプションを使用して、一覧表示されたそれぞれのJavaアプリケーションの\fBmain\fRメソッドに渡される引数を組み込んでいます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps \-m remote\&.domain:2002\fR +\fB3002 /opt/jdk1\&.7\&.0/demo/jfc/Java2D/Java2Demo\&.JAR\fR +\fB3102 sun\&.tools\&.jstatd\&.jstatd \-p 2002\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstatd(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jrunscript.1 b/jdk-1.8.0.281/man/ja/man1/jrunscript.1 new file mode 100755 index 0000000..9beb79e --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jrunscript.1 @@ -0,0 +1,194 @@ +'\" t +.\" Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jrunscript +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: スクリプティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jrunscript" "1" "2013å¹´11月21日" "JDK 8" "スクリプティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jrunscript \- 対話型モードとバッチ・モードをサポートするコマンド行スクリプト・シェルを実行します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript\fR [\fIoptions\fR] [\fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIarguments\fR +.RS 4 +引数を使用する場合、オプションまたはコマンド名の直後に記述してください。引数を参照してください。 +.RE +.SH "説明" +.PP +\fBjrunscript\fRコマンドは、言語に依存しないコマンド行スクリプト・シェルです。\fBjrunscript\fRは、対話型(read\-eval\-print)モードとバッチ(\fB\-f\fRオプション)・モードの両方のスクリプト実行をサポートします。デフォルトの使用言語はJavaScriptですが、\fB\-l\fRオプションを使用すれば他の言語も指定できます。\fBjrunscript\fRコマンドは、Javaとスクリプト言語との通信を使用して探求的なプログラミング・スタイルをサポートします。 +.SH "オプション" +.PP +\-classpath \fIpath\fR +.RS 4 +スクリプトがアクセスする必要のあるクラス・ファイルの場所を示します。 +.RE +.PP +\-cp \fIpath\fR +.RS 4 +\fB\-classpath\fR +\fIpath\fRと同じです。 +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +Javaのシステム・プロパティを設定します。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBflag\fRを、\fBjrunscript\fRコマンドが実行されているJava仮想マシンに直接渡します。 +.RE +.PP +\-I \fIlanguage\fR +.RS 4 +指定されたスクリプト言語を使用します。デフォルトではJavaScriptが使用されます。他のスクリプト言語を使用するには、\fB\-cp\fRまたは\fB\-classpath\fRオプションを使用して、対応するスクリプト・エンジンのJARファイルを指定する必要があります。 +.RE +.PP +\-e \fIscript\fR +.RS 4 +指定されたスクリプトを評価します。このオプションを使用すれば、コマンドラインにすべてが指定された1行スクリプトを実行できます。 +.RE +.PP +\-encoding \fIencoding\fR +.RS 4 +スクリプト・ファイルの読取り時に使用する文字エンコーディングを指定します。 +.RE +.PP +\-f \fIscript\-file\fR +.RS 4 +指定されたスクリプト・ファイル(バッチ・モード)を評価します。 +.RE +.PP +\-f \- +.RS 4 +標準入力からスクリプトを読み取り、それを評価します(対話型モード)。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-? +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-q +.RS 4 +利用可能なすべてのスクリプト・エンジンを一覧表示したあと、終了します。 +.RE +.SH "引数" +.PP +argumentsが存在していて、かつ\fB\-e\fR、\fB\-f\fRのいずれのオプションも使用されなかった場合、最初の引数がスクリプト・ファイルとなり、他の引数が存在する場合はスクリプトに渡されます。argumentsと、\fB\-e\fRまたは\fB\-f\fRオプションが使用されている場合、すべてのargumentsがスクリプトに渡されます。arguments、\fB\-e\fR、\fB\-f\fRがどれも存在しなかった場合は、対話型モードが使用されます。スクリプトからスクリプト引数を使用するには、\fBarguments\fRという名前の\fBString\fR配列型のエンジン変数を使用します。 +.SH "例" +.SS "インライン・スクリプトの実行" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript \-e "print(\*(Aqhello world\*(Aq)"\fR +\fBjrunscript \-e "cat(\*(Aqhttp://www\&.example\&.com\*(Aq)"\fR + +.fi +.if n \{\ +.RE +.\} +.SS "指定された言語の使用およびスクリプト・ファイルの評価" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript \-l js \-f test\&.js\fR + +.fi +.if n \{\ +.RE +.\} +.SS "対話型モード" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript\fR +\fBjs> print(\*(AqHello World\en\*(Aq);\fR +\fBHello World\fR +\fBjs> 34 + 55\fR +\fB89\&.0\fR +\fBjs> t = new java\&.lang\&.Thread(function() { print(\*(AqHello World\en\*(Aq); })\fR +\fBThread[Thread\-0,5,main]\fR +\fBjs> t\&.start()\fR +\fBjs> Hello World\fR +\fB \fR +\fBjs>\fR + +.fi +.if n \{\ +.RE +.\} +.SS "スクリプト引数を指定したスクリプト・ファイルの実行" +.PP +test\&.jsファイルはスクリプト・ファイルです。\fBarg1\fR、\fBarg2\fRおよび\fBarg3\fRの各引数がスクリプトに渡されます。スクリプトはarguments配列を使用してこれらの引数にアクセスできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript test\&.js arg1 arg2 arg3\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.PP +JavaScriptを使用している場合、ユーザー定義スクリプトを評価する前に、\fBjrunscript\fRコマンドによって特定の組込み関数およびオブジェクトが初期化されます(これらについては、次のjrunscript JavaScript組込みのAPI仕様に記載されています)。 +.PP +http://docs\&.oracle\&.com/javase/7/docs/technotes/tools/share/jsdocs/overview\-summary\&.html +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jsadebugd.1 b/jdk-1.8.0.281/man/ja/man1/jsadebugd.1 new file mode 100755 index 0000000..116ee71 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jsadebugd.1 @@ -0,0 +1,155 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jsadebugd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jsadebugd" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jsadebugd \- Javaプロセスまたはコア・ファイルに接続し、デバッグ・サーバーとして機能します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjsadebugd\fR \fIpid\fR [ \fIserver\-id\fR ] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjsadebugd\fR \fIexecutable\fR \fIcore\fR [ \fIserver\-id\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIpid\fR +.RS 4 +デバッグ・サーバーが接続するプロセスのプロセスIDです。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。単一のプロセスに接続できるデバッグ・サーバーのインスタンスは、1つに制限されます。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +デバッグ・サーバーを接続するコア・ファイルです。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のマシン上で実行されている場合に必要になる、オプションの一意のIDです。このIDは、リモート・クライアントが、接続先のデバッグ・サーバーを特定するために使用する必要があります。このIDは、単一のマシン内で一意にする必要があります。 +.RE +.SH "説明" +.PP +\fBjsadebugd\fRコマンドは、Javaプロセスまたはコア・ファイルに接続し、デバッグ・サーバーとして機能します。\fBjstack\fR、\fBjmap\fRおよび\fBjinfo\fRなどのリモート・クライアントは、Java Remote Method Invocation (RMI)を使用しているサーバーに接続できます。\fBjsadebugd\fRコマンドを起動する前に、\fBrmiregistry\fRコマンドでRMIレジストリを次のように起動します。\fI$JAVA_HOME\fRはJDKのインストール・ディレクトリです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry \-J\-Xbootclasspath/p:$JAVA_HOME/lib/sajdi\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.PP +RMIレジストリが起動していない場合、\fBjsadebugd\fRコマンドはRMIレジストリを標準(1099)ポートで内部で起動します。デバッグ・サーバーは、\fBSIGINT\fRを送信することにより停止できます。SIGINTを送信するには、\fB[Ctrl] + [C]\fRを押します。 +.PP +\fB注意:\fR +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。\fBdbgeng\&.dll\fRが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。\fBPATH\fR環境変数には、ターゲット・プロセスによって使用されるjvm\&.dllの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。例: +\fBs\fR\fBet PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jinfo(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jmap(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstack(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jstack.1 b/jdk-1.8.0.281/man/ja/man1/jstack.1 new file mode 100755 index 0000000..4e6f606 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jstack.1 @@ -0,0 +1,194 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstack +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstack" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jstack \- Javaプロセス、コア・ファイルまたはリモート・デバッグ・サーバーに対するJavaスレッドのスタック・トレースを出力します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstack\fR [ \fIoptions\fR ] \fIpid\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstack\fR [ \fIoptions\fR ] \fIexecutable\fR \fIcore\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstack\fR [ \fIoptions\fR ] [ \fIserver\-id\fR@ ] \fIremote\-hostname\-or\-IP\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIpid\fR +.RS 4 +出力するスタック・トレースのプロセスIDです。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +出力するスタック・トレースのコア・ファイルです。 +.RE +.PP +\fIremote\-hostname\-or\-IP\fR +.RS 4 +リモート・デバッグ・サーバーの\fBホスト名\fRまたは\fBIP\fRアドレス。jsadebugd(1)を参照してください。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のリモート・ホストで実行している場合の、オプション固有のID。 +.RE +.SH "説明" +.PP +\fBjstack\fRコマンドは、指定されたJavaプロセス、コア・ファイルまたはリモート・デバッグ・サーバーに対するJavaスレッドのJavaスタック・トレースを出力します。Javaフレームごとに、フルクラス名、メソッド名、バイトコード・インデックス(bci)、および行番号(利用可能な場合)が出力されます。\fB\-m\fRオプションを使用すると、\fBjstack\fRコマンドは、すべてのスレッドのJavaフレームとネイティブ・フレームの両方を、プログラム・カウンタ(PC)とともに出力します。ネイティブ・フレームごとに、PCに最も近いネイティブ・シンボル(利用可能な場合)が出力されます。C++分解名は分解解除されません。C++名を分解解除するには、このコマンドの出力を\fBc++filt\fRにパイプします。指定されたプロセスが64ビットJava仮想マシン上で実行されている場合は、\fB\-J\-d64\fRオプションを指定する必要があります(例: +\fBjstack \-J\-d64 \-m pid\fR)。 +.PP +\fB注意\fR +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。dbgeng\&.dllファイルが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。また、\fBPATH\fR環境変数には、ターゲット・プロセスによって使用されるjvm\&.dllの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBset PATH=<jdk>\ejre\ebin\eclient;%PATH%\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-F +.RS 4 +\fBjstack\fR +[\fB\-l\fR] +\fBpid\fRが応答しない場合にスタック・ダンプを強制します。 +.RE +.PP +\-l +.RS 4 +長形式のリスト。所有\fBjava\&.util\&.concurrent\fRの所有できるシンクロナイザの一覧など、ロックについての追加情報を印刷します。http://docs\&.oracle\&.com/javase/8/docs/api/java/util/concurrent/locks/AbstractOwnableSynchronizer\&.htmlにある +\fBAbstractOwnableSynchronizer\fRクラス記述を参照してください +.RE +.PP +\-m +.RS 4 +JavaおよびネイティブC/C++フレームの両方を持つ混合モードのスタック・トレースを出力します。 +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.SH "既知の不具合" +.PP +混合モードのスタック・トレースでは、\fB\-m\fRオプションはリモート・デバッグ・サーバーでは機能しません。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +pstack(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +C++filt(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jstat.1 b/jdk-1.8.0.281/man/ja/man1/jstat.1 new file mode 100755 index 0000000..b30b1ab --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jstat.1 @@ -0,0 +1,625 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstat +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: モニタリング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstat" "1" "2015å¹´3月3日" "JDK 8" "モニタリング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jstat \- Java Virtual Machine (JVM)の統計をモニターします。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat\fR [ \fIgeneralOption\fR | \fIoutputOptions vmid\fR [ \fIinterval\fR[s|ms] [ \fIcount \fR] ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIgeneralOption\fR +.RS 4 +単独で使用する一般的なコマンド行オプションです(\fB\-help\fRまたは\fB\-options\fR)。一般的なオプションを参照してください。 +.RE +.PP +\fIoutputOptions\fR +.RS 4 +単一の\fBstatOption\fRと\fB\-t\fR、\fB\-h\fRおよび\fB\-J\fRのいずれかのオプションで構成される1つ以上の出力オプション。出力オプションを参照してください。 +.RE +.PP +\fIvmid\fR +.RS 4 +ターゲットJVMを示す文字列である仮想マシン識別子です。一般的な構文は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][//]lvmid[@hostname[:port]/servername]\fR + +.fi +.if n \{\ +.RE +.\} +\fBvmid\fR文字列の構文は、URIの構文に対応しています。\fBvmid\fR文字列は、ローカルJVMを表す単純な整数から、通信プロトコル、ポート番号、および他の実装固有の値を示す複雑な構造まで、様々に異なります。仮想マシン識別子を参照してください。 +.RE +.PP +\fIinterval\fR [s|ms] +.RS 4 +秒(s)またはミリ秒(ms)のうち指定した単位でのサンプリング間隔です。デフォルトの単位はミリ秒です。正の整数にする必要があります。指定した場合、\fBjstat\fRコマンドは各間隔で出力を生成します。 +.RE +.PP +\fIcount\fR +.RS 4 +表示するサンプル数です。デフォルト値は無限で、ターゲットJVMが終了するまで、または\fBjstat\fRコマンドが終了するまで、\fBjstat\fRコマンドは統計データを表示します。この値は、正の整数である必要があります。 +.RE +.SH "説明" +.PP +\fBjstat\fRコマンドは、設置されているJava HotSpot VMのパフォーマンス統計データを表示します。ターゲットJVMは、仮想マシン識別子または\fBvmid\fRオプションによって識別されます。 +.SH "仮想マシン識別子" +.PP +\fBvmid\fR文字列の構文は、URIの構文に対応しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][//]lvmid[@hostname[:port]/servername]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fIprotocol\fR +.RS 4 +通信プロトコルです。\fIprotocol\fR値が省略され、ホスト名が指定されていない場合、デフォルトのプロトコルが、プラットフォーム固有の最適化されたローカル・プロトコルになります。\fIprotocol\fR値が省略され、ホスト名が指定されている場合は、デフォルト・プロトコルは\fBrmi\fRになります。 +.RE +.PP +\fIlvmid\fR +.RS 4 +ターゲットJVMのローカル仮想マシン識別子です。\fBlvmid\fRは、システム上のJVMを一意に識別するプラットフォーム固有の値です。\fBlvmid\fRは、仮想マシン識別子の唯一の必須要素です。\fBlvmid\fRは、一般的にはターゲットJVMプロセスに対するオペレーティング・システムのプロセス識別子ですが、必ずしもそうであるとは限りません。\fBjps\fRコマンドを使用して、\fBlvmid\fRを特定できます。また、Solaris、LinuxおよびOS Xプラットフォームでは\fBps\fRコマンドを使用して、WindowsではWindowsタスク・マネージャを使用して、\fBlvmid\fRを特定できます。 +.RE +.PP +\fIhostname\fR +.RS 4 +ターゲット・ホストを示すホスト名またはIPアドレスです。\fIhostname\fR値が省略されている場合は、ターゲット・ホストはローカル・ホストになります。 +.RE +.PP +\fIport\fR +.RS 4 +リモート・サーバーと通信するためのデフォルト・ポートです。\fIhostname\fR値が省略されているか、最適化されたローカル・プロトコルが\fIprotocol\fR値に指定されている場合、\fIport\fR値は無視されます。それ以外の場合、\fBport\fRパラメータの扱いは、実装によって異なります。デフォルトの\fBrmi\fRプロトコルの場合、ポート値は、リモート・ホスト上のrmiregistryのポート番号を示します。\fIport\fR値が省略され、\fIprotocol\fR値で\fBrmi\fRが指定されている場合、デフォルトのrmiregistryポート(1099)が使用されます。 +.RE +.PP +\fIservername\fR +.RS 4 +\fBservername\fRパラメータの扱いは、実装によって異なります。最適化されたローカル・プロトコルの場合、このフィールドは無視されます。\fBrmi\fRプロトコルの場合、これは、リモート・ホスト上のRMIリソース・オブジェクトの名前を表します。 +.RE +.SH "オプション" +.PP +\fBjstat\fRコマンドは、一般的なオプションと出力オプションの2つのタイプのオプションをサポートしています。一般的なオプションを使用した場合、\fBjstat\fRコマンドは簡単な使用率およびバージョン情報を表示します。出力オプションによって、統計データ出力の内容と形式が決まります。 +.PP +すべてのオプションとその機能は、将来のリリースで変更または廃止される可能性があります。 +.SS "一般的なオプション" +.PP +いずれかの一般的なオプションを指定した場合、他のオプションまたはパラメータは一切指定できません。 +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.PP +\-options +.RS 4 +Staticオプションのリストを表示します。出力オプションを参照してください。 +.RE +.SS "出力オプション" +.PP +一般的なオプションを指定しない場合に、出力オプションを指定できます。出力オプションは、\fBjstat\fRコマンドの出力の内容と形式を決定し、単一の\fBstatOption\fRといずれかの出力オプション(\fB\-h\fR、\fB\-t\fRおよび\fB\-J\fR)で構成されます。\fBstatOption\fRは最初に記述する必要があります。 +.PP +出力は、各列が空白で区切られた表の形式になります。タイトルを含むヘッダー行によって、各列の意味がわかります。ヘッダーの表示頻度を設定するには、\fB\-h\fRオプションを使用します。列のヘッダー名は、様々なオプション間で一貫性が保たれています。一般に、2つのオプションで同じ名前の列が使用されていれば、2つの列のデータ・ソースは同じです。 +.PP +\fB\-t\fRオプションを使用すると、Timestampというラベルの付いたタイムスタンプの列が、出力の最初の列として表示されます。Timestamp列には、ターゲットJVMの起動からの経過時間が、秒単位で表示されます。タイムスタンプの精度は、様々な要因によって異なり、大量の負荷のかかったシステムでのスレッド・スケジュールの遅延により変動します。 +.PP +intervalおよびcountパラメータを使用して、\fBjstat\fRコマンドがその出力を表示する頻度と回数をそれぞれ指定します。 +.PP +\fB注意:\fR +将来のリリースでこの形式は変更される可能性があるため、\fBjstat\fRコマンドの出力を解析するスクリプトは作成しなでください。\fBjstat\fRコマンドの出力を解析するスクリプトを作成する場合は、このツールの将来のリリースで、そのスクリプトを変更する必要があることに留意してください。 +.PP +\-\fIstatOption\fR +.RS 4 +\fBjstat\fRコマンドが表示する統計データ情報を指定します。次に、利用可能なオプションの一覧を示します。特定のプラットフォーム・インストールのオプションを一覧表示するには、一般的なオプションの\fB\-options\fRを使用します。Statオプションおよび出力を参照してください。 +.sp +\fBclass\fR: クラス・ローダーの動作に関する統計データを表示します。 +.sp +\fBcompiler\fR: Java HotSpot VM Just\-in\-Timeコンパイラの動作に関する統計データを表示します。 +.sp +\fBgc\fR: ガベージ・コレクトされたヒープの動作に関する統計データを表示します。 +.sp +\fBgccapacity\fR: 世代ごとの容量と対応する領域に関する統計データを表示します。 +.sp +\fBgccause\fR: ガベージ・コレクション統計データのサマリー(\fB\-gcutil\fRと同じ)と、直前および現在(適用可能な場合)のガベージ・コレクション・イベントの原因を表示します。 +.sp +\fBgcnew\fR: New世代の動作に関する統計データを表示します。 +.sp +\fBgcnewcapacity\fR: New世代のサイズと対応する領域に関する統計データを表示します。 +.sp +\fBgcold\fR: Old世代の動作とメタスペースに関する統計データを表示します。 +.sp +\fBgcoldcapacity\fR: Old世代のサイズに関する統計データを表示します。 +.sp +\fBgcmetacapacity\fR: メタスペースのサイズに関する統計データを表示します。 +.sp +\fBgcutil\fR: ガベージ・コレクションのサマリーに関する統計データを表示します。 +.sp +\fBprintcompilation\fR: Java HotSpot VMコンパイル・メソッドの統計データを表示します。 +.RE +.PP +\-h \fIn\fR +.RS 4 +\fIn\fRサンプル(出力行)ごとに列ヘッダーを表示します。ここで、\fIn\fRは正の整数値です。デフォルト値は0です。この場合、データの最初の行の上に列ヘッダーが表示されます。 +.RE +.PP +\-t +.RS 4 +タイムスタンプ列を出力の最初の列として表示します。タイムスタンプは、ターゲットJVMの起動時からの経過時間です。 +.RE +.PP +\-J\fIjavaOption\fR +.RS 4 +\fBjavaOption\fRをJavaアプリケーション起動ツールに渡します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。オプションの完全なリストについては、java(1)を参照してください。 +.RE +.SS "Statオプションおよび出力" +.PP +次の情報は、\fBjstat\fRコマンドが各\fIstatOption\fRについて出力する列をまとめたものです。 +.PP +\-class \fIoption\fR +.RS 4 +クラス・ローダーの統計データ。 +.sp +\fBLoaded\fR: ロードされたクラスの数。 +.sp +\fBBytes\fR: ロードされたKBの数。 +.sp +\fBUnloaded\fR: アンロードされたクラスの数。 +.sp +\fBBytes\fR: アンロードされたKBの数。 +.sp +\fBTime\fR: クラスのロードやアンロード処理に要した時間。 +.RE +.PP +\-compiler \fIoption\fR +.RS 4 +Java HotSpot VM Just\-in\-Timeコンパイラの統計データ。 +.sp +\fBCompiled\fR: 実行されたコンパイル・タスクの数。 +.sp +\fBFailed\fR: 失敗したコンパイル・タスクの数。 +.sp +\fBInvalid\fR: 無効にされたコンパイル・タスクの数。 +.sp +\fBTime\fR: コンパイル・タスクの実行に要した時間。 +.sp +\fBFailedType\fR: 最後に失敗したコンパイルのコンパイル・タイプ。 +.sp +\fBFailedMethod\fR: 最後に失敗したコンパイルのクラス名とメソッド。 +.RE +.PP +\-gc \fIoption\fR +.RS 4 +ガベージ・コレクトされたヒープの統計データ。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBS0U\fR: Survivor領域0の使用率(KB)。 +.sp +\fBS1U\fR: Survivor領域1の使用率(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBEU\fR: Eden領域の使用率(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBOU\fR: Old領域の使用率(KB)。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBMU\fR: メタスペースの使用率(KB)。 +.sp +\fBCCSC\fR: 圧縮されたクラス領域の容量(KB)。 +.sp +\fBCCSU\fR: 使用されている圧縮されたクラス領域(KB)。 +.sp +\fBYGC\fR: 若い世代のガベージ・コレクション・イベントの数。 +.sp +\fBYGCT\fR: 若い世代のガベージ・コレクション時間。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gccapacity \fIoption\fR +.RS 4 +メモリー・プール世代および領域容量。 +.sp +\fBNGCMN\fR: New世代の最小容量(KB)。 +.sp +\fBNGCMX\fR: New世代の最大容量(KB)。 +.sp +\fBNGC\fR: New世代の現在の容量(KB)。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBOGCMN\fR: Old世代の最小容量(KB)。 +.sp +\fBOGCMX\fR: Old世代の最大容量(KB)。 +.sp +\fBOGC\fR: Old世代の現在の容量(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBMCMN\fR: メタスペースの最小容量(KB)。 +.sp +\fBMCMX\fR: メタスペースの最大容量(KB)。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBCCSMN\fR: 圧縮されたクラス領域の最小容量(KB)。 +.sp +\fBCCSMX\fR: 圧縮されたクラス領域の最大容量(KB)。 +.sp +\fBCCSC\fR: 圧縮されたクラス領域の容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.RE +.PP +\-gccause \fIoption\fR +.RS 4 +このオプションは、\fB\-gcutil\fRオプションと同じガベージ・コレクション統計データのサマリーを表示しますが、最後のガベージ・コレクション・イベントと(適用可能な場合は)現在のガベージ・コレクション・イベントの原因が含まれます。\fB\-gcutil\fRで一覧表示される列のほか、このオプションでは次の列が追加されます。 +.sp +\fBLGCC\fR: 最後のガベージ・コレクションの原因 +.sp +\fBGCC\fR: 現在のガベージ・コレクションの原因 +.RE +.PP +\-gcnew \fIoption\fR +.RS 4 +New世代の統計データ。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBS0U\fR: Survivor領域0の使用率(KB)。 +.sp +\fBS1U\fR: Survivor領域1の使用率(KB)。 +.sp +\fBTT\fR: 殿堂入りしきい値。 +.sp +\fBMTT\fR: 最大殿堂入りしきい値。 +.sp +\fBDSS\fR: 適切なSurvivorサイズ(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBEU\fR: Eden領域の使用率(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBYGCT\fR: 若い世代のガベージ・コレクション時間。 +.RE +.PP +\-gcnewcapacity \fIoption\fR +.RS 4 +New世代領域サイズの統計データ。 +.sp +\fBNGCMN\fR: New世代の最小容量(KB)。 +.sp +\fBNGCMX\fR: New世代の最大容量(KB)。 +.sp +\fBNGC\fR: New世代の現在の容量(KB)。 +.sp +\fBS0CMX\fR: Survivor領域0の最大容量(KB)。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1CMX\fR: Survivor領域1の最大容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBECMX\fR: Eden領域の最大容量(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.RE +.PP +\-gcold \fIoption\fR +.RS 4 +OldおよびPermanent世代の統計データ。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBMU\fR: メタスペースの使用率(KB)。 +.sp +\fBCCSC\fR: 圧縮されたクラス領域の容量(KB)。 +.sp +\fBCCSU\fR: 使用されている圧縮されたクラス領域(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBOU\fR: Old領域の使用率(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gcoldcapacity \fIoption\fR +.RS 4 +Old世代の統計データ。 +.sp +\fBOGCMN\fR: Old世代の最小容量(KB)。 +.sp +\fBOGCMX\fR: Old世代の最大容量(KB)。 +.sp +\fBOGC\fR: Old世代の現在の容量(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gcmetacapacity \fIoption\fR +.RS 4 +Permanent世代の統計データ。 +.sp +\fBMCMN\fR: メタスペースの最小容量(KB)。 +.sp +\fBMCMX\fR: メタスペースの最大容量(KB)。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBCCSMN\fR: 圧縮されたクラス領域の最小容量(KB)。 +.sp +\fBCCSMX\fR: 圧縮されたクラス領域の最大容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gcutil \fIoption\fR +.RS 4 +ガベージ・コレクション統計データのサマリー +.sp +\fBS0\fR: Survivor領域0の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBS1\fR: Survivor領域1の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBE\fR: Eden領域の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBO\fR: Old領域の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBM\fR: メタスペースの使用率(領域の現在の容量に対するパーセンテージ)。 +.sp +\fBCCS\fR: 圧縮されたクラス領域の使用率(パーセンテージ)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBYGCT\fR: 若い世代のガベージ・コレクション時間。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-printcompilation \fIoption\fR +.RS 4 +Java HotSpot VMコンパイル・メソッドの統計データ。 +.sp +\fBCompiled\fR: 最近コンパイルされたメソッドで実行されたコンパイル・タスクの数。 +.sp +\fBSize\fR: 最近コンパイルされたメソッドのバイト・コードのバイト数。 +.sp +\fBType\fR: 最近コンパイルされたメソッドのコンパイル・タイプ。 +.sp +\fBMethod\fR: 最近コンパイルされたメソッドを特定するクラス名とメソッド名。クラス名では、名前空間の区切り文字として、ドット(\&.)のかわりにスラッシュ(/)が使用されます。メソッド名は、指定されたクラス内のメソッドです。これらの2つのフィールドの形式は、HotSpot +\fB\-XX:+PrintCompilation\fRオプションと対応しています。 +.RE +.SH "例" +.PP +この項では、21891の\fIlvmid\fRを持つローカルJVMをモニタリングする例を示します。 +.SS "gcutilオプション" +.PP +この例では、lvmid 21891に接続して、250ミリ秒間隔で7つのサンプルを取得し、\-\fBgcutil\fRオプションでの指定に従って出力を表示します。 +.PP +この例の出力は、若い世代のコレクションが3番目と4番目のサンプル間で行われたことを示しています。コレクションには0\&.078秒かかっており、オブジェクトがEden領域(E)からOld領域(O)に昇格したため、Old領域の使用率は66\&.80%から68\&.19%に増加しています。Survivor領域は、コレクション前は97\&.02%が使用されていましたが、コレクション後の使用は91\&.03%です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcutil 21891 250 7\fR +\fB S0 S1 E O M CCS YGC YGCT FGC FGCT GCT \fR +\fB 0\&.00 97\&.02 70\&.31 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 0\&.00 97\&.02 86\&.23 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 0\&.00 97\&.02 96\&.53 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 91\&.03 0\&.00 1\&.98 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 15\&.82 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 17\&.80 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 17\&.80 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +.fi +.if n \{\ +.RE +.\} +.SS "列ヘッダー文字列の繰返し" +.PP +この例では、lvmid 21891に接続して、250ミリ秒間隔でサンプルを取得し、\fB\-gcnew\fRオプションでの指定に従って出力を表示します。さらに、\fB\-h3\fRオプションを使用して、データが3行表示されるごとに列ヘッダーを出力します。 +.PP +この例では、ヘッダー文字列の繰返しが表示されているほか、2番目と3番目のサンプル間でYoung GCが行われたことがわかります。この継続時間は0\&.001秒でした。このコレクションでは、Survivor領域0の使用率(S0U)が適切なSurvivorサイズ(DSS)を超過することになるアクティブ・データが検出されました。この結果、オブジェクトは、Old世代(この出力には非表示)へ昇格され、殿堂入りしきい値(TT)が、31から2へ降格されました。 +.PP +別のコレクションが、5番目と6番目のサンプル間で行われています。このコレクションでは、Survivorがほとんど見られず、殿堂入りしきい値を31に戻しました。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcnew \-h3 21891 250\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 0\&.0 31\&.7 31 31 32\&.0 512\&.0 178\&.6 249 0\&.203\fR +\fB 64\&.0 64\&.0 0\&.0 31\&.7 31 31 32\&.0 512\&.0 355\&.5 249 0\&.203\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 21\&.9 250 0\&.204\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 245\&.9 250 0\&.204\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 421\&.1 250 0\&.204\fR +\fB 64\&.0 64\&.0 0\&.0 19\&.0 31 31 32\&.0 512\&.0 84\&.4 251 0\&.204\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 0\&.0 19\&.0 31 31 32\&.0 512\&.0 306\&.7 251 0\&.204\fR + +.fi +.if n \{\ +.RE +.\} +.SS "サンプルごとのタイムスタンプの挿入" +.PP +この例では、lvmid21891へ接続し、250ミリ秒間隔で3つのサンプルを取得しています。\fB\-t\fRオプションを使用して、最初の列にサンプルごとのタイムスタンプを表示しています。 +.PP +Timestamp列には、ターゲットJVMの起動時からの経過時間が、秒単位でレポートされています。さらに、\fB\-gcoldcapacity\fR出力では、割当リクエストまたは昇格リクエストあるいはその両方を満たすためにヒープが拡張するたびに、Old世代の容量(OGC)とOld領域の容量(OC)とが増加していることがわかります。81番目のフル・ガベージ・コレクション(FGC)の後、Old世代の容量(OGC)は11,696KBから13,820KBに増加しました。この世代(および領域)の最大容量は、60,544KB (OGCMX)なので、まだ拡張できる余裕が残されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBTimestamp OGCMN OGCMX OGC OC YGC FGC FGCT GCT\fR +\fB 150\&.1 1408\&.0 60544\&.0 11696\&.0 11696\&.0 194 80 2\&.874 3\&.799\fR +\fB 150\&.4 1408\&.0 60544\&.0 13820\&.0 13820\&.0 194 81 2\&.938 3\&.863\fR +\fB 150\&.7 1408\&.0 60544\&.0 13820\&.0 13820\&.0 194 81 2\&.938 3\&.863\fR + +.fi +.if n \{\ +.RE +.\} +.SS "リモートJVMのインストゥルメンテーションのモニター" +.PP +この例は、\fB\-gcutil\fRオプションを使用して、remote\&.domainというシステム上のlvmid 40496に接続し、サンプルを秒単位で無期限に取得しています。 +.PP +lvmidは、リモート・ホストの名前と結合されて、\fB40496@remote\&.domain\fRの\fIvmid\fRを構成しています。結果として、このvmidは、\fBrmi\fRプロトコルを使用して、リモート・ホスト上のデフォルトの\fBjstatd\fRサーバーと通信します。\fBjstatd\fRサーバーは、\fBrmiregistry\fRコマンドを使用して、\fBrmiregistry\fRコマンドのデフォルトのポート(ポート1099)にバインドされた\fBremote\&.domain\fRに配置されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcutil 40496@remote\&.domain 1000\fR +\fB\fI\&.\&.\&. output omitted\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstatd(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jstatd.1 b/jdk-1.8.0.281/man/ja/man1/jstatd.1 new file mode 100755 index 0000000..d92ff23 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jstatd.1 @@ -0,0 +1,259 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstatd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: モニタリング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstatd" "1" "2013å¹´11月21日" "JDK 8" "モニタリング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jstatd \- Java仮想マシン(JVM)をモニターし、リモート・モニタリング・ツールがJVMに接続できるようにします。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd\fR [ \fIoptions\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +\fBjstatd\fRコマンドは、計測されたJava HotSpot VMの作成と終了をモニターし、ローカル・システム上で実行されているJVMに、リモート・モニタリング・ツールが接続できるようにするためのインタフェースを提供するRMIサーバー・アプリケーションです。 +.PP +\fBjstatd\fRサーバーでは、ローカル・ホストにRMIレジストリが必要になります。\fBjstatd\fRサーバーはデフォルト・ポートで、または\fB\-p\fR +\fBport\fRオプションで指定したポートで、RMIレジストリに接続しようとします。RMIレジストリが見つからない場合、\fB\-p\fR +\fBport\fRオプションで指定されたポート、または\fB\-p\fR +\fBport\fRオプションが省略されている場合は、デフォルトRMIレジストリにバインドされた\fBjstatd\fRアプリケーション内に、1つのRMIレジストリが作成されます。内部RMIレジストリの作成は、\fB\-nr\fRオプションを指定することによって中止できます。 +.SH "オプション" +.PP +\-nr +.RS 4 +既存のRMIレジストリが見つからない場合、\fBjstatd\fRプロセス内に内部RMIレジストリを作成しないようにします。 +.RE +.PP +\-p \fIport\fR +.RS 4 +RMIレジストリがあると予想されるポート番号です。見つからない場合は、\fB\-nr\fRオプションが指定されていなければ作成されます。 +.RE +.PP +\-n \fIrminame\fR +.RS 4 +RMIレジストリにおいて、リモートRMIオブジェクトがバインドされる名前です。デフォルト名は\fBJStatRemoteHost\fRです。複数の\fBjstatd\fRサーバーが同じホスト上で起動している場合、各サーバーのエクスポートしたRMIオブジェクトの名前は、このオプションを指定することによって、一意の名前にすることができます。ただし、このオプションを使用する場合、モニタリング・クライアントの\fBhostid\fRおよび\fBvmid\fR文字列に、その一意のサーバー名を含める必要があります。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +JVMに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されている\fBオプション\fRを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "セキュリティ" +.PP +\fBjstatd\fRサーバーは、適切なネイティブ・アクセス権を持つJVMのみをモニターできます。したがって、\fBjstatd\fRプロセスは、ターゲットJVMと同じユーザー資格証明で実行されている必要があります。Solaris、LinuxおよびOS Xオペレーティング・システムにおけるrootユーザーなどの一部のユーザー資格証明は、システム上の任意のJVMによってエクスポートされたインストゥルメンテーションへのアクセス権を持っています。このような資格証明で実行されている\fBjstatd\fRプロセスは、システム上のすべてのJVMをモニターできますが、セキュリティ上の別の問題が起こります。 +.PP +\fBjstatd\fRサーバーには、リモート・クライアントの認証機能がありません。そのため、\fBjstatd\fRサーバー・プロセスを実行すると、\fBjstatd\fRプロセスがアクセス権を持つすべてのJVMによるインストゥルメンテーションのエクスポートを、ネットワーク上のすべてのユーザーに公開することになります。この無防備な状態は、環境によっては望ましくない場合があるので、特に本番環境またはセキュアでないネットワークでは、\fBjstatd\fRプロセスを起動する前に、ローカル・セキュリティ・ポリシーを検討する必要があります。 +.PP +\fBjstatd\fRサーバーは、他のセキュリティ・マネージャがインストールされていない場合には、\fBRMISecurityPolicy\fRのインスタンスをインストールします。そのため、セキュリティ・ポリシー・ファイルを指定する必要があります。ポリシー・ファイルは、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.htmlにある +「デフォルトのPolicyの実装とポリシー・ファイルの構文」に準拠している必要があります +.PP +次のポリシー・ファイルでは、セキュリティ例外を発生せずに\fBjstatd\fRサーバーを実行できます。このポリシーは、すべてのコード・ベースへのあらゆるアクセス権を認めるポリシーよりも自由度が低いですが、\fBjstatd\fRサーバーを実行するために最低限必要なアクセス権のみを認めるポリシーよりも自由度が高くなっています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBgrant codebase "file:${java\&.home}/\&.\&./lib/tools\&.jar" { \fR +\fB permission java\&.security\&.AllPermission;\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +このポリシー設定を使用するには、このテキストを\fBjstatd\&.all\&.policy\fRというファイルにコピーし、次のように\fBjstatd\fRサーバーを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=jstatd\&.all\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.PP +より厳しいセキュリティを実施するサイトの場合、カスタム・ポリシー・ファイルを使用して、特定の信頼できるホストまたはネットワークにアクセスを制限することができます。ただし、このような方法は、IPアドレスの盗聴攻撃を受けやすくなります。セキュリティの問題について、カスタマイズしたポリシー・ファイルでも対処できない場合は、\fBjstatd\fRサーバーを実行せずに、\fBjstat\fRと\fBjps\fRツールをローカルで使用することが最も安全な方法になります。 +.SH "リモート・インタフェース" +.PP +\fBjstatd\fRプロセスがエクスポートするインタフェースは、独自に開発したものであり変更される予定です。ユーザーおよび開発者は、このインタフェースへの書込みを行わないでください。 +.SH "例" +.PP +次に、\fBjstatd\fRコマンドの例を示します。\fBjstatd\fRスクリプトによって、サーバーはバックグラウンドで自動的に起動します。 +.SS "内部RMIレジストリ" +.PP +この例は、内部RMIレジストリを使用した\fBjstatd\fRセッションの起動方法を表しています。この例では、デフォルトのRMIレジストリ・ポート(ポート1099)には、他のサーバーはバインドされていないと想定しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.SS "外部RMIレジストリ" +.PP +この例は、外部RMIレジストリを使用した\fBjstatd\fRセッションの起動を表しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry&\fR +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例では、ポート2020の外部RMIレジストリを使用して\fBjstatd\fRセッションを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrmiregistry 2020&\fR +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy \-p 2020\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例では、ポート2020の外部RMIレジストリを使用して、\fBAlternateJstatdServerName\fRにバインドされている\fBjstatd\fRセッションを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry 2020&\fR +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy \-p 2020\fR +\fB \-n AlternateJstatdServerName\fR + +.fi +.if n \{\ +.RE +.\} +.SS "インプロセスRMIレジストリの作成の停止" +.PP +この例では、外部RMIレジストリがない場合に作成しない\fBjstatd\fRセッションを起動します。この例では、RMIレジストリがすでに実行されていると想定しています。RMIレジストリが実行されていない場合、エラー・メッセージが表示されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy \-nr\fR + +.fi +.if n \{\ +.RE +.\} +.SS "RMIロギングの有効化" +.PP +この例では、RMIロギング機能を有効化して\fBjstatd\fRセッションを起動します。この方法は、トラブルシューティングまたはサーバー活動のモニタリングに役立ちます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy\fR +\fB \-J\-Djava\&.rmi\&.server\&.logCalls=true\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/jvisualvm.1 b/jdk-1.8.0.281/man/ja/man1/jvisualvm.1 new file mode 100755 index 0000000..3a3abcb --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/jvisualvm.1 @@ -0,0 +1,107 @@ +'\" t +.\" Copyright (c) 2008, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jvisualvm +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaトラブルシューティング、プロファイリング、モニタリングおよび管理ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jvisualvm" "1" "2013å¹´11月21日" "JDK 8" "Javaトラブルシューティング、プロファイリング、モニタリン" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jvisualvm \- Javaアプリケーションを視覚的に監視、トラブルシュートおよびプロファイルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjvisualvm\fR [ \fIoptions\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +Java VisualVMは、指定されたJava Virtual Machine (JVM)でJavaテクノロジ・ベースのアプリケーション(Javaアプリケーション)が実行されているときに、そのJavaアプリケーションに関する詳細な情報を提供する直感的なグラフィカル・ユーザー・インタフェースです。Java VisualVMという名前は、Java VisualVMがJVMソフトウェアに関する情報を視覚的に提供するという事実に由来しています。 +.PP +Java VisualVMは、いくつかのモニタリング、トラブルシューティングおよびプロファイリング・ユーティリティを1つのツールに統合します。たとえば、スタンドアロン・ツール\fBjmap\fR、\fBjinfo\fR、\fBjstat\fRおよび\fBjstack\fRで提供されている機能のほとんどが、Java VisualVMに組み込まれています。\fBjconsole\fRコマンドによって提供される一部の機能など、他の機能はオプションのプラグインとして追加できます。 +.PP +Java VisualVMは、Javaアプリケーションの開発者がアプリケーションのトラブルシューティングを行ったり、アプリケーションのパフォーマンスを監視および改善したりするのに役立ちます。Java VisualVMを使用すると、開発者はヒープ・ダンプの生成および解析、メモリー・リークの特定、ガベージ・コレクションの実行および監視、およびメモリーとCPUの簡易プロファイリングの実行が可能になります。プラグインでJava VisualVMの機能を拡張できます。たとえば、\fBjconsole\fRコマンドのほとんどの機能は、「MBean」タブおよびJConsole Plug\-in Wrapperプラグインを介して使用できます。標準のJava VisualVMプラグインのカタログから選択するには、Java VisualVMメニューの\fB「ツール」\fR、\fB「プラグイン」\fRを選択します。 +.PP +Java VisualVMを起動するには、次のコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% jvisualvm <options>\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +次のオプションは、Java VisualVMを起動したときに実行可能になります。 +.PP +\-J\fIjvm_option\fR +.RS 4 +この\fBjvm_option\fRをJVMソフトウェアに渡します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java VisualVM開発者のサイト +http://visualvm\&.java\&.net/ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java SEドキュメントのJava VisualVM +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/visualvm/index\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/keytool.1 b/jdk-1.8.0.281/man/ja/man1/keytool.1 new file mode 100755 index 0000000..9b84d04 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/keytool.1 @@ -0,0 +1,2229 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: keytool +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: セキュリティ・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "keytool" "1" "2015å¹´3月3日" "JDK 8" "セキュリティ・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +keytool \- 暗号化鍵、X\&.509証明書チェーンおよび信頼できる証明書を含むキーストア(データベース)を管理します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool\fR [\fIcommands\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommands\fR +.RS 4 +コマンドを参照してください。これらのコマンドは、次のようにタスク別に分類されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +キーストアへのデータの作成または追加 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-gencert +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-genkeypair +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-genseckey +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-importcert +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-importpassword +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +別のキーストアの内容のインポート +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-importkeystore +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書リクエストの生成 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-certreq +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +データのエクスポート +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-exportcert +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +データの表示 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-list +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-printcert +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-printcertreq +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-printcrl +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +キーストアの管理 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-storepasswd +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-keypasswd +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-delete +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-changealias +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ヘルプの表示 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-help +.RE +.RE +.RE +.SH "説明" +.PP +\fBkeytool\fRコマンドは、鍵と証明書を管理するためのユーティリティです。これにより、ユーザーは自分の公開鍵と秘密鍵のペアおよび関連する証明書を管理し、デジタル署名を使用した自己認証(他のユーザーまたはサービスに対して自分自身を認証すること)や、データの整合性と証明書に関するサービスを利用することができます。\fBkeytool\fRコマンドでは、通信しているピアの公開鍵をキャッシュすることもできます(証明書のフォームで)。 +.PP +証明書とは、あるエンティティ(人物、会社など)からのデジタル署名付きの文書のことです。証明書には、他のあるエンティティの公開鍵(およびその他の情報)が特別な値を持っていることが書かれています。(証明書を参照してください。)データにデジタル署名が付いている場合は、デジタル署名を検証することで、データの整合性およびデータが本物であることをチェックできます。データの整合性とは、データが変更されたり、改変されたりしていないことを意味します。また、データが本物であるとは、そのデータが、データを作成して署名したと称する人物から渡されたデータであることを意味します。 +.PP +また、\fBkeytool\fRコマンドを使用すれば、対称暗号化/復号化(DES)で使用される秘密鍵およびパスフレーズを管理することもできます。 +.PP +\fBkeytool\fRコマンドは、鍵と証明書をキーストアに格納します。キーストアの別名を参照してください。 +.SH "コマンドとオプションに関する注意" +.PP +様々なコマンドとその説明については、コマンドを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +どのコマンド名およびオプション名にも先頭にマイナス記号(\-)が付きます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +各コマンドのオプションは任意の順序で指定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +イタリックになっていないすべての項目、または中カッコか角カッコで囲まれているすべての項目は、そのとおりに指定する必要があります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションを囲む中カッコは、そのオプションをコマンド行で指定しなかった場合に、デフォルト値が使用されることを意味します。オプションのデフォルト値を参照してください。中カッコは、\fB\-v\fR、\fB\-rfc\fRおよび\fB\-J\fRオプションを囲むためにも使用されますが、これらのオプションはコマンド行で指定された場合にのみ意味を持ちます。指定されていない場合以外、デフォルト値はありません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションを囲む角カッコは、そのオプションをコマンド行で指定しなかった場合に、値の入力を求められることを意味します。\fB\-keypass\fRオプションの場合、オプションをコマンド行で指定しなかった場合は、\fBkeytool\fRコマンドがまずキーストアのパスワードを使用して非公開/秘密鍵の復元を試みます。この試みが失敗した場合、\fBkeytool\fRコマンドにより、非公開/秘密鍵のパスワードの入力を求められます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +イタリックの項目の実際の値(オプションの値)は、指定する必要があります。たとえば、\fB\-printcert\fRコマンドの形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-printcert {\-file \fR\fB\fIcert_file\fR\fR\fB} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +\fB\-printcert\fRコマンドを指定する場合は、\fIcert_file\fRを実際のファイル名で置き換えます。例: +\fBkeytool \-printcert \-file VScert\&.cer\fR +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションの値に空白(スペース)が含まれている場合は、値を引用符で囲む必要があります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-help\fRオプションがデフォルトです。\fBkeytool\fRコマンドは、\fBkeytool \-help\fRと同じです。 +.RE +.SH "オプションのデフォルト値" +.PP +次の例で、様々なオプション値のデフォルト値を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-alias "mykey"\fR +\fB \fR +\fB\-keyalg\fR +\fB "DSA" (when using \-genkeypair)\fR +\fB "DES" (when using \-genseckey)\fR +\fB \fR +\fB\-keysize\fR +\fB 2048 (when using \-genkeypair and \-keyalg is "RSA")\fR +\fB 1024 (when using \-genkeypair and \-keyalg is "DSA")\fR +\fB 256 (when using \-genkeypair and \-keyalg is "EC")\fR +\fB 56 (when using \-genseckey and \-keyalg is "DES")\fR +\fB 168 (when using \-genseckey and \-keyalg is "DESede")\fR +\fB \fR +\fB\-validity 90\fR +\fB \fR +\fB\-keystore <the file named \&.keystore in the user\*(Aqs home directory>\fR +\fB \fR +\fB\-storetype <the value of the "keystore\&.type" property in the\fR +\fB security properties file, which is returned by the static\fR +\fB getDefaultType method in java\&.security\&.KeyStore>\fR +\fB \fR +\fB\-file\fR +\fB stdin (if reading)\fR +\fB stdout (if writing)\fR +\fB \fR +\fB\-protected false\fR + +.fi +.if n \{\ +.RE +.\} +.PP +公開/秘密鍵ペアの生成において、署名アルゴリズム(\fB\-sigalg\fRオプション)は、基になる秘密鍵のアルゴリズムから派生します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +基になる秘密鍵がDSAタイプである場合は、\fB\-sigalg\fRオプションのデフォルト値はSHA1withDSAになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +基になる秘密鍵がRSAタイプである場合は、\fB\-sigalg\fRオプションのデフォルト値はSHA256withRSAになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +基になる秘密鍵がECタイプである場合は、\fB\-sigalg\fRオプションのデフォルト値はSHA256withECDSAになります。 +.RE +.PP +\fB\-keyalg\fRおよび\fB\-sigalg\fR引数の完全なリストについては、 +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppAの「Java Cryptography Architecture (JCA) Reference Guide」を参照してください。 +.SH "一般オプション" +.PP +\fB\-v\fRオプションは、\fB\-help\fRコマンドを除くすべてのコマンドで使用できます。\fB\-v\fRオプションを指定した場合、コマンドは冗長モードで実行され、詳細な情報が出力されます。 +.PP +任意のコマンドで指定できる\fB\-Jjavaoption\fR引数もあります。\fB\-Jjavaoption\fRを指定した場合、指定された\fBjavaoption\fR文字列がJavaインタプリタに直接渡されます。このオプションには、空白を含めることはできません。このオプションは、実行環境またはメモリー使用を調整する場合に便利です。指定できるインタプリタ・オプションを一覧表示するには、コマンド行で\fBjava \-h\fRまたは\fBjava \-X\fRと入力してください。 +.PP +次のオプションは、キーストアに対する操作を行うすべてのコマンドで指定できます。 +.PP +\-storetype \fIstoretype\fR +.RS 4 +この修飾子は、インスタンスを生成するキーストアのタイプを指定します。 +.RE +.PP +\-keystore \fIkeystore\fR +.RS 4 +キーストアの場所を指定します。 +.sp +特定の\fBkeytool\fRコマンドを実行する際に、JKS +\fBstoretype\fRが使用され、かつキーストア・ファイルがまだ存在していなかった場合、新しいキーストア・ファイルが作成されます。たとえば、\fBkeytool \-genkeypair\fRの呼出し時に\fB\-keystore\fRオプションが指定されなかった場合、\fB\&.keystore\fRという名前のデフォルト・キーストア・ファイルがユーザーのホーム・ディレクトリ内にまだ存在していなければ、そこに作成されます。同様に、\fB\-keystore ks_file\fRというオプションが指定されてもそのks_fileが存在しなかった場合、そのファイルが作成されます。JKS +\fBstoretype\fRの詳細は、\fIの\fRKeyStoreの実装キーストアの別名に関する項を参照してください。 +.sp +\fB\-keystore\fRオプションからの入力ストリームは、\fBKeyStore\&.load\fRメソッドに渡されます。URLとして\fBNONE\fRが指定されている場合は、nullのストリームが\fBKeyStore\&.load\fRメソッドに渡されます。\fBNONE\fRは、KeyStoreがファイルベースではない場合に指定してください。たとえば、ハードウェア・トークン・デバイス上に存在している場合などです。 +.RE +.PP +\-storepass[:\fIenv\fR| :\fIfile\fR] argument +.RS 4 +キーストアの整合性を保護するために使用するパスワードを指定します。 +.sp +修飾子\fBenv\fRまたは\fBfile\fRを指定しない場合、パスワードの値は\fBargument\fRになります。この値は、6文字以上にする必要があります。それ以外の場合、パスワードは次のようにして取得されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBenv\fR: +\fBargument\fRという名前の環境変数からパスワードを取得します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBfile\fR: argumentという名前のファイルからパスワードを取得します。 +.RE +.sp +\fB注意:\fR +\fB\-keypass\fR、\fB\-srckeypass\fR、\-\fBdestkeypass\fR、\fB\-srcstorepass\fR、\fB\-deststorepass\fRなどのパスワードを必要とするその他のオプションはすべて、\fIenv\fRおよび\fIfile\fR修飾子を受け付けます。パスワード・オプションと修飾子は、必ずコロン(:)で区切ってください。 +.sp +パスワードは、キーストアの内容にアクセスするすべてのコマンドで使用されます。この種のコマンドを実行するときに、コマンド行で\fB\-storepass\fRオプションを指定しなかった場合は、パスワードの入力を求められます。 +.sp +キーストアから情報を取得する場合、パスワードは省略可能です。パスワードが指定されていない場合は、取得した情報の整合性を検証できず、警告が表示されます。 +.RE +.PP +\-providerName \fIprovider_name\fR +.RS 4 +セキュリティ・プロパティ・ファイル内に含まれる暗号化サービス・プロバイダ名を特定するために使用されます。 +.RE +.PP +\-providerClass \fIprovider_class_name\fR +.RS 4 +暗号化サービス・プロバイダがセキュリティ・プロパティ・ファイルに指定されていないときは、そのマスター・クラス・ファイルの名前を指定するときに使用されます。 +.RE +.PP +\-providerArg \fIprovider_arg\fR +.RS 4 +\fB\-providerClass\fRオプションとともに使用され、\fBprovider_class_name\fRのコンストラクタのオプションの文字列入力引数を表します。 +.RE +.PP +\-protected +.RS 4 +\fBtrue\fRまたは\fBfalse\fRのいずれか。パスワードを専用PINリーダーなどの保護された認証パス経由で指定する必要がある場合は、この値を\fBtrue\fRに指定する必要があります。\fB\-importkeystore\fRコマンドには2つのキーストアが関連しているため、ソース・キーストアと宛先キーストアにそれぞれ次の2つのオプション、\fB\-srcprotected\fRと\-\fBdestprotected\fRが用意されています。 +.RE +.PP +\-ext \fI{name{:critical} {=value}}\fR +.RS 4 +X\&.509証明書エクステンションを示します。このオプションを\fB\-genkeypair\fRおよび\fB\-gencert\fRで使用して、生成される証明書または\fB\-certreq\fRにエクステンションを埋め込み、証明書リクエストでリクエストされるエクステンションを示すことができます。このオプションは複数回指定できます。\fBname\fR引数には、サポートされているエクステンション名(名前付きエクステンションを参照)または任意のOID番号を指定できます。指定されている場合、\fBvalue\fR引数はエクステンションの引数を指します。\fIvalue\fRを省略した場合、エクステンションのデフォルト値またはエクステンションが引数を必要としないことを示します。\fB:critical\fR修飾子が指定された場合、エクステンションの\fBisCritical\fR属性は\fBtrue\fRで、指定されない場合は\fBfalse\fRです。\fB:critical\fRのかわりに\fB:c\fRを使用できます。 +.RE +.SH "名前付きエクステンション" +.PP +\fBkeytool\fRコマンドは、次の名前のエクステンションをサポートしています。名前の大/小文字は区別されません。 +.PP +BCまたはBasicContraints +.RS 4 +\fB値\fR: 完全な形式は、\fBca:{true|false}[,pathlen:<len>]\fRまたは\fB<len>\fR(\fBca:true,pathlen:<len>\fRの短縮形)です。<\fBlen\fR>を省略すると、\fBca:true\fRの意味になります。 +.RE +.PP +KUまたはKeyUsage +.RS 4 +\fB値\fR: +\fBusage\fR(\fBusage\fR)*、\fIusage\fRには\fBdigitalSignature\fR、\fBnonRepudiation\fR +(contentCommitment)、\fBkeyEncipherment\fR、\fBdataEncipherment\fR、\fBkeyAgreement\fR、\fBkeyCertSign\fR、\fBcRLSign\fR、\fBencipherOnly\fR、\fBdecipherOnly\fRのいずれかを指定できます。\fIusage\fR引数は、不明確にならないかぎり、最初の数文字(\fBdigitalSignature\fRの場合は\fBdig\fR)またはキャメルケース・スタイル(\fBdigitalSignature\fRの場合は\fBdS\fR、\fBcRLSign\fRの場合は\fBcRLS\fR)で省略表記できます。\fBusage\fR値は、大文字と小文字が区別されます。 +.RE +.PP +EKUまたはExtendedKeyUsage +.RS 4 +\fB値\fR: +\fBusage\fR(\fBusage\fR)*、\fIusage\fRには\fBanyExtendedKeyUsage\fR、\fBserverAuth\fR、\fBclientAuth\fR、\fBcodeSigning\fR、\fBemailProtection\fR、\fBtimeStamping\fR、\fBOCSPSigning\fRまたは任意の\fIOID文字列\fRのいずれかを指定できます。\fIusage\fR引数は、不明確にならないかぎり、最初の数文字またはキャメルケース・スタイルで省略表記できます。\fBusage\fR値は、大文字と小文字が区別されます。 +.RE +.PP +SANまたはSubjectAlternativeName +.RS 4 +\fB値\fR: +\fBtype\fR:\fBvalue\fR(t\fBype:value\fR)*、\fBtype\fRには\fBEMAIL\fR、\fBURI\fR、\fBDNS\fR、\fBIP\fRまたは\fBOID\fRを指定できます。\fBvalue\fR引数は、\fBtype\fRの文字列形式の値です。 +.RE +.PP +IANまたはIssuerAlternativeName +.RS 4 +\fB値\fR: +\fBSubjectAlternativeName\fRと同じです。 +.RE +.PP +SIAまたはSubjectInfoAccess +.RS 4 +\fB値\fR: +\fBmethod\fR:\fBlocation\-type\fR:\fBlocation\-value\fR +(\fBmethod:location\-type\fR:\fBlocation\-value\fR)*、\fBmethod\fRには\fBtimeStamping\fR、\fBcaRepository\fRまたは任意のOIDを指定できます。\fBlocation\-type\fRおよび\fBlocation\-value\fR引数には、\fBSubjectAlternativeName\fRエクステンションでサポートされる任意の\fBtype\fR:\fBvalue\fRを指定できます。 +.RE +.PP +AIAまたはAuthorityInfoAccess +.RS 4 +\fB値\fR: +\fBSubjectInfoAccess\fRと同じです。\fBmethod\fR引数には、\fBocsp\fR、\fBcaIssuers\fRまたは任意のOIDを指定できます。 +.RE +.PP +\fBname\fRがOIDの場合、OCTET STRINGタイプと長さのバイトを除外したエクステンションについては、値は\fBextnValue\fRの16進ダンプのDERエンコーディングです。HEX文字列では、標準の16進数(0\-9、a\-f、A\-F)以外の文字は無視されます。したがって、01:02:03:04と01020304の両方とも同一の値として受け付けられます。値がない場合、エクステンションの値フィールドは空になります。 +.PP +\fB\-gencert\fRでのみ使用する\fBhonored\fRという特別な名前は、証明書リクエストに含まれるエクステンションを優先する方法を示します。この名前の値は、\fBall\fR(リクエストされるすべてのエクステンションが優先される)、\fBname{:[critical|non\-critical]}\fR(名前付きのエクステンションが優先されるが、別の\fBisCritical\fR属性を使用する)、および\fB\-name\fR(\fBall\fRとともに使用し、例外を示す)のカンマ区切りリストです。デフォルトでは、リクエストされるエクステンションは優先されません。 +.PP +\fB\-ext honored\fRオプションに加え、別の名前の、またはOID +\fB\-ext\fRのオプションを指定した場合は、このエクステンションが、すでに優先されているエクステンションに追加されます。ただし、この名前(またはOID)を優先される値でも使用した場合は、その値と重要性がリクエストに含まれるものをオーバーライドします。 +.PP +\fBsubjectKeyIdentifier\fRエクステンションは常に作成されます。自己署名でない証明書の場合は、\fBauthorityKeyIdentifier\fRが作成されます。 +.PP +\fB注意:\fR +ユーザーは、エクステンション(および証明書の他のフィールド)の組合せによっては、インターネットの標準に準拠しない場合があることに注意してください。証明書の準拠に関する警告を参照してください。 +.SH "コマンド" +.PP +\-gencert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-rfc} {\-infile \fR\fB\fIinfile\fR\fR\fB} {\-outfile \fR\fB\fIoutfile\fR\fR\fB} {\-alias \fR\fB\fIalias\fR\fR\fB} {\-sigalg \fR\fB\fIsigalg\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-dname \fR\fB\fIdname\fR\fR\fB} {\-startdate \fR\fB\fIstartdate\fR\fR\fB {\-ext \fR\fB\fIext\fR\fR\fB}* {\-validity \fR\fB\fIvalDays\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-providername \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +証明書リクエスト・ファイル(\fBkeytool\fR +\fB\-certreq\fRコマンドで作成可能)に対するレスポンスとして証明書を生成します。このコマンドは、\fIinfile\fRから(省略した場合は、標準入力から)リクエストを読み込み、別名の秘密鍵を使用してそのリクエストに署名して、X\&.509証明書を\fIoutfile\fRに(省略した場合は、標準出力に)出力します。\fB\-rfc\fRを指定した場合、出力形式はBASE64符号化のPEMになります。それ以外の場合は、バイナリDERが作成されます。 +.sp +\fBsigalg\fR値には、証明書に署名を付けるときに使用するアルゴリズムを指定します。\fBstartdate\fR引数は、証明書の有効開始日時です。\fBvalDays\fR引数は、証明書の有効日数を示します。 +.sp +\fBdname\fRを指定すると、生成される証明書の主体として使用されます。それ以外の場合は、証明書リクエストからの名前が使用されます。 +.sp +\fBext\fR値は、証明書に埋め込まれるX\&.509エクステンションを示します。\fB\-ext\fRの構文については、一般オプションを参照してください。 +.sp +\fB\-gencert\fRオプションを使用すると、証明書チェーンを作成できます。次の例では、\fBe1\fRという証明書を作成します。この証明書の証明書チェーンには、3つの証明書が含まれています。 +.sp +次のコマンドは、\fBca\fR、\fBca1\fR、\fBca2\fRおよび\fBe1\fRの4つの鍵ペアを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-alias ca \-dname CN=CA \-genkeypair\fR +\fBkeytool \-alias ca1 \-dname CN=CA \-genkeypair\fR +\fBkeytool \-alias ca2 \-dname CN=CA \-genkeypair\fR +\fBkeytool \-alias e1 \-dname CN=E1 \-genkeypair\fR + +.fi +.if n \{\ +.RE +.\} +次の2つのコマンドは、署名付き証明書のチェーンを作成します。\fBca\fRは\fBca1\fRに署名し、\fBca1\fRは\fBca2\fRに署名します。すべて自己発行です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-alias ca1 \-certreq |\fR +\fB keytool \-alias ca \-gencert \-ext san=dns:ca1 |\fR +\fB keytool \-alias ca1 \-importcert\fR + +\fBkeytool \-alias ca2 \-certreq |\fR +\fB $KT \-alias ca1 \-gencert \-ext san=dns:ca2 |\fR +\fB $KT \-alias ca2 \-importcert\fR + +.fi +.if n \{\ +.RE +.\} +次のコマンドは、証明書\fBe1\fRを作成してファイル\fBe1\&.cert\fRに格納します。この証明書は\fBca2\fRによって署名されます。その結果、\fBe1\fRの証明書チェーンには\fBca\fR、\fBca1\fRおよび\fBca2\fRが含まれることになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-alias e1 \-certreq | keytool \-alias ca2 \-gencert > e1\&.cert\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-genkeypair +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-keyalg \fR\fB\fIkeyalg\fR\fR\fB} {\-keysize \fR\fB\fIkeysize\fR\fR\fB} {\-sigalg \fR\fB\fIsigalg\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-dname \fR\fB\fIdname\fR\fR\fB] [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-startdate \fR\fB\fIvalue\fR\fR\fB} {\-ext \fR\fB\fIext\fR\fR\fB}*\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-validity \fR\fB\fIvalDays\fR\fR\fB} {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +鍵のペア(公開鍵および関連する秘密鍵)を生成します。公開鍵はX\&.509 v3自己署名証明書でラップされます。証明書は、単一の要素を持つ証明書チェーンとして格納されます。この証明書チェーンと秘密鍵は、aliasで特定される新しいキーストア・エントリに格納されます。 +.sp +\fBkeyalg\fR値は鍵ペアの生成に使用するアルゴリズムを、\fBkeysize\fR値は生成する各鍵のサイズを、それぞれ指定します。\fBsigalg\fR値は、自己署名証明書に署名を付けるために使用するアルゴリズムを指定します。このアルゴリズムは\fBkeyalg\fR値と互換性がある必要があります。 +.sp +\fBdname\fR値には、\fBalias\fR値に関連付け、自己署名証明書のissuerフィールドとsubjectフィールドとして使用するX\&.500識別名を指定します。コマンド行で識別名を指定しなかった場合は、識別名の入力を求められます。 +.sp +\fBkeypass\fR値には、生成される鍵のペアのうち、秘密鍵を保護するのに使用するパスワードを指定します。パスワードを指定しなかった場合は、パスワードの入力を求められます。このとき、[Return]キーを押すと、キーストアのパスワードと同じパスワードが鍵のパスワードに設定されます。\fBkeypass\fR値は、6文字以上にする必要があります。 +.sp +\fBstartdate\fR値には、証明書の発行時刻を指定します。これは、X\&.509証明書の「Validity」フィールドの「Not Before」値とも呼ばれます。 +.sp +オプションの値は、次の2つの形式のいずれかで設定できます。 +.sp +\fB([+\-]nnn[ymdHMS])+\fR +.sp +\fB[yyyy/mm/dd] [HH:MM:SS]\fR +.sp +最初の形式では、発行時刻は、指定される値の分、現在の時刻から移ります。指定される値は、一連の下位の値を連結したものになります。下位の各値で、プラス記号(「+」)は時間が進むことを、マイナス記号(「\-」)は時間が戻ることを意味しています。移る時間は\fBnnn\fRで、単位は年、月、日、時間、分または秒です(それぞれ、1文字の\fBy\fR、\fBm\fR、\fBd\fR、\fBH\fR、\fBM\fRまたは\fBS\fR」で示されています)。下位の各値で\fBjava\&.util\&.GregorianCalendar\&.add(int field, int amount)\fRメソッドを使用することで、発行時刻の追加の値が左から右へ計算されます。たとえば、指定すると、発行時刻は次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCalendar c = new GregorianCalendar();\fR +\fBc\&.add(Calendar\&.YEAR, \-1);\fR +\fBc\&.add(Calendar\&.MONTH, 1);\fR +\fBc\&.add(Calendar\&.DATE, \-1);\fR +\fBreturn c\&.getTime()\fR + +.fi +.if n \{\ +.RE +.\} +2番目の形式では、ユーザーは、年/月/日と時間:分:秒の2つの部分で厳密な開始時刻を設定します(地元の時間帯を使用)。ユーザーは、1つの部分のみを指定できます。これは、もう1つの部分は現在の日付(または時刻)と同じになるということです。ユーザーは、形式の定義に示されているように、桁数を厳密に指定する必要があります(短い場合は0で埋めます)。日付と時刻の両方が指定された状態で、2つの部分の間に空白文字が1つ(1つのみ)あります。時間は常に24時間形式で指定してください。 +.sp +オプションを指定しないと、開始日付は現在の時刻になります。オプションは、最大で1回指定できます。 +.sp +\fBvalDays\fRの値には、証明書の有効日数を指定します(\fB\-startdate\fRで指定された日付、または\fB\-startdate\fRが指定されていない場合は現在の日付から始まります)。 +.sp +このコマンドは、以前のリリースでは\fB\-genkey\fRという名前でした。このリリースでは、引き続き古い名前がサポートされています。今後は、新しい名前\fB\-genkeypair\fRが優先されます。 +.RE +.PP +\-genseckey +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-keyalg \fR\fB\fIkeyalg\fR\fR\fB} {\-keysize \fR\fB\fIkeysize\fR\fR\fB} [\-keypass \fR\fB\fIkeypass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +秘密鍵を生成し、それを新しい\fBKeyStore\&.SecretKeyEntry\fR(\fBalias\fRで特定される)内に格納します。 +.sp +\fBkeyalg\fR値は鍵ペアの生成に使用するアルゴリズムを、\fBkeysize\fR値は生成する各鍵のサイズを、それぞれ指定します。\fBkeypass\fR値は、秘密鍵を保護するパスワードです。パスワードを指定しなかった場合は、パスワードの入力を求められます。このとき、[Return]キーを押すと、\fBkeystore\fRのパスワードと同じパスワードが鍵のパスワードに設定されます。\fBkeypass\fR値は、6文字以上にする必要があります。 +.RE +.PP +\-importcert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-file \fR\fB\fIcert_file\fR\fR\fB} [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-noprompt} {\-trustcacerts}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +ファイル\fBcert_file\fRから証明書または証明書チェーン(証明書チェーンの場合は、PKCS#7形式の応答または一連のX\&.509証明書で提供されるもの)を読み込み、\fBalias\fRによって特定される\fBkeystore\fRエントリに格納します。ファイルが指定されていない場合は、\fBstdin\fRから証明書または証明書チェーンを読み込みます。 +.sp +\fBkeytool\fRコマンドでは、X\&.509 v1、v2、v3の証明書、およびPKCS#7形式の証明書から構成されているPKCS#7形式の証明書チェーンをインポートできます。インポートするデータは、バイナリ符号化方式、または出力可能符号化方式(Base64符号化とも呼ばれる)のどちらかで提供する必要があります。出力可能符号化方式は、インターネットRFC 1421証明書符号化規格で定義されています。この符号化方式の場合、証明書は\fB\-\fR\fB\-\-\-\-BEGIN\fRで始まる文字列で開始され、\fB\-\-\-\-\-END\fRで始まる文字列で終了する必要があります。 +.sp +証明書は、信頼できる証明書のリストに追加するため、および認証局(CA)に証明書署名リクエストを送信した結果としてCAから受信した証明書応答をインポートするため(\fBの\fR\-certreqコマンドオプションを参照)という2つの理由でインポートします。 +.sp +どちらのタイプのインポートを行うかは、\fB\-alias\fRオプションの値によって指定します。別名がキー・エントリをポイントしない場合、\fBkeytool\fRコマンドはユーザーが信頼できる証明書エントリを追加しようとしているものとみなします。この場合、別名がキーストア内に存在していないことが必要です。別名がすでに存在している場合、その別名の信頼できる証明書がすでに存在することになるので、\fBkeytool\fRコマンドはエラーを出力し、証明書のインポートを行いません。別名がキー・エントリをポイントする場合、\fBkeytool\fRコマンドはユーザーが証明書応答をインポートしようとしているものとみなします。 +.RE +.PP +\-importpassword +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +パスフレーズをインポートし、\fBalias\fRで識別される新規\fBKeyStore\&.SecretKeyEntry\fRに格納します。パスフレーズは、標準入力ストリームを介して提供できます。または、ユーザーにそのプロンプトが表示されます。\fBkeypass\fRは、インポートされるパスフレーズの保護に使用されるパスワードです。パスワードを指定しなかった場合は、パスワードの入力を求められます。このとき、[Return]キーを押すと、\fBkeystore\fRのパスワードと同じパスワードが鍵のパスワードに設定されます。\fBkeypass\fRは、6文字以上にする必要があります。 +.RE +.PP +\-importkeystore +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-srcstoretype \fR\fB\fIsrcstoretype\fR\fR\fB} {\-deststoretype \fR\fB\fIdeststoretype\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-srcstorepass \fR\fB\fIsrcstorepass\fR\fR\fB] [\-deststorepass \fR\fB\fIdeststorepass\fR\fR\fB] {\-srcprotected}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-destprotected} \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-srcalias \fR\fB\fIsrcalias\fR\fR\fB {\-destalias \fR\fB\fIdestalias\fR\fR\fB} [\-srckeypass \fR\fB\fIsrckeypass\fR\fR\fB]} \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-destkeypass \fR\fB\fIdestkeypass\fR\fR\fB] {\-noprompt}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-srcProviderName \fR\fB\fIsrc_provider_name\fR\fR\fB} {\-destProviderName \fR\fB\fIdest_provider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +ソース・キーストアからターゲット・キーストアへ、単一のエントリまたはすべてのエントリをインポートします。 +.sp +\fB\-srcalias\fRオプションが指定された場合、このコマンドは、その別名で特定される単一のエントリをターゲット・キーストアにインポートします。\fBdestalias\fR経由でターゲット別名が指定されなかった場合、\fBsrcalias\fRがターゲット別名として使用されます。ソースのエントリがパスワードで保護されていた場合、\fBsrckeypass\fRを使用してそのエントリが回復されます。\fIsrckeypass\fRが指定されなかった場合、\fBkeytool\fRコマンドは\fBsrcstorepass\fRを使用してそのエントリを回復しようとします。\fBsrcstorepass\fRが指定されなかったか正しくなかった場合、ユーザーはパスワードの入力を求められます。ターゲットのエントリは\fBdestkeypass\fRによって保護されます。\fBdestkeypass\fRが指定されなかった場合、ターゲット・エントリはソース・エントリのパスワードによって保護されます。たとえば、ほとんどのサード・パーティ・ツールでは、PKCS #12キーストアで\fBstorepass\fRと\fBkeypass\fRが同じである必要があります。これらのツールのPKCS #12キーストアを作成する場合は、常に\fB\-destkeypass\fRと\fB\-deststorepass\fRが同じになるように指定します。 +.sp +\fB\-srcalias\fRオプションが指定されなかった場合、ソース・キーストア内のすべてのエントリがターゲット・キーストア内にインポートされます。各ターゲット・エントリは対応するソース・エントリの別名の下に格納されます。ソースのエントリがパスワードで保護されていた場合、\fBsrcstorepass\fRを使用してそのエントリが回復されます。\fBsrcstorepass\fRが指定されなかったか正しくなかった場合、ユーザーはパスワードの入力を求められます。ソース・キーストア内のあるエントリ・タイプがターゲット・キーストアでサポートされていない場合や、あるエントリをターゲット・キーストアに格納する際にエラーが発生した場合、ユーザーはそのエントリをスキップして処理を続行するか、または中止するかの選択を求められます。ターゲット・エントリはソース・エントリのパスワードによって保護されます。 +.sp +ターゲット別名がターゲット・キーストア内にすでに存在していた場合、ユーザーは、そのエントリを上書きするか、あるいは異なる別名の下で新しいエントリを作成するかの選択を求められます。 +.sp + +\fB\-noprompt\fRオプションを指定した場合、ユーザーは新しいターゲット別名の入力を求められません。既存のエントリがそのターゲット別名で上書きされます。インポートできないエントリはスキップされ、警告が出力されます。 +.RE +.PP +\-printcertreq +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-file \fR\fB\fIfile\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +PKCS#10形式の証明書リクエストの内容を出力します。このリクエストは、\fBkeytool\fR +\fB\-certreq\fRコマンドで生成できます。このコマンドは、ファイルからリクエストを読み取ります。ファイルが存在しない場合、リクエストは標準入力から読み取られます。 +.RE +.PP +\-certreq +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-dname \fR\fB\fIdname\fR\fR\fB} {\-sigalg \fR\fB\fIsigalg\fR\fR\fB} {\-file \fR\fB\fIcertreq_file\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +PKCS#10形式を使用して証明書署名リクエスト(CSR)を生成します。 +.sp +CSRは、証明書発行局(CA)に送信することを目的としたものです。CAは、証明書要求者を(通常はオフラインで)認証し、証明書または証明書チェーンを送り返します。この証明書または証明書チェーンは、キーストア内の既存の証明書チェーン(最初は1つの自己署名証明書から構成される)に置き換えて使用します。 +.sp +aliasに関連付けられた秘密鍵は、PKCS#10証明書リクエストを作成するのに使用されます。秘密鍵にアクセスするには、正しいパスワードを指定する必要があります。コマンド行で\fBkeypass\fRを指定しておらず、秘密鍵のパスワードがキーストアのパスワードと異なる場合は、秘密鍵のパスワードの入力を求められます。\fBdname\fRが指定されている場合は、それがCSRで主体として使用されます。それ以外の場合は、別名に関連付けられたX\&.500識別名が使用されます。 +.sp +\fBsigalg\fR値には、CSRに署名を付けるときに使用するアルゴリズムを指定します。 +.sp +CSRは、ファイルcertreq_fileに格納されます。ファイルが指定されていない場合は、\fBstdout\fRにCSRが出力されます。 +.sp +CAからのレスポンスをインポートするには、\fBimportcert\fRコマンドを使用します。 +.RE +.PP +\-exportcert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-file \fR\fB\fIcert_file\fR\fR\fB} {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-rfc} {\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fIalias\fRに関連付けられた証明書をキーストアから読み込み、ファイルcert_fileに格納します。ファイルが指定されていない場合は、\fBstdout\fRに証明書が出力されます。 +.sp +デフォルトでは、証明書はバイナリ符号化で出力されます。\fB\-rfc\fRオプションが指定されている場合、出力可能符号化方式の出力はインターネットRFC 1421証明書符号化規格で定義されます。 +.sp +\fBalias\fRが、信頼できる証明書を参照している場合は、該当する証明書が出力されます。それ以外の場合、\fBalias\fRは、関連付けられた証明書チェーンを持つ鍵エントリを参照します。この場合は、チェーン内の最初の証明書が返されます。この証明書は、\fBalias\fRによって表されるエンティティの公開鍵を認証する証明書です。 +.sp +このコマンドは、以前のリリースでは\fB\-export\fRという名前でした。このリリースでは、引き続き古い名前がサポートされています。今後は、新しい名前\fB\-exportcert\fRが優先されます。 +.RE +.PP +\-list +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v | \-rfc} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fBalias\fRで特定されるキーストア・エントリの内容を\fBstdout\fRに出力します。\fBalias\fRが指定されていない場合は、キーストア全体の内容が表示されます。 +.sp +このコマンドは、デフォルトでは証明書のSHA1フィンガープリントを表示します。 +\fB\-v\fRオプションが指定されている場合は、所有者、発行者、シリアル番号、拡張機能などの付加的な情報とともに、人間が読むことのできる形式で証明書が表示されます。\fB\-rfc\fRオプションが指定されている場合は、出力可能符号化方式で証明書の内容が出力されます。出力可能符号化方式は、インターネットRFC 1421証明書符号化規格で定義されています。 +.sp +\fB\-v\fRオプションと\fB\-rfc\fRオプションを同時に指定することはできません。 +.RE +.PP +\-printcert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-file \fR\fB\fIcert_file\fR\fR\fB | \-sslserver \fR\fB\fIhost\fR\fR\fB[:\fR\fB\fIport\fR\fR\fB]} {\-jarfile \fR\fB\fIJAR_file\fR\fR\fB {\-rfc} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +ファイルcert_file、host:portにあるSSLサーバー、または署名付きJARファイル\fBJAR_file\fR(\fB\-jarfile\fRオプションを指定)から証明書を読み込み、人間が読むことのできる形式で証明書の内容を表示します。ポートが指定されていない場合は、標準のHTTPSポート443が想定されます。\fB\-sslserver\fRおよび\-fileオプションを同時に指定することはできません。それ以外の場合、エラーが報告されます。オプションが指定されていない場合は、\fBstdin\fRから証明書を読み込みます。 +.sp +\fB\-rfc\fRが指定されている場合、\fBkeytool\fRコマンドは、インターネットRFC 1421証明書符号化標準で定義されているように、PEMモードで証明書を出力します。インターネットRFC 1421証明書符号化規格を参照してください。 +.sp +ファイルまたは\fBstdin\fRから証明書を読み込む場合、その証明書は、インターネットRFC 1421証明書符号化標準で定義されているように、バイナリ符号化方式または出力可能符号化方式で表示できます。 +.sp +SSLサーバーがファイアウォールの背後にある場合は、\fB\-J\-Dhttps\&.proxyHost=proxyhost\fRおよび\fB\-J\-Dhttps\&.proxyPort=proxyport\fRオプションをコマンド行で指定して、プロキシ・トンネリングを使用できます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide\&.htmlの +「Java Secure Socket Extension (JSSE) Reference Guide」を参照してください +.sp +\fB注意:\fR +このオプションはキーストアとは関係なく使用できます。 +.RE +.PP +\-printcrl +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-file \fR\fB\fIcrl_\fR\fR\fB {\-v}\fR +.fi +.if n \{\ +.RE +.\} +ファイル\fBcrl_\fRから証明書失効リスト(CRL)を読み込みます。CRLは、発行したCAによって失効されたデジタル証明書のリストです。CAは、\fBcrl_\fRを生成します。 +.sp +\fB注意:\fR +このオプションはキーストアとは関係なく使用できます。 +.RE +.PP +\-storepasswd +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-new \fR\fB\fInew_storepass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +キーストアの内容の整合性を保護するために使用するパスワードを変更します。\fBnew_storepass\fRには、新しいパスワードを指定します。new_storepassは、6文字以上である必要があります。 +.RE +.PP +\-keypasswd +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} [\-keypass \fR\fB\fIold_keypass\fR\fR\fB] [\-new \fR\fB\fInew_keypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fBalias\fRによって特定される非公開/秘密鍵を保護するためのパスワードを、\fBold_keypass\fRから\fBnew_keypass\fRに変更します。new_keypassは、6文字以上である必要があります。 +.sp +コマンド行で\fB\-keypass\fRオプションを指定しておらず、鍵のパスワードがキーストアのパスワードと異なる場合は、鍵のパスワードの入力を求められます。 +.sp +コマンド行で\fB\-new\fRオプションを指定しなかった場合は、新しいパスワードの入力を求められます。 +.RE +.PP +\-delete +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-alias \fR\fB\fIalias\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerName \fR\fB\fIprovider_name\fR\fR\fB} \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fBalias\fRによって特定されるエントリをキーストアから削除します。コマンド行で別名を指定しなかった場合は、別名の入力を求められます。 +.RE +.PP +\-changealias +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} [\-destalias \fR\fB\fIdestalias\fR\fR\fB] [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +指定された\fBalias\fRから新しい別名\fBdestalias\fRへ、既存のキーストア・エントリを移動します。ターゲット別名を指定しなかった場合、ターゲット別名の入力を求められます。元のエントリがエントリ・パスワードで保護されていた場合、\fB\-keypass\fRオプションでそのパスワードを指定できます。鍵パスワードが指定されなかった場合、\fBstorepass\fR(指定された場合)がまず試みられます。その試みが失敗すると、ユーザーはパスワードの入力を求められます。 +.RE +.PP +\-help +.RS 4 +基本的なコマンドとそのオプションの一覧を表示します。 +.sp +特定のコマンドの詳細を参照するには、次のように入力してください: +\fBkeytool \-command_name \-help\fR。\fBcommand_name\fRはコマンドの名前です。 +.RE +.SH "例" +.PP +この例では、公開/秘密鍵のペアおよび信頼できるエンティティからの証明書を管理するためのキーストアを作成する手順を示します。 +.SS "鍵のペアの生成" +.PP +まず、キーストアを作成して鍵のペアを生成します。単一行に入力する、次のようなコマンドを使用できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-dname "cn=Mark Jones, ou=Java, o=Oracle, c=US"\fR +\fB \-alias business \-keypass <new password for private key>\fR +\fB \-keystore /working/mykeystore\fR +\fB \-storepass <new password for keystore> \-validity 180\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コマンドは、workingディレクトリに\fBmykeystore\fRという名前のキーストアを作成し(キーストアはまだ存在していないと仮定)、作成したキーストアに、\fB<new password for keystore>\fRで指定したパスワードを割り当てます。生成する公開鍵と秘密鍵のペアに対応するエンティティの「識別名」は、通称がMark Jones、組織単位がJava、組織がOracle、2文字の国番号がUSです。公開鍵と秘密鍵のサイズはどちらも1024ビットで、鍵の作成にはデフォルトのDSA鍵生成アルゴリズムを使用します。 +.PP +このコマンドは、デフォルトのSHA1withDSA署名アルゴリズムを使用して、公開鍵と識別名情報を含む自己署名証明書を作成します。証明書の有効期間は180日です。証明書は、別名\fBbusiness\fRで特定されるキーストア・エントリ内の秘密鍵に関連付けられます。秘密鍵には、\fB<new password for private key>\fRで指定したパスワードが割り当てられます。 +.PP +オプションのデフォルト値を使用する場合、コマンドは大幅に短くなります。この場合、オプションは不要です。デフォルト値を持つオプションでは、オプションを指定しなければデフォルト値が使用されます。必須値の入力を求められます。使用可能な値は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この場合は、\fBmykey\fRという別名でキーストア・エントリが作成され、新しく生成された鍵のペア、および90日間有効な証明書がこのエントリに格納されます。このエントリは、ホーム・ディレクトリ内の\fB\&.keystore\fRという名前のキーストアに置かれます。キーストアは、まだ存在していない場合に作成されます。識別名情報、キーストアのパスワードおよび秘密鍵のパスワードの入力を求められます。 +.PP +以降では、オプションを指定しないで\fB\-genkeypair\fRコマンドを実行したものとして例を示します。情報の入力を求められた場合は、最初に示した\fB\-genkeypair\fRコマンドの値を入力したものとします。たとえば識別名には\fBcn=Mark Jones\fR、\fBou=Java\fR、\fBo=Oracle\fR、\fBc=US\fRと指定します。 +.SS "CAからの署名付き証明書のリクエスト" +.PP +自己署名証明書を作成する鍵のペアの生成。証明書に証明書発行局(CA)の署名が付いていれば、他のユーザーから証明書が信頼される可能性も高くなります。CAの署名を取得するには、まず、証明書署名リクエスト(CSR)を生成します。たとえば、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-certreq \-file MarkJ\&.csr\fR + +.fi +.if n \{\ +.RE +.\} +.PP +CSR(デフォルト別名\fBmykey\fRによって特定されるエンティティのCSR)が作成され、MarkJ\&.csrという名前のファイルに置かれます。このファイルをCA (VeriSignなど)に提出します。CAは要求者を(通常はオフラインで)認証し、要求者の公開鍵を認証した署名付きの証明書を送り返します。場合によっては、CAが証明書のチェーンを返すこともあります。証明書のチェーンでは、各証明書がチェーン内のその前の署名者の公開鍵を認証します。 +.SS "CAからの証明書のインポート" +.PP +作成した自己署名証明書は、証明書チェーンで置き換える必要があります。証明書チェーンでは、各証明書が、「ルート」CAを起点とするチェーン内の次の証明書の署名者の公開鍵を認証します。 +.PP +CAからの証明書応答をインポートするには、キーストアか、\fBcacerts\fRキーストア・ファイル内に1つ以上の信頼できる証明書がある必要があります。コマンドの\fB\-importcert\fRを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明応答が証明書チェーンの場合は、チェーンの最上位証明書が必要です。CAの公開鍵を認証するルートCA証明書。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書応答が単一の証明書の場合は、発行CA(署名した)の証明書が必要です。その証明書が自己署名でない場合は、その署名者の証明書が必要であり、このようにして自己署名ルート証明書が必要になります。 +.RE +.PP +\fBcacerts\fRキーストア・ファイルは、いくつかのVeriSignルートCA証明書を含んだ状態で出荷されているので、VeriSignの証明書を、信頼できる証明書としてキーストア内にインポートする必要がない場合があります。ただし、他のCAに対して署名付き証明書をリクエストしていて、このCAの公開鍵を認証する証明書が、\fBcacerts\fRにまだ追加されていない場合は、該当するCAからの証明書を、「信頼できる証明書」としてインポートする必要があります。 +.PP +通常、CAからの証明書は、自己署名証明書、または他のCAによって署名された証明書です(後者の場合は、該当する他のCAの公開鍵を認証する証明書が必要)。ABC, Inc\&.,がCAで、ABCから自己署名証明書であるA\fBBCCA\&.cer\fRという名前のファイルを取得したとします(この証明書はCAの公開鍵を認証します)。信頼できる証明書として証明書をインポートするときは、証明書が有効であることを確認する必要があります。まず、証明書の内容を表示し\fBkeytool \-printcert\fRコマンドを使用するか、または\fB\-noprompt\fRオプションを指定しないで\fBkeytool \-importcert\fRコマンドを使用し、表示された証明書のフィンガープリントが、期待されるフィンガープリントと一致するかどうかを確認します。証明書を送信した人物に連絡し、この人物が提示した(または安全な公開鍵のリポジトリによって提示される)フィンガープリントと、上のコマンドで表示されたフィンガープリントとを比較します。フィンガープリントが一致すれば、送信途中で他の何者か(攻撃者など)による証明書のすり替えが行われていないことを確認できます。送信途中でこの種の攻撃が行われていた場合、チェックを行わずに証明書をインポートすると、攻撃者によって署名されたすべてのものを信頼することになります。 +.PP +証明書が有効であると信頼する場合は、次のコマンドでキーストアに追加できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importcert \-alias abc \-file ABCCA\&.cer\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ABCCA\&.cerファイルのデータを含む信頼できる証明書のエントリがキーストア内に作成され、該当するエントリに\fBabc\fRという別名が割り当てられます。 +.SS "CAからの証明書応答のインポート" +.PP +証明書署名リクエストの提出先のCAの公開鍵を認証する証明書をインポートした後は(または同種の証明書がすでにcacertsファイル内に存在している場合は)、証明応答をインポートし、自己署名証明書を証明書チェーンで置き換えることができます。このチェーンは、CAの応答がチェーンの場合に、リクエストに対するレスポンスとしてCAから送り返された証明書チェーンです。また、CAの応答が単一の証明書の場合は、この証明応答と、インポート先のキーストア内または\fBcacerts\fRキーストアファイル内にすでに存在する信頼できる証明書とを使用して構築した証明書チェーンです。 +.PP +たとえば、証明書署名リクエストをVeriSignに送信する場合、送り返された証明書の名前がVSMarkJ\&.cerだとすると、次のようにして応答をインポートできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importcert \-trustcacerts \-file VSMarkJ\&.cer\fR + +.fi +.if n \{\ +.RE +.\} +.SS "公開鍵を認証する証明書のエクスポート" +.PP +\fBjarsigner\fRコマンドを使用してJava Archive (JAR)ファイルに署名する場合、このファイルを使用するクライアントは署名を認証する必要があります。クライアントが署名を認証する方法の1つに、まず自分の公開鍵の証明書を信頼できるエントリとしてクライアントのキーストアにインポートする方法があります。 +.PP +そのためには、証明書をエクスポートして、クライアントに提供します。例として、次のコマンドを使用して、MJ\&.cerという名前のファイルに証明書をコピーできます。このコマンドでは、エントリに別名\fBmykey\fRがあると仮定しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-exportcert \-alias mykey \-file MJ\&.cer\fR + +.fi +.if n \{\ +.RE +.\} +.PP +証明書と署名付きJARファイルを入手したクライアントは、\fBjarsigner\fRコマンドを使用して署名を認証できます。 +.SS "キーストアのインポート" +.PP +コマンド\fBimportkeystore\fRを使用すれば、あるキーストアの全体を別のキーストア内にインポートできます。これは、鍵や証明書といったソースキーストア内のすべてのエントリが、単一のコマンドを使用してターゲットキーストア内にインポートされることを意味します。このコマンドを使用すれば、異なるタイプのキーストア内に含まれるエントリをインポートすることができます。インポート時には、ターゲット・キーストア内の新しいエントリはすべて、元と同じ別名および(秘密鍵や秘密鍵の場合は)保護用パスワードを持ちます。ソースキーストア内の非公開/秘密鍵をリカバリできない場合、\fBkeytool\fRコマンドはユーザーにパスワードの入力を求めます。このコマンドは、別名の重複を検出すると、ユーザーに新しい別名の入力を求めます。ユーザーは、新しい別名を指定することも、単純に既存の別名の上書きを\fBkeytool\fRコマンドに許可することもできます。 +.PP +たとえば、通常のJKSタイプのキーストアkey\&.jks内のエントリをPKCS#11タイプのハードウェア・ベースのキーストア内にインポートするには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importkeystore\fR +\fB \-srckeystore key\&.jks \-destkeystore NONE\fR +\fB \-srcstoretype JKS \-deststoretype PKCS11\fR +\fB \-srcstorepass <src keystore password>\fR +\fB \-deststorepass <destination keystore pwd>\fR + +.fi +.if n \{\ +.RE +.\} +.PP +また、\fBimportkeystore\fRコマンドを使用すれば、あるソース・キーストア内の単一のエントリをターゲット・キーストアにインポートすることもできます。この場合は、前例のオプションに加えて、インポートする別名を指定する必要があります。\fB\-srcalias\fRオプションを指定する場合には、ターゲット別名もコマンドラインから指定できるほか、秘密/秘密鍵の保護用パスワードやターゲット保護用パスワードも指定できます。その方法を示すコマンドを次に示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importkeystore\fR +\fB \-srckeystore key\&.jks \-destkeystore NONE\fR +\fB \-srcstoretype JKS \-deststoretype PKCS11\fR +\fB \-srcstorepass <src keystore password>\fR +\fB \-deststorepass <destination keystore pwd>\fR +\fB \-srcalias myprivatekey \-destalias myoldprivatekey\fR +\fB \-srckeypass <source entry password>\fR +\fB \-destkeypass <destination entry password>\fR +\fB \-noprompt\fR + +.fi +.if n \{\ +.RE +.\} +.SS "SSLサーバーの証明書の生成" +.PP +次に、3つのエンティティ、つまりルートCA(\fBroot\fR)、中間CA(\fBca\fR)およびSSLサーバー(\fBserver\fR)用の鍵ペアと証明書を生成する\fBkeytool\fRコマンドを示します。すべての証明書を同じキーストアに格納するようにしてください。これらの例では、RSAが推奨される鍵のアルゴリズムです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-keystore root\&.jks \-alias root \-ext bc:c\fR +\fBkeytool \-genkeypair \-keystore ca\&.jks \-alias ca \-ext bc:c\fR +\fBkeytool \-genkeypair \-keystore server\&.jks \-alias server\fR +\fB \fR +\fBkeytool \-keystore root\&.jks \-alias root \-exportcert \-rfc > root\&.pem\fR +\fB \fR +\fBkeytool \-storepass <storepass> \-keystore ca\&.jks \-certreq \-alias ca |\fR +\fB keytool \-storepass <storepass> \-keystore root\&.jks\fR +\fB \-gencert \-alias root \-ext BC=0 \-rfc > ca\&.pem\fR +\fBkeytool \-keystore ca\&.jks \-importcert \-alias ca \-file ca\&.pem\fR +\fB \fR +\fBkeytool \-storepass <storepass> \-keystore server\&.jks \-certreq \-alias server |\fR +\fB keytool \-storepass <storepass> \-keystore ca\&.jks \-gencert \-alias ca\fR +\fB \-ext ku:c=dig,kE \-rfc > server\&.pem\fR +\fBcat root\&.pem ca\&.pem server\&.pem |\fR +\fB keytool \-keystore server\&.jks \-importcert \-alias server\fR + +.fi +.if n \{\ +.RE +.\} +.SH "用語" +.PP +キーストア +.RS 4 +キーストアは、暗号化の鍵と証明書を格納するための機能です。 +.RE +.PP +キーストアのエントリ +.RS 4 +キーストアには異なるタイプのエントリを含めることができます。\fBkeytool\fRコマンドで最も適用範囲の広いエントリ・タイプは、次の2つです。 +.sp +\fB鍵のエントリ\fR +\- 各エントリは、非常に重要な暗号化の鍵の情報を保持します。この情報は、許可していないアクセスを防ぐために、保護された形で格納されます。一般に、この種のエントリとして格納される鍵は、秘密鍵か、対応する公開鍵の証明書チェーンを伴う秘密鍵です。証明書チェーンを参照してください。\fBkeytool\fRコマンドがこの両方のタイプのエントリを処理できるのに対し、\fBjarsigner\fRツールは後者のタイプのエントリ、つまり秘密鍵とそれに関連付けられた証明書チェーンのみを処理します。 +.sp +\fB信頼できる証明書のエントリ\fR: 各エントリは、第三者からの公開鍵証明書を1つ含んでいます。このエントリは、信頼できる証明書と呼ばれます。それは、証明書内の公開鍵が、証明書のSubject(所有者)によって特定されるアイデンティティに由来するものであることを、キーストアの所有者が信頼するからです。証明書の発行者は、証明書に署名を付けることによって、その内容を保証します。 +.RE +.PP +キーストアの別名 +.RS 4 +キーストアのすべてのエントリ(鍵および信頼できる証明書エントリ)は、一意の別名を介してアクセスされます。 +.sp +別名を指定するのは、\fB\-genseckey\fRコマンドを使用して秘密鍵を生成したり、\fB\-genkeypair\fRコマンドを使用して鍵ペア(公開鍵と秘密鍵)を生成したり、\fB\-importcert\fRコマンドを使用して証明書または証明書チェーンを信頼できる証明書のリストに追加するなど、特定のエンティティをキーストアに追加する場合です。これ以後、\fBkeytool\fRコマンドでエンティティを参照する場合は、このときに指定した別名を使用する必要があります。 +.sp +たとえば、\fBduke\fRという別名を使用して新しい公開鍵と秘密鍵のペアを生成し、公開鍵を自己署名証明書でラップするとします。この場合は、次のコマンドを実行します。証明書チェーンを参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-alias duke \-keypass dukekeypasswd\fR + +.fi +.if n \{\ +.RE +.\} +この例では、初期パスワードとして\fBdukekeypasswd\fRを指定しています。以後、別名\fBduke\fRに関連付けられた秘密鍵にアクセスするコマンドを実行するときは、このパスワードが必要になります。Dukeの秘密鍵のパスワードをあとから変更するには、次のコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-keypasswd \-alias duke \-keypass dukekeypasswd \-new newpass\fR + +.fi +.if n \{\ +.RE +.\} +パスワードが、\fBdukekeypasswd\fRから\fBnewpass\fRに変更されます。テスト目的の場合、またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。必要なパスワードのオプションをコマンド行で指定しなかった場合は、パスワードの入力を求められます。 +.RE +.PP +キーストアの実装 +.RS 4 +\fBjava\&.security\fRパッケージで提供されている\fBKeyStore\fRクラスは、キーストア内の情報へのアクセスおよび情報の変更を行うための、明確に定義されたインタフェースを提供します。キーストアの固定実装としては、それぞれが特定のタイプのキーストアを対象とする複数の異なる実装が存在可能です。 +.sp +現在、\fBkeytool\fRと\fBjarsigner\fRの2つのコマンド行ツールと、Policy Toolという名前のGUIベースのツールが、キーストアの実装を使用しています。\fBKeyStore\fRクラスは\fBpublic\fRであるため、ユーザーはKeyStoreを使用した他のセキュリティ・アプリケーションも作成できます。 +.sp +キーストアには、Oracleが提供する組込みのデフォルトの実装があります。これは、JKSという名前の独自のキーストア・タイプ(形式)を利用するもので、キーストアをファイルとして実装しています。この実装では、個々の秘密鍵は個別のパスワードによって保護され、キーストア全体の整合性も(秘密鍵とは別の)パスワードによって保護されます。 +.sp +キーストアの実装は、プロバイダベースです。具体的には、\fBKeyStore\fRによって提供されるアプリケーション・インタフェースがサービス・プロバイダ・インタフェース(SPI)に基づいて実装されます。つまり、対応する\fBKeystoreSpi\fR抽象クラス(これも\fBjava\&.security\fRパッケージに含まれています)があり、このクラスが、プロバイダが実装する必要のあるService Provider Interfaceのメソッドを定義しています。ここで、\fIプロバイダ\fRとは、Java Security APIによってアクセス可能なサービスのサブセットに対し、その固定実装を提供するパッケージまたはパッケージの集合のことです。キーストアの実装を提供するには、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/HowToImplAProvider\&.htmlにある +Java暗号化アーキテクチャのプロバイダの実装方法で説明しているように、クライアントはプロバイダを実装し、\fBKeystoreSpi\fRサブクラスの実装を提供する必要があります。 +.sp +アプリケーションでは、\fBKeyStore\fRクラスが提供する\fBgetInstance\fRファクトリ・メソッドを使用することで、様々なプロバイダから異なるタイプのキーストアの実装を選択できます。キーストアのタイプは、キーストア情報の格納形式とデータ形式を定義するとともに、キーストア内の非公開/秘密鍵とキーストアの整合性を保護するために使用されるアルゴリズムを定義します。異なるタイプのキーストアの実装には、互換性はありません。 +.sp +\fBkeytool\fRコマンドは、任意のファイルベースのキーストア実装で動作します。コマンド行で渡されたキーストアの場所をファイル名として扱って、\fBFileInputStream\fRに変換し、ここからキーストア情報をロードします。\fBjarsigner\fRおよび\fBpolicytool\fRコマンドは、URLで指定できる任意の場所からキーストアを読み取ることができます。 +.sp +\fBkeytool\fRと\fBjarsigner\fRの場合、\fB\-storetype\fRオプションを使用してコマンド行でキーストアのタイプを指定できます。Policy Toolの場合は、「キーストア」メニューによってキーストアのタイプを指定できます。 +.sp +ユーザーがキーストアのタイプを明示的に指定しなかった場合、セキュリティ・プロパティ・ファイルで指定された\fBkeystore\&.type\fRプロパティの値に基づいて、ツールによってキーストアの実装が選択されます。このセキュリティ・プロパティ・ファイルは\fBjava\&.security\fRと呼ばれ、Windowsではセキュリティ・プロパティ・ディレクトリ\fBjava\&.home\elib\esecurity\fR、Oracle Solarisでは\fBjava\&.home/lib/security\fRにあります。\fBjava\&.home\fRは、実行時環境のディレクトリです。\fBjre\fRディレクトリは、SDKまたはJava Runtime Environment (JRE)の最上位のディレクトリにあります。 +.sp +各ツールは、\fBkeystore\&.type\fRの値を取得し、この値で指定されたタイプのキーストアを実装しているプロバイダが見つかるまで、現在インストールされているすべてのプロバイダを調べます。そのプロバイダからのキーストアの実装を使用します。\fBKeyStore\fRクラスに定義されているstaticメソッド\fBgetDefaultType\fRを使用すると、アプリケーションやアプレットから\fBkeystore\&.type\fRプロパティの値を取得できます。次のコードは、デフォルトのキーストア・タイプ(\fBkeystore\&.type\fRプロパティで指定されたタイプ)のインスタンスを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBKeyStore keyStore = KeyStore\&.getInstance(KeyStore\&.getDefaultType());\fR + +.fi +.if n \{\ +.RE +.\} +デフォルトのキーストア・タイプは\fBjks\fRで、これはOracleが提供する独自のタイプのキーストアの実装です。これは、セキュリティ・プロパティ・ファイル内の次の行によって指定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=jks\fR + +.fi +.if n \{\ +.RE +.\} +各ツールでデフォルト以外のキーストアの実装を使用するには、上の行を変更して別のキーストアのタイプを指定します。たとえば、\fBpkcs12\fRと呼ばれるキーストアのタイプのキーストアの実装を提供するプロバイダ・パッケージがある場合、行を次のように変更します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=pkcs12\fR + +.fi +.if n \{\ +.RE +.\} +\fB注意:\fR +キーストアのタイプの指定では、大文字と小文字は区別されません。たとえば、JKSとjksは同じものとして扱われます。 +.RE +.PP +証明書 +.RS 4 +証明書(公開鍵証明書)とは、あるエンティティ(発行者)からのデジタル署名付きの文書のことです。証明書には、他のあるエンティティ(署名者)の公開鍵(およびその他の情報)が特別な値を持っていることが書かれています。次の用語は、証明書に関連しています。 +.sp +\fB公開鍵\fR: 公開鍵は、特定のエンティティに関連付けられた数です。公開鍵は、該当するエンティティとの間に信頼できる関係を持つ必要があるすべての人に対して公開することを意図したものです。公開鍵は、署名を検証するのに使用されます。 +.sp +\fBデジタル署名\fR: データがデジタル署名されると、そのデータは、エンティティのアイデンティティと、そのエンティティがデータの内容について知っていることを証明書する署名とともに格納されます。エンティティの秘密鍵を使用してデータに署名を付けると、データの偽造は不可能になります。 +.sp +\fBアイデンティティ\fR: エンティティをアドレス指定する既知の方法。システムによっては、公開鍵をアイデンティティにするものがあります。公開鍵の他にも、Oracle Solaris UIDや電子メール・アドレス、X\&.509識別名など、様々なものをアイデンティティとすることができます。 +.sp +\fB署名\fR: 署名は、なんらかのデータを基にエンティティの秘密鍵を使用して計算されます。署名者、証明書の場合は発行者とも呼ばれます。 +.sp +\fB秘密鍵\fR: 秘密鍵は特定のエンティティのみが知っている数のことで、この数のことを、そのエンティティの秘密鍵といいます。秘密鍵は、他に知られないように秘密にしておくことが前提になっています。秘密鍵と公開鍵は、すべての公開鍵暗号化システムで対になって存在しています。DSAなどの典型的な公開鍵暗号化システムの場合、1つの秘密鍵は正確に1つの公開鍵に対応します。秘密鍵は、署名を計算するのに使用されます。 +.sp +\fBエンティティ\fR: エンティティは、人、組織、プログラム、コンピュータ、企業、銀行など、一定の度合いで信頼の対象となる様々なものを指します。 +.sp +公開鍵暗号化では、ユーザーの公開鍵にアクセスする必要があります。大規模なネットワーク環境では、互いに通信しているエンティティ間で以前の関係が引続き確立されていると仮定したり、使用されているすべての公開鍵を収めた信頼できるリポジトリが存在すると仮定したりすることは不可能です。このような公開鍵の配布に関する問題を解決するために証明書が考案されました。現在では、証明書発行局(CA)が信頼できる第三者として機能します。CAは、他のエンティティの証明書に署名する(発行する)行為を、信頼して任されているエンティティ(企業など)です。CAは法律上の契約に拘束されるので、有効かつ信頼できる証明書のみを作成するものとして扱われます。VeriSign、Thawte、Entrustをはじめ、多くの公的な証明書発行局が存在します。 +.sp +Microsoftの認証サーバー、EntrustのCA製品などを所属組織内で利用すれば、独自の証明書発行局を運営することも可能です。\fBkeytool\fRコマンドを使用すると、証明書の表示、インポートおよびエクスポートを行うことができます。また、自己署名証明書を生成することもできます。 +.sp +現在、\fBkeytool\fRコマンドはX\&.509証明書を対象にしています。 +.RE +.PP +X\&.509証明書 +.RS 4 +X\&.509規格では、証明書に含める情報が定義されており、この情報を証明書に書き込む方法(データ形式)についても記述されています。証明書のすべてのデータは、ASN\&.1/DERと呼ばれる2つの関連規格を使用して符号化されます。Abstract Syntax Notation 1はデータについて記述しています。Definite Encoding Rulesは、データの保存および転送の方法について記述しています。 +.sp +すべてのX\&.509証明書は、署名の他に次のデータを含んでいます。 +.sp +\fBバージョン\fR: 証明書に適用されるX\&.509規格のバージョンを特定します。証明書に指定できる情報は、バージョンによって異なります。今のところ、3つのバージョンが定義されています。\fBkeytool\fRコマンドでは、v1、v2、v3の証明書をインポートおよびエクスポートできます。v3の証明書を生成します。 +.sp +X\&.509 Version 1は、1988年から利用されて広く普及しており、最も一般的です。 +.sp +X\&.509 Version 2では、Subjectや発行者の名前をあとで再利用できるようにするために、Subjectと発行者の一意識別子の概念が導入されました。ほとんどの証明書プロファイル文書では、名前を再使用しないことと、証明書で一意の識別子を使用しないことが、強く推奨されています。Version 2の証明書は、広くは使用されていません。 +.sp +X\&.509 Version 3は最も新しい(1996å¹´)規格で、エクステンションの概念をサポートしています。エクステンションは誰でも定義することができ、証明書に含めることができます。一般的なエクステンションとしては、KeyUsage(\fB署名専用\fRなど、鍵の使用を特定の目的に制限する)、AlternativeNames(DNS名、電子メール・アドレス、IPアドレスなど、他のアイデンティティを公開鍵に関連付けることができる)などがあります。エクステンションには、criticalというマークを付けて、そのエクステンションのチェックと使用を義務づけることができます。たとえば、criticalとマークされ、\fBkeyCertSign\fRが設定されたKeyUsageエクステンションが証明書に含まれている場合、この証明書をSSL通信中に提示すると、証明書が拒否されます。これは、証明書のエクステンションによって、関連する秘密鍵が証明書の署名専用として指定されており、SSLでは使用できないためです。 +.sp +\fBシリアル番号\fR: 証明書を作成したエンティティは、そのエンティティが発行する他の証明書と区別するために、証明書にシリアル番号を割り当てます。この情報は、様々な方法で使用されます。たとえば、証明書が取り消されると、シリアル番号が証明書失効リスト(CRL)に格納されます。 +.sp +\fB証明書アルゴリズム識別子\fR: 証明書に署名を付けるときにCAが使用したアルゴリズムを特定します。 +.sp +\fB発行者名\fR: 証明書に署名を付けたエンティティのX\&.500識別名です。X\&.500識別名を参照してください。通常はCAです。この証明書を使用することは、証明書に署名を付けたエンティティを信頼することを意味します。ルートつまりトップレベルのCAの証明書など、場合によっては発行者が自身の証明書に署名を付けることがあります。 +.sp +\fB有効期間\fR: 各証明書は限られた期間のみ有効です。この期間は開始の日時と終了の日時によって指定され、数秒の短い期間から100年という長期にわたることもあります。選択される有効期間は、証明書への署名に使用される秘密鍵の強度や証明書に支払う金額など、様々な要因で異なります。有効期間は、関連する秘密鍵が損われない場合に、エンティティが公開鍵を信頼できると期待される期間です。 +.sp +\fB主体名\fR: 証明書で公開鍵を認証するエンティティの名前。この名前はX\&.500標準を使用するので、インターネット全体で一意なものと想定されます。これは、エンティティのX\&.500識別名(DN)です。X\&.500識別名を参照してください。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=Java Duke, OU=Java Software Division, O=Oracle Corporation, C=US\fR + +.fi +.if n \{\ +.RE +.\} +これらはそれぞれ主体の通称(CN)、組織単位(OU)、組織(O)、国(C)を表します。 +.sp +\fB主体の公開鍵情報\fR: 名前を付けられたエンティティの公開鍵とアルゴリズム識別子です。アルゴリズム識別子では、公開鍵に対して使用されている公開鍵暗号化システムおよび関連する鍵パラメータが指定されています。 +.RE +.PP +証明書チェーン +.RS 4 +\fBkeytool\fRコマンドでは、秘密鍵および関連する証明書チェーンを含むキーストアの鍵エントリを作成し、管理することができます。このようなエントリでは、秘密鍵に対応する公開鍵は、チェーンの最初の証明書に含まれています。 +.sp +鍵を初めて作成すると、自己署名証明書という1つの要素のみを含むチェーンが開始されます。コマンドの\fB\-genkeypair\fRを参照してください。自己署名証明書は発行者(署名者)が主体と同じです。主体は、その公開鍵が証明書によって認証されるエンティティです。\fB\-genkeypair\fRコマンドを呼び出して新しい公開鍵と秘密鍵のペアを作成すると、公開鍵は常に自己署名証明書でラップされます。 +.sp +この後、証明書署名リクエスト(CSR)が\fB\-certreq\fRコマンドで生成されて、CSRが証明書発行局(CA)に送信されると、CAからのレスポンスが\fB\-importcert\fRでインポートされ、元の自己署名証明書は証明書チェーンによって置き換えられます。\fBの\fR\-certreq\fBおよび\fR\-importcertコマンドオプションを参照してください。チェーンの最後にあるのは、Subjectの公開鍵を認証したCAが発行した証明書(応答)です。チェーン内のその前の証明書は、CAの公開鍵を認証する証明書です。 +.sp +CAの公開鍵を認証する証明書は、多くの場合、自己署名証明書(つまりCAが自身の公開鍵を認証した証明書)であり、これはチェーンの最初の証明書になります。場合によっては、CAが証明書のチェーンを返すこともあります。この場合、チェーン内の最後の証明書(CAによって署名され、鍵エントリの公開鍵を認証する証明書)に変わりはありませんが、チェーン内のその前の証明書は、CSRの送信先のCAとは別のCAによって署名され、CSRの送信先のCAの公開鍵を認証する証明書になります。チェーン内のその前の証明書は、次のCAの鍵を認証する証明書になります。以下同様に、自己署名された「ルート」証明書に達するまでチェーンが続きます。したがって、チェーン内の(最初の証明書以後の)各証明書では、チェーン内の次の証明書の署名者の公開鍵が認証されていることになります。 +.sp +多くのCAは、チェーンをサポートせずに発行済の証明書のみを返します。特に、中間のCAが存在しないフラットな階層構造の場合は、その傾向が顕著です。このような場合は、キーストアにすでに格納されている信頼できる証明書情報から、証明書チェーンを確立する必要があります。 +.sp +別の応答形式(PKCS#7で定義されている形式)では、発行済証明書に加え、証明書チェーンのサポートが含まれています。\fBkeytool\fRコマンドでは、どちらの応答形式も扱うことができます。 +.sp +トップレベル(ルート)CAの証明書は、自己署名証明書です。ただし、ルートの公開鍵への信頼は、ルート証明書自体からではなく、新聞など他のソースから取得されます。これは、VeriSignルートCAなどの識別名を使用して、誰でも自己署名型証明書を生成できるためです。ルートCAの公開鍵は広く知られています。ルートCAの公開鍵を証明書に格納する理由は、証明書という形式にすることで多くのツールから利用できるようになるからにすぎません。つまり、証明書は、ルートCAの公開鍵を運ぶ「媒体」として利用されるのみです。ルートCAの証明書をキーストアに追加するときは、\fB\-printcert\fRオプションを使用して、その前に証明書の内容を表示し、表示されたフィンガープリントと、新聞やルートCAのWebページなどから入手した既知のフィンガープリントとを比較する必要があります。 +.RE +.PP +cacerts証明書ファイル +.RS 4 +\fBcacerts\fRという名前の証明書ファイルは、Windowsではセキュリティ・プロパティ・ディレクトリ\fBjava\&.home\elib\esecurity\fR、Oracle Solarisでは\fBjava\&.home/lib/security\fRに置かれています。\fBjava\&.home\fRは、実行環境のディレクトリ(SDKの\fBjre\fRディレクトリまたはJREの最上位ディレクトリ)です。 +.sp +\fBcacerts\fRファイルは、CAの証明書を含む、システム全体のキーストアです。システム管理者は、キーストア・タイプに\fBjks\fRを指定することで、\fBkeytool\fRコマンドを使用してこのファイルの構成と管理を行うことができます。\fBcacerts\fRキーストア・ファイルは、ルートCA証明書のデフォルト・セットを含んだ状態で出荷されています。デフォルトの証明書を一覧表示するには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-list \-keystore java\&.home/lib/security/cacerts\fR + +.fi +.if n \{\ +.RE +.\} +\fBcacerts\fRキーストア・ファイルの初期パスワードは、\fBchangeit\fRです。システム管理者は、SDKのインストール後、このファイルのパスワードとデフォルト・アクセス権を変更する必要があります。 +.sp +\fB注意:\fR +\fBcacerts\fRファイルを確認することが重要です。\fBcacerts\fRファイル内のCAは、署名および他のエンティティへの証明書発行のためのエンティティとして信頼されるため、\fBcacerts\fRファイルの管理は慎重に行う必要があります。\fBcacerts\fRファイルには、信頼するCAの証明書のみが含まれている必要があります。ユーザーは、自身の責任において、\fBcacerts\fRファイルにバンドルされている信頼できるルートCA証明書を検証し、信頼性に関する独自の決定を行います。 +.sp +信頼できないCA証明書を\fBcacerts\fRファイルから削除するには、\fBkeytool\fRコマンドの\fBdelete\fRオプションを使用します。\fBcacerts\fRファイルはJREのインストール・ディレクトリにあります。このファイルを編集するアクセス権がない場合は、システム管理者に連絡してください +.RE +.PP +インターネットRFC 1421証明書符号化規格 +.RS 4 +多くの場合、証明書は、バイナリ符号化ではなく、インターネットRFC 1421規格で定義されている出力可能符号化方式を使用して格納されます。Base 64符号化とも呼ばれるこの証明書形式では、電子メールやその他の機構を通じて、他のアプリケーションに証明書を容易にエクスポートできます。 +.sp +\fB\-importcert\fRと\fB\-printcert\fRコマンドでは、この形式の証明書とバイナリ符号化の証明書を読み込むことができます。\fB\-exportcert\fRコマンドでは、デフォルトでバイナリ符号化の証明書が出力されます。ただし、\fB\-rfc\fRオプションを指定した場合は、出力可能符号化方式の証明書が出力されます。 +.sp +\fB\-list\fRコマンドでは、デフォルトで証明書のSHA1フィンガープリントが出力されます。\fB\-v\fRオプションが指定されている場合、証明書は人が理解できる形式で出力されます。\fB\-rfc\fRオプションが指定されている場合、証明書は出力可能符号化方式で出力されます。 +.sp +出力可能符号化方式で符号化された証明書は、次のテキストで始まり、次のテキストで終了します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\-\fR + +\fBencoded certificate goes here\&. \fR + +\fB\-\-\-\-\-END CERTIFICATE\-\-\-\-\-\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +X\&.500識別名 +.RS 4 +X\&.500識別名は、エンティティを特定するために使用されます。たとえば、X\&.509証明書の\fBsubject\fRフィールドと\fBissuer\fR(署名者)フィールドで指定される名前は、X\&.500識別名です。\fBkeytool\fRコマンドは、次のサブパートをサポートしています。 +.sp +\fBcommonName\fR: Susan Jonesなど、人の通称。 +.sp +\fBorganizationUnit\fR: 小さな組織(部、課など)の名称。Purchasingなどです。 +.sp +\fBlocalityName\fR: 地域(都市)名。Palo Altoなど。 +.sp +\fBstateName\fR: 州名または地方名。Californiaなど。 +.sp +\fBcountry\fR: 2文字の国コード。CHなど。 +.sp +識別名文字列を\fB\-dname\fRオプションの値として指定する場合(たとえば\fB\-genkeypair\fRコマンドに)、文字列は次の形式にする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=cName, OU=orgUnit, O=org, L=city, S=state, C=countryCode\fR + +.fi +.if n \{\ +.RE +.\} +イタリックの項目は、実際に指定する値を表します。短縮形のキーワードの意味は、次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=commonName\fR +\fBOU=organizationUnit\fR +\fBO=organizationName\fR +\fBL=localityName\fR +\fBS=stateName\fR +\fBC=country\fR + +.fi +.if n \{\ +.RE +.\} +次に示すのは、識別名文字列の例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=Mark Smith, OU=Java, O=Oracle, L=Cupertino, S=California, C=US\fR + +.fi +.if n \{\ +.RE +.\} +この文字列を使用したコマンドの例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-dname "CN=Mark Smith, OU=Java, O=Oracle, L=Cupertino,\fR +\fBS=California, C=US" \-alias mark\fR + +.fi +.if n \{\ +.RE +.\} +キーワードの短縮形では、大文字と小文字は区別されません。たとえば、CN、cnおよびCnは、どれも同じものとして扱われます。 +.sp +一方、キーワードの指定順序には意味があり、各サブコンポーネントは上に示した順序で指定する必要があります。ただし、サブコンポーネントをすべて指定する必要はありません。たとえば、次のように一部のサブコンポーネントのみを指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=Steve Meier, OU=Java, O=Oracle, C=US\fR + +.fi +.if n \{\ +.RE +.\} +識別名文字列の値にカンマが含まれる場合に、コマンドラインで文字列を指定するときには、次のようにカンマをバックスラッシュ文字(\e)でエスケープする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcn=Peter Schuster, ou=Java\e, Product Development, o=Oracle, c=US\fR + +.fi +.if n \{\ +.RE +.\} +識別名文字列をコマンドラインで指定する必要はありません。識別名を必要とするコマンドを実行するときに、コマンドラインで識別名を指定しなかった場合は、各サブコンポーネントの入力を求められます。この場合は、カンマをバックスラッシュ(\e)でエスケープする必要はありません。 +.RE +.SH "警告" +.SS "信頼できる証明書のインポート警告" +.PP +\fB重要\fR: 信頼できる証明書として証明書をインポートする前に、証明書の内容を慎重に調べてください。 +.PP +Windowsの例: +.PP +まず、\fB\-noprompt\fRオプションを指定せずに\fB\-printcert\fRコマンドまたは\fB\-importcert\fRコマンドを使用して、証明書を表示します。表示された証明書のフィンガープリントが、期待されるフィンガープリントと一致することを確認します。たとえば、証明書が送られてきて、この証明書を\fB\etmp\ecert\fRという名前でファイルに格納しているとします。この場合は、信頼できる証明書のリストにこの証明書を追加する前に、\fB\-printcert\fRコマンドを実行してフィンガープリントを表示できます。たとえば、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB keytool \-printcert \-file \etmp\ecert\fR +\fB Owner: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Issuer: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Serial Number: 59092b34\fR +\fB Valid from: Thu Sep 25 18:01:13 PDT 1997 until: Wed Dec 24 17:01:13 PST 1997\fR +\fB Certificate Fingerprints:\fR +\fB MD5: 11:81:AD:92:C8:E5:0E:A2:01:2E:D4:7A:D7:5F:07:6F\fR +\fB SHA1: 20:B6:17:FA:EF:E5:55:8A:D0:71:1F:E8:D6:9D:C0:37:13:0E:5E:FE\fR +\fB SHA256: 90:7B:70:0A:EA:DC:16:79:92:99:41:FF:8A:FE:EB:90:\fR +\fB 17:75:E0:90:B2:24:4D:3A:2A:16:A6:E4:11:0F:67:A4\fR +.fi +.if n \{\ +.RE +.\} +.PP +Oracle Solarisの例: +.PP +まず、\fB\-noprompt\fRオプションを指定せずに\fB\-printcert\fRコマンドまたは\fB\-importcert\fRコマンドを使用して、証明書を表示します。表示された証明書のフィンガープリントが、期待されるフィンガープリントと一致することを確認します。たとえば、あるユーザーから証明書が送られてきて、この証明書を\fB/tmp/cert\fRという名前でファイルに格納しているとします。この場合は、信頼できる証明書のリストにこの証明書を追加する前に、\fB\-printcert\fRコマンドを実行してフィンガープリントを表示できます。たとえば、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB keytool \-printcert \-file /tmp/cert\fR +\fB Owner: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Issuer: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Serial Number: 59092b34\fR +\fB Valid from: Thu Sep 25 18:01:13 PDT 1997 until: Wed Dec 24 17:01:13 PST 1997\fR +\fB Certificate Fingerprints:\fR +\fB MD5: 11:81:AD:92:C8:E5:0E:A2:01:2E:D4:7A:D7:5F:07:6F\fR +\fB SHA1: 20:B6:17:FA:EF:E5:55:8A:D0:71:1F:E8:D6:9D:C0:37:13:0E:5E:FE\fR +\fB SHA256: 90:7B:70:0A:EA:DC:16:79:92:99:41:FF:8A:FE:EB:90:\fR +\fB 17:75:E0:90:B2:24:4D:3A:2A:16:A6:E4:11:0F:67:A4\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次に、証明書を送信した人物に連絡し、この人物が提示したフィンガープリントと、上のコマンドで表示されたフィンガープリントとを比較します。フィンガープリントが一致すれば、送信途中で他の何者か(攻撃者など)による証明書のすり替えが行われていないことを確認できます。送信途中でこの種の攻撃が行われていた場合、チェックを行わずに証明書をインポートすると、攻撃者によって署名されたすべてのもの(攻撃的意図を持つクラス・ファイルを含んだJARファイルなど)を信頼することになります。 +.PP +\fB注意:\fR +証明書をインポートする前に\fB\-printcert\fRコマンドを実行する必要はありません。キーストア内の信頼できる証明書のリストに証明書を追加する前に、\fB\-importcert\fRコマンドによって証明書の情報が表示され、確認を求めるメッセージが表示されるためです。ユーザーはインポート操作を停止できます。ただし、これを実行できるのは、\fB\-noprompt\fRオプションを指定せずに\fB\-importcert\fRコマンドを呼び出す場合のみです。\fB\-noprompt\fRオプションが指定されている場合、ユーザーとの対話は行われません。 +.SS "パスワード警告" +.PP +キーストアに対する操作を行うほとんどのコマンドでは、ストアのパスワードが必要です。また、一部のコマンドでは、非公開/秘密鍵のパスワードが必要になることがあります。パスワードはコマンド行で指定できます(\fB\-storepass\fRオプションと\fB\-keypass\fRオプションを使用)。ただし、テスト目的の場合、またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。必要なパスワードのオプションをコマンド行で指定しなかった場合は、パスワードの入力を求められます。 +.SS "証明書の準拠に関する警告" +.PP +インターネット標準RFC 5280では、X\&.509証明書の準拠に関するプロファイルが定義されており、証明書のフィールドおよびエクステンションに有効な値および値の組合せが記載されています。標準については、 +http://tools\&.ietf\&.org/rfc/rfc5280\&.txtを参照してください +.PP +\fBkeytool\fRコマンドでは、これらのルールすべてが適用されるわけではないため、標準に準拠しない証明書を生成できます。標準に準拠しない証明書は、JREや他のアプリケーションで拒否されることがあります。ユーザーは、\fB\-dname\fRや\fB\-ext\fRなどで適正なオプションを指定するようにしてください。 +.SH "注意" +.SS "新しい信頼できる証明書のインポート" +.PP +\fBkeytool\fRコマンドは、キーストアに証明書を追加する前に、キーストア内にすでに存在する信頼できる証明書を使用して、インポートする証明書から(ルートCAの)自己署名証明書に至るまでの信頼のチェーンの構築を試みます。 +.PP +\fB\-trustcacerts\fRオプションを指定した場合、追加の証明書は信頼できるすなわち\fBcacerts\fRという名前のファイルに含まれる証明書のチェーンとみなされます。 +.PP +\fBkeytool\fRコマンドが、インポートする証明書から自己署名証明書(キーストアまたは\fBcacerts\fRファイルに含まれている自己署名証明書)に至るまでの信頼のパスの構築に失敗した場合は、インポートする証明書の情報を表示し、ユーザーに確認を求めます。この場合は、表示された証明書のフィンガープリントと、他のなんらかの(信頼できる)情報源(証明書の所有者など)から入手したフィンガープリントとを比較します。信頼できる証明書として証明書をインポートするときは、証明書が有効であることを慎重に確認する必要があります。信頼できる証明書のインポート警告を参照してください。インポート操作は、証明書を確認する時点で中止できます。\fB\-noprompt\fRオプションが指定されている場合、ユーザーとの対話は行われません。 +.SS "証明書応答のインポート" +.PP +証明書応答をインポートするときは、キーストア内の信頼できる証明書、および(\fB\-trustcacert\fR\fBs\fRオプションが指定されている場合は)\fBcacerts\fRキーストア・ファイルで構成された証明書を使用して証明書応答が検査されます。cacerts証明書ファイルを参照してください。 +.PP +証明書応答が信頼できるかどうかを決定する方法は次のとおりです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書応答が単一のX\&.509証明書である場合、\fBkeytool\fRコマンドは、証明書応答から(ルートCAの)自己署名証明書に至るまでの信頼チェーンの確立を試みます。証明書応答と、証明書応答の認証に使用される証明書の階層構造は、aliasの新しい証明書チェーンを形成します。信頼チェーンが確立されない場合、証明書応答はインポートされません。この場合、\fBkeytool\fRコマンドは証明書を出力せず、ユーザーに検証を求めるプロンプトを表示します。ユーザーが証明書応答の信頼性を判断するのは非常に難しいためです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書応答がPKCS#7形式の証明書チェーンまたは一連のX\&.509証明書である場合、チェーンは、ユーザーの証明書が最初に、0以上のCA証明書がその次にくるように並べられます。チェーンが自己署名のルートCA証明書で終わり、\fB \-trustcacerts\fRオプションが指定されている場合、\fBkeytool\fRコマンドは、その証明書と、キーストア内または\fBcacerts\fRキーストア・ファイル内の信頼できるすべての証明書を照合しようとします。チェーンが自己署名のルートCA証明書で終わっておらず、\fB\-trustcacerts\fRオプションが指定されている場合、\fBkeytool\fRコマンドは、キーストア内または\fBcacerts\fRキーストア・ファイル内の信頼できる証明書から自己署名のルートCA証明書を見つけてそれをチェーンの末尾に追加しようとします。その証明書が見つからず、\fB\-noprompt\fRオプションが指定されていない場合は、チェーン内の最後の証明書の情報が出力され、ユーザーは確認を求められます。 +.RE +.PP +証明書応答内の公開鍵が\fBalias\fRですでに格納されているユーザーの公開鍵に一致した場合、古い証明書チェーンが応答内の新しい証明書チェーンで置き換えられます。以前の証明書チェーンを有効な\fBkeypass\fRで置き換えることができるのは、エントリの秘密鍵を保護するためのパスワードを指定した場合のみです。パスワードを指定しておらず、秘密鍵のパスワードがキーストアのパスワードと異なる場合は、秘密鍵のパスワードの入力を求められます。 +.PP +このコマンドは、以前のリリースでは\fB\-import\fRという名前でした。このリリースでは、引き続き古い名前がサポートされています。今後は、新しい名前\fB\-importcert\fRが優先されます。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jarsigner(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/security/index\&.htmlにある +「コース: Java SEのセキュリティ機能」 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/native2ascii.1 b/jdk-1.8.0.281/man/ja/man1/native2ascii.1 new file mode 100755 index 0000000..1c7c319 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/native2ascii.1 @@ -0,0 +1,81 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: native2ascii +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 国際化ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "native2ascii" "1" "2013å¹´11月21日" "JDK 8" "国際化ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +native2ascii \- サポートされている任意の文字エンコーディングの文字を含むファイルを、ASCIIおよびUnicodeでエスケープされたファイルに変換して(またはその逆)、ローカライズ可能なアプリケーションを作成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBnative2ascii\fR [ \fIinputfile\fR ] [ \fIoutputfile\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIinputfile\fR +.RS 4 +ASCIIに変換するエンコードされたファイル。 +.RE +.PP +\fIoutputfile\fR +.RS 4 +変換されたASCIIファイル。 +.RE +.SH "説明" +.PP +\fBnative2ascii\fRコマンドは、ASCII文字セットに含まれないすべての文字にUnicodeエスケープ(\fB\eu\fR\fIxxxx\fR)表記法を使用して、Java Runtime Environment (JRE)でサポートされているエンコードされたファイルを、ASCIIでエンコードされたファイルに変換します。このプロセスは、ISO\-8859\-1文字セットに含まれない文字が含まれているプロパティ・ファイルで必要です。このツールは、その逆の変換を実行することもできます。 +.PP +\fBoutputfile\fR値を省略した場合、標準出力に出力されます。さらに、\fBinputfile\fR値を省略した場合、標準入力から入力されます。 +.SH "オプション" +.PP +\-reverse +.RS 4 +逆の処理を行います。つまり、ISO\-8859\-1でUnicodeエスケープを使用してエンコードされたファイルを、JREでサポートされる文字エンコーディングのファイルに変換します。 +.RE +.PP +\-encoding \fIencoding_name\fR +.RS 4 +変換処理で使用する文字エンコーディングの名前を指定します。このオプションが存在しない場合は、デフォルトの文字エンコーディング(\fBjava\&.nio\&.charset\&.Charset\&.defaultCharset\fRメソッドで定義された)が使用されます。\fBencoding_name\fR文字列は、JREでサポートされている文字エンコーディングの名前にする必要があります。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/intl/encoding\&.doc\&.htmlにある +「サポートされているエンコーディング」を参照してください +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machine (JVM)に\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/orbd.1 b/jdk-1.8.0.281/man/ja/man1/orbd.1 new file mode 100755 index 0000000..7a37084 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/orbd.1 @@ -0,0 +1,266 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: orbd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "orbd" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +orbd \- CORBA環境のサーバーにある永続オブジェクトをクライアントから検索して呼び出せるようにします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBorbd\fR [ \fIoptions\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +\fBorbd\fRコマンドを使用すると、CORBA環境のサーバーにある永続オブジェクトをクライアントから透過的に検索して呼び出すことができます。orbdツールに含まれるサーバー・マネージャを使用すると、クライアントはCORBA環境でサーバー上にある永続オブジェクトを透過的に検索して呼び出すことができます。永続サーバーは、ネーミング・サービスに永続オブジェクト参照を発行する際、サーバーのポート番号のかわりにORBDのポート番号をオブジェクト参照に含めます。永続オブジェクト参照のオブジェクト参照にORBDポート番号を含めることには、次のような利点があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ネーミング・サービスにあるオブジェクト参照が、サーバーのライフ・サイクルと無関係になります。たとえば、オブジェクト参照は、初めてインストールされたときはネーミング・サービスのサーバーによってネーミング・サービスに発行されますが、その後は、サーバーの開始またはシャットダウンの回数にかかわらず、呼び出したクライアントにORBDが正しいオブジェクト参照を返します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クライアントは一度のみネーミング・サービスのオブジェクト参照をルックアップする必要がありますが、その後はサーバーのライフ・サイクルによる変更とは無関係にこの参照を利用することができます。 +.RE +.PP +ORBDのサーバー・マネージャにアクセスするには、\fBservertool\fRを使用してサーバーを起動する必要があります。servertoolは、アプリケーション・プログラマが、永続サーバーの登録、登録解除、起動および停止を行うためのコマンド行インタフェースです。サーバー・マネージャの詳細は、サーバー・マネージャを参照してください。 +.PP +\fBorbd\fRを起動すると、ネーミング・サービスも起動されます。ネーミング・サービスの詳細。ネーミング・サービスの起動と停止を参照してください。 +.SH "オプション" +.PP +\-ORBInitialPort \fInameserverport\fR +.RS 4 +必須。ネーム・サーバーを起動するポートの番号を指定します。\fBorbd\fRは、起動されると、このポート上で着信リクエストをリスニングします。Oracle Solarisソフトウェアでは、1024より小さいポートでプロセスを開始する場合、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。 +.RE +.SS "必須でないオプション" +.PP +\-port \fIport\fR +.RS 4 +ORBDを起動するポートを指定します。このポートで、永続オブジェクトに対するリクエストをORBDが受け取ります。このポートのデフォルト値は1049です。このポート番号は、永続Interoperable Object References (IOR)のポート・フィールドに追加されます。 +.RE +.PP +\-defaultdb \fIdirectory\fR +.RS 4 +ORBD永続格納ディレクトリ\fBorb\&.db\fRが作成されるベース・ディレクトリを指定します。このオプションが指定されていない場合、デフォルト値は\fB\&./orb\&.db\fRになります。 +.RE +.PP +\-serverPollingTime \fImilliseconds\fR +.RS 4 +\fBservertool\fRを使用して登録された永続サーバーが正常に動作していることをORBDが確認する間隔を指定します。デフォルト値は1000ミリ秒です。\fBmilliseconds\fRに指定する値は、有効な正の整数にする必要があります。 +.RE +.PP +\-serverStartupDelay milliseconds +.RS 4 +\fBservertool\fRを使用して登録された永続サーバーを再起動してから、位置転送の例外を送信するまでのORBDの待機時間を指定します。デフォルト値は1000ミリ秒です。\fBmilliseconds\fRに指定する値は、有効な正の整数にする必要があります。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SS "ネーミング・サービスの起動と停止" +.PP +ネーミング・サービスは、CORBAオブジェクトにネーミングを可能にするCORBAサービスです。ネーミングは名前をオブジェクト参照にバインドすることにより可能になります。ネーム・バインディングをネーミング・サービスに格納すれば、クライアントが名前を指定して目的のオブジェクト参照を取得できるようになります。 +.PP +クライアントまたはサーバーを実行する前に、ORBDを起動します。ORBDには、永続ネーミング・サービスおよび一時ネーミング・サービスが組み込まれています。これらはどちらもCOSネーミング・サービスの実装です。 +.PP +永続ネーミング・サービスは、ネーミング・コンテキストに対して永続性を提供します。つまり、この情報は、サービスの停止や起動後にも維持され、サービスに障害が発生した場合でも回復できます。ORBDを再起動すると、永続ネーミング・サービスはネーミング・コンテキストのグラフを復元し、すべてのクライアントとサーバーの名前のバインディングがそのまま(永続的に)保持されるようにします。 +.PP +後方互換性のため、旧リリースのJDKに同梱されていた一時ネーミング・サービス\fBtnameserv\fRが、今回のリリースのJava SEにも同梱されています。一時ネーム・サービスでは、ネーム・サービスの実行中にのみネーミング・コンテキストが保持されます。サービスが中断されると、ネーミング・コンテキスト・グラフは失われます。 +.PP +\fB\-ORBInitialPort\fR引数は、\fBorbd\fRの必須のコマンド行引数で、ネーミング・サービスが実行されるポートの番号を設定するために使用されます。次の手順では、Java IDL Object Request Broker Daemon用にポート1050を使用できることを前提としています。Oracle Solarisソフトウェアを使用する場合、1024より小さいポートでプロセスを開始するには、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。必要であれば別のポートに変更してください。 +.PP +Solaris、LinuxまたはOS Xコマンド・シェルから\fBorbd\fRを開始するには、次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBorbd \-ORBInitialPort 1050&\fR + +.fi +.if n \{\ +.RE +.\} +.PP +WindowsのMS\-DOSシステム・プロンプトでは、次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBstart orbd \-ORBInitialPort 1050\fR + +.fi +.if n \{\ +.RE +.\} +.PP +これでORBDが実行され、サーバーとクライアントのアプリケーションを実行できるようになります。クライアントとサーバーのアプリケーションは、実行時に、ネーミング・サービスが実行されているポートの番号(必要な場合はさらにマシン名)を認識している必要があります。これを実現する1つの方法は、次のコードをアプリケーションに追加することです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBProperties props = new Properties();\fR +\fBprops\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fR +\fBprops\&.put("org\&.omg\&.CORBA\&.ORBInitialHost", "MyHost");\fR +\fBORB orb = ORB\&.init(args, props);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例では、ネーミング・サービスは、ホスト\fBMyHost\fRのポート1050上で実行されます。別の方法として、コマンド行からサーバーまたはクライアントのアプリケーションを実行するときに、ポート番号またはマシン名あるいはその両方を指定する方法もあります。たとえば、次のコマンド行オプションを使用して、\fBHelloApplication\fRを起動できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava HelloApplication \-ORBInitialPort 1050 \-ORBInitialHost MyHost\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーミング・サービスを停止するには、適切なオペレーティング・システム・コマンドを使用します。たとえば、Oracle Solaris上で\fBpkill\fR +\fBorbd\fRを実行したり、\fBorbd\fRが動作中のDOSウィンドウで\fB[Ctrl]+[C]\fRキーを押します。一時ネーミング・サービスの場合は、サービスが終了されると、ネーミング・サービスに登録された名前が消去される場合があります。Java IDLネーム・サービスは、明示的に停止されるまで実行されます。 +.PP +ORBDに付属するネーミング・サービスの詳細は、 +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.htmlの「Naming Service」を参照してください +.SH "サーバー・マネージャ" +.PP +ORBDのサーバー・マネージャにアクセスして、永続サーバーを実行するには、\fBservertool\fRを使用してサーバーを起動する必要があります。servertoolは、アプリケーション・プログラマが、永続サーバーの登録、登録解除、起動および停止を行うためのコマンド行インタフェースです。\fBservertool\fRを使用してサーバーを起動する場合は、\fBorbd\fRが実行されている場所と同じポートとホストで起動する必要があります。サーバーを異なるポートで実行すると、ローカル・コンテキスト用にデータベースに保存されている情報が無効になり、サービスが正しく動作しません。 +.PP +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlExample\&.htmlの +「Java IDL: The "Hello World" Example」を参照してください +.PP +この例では、チュートリアルの手順に従って\fBidlj\fRコンパイラと\fBjavac\fRコンパイラを実行します。ORBDのサーバー・マネージャを実行するには、次の手順に従ってアプリケーションを実行します。 +.PP +\fBorbd\fRを起動します。 +.PP +Solaris、LinuxまたはOS Xコマンド・シェルで、次のように入力します: +\fBorbd \-ORBInitialPort 1050\fR +.PP +MS\-DOSシステム・プロンプト(Windows)で次のように入力します: +\fBs\fR\fBtart orbd \-ORBInitialPort 105\fR\fB0\fR +.PP +ポート1050はネーム・サーバーを実行するポートです。\fB\-ORBInitialPort\fRオプションは必須コマンド行引数です。Oracle Solarisソフトウェアを使用する場合、1024より小さいポートでプロセスを開始するには、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。 +.PP +\fBservertool\fRを起動します: +\fBservertool \-ORBInitialPort 1050\fR。 +.PP +前回の手順とネーム・サーバー(\fBorbd\fR)のポートが同じであることを確認します。たとえば\fB\-ORBInitialPort 1050\&.\fRのようになります。\fBservertool\fRは、ネーム・サーバーと同じポート上で起動する必要があります。 +.PP +\fBservertool\fRコマンドライン・インタフェースで、\fBservertool\fRプロンプトから\fBHello\fRサーバーを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBservertool > register \-server HelloServer \-classpath \&. \-applicationName\fR +\fB HelloServerApName\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBservertool\fRによってサーバーが登録されて、\fBHelloServerApName\fRという名前がサーバーに割り当てられ、登録されているすべてのサーバー一覧とともにサーバーIDが表示されます。他の端末ウィンドウまたはプロンプトからクライアント・アプリケーションを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava HelloClient \-ORBInitialPort 1050 \-ORBInitialHost localhost\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例の\fB\-ORBInitialHost localhost\fRは省略することができます。ネーム・サーバーが\fBHello\fRクライアントとして同一ホスト上で動作しているからです。ネーム・サーバーが別のホストで実行されている場合は、\-\fBORBInitialHost nameserverhost\fRオプションを使用してIDLネーム・サーバーが実行されているホストを指定します。前の手順で行われたとおりにネーム・サーバー(\fBorbd\fR)ポートを指定します(例: +\fB\-ORBInitialPort 1050\fR)。ORBDのサーバー・マネージャの操作が終了したら、ネーム・サーバー(\fBorbd\fR)と\fBservertool\fRを停止するか終了してください。MS\-DOSプロンプトで\fBorbd\fRをシャットダウンするには、サーバーを実行しているウィンドウを選択して\fB[Ctrl]+[C]\fRキーを押します。 +.PP +Oracle Solarisから\fBorbd\fRをシャットダウンするには、プロセスを検索して、\fBkill\fRコマンドで終了します。サーバーを明示的に停止するまでは、呼出し待機状態が続きます。\fBservertool\fRをシャットダウンするには、\fBquit\fRと入力してキーボードの\fB[Enter]\fRキーを押します。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +servertool(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.htmlの +「Naming Service」 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/pack200.1 b/jdk-1.8.0.281/man/ja/man1/pack200.1 new file mode 100755 index 0000000..fdd0517 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/pack200.1 @@ -0,0 +1,354 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: pack200 +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "pack200" "1" "2013å¹´11月21日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +pack200 \- WebデプロイメントのためにJARファイルをpack200圧縮ファイルにパッケージします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200\fR [\fIoptions\fR] \fIoutput\-file\fR \fIJAR\-file\fR +.fi +.if n \{\ +.RE +.\} +.PP +オプションは任意の順序で指定できます。コマンド行またはpropertiesファイルに指定された最後のオプションが、それ以前に指定されたすべてのオプションより優先されます。 +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIoutput\-file\fR +.RS 4 +出力ファイルの名前。 +.RE +.PP +\fIJAR\-file\fR +.RS 4 +入力ファイルの名前。 +.RE +.SH "説明" +.PP +\fBpack200\fRコマンドは、Java gzipコンプレッサを使用してJARファイルをpack200圧縮ファイルに変換するJavaアプリケーションです。pack200ファイルは高圧縮のファイルで、直接デプロイでき、帯域幅の節約やダウンロード時間の短縮が可能です。 +.PP +\fBpack200\fRコマンドには、圧縮エンジンの設定や微調整を行うオプションがあります。一般的な使用方法を次の例に示します。\fBmyarchive\&.pack\&.gz\fRがデフォルトの\fBpack200\fRコマンド設定で作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 myarchive\&.pack\&.gz myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-r +.br +\-\-repack +.RS 4 +JARファイルをパックした後アンパックして、JARファイルを生成します。生成されたファイルは\fBjarsigner\fR(1)ツールの入力ファイルとして使用できます。次の例では、myarchive\&.jarファイルをパックした後、アンパックします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 \-\-repack myarchive\-packer\&.jar myarchive\&.jar\fR +\fBpack200 \-\-repack myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、入力ファイル内のファイルの順序を保持します。 +.RE +.PP +\-g +.br +\-\-no\-gzip +.RS 4 +\fBpack200\fRファイルを生成します。このオプションを指定するときは、適切な圧縮ツールを使用する必要があります。また、ターゲット・システムでは、対応する圧縮解除ツールを使用する必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 \-\-no\-gzip myarchive\&.pack myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-G +.br +\-\-strip\-debug +.RS 4 +出力からデバッグ属性を削除します。これには、\fBSourceFile\fR、\fBLineNumberTable\fR、\fBLocalVariableTable\fR、\fBLocalVariableTypeTable\fRが含まれます。これらの属性を削除すれば、ダウンロードとインストールのサイズは小さくなりますが、デバッガの機能は制限されます。 +.RE +.PP +\-\-keep\-file\-order +.RS 4 +入力ファイル内のファイルの順序を保持します。これは、デフォルトの動作です。 +.RE +.PP +\-O +.br +\-\-no\-keep\-file\-order +.RS 4 +パック・ツールは、すべての要素を並べ替えて送信します。パック・ツールは、JARディレクトリ名を削除してダウンロード・サイズを削減することもできます。ただし、インデックスなど、特定のJARファイルの最適化機能が正常に動作しなくなることがあります。 +.RE +.PP +\-S\fIvalue\fR +.br +\-\-segment\-limit=\fIvalue\fR +.RS 4 +この値は、各アーカイブ・セグメントの予想ターゲット・サイズ\fIN\fR +(バイト単位)です。単一の入力ファイルの必要サイズが\fIN\fRバイトを超えると、独立したセグメントが割り当てられます。特殊なケースとして、値が\fB\-1\fRの場合は、すべての入力ファイルを含む大きな単一のセグメントが生成され、値が0の場合は、クラスごとにセグメントが1つずつ生成されます。アーカイブ・セグメントが大きくなると、断片化が少なくなり圧縮率が高くなりますが、その処理には多くのメモリーが必要です。 +.sp +各セグメントのサイズは、セグメントに変換されるそれぞれの入力ファイルのサイズのほか、その名前と他の送信されるプロパティのサイズを計算して推測されます。 +.sp +デフォルトは\-1です。つまり、パック・ツールは単一のセグメント出力ファイルを作成します。極端に大きな出力ファイルが生成される場合には、入力ファイルをセグメント化(分割)してより小さなJARにすることを強くお薦めします。 +.sp +この制限が課されていない10 MBのJARパック・ファイルは通常、約10%小さくパックされます。しかし、パック・ツールでより大きなJavaヒープ(セグメントの制限の約10倍)を必要とする場合もあります。 +.RE +.PP +\-E\fIvalue\fR +.br +\-\-effort=\fIvalue\fR +.RS 4 +単一の10進数値を指定した場合、パック・ツールは、指定された圧縮率でアーカイブを圧縮します。レベル1の場合は、比較的短い圧縮時間で多少大きめのファイルが生成されますが、レベル9の場合は、非常に長い時間がかかるものの、より圧縮率の高いファイルが生成されます。特殊な値0を指定した場合は、\fBpack200\fRコマンドは元のJARファイルを圧縮なしで直接コピーします。JSR 200標準では、すべての解凍プログラムが、この特別な場合をアーカイブ全体のパススルーと解釈するように規定しています。 +.sp +デフォルトは5です。この場合、標準的な時間で適切な圧縮が行われます。 +.RE +.PP +\-H\fIvalue\fR +.br +\-\-deflate\-hint=\fIvalue\fR +.RS 4 +入力情報を保存するというデフォルト値をオーバーライドします。転送されるアーカイブのサイズは大きくなる場合があります。指定可能な値は、\fBtrue\fR、\fBfalse\fRまたは\fBkeep\fRです。 +.sp +\fBvalue\fRが\fBtrue\fRまたはfalseの場合、\fBpacker200\fRコマンドは指定に従ってデフレーション・ヒントを出力アーカイブに設定します。アーカイブ要素の個々のデフレーション・ヒントは転送されません。 +.sp +\fBkeep\fR値は、入力JARで確認されたデフレーション・ヒントを保持します。これがデフォルトです。 +.RE +.PP +\-m\fIvalue\fR +.br +\-\-modification\-time=\fIvalue\fR +.RS 4 +指定可能な値は\fBlatest\fRと\fBkeep\fRです。 +.sp +値が最新の場合、パック・ツールは、元のアーカイブの使用可能なすべてのエントリのうちの最終更新時刻か、そのセグメントの使用可能なすべてのエントリの最終更新時刻を特定しようとします。この単一の値はセグメントの一部として転送され、各セグメントの全エントリに適用されます。この場合、すべてのインストール・ファイルに単一の日付が設定されるという問題はありますが、アーカイブの転送サイズを少し小さくすることができます。 +.sp +値が\fBkeep\fRの場合、入力JARで確認された変更時間が保持されます。これがデフォルトです。 +.RE +.PP +\-P\fIfile\fR +.br +\-\-pass\-file=\fIfile\fR +.RS 4 +ファイルを圧縮せず、バイト単位で転送するように指定します。このオプションを繰返し使用して、複数のファイルを指定できます。システム・ファイル・セパレータがJARファイル・セパレータのスラッシュ(/)に置き換えられる点を除き、パス名の変換は行われません。結果として得られるファイル名は、文字列として正確にJARファイルでの出現と一致している必要があります。\fBfile\fRにディレクトリ名を指定した場合、そのディレクトリ内のすべてのファイルが転送されます。 +.RE +.PP +\-U\fIaction\fR +.br +\-\-unknown\-attribute=\fIaction\fR +.RS 4 +デフォルトの動作をオーバーライドします。つまり、不明な属性を含むクラス・ファイルが、指定した\fBaction\fRによって渡されます。アクションとして指定可能な値は、\fBerror\fR、\fBstrip\fRまたは\fBpass\fRです。 +.sp +値が\fBerror\fRの場合、\fBpack200\fRコマンド操作全体が失敗して適切な説明が表示されます。 +.sp +値が\fBstrip\fRの場合、属性は削除されます。Java Virtual Machine (JVM)必須属性を削除すると、クラス・ローダーの障害が発生することがあります。 +.sp +値が\fBpass\fRの場合、クラス全体が1つのリソースとして転送されます。 +.RE +.PP +\-C\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-class\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +次のオプションを参照してください。 +.RE +.PP +\-F\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-field\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +次のオプションを参照してください。 +.RE +.PP +\-M\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-method\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +次のオプションを参照してください。 +.RE +.PP +\-D\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-code\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +前述の4つのオプションでは、クラス・エンティティに\fBclass\-attribute\fR、\fBfield\-attribute\fR、\fBmethod\-attribute\fRおよび\fBcode\-attribute\fRなどの属性のレイアウトを指定できます。\fIattribute\-name\fRには、これからレイアウトまたはアクションを定義する属性の名前を指定します。\fIaction\fRとして指定可能な値は、\fBsome\-layout\-string\fR、\fBerror\fR、\fBstrip\fR、\fBpass\fRです。 +.sp +\fBsome\-layout\-string\fR: レイアウト言語はJSR 200仕様で定義されています。例: +\fB\-\-class\-attribute=SourceFile=RUH\fR。 +.sp +値が\fBerror\fRの場合、\fBpack200\fR操作が失敗して説明が表示されます。 +.sp +値が\fBstrip\fRの場合、属性が出力から削除されます。VM必須属性を削除するとクラス・ローダーの障害が発生することがあります。たとえば、\fB\-\-class\-attribute=CompilationID=pass\fRというこの属性を含むクラス・ファイルを転送します。パック・ツールは、その他のアクションを行いません。 +.sp +値が\fBpass\fRの場合、クラス全体が1つのリソースとして転送されます。 +.RE +.PP +\-f \fIpack\&.properties\fR +.br +\-\-config\-file=\fIpack\&.properties\fR +.RS 4 +コマンド行に、パック・ツールを初期化するためのJavaプロパティが含まれている構成ファイルを指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 \-f pack\&.properties myarchive\&.pack\&.gz myarchive\&.jar\fR +\fBmore pack\&.properties\fR +\fB# Generic properties for the packer\&.\fR +\fBmodification\&.time=latest\fR +\fBdeflate\&.hint=false\fR +\fBkeep\&.file\&.order=false\fR +\fB# This option will cause the files bearing new attributes to\fR +\fB# be reported as an error rather than passed uncompressed\&.\fR +\fBunknown\&.attribute=error\fR +\fB# Change the segment limit to be unlimited\&.\fR +\fBsegment\&.limit=\-1\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-v +.br +\-\-verbose +.RS 4 +最小限のメッセージを出力します。このオプションを複数指定すると、より長いメッセージが作成されます。 +.RE +.PP +\-q +.br +\-\-quiet +.RS 4 +メッセージを表示せずに動作するように指定します。 +.RE +.PP +\-l\fIfilename\fR +.br +\-\-log\-file=\fIfilename\fR +.RS 4 +出力メッセージのログ・ファイルを指定します。 +.RE +.PP +\-? +.br +\-h +.br +\-\-help +.RS 4 +このコマンドに関するヘルプ情報を出力します。 +.RE +.PP +\-V +.br +\-\-version +.RS 4 +このコマンドに関するバージョン情報を出力します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定されたオプションをJava Virtual Machineに渡します。詳細は、java(1)コマンドのリファレンス・ページを参照してください。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。 +.RE +.SH "終了ステータス" +.PP +次の終了値が返されます: 正常終了の場合は0、エラーが発生した場合は0より大きい値。 +.SH "注意" +.PP +このコマンドと\fBpack\fR(1)を混同しないでください。\fBpack\fRおよび\fBpack200\fRコマンドは、別々の製品です。 +.PP +JDKに付属するJava SE API仕様との相違が見つかった場合には、仕様を優先してください。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +unpack200(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jarsigner(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/policytool.1 b/jdk-1.8.0.281/man/ja/man1/policytool.1 new file mode 100755 index 0000000..749a8fd --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/policytool.1 @@ -0,0 +1,158 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: policytool +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: セキュリティ・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "policytool" "1" "2015å¹´3月3日" "JDK 8" "セキュリティ・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +policytool \- ユーティリティGUI経由で取得したユーザー入力に基づいて、プレーン・テキストのポリシー・ファイルを読み書きします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpolicytool\fR [ \fB\-file\fR ] [ \fIfilename\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\-file +.RS 4 +ポリシー・ファイルを読み込むように\fBpolicytool\fRに指示します。 +.RE +.PP +\fIfilename\fR +.RS 4 +ロードするファイルの名前。 +.RE +.PP +\fB例\fR: +.PP +ポリシー・ツール管理ユーティリティを実行します: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpolicytool\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBpolicytool\fRコマンドを実行し、指定されたファイルをロードします: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpolicytool \-file \fR\fB\fImypolicyfile\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SH "説明" +.PP +\fBpolicytool\fRコマンドは、管理者のGUIを呼び出します。これにより、システム管理者はローカル・ポリシー・ファイルの内容を管理できるようになります。ポリシー・ファイルは\fB\&.policy\fR拡張子を持つプレーンテキスト・ファイルで、ドメイン別にリモート・リクエスタを権限オブジェクトにマップします。詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.htmlにある +「Default Policy Implementation and Policy File Syntax」を参照してください +.SH "オプション" +.PP +\-file +.RS 4 +ポリシー・ファイルを読み込むように\fBpolicytool\fRに指示します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Default Policy Implementation and Policy File Syntax」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Policy File Creation and Management」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyGuide\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Permissions in Java SE Development Kit (JDK)」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/permissions\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Java Security Overview」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/overview/jsoverview\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Java Cryptography Architecture (JCA) Reference Guide」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/rmic.1 b/jdk-1.8.0.281/man/ja/man1/rmic.1 new file mode 100755 index 0000000..1bf2417 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/rmic.1 @@ -0,0 +1,338 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: rmic +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "rmic" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +rmic \- Java Remote Method Protocol (JRMP)またはInternet Inter\-Orb protocol (IIOP)を使用するリモート・オブジェクトのスタブ、スケルトンおよびTieクラスを生成します。Object Management Group (OMG)インタフェース定義言語(IDL)も生成します +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmic\fR [ \fIoptions\fR ] \fIpackage\-qualified\-class\-names\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行\fBオプション\fR。オプションを参照してください。 +.RE +.PP +\fIpackage\-qualified\-class\-names\fR +.RS 4 +パッケージを含むクラス名。例: +\fBjava\&.awt\&.Color\fR。 +.RE +.SH "説明" +.PP +\fB非推奨に関する注意:\fR +Java Remote Method Protocol (JRMP)スタブおよびスケルトンの静的な生成のサポートは非推奨になりました。動的に生成されるJRMPスタブをかわりに使用して、JRMPベースのアプリケーションにこのツールを使用する必要性をなくすことをお薦めします。詳細は、\fBjava\&.rmi\&.server\&.UnicastRemoteObject\fR仕様(http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/server/UnicastRemoteObject\&.html)を参照してください。 +.PP +\fBrmic\fRコンパイラは、Java Remote Method Protocol (JRMP)とスタブおよびTieクラス・ファイル(IIOPプロトコル)を使用して、リモート・オブジェクトのスタブおよびスケルトン・クラス・ファイルを生成します。リモート・オブジェクトの実装クラスであるこれらのクラス・ファイルは、Javaプログラミング言語のクラスをコンパイルしたときに生成されます。リモート実装クラスは、\fBjava\&.rmi\&.Remote\fRインタフェースを実装するクラスです。\fBrmic\fRコマンドでのクラス名は、そのクラスが\fBjavac\fRコマンドでコンパイルが成功していて、かつ完全修飾パッケージ名である必要があります。たとえば、次に示すクラス・ファイル名\fBHelloImpl\fRで\fBrmic\fRコマンドを実行すると、helloサブディレクトリ(クラスのパッケージの名前の付いた)に\fBHelloImpl_Stub\&.class \fRファイルが作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmic hello\&.HelloImpl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +リモート・オブジェクトのスケルトンはJRMPプロトコル・サーバー側のエンティティで、リモート・オブジェクト実装を呼び出すメソッドを含みます。 +.PP +リモート・オブジェクトのTieは、スケルトンと同様にサーバー側のエンティティですが、IIOPプロトコルを使用してクライアントと通信します。 +.PP +スタブとは、リモート・オブジェクトのクライアント側での代理です。スタブは、リモート・オブジェクトのメソッド呼出しを、実物のリモート・オブジェクトが常駐するサーバーと通信する役割を持ちます。したがって、クライアントのリモート・オブジェクトへの参照は、実際はローカル・スタブへの参照となります。 +.PP +デフォルトで\fBrmic\fRコマンドは、1\&.2 JRMPスタブ・プロトコル・バージョンのみを使用するスタブ・クラスを生成します。これは、\fB\-v1\&.2\fRオプションを指定した場合と同じ動作です。リリース5\&.0以前では\fB\-vcompat\fRオプションがデフォルトでした。IIOPプロトコル用のスタブおよびTieクラスを生成するには\fB\-iiop\fRオプションを使用します。オプションを参照してください。 +.PP +スタブはリモート・インタフェースのみを実装し、リモート・オブジェクトが実装するローカル・インタフェースは実装していません。JRMPスタブはリモート・オブジェクトが実装するリモート・インタフェースと同じものを実装しているので、クライアントは、キャストや型チェックにJavaプログラミング言語に組み込まれた演算子を使用することができます。IIOPの場合は、\fBPortableRemoteObject\&.narrow\fRメソッドを使用する必要があります。 +.SH "オプション" +.PP +\-bootclasspath \fIpath\fR +.RS 4 +ブートストラップ・クラス・ファイルの位置をオーバーライドします。 +.RE +.PP +\-classpath path +.RS 4 +\fBrmic\fRコマンドがクラスを探すためのパスを指定します。このオプションは、デフォルトや\fBCLASSPATH\fR環境変数設定をオーバーライドします。ディレクトリはコロンで分割します。パスの一般的な形式は\fB\&.:<your_path>\fRです。例: +\fB\&.:/usr/local/java/classes\fR +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +生成されたクラス階層の出力先ディレクトリのルートを指定します。このオプションを使用すると、スタブ、スケルトン、およびTieファイルを格納するディレクトリを指定できます。たとえば、次のコマンドはMyClassから導出されたスタブおよびスケルトン・クラスをディレクトリ/java/classes/exampleclassに格納します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmic \-d /java/classes exampleclass\&.MyClass\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-d\fRオプションが指定されていない場合、デフォルトの動作は\fB\-d\fRが指定されていた場合と同じです。ターゲット・クラスのパッケージ階層が現在のディレクトリに作成され、stub/tie/skeletonファイルが格納されます。以前のリリースの\fBrmic\fRコマンドでは、\fB\-d\fRが指定されていない場合は、パッケージ階層は作成されず、出力ファイルはすべて現在のディレクトリに直接格納されていました。 +.RE +.PP +\-extdirs \fIpath\fR +.RS 4 +インストール済拡張機能の位置をオーバーライドします。 +.RE +.PP +\-g +.RS 4 +ローカル変数を含むすべてのデバッグ情報を生成します。デフォルトでは、行番号情報のみ生成されます。 +.RE +.PP +\-idl +.RS 4 +\fBrmic\fRコマンドによって、指定したクラスおよび参照されたクラスのOMG IDLが生成されます。IDLでは、プログラミング言語に依存せずに、宣言するだけでオブジェクトのAPIを指定することができます。IDLは、メソッドおよびデータの仕様として使用します。CORBAバインディングを提供する任意の言語で、メソッドおよびデータの作成および呼出しを行うことができます。これらの言語には、JavaおよびC++が含まれています。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.htmlの +「Java IDL: IDL to Java Language Mapping」を参照してください +.sp +\fB\-idl\fRオプションを使用するときには、他のオプションも指定できます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +既存のスタブ/Tie/IDLが入力クラスよりも新しい場合でも、\fB\-always\fRまたは\fB\-alwaysgenerate\fRオプションは再生成を強制します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-factory\fRオプションは、生成されたIDLで\fBfactory\fRキーワードを使用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +J\fBavaPackage[\&.class]\fR +\fBtoIDLModule\fRの\fB\-idlModule\fRは\fBIDLEntity\fRパッケージ・マッピングを指定します。例: +\fB\-idlModule\fR +\fBmy\&.module my::real::idlmod\fR +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-idlFile\fR +\fBfromJavaPackage[\&.class] toIDLFile\fRは\fBIDLEntity\fRファイル・マッピングを指定します。例: +\fB\-idlFile test\&.pkg\&.X TEST16\&.idl\fR +.RE +.RE +.PP +\-iiop +.RS 4 +\fBrmic\fRコマンドによって、JRMPのスタブとスケルトン・クラスのかわりに、IIOPのスタブとTieクラスが生成されます。スタブ・クラスは、リモート・オブジェクトのローカル・プロキシで、クライアントからサーバーに呼出しを送信するときに使用されます。各リモート・インタフェースにはスタブ・クラスが必要です。スタブ・クラスによってリモート・インタフェースが実装されます。クライアントでリモート・オブジェクトを参照するときは、スタブを参照することになります。タイ・クラスは、サーバー側で着呼を処理し、その呼出しを適切な実装クラスにディスパッチするときに使用されます。各実装クラスには、タイ・クラスが必要です。 +.sp +\fB\-iiop\fRを使用して\fBrmic\fRコマンドを呼び出すと、次の命名規則に準拠したスタブとTieが生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB_<implementationName>_stub\&.class\fR +\fB_<interfaceName>_tie\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-iiop\fRオプションを使用するときには、他のオプションも指定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +既存のスタブ/Tie/IDLが入力クラスよりも新しい場合でも、\fB\-always\fRまたは\fB\-alwaysgenerate\fRオプションは再生成を強制します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-nolocalstubs\fRオプションでは、同じプロセスのクライアントとサーバーに最適化されたスタブは作成されません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-noValueMethods\fRオプションは\fB\-idl\fRオプションとともに使用する必要があります。\fB\-noValueMethods\fRオプションは、送信されるIDLに\fBvaluetype\fRメソッドおよび初期化子を追加できないようにします。このメソッドおよび初期化子は、valuetypeの場合はオプションです。\fB\-idl\fRオプションとともに\fB\-noValueMethods\fRオプションを指定しないかぎり生成されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-poa\fRオプションは継承を\fBorg\&.omg\&.CORBA_2_3\&.portable\&.ObjectImpl\fRから\fBorg\&.omg\&.PortableServer\&.Servant\fRに変更します。ポータブル・オブジェクト・アダプタ(POA)の\fBPortableServer\fRモジュールは、ネイティブの\fBServant\fR型を定義します。Javaプログラミング言語では、\fBServant\fR型はJavaの\fBorg\&.omg\&.PortableServer\&.Servant\fRクラスにマップされます。これは、すべてのPOAサーバント実装のベース・クラスとして機能し、アプリケーション・プログラマが呼び出すことのできるいくつかのメソッド、およびPOAによって呼び出され、サーバントの動作を制御するためにユーザーがオーバーライドできるメソッドを提供します。OMG IDL to Java Language Mapping Specification、CORBA V 2\&.3\&.1 ptc/00\-01\-08\&.pdfに準拠しています。 +.RE +.RE +.PP +\-J +.RS 4 +Javaコマンドとともに使用して、\fB\-J\fRオプションは\fB\-J\fRの後ろに続く引数をJavaインタプリタに渡します(\fB\-J\fRと引数の間にスペースは入れません)。 +.RE +.PP +\-keep or \-keepgenerated +.RS 4 +スタブ、スケルトン、またはTieクラスのために生成された\fB\&.java\fRソース・ファイルを保持し、\fB\&.class\fRファイルと同じディレクトリに書き込みます。 +.RE +.PP +\-nowarn +.RS 4 +警告をオフにします。\fB\-nowarn\fRオプションが使用される場合。コンパイラは警告を表示しません。 +.RE +.PP +\-nowrite +.RS 4 +コンパイルしたクラスをファイル・システムに書き込みません。 +.RE +.PP +\-vcompat (非推奨) +.RS 4 +1\&.1と1\&.2の両方のJRMPスタブ・プロトコル・バージョンと互換性のあるスタブおよびスケルトン・クラスを作成します。5\&.0以前のリリースではこのオプションがデフォルトでした。生成されたスタブ・クラスは、JDK 1\&.1仮想マシンにロードされると1\&.1スタブ・プロトコル・バージョンを使用し、JDK 1\&.2以降の仮想マシンにロードされると1\&.2スタブ・プロトコル・バージョンを使用します。生成されたスケルトン・クラスでは、1\&.1と1\&.2の両方のスタブ・プロトコル・バージョンをサポートします。生成されたクラスは両方の操作モードをサポートするために、サイズが大きくなります。注意:このオプションは非推奨になりました。説明を参照してください。 +.RE +.PP +\-verbose +.RS 4 +コンパイラやリンカーが、コンパイルされているクラスやロードされているクラス・ファイルについてのメッセージを表示するようにします。 +.RE +.PP +\-v1\&.1 (非推奨) +.RS 4 +1\&.1 JRMPスタブ・プロトコル・バージョンのみのスタブおよびスケルトン・クラスを生成します。\fB\-v1\&.1\fRオプションを使用できるのは、JDK 1\&.1から\fBrmic\fRコマンドで生成され、アップグレードできない(さらにダイナミック・クラス・ローディングを使用していない)、既存の静的デプロイされたスタブ・クラスに対し、直列化互換性のあるスタブ・クラスを生成する場合のみです。注意:このオプションは非推奨になりました。説明を参照してください。 +.RE +.PP +\-v1\&.2 (非推奨) +.RS 4 +(デフォルト)1\&.2 JRMPスタブ・プロトコル・バージョンのみのスタブ・クラスを生成します。スケルトン・クラスは1\&.2スタブ・プロトコル・バージョンで使用できないため、スケルトン・クラスは生成されません。生成されたスタブ・クラスは、JDK 1\&.1仮想マシンにロードされても動作しません。注意:このオプションは非推奨になりました。説明を参照してください。 +.RE +.SH "環境変数" +.PP +CLASSPATH +.RS 4 +ユーザー定義クラスへのパスをシステムに指定します。ディレクトリはコロンで区切られます。例: +\fB\&.:/usr/local/java/classes\fR +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラス・パスの設定 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/rmid.1 b/jdk-1.8.0.281/man/ja/man1/rmid.1 new file mode 100755 index 0000000..bfaa24d --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/rmid.1 @@ -0,0 +1,354 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: rmid +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "rmid" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +rmid \- 起動システム・デーモンを開始すると、オブジェクトをJava Virtual Machine(VM)に登録してアクティブ化できるようになります。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +\fBrmid\fRコマンドは、起動システム・デーモンを開始します。起動システム・デーモンを開始してからでないと、アクティブ化可能オブジェクトをアクティブ化システムに登録したり、JVM内でアクティブ化したりすることができません。アクティブ化可能なオブジェクトを使用するプログラムの作成方法の詳細は、\fIアクティブ化の使用\fRに関するチュートリアル(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi/activation/overview\&.html)を参照してください +.PP +\fBrmid\fRコマンドを実行し、次のようにセキュリティ・ポリシー・ファイルを指定して、デーモンを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBrmid\fRコマンドのOracleの実装を実行する場合、デフォルトでは、セキュリティ・ポリシー・ファイルを指定する必要があります。それは、\fBrmid\fRコマンドが起動グループ用にJVMを起動するために各\fBActivationGroupDesc\fR内の情報を使用できるかどうかを検証できるようにするためです特に、\fBActivationGroupDesc\fRコンストラクタに渡される\fBCommandEnvironment\fRや任意のプロパティによって指定されるコマンドおよびオプションは、\fBrmid\fRコマンドのセキュリティ・ポリシー・ファイルの中で明示的に許可することが必要になりました。\fBsun\&.rmi\&.activation\&.execPolicy\fRプロパティの値は、起動グループ用にJVMを起動するために\fBActivationGroupDesc\fR内の情報を使用できるかどうかを判断するときに\fBrmid\fRコマンドが使用するポリシーを決定します。詳細は、\-J\-Dsun\&.rmi\&.activation\&.execPolicy=policyオプションの説明を参照してください。 +.PP +\fBrmid\fRコマンドを実行すると、デフォルト・ポート1098でアクティベータと内部レジストリが起動され、\fBActivationSystem\fRがこの内部レジストリ内の名前\fBjava\&.rmi\&.activation\&.ActivationSystem\fRにバインドされます。 +.PP +レジストリに他のポートを指定するには、\fBrmid\fRコマンドの実行時に\fB\-port\fRオプションを指定する必要があります。たとえば、次のコマンドは、レジストリのデフォルト・ポート1099で、起動システム・デーモンとレジストリを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-J\-Djava\&.security\&.policy=rmid\&.policy \-port 1099\fR + +.fi +.if n \{\ +.RE +.\} +.SH "必要に応じてRMIDを開始" +.PP +\fBrmid\fRをコマンドラインから開始するには、\fBinetd\fR(Oracle Solarisの場合)、または\fBxinetd\fR(Linuxの場合)を構成して\fBrmid\fRを必要に応じて開始する方法もあります。 +.PP +RMIDを開始すると、\fBSystem\&.inheritedChannel\fRメソッドを呼び出して、継承されたチャンネル(\fBinetd\fR/\fBxinetd\fRから継承)を取得しようとします。継承されたチャンネルがnullであるか、\fBjava\&.nio\&.channels\&.ServerSocketChannel\fRのインスタンスでなかった場合、RMIDはそのチャンネルは\fBinetd\fR/\fBxinetd\fRによって起動されたものではないと判断し、前述のように起動します。 +.PP +継承されたチャンネルが\fBServerSocketChannel\fRインスタンスである場合は、RMIDはエクスポートするリモート・オブジェクト、つまり\fBjava\&.rmi\&.activation\&.ActivationSystem\fRがバインドされているレジストリと\fBjava\&.rmi\&.activation\&.Activator\fRリモート・オブジェクトに対するリクエストを受信するサーバー・ソケットとして、\fBServerSocketChannel\fRから取得した\fBjava\&.net\&.ServerSocket\fRを使用します。このモードでは、RMIDの動作は、次のことを除いて、コマンドラインから起動した場合と同じです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSystem\&.err\fRに対する出力は、ファイルにリダイレクトされる。このファイルは\fBjava\&.io\&.tmpdir\fRシステム・プロパティで指定されるディレクトリ(通常は\fB/var/tmp\fRまたは\fB/tmp\fR)にある。ファイル名の接頭辞は\fBrmid\-err\fRで、接尾辞は\fBtmp\fRである。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-port\fRオプションは使用できません。このオプションが指定されている場合、RMIDはエラー・メッセージが表示されて終了します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-log\fRオプションは必須。このオプションが指定されていない場合、RMIDはエラー・メッセージが表示されて終了します。 +.RE +.PP +必要に応じてサービスを開始するように構成する方法の詳細は、\fBinetd\fR +(Oracle Solarisの場合)、または\fBxinetd\fR +(Linux)のマニュアル・ページを参照してください。 +.SH "オプション" +.PP +\-C\fIオプション\fR +.RS 4 +\fBrmid\fRコマンドの子プロセス(起動グループ)が作成されたときに、それぞれの子プロセスにコマンド行引数として渡されるオプションを指定します。たとえば、次のように指定すると、起動システム・デーモンによって生成される各仮想マシンにプロパティを渡すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-C\-Dsome\&.property=value\fR + +.fi +.if n \{\ +.RE +.\} +コマンド行引数を子プロセスに渡す機能は、デバッグを行う場合に便利です。たとえば、次のコマンドでは、すべての子JVMでserver\-callロギングが可能です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-C\-Djava\&.rmi\&.server\&.logCalls=true\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\fIoption\fR +.RS 4 +RMIDを実行しているJavaインタプリタに渡すオプションを指定します。たとえば、\fBrmid\fRコマンドが\fBrmid\&.policy\fRという名前のポリシー・ファイルを使用するように指定するには、\fBrmid\fRのコマンド行で\fB\-J\fRオプションを使用して、\fBjava\&.security\&.policy\fRプロパティを定義します。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-J\-Djava\&.security\&.policy\-rmid\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\-Dsun\&.rmi\&.activation\&.execPolicy=\fIpolicy\fR +.RS 4 +起動グループが実行されることになるJVMの起動に使用するコマンドおよびコマンド行オプションをチェックするために、RMIDが採用するポリシーを指定します。このオプションは、Java RMI起動デーモンのOracleの実装のみに存在することに注意してください。コマンド行にこのプロパティを指定しない場合、結果は\fB\-J\-Dsun\&.rmi\&.activation\&.execPolicy=default\fRを指定した場合と同じになります。\fBpolicy\fRに指定可能な値は、\fBdefault\fR、\fBpolicyClassName\fRまたは\fBnone\fRです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +デフォルト +.sp +\fBdefault\fRまたは未指定値の\fBexecPolicy\fRの場合、\fBrmid\fRコマンドが実行できるのは、\fBrmid\fRコマンドが使用するセキュリティ・ポリシー・ファイルの中で、実行する権限が\fBrmid\fRに与えられているコマンドおよびコマンド行オプションのみです。デフォルトの実行ポリシーで使用できるのは、デフォルトの起動グループ実装のみです。 +.sp +\fBrmid\fRコマンドは、起動グループ用のJVMを起動するときに、そのグループについて登録された起動グループ記述子である\fBActivationGroupDesc\fR内の情報を使用します。グループ記述子は、\fBActivationGroupDesc\&.CommandEnvironment\fRを指定します(省略可能)。これには、起動グループを開始するコマンドと、そのコマンド行に追加できるコマンド行オプションが含まれています。デフォルトでは、\fBrmid\fRコマンドは\fBjava\&.home\fRにある\fBjava\fRコマンドを使用します。グループ記述子には、コマンド行にオプションとして追加されるプロパティ・オーバーライドも含まれます(\fB\-D<property>=<value>\fRとして定義されます)。\fBcom\&.sun\&.rmi\&.rmid\&.ExecPermission\fR権限は\fBrmid\fRコマンドに、起動グループを開始するためにグループ記述子の\fBCommandEnvironment\fRで指定されたコマンドを実行する権限を付与します。\fBcom\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR権限は起動グループの開始時に、グループ記述子でプロパティ・オーバーライドとして、または\fBCommandEnvironment\fRでオプションとして指定されたコマンド行オプションを、\fBrmid\fRコマンドが使用することを許可します。\fBrmid\fRコマンドに様々なコマンドおよびオプションを実行する権限を付与する場合、権限\fBExecPermission\fRおよび\fBExecOptionPermission\fRをすべてのコード・ソースに付与する必要があります。 +.sp +\fBExecPermission\fR +.sp +\fBExecPermission\fRクラスは、起動グループを開始するために\fBrmid\fRコマンドが特定のコマンドを実行する権限を表します。 +.sp +\fB構文\fR: +\fBExecPermission\fRの名前は、\fBrmid\fRコマンドに実行を許可するコマンドのパス名です。スラッシュ(/)およびアスタリスク(*)で終わるパス名は、そのディレクトリに含まれるすべてのファイルを示します。スラッシュはファイル区切り文字\fBFile\&.separatorChar\fRです。スラッシュ(/)およびマイナス符号(\-)で終わるパス名は、そのディレクトリに含まれるすべてのファイルとサブディレクトリ(再帰的に)を示します。特殊なトークン\fB<<ALL FILES>>\fRで構成されるパス名は、どのファイルとも一致します。 +.sp +パス名にアスタリスク(*)を指定した場合は、現在のディレクトリ内のすべてのファイルを示します。パス名にマイナス符号(\-)を指定した場合は、現在のディレクトリ内のすべてのファイルおよび(再帰的に)現在のディレクトリに含まれるすべてのファイルとサブディレクトリを示します。 +.sp +\fBExecOptionPermission\fR +.sp +\fBExecOptionPermission\fRクラスは、起動グループを開始するときに\fBrmid\fRコマンドで特定のコマンド行オプションを使用できる権限を表します。\fBExecOptionPermission\fRの名前は、コマンド行オプションの値です。 +.sp +\fB構文\fR: オプションでは、ワイルドカードが限定的にサポートされます。アスタリスクは、ワイルドカード・マッチを表します。アスタリスク(*)は、オプション名そのものとして使用できます。つまり、任意のオプションを表すことができます。また、オプション名の末尾に使用することもできます。ただし、ドット(\&.)か等号(=)の直後にアスタリスク(*)を指定する必要があります。 +.sp +例: +\fB*\fRや\fB\-Dmydir\&.*\fRや\fB\-Da\&.b\&.c=*\fRは有効ですが、\fB*mydir\fRや\fB\-Da*b\fRや\fBab*\fRは無効です。 +.sp +\fBrmidのポリシー・ファイル\fR +.sp +\fBrmid\fRコマンドに様々なコマンドおよびオプションを実行する権限を許可する場合は、権限\fBExecPermission\fRおよび\fBExecOptionPermission\fRをすべてのコード・ソースに付与する必要があります(汎用的に)。これらの権限をチェックするのは\fBrmid\fRコマンドのみなので、これらの権限を汎用的に付与しても安全です。 +.sp +\fBrmid\fRコマンドに各種の実行権限を付与するポリシー・ファイルの例を、次に示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBgrant {\fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR +\fB "/files/apps/java/jdk1\&.7\&.0/solaris/bin/java";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR +\fB "/files/apps/rmidcmds/*";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR +\fB "\-Djava\&.security\&.policy=/files/policies/group\&.policy";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR +\fB "\-Djava\&.security\&.debug=*";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR +\fB "\-Dsun\&.rmi\&.*";\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +最初に付与されている権限は、\fBrmid\fRコマンドに対し、パス名により明示的に指定される\fBjava\fRコマンドの1\&.7\&.0リリースの実行を許可します。デフォルトでは、\fBjava\&.home\fRにあるバージョンの\fBjava\fRコマンドを使用します。\fBrmid\fRコマンドが使用するのと同じバージョンが使用されるため、そのコマンドは、ポリシー・ファイルで指定する必要はありません。2番目の権限は、\fBrmid\fRコマンドに対して、ディレクトリ\fB/files/apps/rmidcmds\fR内の任意のコマンドの実行権限を許可します。 +.sp +3番目に付与されている権限\fBExecOptionPermission\fRは、\fBrmid\fRコマンドに対して、セキュリティ・ポリシー・ファイルを\fB/files/policies/group\&.policy\fRとして定義している起動グループの開始を許可します。次の権限は、起動グループが\fBjava\&.security\&.debug property\fRを使用することを許可しています。最後の権限は、起動グループが\fBsun\&.rmi property\fR名の階層内の任意のプロパティを使用することを許可しています。 +.sp +ポリシー・ファイルを指定して\fBrmid\fRコマンドを起動するには、\fBrmid\fRのコマンド行で\fBjava\&.security\&.policy\fRプロパティを指定する必要があります。次に例を示します。 +.sp +\fBrmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fR\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +<policyClassName> +.sp +デフォルトの動作では十分な柔軟性が得られない場合、管理者は、\fBrmid\fRの起動時に、\fBcheckExecCommand\fRメソッドが所属するクラスの名前を指定して、\fBrmid\fRコマンドが実行するコマンドをチェックすることができます。 +.sp +\fBpolicyClassName\fRには、引数なしのコンストラクタを持ち、次のような\fBcheckExecCommand\fRメソッドを実装しているpublicクラスを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB public void checkExecCommand(ActivationGroupDesc desc, String[] command)\fR +\fB throws SecurityException;\fR + +.fi +.if n \{\ +.RE +.\} +起動グループを開始する前に、\fBrmid\fRコマンドは、ポリシーの\fBcheckExecCommand\fRメソッドを呼び出します。このとき、起動グループの記述子と、起動グループを開始するための完全なコマンドを含む配列をそのメソッドに渡します。\fBcheckExecCommand\fRが\fBSecurityException\fRをスローすると、\fBrmid\fRコマンドはその起動グループを開始せず、オブジェクトの起動を試行している呼出し側には\fBActivationException\fRがスローされます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +none +.sp +\fBsun\&.rmi\&.activation\&.execPolicy\fRプロパティの値が\fBnone\fRの場合、\fBrmid\fRコマンドは、起動グループを開始するコマンドをまったく検証しません。 +.RE +.RE +.PP +\-log \fIdir\fR +.RS 4 +起動システム・デーモンがデータベースおよび関連情報を書き込むのに使用するディレクトリの名前を指定します。デフォルトでは、\fBrmid\fRコマンドを実行したディレクトリに、logというログ・ディレクトリが作成されます。 +.RE +.PP +\-port \fIport\fR +.RS 4 +レジストリが使用するポートを指定します。起動システム・デーモンは、このレジストリの中で、\fBjava\&.rmi\&.activation\&.ActivationSystem\fRという名前で\fBActivationSystem\fRをバインドします。ローカル・マシン上の\fBActivationSystem\fRは、次のように\fBNaming\&.lookup\fRメソッドを呼び出すことによって取得できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.rmi\&.*; \fR +\fB import java\&.rmi\&.activation\&.*;\fR +\fB \fR +\fB ActivationSystem system; system = (ActivationSystem)\fR +\fB Naming\&.lookup("//:port/java\&.rmi\&.activation\&.ActivationSystem");\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-stop +.RS 4 +\fB\-port\fRオプションによって指定されたポートの、現在の\fBrmid\fRコマンドの呼出しを停止します。ポートが指定されていない場合は、このオプションはポート1098で実行されている\fBrmid\fRの呼出しを停止します。 +.RE +.SH "環境変数" +.PP +CLASSPATH +.RS 4 +ユーザー定義クラスへのパスをシステムに指定します。ディレクトリはコロンで区切られます。例: +\fB\&.:/usr/local/java/classes\fR +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラス・パスの設定 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/rmiregistry.1 b/jdk-1.8.0.281/man/ja/man1/rmiregistry.1 new file mode 100755 index 0000000..781645e --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/rmiregistry.1 @@ -0,0 +1,116 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: rmiregistry +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "rmiregistry" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +rmiregistry \- 現在のホストの指定したポート上にリモート・オブジェクト・レジストリを開始します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry\fR [ \fIport\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIport\fR +.RS 4 +リモート・オブジェクト・レジストリを開始する現在のホスト上の\fBport\fRの数。 +.RE +.SH "説明" +.PP +\fBrmiregistry\fRコマンドは、現在のホストの指定したポート上にリモート・オブジェクト・レジストリを作成し、開始します。portの指定を省略した場合、レジストリはポート1099で開始します。\fBrmiregistry\fRコマンドに、出力機能はありません。通常、これはバックグラウンドで実行されます。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry &\fR + +.fi +.if n \{\ +.RE +.\} +.PP +リモート・オブジェクト・レジストリは、ブートストラップのネーム・サービスです。同一ホストのRMIサーバーが、リモート・オブジェクトを名前にバインドするために使用されます。次に、ローカルおよびリモート・ホストのクライアントはリモート・オブジェクトを検索し、リモート・メソッドの呼出しを行います。 +.PP +レジストリは、一般的に、最初のリモート・オブジェクトの位置を指定します。そこで、アプリケーションはメソッドを呼び出す必要があります。その後、そのオブジェクトはアプリケーション指定のサポートを提供し、他のオブジェクトを探します。 +.PP +\fBjava\&.rmi\&.registry\&.LocateRegistry\fRクラスのメソッドは、ローカル・ホスト、またはローカル・ホストとポートで動作するレジストリを取得するために使用されます。 +.PP +\fBjava\&.rmi\&.Naming\fRクラスのURLベース・メソッドはレジストリに対して操作を実行し、任意のホストおよびローカル・ホストでのリモート・オブジェクトの検索に使用できます。単純名(文字列)をリモート・オブジェクトにバインドし、新しい名前をリモート・オブジェクトに再バインドし(古いバインドをオーバーライド)、リモート・オブジェクトをアンバインドし、レジストリにバインドされているURLをリスト表示します。 +.SH "オプション" +.PP +\-J +.RS 4 +Javaオプションとともに使用して、\fB\-J\fRの後ろに続くオプションをJavaインタプリタに引き渡します(\fB\-J\fRとオプションの間にスペースは入れません)。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB「java\&.rmi\&.registry\&.LocateRegistry」\fR(http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/registry/LocateRegistry\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB「java\&.rmi\&.Naming class description」\fR(http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/Naming\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/schemagen.1 b/jdk-1.8.0.281/man/ja/man1/schemagen.1 new file mode 100755 index 0000000..a79ddbc --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/schemagen.1 @@ -0,0 +1,142 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: schemagen +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "schemagen" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +schemagen \- Javaクラス内で参照されているネームスペースごとにスキーマを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBschemagen\fR [ \fIoptions\fR ] \fIjava\-files\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIjava\-files\fR +.RS 4 +処理するJavaクラス・ファイル。 +.RE +.SH "説明" +.PP +スキーマ・ジェネレータは、Javaクラス内で参照されているネームスペースごとに1つのスキーマ・ファイルを作成します。現在、生成されるスキーマ・ファイルの名前は制御できません。スキーマ・ファイル名を制御する場合は、http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/schemagenTask\&.htmlにある +「Using SchemaGen with Ant」を参照してください +.PP +プラットフォームのbinディレクトリにある適切な\fBschemagen\fRシェル・スクリプトを使用して、スキーマ・ジェネレータを起動します。現在のスキーマ・ジェネレータは、Javaソース・ファイルとクラス・ファイルのいずれも処理できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBschemagen\&.sh Foo\&.java Bar\&.java \&.\&.\&.\fR +\fBNote: Writing schema1\&.xsd\fR + +.fi +.if n \{\ +.RE +.\} +.PP +javaファイルが他のクラスを参照している場合、それらのクラスにシステム\fBCLASSPATH\fR環境変数でアクセスできる必要があります。または、クラス・パス・オプションを指定して\fBschemagen\fRコマンド行で指定する必要があります。オプションを参照してください。参照されるファイルにアクセスできない、または参照されるファイルが指定されていない場合、スキーマの生成時にエラーが表示されます。 +.SH "オプション" +.PP +\-d \fIpath\fR +.RS 4 +\fBschemagen\fRコマンドがプロセッサ生成および\fBjavac\fR生成クラス・ファイルを配置する場所。 +.RE +.PP +\-cp \fIpath\fR +.RS 4 +\fBschemagen\fRコマンドがユーザー指定ファイルを配置する場所。 +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +\fBschemagen\fRコマンドがユーザー指定ファイルを配置する場所。 +.RE +.PP +\-encoding \fIencoding\fR +.RS 4 +\fBapt\fRまたは\fBjavac\fRコマンドの呼出しに使用するエンコーディングを指定します。 +.RE +.PP +\-episode \fIfile\fR +.RS 4 +コンパイルごとにエピソード・ファイルを生成します。 +.RE +.PP +\-version +.RS 4 +リリース情報を表示します。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Using SchemaGen with Ant + +(http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/schemagenTask\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java Architecture for XML Binding (JAXB) + +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/xml/jaxb/index\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/serialver.1 b/jdk-1.8.0.281/man/ja/man1/serialver.1 new file mode 100755 index 0000000..469515d --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/serialver.1 @@ -0,0 +1,129 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: serialver +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "serialver" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +serialver \- 指定したクラスのシリアル・バージョンUIDを戻します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBserialver\fR [ \fIoptions\fR ] [ \fIclassnames\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclassnames\fR +.RS 4 +\fBserialVersionUID\fRを戻すクラスです。 +.RE +.SH "説明" +.PP +\fBserialver\fRコマンドは、1つ以上のクラスの\fBserialVersionUID\fRを、展開しているクラスへコピーするのに適した形式で返します。引数なしで呼び出された場合、\fBserialver\fRコマンドは使用率行を出力します。 +.SH "オプション" +.PP +\-classpath \fIpath\-files\fR +.RS 4 +アプリケーションのクラスおよびリソースの検索パスを設定します。クラスとリソースをコロン(:)で区切ります。 +.RE +.PP +\-show +.RS 4 +簡単なユーザー・インタフェースを表示します。完全指定のクラス名を入力して、Enterキーか「表示」ボタンを押し、\fBserialVersionUID\fRを表示します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "注意" +.PP +\fBserialver\fRコマンドは、指定されたクラスをその仮想マシン内に読み込んで初期化しますが、デフォルトではセキュリティ・マネージャの設定は行いません。信頼できないクラスとともに\fBserialver\fRコマンドを実行する場合には、次のオプションを使用してセキュリティ・マネージャを設定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-J\-Djava\&.security\&.manager\fR + +.fi +.if n \{\ +.RE +.\} +.PP +必要であれば、次のオプションを使用してセキュリティ・ポリシーを指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-J\-Djava\&.security\&.policy=<policy file>\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +policytool(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/api/java/io/ObjectStreamClass\&.htmlにある +\fBjava\&.io\&.ObjectStream\fRクラス記述 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/servertool.1 b/jdk-1.8.0.281/man/ja/man1/servertool.1 new file mode 100755 index 0000000..bdcb783 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/servertool.1 @@ -0,0 +1,182 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: servertool +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "servertool" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +servertool \- 開発者が永続サーバーを登録、登録解除、起動、停止するための使いやすいユーザー・インタフェースを提供します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBservertool\fR \-ORBInitialPort \fInameserverport\fR [ \fIoptions\fR ] [ \fIcommands \fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +commands +.RS 4 +コマンド行コマンド。コマンドを参照してください。 +.RE +.PP +\fBservertool\fR\fBservertool >\fR\fBservertool >\fR +.SH "説明" +.PP +\fBservertool\fRコマンドは、開発者が永続サーバーを登録、登録解除、起動、停止するためのコマンド行インタフェースを提供します。コマンド行コマンドを使用すると、サーバーに関する様々な統計情報を取得できます。コマンドを参照してください。 +.SH "オプション" +.PP +\-ORBInitialHost \fInameserverhost\fR +.RS 4 +このオプションは必須です。ネーム・サーバーが実行され、着信リクエストをリスニングするホスト・マシンを指定します。\fBnameserverhost\fR値は、\fBorb\fRが実行され、リクエストをリスニングしているポートを指定する必要があります。このオプションを指定しない場合、値はデフォルトで\fBlocalhost\fRに設定されます。\fBorbd\fRと\fBservertool\fRが異なるマシン上で実行されている場合は、\fBorbd\fRが実行されているホストの名前またはIPアドレスを指定する必要があります。 +.sp +\fB注意:\fR +Oracle Solarisでは、1024より小さいポート上でプロセスを開始するには、rootユーザーになる必要があります。\fBnameserverport\fR値には、1024以上のポート番号を使用することをお薦めします。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "コマンド" +.PP +\fBservertool\fRコマンドは、コマンド行コマンドを使用して、または使用せずに起動できます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBservertool\fRの起動時にコマンドを指定しなかった場合、コマンド行ツールにコマンド入力を求める\fBservertool\fRプロンプトが表示されます: +\fBservertool >\fR。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBservertool\fRの起動時にコマンドを指定した場合、Java IDL Server Toolが起動してコマンドを実行し、終了します。 +.RE +.PP +register \-server \fIserver\-class\-name\fR \-classpath \fIclasspath\-to\-server\fR [ \-applicationName \fIapplication\-name\fR \-args \fIargs\-to\-server\fR \-vmargs \fIflags\-for\-JVM\fR ] +.RS 4 +Object Request Broker Daemon (ORBD)に新規永続サーバーを登録します。サーバーが未登録の場合、登録してアクティブ化します。このコマンドによって、\fB\-server\fRオプションで識別されるサーバーの\fBメイン\fR・クラス内でインストール・メソッドが呼び出されます。このインストール・メソッドは、\fBpublic static void install(org\&.omg\&.CORBA\&.ORB)\fRになっている必要があります。インストール・メソッドはオプションであり、開発者はデータベース・スキーマの作成など独自のサーバー・インストール動作を指定できます。 +.RE +.PP +unregister \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR +.RS 4 +サーバーIDまたはアプリケーション名で、サーバーをORBDから登録解除します。このコマンドによって、\fB\-server\fRオプションで識別されるサーバーの\fBメイン\fR・クラス内でアンインストール・メソッドが呼び出されます。 +\fBuninstall\fRメソッドは、\fBpublic static void uninstall(org\&.omg\&.CORBA\&.ORB)\fRになっている必要があります。\fBuninstall\fRメソッドはオプションであり、開発者は\fBinstall\fRメソッドの動作の取消など、独自のサーバー・アンインストール動作を指定できます。 +.RE +.PP +getserverid \-applicationName \fIapplication\-name\fR +.RS 4 +\fBapplication\-name\fR値に対応するサーバーIDを返します。 +.RE +.PP +list +.RS 4 +ORBDに登録されているすべての永続サーバーに関する情報を一覧表示します。 +.RE +.PP +listappnames +.RS 4 +現在ORBDに登録されているすべてのサーバーのアプリケーション名を一覧表示します。 +.RE +.PP +listactive +.RS 4 +ORBDによって起動され、現在実行されているすべての永続サーバーに関する情報を一覧表示します。 +.RE +.PP +locate \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR [ \-endpointType \fIendpointType\fR ] +.RS 4 +登録されたサーバーで作成したすべてのORBの特定のタイプについてエンドポイント(ポート)を検出します。サーバーが実行されていない場合、アクティブ化されます。\fBendpointType\fR値が指定されていない場合、サーバーのORBごとに関連付けられているplainタイプまたはnon\-protectedタイプのエンドポイントが返されます。 +.RE +.PP +locateperorb \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR [ \-orbid \fIORB\-name\fR ] +.RS 4 +登録されたサーバーの特定のObject Request Broker (ORB)で登録されたエンドポイント(ポート)を検出します。サーバーが実行されていない場合、アクティブ化されます。\fBorbid\fRが指定されていない場合、デフォルト値の\fB""\fRが\fBorbid\fRに割り当てられます。ORBが空文字列の\fBorbid\fRで作成されている場合、登録したポートがすべて返されます。 +.RE +.PP +orblist \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR +.RS 4 +サーバー上に定義されたORBの\fBORBId\fRを一覧表示します。\fBORBId\fRはサーバーで作成されたORBの文字列名です。サーバーが実行されていない場合、アクティブ化されます。 +.RE +.PP +shutdown \-serverid \fIserver\-id\fR | \-applicationName application\-name +.RS 4 +ORBDに登録されたアクティブなサーバーを停止します。このコマンドの実行中に、\fB\-serverid\fRパラメータまたは\fB\-applicationName\fRパラメータで指定されたクラス内に定義された\fBshutdown\fRメソッドも呼び出されてサーバー・プロセスを停止します。 +.RE +.PP +startup \-serverid \fIserver\-id\fR | \-applicationName application\-name +.RS 4 +ORBDに登録されたサーバーを起動またはアクティブ化します。サーバーが実行されていない場合、このコマンドがサーバーを起動します。サーバーがすでに実行されている場合は、エラー・メッセージが表示されます。 +.RE +.PP +help +.RS 4 +\fBservertool\fRコマンドを介してサーバーが利用できるすべてのコマンドをリストします。 +.RE +.PP +quit +.RS 4 +\fBservertool\fRコマンドを終了します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +orbd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/tnameserv.1 b/jdk-1.8.0.281/man/ja/man1/tnameserv.1 new file mode 100755 index 0000000..20e104c --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/tnameserv.1 @@ -0,0 +1,427 @@ +'\" t +.\" Copyright (c) 1999, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: tnameserv +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "tnameserv" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +tnameserv \- インタフェース定義言語(IDL)。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserve\fR \fB\-ORBInitialPort\fR [ \fInameserverport\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\-ORBInitialPort \fInameserverport\fR +.RS 4 +ネーミング・サービスがORBの\fBresolve_initial_references\fRメソッドと\fBlist_initial_references\fRメソッドの実装に使用するブートストラップ・プロトコルをリスニングする初期ポートです。 +.RE +.SH "説明" +.PP +Java IDLには、Object Request Broker Daemon (ORBD)が含まれます。ORBDは、ブートストラップ・サービス、一時ネーミング・サービス、永続ネーミング・サービスおよびサーバー・マネージャを含むデーモン・プロセスです。Java IDLのすべてのチュートリアルではORBDを使用していますが、一時ネーミング・サービスを使用する例では、\fBorbd\fRのかわりに\fBtnameserv\fRを使用できます。 +.PP +orbd(1)http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html +にあるまたは「Naming Service」を参照してください。 +.PP +CORBAのCOS (Common Object Services)ネーミング・サービスは、ファイル・システムがファイルに対してディレクトリ構造を提供しているのと同じように、オブジェクト参照に対してツリー構造のディレクトリを提供します。Java IDLの一時ネーム・サービスである\fBtnameserv\fRは、COSネーム・サービスの仕様を単純な形で実装したものです。 +.PP +オブジェクト参照はネームスペースに名前で格納され、オブジェクト参照と名前のペアは、それぞれネーム・バインディングと呼ばれます。ネーム・バインディングはネーミング・コンテキストに組み込むことができます。ネーミング・コンテキストはネーム・バインディングであり、ファイル・システムのサブディレクトリと同じ編成機能を持ちます。すべてのバインディングは初期ネーミング・コンテキストの下に格納されます。初期ネーミング・コンテキストは、ネームスペースの唯一の永続バインディングです。Java IDLネーミング・サービス・プロセスを停止して再起動すると、残りのネームスペースは失われます。 +.PP +アプレットまたはアプリケーションからCOSネーミング・サービスを使用するためには、そのORBがネーミング・サービスが動作しているホストのポートを知っているか、そのネーミング・サービスの初期ネーミング・コンテキスト文字列にアクセスできる必要があります。ネーム・サービスは、Java IDLのネーム・サービスでもその他のCOS準拠のネーム・サービスでもかまいません。 +.SS "ネーミング・サービスの起動" +.PP +Java IDLネーム・サービスは、ネーム・サービスを使用するアプリケーションまたはアプレットより前に起動しておく必要があります。Java IDL製品をインストールすると、Java IDLネーミング・サービスを起動するスクリプト(Oracle Solaris: +\fBtnameserv\fR)または実行可能ファイル(Windows: +\fBtnameserv\&.exe\fR)が作成されます。バックグラウンドで動作するように、ネーム・サービスを起動してください。 +.PP +特に指定しない場合、Java IDLネーミング・サービスは、ORBの\fBresolve_initial_references\fRメソッドと\fBlist_initial_references methods\fRメソッドの実装に使用するブートストラップ・プロトコルに対してポート900でリスニングします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserv \-ORBInitialPort nameserverport&\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーム・サーバー・ポートを指定しない場合、デフォルトでポート900が使用されます。Oracle Solarisソフトウェアの実行時、1024より小さいポートでプロセスを開始する場合は、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。1050のように別のポートを指定し、ネーム・サービスをバックグラウンドで実行するには、Solaris、LinuxまたはOS Xコマンド・シェルで次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserv \-ORBInitialPort 1050&\fR + +.fi +.if n \{\ +.RE +.\} +.PP +WindowsのMS\-DOSシステム・プロンプトでは、次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBstart tnameserv \-ORBInitialPort 1050\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーム・サーバーのクライアントには、新しいポート番号を知らせる必要があります。これを行うには、ORBオブジェクトの作成時に\fBorg\&.omg\&.CORBA\&.ORBInitialPort\fRプロパティに新しいポート番号を設定します。 +.SS "異なるホスト上でのサーバーとクライアントの実行" +.PP +Java IDLとRMI\-IIOPのほとんどのチュートリアルでは、ネーミング・サービス、サーバーおよびクライアントはすべて開発用のマシン上で実行されます。実際にデプロイメントする場合には、クライアントとサーバーを、ネーミング・サービスとは異なるホスト・マシン上で実行することが多くなります。 +.PP +クライアントとサーバーがネーム・サービスを見つけるには、クライアントとサーバーが、ネーム・サービスが実行されているポートの番号とホストを認識している必要があります。そのためには、クライアントとサーバーのファイル内の\fBorg\&.omg\&.CORBA\&.ORBInitialPort\fRプロパティと\fBorg\&.omg\&.CORBA\&.ORBInitialHost\fRプロパティをネーム・サービスが実行されているポートの番号とマシンの名前に設定します。この例は、「Getting Started Using RMI\-IIOP」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi\-iiop/rmiiiopexample\&.html)に示されています +.PP +コマンド行オプション\fB\-ORBInitialPort nameserverport#\fRと\fB\-ORBInitialHost nameserverhostname\fRを使用して、クライアントとサーバーに対してネーミング・サービスを探す場所を指定することもできます。コマンド行オプションを使用してこれを行う方法の1つの例は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/tutorial/jidl2machines\&.htmlの「Java IDL: The Hello World Example on Two Machines」 +を参照してください +.PP +たとえば、一時ネーム・サービス\fBtnameserv\fRが、ホスト\fBnameserverhost\fRのポート1050上で実行されているとします。さらに、クライアントがホスト\fBclienthost\fR上で実行され、サーバーはホスト\fBserverhost\fR上で実行されているとします。 +.PP +ホスト\fBnameserverhost\fR上で\fBtnameserv\fRを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserv \-ORBInitialPort 1050\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBserverhost\fR上でサーバーを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava Server \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fR + +.fi +.if n \{\ +.RE +.\} +.PP + +\fBclienthost\fR上でクライアントを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava Client \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fR + +.fi +.if n \{\ +.RE +.\} +.SS "ネーミング・サービスの停止" +.PP +Java IDLネーミング・サービスを停止するには、Solaris、LinuxまたはOS Xの場合は、\fBkill\fRなどのオペレーティング・システムのコマンドを使用し、Windowsの場合は、\fB[Ctrl]+[C]\fRキーを使用します。ネーミング・サービスを明示的に停止するまでは、呼出し待機状態が続きます。サービスを終了させると、Java IDLネーム・サービスに登録されている名前は失われます。 +.SH "オプション" +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "例" +.SS "ネームスペースへのオブジェクトの追加" +.PP +次の例では、ネームスペースに名前を追加する方法を示します。このサンプル・プログラムは、このままの状態で完全に動作する一時ネーム・サービス・クライアントで、次のような単純なツリーを作成するものです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBInitial Naming Context\fR +\fB plans\fR +\fB Personal\fR +\fB calendar\fR +\fB schedule\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例で、\fBplans\fRはオブジェクト参照、\fBPersonal\fRは\fBcalendar\fRと\fBschedule\fRの2つのオブジェクト参照を含むネーミング・コンテキストです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.util\&.Properties;\fR +\fBimport org\&.omg\&.CORBA\&.*;\fR +\fBimport org\&.omg\&.CosNaming\&.*;\fR +\fB \fR +\fBpublic class NameClient {\fR + +\fB public static void main(String args[]) {\fR + +\fB try {\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーミング・サービスの起動で、\fBnameserver\fRはポート1050で起動されました。次のコードで、このポート番号をクライアント・システムに知らせます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB Properties props = new Properties();\fR +\fB props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fR +\fB ORB orb = ORB\&.init(args, props);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、初期ネーミング・コンテキストを取得し、それを\fBctx\fRに代入します。2行目では、\fBctx\fRをダミーのオブジェクト参照\fBobjref\fRにコピーします。このobjrefには、あとで様々な名前を割り当ててネームスペースに追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NamingContext ctx =\fR +\fB NamingContextHelper\&.narrow(\fR +\fB orb\&.resolve_initial_references("NameService"));\fR +\fB NamingContext objref = ctx;\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、\fBtext\fRタイプの名前\fBplans\fRを作成し、それをダミーのオブジェクト参照にバインドします。その後、\fBrebind\fRメソッドを使用して初期ネーミング・コンテキストの下に\fBplans\fRを追加しています。\fBrebind\fRメソッドを使用すれば、\fBbind\fRメソッドを使用した場合に発生する例外を発生させずに、このプログラムを何度も繰返し実行できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NameComponent nc1 = new NameComponent("plans", "text");\fR +\fB NameComponent[] name1 = {nc1};\fR +\fB ctx\&.rebind(name1, objref);\fR +\fB System\&.out\&.println("plans rebind successful!");\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、\fBdirectory\fRタイプの\fBPersonal\fRというネーミング・コンテキストを作成します。その結果得られるオブジェクト参照\fBctx2\fRを\fBname\fRにバインドし、初期ネーミング・コンテキストに追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NameComponent nc2 = new NameComponent("Personal", "directory");\fR +\fB NameComponent[] name2 = {nc2};\fR +\fB NamingContext ctx2 = ctx\&.bind_new_context(name2);\fR +\fB System\&.out\&.println("new naming context added\&.\&.");\fR + +.fi +.if n \{\ +.RE +.\} +.PP +残りのコードでは、ダミーのオブジェクト参照を\fBschedule\fRと\fBcalendar\fRという名前でネーミング・コンテキスト\fBPersonal\fR(\fBctx2\fR)にバインドします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NameComponent nc3 = new NameComponent("schedule", "text");\fR +\fB NameComponent[] name3 = {nc3};\fR +\fB ctx2\&.rebind(name3, objref);\fR +\fB System\&.out\&.println("schedule rebind successful!");\fR +\fB \fR +\fB NameComponent nc4 = new NameComponent("calender", "text");\fR +\fB NameComponent[] name4 = {nc4};\fR +\fB ctx2\&.rebind(name4, objref);\fR +\fB System\&.out\&.println("calender rebind successful!");\fR +\fB } catch (Exception e) {\fR +\fB e\&.printStackTrace(System\&.err);\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SS "ネームスペースの参照" +.PP +次のサンプル・プログラムでは、ネームスペースをブラウズする方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.util\&.Properties;\fR +\fBimport org\&.omg\&.CORBA\&.*;\fR +\fBimport org\&.omg\&.CosNaming\&.*;\fR +\fB \fR +\fBpublic class NameClientList {\fR + +\fB public static void main(String args[]) {\fR + +\fB try {\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーミング・サービスの起動で、\fBnameserver\fRはポート1050で起動されました。次のコードで、このポート番号をクライアント・システムに知らせます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB Properties props = new Properties();\fR +\fB props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fR +\fB ORB orb = ORB\&.init(args, props);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、初期ネーミング・コンテキストを取得しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NamingContext nc =\fR +\fB NamingContextHelper\&.narrow(\fR +\fB orb\&.resolve_initial_references("NameService"));\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBlist\fRメソッドは、ネーミング・コンテキストのバインディングをリストします。この場合、最大1000個までのバインディングが初期ネーミング・コンテキストから\fBBindingListHolder\fRに返されます。残りのバインディングは、\fBBindingIteratorHolder\fRに返されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB BindingListHolder bl = new BindingListHolder();\fR +\fB BindingIteratorHolder blIt= new BindingIteratorHolder();\fR +\fB nc\&.list(1000, bl, blIt);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、返された\fBBindingListHolder\fRからバインディングの配列を取得します。バインディングがない場合は、プログラムが終了します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB Binding bindings[] = bl\&.value;\fR +\fB if (bindings\&.length == 0) return;\fR + +.fi +.if n \{\ +.RE +.\} +.PP +残りのコードでは、バインディングに対してループ処理を行い、名前を出力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB for (int i=0; i < bindings\&.length; i++) {\fR +\fB \fR +\fB // get the object reference for each binding\fR +\fB org\&.omg\&.CORBA\&.Object obj = nc\&.resolve(bindings[i]\&.binding_name);\fR +\fB String objStr = orb\&.object_to_string(obj);\fR +\fB int lastIx = bindings[i]\&.binding_name\&.length\-1;\fR +\fB \fR +\fB // check to see if this is a naming context\fR +\fB if (bindings[i]\&.binding_type == BindingType\&.ncontext) {\fR +\fB System\&.out\&.println("Context: " +\fR +\fB bindings[i]\&.binding_name[lastIx]\&.id);\fR +\fB } else {\fR +\fB System\&.out\&.println("Object: " +\fR +\fB bindings[i]\&.binding_name[lastIx]\&.id);\fR +\fB }\fR +\fB }\fR +\fB } catch (Exception e) {\fR +\fB e\&.printStackTrace(System\&.err)\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +orbd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/unpack200.1 b/jdk-1.8.0.281/man/ja/man1/unpack200.1 new file mode 100755 index 0000000..1425257 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/unpack200.1 @@ -0,0 +1,186 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: unpack200 +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "unpack200" "1" "2013å¹´11月21日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +unpack200 \- \fBpack200\fR(1)で作成されたパック・ファイルを、WebデプロイメントのためにJARファイルに変換します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBunpack200\fR [ \fIoptions\fR ] input\-file \fIJAR\-file\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIinput\-file\fR +.RS 4 +入力ファイルの名前。pack200 gzipファイルかpack200ファイルを指定できます。入力ファイルには、\fBpack200\fR(1)で作成されたJARファイルを指定することもできます(手間は\fB0\fRです)。この場合、入力ファイルの内容はPack2000マーカーで出力JARファイルにコピーされます。 +.RE +.PP +\fIJAR\-file\fR +.RS 4 +出力JARファイル名。 +.RE +.SH "説明" +.PP +\fBunpack200\fRコマンドは、\fBpack200\fR\fB(1)\fRで作成されたパック・ファイルをJARファイルに変換するネイティブ実装です。一般的な使用方法は次のとおりです。次の例では、デフォルトの\fBunpack200\fRコマンド設定で、\fBmyarchive\&.jar\fRファイルが\fBmyarchive\&.pack\&.gz\fRから作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBunpack200 myarchive\&.pack\&.gz myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-Hvalue \-\-deflate\-hint=\fIvalue\fR +.RS 4 +JARファイル内のすべてのエントリに\fBtrue\fR、\fBfalse\fRまたは\fBkeep\fRのデフレーションを設定します。デフォルト・モードは\fBkeep\fRです。値が\fBtrue\fRまたは\fBfalse\fR場合、\fB\-\-deflate=hint\fRオプションはデフォルトの動作をオーバーライドして、出力JARファイル内のすべてのエントリのデフレーション・モードが設定されます。 +.RE +.PP +\-r \-\-remove\-pack\-file +.RS 4 +入力パック・ファイルを削除します。 +.RE +.PP +\-v \-\-verbose +.RS 4 +最小限のメッセージが表示されます。このオプションの複数の仕様には、より詳細なメッセージが表示されます。 +.RE +.PP +\-q \-\-quiet +.RS 4 +メッセージを表示せずに動作するように指定します。 +.RE +.PP +\-lfilename \-\-log\-file=\fIfilename\fR +.RS 4 +出力メッセージが記録されるログ・ファイルを指定します。 +.RE +.PP +\-? \-h \-\-help +.RS 4 +\fBunpack200\fRコマンドに関するヘルプ情報を出力します。 +.RE +.PP +\-V \-\-version +.RS 4 +\fBunpack200\fRコマンドに関するバージョン情報を出力します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineにoptionを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "注意" +.PP +このコマンドと\fBunpack\fRコマンドを混同しないでください。これらは別製品です。 +.PP +JDKに付属するJava SE API仕様との相違が見つかった場合には、仕様を優先してください。 +.SH "終了ステータス" +.PP +次の終了値が返されます: 正常終了の場合は0、エラーが発生した場合は0より大きい値。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +pack200(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jarsigner(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Compression Formats for Network Deployment」 + +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jweb/networking/compression_formats\&.html +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Java SE Technical Documentation」 +(http://docs\&.oracle\&.com/javase/) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/wsgen.1 b/jdk-1.8.0.281/man/ja/man1/wsgen.1 new file mode 100755 index 0000000..d5e51f4 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/wsgen.1 @@ -0,0 +1,215 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: wsgen +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "wsgen" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +wsgen \- Webサービスのエンドポイント実装(SEI)クラスを読取り、Webサービスのデプロイメントと呼出しに必要なすべてのアーティファクトを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen\fR [ \fIoptions\fR ] \fISEI\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fISEI\fR +.RS 4 +読み取るWebサービスのエンドポイント実装クラス(SEI)です。 +.RE +.SH "説明" +.PP +\fBwsgen\fRコマンドは、JAX\-WS Webサービスで使用されるJAX\-WSポータブル・アーティファクトを生成します。このツールは、Webサービスのエンドポイント・クラスを読取り、Webサービスのデプロイメントと呼出しに必要なすべてのアーティファクトを生成します。JAXWS 2\&.1\&.1 RIでは\fBwsgen\fR +Antタスクも提供されます。 +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsgenant\&.htmlのJAX\-WS (wsgen)ページのToolsタブを参照してください。 +.PP +\fBwsgen\fRコマンドを起動するには、次を行います。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBexport JAXWS_HOME=/pathto/jaxws\-ri\fR +\fB$JAXWS_HOME/bin/wsgen\&.sh \-help\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-classpath \fIpath\fR +.RS 4 +入力クラス・ファイルの場所。 +.RE +.PP +\-cp \fIpath\fR +.RS 4 +入力クラス・ファイルの場所。 +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +生成された出力ファイルを格納する場所。 +.RE +.PP +\-extension +.RS 4 +ベンダー拡張を使用可能にします。拡張を使用すると、アプリケーションの移植性が失われたり、他の実装と連携できなくなる可能性があります。 +.RE +.PP +\-help +.RS 4 +\fBwsgen\fRコマンドに関するヘルプ・メッセージを表示します。 +.RE +.PP +\-keep +.RS 4 +生成されたファイルを保存します。 +.RE +.PP +\-r \fIdirectory\fR +.RS 4 +このオプションを\fB\-wsdl\fRオプションとともに使用して、WSDLなど生成されたリソース・ファイルを配置する場所を指定します。 +.RE +.PP +\-s \fIdirectory\fR +.RS 4 +生成されたソース・ファイルを格納する場所。 +.RE +.PP +\-verbose +.RS 4 +コンパイラ・メッセージを表示します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-wsdl [ :protocol ] +.RS 4 +エンドポイントをデプロイする前に確認するWSDLファイルを生成するオプション・コマンド。WSDLファイルには、サービスを呼び出す方法、パラメータに必要な値、返されるデータ構造についてのコンピュータで読取り可能な記述が含まれます。 +.sp +デフォルトでは\fBwsgen\fRコマンドはWSDLファイルを生成しません。\fBprotocol\fR値は省略可能であり、WSDLバインディング(\fBwsdl:binding\fR)で使用するプロトコルを指定するために使用されます。有効なプロトコルは、\fBsoap1\&.1\fRと\fBXsoap1\&.2\fRです。デフォルトは\fBsoap1\&.1\fRです。\fBXsoap1\&.2\fRプロトコルは標準ではないため、\fB\-extension\fRオプションとともにのみ使用可能です。 +.RE +.PP +\-servicename \fIname\fR +.RS 4 +\fB\-wsdl\fRオプションとともにのみ使用して、WSDLで生成される特定のWSDLサービス(\fBwsdl:service\fR)名を指定します。例: +\fB\-servicename "{http://mynamespace/}MyService"\fR。 +.RE +.PP +\-portname \fIname\fR +.RS 4 +\fB\-wsdl\fRオプションとともにのみ使用して、WSDLで生成される特定のWSDLポート(\fBwsdl:port\fR)名を指定します。例: +\fB\-portname "{http://mynamespace/}MyPort"\fR。 +.RE +.SH "例" +.PP +次の例では、Stockディレクトリ内に\fB@WebService\fR注釈を持つ\fBStockService\fRのラッパー・クラスを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen \-d stock \-cp myclasspath stock\&.StockService\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、SOAP 1\&.1 WSDLおよび\fB@WebService\fR注釈を持つ\fBstock\&.StockService\fRクラスのスキーマを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen \-wsdl \-d stock \-cp myclasspath stock\&.StockService\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、SOAP 1\&.2 WSDLを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen \-wsdl:Xsoap1\&.2 \-d stock \-cp myclasspath stock\&.StockService \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB注意:\fR +サービスのデプロイ時にJAXWS実行時環境でWSDLが生成されるため、開発時にWSDLを生成する必要はありません。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +wsimport(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsgenant\&.htmlの +JAX\-WS (wsgen)ページのToolsタブを参照してください。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/wsimport.1 b/jdk-1.8.0.281/man/ja/man1/wsimport.1 new file mode 100755 index 0000000..9a6ba38 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/wsimport.1 @@ -0,0 +1,318 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: wsimport +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "wsimport" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +wsimport \- Webアプリケーション・アーカイブ(WAR)ファイルにパッケージできるJAX\-WSポータブル・アーティファクトを生成して、Antタスクを指定します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsimport\fR [ \fIoptions\fR ] \fIwsdl\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIwsdl\fR +.RS 4 +Webサービスを呼び出す方法、パラメータに必要な値、返されるデータ構造についてのコンピュータで読取り可能な記述が含まれまるファイルです。 +.RE +.SH "説明" +.PP +\fBwsimport\fRコマンドは、次のJAX\-WSポータブル・アーティファクトを生成します。これらのアーティファクトは、デプロイするWSDLおよびスキーマ・ドキュメントおよびエンドポイント実装とともに、WARファイルにパッケージできます。\fBwsimport\fRコマンドでは\fBwsimport\fR +Antタスクも提供されます。 +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlのWsimport Ant TaskページのToolsタブを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +サービス・エンドポイント・インタフェース(SEI) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +サービス +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +例外クラスは\fBwsdl:fault\fRからマップされます(存在する場合) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非同期レスポンスBeanはレスポンス\fBwsdl:message\fRから派生します(存在する場合) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JAXBが生成する値タイプ(スキーマのタイプからマップされたJavaクラス) +.RE +.PP +\fBwsgen\fRコマンドを起動するには、次を行います。 +.PP +\fBOracle Solaris/Linux\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/bin/wsimport\&.sh \-help\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBWindows\fRの場合: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\ebin\ewsimport\&.bat \-help\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-d \fIdirectory\fR +.RS 4 +生成される出力ファイルを格納する場所を指定します。 +.RE +.PP +\-b \fIpath\fR +.RS 4 +外部JAX\-WSまたはJAXBバインディング・ファイルを指定します。\fB\-b\fRオプションで複数のJAX\-WSおよびJAXBバインディング・ファイルを指定できます。これらのファイルを使用して、パッケージ名、Bean名などをカスタマイズできます。JAX\-WSおよびJAXBバインディング・ファイルの詳細は、 +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlのWSDL CustomizationのUsers Guideタブを参照してください +.RE +.PP +\-B \fIjaxbOption\fR +.RS 4 +JAXBスキーマ・コンパイラに\fBjaxbOption\fRオプションを渡します。 +.RE +.PP +\-catalog +.RS 4 +外部エンティティ参照を解決するカタログ・ファイルを指定します。\fB\-catalog\fRオプションは、TR9401、XCatalog、OASIS XML Catalogの各形式をサポートしています。http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/catalog\-support\&.htmlの +Catalog SupportページのUsers Guideタブを参照してください。 +.RE +.PP +\-extension +.RS 4 +ベンダー拡張を使用可能にします。拡張を使用すると、アプリケーションの移植性が失われたり、他の実装と連携できなくなる可能性があります。 +.RE +.PP +\-help +.RS 4 +\fBwsimport\fRコマンドに関するヘルプ・メッセージを表示します。 +.RE +.PP +\-httpproxy: \fIhost\fR:\fIport\fR +.RS 4 +HTTPプロキシ・サーバーを指定します。デフォルトは8080です。 +.RE +.PP +\-keep +.RS 4 +生成されたファイルを保持します +.RE +.PP +\-p \fIname\fR +.RS 4 +ターゲット・パッケージ\fIname\fRを指定して、WSDLおよびスキーマ・バインディングのカスタマイズ、および仕様部で定義されたデフォルトのアルゴリズムをオーバーライドします。 +.RE +.PP +\-s \fIdirectory\fR +.RS 4 +生成されるソース・ファイルを格納する場所を指定します +.RE +.PP +\-verbose +.RS 4 +コンパイラ・メッセージを表示します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-wsdllocation \fIlocation\fR +.RS 4 +\fB@WebServiceClient\&.wsdlLocation\fRの値を指定します。 +.RE +.PP +\-target +.RS 4 +指定されたJAX\-WS仕様バージョンに従って、コードを生成します。バージョン2\&.0では、JAX\-WS 2\&.0仕様に準拠したコードを生成します。 +.RE +.PP +\-quiet +.RS 4 +\fBwsimport\fRコマンド出力を抑制します。 +.RE +.PP +\fB\-b\fRオプションを使用して、複数の\fBJAX\-WS\fRおよび\fBJAXB\fRバインディング・ファイルを指定できます。これらのファイルを使用して、パッケージ名やBean名など、様々なものをカスタマイズできます。\fBJAX\-WS\fRおよび\fBJAXB\fRバインディング・ファイルの詳細は、 +https://jax\-ws\&.java\&.net/nonav/2\&.1\&.2/docs/customizations\&.htmlのカスタマイズ・ドキュメントを参照してください +.SH "非標準オプション" +.PP +\-XadditionalHeaders +.RS 4 +リクエストまたはレスポンス・メッセージにバインドされないヘッダーをJavaメソッドのパラメータにマップします +.RE +.PP +\-Xauthfile \fIfile\fR +.RS 4 +認証情報を含むファイルを指定するWSDL URIです。このURIの形式は次のとおりです。 +.sp +http://\fIuser\-name\fR:\fBpassword\fR@\fIhost\-name\fR/\fIweb\-service\-name\fR>?wsdl\&. +.RE +.PP +\-Xdebug +.RS 4 +デバッグ情報を出力します +.RE +.PP +\-Xno\-addressing\-databinding +.RS 4 +W3C EndpointReferenceTypeとJavaのバインディングを有効にします。 +.RE +.PP +\-Xnocompile +.RS 4 +生成されたJavaファイルをコンパイルしません +.RE +.SH "例" +.PP +次の例では、Javaアーティファクトを生成し、\fBhttp://stockquote\&.example\&.com/quote?wsdl\fRをインポートしてアーティファクトをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsimport \-p stockquote http://stockquote\&.example\&.com/quote?wsdl\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +wsgen(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlの +Wsimport Ant TaskページのToolsタブ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/catalog\-support\&.htmlの +Catalog SupportページのUsers Guideタブ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlの +WSDL CustomizationページのUsers Guideタブ +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja/man1/xjc.1 b/jdk-1.8.0.281/man/ja/man1/xjc.1 new file mode 100755 index 0000000..e9a04e0 --- /dev/null +++ b/jdk-1.8.0.281/man/ja/man1/xjc.1 @@ -0,0 +1,325 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: xjc +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "xjc" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +xjc \- XMLスキーマ・ファイルを完全注釈付きのJavaクラスにコンパイルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBxjc\fR [ \fIoptions\fR ] \fBschema\fR \fIfile/URL/dir/jar\fR \&.\&.\&. [\fB\-b\fR \fIbindinfo\fR ] \&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +schema \fIfile/URL/dir/jar \&.\&.\&.\fR +.RS 4 +XMLスキーマ・ファイルの場所。\fBdir\fRが指定されている場合は、すべてのスキーマ・ファイルがコンパイルされます。\fBjar\fRが指定されている場合は、\fB/META\-INF/sun\-jaxb\&.episode\fRバインディング・ファイルがコンパイルされます。 +.RE +.PP +\-b \fIbindinfo\fR +.RS 4 +バインディング・ファイルの場所。 +.RE +.SH "説明" +.PP +プラットフォームのbinディレクトリにある適切な\fBxjc\fRシェル・スクリプトを使用して、バインディング・コンパイラを起動します。バインディング・コンパイラを実行するAntタスクもあります。http://jaxb\&.java\&.net/nonav/2\&.1\&.3/docs/xjcTask\&.htmlの +Using the XJC with Antを参照してください +.SH "オプション" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非標準オプションも参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非推奨で削除されたオプションも参照してください +.RE +.PP +\-nv +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、ソース・スキーマを処理する前に厳密な検証を実行します。このオプションを使用すると、厳密なスキーマ検証か無効になります。これは、バインディング・コンパイラが検証を一切実行しないということではありません。より厳密でない検証を実行するということです。 +.RE +.PP +\-extension +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、JAXB仕様のCompatibilityの章で説明されているルールを厳密に強制します。付録E\&.2には、JAXB v1\&.0で完全にはサポートされていない一連のW3C XMLスキーマ機能が定義されています。場合によっては、このスイッチで有効になる\fB\-extension\fRモードでそれらの機能が使用できる場合があります。また、デフォルトの厳密なモードでは、仕様に定義されているバインディング・カスタマイズのみが使用できます。\fB\-extension\fRスイッチを指定すれば、JAXB Vendor Extensionを使用できます。 +.RE +.PP +\-b \fIfile\fR +.RS 4 +処理する外部バインディング・ファイルを1つまたは複数指定します。バインディング・ファイルごとに\fB\-b\fRスイッチを指定する必要があります。外部バインディング・ファイルの構文は柔軟です。複数のスキーマのカスタマイズが含まれる1つのバインディング・ファイルを使用したり、それらのカスタマイズを複数のバインディング・ファイルに分割したりできます。次に例を示します。\fBxjc schema1\&.xsd schema2\&.xsd schema3\&.xsd \-b bindings123\&.xjb\fR +\fBxjc schema1\&.xsd schema2\&.xsd schema3\&.xsd \-b bindings1\&.xjb \-b bindings2\&.xjb \-b bindings3\&.xjb\fRまた、コマンドラインにスキーマ・ファイルとバインディング・ファイルを指定する順番は任意です。 +.RE +.PP +\-d \fIdir\fR +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、Javaコンテンツ・クラスを現在のディレクトリに生成します。このオプションを使用すると、代替出力ディレクトリを指定できます。出力ディレクトリはすでに存在している必要があります。XJCバインディング・コンパイラでは作成されません。 +.RE +.PP +\-p \fIpkg\fR +.RS 4 +このコマンドライン・オプションでターゲット・パッケージを指定した場合、その指定内容は、パッケージ名に対するすべてのバインディング・カスタマイズや、仕様で規定されているデフォルトのパッケージ名アルゴリズムよりも優先されます。 +.RE +.PP +\-httpproxy \fIproxy\fR +.RS 4 +\fI[user[:password]@]proxyHost[:proxyPort]\fR形式でHTTPまたはHTTPSプロキシを指定します。古い\fB\-host\fRおよび\fB\-port\fRオプションは、下位互換性のために引き続きRIでサポートされますが、非推奨となりました。このオプションで指定されたパスワードは、topコマンドを使用する他のユーザーが表示できる引数です。セキュリティを高めるには、\fB\-httpproxyfile\fRを使用してください。 +.RE +.PP +\-httpproxyfile file +.RS 4 +ファイルを使用して、HTTPまたはHTTPSプロキシを指定します。形式は\fB\-httpproxy\fRオプションと同じですが、このファイル内に指定されたパスワードを他のユーザーが表示することはできません。 +.RE +.PP +\-classpath arg +.RS 4 +\fIjxb:javaType\fRおよびxjc:\fIsuperClass\fRカスタマイズが使用するクライアント・アプリケーションのクラス・ファイルの検索場所を指定します。 +.RE +.PP +\-catalog file +.RS 4 +外部エンティティ参照を解決するカタログ・ファイルを指定します。TR9401、XCatalogおよびOASIS XML Catalogの各形式がサポートされます。http://xerces\&.apache\&.org/xml\-commons/components/resolver/resolver\-article\&.htmlの +XML Entity and URI Resolversを参照してください +.RE +.PP +\-readOnly +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、生成するJavaソース・ファイルを書込みから保護しません。このオプションを使用すると、XJCバインディング・コンパイラは生成されるJavaソースを強制的に読取り専用にします。 +.RE +.PP +\-npa +.RS 4 +\fB**/package\-info\&.java\fRへのパッケージ・レベルの注釈の生成を抑制します。このスイッチを使用して生成するコードでは、これらの注釈が他の生成済クラスに内部化されます。 +.RE +.PP +\-no\-header +.RS 4 +多少のメモとタイムスタンプを含むファイル・ヘッダー・コメントの生成を抑制します。これを使用すると、生成されたコードと\fBdiff\fRコマンドとの互換性がより強くなります。 +.RE +.PP +\-target 2\&.0 +.RS 4 +JAXB 2\&.1機能に依存するコードを生成しないようにします。これにより、生成されたコードをJAXB 2\&.0ランタイム環境(Java SE 6など)で実行できるようになります。 +.RE +.PP +\-xmlschema +.RS 4 +入力スキーマをW3C XMLスキーマとして扱います(デフォルト)。このスイッチを指定しない場合、入力スキーマはW3C XMLスキーマと同じように扱われます。 +.RE +.PP +\-relaxing +.RS 4 +入力スキーマをRELAX NGとして扱います(試験的および未サポート)。RELAX NGスキーマのサポートはJAXB Vendor Extensionとして提供されています。 +.RE +.PP +\-relaxing\-compact +.RS 4 +入力スキーマをRELAX NG圧縮構文として処理します(試験的および未サポート)。RELAX NGスキーマのサポートはJAXB Vendor Extensionとして提供されています。 +.RE +.PP +\-dtd +.RS 4 +入力スキーマをXML DTDとして扱います(試験的および未サポート)。RELAX NGスキーマのサポートはJAXB Vendor Extensionとして提供されています。 +.RE +.PP +\-wsdl +.RS 4 +入力をWSDLとして扱い、その内部のスキーマをコンパイルします(試験的および未サポート)。 +.RE +.PP +\-quiet +.RS 4 +進捗情報や警告など、コンパイラの出力を抑制します。 +.RE +.PP +\-verbose +.RS 4 +情報メッセージを出力したり特定のエラー発生時にスタック・トレースを表示したりするなど、きわめて冗長になります。 +.RE +.PP +\-help +.RS 4 +コンパイラ・スイッチのサマリーを表示します。 +.RE +.PP +\-version +.RS 4 +コンパイラのバージョン情報を表示します。 +.RE +.PP +\fIschema file/URL/dir\fR +.RS 4 +コンパイル対象となる1つまたは複数のスキーマ・ファイルを指定します。ディレクトリを指定する場合、\fBxjc\fRコマンドはすべてのスキーマ・ファイルをスキャンしてコンパイルします。 +.RE +.SS "非標準オプション" +.PP +\-XLocator +.RS 4 +生成されたコードでは、非整列化の後にJava Beanインスタンスに含まれるソースXMLに関するSAX Locator情報が公開されます。 +.RE +.PP +\-Xsync\-methods +.RS 4 +生成されたすべてのメソッド・シグニチャに\fBsynchronized\fRキーワードが含められます。 +.RE +.PP +\-mark\-generated +.RS 4 +生成されたコードに注釈\fB@javax\&.annotation\&.Generated\fRを付けます。 +.RE +.PP +\-episode file +.RS 4 +コンパイルごとに指定されたエピソード・ファイルを生成します。 +.RE +.SS "非推奨で削除されたオプション" +.PP +\-host & \-port +.RS 4 +これらのオプションは\fB\-httpproxy\fRオプションで置き換えられました。これらのオプションは、後方互換性を確保するためにサポートされますが、ドキュメントには記載されず、将来のリリースで削除される可能性もあります。 +.RE +.PP +\-use\-runtime +.RS 4 +JAXB 2\&.0仕様では、移植性のあるランタイム環境が定義されたため、JAXB RIが\fB**/impl/runtime \fRパッケージを生成する必要がなくなりました。このため、このスイッチは不要となり、削除されました。 +.RE +.PP +\-source +.RS 4 +\fB\-source\fR互換性スイッチは、JAXB 2\&.0の最初のEarly Access版で導入されました。このスイッチはJAXB 2\&.0の今後のリリースから削除されます。1\&.0\&.xコードを生成する必要がある場合は、1\&.0\&.xコード・ベースのインストールを使用してください。 +.RE +.SH "コンパイラの制限" +.PP +通常は、関連するすべてのスキーマを、同じバインディング・コンパイラ・スイッチを指定して1つの単位としてコンパイルするのが最も安全です。\fBxjc\fRコマンドの実行時には、次の制限リストに留意してください。これらの問題のほとんどは、\fBxjc\fRコマンドを何度か呼び出して複数のスキーマをコンパイルする場合にのみ当てはまります。 +.PP +複数のスキーマを同時にコンパイルする場合は、ターゲットのJavaパッケージ名に次の優先順位のルールが適用されることに注意してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +\fB\-p\fRオプションが最も優先されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +\fIjaxb:package\fRのカスタマイズ。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +\fBtargetNamespace\fRが宣言されている場合は、\fBt\fR\fBargetNamespace\fRを仕様で定義されているJavaパッケージ名のアルゴリズムに適用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +\fBtargetNamespace\fRが宣言されていない場合は、\fBgenerated\fRという名前のハードコードされたパッケージを使用します。 +.RE +.PP +1つのネームスペースが複数の\fIjaxb:schemaBindings\fRを持つことはできないため、異なるJavaパッケージにコンパイラされる同一ターゲット・ネームスペースが2つのスキーマを持つことはできません。 +.PP +同じJavaパッケージにコンパイラされるスキーマはすべて、同時にXJCバインディング・コンパイラに送信される必要があります。別々にコンパイルすると、予想どおりに機能しません。 +.PP +複数のスキーマ・ファイルにまたがる要素置換グループは、同時にコンパイルする必要があります。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/xjc\&.htmlの +Binding Compiler (xjc) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://www\&.oracle\&.com/technetwork/articles/javase/index\-140168\&.htmlの +Java Architecture for XML Binding (JAXB) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/appletviewer.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/appletviewer.1 new file mode 100755 index 0000000..381ac86 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/appletviewer.1 @@ -0,0 +1,88 @@ +'\" t +.\" Copyright (c) 1995, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: appletviewer +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "appletviewer" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +appletviewer \- Webブラウザの外側でアプレットを実行します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBappletviewer\fR [\fIoptions\fR] \fIurl\fR\&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +空白で区切られたコマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIurl\fR +.RS 4 +表示するドキュメントまたはリソースの場所。空白で区切られた複数のURLを指定できます。 +.RE +.SH "説明" +.PP +\fBappletviewer\fRコマンドは\fIurls\fRに指定されたドキュメントあるいはリソースと接続して、そのドキュメントが参照するそれぞれのアプレットを独自のウィンドウで表示します。urlsによって参照されたドキュメントが、\fBOBJECT\fR、\fBEMBED\fRまたは\fBAPPLET\fRタグでどのアプレットも参照していない場合、\fBappletviewer\fRコマンドは何も行いません。\fBappletviewer\fRコマンドでサポートされるHTMLタグの詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/appletviewertags\&.htmlにある +アプレット・ビューア・タグを参照してください。 +.PP +\fBappletviewer\fRコマンドは、RFC2396で定義されたエスケープ・メカニズムに従ってエンコードされたURLを必要とします。サポートされるのは、エンコードされたURLのみです。ただし、ファイル名については、RFC2396の仕様に従ってエンコードを解除しておく必要があります。 +.PP +\fB注意:\fR +The +\fBappletviewer\fRコマンドは開発専用です。詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/aboutCodeSamples\&.htmlにある +サンプル/テスト・アプリケーションおよびコードについてを参照してください。 +.SH "オプション" +.PP +\-debug +.RS 4 +\fBjdb\fRコマンドを使用してJavaデバッガでアプレット・ビューアを開始して、ドキュメント中のアプレットをデバッグします。 +.RE +.PP +\-encoding \fIencoding\-name\fR +.RS 4 +入力HTMLファイルのエンコーディング名を指定します。 +.RE +.PP +\-J\fIjavaoption\fR +.RS 4 +文字列\fBjavaoption\fRは、アプレット・ビューアを実行するJavaインタプリタに1つの引数として渡されます。引数にスペースを含めないでください。複数の引数は、すべてが接頭辞\fB\-J\fRで始まる必要があります。これは、コンパイラの実行環境またはメモリー使用の調整に有効です。 +.RE +.PP + +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/extcheck.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/extcheck.1 new file mode 100755 index 0000000..192e5a9 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/extcheck.1 @@ -0,0 +1,91 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: extcheck +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "extcheck" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +extcheck \- ターゲットのJavaアーカイブ(JAR)ファイルと現在インストールされている拡張機能のJARファイル間のバージョンの競合を検出します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBextcheck\fR [\fIoptions\fR] \fItargetfile\&.jar\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fItargetfile\&.jar\fR +.RS 4 +バージョンの競合を検出するために、現在インストールされている拡張機能JARファイルと比較するターゲットJARファイル。 +.RE +.SH "説明" +.PP +\fBextcheck\fRコマンドは、指定されたJARファイルのタイトルおよびバージョンがJava SE SDKにインストールされている拡張機能と競合していないかをチェックします。拡張機能をインストールする前に、このユーティリティを使用して、同じバージョンまたはより新しいバージョンの拡張機能がすでにインストールされていないかどうかを調べることができます。 +.PP +\fBextcheck\fRコマンドは、\fBtargetfile\&.jar\fRファイルのマニフェスト内のヘッダーSpecification\-titleおよびSpecification\-versionを、拡張機能ディレクトリ内に現在インストールされているすべてのJARファイル内の対応するヘッダーと比較します。デフォルトでは、拡張機能ディレクトリは、Oracle Solarisの場合は\fBjre/lib/ext\fR、Windowsの場合は\fB\ejre\elib\eext\fRです。\fBextcheck\fRコマンドは、\fBjava\&.lang\&.Package\&.isCompatibleWith\fRメソッドと同様の方法でバージョン番号を比較します。 +.PP +競合が検出されない場合、リターン・コードは0です。 +.PP +拡張機能ディレクトリ内のいずれかのJARファイルのマニフェストに、同一の\fBSpecification\-title\fR、および同一またはより新しい\fBSpecification\-version\fR番号がある場合は、ゼロでないエラー・コードが返されます。\fBtargetfile\&.jar\fRのマニフェスト・ファイルに\fBSpecification\-title\fRまたは\fBSpecification\-version\fR属性がない場合も、ゼロでないエラー・コードが返されます。 +.SH "オプション" +.PP +\-verbose +.RS 4 +拡張機能ディレクトリ内のJARファイルを、チェック時に一覧表示します。また、ターゲットJARファイルのマニフェストの属性、および競合するJARファイルについても報告します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machine (JVM)に\fIoption\fRを渡します。optionには、Java起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/idlj.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/idlj.1 new file mode 100755 index 0000000..bbd4b58 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/idlj.1 @@ -0,0 +1,529 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: idlj +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "idlj" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +idlj \- 指定されたインタフェース定義言語(IDL)ファイルに対してJavaバインディングを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj\fR [ \fIoptions\fR ] \fIidlfile\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。optionsの順番は任意ですが、\fBidlfile\fRよりも前に指定する必要があります。 +.RE +.PP +\fIidlfile\fR +.RS 4 +インタフェース定義言語(IDL)による定義が含まれるファイルの名前。 +.RE +.SH "説明" +.PP +IDL\-to\-Javaコンパイラは、指定されたIDLファイルに対してJavaバインディングを生成します。バインディングの詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.htmlにある +Java IDL: Java言語マッピングへのIDLを参照してください。 +.PP +IDL\-to\-Javaコンパイラの以前のリリースの中には、\fBidltojava\fRという名前だったものがあります。 +.SS "クライアント・バインディングおよびサーバー・バインディングの発行" +.PP +次の\fBidlj\fRコマンドは、クライアント側バインディングを含む\fBMy\&.idl\fRという名前のIDLファイルを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +前の構文は次と同等です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fclient My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、サーバー側バインディングを生成し、クライアント側バインディングおよびスケルトンを含めており、これらはすべて、POA (継承モデル)です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlg \-fserver My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +クライアント側とサーバー側の両方のバインディングを生成する場合は、次のコマンド(どれも等価)のうちの1つを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fclient \-fserver My\&.idl\fR +\fBidlj \-fall My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +サーバー側で可能なモデルは2つあります。移殖可能サーバント継承モデルとTieモデルです。Tie委譲モデルを参照してください。 +.PP +\fB移殖可能サーバント継承モデル\fR. デフォルトのサーバー側のモデルは、移殖可能サーバント継承モデルです。\fBMy\&.idl\fR内で\fBMy\fRインタフェースが定義されている場合は、\fBMyPOA\&.java\fRというファイルが生成されます。\fBMy\fRインタフェースの実装を提供する必要があり、\fBMy\fRインタフェースは\fBMyPOA\fRクラスから継承する必要があります。\fBMyPOA\&.java\fRは、http://docs\&.oracle\&.com/javase/8/docs/api/org/omg/PortableServer/Servant\&.htmlにある +\fBorg\&.omg\&.PortableServer\&.Servant\fRクラスを拡張するストリームベースのスケルトンです。 +.PP +\fBMy\fRインタフェースは、スケルトンが実装するIDLインタフェースに関連付けられている\fBcallHandler\fRインタフェースと操作インタフェースを実装します。 +.PP +ポータブル・オブジェクト・アダプタ(POA)の\fBPortableServer\fRモジュールは、ネイティブの\fBServant\fR型を定義します。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/POA\&.htmlにある +ポータブル・オブジェクト・アダプタ(POA)を参照してください。 +.PP +Javaプログラミング言語では、\fBServant\fR型はJavaの\fBorg\&.omg\&.PortableServer\&.Servant\fRクラスにマップされます。これは、すべてのPOAサーバント実装のベース・クラスとして機能し、アプリケーション・プログラマが呼び出すことのできるいくつかのメソッド、およびPOAによって呼び出され、サーバントの動作を制御するためにユーザーがオーバーライドできるメソッドを提供します。 +.PP +継承モデルのもう1つのオプションは、\fB\-oldImplBase\fRフラグを使用して、Java SE 1\&.4より前のリリースのJavaプログラミング言語と互換性のあるサーバー側バインディングを生成することです。\-\fBoldImplBase\fRフラグは非標準で、これらのAPIは非推奨です。このフラグを使用するのは、Java SE 1\&.3で記述された既存のサーバーとの互換性が必要な場合のみです。その場合、既存のmakeファイルを変更して、\fB\-oldImplBase\fRフラグを\fBidlj\fRコンパイラに追加する必要があります。それ以外の場合、POAベースのサーバー側マッピングが生成されます。後方互換性のあるサーバー側バインディングを生成するには、次を実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fclient \-fserver \-oldImplBase My\&.idl\fR +\fBidlj \-fall \-oldImplBase My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBMy\&.idl\fR内で\fBMy\fRインタフェースが定義されている場合は、\fB_MyImplBase\&.java\fRというファイルが生成されます。\fBMy\fRインタフェースの実装を提供する必要があり、\fBMy\fRインタフェースは\fB_MyImplBase\fRクラスから継承する必要があります。 +.PP +\fBTie委譲モデル\fR. もう1つのサーバー側モデルは、Tieモデルと呼ばれるものです。このサーバー側モデルは、委譲モデルです。Tieとスケルトンを同時に生成することはできないため、それらは別々に生成する必要があります。次のコマンドによって、Tieモデル用のバインディングが生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-fall My\&.idl\fR +\fBidlj \-fallTIE My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBMy\fRインタフェースの場合、2番目のコマンドにより、\fBMyPOATie\&.java\fRが生成されます。\fBMyPOATie\fRクラスへのコンストラクタは、delegateを取ります。この例では、デフォルトのPOAモデルを使用しているため、コンストラクタにもPOAが必要です。delegateに対して実装を提供する必要がありますが、この実装は\fBMyOperations\fRインタフェースから継承する必要があるのみで、その他のクラスから継承する必要はありません。これをORBと一緒に使用するには、たとえば次のように\fBMyPOATie\fRクラス内で実装をラップする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBORB orb = ORB\&.init(args, System\&.getProperties());\fR +\fB \fR +\fB// Get reference to rootpoa & activate the POAManager\fR +\fBPOA rootpoa = (POA)orb\&.resolve_initial_references("RootPOA");\fR +\fBrootpoa\&.the_POAManager()\&.activate();\fR +\fB \fR +\fB// create servant and register it with the ORB\fR +\fBMyServant myDelegate = new MyServant();\fR +\fBmyDelegate\&.setORB(orb); \fR +\fB \fR +\fB// create a tie, with servant being the delegate\&.\fR +\fBMyPOATie tie = new MyPOATie(myDelegate, rootpoa);\fR +\fB \fR +\fB// obtain the objectRef for the tie\fR +\fBMy ref = tie\&._this(orb);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +他の実装から継承する必要がある場合、標準の継承モデルではなくTieモデルを使用することもできます。Javaの場合は、インタフェースの継承の個数に制限はありませんが、クラスの継承に使用できるスロットは1つのみです。継承モデルを使用した場合は、そのスロットが占有されます。Tieモデルを使用すると、そのスロットが使用されず、ユーザーが独自の目的で使用できます。この方法には、間接性のレベルが1つ導入されるという短所があります。メソッドを呼び出すときに、余分なメソッド呼出しが1回発生します。 +.PP +サーバー側の生成の場合、Java SE 1\&.4より前のバージョンのJava言語にマッピングするIDLのバージョンと互換性のある、Tieモデルのバインディングです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-oldImplBase \-fall My\&.idl\fR +\fBidlj \-oldImplBase \-fallTIE My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBMy\fRインタフェースの場合、これにより、\fBMy_Tie\&.java\fRが生成されます。\fBMy_Tie\fRクラスへのコンストラクタは、\fBimpl\fRオブジェクトを取ります。\fBimpl\fRに対して実装を提供する必要がありますが、その実装は\fBHelloOperations\fRインタフェースから継承する必要があるのみで、その他のクラスから継承する必要はありません。しかし、これをORBと一緒に使用するには、たとえば次のように\fBMy_Tie\fR内で実装をラップする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBORB orb = ORB\&.init(args, System\&.getProperties());\fR + +\fB// create servant and register it with the ORB\fR +\fBMyServant myDelegate = new MyServant();\fR +\fBmyDelegate\&.setORB(orb); \fR +\fB \fR +\fB// create a tie, with servant being the delegate\&.\fR +\fBMyPOATie tie = new MyPOATie(myDelegate);\fR +\fB \fR +\fB// obtain the objectRef for the tie\fR +\fBMy ref = tie\&._this(orb);\fR + +.fi +.if n \{\ +.RE +.\} +.SS "発行されたファイルの代替位置の指定" +.PP +発行されたファイルを現在のディレクトリ以外のディレクトリに置くには、\fBi\fR\fBdlj \-td /altdir My\&.idl\fRのコマンドでコンパイラを呼び出します。 +.PP + +\fBMy\fRインタフェースの場合、バインディングは、\fB\&./My\&.java\fRではなく、\fB/altdir/My\&.java\fRなどに発行されます。 +.SS "インクルード・ファイルの代替位置の指定" +.PP +\fBMy\&.idl\fRファイルが別の\fBidl\fRファイルである\fBMyOther\&.idl\fRをインクルードする場合、コンパイラでは、\fBMyOther\&.idl\fRファイルがローカル・ディレクトリに存在することを前提としています。たとえば、それが\fB/includes\fRにある場合は、次のようなコマンドでコンパイラを呼び出します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-i /includes My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +たとえば、\fB/moreIncludes\fRにある\fBAnother\&.idl\fRも\fBMy\&.idl\fRにインクルードされているのであれば、次のようなコマンドでコンパイラを呼び出します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-i /includes \-i /moreIncludes My\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +このような形式の\fBinclude\fRは長くなるため、インクルード・ファイルを検索する場所をコンパイラに指示するための別の方法が用意されています。この方法は、環境変数の考え方と似ています。\fBCLASSPATH\fR変数に一覧表示されているディレクトリ内にidl\&.configという名前のファイルを作成します。その\fBidl\&.config\fRの中に、次のような形式の行を入れます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBincludes=/includes;/moreIncludes\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コンパイラは、このファイルを検索し、インクルード・リストを読み込みます。この例では、ディレクトリの間の区切り文字はセミコロン(;)になっています。この区切り文字は、プラットフォームによって異なります。Windowsプラットフォームではセミコロンを使用し、Solaris、LinuxおよびOS Xプラットフォームではコロンを使用します。 +.SS "インクルード・ファイルに対するバインディングの発行" +.PP +デフォルトでは、コマンド行に指定した\fBidl\fRファイルで定義されているインタフェースや構造体などについてのみ、Javaバインディングが生成されます。インクルードされたファイルで定義されている型については生成されません。たとえば、次の2つの\fBidl\fRファイルについて考えてみます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMy\&.idl file:\fR +\fB \fR +\fB#include <MyOther\&.idl>\fR +\fBinterface My\fR +\fB{\fR +\fB};\fR +\fB \fR +\fBMyOther\&.idl file:\fR +\fB \fR +\fBinterface MyOther\fR +\fB{\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +デフォルトのルールに関して警告があります。グローバル・スコープに表示される\fB#include\fR文は、前述のとおりに処理されます。これらの\fB#include\fR文は、インポート文と見なすことができます。囲まれたスコープ内に表示される\fB#include\fR文は、本当の意味での\fB#include\fR文として処理されます。つまり、インクルードされたファイルにあるコードが、元のファイルにそのまま表示されているかのように処理され、それに対してJavaバインディングが発行されます。次はその例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMy\&.idl file:\fR +\fB \fR +\fB#include <MyOther\&.idl>\fR +\fBinterface My\fR +\fB{\fR +\fB #include <Embedded\&.idl>\fR +\fB};\fR +\fB \fR +\fBMyOther\&.idl file:\fR +\fB \fR +\fBinterface MyOther\fR +\fB{\fR +\fB};\fR +\fB \fR +\fBEmbedded\&.idl\fR +\fB \fR +\fBenum E {one, two, three};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB idlj My\&.idl \fRを実行して、Javaファイルの次のリストを生成します。インポート文とみなされる\fB#include\fRに定義されていたため、\fBMyOther\&.java\fRは生成されませんでした。ただし、本当の意味での\fB#include\fRで定義されていたため、\fBE\&.java\fRは生成されました。\fBEmbedded\&.idl\fRファイルが\fBMy\fRインタフェースのスコープ内にインクルードされているため、\fBMy\fRのスコープ内(つまり、\fBMyPackage\fR内)に生成されています。\fB\-emitAll\fRフラグを使用した場合、インクルードされたすべてのファイルにあるすべての型が発行されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\&./MyHolder\&.java\fR +\fB\&./MyHelper\&.java\fR +\fB\&./_MyStub\&.java\fR +\fB\&./MyPackage\fR +\fB\&./MyPackage/EHolder\&.java\fR +\fB\&./MyPackage/EHelper\&.java\fR +\fB\&./MyPackage/E\&.java\fR +\fB\&./My\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.SS "パッケージの接頭辞の挿入" +.PP +ABCという名前の会社のために作業していて、次のようなIDLファイルを構築したとしましょう。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBWidgets\&.idl file:\fR +\fB \fR +\fBmodule Widgets\fR +\fB{\fR +\fB interface W1 {\&.\&.\&.};\fR +\fB interface W2 {\&.\&.\&.};\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +IDL\-to\-Javaコンパイラを介してこのファイルを実行した場合、W1およびW2に対するJavaバインディングは、\fBWidgets\fRパッケージ内に格納されます。業界の慣例によると、会社のパッケージは、\fBcom\&.<company name>\fRという名前のパッケージ内に置くことになっています。この慣例に従うには、パッケージ名を\fBcom\&.abc\&.Widgets\fRにする必要があります。このパッケージ接頭辞をWidgetsモジュールに付加するには、次のコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBidlj \-pkgPrefix Widgets com\&.abc Widgets\&.idl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +Widgets\&.idlをインクルードしているIDLファイルがある場合は、そのコマンドにも\fB\-pkgPrefix\fRフラグが必要です。このフラグを指定しないと、そのIDLファイルは、\fBcom\&.abc\&.Widgets\fRパッケージではなく、\fBWidgets\fRパッケージを検索することになります。 +.PP +接頭辞が必要なパッケージがいくつもある場合は、前述のidl\&.configファイルで接頭辞を指定するのが簡単です。各パッケージの接頭辞行は、\fBPkgPrefix\&.<type>=<prefix>\fRの形式にする必要があります。前述の例の行では、\fBPkgPrefix\&.Widgets=com\&.abc\fRになります。このオプションは、リポジトリIDには影響しません。 +.SS "コンパイル前のシンボルの定義" +.PP +コンパイル用のシンボルがIDLファイル内で定義されていない場合は、そのシンボルを定義する必要があります。これは、たとえば、バインディング内にデバッグ・コードを組み入れるときに使用します。コマンド\fBidlj \-d MYDEF My\&.idl \fRは、My\&.idl内に行\fB#define MYDEF\fRを配置した場合と同等になります。 +.SS "既存のバインディングの保持" +.PP +Javaバインディング・ファイルがすでに存在する場合は、\fB\-keep\fRフラグを指定すると、コンパイラによる上書きを回避できます。デフォルトでは、すでに存在するかどうかにかかわらず、すべてのファイルが生成されます。これらのファイルをカスタマイズした場合(ただし、それらの内容が正確であるとき以外はカスタマイズは避ける)、\fB\-keep\fRオプションは有用です。コマンド\fBidlj \-keep My\&.idl\fRは、すでに存在しないすべてのクライアント側バインディングを発行します。 +.SS "コンパイルの進捗状況の表示" +.PP +IDL\-to\-Javaコンパイラは、実行の各段階で状態メッセージを生成します。\fB\-v\fRオプションを使用して、\fBidlj \-v My\&.idl\fRのような冗長モードをアクティブ化します。 +.PP +デフォルトでは、コンパイラは冗長モードでは実行されません。 +.SS "バージョン情報の表示" +.PP +IDL\-to\-Javaコンパイラのビルド・バージョンを表示するには、コマンドライン\fBidlj \-version\fRで\fB\-version\fRオプションを指定します。 +.PP +バージョン情報は、コンパイラによって生成されたバインディング内にも書き込まれています。このオプションをコマンドラインに指定すると、それ以外のオプションを指定しても、すべて無視されます。 +.SH "オプション" +.PP +\-d \fIsymbol\fR +.RS 4 +このオプションは、IDLファイルに次のような行を追加した場合と等価です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#define \fR\fB\fIsymbol\fR\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-demitAll +.RS 4 +\fB#include\fRファイル内で定義されているものも含めて、すべての型を発行します。 +.RE +.PP +\-fside +.RS 4 +発行するバインディングを定義します。\fBside\fRパラメータには、\fBclient\fR、\fBserver\fR、\fBserverTIE\fR、\fBall\fRまたは\fBallTIE\fRを指定できます。\fB\-fserverTIE\fRまたは\fB\-fallTIE\fRオプションを指定すると、委譲モデル・スケルトンが発行されます。フラグを指定しない場合、\fB\-fclient\fRにデフォルト設定されます。 +.RE +.PP +\-i \fIinclude\-path\fR +.RS 4 +デフォルトでは、インクルード・ファイルは現在のディレクトリから検索されます。このオプションを指定すると、他のディレクトリを追加できます。 +.RE +.PP +\-i \fIkeep\fR +.RS 4 +生成されるファイルがすでに存在している場合は、そのファイルが上書きされません。デフォルトでは、上書きされます。 +.RE +.PP +\-noWarn +.RS 4 +警告メッセージを表示しないようにします。 +.RE +.PP +\-oldImplBase +.RS 4 +1\&.4より前のJDK ORBと互換性のあるスケルトンを生成します。デフォルトでは、POA継承モデルのサーバー側バインディングが生成されます。このオプションを指定すると、\fBImplBase\fR継承モデルのクラスであるサーバー側バインディングが生成されるので、以前のリリースのJavaプログラミング言語との後方互換性が得られます。 +.RE +.PP +\-pkgPrefix \fItype\fR \fIprefix\fR +.RS 4 +\fBtype\fRがファイル・スコープで検出された場合は、その型に対して生成されるすべてのファイルについて、生成されるJavaパッケージ名に\fBprefix\fRという接頭辞が付加されます。typeは、トップレベル・モジュールの単純名か、どのモジュールよりも外側で定義されたIDL型の単純名のどちらかです。 +.RE +.PP +\-pkgTranslate \fItype\fR \fIpackage\fR +.RS 4 +識別子の中にモジュール名typeが検出されると、生成されるJavaパッケージ内のすべてのファイルについて、識別子の中のその名前がpackageで置き換えられます。最初に\fBpkgPrefix\fRの変更が行われます。typeの値は、トップレベルのモジュールの単純名、またはすべてのモジュールの外部で定義されたIDL型の単純名で、完全なパッケージ名に正確に一致する必要があります。 +.sp +複数の変換が識別子に一致する場合、次の例に示すように、最も長い一致が選択されます。 +.sp +\fBコマンド\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpkgTranslate type pkg \-pkgTranslate type2\&.baz pkg2\&.fizz\fR + +.fi +.if n \{\ +.RE +.\} +\fB結果の変換\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtype => pkg\fR +\fBtype\&.ext => pkg\&.ext\fR +\fBtype\&.baz => pkg2\&.fizz\fR +\fBtype2\&.baz\&.pkg => pkg2\&.fizz\&.pkg\fR + +.fi +.if n \{\ +.RE +.\} +パッケージ名\fBorg\fR、\fBorg\fR\&.o\fBmg\fR、または\fBorg\&.omg\fRのサブパッケージは、変換できません。これらのパッケージ名を変換しようとすると、互換性のないコードが生成され、\fB\-pkgTranslate\fRの後の最初の引数としてそれらのパッケージを使用すると、エラーとして扱われます。 +.RE +.PP +\-skeletonName \fIxxx%yyy\fR +.RS 4 +\fBxxx%yyy\fRが、スケルトンに名前を付けるパターンとして使用されます。デフォルトは次のとおりです。\fBPOA\fRベース・クラスの場合は\fB%POA\fR +(\fB\-fserver\fRまたは\fB\-fall\fR)、\fBoldImplBase\fRクラスの場合は\fB_%ImplBase\fR +(\-\fBoldImplBase\fR)および(\fB\-fserver\fRまたは\fB\-fall\fR))。 +.RE +.PP +\-td \fIdir\fR +.RS 4 +出力ディレクトリとして、現在のディレクトリではなく、\fIdir\fRが使用されます。 +.RE +.PP +\-tieName \fIxxx%yyy\fR +.RS 4 +パターンに従って、\fBxxx%yyy\fRを使用します。デフォルトは次のとおりです。\fBPOA\fRベース・クラスの場合は\fB%POA\fR +(\fB\-fserverTieまたは\-fallTie\fR)、\fBoldImplBase\fR +tieクラスの場合は\fB_%Tie\fR +(\-\fBoldImplBase\fR)および(\fB\-fserverTie\fRまたは\fB\-fallTie\fR))。 +.RE +.PP +\-nowarn、\-verbose +.RS 4 +リリース情報を表示して終了します。 +.RE +.PP +\-version +.RS 4 +リリース情報を表示して終了します。 +.RE +.SH "制限事項" +.PP +グローバル・スコープ内のエスケープされた識別子は、IDLプリミティブ型の\fBObject\fRまたは\fBValueBase\fRと同じ綴りにしないでください。これは、シンボル表がこれらの識別子でプリロードされているためです。これらの再定義を許可すると、元の定義が上書きされます。これは、おそらく恒久的な制約です。 +.PP +\fBfixed\fRというIDL型はサポートされていません。 +.SH "既知の問題" +.PP +グローバル識別子についてインポートが生成されません。予期されないローカル\fBimpl\fRオブジェクトを呼び出すと、例外を受け取ります。しかし、その原因は、\fBServerDelegate\fR +DSIコード内の\fBNullPointerException\fRにあるようです。 +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jar.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jar.1 new file mode 100755 index 0000000..f895305 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jar.1 @@ -0,0 +1,519 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jar +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jar" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jar \- Java Archive (JAR)ファイルを操作します。 +.SH "概要" +.PP +JARファイルの作成 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar c\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルの更新 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar u\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルの抽出 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar\fR \fBx\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルのコンテンツのリスト +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar\fR \fBt\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルへの索引の追加 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar\fR \fBi\fR \fIjarfile\fR [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.if n \{\ +.RE +.\} +.SH "説明" +.PP +\fBjar\fRコマンドは、ZIPおよびZLIB圧縮形式に基づく汎用のアーカイブおよび圧縮ツールです。ただし、\fBjar\fRコマンドは、主にいくつかのJavaアプレットやアプリケーションを単一のアーカイブにパッケージ化するように設計されました。アプレットやアプリケーションのコンポーネント(ファイル、イメージ、およびサウンド)が1つのアーカイブに結合されていると、Javaエージェント(ブラウザなど)は、それらのコンポーネントを1回のHTTPトランザクションでダウンロードすることができ、コンポーネントごとに新しい接続が不要になります。これにより、ダウンロード時間が大幅に短縮されます。また、\fBjar\fRコマンドはファイルの圧縮も行うため、ダウンロード時間がさらに短縮されます。また、\fBjar\fRコマンドによって、ファイル内の個々のエントリにアプレット作成者による署名を書き込めるため、配布元の認証が可能になります。JARファイルは、圧縮されているかどうかにかかわらず、クラス・パスのエントリとして使用できます。 +.PP +\fBjar\fRコマンドの構文は、\fBtar\fRコマンドの構文に似ています。必須の\fI操作の引数\fRの1つで定義された複数の操作モードがあります。他の引数は、操作の動作を変更する\fIオプション\fR、または操作を実行するために必要な\fIオペランド\fRを使用します。 +.SH "操作の引数" +.PP +\fBjar\fRコマンドを使用する場合は、次の操作の引数のいずれかを指定して実行される操作を選択する必要があります。コマンド行で他の1文字のオプションと混在させることができますが、通常、操作の引数は指定される最初の引数です。 +.PP +c +.RS 4 +新しいJARアーカイブを作成します。 +.RE +.PP +i +.RS 4 +JARアーカイブの索引情報を生成します。 +.RE +.PP +t +.RS 4 +JARアーカイブのコンテンツをリストします。 +.RE +.PP +u +.RS 4 +JARアーカイブを更新します。 +.RE +.PP +x +.RS 4 +JARアーカイブからファイルを抽出します。 +.RE +.SH "オプション" +.PP +次のオプションを使用して、JARファイルを作成、更新、抽出または表示する方法をカスタマイズします。 +.PP +e +.RS 4 +\fIentrypoint\fRオペランドで指定されるクラスを、実行可能JARファイルにバンドルされるスタンドアロンJavaアプリケーションのエントリ・ポイントに設定します。このオプションを使用すると、マニフェスト・ファイル内の\fBMain\-Class\fR属性値が作成またはオーバーライドされます。\fBe\fRオプションは、JARファイルの作成時(\fBc\fR)または更新時(\fBu\fR)に使用できます。 +.sp +たとえば、次のコマンドでは、\fBMain\&.jar\fRアーカイブが\fBMain\&.class\fRファイルとともに作成されますが、その際、マニフェスト内の\fBMain\-Class\fR属性値は\fBMain\fRに設定されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar cfe Main\&.jar Main Main\&.class\fR + +.fi +.if n \{\ +.RE +.\} +Java Runtime Environment (JRE)は、次のコマンドを実行して、このアプリケーションを直接呼び出すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-jar Main\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +あるパッケージ内にエントリ・ポイントのクラス名が含まれている場合、ドット(\&.)またはスラッシュ(/)のいずれかを区切り文字として使用できます。たとえば、\fBMain\&.class\fRが\fBmydir\fRという名前のパッケージに含まれている場合、エントリ・ポイントは次のいずれかの方法で指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar \-cfe Main\&.jar mydir/Main mydir/Main\&.class\fR +\fBjar \-cfe Main\&.jar mydir\&.Main mydir/Main\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fB注記\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +注意 +特定のマニフェストにも\fBMain\-Class\fR属性が含まれている場合に\fBm\fRオプションと\fBe\fRオプションの両方を同時に指定すると、\fBMain\-Class\fRの指定があいまいになります。このあいまいさによってエラーが発生し、\fBjar\fRコマンドの作成や更新の操作が終了します。 +T} +.TE +.sp 1 +.sp .5v +.RE +.RE +.PP +f +.RS 4 +\fIjarfile\fRオペランドで指定されたファイルを、作成(\fBc\fR)、更新(\fBu\fR)、抽出(\fBx\fR)または表示(\fBt\fR)されるJARファイルの名前に設定します。\fBf\fRオプションおよび\fIjarfile\fRオペランドを省略すると、\fBjar\fRコマンドに、\fBstdin\fRからのJARファイル名を受け入れるか(\fBx\fRおよび\fBt\fRの場合)、JARファイルを\fBstdout\fRに送信すること(\fBc\fRおよび\fBu\fRの場合)が指示されます。 +.RE +.PP +m +.RS 4 +(\fBMETA\-INF/MANIFEST\&.MF\fRのアーカイブにある) +\fBjar\fRコマンドのマニフェスト・ファイルの\fBmanifest\fRオペランドで指定されたファイルから、属性の名前と値のペアを含めます。\fBjar\fRコマンドは、同じ名前のエントリがすでに存在する場合を除き、属性の名前と値をJARファイルに追加します。同じ名前のエントリがすでに存在する場合、\fBjar\fRコマンドは属性の値を更新します。\fBm\fRオプションは、JARファイルの作成時(\fBc\fR)または更新時(\fBu\fR)に使用できます。 +.sp +デフォルトのマニフェスト・ファイルには含まれないマニフェストに、特別な目的の名前\-値の属性ペアを追加できます。たとえば、ベンダー情報、リリース情報、パッケージ・シーリングを指定する属性、またはJARにバンドルされたアプリケーションを実行可能にするための属性を追加できます。\fBm\fRオプションの使用例は、http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.htmlにある +プログラムのパッケージ化に関する項を参照してください。 +.RE +.PP +M +.RS 4 +マニフェスト・ファイル・エントリを作成しない(\fBc\fRおよび\fBu\fRの場合)か、またはマニフェスト・ファイル・エントリが存在する場合は削除します(\fBu\fRの場合)。\fBM\fRオプションは、JARファイルの作成時(\fBc\fR)または更新時(\fBu\fR)に使用できます。 +.RE +.PP +n +.RS 4 +JARファイルの作成(\fBc\fR)時に、このオプションは、コンテンツがpack200(1)コマンドのパックおよびアンパック操作の影響を受けないようにアーカイブを正規化します。この正規化を使用しない場合、署名付きJARの署名は無効になります。 +.RE +.PP +v +.RS 4 +詳細な出力を標準出力に生成します。例を参照してください。 +.RE +.PP +0 +.RS 4 +(ゼロ) ZIP圧縮を使用しないでJARファイルを作成(\fBc\fR)または更新(\fBu\fR)します。 +.RE +.PP +\-C \fIdir\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、このオプションは\fIfile\fRオペランドで指定されたファイルの処理中にディレクトリを一時的に変更します。この操作は、\fBtar\fRユーティリティの\fB\-C\fRオプションと同様になることを目的としています。たとえば、次のコマンドによって、\fBclasses\fRディレクトリに変更され、そのディレクトリから\fBmy\&.jar\fRに\fBBar\&.class\fRファイルが追加されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar uf my\&.jar \-C classes Bar\&.class\fR + +.fi +.if n \{\ +.RE +.\} +次のコマンドでは、\fBclasses\fRディレクトリに移動し、classesディレクトリ内のすべてのファイルを\fBmy\&.jar\fRに追加します(JARファイルには\fBclasses\fRディレクトリを作成しません)。次に元のディレクトリに戻ってから、\fBbin\fRディレクトリに移動し、\fBXyz\&.class\fRを\fBmy\&.jar\fRに追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar uf my\&.jar \-C classes \&. \-C bin Xyz\&.class\fR + +.fi +.if n \{\ +.RE +.\} +\fBclasses\fRに\fBbar1\fRファイルと\fBbar2\fRファイルが含まれている場合、前述のコマンドを実行した後、JARファイルには次のものが含まれます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% \fR\fB\fBjar tf my\&.jar\fR\fR +\fBMETA\-INF/\fR +\fBMETA\-INF/MANIFEST\&.MF\fR +\fBbar1\fR +\fBbar2\fR +\fBXyz\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定したJVMオプションを、JREがJARファイルを実行する際に使用するように設定します。JVMオプションは、java(1)コマンドのリファレンス・ページで説明されています。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。 +.RE +.SH "オペランド" +.PP +次のオペランドは、\fBjar\fRコマンドで認識されます。 +.PP +\fIfile\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、\fIfile\fRオペランドは、アーカイブに追加する必要のあるファイルまたはディレクトリのパスと名前を定義します。JARファイルの抽出(\fBx\fR)またはコンテンツのリスト(\fBt\fR)時に、\fIfile\fRオペランドは抽出またはリストするファイルのパスと名前を定義します。少なくとも1つの有効なファイルまたはディレクトリを指定する必要があります。複数の\fIfile\fRオペランドを空白で区切ります。\fIentrypoint\fR、\fIjarfile\fRまたは\fImanifest\fRオペランドが使用される場合は、その後に\fIfile\fRオペランドを指定する必要があります。 +.RE +.PP +\fIentrypoint\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、\fIentrypoint\fRオペランドは、実行可能JARファイルにバンドルされているスタンドアロンJavaアプリケーションのエントリ・ポイントとなるクラスの名前を定義します。\fBe\fRオプションが存在する場合は\fIentrypoint\fRオペランドを指定する必要があります。 +.RE +.PP +\fIjarfile\fR +.RS 4 +作成(\fBc\fR)、更新(\fBu\fR)、抽出(\fBx\fR)または表示(\fBt\fR)するファイルの名前を定義します。\fBf\fRオプションが存在する場合は\fIjarfile\fRオペランドを指定する必要があります。\fBf\fRオプションおよび\fIjarfile\fRオペランドを省略すると、\fBjar\fRコマンドに、\fBstdin\fRからのJARファイル名を受け入れるか(\fBx\fRおよび\fBt\fRの場合)、JARファイルを\fBstdout\fRに送信すること(\fBc\fRおよび\fBu\fRの場合)が指示されます。 +.sp +JARファイルを索引付け(\fBi\fR)する場合は、\fBf\fRオプションを指定しないで\fIjarfile\fRオペランドを指定します。 +.RE +.PP +\fImanifest\fR +.RS 4 +JARファイルの作成(\fBc\fR)または更新(\fBu\fR)時に、\fImanifest\fRオペランドはJARファイルの\fBMANIFEST\&.MF\fRに含める属性の名前と値を持つ既存のマニフェスト・ファイルを定義します。\fBf\fRオプションが存在する場合は\fImanifest\fRオペランドを指定する必要があります。 +.RE +.PP +\fI@arg\-file\fR +.RS 4 +\fBjar\fRコマンドを短縮または簡素化するには、別のテキスト・ファイル内の引数を指定し、接頭辞としてアットマーク(@)を付けて\fBjar\fRコマンドに渡すことができます。\fBjar\fRコマンドは、アットマーク文字で始まる引数を見つけると、そのファイルの内容を展開して引数リストに挿入します。 +.sp +引数ファイルには、\fBjar\fRコマンドのオプションと引数(引数ファイルをサポートしない起動ツールに渡される\fB\-J\fRオプションを除く)を含めることができます。ファイル内の引数は、空白または改行文字で区切ることができます。引数ファイル内のファイル名は、\fBjar\fRコマンドを実行できる現在のディレクトリに対して相対的であり、引数ファイルの場所に対しては相対的ではありません。通常はオペレーティング・システム・シェルによって展開されるアスタリスク(*)などのワイルドカードは展開されません。 +.sp +次の例は、\fBfind\fRコマンドによる現在のディレクトリ出力からのファイル名で\fBclasses\&.list\fRファイルを作成する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBfind \&. \-name \*(Aq*\&.class\*(Aq \-print > classes\&.list\fR + +.fi +.if n \{\ +.RE +.\} +\fBjar\fRコマンドを実行し、\fI@arg\-file\fR構文を使用して\fBclasses\&.list\fRファイルを渡すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar cf my\&.jar @classes\&.list\fR + +.fi +.if n \{\ +.RE +.\} +引数ファイルはパスを指定できますが、相対パスが記述された引数ファイル内のすべてのファイル名は、渡されたパスに対して相対的ではなく、\fBjar\fRコマンドの現在の作業ディレクトリに相対的となります。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar @dir/classes\&.list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "注意" +.PP +\fBe\fR、\fBf\fRおよび\fBm\fRオプションは、\fIentrypoint\fR、\fIjarfile\fRおよび\fImanifest\fRオペランドと同じ順序でコマンド行に出現する必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjar cmef myManifestFile MyMainClass myFile\&.jar *\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.SH "例" +.PP +\fB例 1 \fR冗長な出力による現在のディレクトリからのすべてのファイルの追加 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% ls\fR +\fB1\&.au Animator\&.class monkey\&.jpg\fR +\fB2\&.au Wave\&.class spacemusic\&.au\fR +\fB3\&.au at_work\&.gif\fR + +\fB% jar cvf bundle\&.jar *\fR +\fBadded manifest\fR +\fBadding: 1\&.au(in = 2324) (out= 67)(deflated 97%)\fR +\fBadding: 2\&.au(in = 6970) (out= 90)(deflated 98%)\fR +\fBadding: 3\&.au(in = 11616) (out= 108)(deflated 99%)\fR +\fBadding: Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fR +\fBadding: Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fR +\fBadding: at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fR +\fBadding: monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fR +\fBadding: spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRサブディレクトリからのファイルの追加 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% ls \-F\fR +\fBaudio/ classes/ images/\fR +\fB% jar cvf bundle\&.jar audio classes images\fR +\fBadded manifest\fR +\fBadding: audio/(in = 0) (out= 0)(stored 0%)\fR +\fBadding: audio/1\&.au(in = 2324) (out= 67)(deflated 97%)\fR +\fBadding: audio/2\&.au(in = 6970) (out= 90)(deflated 98%)\fR +\fBadding: audio/3\&.au(in = 11616) (out= 108)(deflated 99%)\fR +\fBadding: audio/spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fR +\fBadding: classes/(in = 0) (out= 0)(stored 0%)\fR +\fBadding: classes/Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fR +\fBadding: classes/Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fR +\fBadding: images/(in = 0) (out= 0)(stored 0%)\fR +\fBadding: images/monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fR +\fBadding: images/at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fR + +\fB% ls \-F\fR +\fBaudio/ bundle\&.jar classes/ images/\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRJARのコンテンツのリスト +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% jar tf bundle\&.jar\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMETA\-INF/\fR +\fBMETA\-INF/MANIFEST\&.MF\fR +\fBaudio/1\&.au\fR +\fBaudio/2\&.au\fR +\fBaudio/3\&.au\fR +\fBaudio/spacemusic\&.au\fR +\fBclasses/Animator\&.class\fR +\fBclasses/Wave\&.class\fR +\fBimages/monkey\&.jpg\fR +\fBimages/at_work\&.gif\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fR索引の追加 +.RS 4 +株式取引のアプリケーションの相互依存クラスを、\fBmain\&.jar\fR、\fBbuy\&.jar\fRおよび\fBsell\&.jar\fRの3つのJARファイルに分割する場合、\fBi\fRオプションを使用します。\fBmain\&.jar\fRマニフェスト内の\fBClass\-Path\fR属性を指定する場合、\fBi\fRオプションを使用して、アプリケーションのクラス・ロードの速度を向上できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBClass\-Path: buy\&.jar sell\&.jar\fR +\fBjar i main\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +\fBINDEX\&.LIST\fRファイルが\fBMETA\-INF\fRディレクトリに挿入されます。これにより、アプリケーションのクラス・ローダーによってクラスまたはリソースの検索が行われるときに、指定したJARファイルがダウンロードされるようになります。 +.sp +アプリケーションのクラス・ローダーは、このファイルに格納されている情報を使用して、効率的にクラスをロードします。ディレクトリをコピーするには、最初に\fBdir1\fR内のファイルを\fBstdout\fRに圧縮してから、\fBstdin\fRから\fBdir2\fRにパイプラインを作成して抽出します(\fB\-f\fRオプションは両方の\fBjar\fRコマンドで省略します)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB(cd dir1; jar c \&.) | (cd dir2; jar x)\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +pack200(1)\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.htmlにある +JavaチュートリアルのJARに関する項 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jarsigner.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jarsigner.1 new file mode 100755 index 0000000..2f8b163 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jarsigner.1 @@ -0,0 +1,1078 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jarsigner +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: セキュリティ・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jarsigner" "1" "2013å¹´11月21日" "JDK 8" "セキュリティ・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jarsigner \- Javaアーカイブ(JAR)ファイルに対して署名および検証を行います。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner\fR [ \fIoptions\fR ] \fIjar\-file\fR \fIalias\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner\fR \fB\-verify\fR [ \fIoptions\fR ] \fIjar\-file\fR [\fIalias \&.\&.\&.\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\-verify +.RS 4 +\fB\-verify\fRオプションでは、JARファイル名の後に0個以上のキーストア別名を指定できます。\fB\-verify\fRオプションが指定された場合、\fBjarsigner\fRコマンドでは、JARファイル内の各署名付きエンティティの検証に使用される証明書が、いずれかのキーストア別名に一致することをチェックします。別名は、\fB\-keystore\fRで指定されたキーストア内またはデフォルトのキーストア内に定義されます。 +.sp +\fB\-strict\fRオプションも指定した場合、\fBjarsigner\fRコマンドにより重大な警告が検出されると、メッセージ「jarが検証されました。署名者エラー」が表示されます。 +.RE +.PP +\fIjar\-file\fR +.RS 4 +署名されるJARファイル。 +.sp +\fB\-strict\fRオプションも指定した場合、\fBjarsigner\fRコマンドにより重大な警告が検出されると、メッセージ「jarは署名されました \- 署名者エラーがあります。」というメッセージが表示されます。 +.RE +.PP +\fIalias\fR +.RS 4 +別名は、\fB\-keystore\fRで指定されたキーストア内またはデフォルトのキーストア内に定義されます。 +.RE +.SH "説明" +.PP +\fBjarsigner\fRツールには、次の2つの目的があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javaアーカイブ(JAR)ファイルに署名する目的。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +署名付きJARファイルの署名と整合性を検証する目的。 +.RE +.PP +JAR機能を使用すると、クラス・ファイル、イメージ、サウンドおよびその他のデジタル・データを単一のファイルにパッケージ化できるので、ファイルを迅速かつ容易に配布できます。\fBjar\fRという名前のツールを使用して、開発者はJARファイルを作成できます。(技術的な観点から言えば、すべてのZIPファイルもJARファイルとみなすことができます。ただし、\fBjar\fRコマンドによって作成されたJARファイル、または\fBjarsigner\fRコマンドによって処理されたJARファイルには、\fBMETA\-INF/MANIFEST\&.MF\fRファイルも含まれています。) +.PP +デジタル署名は、なんらかのデータ(署名の対象となるデータ)、およびエンティティ(人、会社など)の秘密鍵から計算されるビットの文字列です。手書きの署名同様、デジタル署名には多くの利点があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +署名の生成に使用された秘密鍵に対応する公開鍵を使用する計算によって、それが本物であることを検証できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +秘密鍵が他人に知られない限り、デジタル署名の偽造は不可能です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +これは、署名が付いたデータの機能であり、他のデータの署名となるように要求できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +署名付きデータは変更できません。データが変更された場合、署名によって本物であると検証できません。 +.RE +.PP +ファイルに対してエンティティの署名を生成するには、まず、エンティティは、そのエンティティに関連する公開鍵/秘密鍵のペアと、公開鍵を認証する1つ以上の証明書を持つ必要があります。証明書とは、あるエンティティからのデジタル署名付きの文書で、別のエンティティの公開鍵が特定の値を持つことを示しています。 +.PP +\fBjarsigner\fRコマンドは、キーストアからの鍵と証明書情報を使用して、JARファイルのデジタル署名を生成します。キーストアは、秘密鍵、および対応する公開鍵を認証する、秘密鍵に関連したX\&.509証明書チェーンのデータベースです。\fBkeytool\fRコマンドを使用して、キーストアを作成および管理します。 +.PP +\fBjarsigner\fRコマンドでは、エンティティの秘密鍵を使用して署名を生成します。署名付きJARファイルには、特に、ファイルへの署名に使用する秘密鍵に対応する公開鍵のキーストアからの証明書のコピーが含まれます。\fBjarsigner\fRコマンドでは、内部(署名ブロック・ファイル内)の証明書を使用して、署名付きJARファイルのデジタル署名を検証できます。 +.PP +\fBjarsigner\fRコマンドでは、署名証明書の有効期間中にJARファイルが署名されたされたかどうかをシステムやデプロイヤ(Java Plug\-inを含む)がチェックできる、タイムスタンプを含む署名を生成できます。さらに、APIを使用すると、アプリケーションでタイムスタンプ情報を取得できます。 +.PP +現時点では、\fBjarsigner\fRコマンドでは、\fBjar\fRコマンドまたはZIPファイルによって作成されたJARファイルのみに署名できます。JARファイルはZIPファイルと同じですが、JARファイルには\fBMETA\-INF/MANIFEST\&.MF\fRファイルも含まれている点が異なります。\fBMETA\-INF/MANIFEST\&.MF\fRファイルは、\fBjarsigner\fRコマンドによってZIPファイルに署名する際に作成されます。 +.PP +デフォルトの\fBjarsigner\fRコマンドの動作では、JARまたはZIPファイルに署名します。\fB\-verify\fRオプションを使用して、署名付きJARファイルを検証します。 +.PP +\fBjarsigner\fRコマンドは、署名または検証の後に署名者の証明書の検証も試行します。検証エラーまたはその他の問題が発生すると、コマンドにより警告メッセージが生成されます。\fB\-strict\fRオプションを指定した場合、コマンドにより重大な警告がエラーとして処理されます。エラーと警告を参照してください。 +.SS "キーストアの別名" +.PP +キーストアのすべてのエンティティは、一意の別名を使用してアクセスされます。 +.PP +\fBjarsigner\fRコマンドを使用してJARファイルに署名するときは、署名の生成に必要な秘密鍵を含むキーストア・エントリの別名を指定する必要があります。たとえば、次のコマンドでは、\fBworking\fRディレクトリの\fBmystore\fRという名前のキーストアに含まれる別名\fBduke\fRに関連付けられた秘密鍵を使用して、\fBMyJARFile\&.jar\fRという名前のJARファイルに署名します。出力ファイルは指定されていないため、\fBMyJARFile\&.jar\fRは署名付きのJARファイルによって上書きされます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore \-storepass <keystore password>\fR +\fB \-keypass <private key password> MyJARFile\&.jar duke\fR + +.fi +.if n \{\ +.RE +.\} +.PP +キーストアはパスワードで保護されているので、ストアのパスワードを指定する必要があります。コマンド行で指定しないと、入力を求められます。同様に、秘密鍵もキーストア内でパスワードによって保護されているため、秘密鍵のパスワードを指定する必要があります。コマンド行でパスワードを指定していない場合、または指定したパスワートが保存されているパスワードと同じではない場合は、パスワードの入力を求められます。 +.SS "キーストアの場所" +.PP +\fBjarsigner\fRコマンドには、使用するキーストアのURLを指定する\fB\-keystore\fRオプションがあります。キーストアはデフォルトで、\fBuser\&.home\fRシステム・プロパティで決まるユーザーのホーム・ディレクトリの\fB\&.keystore\fRという名前のファイル内に格納されます。 +.PP +Oracle Solarisシステムの場合、\fBuser\&.home\fRは、ユーザーのホーム・ディレクトリにデフォルト設定されます。 +.PP +\fB\-keystore\fRオプションからの入力ストリームは、\fBKeyStore\&.load\fRメソッドに渡されます。URLとして\fBNONE\fRが指定されている場合は、nullのストリームが\fBKeyStore\&.load\fRメソッドに渡されます。\fBNONE\fRは、\fBKeyStore\fRクラスがファイルベースではない場合、たとえば、ハードウェア・トークン・デバイスに置かれている場合に指定します。 +.SS "キーストアの実装" +.PP +\fBjava\&.security package\fRで提供されている\fBKeyStore\fRクラスは、キーストア内の情報へのアクセスおよび情報の変更を行うための、明確に定義された多くのインタフェースを提供します。複数の異なる固定実装を指定することができ、各実装は特定のタイプのキーストアを対象とします。 +.PP +現在、キーストアの実装を使用する2つのコマンド行ツール(\fBkeytool\fRと\fBjarsigner\fR)、およびポリシー・ツールという名前の1つのGUIベースのツールがあります。\fBKeyStore\fRクラスは公開されているため、JDKユーザーは、それを使用する他のセキュリティ・アプリケーションを書き込むことができます。 +.PP +Oracleが提供する組込みのデフォルトの実装があります。これは、JKSという名前の独自のキーストア・タイプ(形式)を使用するもので、キーストアをファイルとして実装しています。組込みの実装では、各秘密鍵は個別のパスワードによって保護され、キーストア全体の整合性は(秘密鍵とは別の)パスワードによって保護されます。 +.PP +キーストアの実装はプロバイダベースで、つまり、\fBKeyStore\fRクラスにより提供されるアプリケーション・インタフェースは、サービス・プロバイダ・インタフェース(SPI)に関して実装されます。対応する\fBKeystoreSpi\fR抽象クラスがあり、これも\fBjava\&.security package\fRに含まれています。このクラスが、プロバイダが実装する必要のあるサービス・プロバイダ・インタフェースのメソッドを定義しています。ここで、プロバイダとは、Java Security APIによってアクセス可能なサービスのサブセットに対し、その固定実装を提供するパッケージまたはパッケージの集合のことです。キーストアの実装を提供するには、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/HowToImplAProvider\&.htmlにある +Java暗号化アーキテクチャのプロバイダの実装方法で説明しているように、クライアントはプロバイダを実装し、\fBKeystoreSpi\fRサブクラスの実装を提供する必要があります。 +.PP +アプリケーションでは、\fBKeyStore\fRクラスの\fBgetInstance\fRファクトリ・メソッドを使用して、様々なプロバイダから異なるタイプのキーストアの実装を選択できます。キーストアのタイプは、キーストア情報の格納形式とデータ形式を定義するとともに、キーストア内の秘密鍵とキーストア自体の整合性を保護するために使用されるアルゴリズムを定義します。異なるタイプのキーストアの実装には、互換性はありません。 +.PP +\fBjarsigner\fRおよび\fBpolicytool\fRコマンドは、URLを使用して指定できる任意の場所からファイルベースのキーストアを読み取ることができます。また、これらのコマンドは、Windows上のMSCAPIおよびすべてのプラットフォーム上のPKCS11で提供されるような非ファイルベースのキーストアを読み取ることができます。 +.PP +\fBjarsigner\fRコマンドおよび\fBkeytool\fRコマンドの場合、\fB\-storetype\fRオプションを使用して、コマンド行でキーストアのタイプを指定できます。ポリシー・ツールの場合、\fB「キーストア」\fRメニューの\fB「編集」\fRコマンドを使用して、キーストアのタイプを指定できます。 +.PP +ユーザーがキーストアのタイプを明示的に指定しなかった場合、セキュリティ・プロパティ・ファイルで指定された\fBkeystore\&.type\fRプロパティの値に基づいて、ツールによってキーストアの実装が選択されます。このセキュリティ・プロパティ・ファイルは\fBjava\&.security\fRと呼ばれ、JDKセキュリティ・プロパティ・ディレクトリ\fBjava\&.home/lib/security\fR内に存在しています。ここで、\fBjava\&.home\fRは実行時環境のディレクトリです。\fBjre\fRディレクトリは、JDKまたはJava Runtime Environment (JRE)の最上位のディレクトリにあります。 +.PP +各ツールは、\fBkeystore\&.type\fRの値を取得し、そのタイプのキーストアを実装しているプロバイダが見つかるまで、インストールされているすべてのプロバイダを調べます。目的のプロバイダが見つかると、そのプロバイダからのキーストアの実装を使用します。 +.PP +\fBKeyStore\fRクラスに定義されているstaticメソッド\fBgetDefaultType\fRを使用すると、アプリケーションやアプレットから\fBkeystore\&.type\fRプロパティの値を取得できます。次のコードの行では、\fBkeystore\&.type property\fRで指定された、デフォルトのキーストア・タイプのインスタンスを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBKeyStore keyStore = KeyStore\&.getInstance(KeyStore\&.getDefaultType());\fR + +.fi +.if n \{\ +.RE +.\} +.PP +デフォルトのキーストア・タイプは、\fBjks\fR +(Oracleが提供する独自のタイプのキーストアの実装)です。これは、セキュリティ・プロパティ・ファイル内の次の行によって指定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=jks\fR + +.fi +.if n \{\ +.RE +.\} +.PP +キーストアのタイプの指定では、大文字と小文字は区別されません。たとえば、\fBJKS\fRは\fBjks\fRと同じになります。 +.PP +ツールでデフォルト以外のキーストアの実装を使用するには、その行を変更して別のキーストアのタイプを指定します。たとえば、\fBpkcs12\fRと呼ばれるキーストアのタイプのキーストアの実装を提供するプロバイダ・パッケージがある場合、行を次のように変更します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=pkcs12\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB注意:\fR +PKCS 11プロバイダ・パッケージを使用する場合、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/p11guide\&.htmlにある +Java PKCS #11リファレンス・ガイドの「KeyTool」および「JarSigner」を参照してください。 +.SS "サポートされるアルゴリズム" +.PP +デフォルトで、\fBjarsigner\fRコマンドでは次のいずれかのアルゴリズムを使用してJARファイルに署名します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHA1ダイジェスト・アルゴリズムを使用したデジタル署名アルゴリズム(DSA) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHA256ダイジェスト・アルゴリズムを使用したRSAアルゴリズム。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHA256と楕円曲線デジタル署名アルゴリズム(ECDSA)を使用した楕円曲線(EC)暗号方式アルゴリズム +.RE +.PP +署名者の公開鍵と秘密鍵がDSA鍵である場合、\fBjarsigner\fRは\fBSHA1withDSA\fRアルゴリズムを使用してJARファイルに署名します。署名者の鍵がRSA鍵である場合、\fBjarsigner\fRは\fBSHA256withRSA\fRアルゴリズムを使用してJARファイルに署名しようとします。署名者の鍵がEC鍵である場合、\fBjarsigner\fRは\fBSHA256withECDSA\fRアルゴリズムを使用してJARファイルに署名します。 +.PP +これらのデフォルトの署名アルゴリズムは、\fB\-sigalg\fRオプションを使用してオーバーライドできます。 +.SS "署名付きJARファイル" +.PP +\fBjarsigner\fRコマンドを使用してJARファイルに署名する場合、出力される署名付きJARファイルは入力JARファイルと同じですが、次の2つの追加ファイルがMETA\-INFディレクトリに置かれる点が異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\&.SF\fR拡張子の付いた署名ファイル +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\&.DSA\fR、\fB\&.RSA\fRまたは\fB\&.EC\fR拡張子の付いた署名ブロック・ファイル +.RE +.PP +これら2つのファイルのベース・ファイル名は、\fB\-sigFile\fRオプションの値から作成されます。たとえば、オプションが\fB\-sigFile MKSIGN\fRの場合、ファイルは\fBMKSIGN\&.SF\fRおよび\fBMKSIGN\&.DSA\fRという名前になります。 +.PP +コマンドラインで\fB\-sigfile\fRオプションを指定しなかった場合、\fB\&.SF\fRファイルと\fB\&.DSA\fRファイルのベース・ファイル名は、コマンドラインで指定された別名の先頭の8文字をすべて大文字に変換したものになります。別名が8文字未満の場合は、別名がそのまま使用されます。別名に、署名ファイル名で使用できない文字が含まれている場合、ファイル名の作成時に、該当する文字が下線(_)文字に変換されます。有効な文字は、アルファベット、数字、下線およびハイフンです。 +.PP +署名ファイル +.PP +署名ファイル(\fB\&.SF\fRファイル)は、\fBjarsigner\fRコマンドを使用してファイルに署名する際にJARファイルに常に含まれるマニフェスト・ファイルと似ています。JARファイルに含まれているソース・ファイルごとに、\fB\&.SF\fRファイルには、マニフェスト・ファイルにあるような、次に示す3つの行があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ファイル名 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ダイジェスト・アルゴリズム(SHA)の名前 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +SHAダイジェストの値 +.RE +.PP +マニフェスト・ファイルでは、各ソース・ファイルのSHAダイジェストの値は、ソース・ファイルのバイナリ・データのダイジェスト(ハッシュ)になります。\fB\&.SF\fRファイルでは、指定されたソース・ファイルのダイジェストの値は、ソース・ファイルのマニフェスト・ファイル内のその3行のハッシュになります。 +.PP +署名ファイルには、デフォルトで、マニフェスト・ファイル全体のハッシュが格納されたヘッダーが含まれています。ヘッダーにはマニフェスト・ヘッダーのハッシュも含まれています。ヘッダーが存在すると、検証の最適化が有効になります。JARファイルの検証を参照してください。 +.PP +署名ブロック・ファイル +.PP +\fB\&.SF\fRファイルには署名が付けられ、署名は署名ブロック・ファイルに置かれます。このファイルには、署名に使用された秘密鍵に対応する公開鍵を認証するキーストアからの証明書または証明書チェーンも、内部でエンコードされて含まれています。ファイルの拡張子は、使用されるダイジェスト・アルゴリズムに応じて、\fB\&.DSA\fR、\fB\&.RSA\fRまたは\fB\&.EC\fRになります。 +.SS "署名タイムスタンプ" +.PP +\fBjarsigner\fRコマンドでは、JARファイルの署名時に署名タイムスタンプを生成および保存できます。さらに、\fBjarsigner\fRは代替署名機構をサポートします。この動作は省略可能で、署名時に次の各オプションによって制御されます。オプションを参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-tsa \fR\fB\fIurl\fR\fR +\fB\-tsacert \fR\fB\fIalias\fR\fR +\fB\-altsigner \fR\fB\fIclass\fR\fR +\fB\-altsignerpath \fR\fB\fIclasspathlist\fR\fR +\fB\-tsapolicyid \fR\fB\fIpolicyid\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SS "JARファイルの検証" +.PP +JARファイルの検証が成功するのは、署名が有効であり、かつ署名の生成以降にJARファイル内のどのファイルも変更されていない場合です。JARファイルの検証は、次の手順で行われます。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +\fB\&.SF\fRファイルの署名を検証します。 +.sp +検証では、各署名ブロック(\fB\&.DSA\fR)ファイルに格納された署名が、証明書(または証明書チェーン)も\fB\&.DSA\fRファイルに示される公開鍵に対応する秘密鍵を使用して生成されたことを確認します。また、署名が対応する署名(\fB\&.SF\fR)ファイルの有効な署名であることが確認され、それにより、\fB\&.SF\fRファイルが改ざんされていないことも確認されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +\fB\&.SF\fRファイル内の各エントリに示されるダイジェストを、マニフェスト内の対応する各セクションと突きあわせて検証します。 +.sp +\fB\&.SF\fRファイルには、マニフェスト・ファイル全体のハッシュが格納されたヘッダーがデフォルトで含まれています。ヘッダーが存在する場合、検証では、ヘッダー内のハッシュがマニフェスト・ファイルのハッシュと一致するかどうかを確認するためにチェックできます。一致する場合、検証は次の手順に進みます。 +.sp +一致しない場合、\fB\&.SF\fRファイル内の各ソース・ファイル情報セクションのハッシュが、マニフェスト・ファイル内の対応するセクションのハッシュと一致することを確認するために、あまり最適化されていない検証が必要になります。署名ファイルを参照してください。 +.sp +\fB\&.SF\fRファイルのヘッダーに格納されたマニフェスト・ファイルのハッシュが、現在のマニフェスト・ファイルのハッシュに一致しない理由の1つは、署名および\fB\&.SF\fRファイルの生成後に、(\fBjar\fRツールを使用して)1つ以上のファイルがJARファイルに追加されたことです。\fBjar\fRツールを使用してファイルを追加した場合、新しいファイル用のセクションが追加されることにより、マニフェスト・ファイルは変更されますが、\fB\&.SF\fRファイルは変更されません。検証がまだ成功しているとみなされるのは、署名の生成以降にJARファイル内のどのファイルも変更されていない場合です。これが発生するのは、\fB\&.SF\fRファイルのヘッダー以外のセクションのハッシュが、マニフェスト・ファイル内の対応するセクションのハッシュと一致する場合です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +\fB\&.SF\fRファイル内にエントリを持つJARファイル内の各ファイルを読み取ります。読取り中にファイルのダイジェストを計算し、結果をマニフェスト・セクション内のこのファイルのダイジェストと比較します。ダイジェストは同じである必要があり、そうでない場合は検証が失敗します。 +.sp +検証プロセス中になんらかの重大な検証エラーが発生した場合、そのプロセスは停止され、セキュリティ例外がスローされます。\fBjarsigner\fRコマンドでは、例外を捕捉および表示します。 +.RE +.PP +\fB注意:\fR +追加の警告(または、\fB\-strict\fRオプションを指定した場合はエラー)はすべて読む必要があります。同様に、証明が信頼できるかを決定するために、(\fB\-verbose\fRおよび\fB\-certs\fRオプションを指定して)証明書の内容も読む必要があります。 +.SS "1つのJARファイルを対象とする複数の署名" +.PP +次のように、\fBjarsigner\fRコマンドをファイルで複数回実行し、実行のたびに異なるユーザーの別名を指定することによって、1つのJARファイルに複数のユーザーの署名を付けることができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner myBundle\&.jar susan\fR +\fBjarsigner myBundle\&.jar kevin\fR + +.fi +.if n \{\ +.RE +.\} +.PP +JARファイルが複数回署名されている場合、そのJARファイルには、複数の\fB\&.SF\fRファイルと\fB\&.DSA\fRファイルが含まれており、1回の署名に対して1つのペアとなります。前述の例では、出力JARファイルには、次の名前のファイルが含まれています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBSUSAN\&.SF\fR +\fBSUSAN\&.DSA\fR +\fBKEVIN\&.SF\fR +\fBKEVIN\&.DSA\fR +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +次の各項では、様々な\fBjarsigner\fRオプションについて説明します。次の標準に注意してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +どのオプション名にも先頭にマイナス記号(\-)が付きます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションは任意の順序で指定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +イタリックまたは下線付きの項目(オプションの値)の実際の値は、指定する必要があります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-storepass\fR、\fB\-keypass\fR、\fB\-sigfile\fR、\fB\-sigalg\fR、\fB\-digestalg\fR、\fB\-signedjar\fRおよびTSA関連のオプションを使用できるのは、JARファイルに署名する場合のみです。署名付きJARファイルを検証する場合ではありません。\fB\-keystore \fRオプションは、JARファイルの署名および検証に関連します。また、別名は、JARファイルの署名および検証時に指定します。 +.RE +.PP +\-keystore \fIurl\fR +.RS 4 +キーストアの場所を示すURLを指定します。これにより、\fBuser\&.home\fRシステム・プロパティで決定されたユーザーのホーム・ディレクトリ内のファイル\fB\&.keystore\fRにデフォルト設定されます。 +.sp +キーストアは署名時には必要です。デフォルトのキーストアが存在しない場合、またはデフォルト以外のキーストアを使用する場合は、キーストアを明示的に指定する必要があります。 +.sp +検証するときはキーストアは必要ありません。ただし、キーストアが指定されているか、あるいはデフォルトのキーストアが存在していて、さらに\fB\-verbose\fRオプションも指定されていた場合、JARファイルの検証に使用される証明書がそのキーストアに1つでも含まれているかどうかに関する追加情報が出力されます。 +.sp +\fB\-keystore\fR引数には、URLではなくファイル名とパスを指定でき、この場合、ファイル: URLと同じように処理されます。たとえば、次にように指定すると同等になります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-keystore \fR\fB\fIfilePathAndName\fR\fR +\fB\-keystore file:\fR\fB\fIfilePathAndName\fR\fR + +.fi +.if n \{\ +.RE +.\} +(JREの\fB$JAVA_HOME/lib/security directory\fRにある) +\fBjava\&.security\fRセキュリティ・プロパティ・ファイル内でSun PKCS #11プロバイダが構成された場合、\fBkeytool\fRおよび\fBjarsigner\fRツールはPKCS#11トークンに基づいて動作できます。次のオプションを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-keystore NONE\fR +\fB\-storetype PKCS11\fR + +.fi +.if n \{\ +.RE +.\} +たとえば、次のコマンドは、構成されたPKCS#11トークンの内容を一覧表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-keystore NONE \-storetype PKCS11 \-list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-storetype \fIstoretype\fR +.RS 4 +インスタンスを生成するキーストアのタイプを指定します。デフォルトのキーストア・タイプは、セキュリティ・プロパティ・ファイル内の\fBkeystore\&.type\fRプロパティの値で指定されたタイプです。この値は、\fBjava\&.security\&.KeyStore\fRのstatic +\fBgetDefaultType\fRメソッドによって返されます。 +.sp +\fB\-storepass\fRオプションを使用して、PCKS #11トークンのPINを指定することもできます。何も指定しない場合、\fBkeytool\fRおよび\fBjarsigner\fRコマンドによって、トークンPINの指定を求められます。トークンに保護された認証パス(専用のPINパッドや生体読取り機など)がある場合、\fB\-protected\fRオプションを指定する必要がありますが、パスワード・オプションは指定できません。 +.RE +.PP +\-storepass[:env | :file] \fIargument\fR +.RS 4 +キーストアにアクセスするのに必要なパスワードを指定します。これが必要なのは、JARファイルに署名を付けるときのみです(検証するときには不要です)。その場合、\fB\-storepass\fRオプションをコマンド行で指定しないと、パスワードの入力を求められます。 +.sp +修飾子\fBenv\fRまたは\fBfile\fRが指定されていない場合、パスワードの値は\fIargument\fRになります。それ以外の場合、パスワードは次のようにして取得されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBenv\fR: +\fBargument\fRという名前の環境変数からパスワードを取得します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBfile\fR: +\fBargument\fRという名前のファイルからパスワードを取得します。 +.RE +.sp +\fB注意:\fR +テストを目的とする場合またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。 +.RE +.PP +\-keypass [:env | :file] \fIargument\fR +.RS 4 +コマンド行で指定された別名に対応するキーストア・エントリの秘密鍵を保護するのに使用するパスワードを指定します。\fBjarsigner\fRを使用してJARファイルに署名を付けるときは、パスワードが必要です。コマンド行でパスワードが指定されておらず、必要なパスワードがストアのパスワードと異なる場合は、パスワードの入力を求められます。 +.sp +修飾子\fBenv\fRまたは\fBfile\fRが指定されていない場合、パスワードの値は\fBargument\fRになります。それ以外の場合、パスワードは次のようにして取得されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBenv\fR: +\fBargument\fRという名前の環境変数からパスワードを取得します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBfile\fR: +\fBargument\fRという名前のファイルからパスワードを取得します。 +.RE +.sp +\fB注意:\fR +テストを目的とする場合またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。 +.RE +.PP +\-sigfile \fIfile\fR +.RS 4 +生成された\fB\&.SF\fRファイルおよび\fB\&.DSA\fRファイルに使用するベース・ファイル名を指定します。たとえば、ファイルが\fBDUKESIGN\fRの場合、生成される\fB\&.SF\fRおよび\fB\&.DSA\fRファイルは、\fBDUKESIGN\&.SF\fRおよび\fBDUKESIGN\&.DSA\fRという名前で、署名付きJARファイルの\fBMETA\-INF\fRディレクトリに格納されます。 +.sp +ファイル内の文字は、セット\fBa\-zA\-Z0\-9_\-\fRから指定される必要があります。アルファベット、数字、下線およびハイフン文字のみを使用できます。\fB\&.SF\fRおよび\fB\&.DSA\fRのファイル名では、小文字はすべて大文字に変換されます。 +.sp +コマンド行で\fB\-sigfile\fRオプションを指定しなかった場合、\fB\&.SF\fRファイルと\fB\&.DSA\fRファイルのベース・ファイル名は、コマンド行で指定された別名の先頭の8文字をすべて大文字に変換したものになります。別名が8文字未満の場合は、別名がそのまま使用されます。別名に、署名ファイル名で無効な文字が含まれている場合、ファイル名を作成するために、該当する文字が下線(_)文字に変換されます。 +.RE +.PP +\-sigalg \fIalgorithm\fR +.RS 4 +JARファイルの署名に使用する署名アルゴリズムの名前を指定します。 +.sp +標準的な署名アルゴリズム名のリストは、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppAにある +Java Cryptography Architecture (JCA)リファレンス・ガイドの「付録A: 標準名」を参照してください。 +.sp +このアルゴリズムには、JARファイルの署名に使用する秘密鍵との互換性が必要です。このオプションを指定しない場合、秘密鍵のタイプに応じて、\fBSHA1withDSA\fR、\fBSHA256withRSA\fRまたは\fBSHA256withECDSA\fRが使用されます。指定されたアルゴリズムの実装を提供するプロバイダが静的にインストールされているか、\fB\-providerClass\fRオプションを使用してそのようなプロバイダをユーザーが指定する必要があります。そうでない場合、コマンドは失敗します。 +.RE +.PP +\-digestalg \fIalgorithm\fR +.RS 4 +JARファイルのエントリをダイジェストする際に使用するメッセージ・ダイジェスト・アルゴリズムの名前を指定します。 +.sp +標準的なメッセージ・ダイジェスト・アルゴリズム名のリストは、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppAにある +Java Cryptography Architecture (JCA)リファレンス・ガイドの「付録A: 標準名」を参照してください。 +.sp +このオプションを指定しない場合、\fBSHA256\fRが使用されます。指定されたアルゴリズムの実装を提供するプロバイダが静的にインストールされているか、\fB\-providerClass\fRオプションを使用してそのようなプロバイダをユーザーが指定する必要があります。そうでない場合、コマンドは失敗します。 +.RE +.PP +\-certs +.RS 4 +コマンド行で、\fB\-certs\fRオプションを\fB\-verify\fRおよび\fB\-verbose\fRオプションとともに指定した場合、JARファイルの各署名者の証明書情報が出力に含まれます。この情報には、署名者の公開鍵を証明する証明書(\fB\&.DSA\fRファイルに格納)のタイプの名前が含まれ、証明書がX\&.509証明書(\fBjava\&.security\&.cert\&.X509Certificate\fRのインスタンス)の場合、署名者の識別名が含まれます。 +.sp +キーストアの確認も行われます。コマンド行でキーストアの値が指定されていない場合、デフォルトのキーストア・ファイル(ある場合)がチェックされます。署名者の公開鍵の証明書がキーストア内のエントリと一致する場合、その署名者のキーストアのエントリの別名が丸カッコ内に表示されます。 +.RE +.PP +\-certchain \fIfile\fR +.RS 4 +コマンド行で指定した別名によって表されるキーストア・エントリの秘密鍵に関連付けられた証明書チェーンが完全ではない場合に、使用する証明書チェーンを指定します。これは、証明書チェーン全体を保持するのに十分な領域がないハードウェア・トークン上にキーストアが格納されている場合に発生します。このファイルは一連の連結されたX\&.509証明書、PKCS#7形式の単一データ・ブロックのいずれかとなり、そのエンコーディング形式はバイナリ・エンコーディング形式、Internet RFC 1421標準で規定される印刷可能エンコーディング形式(Base64エンコーディングとも呼ばれる)のいずれかになります。インターネットRFC 1421証明書符号化規格およびhttp://tools\&.ietf\&.org/html/rfc1421を参照してください。 +.RE +.PP +\-verbose +.RS 4 +コマンド行で\fB\-verbose\fRオプションを指定した場合、冗長モードで動作し、このモードでは、\fBjarsigner\fRは、JARの署名または検証の進行状況に関する追加情報を出力します。 +.RE +.PP +\-internalsf +.RS 4 +以前は、JARファイルの署名時に生成された\fB\&.DSA\fR +(署名ブロック)ファイルに、生成された\fB\&.SF\fRファイル(署名ファイル)のエンコードされた完全なコピーが含まれていました。 この動作は変更されました。出力JARファイル全体のサイズを小さくするために、デフォルトでは\fB\&.DSA\fRファイルには\fB\&.SF\fRファイルのコピーが含まれないようになっています。コマンド行で\fB\-internalsf\fRを指定した場合、以前と同じように動作します。このオプションは、テストを行う場合に便利です。実際には、\fB\-internalsf\fRオプションは、オーバーヘッドが大きくなるため、使用しないでください。 +.RE +.PP +\-sectionsonly +.RS 4 +コマンド行で\fB\-sectionsonly\fRオプションを指定した場合、JARファイルの署名時に生成される\fB\&.SF\fRファイル(署名ファイル)には、マニフェスト・ファイル全体のハッシュを含むヘッダーは含まれません。これに含まれるのは、JARファイル内の各ソース・ファイルに関連する情報およびハッシュのみです。署名ファイルを参照してください。 +.sp +デフォルトでは、最適化のために、このヘッダーが追加されます。ヘッダーが存在する場合、JARファイルを検証するたびに、検証では、まずヘッダー内のハッシュがマニフェスト・ファイル全体のハッシュと一致するかどうかを確認するためにチェックできます。一致する場合、検証は次の手順に進みます。一致しない場合、\fB\&.SF\fRファイル内の各ソース・ファイル情報セクションのハッシュが、マニフェスト・ファイル内の対応するセクションのハッシュと一致するという、あまり最適化されていない検証を実行する必要があります。JARファイルの検証を参照してください。 +.sp +\fB\-sectionsonly\fRオプションは、主にテスト用に使用されます。これを使用するとオーバーヘッドが大きくなるため、テスト用以外では使用しないでください。 +.RE +.PP +\-protected +.RS 4 +\fBtrue\fRまたは\fBfalse\fRのいずれかの値を指定できます。専用PINリーダーなどの保護された認証パスによってパスワードを指定する必要がある場合、\fBtrue\fRを指定します。 +.RE +.PP +\-providerClass \fIprovider\-class\-name\fR +.RS 4 +暗号化サービス・プロバイダが\fBjava\&.security\fRセキュリティ・プロパティ・ファイルに指定されていないときは、そのマスター・クラス・ファイルの名前を指定するときに使用されます。 +.sp +\fB\-providerArg ConfigFilePath\fRオプションとともに使用し、\fBkeytool\fRおよび\fBjarsigner\fRツールは、プロバイダを動的にインストールし、トークン構成ファイルへのパスに\fIConfigFilePath\fRを使用します。次の例は、Oracle PKCS #11プロバイダがセキュリティ・プロパティ・ファイルに構成されていなかった場合に\fBPKCS #11\fRキーストアを一覧表示するコマンドを示しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore NONE \-storetype PKCS11 \e\fR +\fB \-providerClass sun\&.security\&.pkcs11\&.SunPKCS11 \e\fR +\fB \-providerArg /mydir1/mydir2/token\&.config \e\fR +\fB \-list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-providerName \fIproviderName\fR +.RS 4 +\fBjava\&.security\fRセキュリティ・プロパティ・ファイル内で2つ以上のプロバイダが構成された場合、\fB\-providerName\fRオプションを使用して、特定のプロバイダ・インスタンスを対象にすることができます。このオプションの引数は、プロバイダの名前です。 +.sp +Oracle PKCS #11プロバイダの場合、\fIproviderName\fRは\fBSunPKCS11\-\fR\fITokenName\fRという形式になります。ここで、構成属性の表で詳細に説明されているように、\fITokenName\fRは、プロバイダ・インスタンスが構成された名前の接尾辞です。たとえば、次のコマンドは、名前接尾辞\fBSmartCard\fRの\fBPKCS #11\fRキーストア・プロバイダ・インスタンスの内容を一覧表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore NONE \-storetype PKCS11 \e\fR +\fB \-providerName SunPKCS11\-SmartCard \e\fR +\fB \-list\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\fIjavaoption\fR +.RS 4 +指定された\fIjavaoption\fR文字列をJavaインタプリタに直接渡します。\fBjarsigner\fRコマンドは、インタプリタに対するラッパーです。このオプションには、空白を含めることはできません。このオプションは、実行環境またはメモリー使用を調整する場合に便利です。指定できるインタプリタ・オプションを一覧表示するには、コマンドラインで\fBjava \-h\fRまたは\fBjava \-X\fRと入力してください。 +.RE +.PP +\-tsa \fIurl\fR +.RS 4 +\fB\-tsa http://example\&.tsa\&.url\fRがJARファイルの署名時にコマンド行にある場合、署名のタイムスタンプが生成されます。URL +\fBhttp://example\&.tsa\&.url\fRは、Time Stamping Authority (TSA)の場所を特定し、\fB\-tsacert\fRオプションを指定して検出されたURLをオーバーライドします。\fB\-tsa\fRオプションでは、TSAの公開鍵証明書をキーストアに配置する必要はありません。 +.sp +タイムスタンプを生成するために、\fBjarsigner\fRは、RFC 3161で定義されているタイムスタンプ・プロトコル(TSP)を使用してTSAと通信します。成功すると、TSAによって返されたタイムスタンプ・トークンは、署名ブロック・ファイルの署名とともに保存されます。 +.RE +.PP +\-tsacert \fIalias\fR +.RS 4 +\fB\-tsacert alias\fRがJARファイルの署名時にコマンド行にある場合、署名のタイムスタンプが生成されます。別名は、キーストア内の有効なTSAの公開鍵証明書を特定します。エントリの証明書で、TSAの場所を特定するURLを含むSubject Information Access拡張機能が確認されます。 +.sp +\fB\-tsacert\fRオプションを使用する場合は、TSAの公開鍵証明書がキーストアに配置されている必要があります。 +.RE +.PP +\-tsapolicyid \fIpolicyid\fR +.RS 4 +TSAサーバーに送信するポリシーIDを識別するオブジェクト識別子(OID)を指定します。このオプションを指定しない場合、ポリシーIDは送信されず、TSAサーバーはデフォルトのポリシーIDを選択します。 +.sp +オブジェクト識別子は、ITU Telecommunication Standardization Sector (ITU\-T)標準であるX\&.696によって定義されます。これらの識別子は、通常、\fB1\&.2\&.3\&.4\fRなどの、負ではない数字のピリオド区切りのセットです。 +.RE +.PP +\-altsigner \fIclass\fR +.RS 4 +このオプションは、代替署名メカニズムを指定します。完全修飾クラス名は、\fBcom\&.sun\&.jarsigner\&.ContentSigner\fR抽象クラスを拡張するクラス・ファイルを識別します。このクラス・ファイルへのパスは、\fB\-altsignerpath\fRオプションによって定義されます。\fB\-altsigner\fRオプションを使用した場合、\fBjarsigner\fRコマンドでは、指定されたクラスによって提供される署名メカニズムを使用します。それ以外の場合、\fBjarsigner\fRコマンドはデフォルトの署名メカニズムを使用します。 +.sp +たとえば、\fBcom\&.sun\&.sun\&.jarsigner\&.AuthSigner\fRという名前のクラスが提供する署名メカニズムを使用するには、jarsignerのオプション\fB\-altsigner com\&.sun\&.jarsigner\&.AuthSigner\fRを使用します。 +.RE +.PP +\-altsignerpath \fIclasspathlist\fR +.RS 4 +クラス・ファイルおよびそれが依存するJARファイルへのパスを指定します。\fB\-altsigner\fRオプションを使用して、クラス・ファイル名を指定します。クラス・ファイルがJARファイル内にある場合、このオプションでは、そのJARファイルへのパスを指定します。 +.sp +絶対パスまたは現在のディレクトリへの相対パスを指定できます。\fIclasspathlist\fRに複数のパスやJARファイルが含まれる場合、それらを、Oracle Solarisの場合はコロン(:)で、Windowsの場合はセミコロン(;)で、それぞれ区切ります。目的のクラスがすでに検索パス内にある場合は、このオプションは不要です。 +.sp +次の例では、クラス・ファイルを含むJARファイルへのパスを指定する方法を示します。JARファイル名を含めます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-altsignerpath /home/user/lib/authsigner\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、クラス・ファイルを含むJARファイルへのパスを指定する方法を示します。JARファイル名を省略します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-altsignerpath /home/user/classes/com/sun/tools/jarsigner/\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-strict +.RS 4 +署名または検証処理中に、コマンドにより警告メッセージが発行される場合があります。このオプションを指定すると、コマンドにより検出された重大な警告メッセージがツールの終了コードに反映されます。エラーと警告を参照してください。 +.RE +.PP +\-verbose \fIsuboptions\fR +.RS 4 +検証処理の場合、\fB\-verbose\fRオプションには、表示する情報の量を決定するサブオプションを指定します。\fB\-certs\fRオプションも指定した場合、デフォルト・モード(またはサブオプション\fBall\fR)では、エントリが処理されるたびに各エントリが表示され、その後にJARファイルの各署名者の証明書情報も表示されます。\fB\-certs\fRおよび\fB\-verbose:grouped\fRサブオプションを指定した場合、同じ署名者情報を持つエントリが、その証明書情報とともに、グループ化されて表示されます。\fB\-certs\fRおよび\fB\-verbose:summary\fRサブオプションを指定した場合、同じ署名者情報を持つエントリが、その証明書情報とともに、グループ化されて表示されます。各エントリの詳細は、\fI1つのエントリ(以上)\fRにまとめられて表示されます。例を参照してください。 +.RE +.SH "エラーと警告" +.PP +署名または検証プロセス中に、\fBjarsigner\fRコマンドで、様々なエラーまたは警告が発行される可能性があります。 +.PP +障害がある場合、\fBjarsigner\fRコマンドはコード1で終了します。障害はないが、1つ以上の重大な警告がある場合、\fB\-strict\fRオプションが指定されて\fBいない\fR場合は、\fBjarsigner\fRコマンドはコード0で終了し、\fB\-strict\fRが指定されている場合は警告コードのOR値で終了します。情報警告のみがある、または警告がまったくない場合、コマンドは常にコード0で終了します。 +.PP +たとえば、エントリの署名に使用される証明書が期限切れで、ファイルの署名を許可しないKeyUsage拡張機能を使用している場合、\fB\-strict\fRオプションが指定されていると、\fBjarsigner\fRコマンドはコード12 (=4+8)で終了します。 +.PP +\fB注意:\fR +Solaris、LinuxおよびOS Xでは0から255までの値のみが有効のため、終了コードは再利用されます。 +.PP +次のセクションでは、\fBjarsigner\fRコマンドにより発行できるエラーおよび警告の名前、コード、説明を記述します。 +.SS "障害" +.PP +コマンド行解析エラー、JARファイルに署名する鍵ペアを検索できない、または署名付きJARファイルの検証失敗など(限定されません)、\fBjarsigner\fRコマンドの失敗理由。 +.PP +failure +.RS 4 +コード1。署名または検証が失敗します。 +.RE +.SS "重大な警告" +.PP +\fB注意:\fR +\fB\-strict\fRオプションを指定した場合、重大な警告はエラーとして報告されます。 +.PP +JARファイルの署名に使用する証明書にエラーがある、または署名付きJARファイルに他の問題があるなど、\fBjarsigner\fRコマンドが重大な警告を発行する理由。 +.PP +hasExpiredCert +.RS 4 +コード4。このjarには、署名者証明書が期限切れのエントリが含まれています。 +.RE +.PP +notYetValidCert +.RS 4 +コード4。このjarには、署名者証明書がまだ有効になっていないエントリが含まれています。 +.RE +.PP +chainNotValidated +.RS 4 +コード4。このjarには、証明書チェーンが検証されていないエントリが含まれています。 +.RE +.PP +badKeyUsage +.RS 4 +コード8。このJARには、署名者証明書のKeyUsage拡張機能がコード署名を許可しないエントリが含まれています。 +.RE +.PP +badExtendedKeyUsage +.RS 4 +コード8。このjarには、署名者証明書のExtendedKeyUsage拡張機能がコード署名を許可しないエントリが含まれています。 +.RE +.PP +badNetscapeCertType +.RS 4 +コード8。このjarには、署名者証明書のNetscapeCertType拡張機能がコード署名を許可しないエントリが含まれています。 +.RE +.PP +hasUnsignedEntry +.RS 4 +コード16。このjarには、整合性チェックをしていない未署名のエントリが含まれています。 +.RE +.PP +notSignedByAlias +.RS 4 +コード32。このjarには、指定された別名によって署名されていない署名済エントリが含まれています。 +.RE +.PP +aliasNotInStore +.RS 4 +コード32。このjarには、このキーストア内の別名によって署名されていない署名済エントリが含まれます。 +.RE +.SS "情報警告" +.PP +情報警告には、エラーではないが不適切とみなされるものが含まれます。コードはありません。 +.PP +hasExpiringCert +.RS 4 +このjarには、署名者証明書が6か月以内に期限切れとなるエントリが含まれています。 +.RE +.PP +noTimestamp +.RS 4 +このjarには、タイムスタンプを含まない署名が含まれています。タイムスタンプなしでは、署名者証明書の有効期限(\fBYYYY\-MM\-DD\fR)後または将来の取消日後、ユーザーはこのJARファイルを検証できない場合があります。 +.RE +.SH "例" +.SS "JARファイルの署名" +.PP +次のコマンドを使用して、キーストア別名が\fBworking\fRディレクトリの\fBmystore\fRという名前のキーストアにある\fBjane\fRであるユーザーの秘密鍵でbundle\&.jarに署名し、署名付きJARファイルに\fBsbundle\&.jar\fRという名前を付けます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore\fR +\fB \-storepass <keystore password>\fR +\fB \-keypass <private key password>\fR +\fB \-signedjar sbundle\&.jar bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.PP +前述のコマンドでは\fB\-sigfile\fRが指定されていないため、署名付きJARファイルに格納される生成された\fB\&.SF\fRファイルおよび\fB\&.DSA\fRファイルの名前は、別名に基づいたデフォルトの名前になります。これらは、名前付きの\fBJANE\&.SF\fRおよび\fBJANE\&.DSA\fRです。 +.PP +ストアのパスワードおよび秘密鍵のパスワードを求められる場合、前述のコマンドを短縮して、次のことを実行できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore\fR +\fB \-signedjar sbundle\&.jar bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.PP +キーストアがデフォルトのキーストア(ホーム・ディレクトリ内の\&.keystore)である場合、次に示すように、キーストアを指定する必要がありません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-signedjar sbundle\&.jar bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.PP +入力JARファイル(bundle\&.jar)を署名付きJARファイルで上書きする場合、次のように\fB\-signedjar\fRオプションを指定する必要はありません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner bundle\&.jar jane\fR + +.fi +.if n \{\ +.RE +.\} +.SS "署名付きJARファイルの検証" +.PP +署名付きJARファイルを検証して、署名が有効でJARファイルが改ざんされなかったことを確認するには、次のようなコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-verify sbundle\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.PP +検証が成功すると、\fBjar verified\fRが表示されます。有効でない場合は、エラー・メッセージが表示されます。\fB\-verbose\fRオプションを使用すると、詳細情報を取得できます。\fBjarsigner\fRを\fB\-verbose\fRオプションとともに使用するサンプルを、次に示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-verify \-verbose sbundle\&.jar\fR +\fB \fR +\fB 198 Fri Sep 26 16:14:06 PDT 1997 META\-INF/MANIFEST\&.MF\fR +\fB 199 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.SF\fR +\fB 1013 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.DSA\fR +\fB smk 2752 Fri Sep 26 16:12:30 PDT 1997 AclEx\&.class\fR +\fB smk 849 Fri Sep 26 16:12:46 PDT 1997 test\&.class\fR +\fB \fR +\fB s = signature was verified\fR +\fB m = entry is listed in manifest\fR +\fB k = at least one certificate was found in keystore\fR +\fB \fR +\fB jar verified\&.\fR + +.fi +.if n \{\ +.RE +.\} +.SS "証明書情報を使用した検証" +.PP +\fB\-certs\fRオプションを\fB\-verify\fRおよび\fB\-verbose\fRオプションとともに指定した場合、JARファイルの各署名者の証明書情報が出力に含まれます。この情報には、証明書タイプ、署名者の識別名情報(X\&.509証明書の場合)が含まれ、丸カッコ内には、JARファイルの公開鍵証明書がキーストア・エントリの公開鍵証明書に一致する場合の署名者のキーストア別名が含まれます。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjarsigner \-keystore /working/mystore \-verify \-verbose \-certs myTest\&.jar\fR +\fB \fR +\fB 198 Fri Sep 26 16:14:06 PDT 1997 META\-INF/MANIFEST\&.MF\fR +\fB 199 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.SF\fR +\fB 1013 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.DSA\fR +\fB 208 Fri Sep 26 16:23:30 PDT 1997 META\-INF/JAVATEST\&.SF\fR +\fB 1087 Fri Sep 26 16:23:30 PDT 1997 META\-INF/JAVATEST\&.DSA\fR +\fB smk 2752 Fri Sep 26 16:12:30 PDT 1997 Tst\&.class\fR +\fB \fR +\fB X\&.509, CN=Test Group, OU=Java Software, O=Oracle, L=CUP, S=CA, C=US (javatest)\fR +\fB X\&.509, CN=Jane Smith, OU=Java Software, O=Oracle, L=cup, S=ca, C=us (jane)\fR +\fB \fR +\fB s = signature was verified\fR +\fB m = entry is listed in manifest\fR +\fB k = at least one certificate was found in keystore\fR +\fB \fR +\fB jar verified\&.\fR + +.fi +.if n \{\ +.RE +.\} +.PP +署名者の証明書がX\&.509証明書ではない場合、識別名情報は表示されません。その場合には、証明書のタイプと別名のみが表示されます。たとえば、証明書がPGP証明書で、別名が\fBbob\fRである場合、\fBPGP, (bob)\fRを取得します。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +keytool(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/security/index\&.htmlにある +「コース: Java SEのセキュリティ機能」 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/java.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/java.1 new file mode 100755 index 0000000..682a21f --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/java.1 @@ -0,0 +1,3117 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: java +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "java" "1" "2015å¹´3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +java \- Javaアプリケーションを起動します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\fR [\fIoptions\fR] \fIclassname\fR [\fIargs\fR] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\fR [\fIoptions\fR] \fB\-jar\fR \fIfilename\fR [\fIargs\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +空白で区切られたコマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclassname\fR +.RS 4 +起動するクラスの名前。 +.RE +.PP +\fIfilename\fR +.RS 4 +呼び出されるJavaアーカイブ(JAR)ファイルの名前。\fB\-jar\fRオプションと一緒にのみ使用します。 +.RE +.PP +\fIargs\fR +.RS 4 +空白で区切られた\fBmain()\fRメソッドに渡される引数。 +.RE +.SH "説明" +.PP +\fBjava\fRコマンドはJavaアプリケーションを開始します。Java Runtime Environment (JRE)を起動した後、指定したクラスをロードし、そのクラスの\fBmain()\fRメソッドを呼び出すことにより、これを行います。このメソッドは、\fIpublic\fRおよび\fIstatic\fRとして宣言する必要があります。また、値は返せません。さらに、\fBString\fR配列をパラメータとして指定できる必要があります。メソッド宣言は次の形式を含みます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static void main(String[] args)\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjava\fRコマンドを使用して、\fBmain()\fRメソッドがあるか\fBjavafx\&.application\&.Application\fRを拡張するクラスをロードすることで、JavaFXアプリケーションを起動できます。後者の場合、起動ツールは\fBApplication\fRクラスのインスタンスを構成し、その\fBinit()\fRメソッドをコールし、\fBstart(javafx\&.stage\&.Stage)\fRメソッドをコールします。 +.PP +デフォルトでは、\fBjava\fRコマンドのオプションではない最初の引数は、呼び出されるクラスの完全修飾名です。\fB\-jar\fRオプションを指定した場合、その引数は、アプリケーションのクラス・ファイルとリソース・ファイルを含むJARファイルの名前になります。起動クラスは、ソース・コードの\fBMain\-Class\fRマニフェスト・ヘッダーによって指定される必要があります。 +.PP +JREは、ブートストラップ・クラス・パス、インストール済拡張機能およびユーザーのクラス・パスの3箇所から、起動クラス(およびアプリケーションで使用されている他のクラス)を検索します。 +.PP +クラス・ファイル名またはJARファイル名の後の引数は、\fBmain()\fRメソッドに渡されます。 +.SH "オプション" +.PP +\fBjava\fRコマンドは、次のカテゴリに分類できる広範なオプションをサポートしています。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +標準オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非標準オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なランタイム・オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なJITコンパイラ・オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なサービスアビリティ・オプション +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +高度なガベージ・コレクション・オプション +.RE +.PP +標準のオプションは、Java Virtual Machine (JVM)のすべての実装でサポートすることが保証されます。これらは、JREのバージョンの確認、クラス・パスの設定、冗長な出力の有効化などの一般的なアクションに使用されます。 +.PP +標準以外のオプションは、Java HotSpot仮想マシンに固有の汎用オプションであるため、すべてのJVM実装でサポートされることは保証されず、変更される可能性があります。これらのオプションは\fB\-X\fRで開始します。 +.PP +拡張オプションは、不用意に使用しないことをお薦めします。これらは、特定のシステム要件を持つことが多く、システム構成パラメータへの特権アクセスが必要な場合があるJava HotSpot仮想マシン操作の特定の領域を調整するために使用される開発者オプションです。これらは、すべてのJVM実装でサポートされることは保証されず、変更される可能性があります。拡張オプションは\fB\-XX\fRで始まります。 +.PP +最新リリースで非推奨または削除されるオプションを追跡するために、ドキュメントの最後に非推奨で削除されたオプションという名前のセクションがあります。 +.PP +ブール・オプションは、デフォルトで無効になっている機能を有効にしたり、デフォルトで有効になっている機能を無効にするために使用されます。このようなオプションは、パラメータを必要としません。ブール値\fB\-XX\fRオプションは、プラス記号(\fB\-XX:+\fR\fIOptionName\fR)を使用して有効にし、マイナス記号(\fB\-XX:\-\fR\fIOptionName\fR)を使用して無効にします。 +.PP +引数が必要なオプションの場合、引数は、オプション名を空白、コロン(:)または等号(=)で区切ったものになるか、あるいは引数がオプションの後に直接続く場合もあります(正確な構文は各オプションによって異なります)。サイズをバイト単位で指定するよう求められている場合、接尾辞を使用しないか、あるいはキロバイト(KB)には接尾辞\fBk\fRまたは\fBK\fR、メガバイト(MB)には接尾辞\fBm\fRまたは\fBM\fR、ギガバイト(GB)には接尾辞\fBg\fRまたは\fBG\fRを使用します。たとえば、サイズを8GBに設定するには、\fB8g\fR、\fB8192m\fR、\fB8388608k\fRまたは\fB8589934592\fRのいずれかを引数として指定できます。パーセントの指定が必要な場合は、0から1の数値を使用します(たとえば、25%の場合は\fB0\&.25\fRを指定します)。 +.SS "標準オプション" +.PP +これらは、JVMのすべての実装でサポートされる最も一般的に使用されるオプションです。 +.PP +\-agentlib:\fIlibname\fR[=\fIoptions\fR] +.RS 4 +指定したネイティブ・エージェント・ライブラリをロードします。ライブラリ名の後に、ライブラリに固有のオプションのカンマ区切りリストを使用できます。 +.sp +オプション\fB\-agentlib:foo\fRを指定した場合、JVMは、\fBLD_LIBRARY_PATH\fRシステム変数(OS Xでは、この変数は\fBDYLD_LIBRARY_PATH\fRになります)で指定された場所に\fBlibfoo\&.so\fRという名前のライブラリをロードしようとします。 +.sp +次の例では、スタックの深さ3で、20ミリ秒ごとにヒープ・プロファイリング・ツール(HPROF)ライブラリをロードして、サンプルのCPU情報を取得する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-agentlib:hprof=cpu=samples,interval=20,depth=3\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、メイン・クラスのロード前にJVMを一時停止して、Javaデバッグ・ワイヤ・プロトコル(JDWP)ライブラリをロードして、ポート8000でのソケット接続用にリスニングする方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-agentlib:jdwp=transport=dt_socket,server=y,address=8000\fR + +.fi +.if n \{\ +.RE +.\} +ネイティブ・エージェント・ライブラリの詳細は、次を参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/api/java/lang/instrument/package\-summary\&.htmlにある\fBjava\&.lang\&.instrument\fRパッケージの説明 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/platform/jvmti/jvmti\&.html#startingにあるJVMツール・インタフェース・ガイドのエージェントのコマンド行オプションに関する項 +.RE +.RE +.PP +\-agentpath:\fIpathname\fR[=\fIoptions\fR] +.RS 4 +絶対パス名で指定されたネイティブ・エージェント・ライブラリをロードします。このオプションは\fB\-agentlib\fRと同等ですが、ライブラリのフル・パスおよびファイル名を使用します。 +.RE +.PP +\-client +.RS 4 +Java HotSpot Client VMを選択します。64ビット・バージョンのJava SE Development Kit (JDK)では、現在、このオプションは無視され、かわりにServer JVMが使用されます。 +.sp +デフォルトのJVM選択は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/server\-class\&.htmlにある +サーバークラス・マシンの検出を参照してください。 +.RE +.PP +\-D\fIproperty\fR=\fIvalue\fR +.RS 4 +システム・プロパティの値を設定します。\fIproperty\fR変数は、プロパティの名前を表す、空白のない文字列です。\fIvalue\fR変数は、プロパティの値を表す文字列です。\fIvalue\fRが空白を含む文字列の場合、それを引用符で囲みます(例: +\fB\-Dfoo="foo bar"\fR)。 +.RE +.PP +\-d32 +.RS 4 +アプリケーションを32ビット環境で実行します。32ビット環境がインストールされていないかサポートされていない場合は、エラーが報告されます。デフォルトでは、64ビット・システムが使用されている場合を除き、アプリケーションは32ビット環境で実行されます。 +.RE +.PP +\-d64 +.RS 4 +アプリケーションを64ビット環境で実行します。64ビット環境がインストールされていないかサポートされていない場合は、エラーが報告されます。デフォルトでは、64ビット・システムが使用されている場合を除き、アプリケーションは32ビット環境で実行されます。 +.sp +現在のところ、Java HotSpot Server VMのみが64ビットの操作をサポートしているため、\fB\-d64\fR使用時には\fB\-server\fRオプションが暗黙的に使用されます。\fB\-d64\fR使用時には、\fB\-client\fRオプションは無視されます。この仕様は、将来のリリースでは変更になる可能性があります。 +.RE +.PP +\-disableassertions[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.br +\-da[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.RS 4 +アサーションを無効にします。デフォルトでは、アサーションはすべてのパッケージおよびクラスで無効になっています。 +.sp +引数なしの\fB\-disableassertions\fR +(\fB\-da\fR)を指定すると、すべてのパッケージおよびクラスでアサーションが無効になります。\fB\&.\&.\&.\fRで終わる\fIpackagename\fR引数を指定すると、指定したパッケージとそのサブパッケージ内でアサーションが無効になります。引数として\fB\&.\&.\&.\fRのみを指定すると、現在の作業ディレクトリにある名前のないパッケージ内でアサーションが無効になります。\fIclassname\fR引数を指定すると、切替えによって、指定したクラス内でアサーションが無効になります。 +.sp +\fB\-disableassertions\fR +(\fB\-da\fR)オプションは、すべてのクラス・ローダーおよびシステム・クラスに適用されます(システム・クラスにはクラス・ローダーはありません)。このルールには1つ例外があります。オプションの引数が指定されていない場合は、システム・クラスに適用されません。これにより、システム・クラスを除くすべてのクラスでアサーションを簡単に無効にすることができます。\fB\-disablesystemassertions\fRオプションを使用すると、すべてのシステム・クラスでアサーションを無効にすることができます。 +.sp +特定のパッケージやクラスでアサーションを明示的に有効にするには、\fB\-enableassertions\fR +(\fB\-ea\fR)オプションを使用します。両方のオプションを同時に使用できます。たとえば、パッケージ\fBcom\&.wombat\&.fruitbat\fR +(およびそのサブパッケージ)ではアサーションを有効にして、クラス\fBcom\&.wombat\&.fruitbat\&.Brickbat\fRではアサーションを無効にして、\fBMyClass\fRアプリケーションを実行するには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-ea:com\&.wombat\&.fruitbat\&.\&.\&. \-da:com\&.wombat\&.fruitbat\&.Brickbat MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-disablesystemassertions +.br +\-dsa +.RS 4 +すべてのシステム・クラス内でアサーションを無効にします。 +.RE +.PP +\-enableassertions[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.br +\-ea[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.RS 4 +アサーションを有効にします。デフォルトでは、アサーションはすべてのパッケージおよびクラスで無効になっています。 +.sp +引数なしの\fB\-enableassertions\fR +(\fB\-ea\fR)を指定すると、すべてのパッケージおよびクラスでアサーションが有効になります。\fB\&.\&.\&.\fRで終わる\fIpackagename\fR引数を指定すると、指定したパッケージとそのサブパッケージ内でアサーションが有効になります。引数として\fB\&.\&.\&.\fRのみを指定すると、現在の作業ディレクトリにある名前のないパッケージ内でアサーションが有効になります。\fIclassname\fR引数を指定すると、切替えによって、指定したクラス内でアサーションが有効になります。 +.sp +\fB\-enableassertions\fR +(\fB\-ea\fR)オプションは、すべてのクラス・ローダーおよびシステム・クラスに適用されます(システム・クラスにはクラス・ローダーはありません)。このルールには1つ例外があります。オプションの引数が指定されていない場合は、システム・クラスに適用されません。これにより、システム・クラスを除くすべてのクラスでアサーションを簡単に有効にすることができます。\fB\-enablesystemassertions\fRオプションは、すべてのシステム・クラスでアサーションを有効にする別のスイッチを提供します。 +.sp +特定のパッケージやクラスでアサーションを明示的に無効にするには、\fB\-disableassertions\fR +(\fB\-da\fR)オプションを使用します。単一コマンドにこれらのスイッチのインスタンスを複数指定した場合は、指定したスイッチが順番に処理されてからクラスがロードされます。たとえば、パッケージ\fBcom\&.wombat\&.fruitbat\fR +(およびそのサブパッケージ)でのみアサーションを有効にして、クラス\fBcom\&.wombat\&.fruitbat\&.Brickbat\fRではアサーションを無効にして、\fBMyClass\fRアプリケーションを実行するには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-ea:com\&.wombat\&.fruitbat\&.\&.\&. \-da:com\&.wombat\&.fruitbat\&.Brickbat MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-enablesystemassertions +.br +\-esa +.RS 4 +すべてのシステム・クラス内でアサーションを有効にします。 +.RE +.PP +\-help +.br +\-? +.RS 4 +実際にJVMを実行せずに、\fBjava\fRコマンドの使用状況情報を表示します。 +.RE +.PP +\-jar \fIfilename\fR +.RS 4 +JARファイルにカプセル化されたプログラムを実行します。\fIfilename\fR引数は、使用するアプリケーションの開始点として機能する\fBpublic static void main(String[] args)\fRメソッドを定義する、\fBMain\-Class:\fR\fIclassname\fRという形式の1行を含むマニフェストを持つJARファイルの名前です。 +.sp +\fB\-jar\fRオプションを使用すると、指定したJARファイルがすべてのユーザー・クラスのソースになり、クラス・パスの他の設定は無視されます。 +.sp +JARファイルの詳細は、次のリソースを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jar/index\&.htmlにあるJavaアーカイブ(JAR)ファイルのガイド +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.htmlにある +「レッスン: JARファイルのプログラムのパッケージ化」 +.RE +.RE +.PP +\-javaagent:\fIjarpath\fR[=\fIoptions\fR] +.RS 4 +指定したJavaプログラミング言語エージェントをロードします。Javaアプリケーションのインストゥルメントの詳細は、http://docs\&.oracle\&.com/javase/8/docs/api/java/lang/instrument/package\-summary\&.htmlにあるJava APIドキュメントの\fBjava\&.lang\&.instrument\fRパッケージの説明を参照してください。 +.RE +.PP +\-jre\-restrict\-search +.RS 4 +ユーザー・プライベートなJREをバージョン検索に含めます。 +.RE +.PP +\-no\-jre\-restrict\-search +.RS 4 +ユーザー・プライベートなJREをバージョン検索から除外します。 +.RE +.PP +\-server +.RS 4 +Java HotSpot Server VMを選択します。64ビット・バージョンのJDKでは、Server VMのみをサポートしているため、その場合、このオプションは暗黙的です。 +.sp +デフォルトのJVM選択は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/server\-class\&.htmlにある +サーバークラス・マシンの検出を参照してください。 +.RE +.PP +\-showversion +.RS 4 +バージョン情報を表示し、アプリケーションの実行を続行します。このオプションは\fB\-version\fRオプションと同等ですが、\-versionはバージョン情報の表示後にJVMに終了を指示する点が異なります。 +.RE +.PP +\-splash:\fIimgname\fR +.RS 4 +\fIimgname\fRで指定されたイメージを含むスプラッシュ画面を表示します。たとえば、アプリケーションの起動時に\fBimages\fRディレクトリの\fBsplash\&.gif\fRファイルを表示するには、次のオプションを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-splash:images/splash\&.gif\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-verbose:class +.RS 4 +ロードされた各クラスに関する情報を表示します。 +.RE +.PP +\-verbose:gc +.RS 4 +各ガベージ・コレクション(GC)イベントに関する情報を表示します。 +.RE +.PP +\-verbose:jni +.RS 4 +ネイティブ・メソッドの使用およびその他のJava Native Interface (JNI)アクティビティに関する情報を表示します。 +.RE +.PP +\-version +.RS 4 +バージョン情報を表示してから終了します。このオプションは\fB\-showversion\fRオプションと同等ですが、\-showversionはバージョン情報の表示後にJVMに終了を指示しない点が異なります。 +.RE +.PP +\-version:\fIrelease\fR +.RS 4 +アプリケーションの実行に使用するリリース・バージョンを指定します。コールされた\fBjava\fRコマンドのバージョンがこの指定内容を満たさず、かつ適切な実装がシステム上で見つかった場合には、その適切な実装が使用されます。 +.sp +\fIrelease\fR引数は、正確なバージョン文字列、または空白で区切られたバージョン文字列とバージョン範囲のリストを指定します。\fIバージョン文字列\fRは、次の形式で、開発者のバージョン番号を指定します: +\fB1\&.\fR\fIx\fR\fB\&.0_\fR\fIu\fR +(\fIx\fRはメジャー・バージョン番号、\fIu\fRは更新バージョン番号です)。\fIバージョン範囲\fRは、このバージョン以降を指定するにはバージョン文字列の後にプラス記号(\fB+\fR)を続けたもの、または一致する接頭辞を含む任意のバージョン文字列を指定するには一部のバージョン文字列の後にアスタリスク(\fB*\fR)を続けたもので構成されます。論理\fIOR\fRの組合せには空白、2つのバージョンの文字列/範囲の論理\fIAND\fRの組合せにはアンパサンド(\fB&\fR)を使用して、バージョン文字列とバージョン範囲を組み合せることができます。たとえば、クラスまたはJARファイルの実行にJRE 6u13 (1\&.6\&.0_13)または6u10 (1\&.6\&.0_10)以降の任意のJRE 6のいずれかを必要とする場合、次を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-version:"1\&.6\&.0_13 1\&.6* & 1\&.6\&.0_10+"\fR + +.fi +.if n \{\ +.RE +.\} +引用符が必要なのは、\fIrelease\fRパラメータに空白がある場合のみです。 +.sp +JARファイルの場合は、バージョン要件をコマンド行に指定するよりも、JARファイルのマニフェスト内に指定することが推奨されています。 +.RE +.SS "非標準オプション" +.PP +これらのオプションは、Java HotSpot仮想マシンに固有の汎用オプションです。 +.PP +\-X +.RS 4 +使用可能なすべての\fB\-X\fRオプションのヘルプを表示します。 +.RE +.PP +\-Xbatch +.RS 4 +バックグラウンド・コンパイルを無効にします。デフォルトでは、JVMでは、バックグラウンド・コンパイルが終了するまで、メソッドをバックグラウンド・タスクとしてコンパイルし、インタプリタ・モードでメソッドを実行します。\fB\-Xbatch\fRフラグを指定すると、バックグラウンド・コンパイルが無効になり、すべてのメソッドのコンパイルが完了するまでフォアグラウンド・タスクとして処理されます。 +.sp +このオプションは\fB\-XX:\-BackgroundCompilation\fRと同等です。 +.RE +.PP +\-Xbootclasspath:\fIpath\fR +.RS 4 +ブート・クラス・ファイルを検索するディレクトリ、JARファイルおよびZIPアーカイブの、コロン(:)で区切られたリストを指定します。これらは、JDKに含まれるブート・クラス・ファイルのかわりに使用されます。 +.sp +JREバイナリ・コード・ライセンスに違反するため、\fBrt\&.jar\fRでクラスをオーバーライドする目的で、このオプションを使用するアプリケーションをデプロイしないでください。 +.RE +.PP +\-Xbootclasspath/a:\fIpath\fR +.RS 4 +デフォルトのブートストラップ・クラス・パスの最後に追加するディレクトリ、JARファイルおよびZIPアーカイブの、コロン(:)で区切られたリストを指定します。 +.sp +JREバイナリ・コード・ライセンスに違反するため、\fBrt\&.jar\fRでクラスをオーバーライドする目的で、このオプションを使用するアプリケーションをデプロイしないでください。 +.RE +.PP +\-Xbootclasspath/p:\fIpath\fR +.RS 4 +デフォルトのブートストラップ・クラス・パスの先頭に追加するディレクトリ、JARファイルおよびZIPアーカイブの、コロン(:)で区切られたリストを指定します。 +.sp +JREバイナリ・コード・ライセンスに違反するため、\fBrt\&.jar\fRでクラスをオーバーライドする目的で、このオプションを使用するアプリケーションをデプロイしないでください。 +.RE +.PP +\-Xcheck:jni +.RS 4 +Java Native Interface (JNI)機能に対して追加チェックを行います。具体的には、これは、JNIリクエストを処理する前に、JNI関数に渡されるパラメータと実行環境のデータを検証します。無効なデータが見つかった場合は、ネイティブ・コードに問題があることを示しているため、JVMはリカバリ不能なエラーを発生して終了します。このオプションを使用すると、パフォーマンス低下が予想されます。 +.RE +.PP +\-Xcomp +.RS 4 +最初の呼出しでメソッドのコンパイルを強制的に実行します。デフォルトでは、クライアントVM(\fB\-client\fR)は1,000の解釈されたメソッド呼出しを実行し、サーバーVM(\fB\-server\fR)は10,000の解釈されたメソッド呼出しを実行して、効率的なコンパイルのための情報を収集します。\fB\-Xcomp\fRオプションを指定すると、解釈されたメソッド呼出しが無効になり、効率を犠牲にしてコンパイルのパフォーマンスが向上します。 +.sp +\fB\-XX:CompileThreshold\fRオプションを使用して、コンパイルの前に、解釈されたメソッド呼出しの数を変更することもできます。 +.RE +.PP +\-Xdebug +.RS 4 +何も行いません。後方互換性のために用意されています。 +.RE +.PP +\-Xdiag +.RS 4 +追加の診断メッセージを表示します。 +.RE +.PP +\-Xfuture +.RS 4 +クラス・ファイル形式の仕様への準拠を強化する、厳密なクラス・ファイル形式のチェックが有効になります。将来のリリースでは、より厳密なチェックがデフォルトになるため、新しいコードを開発するときには、開発者はこのフラグを使用することをお薦めします。 +.RE +.PP +\-Xint +.RS 4 +インタプリタ専用モードでアプリケーションを実行します。ネイティブ・コードへのコンパイルは無効になり、すべてのバイトコードがインタプリタによって実行されます。ジャスト・イン・タイム(JIT)コンパイラが提供するパフォーマンス上の利点は、このモードでは実現されません。 +.RE +.PP +\-Xinternalversion +.RS 4 +\fB\-version\fRオプションより詳細なJVMバージョン情報を表示してから終了します。 +.RE +.PP +\-Xloggc:\fIfilename\fR +.RS 4 +詳細なGCイベント情報をロギング用にリダイレクトするファイルを設定します。このファイルに書き込まれる情報は、記録された各イベントの前に行われる最初のGCイベント以降に経過した時間を指定した\fB\-verbose:gc\fRの出力と類似しています。\fB\-Xloggc\fRオプションは\fB\-verbose:gc\fRをオーバーライドします(これらの両方が同じ\fBjava\fRコマンドで指定された場合)。 +.sp +例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xloggc:garbage\-collection\&.log\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-Xmaxjitcodesize=\fIsize\fR +.RS 4 +JITコンパイルされたコードの最大コード・キャッシュ・サイズ(バイト単位)を指定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、この値は48MBに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmaxjitcodesize=48m\fR + +.fi +.if n \{\ +.RE +.\} +このオプションは\fB\-XX:ReservedCodeCacheSize\fRと同等です。 +.RE +.PP +\-Xmixed +.RS 4 +ネイティブ・コードにコンパイルされたホット・メソッドを除き、インタプリタによってすべてのバイトコードを実行します。 +.RE +.PP +\-Xmn\fIsize\fR +.RS 4 +若い世代(ナーサリ)のヒープの初期サイズおよび最大サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。 +.sp +ヒープの若い世代リージョンは新しいオブジェクトに使用されます。GCは、他のリージョンよりこのリージョンで、より頻繁に実行されます。若い世代のサイズが小さすぎる場合、多数のマイナー・ガベージ・コレクションが実行されます。サイズが大きすぎる場合、フル・ガベージ・コレクションのみが実行されますが、完了までに時間がかかることがあります。若い世代のサイズは、全体のヒープ・サイズの半分から4分の1の間にしておくことをお薦めします。 +.sp +次の例では、若い世代の初期サイズおよび最大サイズを様々な単位を使用して256MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmn256m\fR +\fB\-Xmn262144k\fR +\fB\-Xmn268435456\fR + +.fi +.if n \{\ +.RE +.\} +若い世代のヒープの初期サイズと最大サイズの両方を設定する\fB\-Xmn\fRオプションのかわりに、初期サイズの設定には\fB\-XX:NewSize\fRを、最大サイズの設定には\fB\-XX:MaxNewSize\fRを使用できます。 +.RE +.PP +\-Xms\fIsize\fR +.RS 4 +ヒープの初期サイズ(バイト単位)を設定します。指定する値は、1MBより大きい1024の倍数にする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。 +.sp +次の例では、割り当てられたメモリーのサイズを様々な単位を使用して6MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xms6291456\fR +\fB\-Xms6144k\fR +\fB\-Xms6m\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを設定しない場合、初期サイズは、古い世代と若い世代に割り当てられたサイズの合計として設定されます。若い世代のヒープの初期サイズは、\fB\-Xmn\fRオプションまたは\fB\-XX:NewSize\fRオプションを使用して設定できます。 +.RE +.PP +\-Xmx\fIsize\fR +.RS 4 +メモリー割当てプールの最大サイズ(バイト単位)を指定します。指定する値は、2MBより大きい1024の倍数にする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は、実行時にシステム構成に基づいて選択されます。サーバー・デプロイメントでは、\fB\-Xms\fRおよび\fB\-Xmx\fRは通常同じ値に設定されます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.htmlの\fIJava SE HotSpot仮想マシンのガベージ・コレクション・チューニング・ガイド\fRのエルゴノミクスに関する項を参照してください。 +.sp +次の例では、割り当てられたメモリーの許可される最大サイズを様々な単位を使用して80MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmx83886080\fR +\fB\-Xmx81920k\fR +\fB\-Xmx80m\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-Xmx\fRオプションは\fB\-XX:MaxHeapSize\fRと同等です。 +.RE +.PP +\-Xnoclassgc +.RS 4 +クラスのガベージ・コレクション(GC)を無効にします。これにより、GC時間を節約でき、アプリケーション実行中の中断が短縮されます。 +.sp +起動時に\fB\-Xnoclassgc\fRを指定すると、アプリケーション内のクラス・オブジェクトは、GCの間はそのまま残り、常にライブであるとみなされます。これにより、より多くのメモリーが永久に占有されることになり、注意して使用しないと、メモリー不足の例外がスローされます。 +.RE +.PP +\-Xprof +.RS 4 +実行中のプログラムをプロファイルし、プロファイリング・データを標準出力に送信します。このオプションは、プログラム開発用のユーティリティとして提供されています。本番稼働システムでの使用を目的としたものではありません。 +.RE +.PP +\-Xrs +.RS 4 +JVMによるオペレーティング・システム・シグナルの使用を減らします。 +.sp +シャットダウン・フックは、JVMが突然終了した場合でも、シャットダウン時にユーザー・クリーンアップ・コード(データベース接続のクローズなど)を実行することによって、Javaアプリケーションのシャットダウンを順番に有効にします。 +.sp +JVMは、予期しない終了のシャットダウン・フックを実装するためにシグナルをキャッチします。JVMは、\fBSIGHUP\fR、\fBSIGINT\fRおよび\fBSIGTERM\fRを使用して、シャットダウン・フックの実行を開始します。 +.sp +JVMは、デバッグの目的でスレッド・スタックをダンプするという機能を実現するために、同様のメカニズムを使用します。JVMは、スレッド・ダンプを実行するために\fBSIGQUIT\fRを使用します。 +.sp +JVMを埋め込んでいるアプリケーションは、\fBSIGINT\fRや\fBSIGTERM\fRなどのシグナルを頻繁にトラップする必要があり、その結果、JVMのシグナル・ハンドラと衝突する可能性があります。\fB\-Xrs\fRオプションは、この問題に対処するために使用できます。\fB\-Xrs\fRが使用されている場合、\fBSIGINT\fR、\fBSIGTERM\fR、\fBSIGHUP\fRおよび\fBSIGQUIT\fRのシグナル・マスクはJVMによって変更されず、これらのシグナルのシグナル・ハンドラはインストールされません。 +.sp +\fB\-Xrs\fRを指定すると、次の2つの結果が生じます: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSIGQUIT\fRによるスレッド・ダンプは使用できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +シャットダウン・フック処理の実行は、JVMが終了しようとしている時点で\fBSystem\&.exit()\fRを呼び出すなどして、ユーザー・コード側で行う必要があります。 +.RE +.RE +.PP +\-Xshare:\fImode\fR +.RS 4 +クラス・データ共有モードを設定します。このオプションで使用可能な\fImode\fR引数は次のとおりです。 +.PP +auto +.RS 4 +可能な場合、共有クラスのデータを使用します。これは、Java HotSpot 32\-Bit Client VMの場合のデフォルト値です。 +.RE +.PP +on +.RS 4 +クラス・データ共有の使用が必要です。クラス・データ共有を使用できない場合、エラー・メッセージを出力して終了します。 +.RE +.PP +off +.RS 4 +共有クラス・データを使用しません。これは、Java HotSpot 32\-Bit Server VM、Java HotSpot 64\-Bit Client VMおよびJava HotSpot 64\-Bit Server VMの場合のデフォルト値です。 +.RE +.PP +dump +.RS 4 +クラス・データ共有アーカイブを手動で生成します。 +.RE +.RE +.PP +\-XshowSettings:\fIcategory\fR +.RS 4 +設定を表示して続行します。このオプションで使用可能な\fIcategory\fR引数は次のとおりです。 +.PP +all +.RS 4 +設定のすべてのカテゴリを表示します。これがデフォルト値です。 +.RE +.PP +locale +.RS 4 +ロケールに関連する設定を表示します。 +.RE +.PP +properties +.RS 4 +システム・プロパティに関連する設定を表示します。 +.RE +.PP +vm +.RS 4 +JVMの設定を表示します。 +.RE +.RE +.PP +\-Xss\fIsize\fR +.RS 4 +スレッドのスタック・サイズ(バイト単位)を設定します。KBを示す場合は文字\fBk\fRまたは\fBK\fR、MBを示す場合は文字\fBm\fRまたは\fBM\fR、GBを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値はプラットフォームによって異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/ARM (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OS X (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Windows: 仮想メモリーによって異なります。 +.RE +.sp +次の例では、スレッド・スタック・サイズを異なる単位で1024KBに設定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xss1m\fR +\fB\-Xss1024k\fR +\fB\-Xss1048576\fR + +.fi +.if n \{\ +.RE +.\} +このオプションは\fB\-XX:ThreadStackSize\fRと同等です。 +.RE +.PP +\-Xusealtsigs +.RS 4 +JVM内部シグナルの\fBSIGUSR1\fRおよび\fBSIGUSR2\fRのかわりに、代替シグナルを使用します。このオプションは\fB\-XX:+UseAltSigs\fRと同等です。 +.RE +.PP +\-Xverify:\fImode\fR +.RS 4 +バイトコード・ベリファイアのモードを設定します。バイトコードの検証は一部の問題のトラブルシューティングに役立ちますが、実行中のアプリケーションへのオーバーヘッドを増大させます。このオプションで使用可能な\fImode\fR引数は次のとおりです。 +.PP +なし +.RS 4 +バイトコードを検証しません。これにより、起動時間が短縮され、Javaによって提供される保護も軽減されます。 +.RE +.PP +remote +.RS 4 +ブートストラップ・クラス・ローダーでロードされていないこれらのクラスを検証します。これは、\fB\-Xverify\fRオプションを指定しない場合のデフォルトの動作です。 +.RE +.PP +all +.RS 4 +すべてのクラスを検証します。 +.RE +.RE +.SS "高度なランタイム・オプション" +.PP +これらのオプションは、Java HotSpot VMの実行時の動作を制御します。 +.PP +\-XX:+DisableAttachMechanism +.RS 4 +JVMにツールをアタッチするメカニズムを無効にするオプションを有効にします。デフォルトでは、このオプションは無効になっており、これは、アタッチ・メカニズムを有効にすると、\fBjcmd\fR、\fBjstack\fR、\fBjmap\fR、\fBjinfo\fRなどのツールを使用できることを意味します。 +.RE +.PP +\-XX:ErrorFile=\fIfilename\fR +.RS 4 +リカバリ不能なエラーが発生した場合にエラー・データが書き込まれるパスおよびファイル名を指定します。デフォルトでは、このファイルは、現在の作業ディレクトリに作成され、名前は\fBhs_err_pid\fR\fIpid\fR\fB\&.log\fR +(\fIpid\fRはエラーの原因となったプロセスの識別子)になります。次の例では、デフォルトのログ・ファイルを設定する方法を示します(プロセスの識別子は\fB%p\fRとして指定されます)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ErrorFile=\&./hs_err_pid%p\&.log\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、エラー・ログを\fB/var/log/java/java_error\&.log\fRに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ErrorFile=/var/log/java/java_error\&.log\fR + +.fi +.if n \{\ +.RE +.\} +(領域不足、権限の問題または別の問題により)指定したディレクトリにファイルを作成できない場合、ファイルはオペレーティング・システムの一時ディレクトリに作成されます。一時ディレクトリは\fB/tmp\fRです。 +.RE +.PP +\-XX:+FailOverToOldVerifier +.RS 4 +新しいタイプ・チェッカが失敗した場合の、古いベリファイアへの自動フェイルオーバーを有効にします。デフォルトでは、このオプションは無効になっており、最近のバイトコード・バージョンを使用したクラスには、これは無視されます(つまり、無効として処理されます)。古いバージョンのバイトコードを使用したクラスには、これを有効化できます。 +.RE +.PP +\-XX:+FlightRecorder +.RS 4 +アプリケーションの実行中に、Java Flight Recorder (JFR)の使用を有効にします。これは商用機能で、\fB\-XX:+UnlockCommercialFeatures\fRオプションを次のように指定することも必要になります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-XX:+UnlockCommercialFeatures \-XX:+FlightRecorder\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:FlightRecorderOptions=\fIparameter\fR=\fIvalue\fR +.RS 4 +JFRの動作を制御するパラメータを設定します。このオプションを使用できるのは、JFRが有効な場合(\fB\-XX:+FlightRecorder\fRオプションが指定されている場合)のみです。 +.sp +次のリストには、使用可能なすべてのJFRパラメータが含まれます。 +.PP +defaultrecording={true|false} +.RS 4 +記録が連続的なバックグラウンド記録か、または限定された時間に対して実行されるかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(記録は限定された時間に対して実行される)に設定されています。記録を連続的に実行するには、パラメータを\fBtrue\fRに設定します。 +.RE +.PP +disk={true|false} +.RS 4 +JFRでディスクに連続記録を書き込む必要があるかどうかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(ディスクへの連続記録は無効)に設定されています。これを有効にするには、パラメータを\fBtrue\fRに設定し、\fBdefaultrecording=true\fRも設定します。 +.RE +.PP +dumponexit={true|false} +.RS 4 +JVMが制御された方式で終了したときに、JFRデータのダンプ・ファイルを生成するかどうかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(終了時にダンプ・ファイルは生成されない)に設定されています。これを有効にするには、パラメータを\fBtrue\fRに設定し、\fBdefaultrecording=true\fRも設定します。 +.sp +ダンプ・ファイルは、\fBdumponexitpath\fRパラメータによって指定された場所に書き込まれます。 +.RE +.PP +dumponexitpath=\fIpath\fR +.RS 4 +\fBdumponexit=true\fRパラメータを設定した場合、JVMが制御された方式で終了したときに、作成されるJFRデータを含むダンプ・ファイルのパスおよび名前を指定します。パスの設定は、\fBdefaultrecording=true\fRも設定した場合のみ有効になります。 +.sp +指定したパスがディレクトリである場合、JVMは、作成の日付および時間を示すファイル名を割り当てます。指定したパスにすでに存在するファイルのファイル名が含まれる場合、指定したファイル名に日付およびタイム・スタンプを追加して新しいファイルが作成されます。 +.RE +.PP +globalbuffersize=\fIsize\fR +.RS 4 +データ保存に使用する総プライマリ・メモリー量(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、サイズは462848バイトに設定されています。 +.RE +.PP +loglevel={quiet|error|warning|info|debug|trace} +.RS 4 +JFRによってログ・ファイルに書き込まれるデータの量を指定します。デフォルトでは、\fBinfo\fRに設定されています。 +.RE +.PP +maxage=\fItime\fR +.RS 4 +デフォルト記録のディスク・データの最大保持時間を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB30s\fRという指定は30秒を意味します)。デフォルトでは、最大保持時間は15分(\fB15m\fR)に設定されています。 +.sp +このパラメータは、\fBdisk=true\fRパラメータが設定されている場合にのみ有効です。 +.RE +.PP +maxchunksize=\fIsize\fR +.RS 4 +記録内のデータ・チャンクの最大サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、データ・チャンクの最大サイズは12MBに設定されています。 +.RE +.PP +maxsize=\fIsize\fR +.RS 4 +デフォルト記録のディスク・データの最大保持サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、ディスク・データの最大サイズは制限されず、このパラメータは0に設定されています。 +.sp +このパラメータは、\fBdisk=true\fRパラメータが設定されている場合にのみ有効です。 +.RE +.PP +repository=\fIpath\fR +.RS 4 +一時ディスク記憶域のリポジトリ(ディレクトリ)を指定します。デフォルトでは、システムの一時ディレクトリが使用されます。 +.RE +.PP +samplethreads={true|false} +.RS 4 +スレッドのサンプリングを有効化するかどうかを指定します。スレッドのサンプリングは、このパラメータでサンプリング・イベントが有効になっている場合に発生します。デフォルトでは、このパラメータは有効になります。 +.RE +.PP +settings=\fIpath\fR +.RS 4 +イベント設定ファイル(タイプはJFC)のパスと名前を指定します。デフォルトでは、\fBJAVA_HOME/jre/lib/jfr\fRにある\fBdefault\&.jfc\fRファイルが使用されます。 +.RE +.PP +stackdepth=\fIdepth\fR +.RS 4 +JFRによるスタック・トレースのスタックの深さ。デフォルトでは、深さは64メソッド呼出しに設定されています。最大は2048で、最小は1です。 +.RE +.PP +threadbuffersize=\fIsize\fR +.RS 4 +スレッドごとのローカル・バッファ・サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。このパラメータの値が高いと、競合することなく、より多くのデータを収集してグローバル記憶域にフラッシュすることができます。スレッドが多い環境ではアプリケーションのフットプリントも増加します。デフォルトでは、ローカル・バッファ・サイズは5KBに設定されています。 +.RE +.sp +カンマで区切って、複数のパラメータの値を指定できます。たとえば、ディスクに連続記録を書き込み、データ・チャンクの最大サイズを10MBに設定するようにJFRに指示するには、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:FlightRecorderOptions=defaultrecording=true,disk=true,maxchunksize=10M\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:LargePageSizeInBytes=\fIsize\fR +.RS 4 +Solarisでは、Javaヒープに使用されるラージ・ページの最大サイズ(バイト単位)を設定します。\fIsize\fR引数は、2の累乗(2、4、8、16、\&.\&.\&.)である必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、サイズは0に設定され、これは、JVMではラージ・ページのサイズが自動的に選択されていることを意味します。 +.sp +次の例では、ラージ・ページのサイズを4メガバイト(MB)に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:LargePageSizeInBytes=4m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxDirectMemorySize=\fIsize\fR +.RS 4 +新規I/O (\fBjava\&.nio\fRパッケージ)の直接バッファ割当ての最大合計サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、サイズは0に設定され、これは、JVMではNIOの直接バッファ割当てのサイズが自動的に選択されていることを意味します。 +.sp +次の例では、NIOサイズを異なる単位で1024KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxDirectMemorySize=1m\fR +\fB\-XX:MaxDirectMemorySize=1024k\fR +\fB\-XX:MaxDirectMemorySize=1048576\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NativeMemoryTracking=\fImode\fR +.RS 4 +JVMのネイティブ・メモリー使用状況のトラッキングのモードを指定します。このオプションで使用可能な\fImode\fR引数は次のとおりです。 +.PP +off +.RS 4 +JVMのネイティブ・メモリー使用状況を追跡しません。これは、\fB\-XX:NativeMemoryTracking\fRオプションを指定しない場合のデフォルトの動作です。 +.RE +.PP +summary +.RS 4 +JVMサブシステム(Javaヒープ、クラス、コード、スレッドなど)によるメモリー使用状況のみ追跡します。 +.RE +.PP +detail +.RS 4 +JVMサブシステムによるメモリー使用状況のトラッキングに加えて、個々の\fBCallSite\fR +(個々の仮想メモリー・リージョンおよびそのコミット済リージョン)によるメモリー使用状況を追跡します。 +.RE +.RE +.PP +\-XX:ObjectAlignmentInBytes=\fIalignment\fR +.RS 4 +Javaオブジェクトのメモリー配置を設定します(バイト単位)。デフォルトでは、値が8バイトに設定されます。指定される値は、2の累乗にして8から256(両端を含む)の範囲内にする必要があります。このオプションにより、大きいJavaヒープ・サイズで圧縮ポインタを使用できます。 +.sp +バイト単位のヒープ・サイズ制限は次のように計算されます: +.sp +\fB4GB * ObjectAlignmentInBytes\fR +.sp +注意: 配置の値が増えると、オブジェクト間の未使用の領域も増えます。結果として、大きいヒープ・サイズで圧縮ポインタを使用するメリットがわからない可能性があります。 +.RE +.PP +\-XX:OnError=\fIstring\fR +.RS 4 +リカバリ不能なエラーが発生したときに実行する、カスタム・コマンドまたは一連のセミコロン区切りのコマンドを設定します。文字列に空白が含まれている場合は、引用符で囲む必要があります。 +.sp +次の例では、\fB\-XX:OnError\fRオプションを使用してコア・イメージを作成するために\fBgcore\fRコマンドを実行する方法、およびリカバリ不能なエラーの場合にデバッガを起動してプロセスに接続する方法を示します(\fB%p\fRは現在のプロセスを指定します)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:OnError="gcore %p;dbx \- %p"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:OnOutOfMemoryError=\fIstring\fR +.RS 4 +\fBOutOfMemoryError\fR例外が最初にスローされたときに実行する、カスタム・コマンドまたは一連のセミコロン区切りのコマンドを設定します。文字列に空白が含まれている場合は、引用符で囲む必要があります。コマンド文字列の例は、\fB\-XX:OnError\fRオプションの説明を参照してください。 +.RE +.PP +\-XX:+PerfDataSaveToFile +.RS 4 +有効な場合、Javaアプリケーションの終了時にjstat(1)バイナリ・データを保存します。このバイナリ・データは\fBhsperfdata_\fR\fI<pid>\fRという名前のファイルに保存されます。\fI<pid>\fRは、実行したJavaアプリケーションのプロセス識別子です。次のように\fBjstat\fRを使用して、このファイルに含まれるパフォーマンス・データを表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-class file:///\fR\fB\fI<path>\fR\fR\fB/hsperfdata_\fR\fB\fI<pid>\fR\fR +\fBjstat \-gc file:///\fR\fB\fI<path>\fR\fR\fB/hsperfdata_\fR\fB\fI<pid>\fR\fR +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+PrintCommandLineFlags +.RS 4 +コマンド行に表示された、人間工学的に選択したJVMフラグの印刷を有効にします。これは、ヒープ領域サイズや選択されたガベージ・コレクタなど、JVMによって設定されたエルゴノミック値を確認する場合に役立ちます。デフォルトでは、このオプションは無効であり、フラグは印刷されません。 +.RE +.PP +\-XX:+PrintNMTStatistics +.RS 4 +ネイティブ・メモリーのトラッキングが有効な場合に、JVMの終了時に収集されたネイティブ・メモリーのトラッキング・データの印刷を有効にします(\fB\-XX:NativeMemoryTracking\fRを参照してください)。デフォルトでは、このオプションは無効であり、ネイティブ・メモリーのトラッキング・データは印刷されません。 +.RE +.PP +\-XX:+RelaxAccessControlCheck +.RS 4 +ベリファイア内のアクセス制御チェックの量を減らします。デフォルトでは、このオプションは無効になっており、最近のバイトコード・バージョンを使用したクラスには、これは無視されます(つまり、無効として処理されます)。古いバージョンのバイトコードを使用したクラスには、これを有効化できます。 +.RE +.PP +\-XX:+ResourceManagement +.RS 4 +アプリケーションの実行中にリソース管理の使用を有効にします。 +.sp +これは商用機能で、\fB\-XX:+UnlockCommercialFeatures\fRオプションを次のように指定することも必要になります。 +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-XX:+ResourceManagement\fR +.RE +.PP +\-XX:ResourceManagementSampleInterval=\fIvalue\fR (ミリ秒) +.RS 4 +ミリ秒単位でリソース管理測定のサンプリング間隔を制御するパラメータを設定します。 +.sp +リソース管理が有効な場合のみ(つまり、\fB\-XX:+ResourceManagement\fRオプションが指定されている場合)、このオプションを使用できます。 +.RE +.PP +\-XX:+ShowMessageBoxOnError +.RS 4 +JVMでリカバリ不能なエラーが発生した場合、ダイアログ・ボックスの表示を有効にします。これにより、JVMにデバッガを接続してエラーの原因を調査できるように、JVMを終了しないようにして、プロセスをアクティブなままにします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:StartFlightRecording=\fIparameter\fR=\fIvalue\fR +.RS 4 +JavaアプリケーションのJFR記録を開始します。このオプションは、実行中に記録を開始する\fBJFR\&.start\fR診断コマンドと同等です。JFR記録の開始時に、次のパラメータを設定できます。 +.PP +compress={true|false} +.RS 4 +\fBgzip\fRファイル圧縮ユーティリティを使用して、ディスクでJFR記録ログ・ファイル(タイプはJFR)を圧縮するかどうかを指定します。このパラメータは、\fBfilename\fRパラメータが指定されている場合のみ有効です。デフォルトでは、\fBfalse\fR +(記録を圧縮しない)に設定されています。圧縮を有効にするには、パラメータを\fBtrue\fRに設定します。 +.RE +.PP +defaultrecording={true|false} +.RS 4 +記録が連続的なバックグラウンド記録か、または限定された時間に対して実行されるかを指定します。デフォルトでは、このパラメータは\fBfalse\fR +(記録は限定された時間に対して実行される)に設定されています。記録を連続的に実行するには、パラメータを\fBtrue\fRに設定します。 +.RE +.PP +delay=\fItime\fR +.RS 4 +Javaアプリケーションの起動時間と記録開始との間の遅延を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB10m\fRという指定は10分を意味します)。デフォルトでは、遅延は存在せず、このパラメータは0に設定されています。 +.RE +.PP +duration=\fItime\fR +.RS 4 +記録の期間を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB5h\fRという指定は5時間を意味します)。デフォルトでは、期間は制限されず、このパラメータは0に設定されています。 +.RE +.PP +filename=\fIpath\fR +.RS 4 +JFR記録ログ・ファイルのパスと名前を指定します。 +.RE +.PP +name=\fIidentifier\fR +.RS 4 +JFR記録の識別子を指定します。デフォルトでは、\fBRecording x\fRに設定されています。 +.RE +.PP +maxage=\fItime\fR +.RS 4 +デフォルト記録のディスク・データの最大保持時間を指定します。時間を指定する際に、秒単位の場合は\fBs\fR、分の場合は\fBm\fR、時間の場合は\fBh\fR、日の場合は\fBd\fRを追加します(たとえば、\fB30s\fRという指定は30秒を意味します)。デフォルトでは、最大保持時間は15分(\fB15m\fR)に設定されています。 +.RE +.PP +maxsize=\fIsize\fR +.RS 4 +デフォルト記録のディスク・データの最大保持サイズ(バイト単位)を指定します。サイズをKBで指定する場合は\fBk\fRまたは\fBK\fR、サイズをMBで指定する場合は\fBm\fRまたは\fBM\fR、サイズをGBで指定する場合は\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、ディスク・データの最大サイズは制限されず、このパラメータは0に設定されています。 +.RE +.PP +settings=\fIpath\fR +.RS 4 +イベント設定ファイル(タイプはJFC)のパスと名前を指定します。デフォルトでは、\fBJAVA_HOME/jre/lib/jfr\fRにある\fBdefault\&.jfc\fRファイルが使用されます。 +.RE +.sp +カンマで区切って、複数のパラメータの値を指定できます。たとえば、記録を現在の作業ディレクトリのtest\&.jfrに保存し、ログ・ファイルを圧縮するようJFRに指示するには、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:StartFlightRecording=filename=test\&.jfr,compress=true\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:ThreadStackSize=\fIsize\fR +.RS 4 +スレッドのスタック・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値はプラットフォームによって異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/ARM (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OS X (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/i386 (32ビット): 320KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/x64 (64ビット): 1024KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Windows: 仮想メモリーによって異なります。 +.RE +.sp +次の例では、スレッド・スタック・サイズを異なる単位で1024KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ThreadStackSize=1m\fR +\fB\-XX:ThreadStackSize=1024k\fR +\fB\-XX:ThreadStackSize=1048576\fR + +.fi +.if n \{\ +.RE +.\} +このオプションは\fB\-Xss\fRと同等です。 +.RE +.PP +\-XX:+TraceClassLoading +.RS 4 +クラスがロードされるときのクラスのトレースを有効にします。デフォルトでは、このオプションは無効であり、クラスはトレースされません。 +.RE +.PP +\-XX:+TraceClassLoadingPreorder +.RS 4 +クラスが参照される順序で、ロードされたすべてのクラスのトレースを有効にします。デフォルトでは、このオプションは無効であり、クラスはトレースされません。 +.RE +.PP +\-XX:+TraceClassResolution +.RS 4 +定数プールの解決のトレースを有効にします。デフォルトでは、このオプションは無効であり、定数プールの解決はトレースされません。 +.RE +.PP +\-XX:+TraceClassUnloading +.RS 4 +クラスがアンロードされるときのクラスのトレースを有効にします。デフォルトでは、このオプションは無効であり、クラスはトレースされません。 +.RE +.PP +\-XX:+TraceLoaderConstraints +.RS 4 +ローダー制約の記録のトレースを有効にします。デフォルトでは、このオプションは無効であり、ローダー制約の記録は追跡されません。 +.RE +.PP +\-XX:+UnlockCommercialFeatures +.RS 4 +商用機能の使用を有効にします。商用機能は、http://www\&.oracle\&.com/technetwork/java/javase/terms/products/index\&.htmlにある\fIJava SE製品\fRページで定義されているように、Oracle Java SE AdvancedまたはOracle Java SE Suiteパッケージに付属しています。 +.sp +デフォルトでは、このオプションは無効であり、JVMは商用機能なしで実行されます。JVMプロセスが有効化された後、そのプロセスの使用を無効にすることはできません。 +.RE +.PP +\-XX:+UseAltSigs +.RS 4 +JVM内部シグナルの\fBSIGUSR1\fRおよび\fBSIGUSR2\fRのかわりに、代替シグナルの使用を有効にします。デフォルトでは、このオプションは無効であり、代替シグナルは使用されません。このオプションは\fB\-Xusealtsigs\fRと同等です。 +.RE +.PP +\-XX:\-UseBiasedLocking +.RS 4 +バイアス・ロックの使用を無効にします。かなりの量の非競合の同期化がある一部のアプリケーションは、このフラグを有効にすると大幅な高速化が実現しますが、特定のパターンのロックがあるアプリケーションは、速度が低下することがあります。バイアス・ロックの方法の詳細は、http://www\&.oracle\&.com/technetwork/java/tuning\-139912\&.html#section4\&.2\&.5にあるJavaチューニングのホワイト・ペーパーの例を参照してください。 +.sp +デフォルトでは、このオプションは有効になっています。 +.RE +.PP +\-XX:\-UseCompressedOops +.RS 4 +圧縮されたポインタの使用を無効にします。デフォルトではこのオプションが有効であり、Javaヒープ・サイズが32GBより小さい場合に圧縮ポインタが使用されます。このオプションを有効にすると、オブジェクト参照は、64ビットのポインタではなく32ビットのオフセットとして表され、これにより、32GBより小さいJavaヒープ・サイズのアプリケーションの実行時に、通常、パフォーマンスが向上します。このオプションは、64ビットのJVMでのみ機能します。 +.sp +Javaヒープ・サイズが32GBより大きい場合にも圧縮ポインタを使用できます。\fB\-XX:ObjectAlignmentInBytes\fRオプションを参照してください。 +.RE +.PP +\-XX:+UseHugeTLBFS +.RS 4 +Linux用のこのオプションは、\fB\-XX:+UseLargePages\fRを指定するのと同じです。このオプションは、デフォルトでは無効になっています。このオプションは、メモリーの予約時にすべてのラージ・ページを事前に割り当てます。そのため、JVMはラージ・ページ・メモリー領域を動的に拡張または縮小できません。この動作を行う場合は、\fB\-XX:UseTransparentHugePages\fRを参照してください。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+UseLargePages +.RS 4 +ラージ・ページのメモリーの使用を有効にします。デフォルトでは、このオプションは無効であり、ラージ・ページのメモリーは使用されません。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+UseMembar +.RS 4 +スレッドの状態の遷移でメンバーの発行を有効にします。このオプションは、有効になっているARMサーバーを除くすべてのプラットフォーム上で、デフォルトでは無効になっています。(ARMサーバーでこのオプションを無効にしないことをお薦めします。) +.RE +.PP +\-XX:+UsePerfData +.RS 4 +\fBperfdata\fR機能を有効にします。このオプションはデフォルトで有効になっており、JVMのモニタリングおよびパフォーマンス・テストが可能になります。これを無効にすると、\fBhsperfdata_userid\fRディレクトリの作成を抑制します。\fBperfdata\fR機能を無効にするには、\fB\-XX:\-UsePerfData\fRを指定します。 +.RE +.PP +\-XX:+UseTransparentHugePages +.RS 4 +Linuxでは、動的に拡張または縮小できるラージ・ページの使用を有効化してください。このオプションは、デフォルトでは無効になっています。OSが他のページを移動してヒュージ・ページを作成するため、透過的ヒュージ・ページでパフォーマンスの問題が検出される場合があります。このオプションは試験的に使用できます。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+AllowUserSignalHandlers +.RS 4 +アプリケーションによるシグナル・ハンドラのインストールを有効にします。デフォルトでは、このオプションは無効であり、アプリケーションはシグナル・ハンドラをインストールすることは許可されていません。 +.RE +.SS "高度なJITコンパイラ・オプション" +.PP +これらのオプションは、Java HotSpot VMで実行される動的なjust\-in\-time (JIT)コンパイラを制御します。 +.PP +\-XX:+AggressiveOpts +.RS 4 +積極的なパフォーマンス最適化機能の使用を有効にします。これは今後のリリースでデフォルトになる予定です。デフォルトでは、このオプションは無効であり、試験的なパフォーマンス機能は使用されません。 +.RE +.PP +\-XX:AllocateInstancePrefetchLines=\fIlines\fR +.RS 4 +インスタンス割当てポインタの前にプリフェッチする行数を設定します。デフォルトでは、プリフェッチする行数は1に設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocateInstancePrefetchLines=1\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchDistance=\fIsize\fR +.RS 4 +オブジェクト割当てのプリフェッチ距離のサイズ(バイト単位)を設定します。新規オブジェクトの値で書き込もうとするメモリーは、最後に割り当てられたオブジェクトのアドレスから、この距離までプリフェッチされます。各Javaスレッドには独自の割当てポイントがあります。 +.sp +負の値は、プリフェッチ距離はプラットフォームに基づいて選択されることを示します。正の値は、プリフェッチするバイト数です。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は\-1に設定されています。 +.sp +次の例では、プリフェッチ距離を1024バイトに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchDistance=1024\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchInstr=\fIinstruction\fR +.RS 4 +割当てポインタの前にプリフェッチするプリフェッチ命令を設定します。Java HotSpot Server VMのみが、このオプションをサポートしています。使用可能な値は0から3までです。値の背後にある実際の命令は、プラットフォームによって異なります。デフォルトでは、プリフェッチ命令は0に設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchInstr=0\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchLines=\fIlines\fR +.RS 4 +コンパイルされたコードで生成されるプリフェッチ命令を使用して、最後のオブジェクト割当て後にロードするキャッシュ行数を設定します。最後に割り当てられたオブジェクトがインスタンスの場合は、デフォルト値は1になり、配列の場合は3になります。 +.sp +次の例では、ロードされるキャッシュ行数を5に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchLines=5\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchStepSize=\fIsize\fR +.RS 4 +順次プリフェッチ命令のステップ・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、ステップ・サイズは16バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchStepSize=16\fR + +.fi +.if n \{\ +.RE +.\} +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:AllocatePrefetchStyle=\fIstyle\fR +.RS 4 +プリフェッチ命令に生成されるコード・スタイルを設定します。\fIstyle\fR引数は、0から3までの整数です。 +.PP +0 +.RS 4 +プリフェッチ命令を生成しません。 +.RE +.PP +1 +.RS 4 +各割当ての後で、プリフェッチ命令を実行します。これはデフォルトのパラメータです。 +.RE +.PP +2 +.RS 4 +スレッド・ローカルな割当てブロック(TLAB)ウォーターマーク・ポインタを使用して、プリフェッチ命令を実行するタイミングを決定します。 +.RE +.PP +3 +.RS 4 +割当てプリフェッチ用のSPARCでBIS命令を使用します。 +.RE +.sp +Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+BackgroundCompilation +.RS 4 +バックグラウンド・コンパイルを有効にします。このオプションはデフォルトで有効になっています。バックグラウンド・コンパイルを無効にするには、\fB\-XX:\-BackgroundCompilation\fRを指定します(これは\fB\-Xbatch\fRを指定するのと同等です)。 +.RE +.PP +\-XX:CICompilerCount=\fIthreads\fR +.RS 4 +コンパイルに使用するコンパイラ・スレッドの数を設定します。デフォルトでは、スレッド数は、サーバーJVMの場合は2、クライアントJVMの場合は1に設定されており、層コンパイルが使用されている場合、コア数に合せて増減します。次の例では、スレッドの数を2に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CICompilerCount=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CodeCacheMinimumFreeSpace=\fIsize\fR +.RS 4 +コンパイルに必要な最小空き領域(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。最小空き領域より少ない領域しか残っていない場合、コンパイルは停止します。デフォルトでは、このオプションは500KBに設定されています。次の例では、最小空き領域を1024MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CodeCacheMinimumFreeSpace=1024m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CompileCommand=\fIcommand\fR,\fImethod\fR[,\fIoption\fR] +.RS 4 +メソッドで実行するコマンドを指定します。たとえば、コンパイル元から\fBString\fRクラスの\fBindexOf()\fRメソッドを実行するには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,java/lang/String\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +スラッシュ(\fB/\fR)で区切られたすべてのパッケージおよびサブパッケージを含む、完全クラス名を指定します。切取りと貼付けの操作を容易にするために、\fB\-XX:+PrintCompilation\fRオプションおよび\fB\-XX:+LogCompilation\fRオプションによって生成されるメソッド名の形式を使用することもできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,java\&.lang\&.String::indexOf\fR + +.fi +.if n \{\ +.RE +.\} +署名なしでメソッドを指定すると、コマンドは指定した名前を持つすべてのメソッドに適用されます。ただし、クラス・ファイル形式でメソッドの署名を指定することもできます。この場合、引数を引用符で囲む必要があり、囲まないと、シェルによりセミコロンがコマンドの終了として扱われます。たとえば、コンパイル元から\fBString\fRクラスの\fBindexOf(String)\fRメソッドのみ除外するには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand="exclude,java/lang/String\&.indexOf,(Ljava/lang/String;)I"\fR + +.fi +.if n \{\ +.RE +.\} +また、クラス名およびメソッド名にワイルドカードとしてアスタリスク(*)を使用できます。たとえば、コンパイル元からすべてのクラスのすべての\fBindexOf()\fRメソッドを除外するには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,*\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +カンマとピリオドは空白の別名で、これにより、シェルを介してコンパイラ・コマンドを渡すことが容易になります。引数を引用符で囲むことで、空白をセパレータとして使用して\fB\-XX:CompileCommand\fRに引数を渡すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand="exclude java/lang/String indexOf"\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-XX:CompileCommand\fRオプションを使用してコマンド行で渡されたコマンドを解析した後に、JITコンパイラは\fB\&.hotspot_compiler\fRファイルからコマンドを読み取ります。このファイルにコマンドを追加するか、または\fB\-XX:CompileCommandFile\fRオプションを使用して別のファイルを指定することができます。 +.sp +複数のコマンドを追加するには、\fB\-XX:CompileCommand\fRオプションを複数回指定するか、または改行セパレータ(\fB\en\fR)を使用して各引数を区切ります。次のコマンドを使用できます。 +.PP +break +.RS 4 +指定したメソッドのコンパイルの最初に停止するために、JVMのデバッグ時のブレークポイントを設定します。 +.RE +.PP +compileonly +.RS 4 +指定したメソッドを除いたすべてのメソッドを、コンパイルから除外します。別の方法として、\fB\-XX:CompileOnly\fRオプションを使用して複数のメソッドを指定できます。 +.RE +.PP +dontinline +.RS 4 +指定したメソッドをインライン化しないようにします。 +.RE +.PP +exclude +.RS 4 +指定したメソッドをコンパイルから除外します。 +.RE +.PP +help +.RS 4 +\fB\-XX:CompileCommand\fRオプションのヘルプ・メッセージを印刷します。 +.RE +.PP +inline +.RS 4 +指定したメソッドをインライン化しようとします。 +.RE +.PP +log +.RS 4 +指定したメソッドを除くすべてのメソッドに対して、(\fB\-XX:+LogCompilation\fRオプションを使用して)コンパイル・ロギングを除外します。デフォルトでは、コンパイルされたすべてのメソッドにロギングが実行されます。 +.RE +.PP +option +.RS 4 +このコマンドは、最後の引数(\fIoption\fR)のかわりに、指定したメソッドにJITコンパイル・オプションを渡すために使用できます。コンパイル・オプションは、メソッド名の後の末尾に設定されます。たとえば、\fBStringBuffer\fRクラスの\fBappend()\fRメソッドに対して\fBBlockLayoutByFrequency\fRオプションを有効にするには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=option,java/lang/StringBuffer\&.append,BlockLayoutByFrequency\fR + +.fi +.if n \{\ +.RE +.\} +カンマまたは空白で区切って、複数のコンパイル・オプションを指定できます。 +.RE +.PP +print +.RS 4 +指定したメソッドのコンパイル後に生成されたアセンブラ・コードを出力します。 +.RE +.PP +quiet +.RS 4 +コンパイル・コマンドを出力しません。デフォルトでは、\fB\-XX:CompileCommand\fRオプションを使用して指定したコマンドが出力されます。たとえば、\fBString\fRクラスの\fBindexOf()\fRメソッドのコンパイルから除外する場合、次が標準出力に出力されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompilerOracle: exclude java/lang/String\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +他の\fB\-XX:CompileCommand\fRオプションの前に\fB\-XX:CompileCommand=quiet\fRオプションを指定することによって、これを抑制できます。 +.RE +.RE +.PP +\-XX:CompileCommandFile=\fIfilename\fR +.RS 4 +JITコンパイラ・コマンドの読取り元のファイルを設定します。デフォルトでは、JITコンパイラによって実行されるコマンドを格納するために、\fB\&.hotspot_compiler\fRファイルが使用されます。 +.sp +コマンド・ファイルの各行は、コマンドが使用されるコマンド、クラス名およびメソッド名を表します。たとえば、次の行は、\fBString\fRクラスの\fBtoString()\fRメソッドに対してアセンブリ・コードを出力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBprint java/lang/String toString\fR + +.fi +.if n \{\ +.RE +.\} +メソッドで実行するJITコンパイラのコマンドの指定の詳細は、\fB\-XX:CompileCommand\fRオプションを参照してください。 +.RE +.PP +\-XX:CompileOnly=\fImethods\fR +.RS 4 +コンパイルを制限する(カンマで区切られた)メソッドのリストを設定します。指定したメソッドのみがコンパイルされます。完全クラス名(パッケージおよびサブパッケージを含む)で各メソッドを指定します。たとえば、\fBString\fRクラスの\fBlength()\fRメソッドおよび\fBList\fRクラスの\fBsize()\fRメソッドのみをコンパイルするには、次を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java/lang/String\&.length,java/util/List\&.size\fR + +.fi +.if n \{\ +.RE +.\} +スラッシュ(\fB/\fR)で区切られたすべてのパッケージおよびサブパッケージを含む、完全クラス名を指定します。切取りと貼付けの操作を容易にするために、\fB\-XX:+PrintCompilation\fRオプションおよび\fB\-XX:+LogCompilation\fRオプションによって生成されるメソッド名の形式を使用することもできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java\&.lang\&.String::length,java\&.util\&.List::size\fR + +.fi +.if n \{\ +.RE +.\} +ワイルドカードはサポートされていませんが、クラス名またはパッケージ名だけを指定してクラスまたはパッケージのすべてのメソッドをコンパイルすることも、メソッドだけを指定して任意のクラスのこの名前を持つメソッドをコンパイルすることもできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java/lang/String\fR +\fB\-XX:CompileOnly=java/lang\fR +\fB\-XX:CompileOnly=\&.length\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CompileThreshold=\fIinvocations\fR +.RS 4 +コンパイル前に解釈されたメソッド呼出しの数を設定します。デフォルトでは、サーバーJVMでは、JITコンパイラは、10,000の解釈されたメソッド呼出しを実行して、効率的なコンパイルのための情報を収集します。クライアントJVMの場合、デフォルト設定は1,500呼出しです。層コンパイルが有効な場合、このオプションは無視されます。オプション\fB\-XX:+TieredCompilation\fRを参照してください。次の例では、解釈されたメソッド呼出しの数を5,000に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileThreshold=5000\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-Xcomp\fRオプションを指定して、コンパイルの前に、Javaメソッドの解釈を完全に無効にすることができます。 +.RE +.PP +\-XX:+DoEscapeAnalysis +.RS 4 +エスケープ分析の使用を有効にします。このオプションはデフォルトで有効になっています。エスケープ分析の使用を無効にするには、\fB\-XX:\-DoEscapeAnalysis\fRを指定します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:InitialCodeCacheSize=\fIsize\fR +.RS 4 +初期コード・キャッシュ・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は500KBに設定されています。初期コード・キャッシュ・サイズをシステムの最小メモリー・ページ・サイズより小さくしないでください。次の例では、初期コード・キャッシュ・サイズを32KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialCodeCacheSize=32k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+Inline +.RS 4 +メソッドのインライン化を有効にします。このオプションは、パフォーマンスを向上させるためにデフォルトで有効になっています。メソッドのインライン化を無効にするには、\fB\-XX:\-Inline\fRを指定します。 +.RE +.PP +\-XX:InlineSmallCode=\fIsize\fR +.RS 4 +インライン化が必要なコンパイルされたメソッドの最大コード・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。指定したサイズより小さいサイズのコンパイルされたメソッドのみが、インライン化されます。デフォルトでは、最大コード・サイズは1000バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InlineSmallCode=1000\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+LogCompilation +.RS 4 +現在の作業ディレクトリにある\fBhotspot\&.log\fRという名前のファイルへのコンパイル・アクティビティのロギングを有効にします。\fB\-XX:LogFile\fRオプションを使用して、異なるログ・ファイル・パスと名前を指定できます。 +.sp +デフォルトでは、このオプションは無効であり、コンパイル・アクティビティは記録されません。\fB\-XX:+LogCompilation\fRオプションは、診断JVMオプションのロックを解除する\fB\-XX:UnlockDiagnosticVMOptions\fRオプションとともに使用する必要があります。 +.sp +\fB\-XX:+PrintCompilation\fRオプションを使用して、メソッドをコンパイルするたびに、コンソールに出力されたメッセージを含む詳細な診断出力を有効化できます。 +.RE +.PP +\-XX:MaxInlineSize=\fIsize\fR +.RS 4 +インライン化するメソッドの最大バイトコード・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、最大バイトコード・サイズは35バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxInlineSize=35\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxNodeLimit=\fInodes\fR +.RS 4 +単一のメソッドのコンパイル時に使用されるノードの最大数を設定します。デフォルトでは、ノードの最大数は65,000に設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxNodeLimit=65000\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxTrivialSize=\fIsize\fR +.RS 4 +インライン化する単純メソッドの最大バイトコード・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、単純メソッドの最大バイトコード・サイズは6バイトに設定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxTrivialSize=6\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+OptimizeStringConcat +.RS 4 +\fBString\fR連結操作の最適化を有効にします。このオプションはデフォルトで有効になっています。\fBString\fR連結操作の最適化を無効にするには、\fB\-XX:\-OptimizeStringConcat\fRを指定します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+PrintAssembly +.RS 4 +外部の\fBdisassembler\&.so\fRライブラリを使用して、バイトコード化されたネイティブのメソッドのアセンブリ・コードの出力を有効にします。これにより、生成されたコードを表示することができ、パフォーマンスの問題の診断に役立ちます。 +.sp +デフォルトでは、このオプションは無効であり、アセンブリ・コードは印刷されません。\fB\-XX:+PrintAssembly\fRオプションは、診断JVMオプションのロックを解除する\fB\-XX:UnlockDiagnosticVMOptions\fRオプションとともに使用する必要があります。 +.RE +.PP +\-XX:+PrintCompilation +.RS 4 +メソッドをコンパイルするたびに、コンソールにメッセージを出力することによって、JVMからの詳細な診断出力を有効にします。これにより、実際にコンパイルされるメソッドを確認できます。デフォルトでは、このオプションは無効であり、診断出力は印刷されません。 +.sp +\fB\-XX:+LogCompilation\fRオプションを使用して、コンパイル・アクティビティをファイルに記録することもできます。 +.RE +.PP +\-XX:+PrintInlining +.RS 4 +インライン化の決定内容の出力を有効にします。これにより、インライン化されるメソッドを確認できます。 +.sp +デフォルトでは、このオプションは無効であり、インライン化情報は出力されません。\fB\-XX:+PrintInlining\fRオプションは、診断JVMオプションのロックを解除する\fB\-XX:+UnlockDiagnosticVMOptions\fRオプションとともに使用する必要があります。 +.RE +.PP +\-XX:ReservedCodeCacheSize=\fIsize\fR +.RS 4 +JITコンパイルされたコードの最大コード・キャッシュ・サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。このオプションは2GBの制限があります。そうでない場合は、エラーが生成されます。最大コード・キャッシュ・サイズを初期コード・キャッシュ・サイズより小さくしないでください。\fB\-XX:InitialCodeCacheSize\fRオプションを参照してください。このオプションは\fB\-Xmaxjitcodesize\fRと同等です。 +.RE +.PP +\-XX:RTMAbortRatio=\fIabort_ratio\fR +.RS 4 +RTM中止率は、すべての実行済RTMトランザクションに対するパーセンテージ(%)として指定されます。中止されたトランザクション数がこの率を超えた場合、コンパイルされたコードが非最適化されます。この率は、\fB\-XX:+UseRTMDeopt\fRオプションが有効な場合に使用されます。このオプションのデフォルト値は50です。つまり、すべてのトランザクションの50%が中止された場合、コンパイルされたコードが非最適化されます。 +.RE +.PP +\-XX:RTMRetryCount=\fInumber_of_retries\fR +.RS 4 +中止またはビジーの場合、RTMロック・コードは、標準のロック・メカニズムにフォールバックする前にこのオプションによって指定された回数再試行されます。このオプションのデフォルト値は5です。\fB\-XX:UseRTMLocking\fRオプションを有効化する必要があります。 +.RE +.PP +\-XX:+TieredCompilation +.RS 4 +層コンパイルの使用を有効にします。デフォルトでは、このオプションは有効になっています。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+UseAES +.RS 4 +Intel、AMDおよびSPARCハードウェアに対して、ハードウェアベースのAES組込みを有効化します。Intel Westmere (2010以降)、AMD Bulldozer (2011以降)およびSPARC (T4以降)が、サポートされているハードウェアです。UseAESは、UseAESIntrinsicsとともに使用します。 +.RE +.PP +\-XX:+UseAESIntrinsics +.RS 4 +UseAESとUseAESIntrinsicsフラグはデフォルトで有効化されており、Java HotSpot Server VM 32ビットおよび64ビットに対してのみサポートされています。ハードウェアベースのAES組込みを無効化するには、\fB\-XX:\-UseAES \-XX:\-UseAESIntrinsics\fRを指定します。たとえば、ハードウェアAESを有効化するには、次のフラグを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:+UseAES \-XX:+UseAESIntrinsics\fR + +.fi +.if n \{\ +.RE +.\} +32ビットおよび64ビットに対してUseAESおよびUseAESIntrinsicsフラグをサポートするには、\fB\-server\fRオプションを使用してJava HotSpot Server VMを選択します。これらのフラグは、クライアントVMではサポートされていません。 +.RE +.PP +\-XX:+UseCodeCacheFlushing +.RS 4 +コンパイラをシャットダウンする前に、コード・キャッシュのフラッシュを有効にします。このオプションはデフォルトで有効になっています。コンパイラをシャットダウンする前にコード・キャッシュのフラッシュを無効にするには\fB\-XX:\-UseCodeCacheFlushing\fRを指定します。 +.RE +.PP +\-XX:+UseCondCardMark +.RS 4 +カード表の更新前に、カードがすでにマークされているかどうかのチェックを有効にします。このオプションは、デフォルトでは無効になっており、複数のソケットを持つマシン上でのみ使用する必要があります。これにより、同時操作にかなり依存しているJavaアプリケーションのパフォーマンスが向上します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.PP +\-XX:+UseRTMDeopt +.RS 4 +中止率に応じて、RTMロックを自動調整します。この率は、\fB\-XX:RTMAbortRatio\fRオプションによって指定されます。中止されたトランザクション数が中止率を超えた場合、ロックを含むメソッドがすべてのロックで標準のロックとして非最適化および再コンパイルされます。このオプションは、デフォルトでは無効になっています。\fB\-XX:+UseRTMLocking\fRオプションを有効化する必要があります。 +.RE +.PP +\-XX:+UseRTMLocking +.RS 4 +フォールバック・ハンドラとして標準のロック・メカニズムを使用して、展開されたすべてのロックに対してRestricted Transactional Memory (RTM)ロック・コードを生成します。このオプションは、デフォルトでは無効になっています。RTMに関連するオプションは、Transactional Synchronization Extensions (TSX)をサポートするx86 CPU上のJava HotSpot Server VMに対してのみ使用可能です。 +.sp +RTMは、x86命令セット拡張でマルチスレッド・アプリケーションの作成を容易にするIntelのTSXの一部です。RTMでは、新しい命令 +\fBXBEGIN\fR、\fBXABORT\fR、\fBXEND\fRおよび\fBXTEST\fRが導入されています。\fBXBEGIN\fRおよび\fBXEND\fR命令は、トランザクションとして実行するための命令セットを囲みます。トランザクションの実行時に競合が見つからなかった場合、メモリーとレジスタの変更が、\fBXEND\fR命令で同時にコミットされます。\fBXABORT\fR命令ではトランザクションを明示的に中止でき、\fBXEND\fR命令では命令セットがトランザクション内で実行中かどうかを確認できます。 +.sp +トランザクションのロックは、別のスレッドが同じトランザクションにアクセスしようとしたときに展開されます。したがって、そのトランザクションへのアクセスを最初にリクエストしなかったスレッドはブロックされます。RTMでは、トランザクションが中止または失敗した場合のために、フォールバックの操作セットを指定する必要があります。RTMロックとは、TSXのシステムに委譲されているロックです。 +.sp +RTMにより、重要なリージョンにおいて衝突が少なく競合度の高いロックのパフォーマンスが向上されます(これは、複数のスレッドによって同時にアクセスできないコードです)。また、RTMにより、粗粒度ロックのパフォーマンスも向上されますが、一般的にマルチスレッド・アプリケーションでのパフォーマンスはよくありません。(粗粒度ロックとは、ロックの取得および解放のオーバーヘッドを最小化するために長い期間ロックを保持する戦略であり、一方、細粒度ロックとは必要な場合のみロックし可能なかぎり早期にロック解除することで最大限の並行処理の達成を試みる戦略です。)さらに、異なるスレッドによって使用されている軽度な競合ロックの場合、RTMにより、誤ったキャッシュ・ライン共有(キャッシュ・ライン・ピンポンとも呼ばれる)を削減できます。これは、異なるプロセッサからの複数のスレッドが異なるリソースにアクセスしている場合に発生しますが、リソースは同じキャッシュ・ラインを共有します。結果として、プロセッサは他のプロセッサのキャッシュ・ラインを繰り返し無効にし、これにより、キャッシュではなくメイン・メモリーからの読取りが強制されます。 +.RE +.PP +\-XX:+UseSHA +.RS 4 +SPARCハードウェアのSHA暗号化ハッシュ関数のハードウェアベースの組込みを有効にします。\fBUseSHA\fRは、\fBUseSHA1Intrinsics\fR、\fBUseSHA256Intrinsics\fRおよび\fBUseSHA512Intrinsics\fRオプションと組み合せて使用します。 +.sp +\fBUseSHA\fRおよび\fBUseSHA*Intrinsics\fRフラグはデフォルトで有効であり、SPARC T4以上のJava HotSpot Server VM 64ビットでのみサポートされます。 +.sp +SHA操作に対して\fBsun\&.security\&.provider\&.Sun\fRプロバイダを使用する場合のみ、この機能を適用できます。 +.sp +すべてのハードウェアベースのSHA組込みを無効化するには、\fB\-XX:\-UseSHA\fRを指定してください。特定のSHA組込みのみ無効化するには、適切な対応するオプションを使用してください。たとえば、\fB\-XX:\-UseSHA256Intrinsics\fRなどです。 +.RE +.PP +\-XX:+UseSHA1Intrinsics +.RS 4 +SHA\-1暗号化ハッシュ関数の組込みを有効にします。 +.RE +.PP +\-XX:+UseSHA256Intrinsics +.RS 4 +SHA\-224およびSHA\-256暗号化ハッシュ関数の組込みを有効にします。 +.RE +.PP +\-XX:+UseSHA512Intrinsics +.RS 4 +SHA\-384およびSHA\-512暗号化ハッシュ関数の組込みを有効にします。 +.RE +.PP +\-XX:+UseSuperWord +.RS 4 +スカラー演算のスーパーワード演算への変換を有効にします。このオプションはデフォルトで有効になっています。スカラー演算のスーパーワード演算への変換を無効にするには、\fB\-XX:\-UseSuperWord\fRを指定します。Java HotSpot Server VMのみが、このオプションをサポートしています。 +.RE +.SS "高度なサービスアビリティ・オプション" +.PP +これらのオプションは、システム情報を収集し、詳細なデバッグを実行する機能を提供します。 +.PP +\-XX:+ExtendedDTraceProbes +.RS 4 +パフォーマンスに影響を与える追加の\fBdtrace\fRツール・プローブを有効にします。デフォルトでは、このオプションは無効になっており、\fBdtrace\fRは標準プローブのみを実行します。 +.RE +.PP +\-XX:+HeapDumpOnOutOfMemory +.RS 4 +\fBjava\&.lang\&.OutOfMemoryError\fR例外がスローされた場合に、ヒープ・プロファイラ(HPROF)を使用して、現在のディレクトリ内のファイルへのJavaヒープのダンプを有効にします。\fB\-XX:HeapDumpPath\fRオプションを使用して、ヒープ・ダンプ・ファイルのパスおよび名前を明示的に設定できます。デフォルトでは、このオプションは無効であり、\fBOutOfMemoryError\fR例外がスローされた場合にヒープはダンプされません。 +.RE +.PP +\-XX:HeapDumpPath=\fIpath\fR +.RS 4 +\fB\-XX:+HeapDumpOnOutOfMemoryError\fRオプションが設定されている場合、ヒープ・プロファイラ(HPROF)が提供するヒープ・ダンプを書き込むパスおよびファイル名を設定します。デフォルトでは、このファイルは、現在の作業ディレクトリに作成され、名前は\fBjava_pid\fR\fIpid\fR\fB\&.hprof\fR +(\fIpid\fRはエラーの原因となったプロセスの識別子)になります。次の例では、デフォルトのファイルを明示的に設定する方法を示します(\fB%p\fRは現在のプロセスの識別子を表します)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:HeapDumpPath=\&./java_pid%p\&.hprof\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、ヒープ・ダンプ・ファイルを\fB/var/log/java/java_heapdump\&.hprof\fRに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:HeapDumpPath=/var/log/java/java_heapdump\&.hprof\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:LogFile=\fIpath\fR +.RS 4 +ログ・データが書き込まれるパスおよびファイル名を設定します。デフォルトでは、ファイルは現在の作業ディレクトリに作成され、名前は\fBhotspot\&.log\fRです。 +.sp +次の例では、ログ・ファイルを\fB/var/log/java/hotspot\&.log\fRに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:LogFile=/var/log/java/hotspot\&.log\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+PrintClassHistogram +.RS 4 +\fB[Control]+[C]\fRイベント(\fBSIGTERM\fR)後にクラス・インスタンスのヒストグラムの印刷を有効にします。デフォルトでは、このオプションは無効です。 +.sp +このオプションを設定すると、\fBjmap \-histo\fRコマンド、または\fBjcmd \fR\fIpid\fR\fB GC\&.class_histogram\fRコマンド(\fIpid\fRは現在のJavaプロセスの識別子)を実行する場合と同じになります。 +.RE +.PP +\-XX:+PrintConcurrentLocks +.RS 4 +印刷を有効にします ロック(次の後) \- イベント。デフォルトでは、このオプションは無効です。 +.sp +\fB[Control]+[C]\fRイベント(\fBSIGTERM\fR)後に\fBjava\&.util\&.concurrent\fRロックの印刷を有効にします。デフォルトでは、このオプションは無効です。 +.sp +このオプションを設定すると、\fBjstack \-l\fRコマンド、または\fBjcmd \fR\fIpid\fR\fB Thread\&.print \-l\fRコマンド(\fIpid\fRは現在のJavaプロセスの識別子)を実行する場合と同じになります。 +.RE +.PP +\-XX:+UnlockDiagnosticVMOptions +.RS 4 +JVMの診断を目的としたオプションをアンロックします。デフォルトでは、このオプションは無効であり、診断オプションは使用できません。 +.RE +.SS "高度なガベージ・コレクション・オプション" +.PP +これらのオプションは、ガベージ・コレクション(GC)がJava HotSpot VMによってどのように実行されるかを制御します。 +.PP +\-XX:+AggressiveHeap +.RS 4 +Javaヒープの最適化を有効にします。これにより、コンピュータの構成(RAMおよびCPU)に基づいて、様々なパラメータが、メモリー割当てが集中した長時間実行ジョブに最適になるように設定されます。デフォルトでは、このオプションは無効であり、ヒープは最適化されません。 +.RE +.PP +\-XX:+AlwaysPreTouch +.RS 4 +JVMの初期化中にJavaヒープ上のすべてのページのタッチを有効にします。これにより、\fBmain()\fRメソッドの入力前に、すべてのページがメモリーに取得されます。このオプションは、物理メモリーにマップされたすべての仮想メモリーを含む長時間実行のシステムをシミュレートするテストで使用できます。デフォルトでは、このオプションは無効になっており、JVMヒープ領域がいっぱいになると、すべてのページがコミットされます。 +.RE +.PP +\-XX:+CMSClassUnloadingEnabled +.RS 4 +並行マークスイープ(CMS)ガベージ・コレクタを使用する場合に、アンロードするクラスを有効にします。このオプションはデフォルトで有効になっています。CMSガベージ・コレクタのクラス・アンロードを無効にするには、\fB\-XX:\-CMSClassUnloadingEnabled\fRを指定します。 +.RE +.PP +\-XX:CMSExpAvgFactor=\fIpercent\fR +.RS 4 +並行コレクション統計の指数平均を計算する際に、現在のサンプルを重み付けするために使用される時間の割合(0から100まで)を設定します。デフォルトでは、指数平均係数は25%に設定されています。次の例では、係数を15%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSExpAvgFactor=15\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CMSInitiatingOccupancyFraction=\fIpercent\fR +.RS 4 +CMS収集サイクルを開始する古い世代の占有率(0から100まで)を設定します。デフォルト値は\-1に設定されています。負の値(デフォルトを含む)は、\fB\-XX:CMSTriggerRatio\fRが開始占有率の値を定義するために使用されることを意味します。 +.sp +次の例では、占有率を20%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSInitiatingOccupancyFraction=20\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+CMSScavengeBeforeRemark +.RS 4 +CMSコメント・ステップの前にスカベンジの試行を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:CMSTriggerRatio=\fIpercent\fR +.RS 4 +CMS収集サイクルが開始する前に割り当てられる\fB\-XX:MinHeapFreeRatio\fRによって指定される値の割合(0から100まで)を設定します。デフォルト値は80%に設定されています。 +.sp +次の例では、占有率を75%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSTriggerRatio=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:ConcGCThreads=\fIthreads\fR +.RS 4 +並行GCに使用されるスレッドの数を設定します。デフォルト値は、JVMに使用できるCPUの数によって異なります。 +.sp +たとえば、並行GCのスレッド数を2に設定するには、次のオプションを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ConcGCThreads=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+DisableExplicitGC +.RS 4 +\fBSystem\&.gc()\fRの呼出しの処理を無効にするオプションを有効にします。このオプションはデフォルトで無効になっており、これは\fBSystem\&.gc()\fRへの呼出しが処理されることを意味します。\fBSystem\&.gc()\fRの呼出しの処理が無効になっている場合、JVMは必要に応じてGCを実行します。 +.RE +.PP +\-XX:+ExplicitGCInvokesConcurrent +.RS 4 +\fBSystem\&.gc()\fRリクエストを使用することによって、並行GCの呼出しを有効にします。このオプションはデフォルトで無効になっており、\fB\-XX:+UseConcMarkSweepGC\fRオプションとともに使用する場合のみ、有効にすることができます。 +.RE +.PP +\-XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses +.RS 4 +\fBSystem\&.gc()\fRリクエストを使用し、並行GCサイクル中にクラスをアンロードすることによって、並行GCの呼出しを有効にします。このオプションはデフォルトで無効になっており、\fB\-XX:+UseConcMarkSweepGC\fRオプションとともに使用する場合のみ、有効にすることができます。 +.RE +.PP +\-XX:G1HeapRegionSize=\fIsize\fR +.RS 4 +ガベージファースト(G1)コレクタを使用する際にJavaヒープを細分化するリージョンのサイズを設定します。値には、1MBから32MBまでを指定できます。デフォルトのリージョン・サイズは、ヒープ・サイズに基づいて人間工学的に決定されます。 +.sp +次の例では、細分化されたサイズを16MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:G1HeapRegionSize=16m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+G1PrintHeapRegions +.RS 4 +割り当てられたリージョンおよびG1コレクタによって再要求されたものに関する情報の印刷を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:G1ReservePercent=\fIpercent\fR +.RS 4 +G1コレクタの昇格が失敗する可能性を減らすためのfalseの上限として予約されたヒープの割合(0から50まで)を設定します。デフォルトでは、このオプションは10%に設定されています。 +.sp +次の例では、予約されたヒープを20%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:G1ReservePercent=20\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:InitialHeapSize=\fIsize\fR +.RS 4 +メモリー割当てプールの初期サイズ(バイト単位)を設定します。指定する値は、0、または1MBより大きい1024の倍数のいずれかにする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は、実行時にシステム構成に基づいて選択されます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.htmlの\fIJava SE HotSpot仮想マシンのガベージ・コレクション・チューニング・ガイド\fRのエルゴノミクスに関する項を参照してください。 +.sp +次の例では、割り当てられたメモリーのサイズを様々な単位を使用して6MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialHeapSize=6291456\fR +\fB\-XX:InitialHeapSize=6144k\fR +\fB\-XX:InitialHeapSize=6m\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを0に設定した場合、初期サイズは、古い世代と若い世代に割り当てられたサイズの合計として設定されます。若い世代のヒープのサイズは、\fB\-XX:NewSize\fRオプションを使用して設定できます。 +.RE +.PP +\-XX:InitialSurvivorRatio=\fIratio\fR +.RS 4 +スループット・ガベージ・コレクタが使用するサバイバ領域の初期比を設定します(\fB\-XX:+UseParallelGC\fRおよび/または\fB\-XX:+UseParallelOldGC\fRオプションによって有効になります)。\fB\-XX:+UseParallelGC\fRオプションおよび\fB\-XX:+UseParallelOldGC\fRオプションを使用することによって、スループット・ガベージ・コレクタで適応サイズ指定をデフォルトで有効にします。初期値から始めて、アプリケーションの動作に従って、サバイバ領域がサイズ変更されます。(\fB\-XX:\-UseAdaptiveSizePolicy\fRオプションを使用して)適応サイズ指定を無効にした場合、\fB\-XX:SurvivorRatio\fRオプションを使用して、アプリケーションの実行全体のサバイバ領域のサイズを設定する必要があります。 +.sp +次の式を使用して、若い世代のサイズ(Y)およびサバイバ領域の初期比(R)に基づいて、サバイバ領域の初期サイズ(S)を計算できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBS=Y/(R+2)\fR + +.fi +.if n \{\ +.RE +.\} +等式内の2は、2つのサバイバ領域を示します。サバイバ領域の初期比に指定する値を大きくすると、サバイバ領域の初期サイズは小さくなります。 +.sp +デフォルトでは、サバイバ領域の初期比は8に設定されています。若い世代の領域サイズのデフォルト値(2MB)を使用した場合、サバイバ領域の初期サイズは0\&.2MBになります。 +.sp +次の例では、サバイバ領域の初期比を4に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialSurvivorRatio=4\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:InitiatingHeapOccupancyPercent=\fIpercent\fR +.RS 4 +並行GCサイクルを開始するヒープ占有率(0から100まで)を設定します。これは、1つの世代のみ(たとえばG1ガベージ・コレクタなど)ではなく、ヒープ全体の占有に基づいて並行GCサイクルをトリガーするガベージ・コレクタによって使用されます。 +.sp +デフォルトでは、開始値は45%に設定されています。値0は、GCサイクルが停止しないことを意味します。次の例では、開始ヒープ占有率を75%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitiatingHeapOccupancyPercent=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxGCPauseMillis=\fItime\fR +.RS 4 +最大GC休止時間(ミリ秒単位)のターゲットを設定します。これはソフト・ゴールのため、JVMは実現のために最善の努力をします。デフォルトでは、休止時間の最大値はありません。 +.sp +次の例では、最大ターゲット休止時間を500ミリ秒に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxGCPauseMillis=500\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxHeapSize=\fIsize\fR +.RS 4 +メモリー割当てプールの最大サイズ(バイト単位)を設定します。指定する値は、2MBより大きい1024の倍数にする必要があります。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。デフォルト値は、実行時にシステム構成に基づいて選択されます。サーバー・デプロイメントでは、\fB\-XX:InitialHeapSize\fRおよび\fB\-XX:MaxHeapSize\fRは通常同じ値に設定されます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.htmlの\fIJava SE HotSpot仮想マシンのガベージ・コレクション・チューニング・ガイド\fRのエルゴノミクスに関する項を参照してください。 +.sp +次の例では、割り当てられたメモリーの許可される最大サイズを様々な単位を使用して80MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxHeapSize=83886080\fR +\fB\-XX:MaxHeapSize=81920k\fR +\fB\-XX:MaxHeapSize=80m\fR + +.fi +.if n \{\ +.RE +.\} +Oracle Solaris 7およびOracle Solaris 8 SPARCプラットフォームの場合のこの値の上限は、およそ4,000MBからオーバーヘッドの量を引いたものです。Oracle Solaris 2\&.6およびx86プラットフォームの場合の上限は、およそ2,000MBからオーバーヘッドの量を引いたものです。Linuxプラットフォームの場合の上限は、およそ2,000MBからオーバーヘッドの量を引いたものです。 +.sp +\fB\-XX:MaxHeapSize\fRオプションは\fB\-Xmx\fRと同等です。 +.RE +.PP +\-XX:MaxHeapFreeRatio=\fIpercent\fR +.RS 4 +GCイベント後の空きヒープ領域の許可されている最大の割合(0から100まで)を設定します。空きヒープ領域がこの値を超えて拡大した場合、そのヒープは縮小します。デフォルトでは、この値は70%に設定されています。 +.sp +次の例では、空きヒープの最大比率を75%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxHeapFreeRatio=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxMetaspaceSize=\fIsize\fR +.RS 4 +クラス・メタデータに割り当てることができるネイティブ・メモリーの最大量を設定します。デフォルトでは、このサイズは制限されていません。アプリケーションのメタデータの量は、アプリケーション自体、他の実行中アプリケーション、およびシステムで使用可能なメモリーの量によって異なります。 +.sp +次の例では、クラス・メタデータの最大サイズを256MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxMetaspaceSize=256m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxNewSize=\fIsize\fR +.RS 4 +若い世代(ナーサリ)のヒープの最大サイズ(バイト単位)を設定します。デフォルト値は人間工学的に設定されます。 +.RE +.PP +\-XX:MaxTenuringThreshold=\fIthreshold\fR +.RS 4 +適応GCサイズ指定で使用する最大殿堂入りしきい値を設定します。最大値は15です。デフォルト値は、パラレル(スループット)コレクタの場合は15、CMSコレクタの場合は6です。 +.sp +次の例では、最大殿堂入りしきい値を10に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxTenuringThreshold=10\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MetaspaceSize=\fIsize\fR +.RS 4 +最初に超えたときにガベージ・コレクションをトリガーする、割り当てられたクラス・メタデータ領域のサイズを設定します。このガベージ・コレクションのしきい値は、使用されるメタデータの量によって増加または減少します。デフォルトのサイズはプラットフォームによって異なります。 +.RE +.PP +\-XX:MinHeapFreeRatio=\fIpercent\fR +.RS 4 +GCイベント後の空きヒープ領域の許可されている最小の割合(0から100まで)を設定します。空きヒープ領域がこの値を下回った場合、そのヒープは拡大します。デフォルトでは、この値は40%に設定されています。 +.sp +次の例では、空きヒープの最小比率を25%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MinHeapFreeRatio=25\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NewRatio=\fIratio\fR +.RS 4 +若い世代のサイズと古い世代のサイズとの比率を設定します。デフォルトでは、このオプションは2に設定されています。次の例では、若い/古いの比率を1に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:NewRatio=1\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NewSize=\fIsize\fR +.RS 4 +若い世代(ナーサリ)のヒープの初期サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。 +.sp +ヒープの若い世代リージョンは新しいオブジェクトに使用されます。GCは、他のリージョンよりこのリージョンで、より頻繁に実行されます。若い世代のサイズが小さすぎる場合、多数のマイナーGCが実行されます。サイズが大きすぎる場合、フルGCのみが実行されますが、完了までに時間がかかることがあります。若い世代のサイズは、全体のヒープ・サイズの半分から4分の1の間にしておくことをお薦めします。 +.sp +次の例では、若い世代の初期サイズを様々な単位を使用して256MBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:NewSize=256m\fR +\fB\-XX:NewSize=262144k\fR +\fB\-XX:NewSize=268435456\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-XX:NewSize\fRオプションは\fB\-Xmn\fRと同等です。 +.RE +.PP +\-XX:ParallelGCThreads=\fIthreads\fR +.RS 4 +若い世代と古い世代でパラレル・ガベージ・コレクションに使用するスレッドの数を設定します。デフォルト値は、JVMに使用できるCPUの数によって異なります。 +.sp +たとえば、パラレルGCのスレッド数を2に設定するには、次のオプションを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ParallelGCThreads=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+ParallelRefProcEnabled +.RS 4 +パラレル参照処理を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintAdaptiveSizePolicy +.RS 4 +適応世代サイズ指定に関する情報の出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGC +.RS 4 +GCごとのメッセージの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCApplicationConcurrentTime +.RS 4 +最後の休止(たとえばGC休止など)以降に経過した時間の出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCApplicationStoppedTime +.RS 4 +休止(たとえばGC休止など)が継続した時間の出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCDateStamps +.RS 4 +GCごとの日付スタンプの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCDetails +.RS 4 +GCごとの詳細メッセージの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCTaskTimeStamps +.RS 4 +個々のGCワーカー・スレッド・タスクごとのタイムスタンプの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintGCTimeStamps +.RS 4 +GCごとのタイムスタンプの出力を有効にします。デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+PrintStringDeduplicationStatistics +.RS 4 +詳細な重複除外統計を印刷します。デフォルトでは、このオプションは無効です。\fB\-XX:+UseStringDeduplication\fRオプションを参照してください。 +.RE +.PP +\-XX:+PrintTenuringDistribution +.RS 4 +殿堂入り期間情報の出力を有効にします。次に、出力の例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBDesired survivor size 48286924 bytes, new threshold 10 (max 10)\fR +\fB\- age 1: 28992024 bytes, 28992024 total\fR +\fB\- age 2: 1366864 bytes, 30358888 total\fR +\fB\- age 3: 1425912 bytes, 31784800 total\fR +\fB\&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +期間1オブジェクトは、最も若いサバイバです(前のスカベンジの後に作成され、最新のスカベンジで存続し、Eden領域からサバイバ領域に移動しました)。期間2オブジェクトは、2つのスカベンジで存続します(2番目のスカベンジ中に、あるサバイバ領域から次の領域にコピーされました)。このように続きます。 +.sp +前述の例では、28,992,024バイトが1つのスカベンジで存続し、Eden領域からサバイバ領域にコピーされました。1,366,864バイトは期間2オブジェクトなどにより占有されています。各行の3番目の値は、期間n以下のオブジェクトの累積サイズです。 +.sp +デフォルトでは、このオプションは無効です。 +.RE +.PP +\-XX:+ScavengeBeforeFullGC +.RS 4 +それぞれのフルGCの前に若い世代のGCを有効にします。このオプションはデフォルトで有効になっています。フルGCの前に若い世代のスカベンジを行うと、古い世代領域から若い世代領域へのアクセスが可能なオブジェクトの数を減らすことができるため、これを無効に\fIしない\fRことをお薦めします。各フルGCの前に若い世代のGCを無効にするには、\fB\-XX:\-ScavengeBeforeFullGC\fRを指定します。 +.RE +.PP +\-XX:SoftRefLRUPolicyMSPerMB=\fItime\fR +.RS 4 +ソフト・アクセスが可能なオブジェクトが最後に参照されてからヒープ上でアクティブなままになっている時間(ミリ秒単位)を設定します。デフォルト値は、ヒープ内の空きメガバイト当たりで1秒の存続期間です。\fB\-XX:SoftRefLRUPolicyMSPerMB\fRオプションは、現在のヒープ・サイズ(Java HotSpot Client VM用)または最大可能ヒープ・サイズ(Java HotSpot Server VM用)の1メガバイト当たりのミリ秒を表す整数値を受け入れます。この違いは、Client VMは、ヒープを大きくするのではなく、ソフト参照をフラッシュする傾向があるのに対し、Server VMは、ソフト参照をフラッシュするのではなく、ヒープを大きくする傾向があることを意味します。後者の場合、\fB\-Xmx\fRオプションの値は、ソフト参照がどのくらい迅速にガベージ・コレクションされるかに重要な影響を及ぼします。 +.sp +次の例では、値を2\&.5秒に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:SoftRefLRUPolicyMSPerMB=2500\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:StringDeduplicationAgeThreshold=\fIthreshold\fR +.RS 4 +指定した期間に到達しつつある\fBString\fRオブジェクトは、重複除外の候補とみなされます。オブジェクトの期間は、オブジェクトがガベージ・コレクションで存続した回数の測定値です。これは、殿堂入りと呼ばれる場合もあります。\fB\-XX:+PrintTenuringDistribution\fRオプションを参照してください。この期間に到達する前に古いヒープ・リージョンに昇格された\fBString\fRオブジェクトは、常に重複除外の候補とみなされます。このオプションのデフォルト値は\fB3\fRです。\fB\-XX:+UseStringDeduplication\fRオプションを参照してください。 +.RE +.PP +\-XX:SurvivorRatio=\fIratio\fR +.RS 4 +Eden領域のサイズとサバイバ領域のサイズとの比率を設定します。デフォルトでは、このオプションは8に設定されています。次の例では、Eden/サバイバ領域の比率を4に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:SurvivorRatio=4\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:TargetSurvivorRatio=\fIpercent\fR +.RS 4 +若いガベージ・コレクションの後に使用されるサバイバ領域の目的の割合(0から100まで)を設定します。デフォルトでは、このオプションは50%に設定されています。 +.sp +次の例では、ターゲットのサバイバ領域の比率を30%に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:TargetSurvivorRatio=30\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:TLABSize=\fIsize\fR +.RS 4 +スレッド・ローカルな割当てバッファ(TLAB)の初期サイズ(バイト単位)を設定します。キロバイトを示す場合は文字\fBk\fRまたは\fBK\fR、メガバイトを示す場合は文字\fBm\fRまたは\fBM\fR、ギガバイトを示す場合は文字\fBg\fRまたは\fBG\fRを追加します。このオプションが0に設定されている場合、JVMでは初期サイズが自動的に選択されます。 +.sp +次の例では、TLABの初期サイズを512KBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:TLABSize=512k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+UseAdaptiveSizePolicy +.RS 4 +適応世代サイズ指定の使用を有効にします。このオプションはデフォルトで有効になっています。適応世代サイズ指定を無効にするには、\fB\-XX:\-UseAdaptiveSizePolicy\fRを指定し、メモリー割当てプールのサイズを明示的に設定します(\fB\-XX:SurvivorRatio\fRオプションを参考にしてください)。 +.RE +.PP +\-XX:+UseCMSInitiatingOccupancyOnly +.RS 4 +CMSコレクタの開始のための唯一の基準としての占有値の使用を有効にします。デフォルトでは、このオプションは無効になっており、他の基準が使用されます。 +.RE +.PP +\-XX:+UseConcMarkSweepGC +.RS 4 +古い世代へのCMSガベージ・コレクタの使用を有効にします。アプリケーションの待機時間の要件を、スループット(\fB\-XX:+UseParallelGC\fR)ガベージ・コレクタによって満たすことができない場合、CMSガベージ・コレクタを使用することをお薦めします。G1ガベージ・コレクタ(\fB\-XX:+UseG1GC\fR)は別の代替となります。 +.sp +デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。このオプションが有効な場合、\fB\-XX:+UseParNewGC\fRオプションは自動的に設定され、無効化しない必要がありますが、理由はJDK 8では\fB\-XX:+UseConcMarkSweepGC \-XX:\-UseParNewGC\fRオプションの組合せが非推奨であるためです。 +.RE +.PP +\-XX:+UseG1GC +.RS 4 +ガベージファースト(G1)・ガベージ・コレクタの使用を有効にします。これはサーバー形式のガベージ・コレクタで、大量のRAMを持つマルチプロセッサ・マシンを対象としています。高い確率でGC休止時間の目標を達成し、同時に適切なスループットも維持します。G1コレクタは、GC待機時間の限定された要件(安定した予測可能な0\&.5秒未満の休止時間)を持つ、大きいヒープ(約6GB以上のサイズ)が必要なアプリケーションに推奨されます。 +.sp +デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。 +.RE +.PP +\-XX:+UseGCOverheadLimit +.RS 4 +\fBOutOfMemoryError\fR例外がスローされるまでに、GCでJVMによって要した時間の割合を制限するポリシーの使用を有効にします。デフォルトでは、このオプションは有効になっており、ガベージ・コレクションに合計時間の98%より多く費やされ、ヒープのリカバリが2%未満である場合、パラレルGCによって\fBOutOfMemoryError\fRがスローされます。ヒープが小さい場合、この機能は、アプリケーションが長期間ほとんどまたはまったく進捗なく実行している状態を回避するために使用できます。このオプションを無効にするには、\fB\-XX:\-UseGCOverheadLimit\fRを指定します。 +.RE +.PP +\-XX:+UseNUMA +.RS 4 +アプリケーションで短い待機時間のメモリーの使用を増加させることで、不均一なメモリー・アーキテクチャ(NUMA)を使用したマシン上のアプリケーションのパフォーマンス最適化を有効にします。デフォルトでは、このオプションは無効になっており、NUMAに対する最適化は行われません。このオプションは、パラレル・ガベージ・コレクタ(\fB\-XX:+UseParallelGC\fR)が使用されている場合のみ使用可能です。 +.RE +.PP +\-XX:+UseParallelGC +.RS 4 +複数のプロセッサを利用してアプリケーションのパフォーマンスを向上させる、パラレル・スカベンジ・ガベージ・コレクタ(スループット・コレクタとも呼ばれる)の使用を有効にします。 +.sp +デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。これを有効にした場合、明示的に無効にしないかぎり、\fB\-XX:+UseParallelOldGC\fRオプションが自動的に有効になります。 +.RE +.PP +\-XX:+UseParallelOldGC +.RS 4 +フルGCへのパラレル・ガベージ・コレクタの使用を有効にします。デフォルトでは、このオプションは無効です。これを有効にすると、\fB\-XX:+UseParallelGC\fRオプションが自動的に有効になります。 +.RE +.PP +\-XX:+UseParNewGC +.RS 4 +若い世代でのコレクションへのパラレル・スレッドの使用を有効にします。デフォルトでは、このオプションは無効です。\fB\-XX:+UseConcMarkSweepGC\fRオプションを設定すると、これは自動的に有効になります。JDK 8では、\fB\-XX:+UseConcMarkSweepGC\fRオプションを指定せずに\fB\-XX:+UseParNewGC\fRオプションを使用することは非推奨です。 +.RE +.PP +\-XX:+UseSerialGC +.RS 4 +シリアル・ガベージ・コレクタの使用を有効にします。ガベージ・コレクションから特別な機能を必要としない、小規模で単純なアプリケーションの場合には、これは一般に最適な選択です。デフォルトでは、このオプションは無効になっており、コレクタは、マシンの構成およびJVMのタイプに基づいて、自動的に選択されます。 +.RE +.PP +\-XX:+UseSHM +.RS 4 +Linuxでは、JVMで共有メモリーを使用してラージ・ページを設定できるようにします。 +.sp +詳細は、"ラージ・ページ"を参照してください。 +.RE +.PP +\-XX:+UseStringDeduplication +.RS 4 +文字列の重複除外を有効化します。デフォルトでは、このオプションは無効です。このオプションを使用するには、ガベージファースト(G1)・ガベージ・コレクタを有効にする必要があります。\fB\-XX:+UseG1GC\fRオプションを参照してください。 +.sp +多くの\fBString\fRオブジェクトが同じであるということから、\fIString deduplication\fRにより、Javaヒープ上の\fBString\fRオブジェクトのメモリー・フットプリントが削減されます。各\fBString\fRオブジェクトが独自の文字配列をポイントするのではなく、同一の\fBString\fRオブジェクトは同じ文字配列をポイントし共有できます。 +.RE +.PP +\-XX:+UseTLAB +.RS 4 +若い世代の領域でのスレッド・ローカルな割当てブロック(TLAB)の使用を有効にします。このオプションはデフォルトで有効になっています。TLABの使用を無効にするには、\fB\-XX:\-UseTLAB\fRを指定します。 +.RE +.SS "非推奨で削除されたオプション" +.PP +これらのオプションは、以前のリリースには含まれていましたが、以降は不要とみなされています。 +.PP +\-Xincgc +.RS 4 +インクリメンタル・ガベージ・コレクションを有効にします。このオプションはJDK 8では非推奨で、それに代わるものはありません。 +.RE +.PP +\-Xrun\fIlibname\fR +.RS 4 +指定したデバッグ/プロファイリングのライブラリをロードします。このオプションは、\fB\-agentlib\fRオプションに取って代わられました。 +.RE +.PP +\-XX:CMSIncrementalDutyCycle=\fIpercent\fR +.RS 4 +並行コレクタの実行が許可されているマイナー・コレクション間の時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:CMSIncrementalDutyCycleMin=\fIpercent\fR +.RS 4 +\fB\-XX:+CMSIncrementalPacing\fRが有効な場合にデューティ・サイクルの下限であるマイナー・コレクション間の時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:+CMSIncrementalMode +.RS 4 +CMSコレクタの増分モードを有効にします。\fBCMSIncremental\fRで始まるその他のオプションとともに、このオプションはJDK 8では非推奨となり、それに代わるものはありません +.RE +.PP +\-XX:CMSIncrementalOffset=\fIpercent\fR +.RS 4 +増分モードのデューティ・サイクルをマイナー・コレクション間で期間内に右に移動する時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:+CMSIncrementalPacing +.RS 4 +JVMの実行中に収集された統計に基づいて、増分モードのデューティ・サイクルの自動調整を有効にします。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:CMSIncrementalSafetyFactor=\fIpercent\fR +.RS 4 +デューティ・サイクルを計算する際に、保守を追加するために使用される時間の割合(0から100まで)を設定します。\fB\-XX:+CMSIncrementalMode\fRオプションの非推奨を受けて、このオプションはJDK 8では非推奨となり、それに代わるものはありません。 +.RE +.PP +\-XX:CMSInitiatingPermOccupancyFraction=\fIpercent\fR +.RS 4 +GCを開始する永久世代占有率(0から100まで)を設定します。このオプションはJDK 8では非推奨で、それに代わるものはありません。 +.RE +.PP +\-XX:MaxPermSize=\fIsize\fR +.RS 4 +永久世代領域の最大サイズ(バイト単位)を設定します。このオプションは、JDK 8で非推奨になり、\fB\-XX:MaxMetaspaceSize\fRオプションに取って代わられました。 +.RE +.PP +\-XX:PermSize=\fIsize\fR +.RS 4 +超えた場合にはガベージ・コレクションをトリガーする、永久世代に割り当てられた領域(バイト単位)を設定します。このオプションは、JDK 8で非推奨になり、\fB\-XX:MetaspaceSize\fRオプションに取って代わられました。 +.RE +.PP +\-XX:+UseSplitVerifier +.RS 4 +検証プロセスの分割を有効にします。デフォルトでは、このオプションは以前のリリースでは有効になっており、検証は、タイプ参照(コンパイラによって実行)と、タイプ・チェック(JVMランタイムによって実行)の2つのフェーズに分割されていました。このオプションはJDK 8で非推奨となり、検証はデフォルトで分割され、無効にする方法はありません。 +.RE +.PP +\-XX:+UseStringCache +.RS 4 +一般に割り当てられた文字列のキャッシングを有効にします。このオプションはJDK 8から削除され、それに代わるものはありません。 +.RE +.SH "パフォーマンス・チューニングの例" +.PP +次の例では、スループットの最適化またはレスポンス時間の短縮化のいずれかを行うための、試験的なチューニング・フラグの使用方法を示します。 +.PP +\fB例 1 \fRスループットを向上するためのチューニング +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-d64 \-server \-XX:+AggressiveOpts \-XX:+UseLargePages \-Xmn10g \-Xms26g \-Xmx26g\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRレスポンス時間を速くするためのチューニング +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-d64 \-XX:+UseG1GC \-Xms26g Xmx26g \-XX:MaxGCPauseMillis=500 \-XX:+PrintGCTimeStamp\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "ラージ・ページ" +.PP +ヒュージ・ページとも呼ばれるラージ・ページは、標準のメモリー・ページ・サイズ(プロセッサおよびオペレーティング・システムによって異なります)よりはるかに大きいメモリー・ページです。ラージ・ページは、プロセッサのTranslation\-Lookaside Bufferを最適化します。 +.PP +Translation\-Lookaside Buffer (TLB)は、最近使用された仮想から物理へのアドレス変換を保持するページ変換キャッシュです。TLBは、少ないシステム・リソースです。プロセッサが複数のメモリー・アクセスが必要な場合のある階層ページ表から読み取る必要があるため、TLBミスは負荷がかかる可能性があります。大きいメモリー・ページ・サイズを使用して、単一のTLBエントリで大きいメモリー範囲を表すことができます。TLB不足が少なくなり、メモリー集約型のアプリケーションのパフォーマンスが向上する可能性があります。 +.PP +ただし、ラージ・ページのページ・メモリーは、システムのパフォーマンスに悪影響を与える場合があります。たとえば、大量のメモリーがアプリケーションで確保される場合、通常メモリー不足や他のアプリケーションの過剰なページングが発生し、システム全体が遅くなる可能性があります。また、長時間稼働しているシステムは、過剰な断片化が発生する可能性があります。これにより、十分な大きさのページ・メモリーを予約できない可能性があります。これが発生した場合、OSまたはJVMのいずれかが通常のページの使用に戻ります。 +.SS "ラージ・ページのサポート" +.PP +SolarisおよびLinuxは、ラージ・ページをサポートします。 +.sp +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBSolaris\fR +.RS 4 +.PP +Solaris 9以上には、Multiple Page Size Support(MPSS)が含まれています。追加の構成は必要ありません。http://www\&.oracle\&.com/technetwork/server\-storage/solaris10/overview/solaris9\-features\-scalability\-135663\&.htmlを参照してください。 +.RE +.sp +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBLinux\fR +.RS 4 +.PP +2\&.6カーネルは、ラージ・ページをサポートします。一部のベンダーは、2\&.4ベースのリリースのコードをバックポートしています。システムがラージ・ページ・メモリーをサポートしているかどうかを確認するには、次を試行してください: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# cat /proc/meminfo | grep Huge\fR +\fBHugePages_Total: 0\fR +\fBHugePages_Free: 0\fR +\fBHugepagesize: 2048 kB\fR + +.fi +.if n \{\ +.RE +.\} +.PP +出力に3つの"Huge"変数が示されている場合、システムはラージ・ページ・メモリーをサポートしていますが、構成する必要があります。コマンドが何も出力しない場合、システムはラージ・ページをサポートしていません。ラージ・ページ・メモリーを使用するシステムを構成するには、\fBroot\fRとしてログインして、次の手順を実行してください: +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +オプション\fB\-XX:+UseSHM\fR(\fB\-XX:+UseHugeTLBFS\fRのかわり)を使用する場合、\fBSHMMAX\fR値を増やしてください。Javaヒープ・サイズより大きくする必要があります。4GB以下の物理RAMを使用したシステムで、次によりすべてのメモリーが共有可能になります: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# echo 4294967295 > /proc/sys/kernel/shmmax\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +オプション\fB\-XX:+UseSHM\fRまたは\fB\-XX:+UseHugeTLBFS\fRを使用する場合、ラージ・ページの数を指定してください。次の例では、4GBシステムの3GBがラージ・ページに予約されます(2048KBのラージ・ページ・サイズを仮定する場合、3GB = 3 * 1024MB = 3072MB = 3072 * 1024KB = 3145728KB and 3145728KB / 2048KB = 1536): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# echo 1536 > /proc/sys/vm/nr_hugepages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fB注記\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +注意 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +システムを再起動した後に\fB/proc\fRに含まれる値がリセットされるので注意してください。そのため、初期化スクリプト(\fBrc\&.local\fRや\fBsysctl\&.conf\fRなど)で設定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OSカーネル・パラメータ\fB/proc/sys/kernel/shmmax\fRまたは\fB/proc/sys/vm/nr_hugepages\fRを構成(またはサイズ変更)する場合、JavaプロセスがJavaヒープ以外の領域に対してラージ・ページを割り当てることがあります。これらの手順を使用して、次の領域に対してラージ・ページを割り当てることができます: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javaヒープ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Permanent世代 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コード・キャッシュ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パラレルGCのマーキング・ビットマップ・データ構造 +.RE +.sp +その結果、Javaヒープのサイズに\fBnr_hugepages\fRパラメータを構成すると、領域のサイズが非常に大きいためにJVMがPermanent世代およびラージ・ページのコード・キャッシュ領域の割当てに失敗する場合があります。 +.RE +T} +.TE +.sp 1 +.sp .5v +.RE +.RE +.SH "終了ステータス" +.PP +通常、次の終了値が起動ツールから返されるのは、起動元が不正な引数で呼び出されたか、深刻なエラーが発生したか、あるいはJVMにより例外がスローされた場合です。ただし、Javaアプリケーションは、API呼出し\fBSystem\&.exit(exitValue)\fRを使用して任意の値を返すことを選択することもできます。値は次のとおりです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB0\fR: 正常終了 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB>0\fR: エラー発生 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javac.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javac.1 new file mode 100755 index 0000000..8b2a0b6 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javac.1 @@ -0,0 +1,1557 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javac +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javac" "1" "2015å¹´3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javac \- Javaクラスおよびインタフェースの定義を読み取り、バイトコードおよびクラス・ファイルにコンパイルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac\fR [ \fIoptions\fR ] [ \fIsourcefiles\fR ] [ \fIclasses\fR] [ \fI@argfiles\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +引数を指定する順序は任意です。 +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIsourcefiles\fR +.RS 4 +コンパイルされる1つ以上のソース・ファイル(\fBMyClass\&.java\fRなど)。 +.RE +.PP +\fIclasses\fR +.RS 4 +注釈の処理対象となる1つ以上のクラス(\fBMyPackage\&.MyClass\fRなど)。 +.RE +.PP +\fI@argfiles\fR +.RS 4 +オプションとソース・ファイルを一覧表示する1つ以上のファイル。このファイルの中では\fB\-J\fRオプションは指定できません。コマンド行引数ファイルを参照してください。 +.RE +.SH "説明" +.PP +\fBjavac\fRコマンドは、Javaプログラミング言語で記述されたクラスとインタフェースの定義を読み取り、バイトコードのクラス・ファイルにコンパイルします。\fBjavac\fRコマンドでは、Javaソース・ファイルおよびクラス内の注釈の処理もできます。 +.PP +ソース・コードのファイル名を\fBjavac\fRに渡すには、2つの方法があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ソース・ファイルの数が少ない場合は、ファイル名をコマンドラインで指定します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ソース・ファイルの数が多い場合は、ファイル内のファイル名を空白または改行で区切って指定します。\fBjavac\fRコマンドで、リスト・ファイル名の先頭にアットマーク(@)を使用します。 +.RE +.PP +ソース・コードのファイル名は\&.java拡張子を、クラスのファイル名は\&.class拡張子を持っている必要があります。また、ソース・ファイルとクラス・ファイルのどちらも、該当するクラスに対応するルート名を持っている必要があります。たとえば、\fBMyClass\fRという名前のクラスは、\fBMyClass\&.java\fRという名前のソース・ファイルに記述されます。このソース・ファイルは、\fBMyClass\&.class\fRという名前のバイトコード・クラス・ファイルにコンパイルされます。 +.PP +内部クラスが定義されていると、追加のクラス・ファイルが生成されます。これらのクラス・ファイルの名前は、\fBMyClass$MyInnerClass\&.class\fRのように、内部クラス名と外部クラス名を組み合せたものになります。 +.PP +ソース・ファイルは、パッケージ・ツリーを反映したディレクトリ・ツリーに配置します。たとえば、すべてのソース・ファイルが\fB/workspace\fRにある場合、\fBcom\&.mysoft\&.mypack\&.MyClass\fRのソース・コードを、\fB/workspace/com/mysoft/mypack/MyClass\&.java\fRに格納します。 +.PP +デフォルトでは、コンパイラは、各クラス・ファイルを対応するソース・ファイルと同じディレクトリに格納します。\fB\-d\fRオプションを使用して、別の出力先ディレクトリを指定できます。 +.SH "オプション" +.PP +コンパイラには、現在の開発環境でサポートされる標準オプションのセットがあります。これ以外の非標準オプションは、現在の仮想マシンおよびコンパイラの実装に固有のオプションで、将来、変更される可能性があります。非標準オプションは、\fB\-X\fRオプションで始まります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クロスコンパイル・オプションも参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非標準オプションも参照してください +.RE +.SS "標準オプション" +.PP +\-A\fIkey\fR[\fI=value\fR] +.RS 4 +注釈プロセッサに渡すオプションを指定します。これらのオプションは、\fBjavac\fRが直接解釈するのではなく、それぞれのプロセッサで使用できるようになります。\fBkey\fRの値は、1つまたは複数の識別子をドット(\&.)で区切る必要があります。 +.RE +.PP +\-cp \fIpath\fR or \-classpath \fIpath\fR +.RS 4 +ユーザー・クラス・ファイル、および(オプションで)注釈プロセッサとソース・ファイルを検索する場所を指定します。このクラス・パスは\fBCLASSPATH\fR環境変数のユーザー・クラス・パスをオーバーライドします。\fBCLASSPATH\fR、\fB\-cp\fR、\fB\-classpath\fRのいずれも指定されていない場合、ユーザーの\fIクラス・パス\fRは、現在のディレクトリになります。クラス・パスの設定 を参照してください。 +.sp +\fB\-sourcepath\fRオプションが指定されていない場合、ソース・ファイルもユーザー・クラス・パスから検索されます。 +.sp +\fB\-processorpath\fRオプションが指定されていない場合、注釈プロセッサもクラス・パスから検索されます。 +.RE +.PP +\-Djava\&.ext\&.dirs=\fIdirectories\fR +.RS 4 +インストール済拡張機能の位置をオーバーライドします。 +.RE +.PP +\-Djava\&.endorsed\&.dirs=\fIdirectories\fR +.RS 4 +承認された標準パスの位置をオーバーライドします。 +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +クラス・ファイルの出力先ディレクトリを設定します。そのディレクトリは\fBjavac\fRでは作成されないため、すでに存在している必要があります。クラスがパッケージの一部である場合、\fBjavac\fRは、パッケージ名を反映したサブディレクトリ内にクラス・ファイルを格納し、必要に応じてディレクトリを作成します。 +.sp +\fB\-d\fR +\fB/home/myclasses\fRと指定し、クラスの名前が\fBcom\&.mypackage\&.MyClass\fRである場合、クラス・ファイルは\fB/home/myclasses/com/mypackage/MyClass\&.class\fRになります。 +.sp +\fI\-d\fRオプションが指定されなかった場合、\fBjavac\fRは、各クラス・ファイルを、その生成元となるソース・ファイルと同じディレクトリ内に格納します。 +.sp +\fB注意:\fR +\fI\-d\fRオプションによって指定されたディレクトリは、ユーザー・クラス・パスに自動的に追加されません。 +.RE +.PP +\-deprecation +.RS 4 +非推奨のメンバーまたはクラスが使用またはオーバーライドされるたびに、説明を表示します。\fB\-deprecation\fRオプションが指定されていない場合、\fBjavac\fRは、非推奨のメンバーまたはクラスを使用またはオーバーライドしているソース・ファイルのサマリーを表示します。\fB\-deprecation\fRオプションは、\fB\-Xlint:deprecation\fRの省略表記です。 +.RE +.PP +\-encoding \fIencoding\fR +.RS 4 +ソース・ファイルのエンコーディング名(EUC\-JPやUTF\-8など)を設定します。\fB\-encoding\fRオプションが指定されていない場合は、プラットフォームのデフォルト・コンバータが使用されます。 +.RE +.PP +\-endorseddirs \fIdirectories\fR +.RS 4 +承認された標準パスの位置をオーバーライドします。 +.RE +.PP +\-extdirs \fIdirectories\fR +.RS 4 +\fBext\fRディレクトリの位置をオーバーライドします。directories変数には、コロンで区切ったディレクトリのリストを指定します。指定したディレクトリ内の各JARファイルから、クラス・ファイルが検索されます。検出されたすべてのJARファイルは、クラス・パスの一部になります。 +.sp +クロスコンパイル(異なるJavaプラットフォームに実装されたブートストラップ・クラスや拡張機能クラスに対してコンパイルを行う)を実行する場合、このオプションには拡張機能クラスを含むディレクトリを指定します。詳細はクロスコンパイル・オプションを参照してください。 +.RE +.PP +\-g +.RS 4 +ローカル変数を含むすべてのデバッグ情報を生成します。デフォルトでは、行番号およびソース・ファイル情報のみが生成されます。 +.RE +.PP +\-g:none +.RS 4 +デバッグ情報を生成しません。 +.RE +.PP +\-g:[\fIkeyword list\fR] +.RS 4 +カンマで区切られたキーワード・リストにより指定された、特定の種類のデバッグ情報のみを生成します。次のキーワードが有効です。 +.PP +source +.RS 4 +ソース・ファイルのデバッグ情報。 +.RE +.PP +lines +.RS 4 +行番号のデバッグ情報。 +.RE +.PP +vars +.RS 4 +ローカル変数のデバッグ情報。 +.RE +.RE +.PP +\-help +.RS 4 +標準オプションの概要を出力します。 +.RE +.PP +\-implicit:[\fIclass, none\fR] +.RS 4 +暗黙的にロードされたソース・ファイルに対するクラス・ファイルの生成を制御します。クラス・ファイルを自動生成するには、\fB\-implicit:class\fRを使用します。クラス・ファイルの生成を抑制するには、\fB\-implicit:none\fRを使用します。このオプションが指定されなかった場合のデフォルト動作は、クラス・ファイルの自動生成になります。その場合、そのようなクラス・ファイルが生成された時に注釈処理も実行されると、コンパイラから警告が発行されます。\fB\-implicit\fRオプションが明示的に設定された場合、警告は発行されません。型の検索を参照してください。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machine (JVM)に\fBoption\fRを渡します。optionには、Java起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.sp +\fB注意:\fR +\fICLASSPATH\fR、\fB\-classpath\fR、\fB\-bootclasspath\fRおよび\fB\-extdirs\fRオプションは、\fBjavac\fRの実行に使用されるクラスを指定しません。これらのオプションおよび変数を使用してコンパイラの実装をカスタマイズしようとすると、リスクが高く、多くの場合、必要な処理が実行されません。コンパイラの実装をカスタマイズする必要がある場合、\fB\-J\fRオプションを使用して、基礎となるJava起動ツールにオプションを渡します。 +.RE +.PP +\-nowarn +.RS 4 +警告メッセージを無効にします。このオプションは、\fB\-Xlint:none\fRオプションと同じように動作します。 +.RE +.PP +\-parameters +.RS 4 +リフレクションAPIのメソッド\fBjava\&.lang\&.reflect\&.Executable\&.getParameters\fRが取得できるように、生成されるクラス・ファイル内のコンストラクタとメソッドの仮パラメータ名を格納します。 +.RE +.PP +\-proc: [\fInone\fR, \fIonly\fR] +.RS 4 +注釈処理およびコンパイルを実行するかを制御します。\fB\-proc:none\fRは、注釈処理なしでコンパイルが実行されることを意味します。\fB\-proc:only\fRは、注釈処理のみが実行され、後続のコンパイルはまったく実行されないことを意味します。 +.RE +.PP +\-processor \fIclass1\fR [,\fIclass2\fR,\fIclass3\fR\&.\&.\&.] +.RS 4 +実行する注釈プロセッサの名前。これを指定した場合、デフォルトの検索処理は省略されます。 +.RE +.PP +\-processorpath \fIpath\fR +.RS 4 +注釈プロセッサを検索する場所を指定します。このオプションが使用されない場合、クラス・パスのプロセッサが検索されます。 +.RE +.PP +\-s \fIdir\fR +.RS 4 +生成されたソース・ファイルの格納先となるディレクトリを指定します。そのディレクトリは\fBjavac\fRでは作成されないため、すでに存在している必要があります。クラスがパッケージの一部である場合、コンパイラは、パッケージ名を反映したサブディレクトリ内にソース・ファイルを格納し、必要に応じてディレクトリを作成します。 +.sp +\fB\-s /home/mysrc\fRと指定し、クラスの名前が\fBcom\&.mypackage\&.MyClass\fRである場合、ソース・ファイルは\fB/home/mysrc/com/mypackage/MyClass\&.java\fRに格納されます。 +.RE +.PP +\-source \fIrelease\fR +.RS 4 +受け付けるソース・コードのバージョンを指定します。\fBrelease\fRには次の値を指定できます。 +.PP +1\&.3 +.RS 4 +このコンパイラでは、Java SE 1\&.3以降に導入されたアサーション、総称または他の言語機能をサポートしません。 +.RE +.PP +1\&.4 +.RS 4 +Java SE 1\&.4で導入された、アサーションを含むコードを受け付けます。 +.RE +.PP +1\&.5 +.RS 4 +Java SE 5で導入された総称および他の言語機能を含んだコードを受け付けます。 +.RE +.PP +5 +.RS 4 +1\&.5と同義です。 +.RE +.PP +1\&.6 +.RS 4 +Java SE 6では言語に対する変更は導入されませんでした。しかし、ソース・ファイル内のエンコーディング・エラーが、Java Platform, Standard Editionの以前のリリースような警告ではなく、エラーとして報告されるようになりました。 +.RE +.PP +6 +.RS 4 +1\&.6と同義です。 +.RE +.PP +1\&.7 +.RS 4 +Java SE 7で導入された機能を含むコードを受け付けます。 +.RE +.PP +7 +.RS 4 +1\&.7と同義です。 +.RE +.PP +1\&.8 +.RS 4 +これがデフォルト値です。Java SE 8で導入された機能を含むコードを受け付けます。 +.RE +.PP +8 +.RS 4 +1\&.8と同義です。 +.RE +.RE +.PP +\-sourcepath \fIsourcepath\fR +.RS 4 +クラスまたはインタフェースの定義を検索するソース・コード・パスを指定します。ユーザー・クラス・パスと同様に、ソース・パスのエントリは、Oracle Solarisではコロン(:)で、Windowsではセミコロンで区切り、ここには、ディレクトリ、JARアーカイブまたはZIPアーカイブを指定できます。パッケージを使用している場合は、ディレクトリまたはアーカイブ内のローカル・パス名がパッケージ名を反映している必要があります。 +.sp +\fB注意:\fR +ソース・ファイルも見つかった場合、クラス・パスにより見つかったクラスは再コンパイルされる可能性があります。型の検索を参照してください。 +.RE +.PP +\-verbose +.RS 4 +ロードされるクラスおよびコンパイルされるソース・ファイルごとの情報が出力される、詳細出力を使用します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-werror +.RS 4 +警告が発生した場合にコンパイルを終了します。 +.RE +.PP +\-X +.RS 4 +非標準オプションに関する情報を表示して終了します。 +.RE +.SS "クロスコンパイル・オプション" +.PP +デフォルトでは、クラスのコンパイルは、\fBjavac\fRが添付されているプラットフォームのブートストラップ・クラスおよび拡張機能クラスに対して行われます。ただし、\fBjavac\fRは、異なるJavaプラットフォームに実装されたブートストラップ・クラスおよび拡張機能クラスに対してコンパイルを行うクロスコンパイルもサポートしています。クロスコンパイルを行う場合は、\fB\-bootclasspath\fRおよび\fB\-extdirs\fRオプションを使用することが重要です。 +.PP +\-target \fIversion\fR +.RS 4 +仮想マシンの指定されたリリースを対象とするクラス・ファイルを生成します。クラス・ファイルは、指定されたターゲット以降のリリースでは動作しますが、それより前のリリースのJVMでは動作しません。有効なターゲットは、1\&.1、1\&.2、1\&.3、1\&.4、1\&.5 (5も可)、1\&.6 (6も可)、1\&.7 (7も可)および1\&.8 (8も可)です。 +.sp +\fB\-target\fRオプションのデフォルトは、\fB\-source\fRオプションの値によって異なります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが指定されていない場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.2の場合、\fB\-target\fRオプションの値は1\&.4です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.3の場合、\fB\-target\fRオプションの値は1\&.4です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.5の場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.6の場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションが1\&.7の場合、\fB\-target\fRオプションの値は1\&.8です。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-source\fRオプションの他のすべての値の場合、\fB\-target\fRオプションの値は、\fB\-source\fRオプションの値になります。 +.RE +.RE +.PP +\-bootclasspath \fIbootclasspath\fR +.RS 4 +指定された一連のブート・クラスに対してクロスコンパイルを行います。ユーザー・クラス・パスと同様に、ブート・クラス・パスのエントリはコロン(:)で区切り、ここには、ディレクトリ、JARアーカイブまたはZIPアーカイブを指定できます。 +.RE +.SS "コンパクト・プロファイル・オプション" +.PP +JDK 8以降から、\fBjavac\fRコンパイラはコンパクト・プロファイルをサポートします。コンパクト・プロファイルを使用すると、Javaプラットフォーム全体を必要としないアプリケーションは、デプロイ可能で、小さいフットプリントで実行できます。コンパクト・プロファイル機能は、アプリケーション・ストアからのアプリケーションのダウンロード時間を短縮するのに使用できます。この機能は、JREをバンドルするJavaアプリケーションの、よりコンパクトなデプロイメントに役立ちます。この機能は、小さいデバイスでも役立ちます。 +.PP +サポートされているプロファイル値は、\fBcompact1\fR、\fBcompact2\fRおよび\fBcompact3\fRです。これらは、追加のレイヤーです。大きい番号の各コンパクト・プロファイルには、小さい番号の名前のプロファイル内のすべてのAPIが含まれます。 +.PP +\-profile +.RS 4 +コンパクト・プロファイルを使用する場合、このオプションは、コンパイル時にプロファイル名を指定します。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-profile compact1 Hello\&.java\fR + +.fi +.if n \{\ +.RE +.\} +javacは、指定されたプロファイルにない任意のJava SE APIを使用するソース・コードをコンパイルしません。これは、そのようなソース・コードをコンパイルしようとすることによって生じるエラー・メッセージの例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd jdk1\&.8\&.0/bin\fR +\fB\&./javac \-profile compact1 Paint\&.java\fR +\fBPaint\&.java:5: error: Applet is not available in profile \*(Aqcompact1\*(Aq\fR +\fBimport java\&.applet\&.Applet;\fR + +.fi +.if n \{\ +.RE +.\} +この例では、\fBApplet\fRクラスを使用しないようにソースを変更することによって、エラーを修正できます。\-profileオプションを指定せずにコンパイルすることによって、エラーを修正することもできます。コンパイルは、Java SE APIの完全なセットに対して実行されます。(どのコンパクト・プロファイルにも、\fBApplet\fRクラスは含まれていません。) +.sp +コンパクト・プロファイルを使用してコンパイルするための別の方法として、\fB\-bootclasspath\fRオプションを使用して、プロファイルのイメージを指定する\fBrt\&.jar\fRファイルへのパスを指定します。かわりに\fB\-profile\fRオプションを使用すると、プロファイル・イメージは、コンパイル時にシステム上に存在する必要がありません。これは、クロスコンパイル時に役立ちます。 +.RE +.SS "非標準オプション" +.PP +\-Xbootclasspath/p:\fIpath\fR +.RS 4 +ブートストラップ・クラス・パスに接尾辞を追加します。 +.RE +.PP +\-Xbootclasspath/a:\fIpath\fR +.RS 4 +ブートストラップ・クラス・パスに接頭辞を追加します。 +.RE +.PP +\-Xbootclasspath/:\fIpath\fR +.RS 4 +ブートストラップ・クラス・ファイルの位置をオーバーライドします。 +.RE +.PP +\-Xdoclint:[\-]\fIgroup\fR [\fI/access\fR] +.RS 4 +\fIgroup\fRの値が\fBaccessibility\fR、\fBsyntax\fR、\fBreference\fR、\fBhtml\fRまたは\fBmissing\fRのいずれかである特定のチェック・グループを有効または無効にします。これらのチェック・グループの詳細は、\fBjavadoc\fRコマンドの\fB\-Xdoclint\fRオプションを参照してください。\fB\-Xdoclint\fRオプションは、\fBjavac\fRコマンドではデフォルトで無効になります。 +.sp +変数\fIaccess\fRは、\fB\-Xdoclint\fRオプションがチェックするクラスとメンバーの最小の可視性レベルを指定します。\fBpublic\fR、\fBprotected\fR、\fBpackage\fRおよび\fBprivate\fRの値(可視性の高い順)の1つを持つことができます。たとえば、次のオプションは、(protected、package、publicを含む) protected以上のアクセス・レベルを持つクラスおよびメンバーを(すべてのチェック・グループで)チェックします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xdoclint:all/protected\fR + +.fi +.if n \{\ +.RE +.\} +次のオプションは、package以上のアクセス権(packageおよびpublicを含む)を持つクラスおよびメンバーに対するHTMLエラーをチェックしないことを除き、すべてのアクセス・レベルに対してすべてのチェック・グループを有効にします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xdoclint:all,\-html/package\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-Xdoclint:none +.RS 4 +すべてのチェック・グループを無効にします。 +.RE +.PP +\-Xdoclint:all[\fI/access\fR] +.RS 4 +すべてのチェック・グループを有効にします。 +.RE +.PP +\-Xlint +.RS 4 +推奨されるすべての警告を有効にします。このリリースでは、利用可能なすべての警告を有効にすることをお薦めします。 +.RE +.PP +\-Xlint:all +.RS 4 +推奨されるすべての警告を有効にします。このリリースでは、利用可能なすべての警告を有効にすることをお薦めします。 +.RE +.PP +\-Xlint:none +.RS 4 +すべての警告を無効にします。 +.RE +.PP +\-Xlint:\fIname\fR +.RS 4 +警告名を無効にします。このオプションで無効にできる警告のリストは、\-Xlintオプションを使用した警告の有効化または無効化を参照してください。 +.RE +.PP +\-Xlint:\fI\-name\fR +.RS 4 +警告名を無効にします。このオプションで無効にできる警告のリストを取得するには、\-Xlintオプションを使用した警告の有効化または無効化\-Xlint\fBオプションを使用した\fRを参照してください。 +.RE +.PP +\-Xmaxerrs \fInumber\fR +.RS 4 +印刷するエラーの最大数を設定します。 +.RE +.PP +\-Xmaxwarns \fInumber\fR +.RS 4 +印刷する警告の最大数を設定します。 +.RE +.PP +\-Xstdout \fIfilename\fR +.RS 4 +コンパイラのメッセージを、指定されたファイルに送信します。デフォルトでは、コンパイラのメッセージは\fBSystem\&.err\fRに送られます。 +.RE +.PP +\-Xprefer:[\fInewer,source\fR] +.RS 4 +ある型に対してソース・ファイルとクラス・ファイルの両方が見つかった場合、そのどちらのファイルを読み取るかを指定します。(型の検索を参照してください)。\fB\-Xprefer:newer\fRオプションを使用した場合、ある型に対するソース・ファイルとクラス・ファイルのうち新しい方が読み取られます(デフォルト)。\fB\-Xprefer:source\fRオプションを使用した場合、ソース・ファイルが読み取られます。\fBSOURCE\fRの保存ポリシーを使用して宣言された注釈に任意の注釈プロセッサがアクセスできるようにする場合は、\fB\-Xprefer:source\fRを使用してください。 +.RE +.PP +\-Xpkginfo:[\fIalways\fR,\fIlegacy\fR,\fInonempty\fR] +.RS 4 +javacがpackage\-info\&.javaファイルから\fBpackage\-info\&.class\fRファイルを生成するかどうかを制御します。このオプションで使用可能なmode引数は次のとおりです。 +.PP +always +.RS 4 +すべての\fBpackage\-info\&.java\fRファイルの\fBpackage\-info\&.class\fRファイルを常に生成します。このオプションは、各\fB\&.java\fRファイルに対応する\fB\&.class\fRファイルがあることを確認するAntなどのビルド・システムを使用する場合に役立つことがあります。 +.RE +.PP +legacy +.RS 4 +package\-info\&.javaに注釈が含まれる場合にのみ\fBpackage\-info\&.class\fRファイルを生成します。package\-info\&.javaにコメントのみ含まれる場合に\fBpackage\-info\&.class\fRファイルを生成しません。 +.sp +\fB注意:\fR +\fBpackage\-info\&.class\fRファイルは生成できますが、package\-info\&.javaファイル内のすべての注釈に\fBRetentionPolicy\&.SOURCE\fRがある場合は空になります。 +.RE +.PP +nonempty +.RS 4 +package\-info\&.javaに\fBRetentionPolicy\&.CLASS\fRまたは\fBRetentionPolicy\&.RUNTIME\fRとともに注釈が含まれる場合にのみ\fBpackage\-info\&.class\fRファイルを生成します。 +.RE +.RE +.PP +\-Xprint +.RS 4 +デバッグ目的で指定した型のテキスト表示を出力します。注釈処理もコンパイルも実行されません。出力形式は変更される可能性があります。 +.RE +.PP +\-XprintProcessorInfo +.RS 4 +ある特定のプロセッサが処理を依頼されている注釈に関する情報を出力します。 +.RE +.PP +\-XprintRounds +.RS 4 +初回および後続の注釈処理ラウンドに関する情報を出力します。 +.RE +.SH "-XLINTオプションを使用した警告の有効化または無効化" +.PP +\fB\-Xlint:name\fRオプションを使用して警告\fIname\fRを有効にします。ここで、\fBname\fRは次の警告名のいずれかになります。\fB\-Xlint:\-name:\fRオプションを使用して、警告を無効化できます。 +.PP +cast +.RS 4 +不要で冗長なキャストについて警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBString s = (String) "Hello!"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +classfile +.RS 4 +クラス・ファイルの内容に関連した問題について警告します。 +.RE +.PP +deprecation +.RS 4 +非推奨の項目の使用について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\&.util\&.Date myDate = new java\&.util\&.Date();\fR +\fBint currentDay = myDate\&.getDay();\fR + +.fi +.if n \{\ +.RE +.\} +メソッド\fBjava\&.util\&.Date\&.getDay\fRはJDK 1\&.1以降は推奨されていません。 +.RE +.PP +dep\-ann +.RS 4 +\fB@deprecated\fR +Javadocコメントでドキュメント化されているが、\fB@Deprecated\fR注釈が付いていない項目について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @deprecated As of Java SE 7, replaced by {@link #newMethod()}\fR +\fB */\fR +\fBpublic static void deprecatedMethood() { }\fR +\fBpublic static void newMethod() { }\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +divzero +.RS 4 +定整数0で除算されることについて警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBint divideByZero = 42 / 0;\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +empty +.RS 4 +\fBif \fR文以降が空の文であることについて警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBclass E {\fR +\fB void m() {\fR +\fB if (true) ;\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +fallthrough +.RS 4 +fall\-throughケースのswitchブロックをチェックし、検出されたものに対して警告メッセージを表示します。Fall\-throughケースは、switchブロック内の最後のケースを除くケースです。このコードにはbreak文は含まれません。コードの実行をそのケースから次のケースへ移動します。たとえば、このswitchブロック内のcase 1ラベルに続くコードは、break文で終わっていません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBswitch (x) {\fR +\fBcase 1:\fR +\fB System\&.out\&.println("1");\fR +\fB // No break statement here\&.\fR +\fBcase 2:\fR +\fB System\&.out\&.println("2");\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +このコードのコンパイル時に\fB\-Xlint:fallthrough\fRオプションが使用されていた場合、コンパイラは、問題になっているケースの行番号とともに、caseにfall\-throughする可能性があることを示す警告を発行します。 +.RE +.PP +finally +.RS 4 +正常に完了できない\fBfinally\fR句について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static int m() {\fR +\fB try {\fR +\fB throw new NullPointerException();\fR +\fB } catch (NullPointerException(); {\fR +\fB System\&.err\&.println("Caught NullPointerException\&.");\fR +\fB return 1;\fR +\fB } finally {\fR +\fB return 0;\fR +\fB }\fR +\fB }\fR + +.fi +.if n \{\ +.RE +.\} +この例では、コンパイラは\fBfinally\fRブロックに関する警告を生成します。\fBint\fRメソッドが呼び出されると、値0が返されます。\fBfinally\fRブロックは、\fBtry\fRブロックが終了すると実行されます。この例では、制御が\fBcatch\fRブロックに移された場合、\fBint\fRメソッドは終了します。ただし、\fBfinally\fRブロックは実行される必要があるため、制御がメソッドの外部に移されていても、このブロックは実行されます。 +.RE +.PP +options +.RS 4 +コマンド行オプションの使用に関する問題について警告します。クロスコンパイル・オプションを参照してください。 +.RE +.PP +overrides +.RS 4 +メソッドのオーバーライドに関する問題について警告します。たとえば、次の2つのクラスがあるとします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class ClassWithVarargsMethod {\fR +\fB void varargsMethod(String\&.\&.\&. s) { }\fR +\fB}\fR + +\fBpublic class ClassWithOverridingMethod extends ClassWithVarargsMethod {\fR +\fB @Override\fR +\fB void varargsMethod(String[] s) { }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは、次のような警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [override] varargsMethod(String[]) in ClassWithOverridingMethod \fR +\fBoverrides varargsMethod(String\&.\&.\&.) in ClassWithVarargsMethod; overriding\fR +\fBmethod is missing \*(Aq\&.\&.\&.\*(Aq\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは、\fBvarargs\fRメソッドを検出すると、\fBvarargs\fRの仮パラメータを配列に変換します。メソッド\fBClassWithVarargsMethod\&.varargsMethod\fRでは、コンパイラは\fBvarargs\fRの仮パラメータ\fBString\&.\&.\&. s\fRを仮パラメータ\fBString[] s\fRに変換します。これは、メソッド\fBClassWithOverridingMethod\&.varargsMethod\fRの仮パラメータに対応する配列です。その結果、この例ではコンパイルが行われます。 +.RE +.PP +path +.RS 4 +コマンドラインでの無効なパス要素と存在しないパス・ディレクトリについて警告します(クラス・パス、ソース・パスなどのパス関連)。このような警告を\fB@SuppressWarnings\fR注釈で抑制することはできません。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-Xlint:path \-classpath /nonexistentpath Example\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +processing +.RS 4 +注釈処理に関する問題について警告します。コンパイラがこの警告を生成するのは、注釈を含むクラスがあるときに、使用している注釈プロセッサでそのタイプの例外を処理できない場合です。たとえば、単純な注釈プロセッサを次に示します。 +.sp +\fBソース・ファイルAnnocProc\&.java\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.util\&.*;\fR +\fBimport javax\&.annotation\&.processing\&.*;\fR +\fBimport javax\&.lang\&.model\&.*;\fR +\fBimport\&.javaz\&.lang\&.model\&.element\&.*;\fR + +\fB@SupportedAnnotationTypes("NotAnno")\fR +\fBpublic class AnnoProc extends AbstractProcessor {\fR +\fB public boolean process(Set<? extends TypeElement> elems, RoundEnvironment renv){\fR +\fB return true;\fR +\fB }\fR + +\fB public SourceVersion getSupportedSourceVersion() {\fR +\fB return SourceVersion\&.latest();\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +\fBソース・ファイルAnnosWithoutProcessors\&.java\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB@interface Anno { }\fR +\fB \fR +\fB@Anno\fR +\fBclass AnnosWithoutProcessors { }\fR + +.fi +.if n \{\ +.RE +.\} +次のコマンドは、注釈プロセッサ\fBAnnoProc\fRをコンパイルし、この注釈プロセッサをソース・ファイル\fBAnnosWithoutProcessors\&.java\fRに対して実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac AnnoProc\&.java\fR +\fBjavac \-cp \&. \-Xlint:processing \-processor AnnoProc \-proc:only AnnosWithoutProcessors\&.java\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラがソース・ファイル\fBAnnosWithoutProcessors\&.java\fRに対して注釈プロセッサを実行すると、次の警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [processing] No processor claimed any of these annotations: Anno\fR +\fB \fR +.fi +.if n \{\ +.RE +.\} +この問題を解決するために、クラス\fBAnnosWithoutProcessors\fRで定義および使用される注釈の名前を、\fBAnno\fRから\fBNotAnno\fRに変更できます。 +.RE +.PP +rawtypes +.RS 4 +raw型に対する未検査操作について警告します。次の文では、\fBrawtypes\fR警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBvoid countElements(List l) { \&.\&.\&. }\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、\fBrawtypes\fR警告は生成されません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBvoid countElements(List<?> l) { \&.\&.\&. }\fR + +.fi +.if n \{\ +.RE +.\} +\fBList\fRはraw型です。ただし、\fBList<?>\fRは、アンバウンド形式のワイルドカードのパラメータ化された型です。\fBList\fRはパラメータ化されたインタフェースであるため、常にその型引数を指定します。この例では、\fBList\fRの仮引数はアンバウンド形式のワイルドカード(\fB?\fR)を使用してその仮型パラメータとして指定されます。つまり、\fBcountElements\fRメソッドは\fBList\fRインタフェースのどのインスタンス化も受け付けることができます。 +.RE +.PP +Serial +.RS 4 +直列化可能クラスに\fBserialVersionUID\fR定義がないことを警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class PersistentTime implements Serializable\fR +\fB{\fR +\fB private Date time;\fR +\fB \fR +\fB public PersistentTime() {\fR +\fB time = Calendar\&.getInstance()\&.getTime();\fR +\fB }\fR +\fB \fR +\fB public Date getTime() {\fR +\fB return time;\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは次の警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [serial] serializable class PersistentTime has no definition of\fR +\fBserialVersionUID\fR + +.fi +.if n \{\ +.RE +.\} +直列化可能クラスが\fBserialVersionUID\fRという名前のフィールドを明示的に宣言しない場合、直列化ランタイム環境では、「Javaオブジェクト直列化仕様」で説明されているように、クラスの様々な側面に基づいて、クラスの\fBserialVersionUID\fRのデフォルト値を計算します。ただし、すべての直列化可能クラスが\fBserialVersionUID\fR値を明示的に宣言することを強くお薦めします。 これは、\fBserialVersionUID\fR値を計算するデフォルトのプロセスが、コンパイラの実装によって異なる可能性のあるクラスの詳細にきわめて影響を受けやすく、その結果、直列化復元中に予期しない\fBInvalidClassExceptions\fRが発生する可能性があるためです。Javaコンパイラの実装が異なっても\fBserialVersionUID\fR値の一貫性を確保にするには、直列化可能クラスが\fBserialVersionUID\fR値を明示的に宣言する必要があります。 +.RE +.PP +static +.RS 4 +staticの使用に関する問題について警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBclass XLintStatic {\fR +\fB static void m1() { }\fR +\fB void m2() { this\&.m1(); }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは次の警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [static] static method should be qualified by type name, \fR +\fBXLintStatic, instead of by an expression\fR + +.fi +.if n \{\ +.RE +.\} +この問題を解決するために、次のように\fBstatic\fRメソッド\fBm1\fRを呼び出すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBXLintStatic\&.m1();\fR + +.fi +.if n \{\ +.RE +.\} +あるいは、\fBstatic\fRキーワードをメソッド\fBm1\fRの宣言から削除することもできます。 +.RE +.PP +try +.RS 4 +try\-with\-resources文を含む、\fBtry\fRブロックの使用に関する問題について警告します。たとえば、\fBtry\fRブロックで宣言されたリソース\fBac\fRが使用されないために、次の文に対して警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtry ( AutoCloseable ac = getResource() ) { // do nothing}\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +unchecked +.RS 4 +Java言語仕様で指定されている未検査変換警告の詳細を示します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBList l = new ArrayList<Number>();\fR +\fBList<String> ls = l; // unchecked warning\fR + +.fi +.if n \{\ +.RE +.\} +型の削除中、型\fBArrayList<Number>\fRおよび\fBList<String>\fRは、それぞれ\fBArrayList\fRおよび\fBList\fRになります。 +.sp +\fBls\fRコマンドには、パラメータ化された型\fBList<String>\fRが指定されています。\fBl\fRによって参照される\fBList\fRが\fBls\fRに割り当てられた場合、コンパイラは未検査警告を生成します。コンパイル時に、コンパイラおよびJVMは、\fBl\fRが\fBList<String>\fR型を参照するかどうかを判別できません。この場合、\fBl\fRは、\fBList<String>\fR型を参照しません。その結果、ヒープ汚染が発生します。 +.sp +ヒープ汚染状態が発生するのは、\fBList\fRオブジェクト\fBl\fR +(そのstatic型は\fBList<Number>\fR)が別の\fBList\fRオブジェクト\fBls\fR +(異なるstatic型\fBList<String>\fRを持つ)に代入される場合です。しかし、コンパイラではこの代入をいまだに許可しています。総称をサポートしないJava SEのリリースとの後方互換性を確保するために、この代入を許可する必要があります。型の削除のため、\fBList<Number>\fRおよび\fBList<String>\fRは、両方\fBList\fRになります。その結果、コンパイラはオブジェクト\fBl\fR +(\fBList\fRというraw型を持つ)をオブジェクト\fBls\fRに代入することを許可します。 +.RE +.PP +varargs +.RS 4 +可変引数(\fBvarargs\fR)メソッド、特に非具象化可能引数を含むものの使用が安全でないことを警告します。たとえば、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class ArrayBuilder {\fR +\fB public static <T> void addToList (List<T> listArg, T\&.\&.\&. elements) {\fR +\fB for (T x : elements) {\fR +\fB listArg\&.add(x);\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +\fB注意:\fR +非具象化可能型は、型情報が実行時に完全に使用不可能な型です。 +.sp +コンパイラは、メソッド\fBArrayBuilder\&.addToList\fRの定義に関する次の警告を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwarning: [varargs] Possible heap pollution from parameterized vararg type T\fR + +.fi +.if n \{\ +.RE +.\} +コンパイラは、varargsメソッドを検出すると、\fBvarargs\fRの仮パラメータを配列に変換します。しかし、Javaプログラミング言語では、パラメータ化された型の配列の作成を許可していません。メソッド\fBArrayBuilder\&.addToList\fRでは、コンパイラは\fBvarargs\fRの仮パラメータ\fBT\&.\&.\&.\fR要素を仮パラメータ\fBT[]\fR要素(配列)に変換します。しかし、型消去により、コンパイラは\fBvarargs\fRの仮パラメータを\fBObject[]\fR要素に変換します。その結果、ヒープ汚染が発生する可能性があります。 +.RE +.SH "コマンド行引数ファイル" +.PP +\fBjavac\fRコマンドを短くしたり簡潔にしたりするために、\fBjavac\fRコマンドに対する引数(\fB\-J\fRオプションを除く)を含む1つ以上のファイルを指定することができます。これにより、どのオペレーティング・システム上でも、任意の長さの\fBjavac\fRコマンドを作成できます。 +.PP +引数ファイルには、\fBjavac\fRのオプションとソース・ファイル名を自由に組み合せて記述できます。ファイル内の引数は、空白または改行文字で区切ることができます。ファイル名に埋め込まれた空白がある場合、ファイル名全体を二重引用符で囲みます。 +.PP +引数ファイル内のファイル名は、引数ファイルの位置ではなく、現在のディレクトリに相対的となります。これらのリストでは、ワイルドカード(*)は使用できません(たとえば、\fB*\&.java\fRとは指定できません)。アットマーク(@)を使用したファイルの再帰的な解釈はサポートされていません。また、\fB\-J\fRオプションもサポートされていません。このオプションは起動ツールに渡されますが、起動ツールでは引数ファイルをサポートしていないからです。 +.PP +\fBjavac\fRコマンドを実行するときに、各引数ファイルのパスと名前の先頭にアットマーク(@)文字を付けて渡します。\fBjavac\fRコマンドは、アットマーク(@)で始まる引数を見つけると、そのファイルの内容を展開して引数リストに挿入します。 +.PP +\fB例 1 \fR単一の引数ファイル +.RS 4 +\fBargfile\fRという名前の単一の引数ファイルを使用して、すべての\fBjavac\fR引数を格納する場合は、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac @argfile\fR + +.fi +.if n \{\ +.RE +.\} +この引数ファイルには、例2で示されている両方のファイルの内容を入れることができます。 +.RE +.PP +\fB例 2 \fR2つの引数ファイル +.RS 4 +\fBjavac\fRオプション用とソース・ファイル名用に、2つの引数ファイルを作成できます。次のリストには、行の継続文字はありません。 +.sp +次を含むoptionsという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-d classes\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-g\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-sourcepath /java/pubs/ws/1\&.3/src/share/classes\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf + +.fi +.if n \{\ +.RE +.\} +次を含むclassesという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBMyClass1\&.java\fR +\fBMyClass2\&.java\fR +\fBMyClass3\&.java\fR + +.fi +.if n \{\ +.RE +.\} +それから、次のように\fBjavac\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac @options @classes\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRパスを使用した引数ファイル +.RS 4 +引数ファイルはパスを指定できますが、ファイル内のすべてのファイル名は、(\fBpath1\fRや\fBpath2\fRではなく)次のように現在の作業ディレクトリに相対的となります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac @path1/options @path2/classes\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "注釈処理" +.PP +\fBjavac\fRコマンドが注釈処理を直接サポートしているため、独立した注釈処理コマンドである\fBapt\fRを使用する必要がなくなりました。 +.PP +注釈プロセッサのAPIは、\fBjavax\&.annotation\&.processing\fRおよび\fBjavax\&.lang\&.model\fRパッケージとそのサブパッケージ内に定義されています。 +.SS "注釈処理を行う方法" +.PP +\fB\-proc:none\fRオプションによって注釈処理が無効化されない限り、コンパイラは使用可能なすべての注釈プロセッサを検索します。検索パスは、\fB\-processorpath\fRオプションを使用して指定できます。パスを指定しない場合、ユーザー・クラス・パスが使用されます。プロセッサの検索は、検索パス上の\fBMETA\-INF/services/javax\&.annotation\&.processing\fR\&.Processorという名前のサービス・プロバイダ構成ファイルに基づいて行われます。このようなファイルには、使用するすべての注釈プロセッサの名前を、1行に1つずつ含めてください。また、別の方法として、\fB\-processor\fRオプションを使用してプロセッサを明示的に指定することもできます。 +.PP +コンパイラは、コマンドラインのソース・ファイルやクラスを走査することで、どのような注釈が存在しているかを確認し終わると、プロセッサに対して問合せを行い、それらのプロセッサがどの注釈を処理できるのかを確認します。一致するものが見つかった場合、そのプロセッサが呼び出されます。各プロセッサは、自身が処理する注釈を要求できます。その場合、それらの注釈に対する別のプロセッサを見つける試みは行われません。すべての注釈が要求されると、コンパイラはそれ以上プロセッサの検索を行いません。 +.PP +いずれかのプロセッサによって新しいソース・ファイルが生成されると、注釈処理の2回目のラウンドが開始されます。新しく生成されたすべてのソース・ファイルがスキャンされ、前回と同様に注釈が処理されます。以前のラウンドで呼び出されたプロセッサはすべて、後続のどのラウンドでも呼び出されます。これが、新しいソース・ファイルが生成されなくなるまで続きます。 +.PP +あるラウンドで新しいソース・ファイルが生成されなかった場合、注釈プロセッサがあと1回のみ呼び出され、残りの処理を実行する機会が与えられます。最後に、\fB\-proc:only\fRオプションが使用されないかぎり、コンパイラは、元のソース・ファイルと生成されたすべてのソース・ファイルをコンパイルします。 +.SS "暗黙的にロードされたソース・ファイル" +.PP +コンパイラは、一連のソース・ファイルをコンパイルする際に、別のソース・ファイルを暗黙的にロードすることが必要な場合があります。型の検索を参照してください。そのようなファイルは、現時点では注釈処理の対象になりません。デフォルトでは、注釈処理が実行され、かつ暗黙的にロードされた任意のソース・ファイルがコンパイルされた場合、コンパイラは警告を発行します。\fB\-implicit\fRオプションでは、警告を抑制する方法が提供されます。 +.SH "型の検索" +.PP +ソース・ファイルをコンパイルするために、コンパイラは通常、型に関する情報を必要としますが、その型の定義はコマンド行で指定したソース・ファイルにありません。コンパイラは、ソース・ファイルで使用されているクラスまたはインタフェース、拡張されているクラスまたはインタフェース、あるいは実装されているクラスまたはインタフェースすべてについて、型の情報を必要とします。これには、ソース・ファイルで明示的には言及されていなくても、継承を通じて情報を提供するクラスとインタフェースも含まれます。 +.PP +たとえば、サブクラス\fBjava\&.applet\&.Applet\fRを作成すると、\fBアプレット\fRの祖先のクラス(\fBjava\&.awt\&.Panel\fR、\fBjava\&.awt\&.Container\fR、\fBjava\&.awt\&.Component\fRおよび\fBjava\&.lang\&.Object\fR)を使用していることにもなります。 +.PP +コンパイラは、型の情報が必要になると、その型を定義しているソース・ファイルまたはクラス・ファイルを検索します。まず、ブートストラップ・クラスと拡張機能クラスを検索し、続いてユーザー・クラス・パス(デフォルトでは現在のディレクトリ)を検索します。ユーザー・クラス・パスは、\fBCLASSPATH\fR環境変数を設定して定義するか、または\fB\-classpath\fRオプションを使用して定義します。 +.PP +\fB\-sourcepath\fRオプションが設定されている場合、コンパイラは、指定されたパスからソース・ファイルを検索します。それ以外の場合、コンパイラは、ユーザー・クラス・パスからクラス・ファイルとソース・ファイルの両方を検索します。 +.PP +\fB\-bootclasspath\fRオプションおよび\fB\-extdirs\fRオプションを使用して、別のブートストラップ・クラスや拡張機能クラスを指定できます。クロスコンパイル・オプションを参照してください。 +.PP +型の検索に成功したときに得られる結果は、クラス・ファイル、ソース・ファイル、またはその両方である場合があります。両方が見つかった場合、そのどちらを使用するかを\fB\-Xprefer\fRオプションでコンパイラに指示できます。\fBnewer\fRが指定された場合、コンパイラは2つのファイルのうち新しい方を使用します。\fBsource\fRが指定された場合、コンパイラはソース・ファイルを使用します。デフォルトは\fBnewer\fRです。 +.PP +型の検索自体によって、または\fB\-Xprefer\fRオプションが設定された結果として必要な型のソース・ファイルが見つかった場合、コンパイラはそのソース・ファイルを読み取り、必要な情報を取得します。デフォルトでは、コンパイラはソース・ファイルのコンパイルも行います。\fB\-implicit\fRオプションを使用してその動作を指定できます。\fBnone\fRが指定された場合、ソース・ファイルに対してクラス・ファイルは生成されません。\fBclass\fRが指定された場合、ソース・ファイルに対してクラス・ファイルが生成されます。 +.PP +コンパイラは、注釈処理が完了するまで、ある型情報の必要性を認識しない場合があります。型情報がソース・ファイル内に見つかり、かつ\fB\-implicit\fRオプションが指定されていない場合、コンパイラによって、そのファイルが注釈処理の対象とならずにコンパイルされることが警告されます。この警告を無効にするには、(そのファイルが注釈処理の対象となるように)そのファイルをコマンド行に指定するか、あるいはそのようなソース・ファイルに対してクラス・ファイルを生成する必要があるかどうかを\fB\-implicit\fRオプションを使用して指定します。 +.SH "プログラマティック・インタフェース" +.PP +\fBjavac\fRコマンドは、\fBjavax\&.tools\fRパッケージ内のクラスとインタフェースによって定義される新しいJava Compiler APIをサポートします。 +.SS "例" +.PP +コマンドライン引数を指定するようにコンパイルするには、次の構文を使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBJavaCompiler javac = ToolProvider\&.getSystemJavaCompiler();\fR + +.fi +.if n \{\ +.RE +.\} +.PP +例では、診断を標準出力ストリームに書き込み、コマンド行からの呼出し時に\fBjavac\fRが指定する終了コードを返します。 +.PP +\fBjavax\&.tools\&.JavaCompiler\fRインタフェースの他のメソッドを使用すると、診断の処理やファイルの読取り元/書込み先の制御などを行うことができます。 +.SS "旧式のインタフェース" +.PP +\fB注意:\fR +このAPIは、後方互換性のためにのみ保持されています。すべての新しいコードは、新しいJava Compiler APIを使用する必要があります。 +.PP +次のように、\fBcom\&.sun\&.tools\&.javac\&.Main\fRクラスには、プログラムからコンパイラを呼び出すためのstaticメソッドが2つ用意されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static int compile(String[] args);\fR +\fBpublic static int compile(String[] args, PrintWriter out);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBargs\fRパラメータは、通常コンパイラに渡される任意のコマンド行引数を表しています。 +.PP +\fBout\fRパラメータは、コンパイラの診断出力の宛先を示します。 +.PP +\fBreturn\fR値は、\fBjavac\fRの\fBexit\fR値と同じです。 +.PP +\fB注意:\fR +名前が\fBcom\&.sun\&.tools\&.javac\fRで始まるパッケージ(\fBcom\&.sun\&.tools\&.javac\fRのサブパッケージ)で検出される他のすべてのクラスおよびメソッドは、完全に内部用であり、いつでも変更される可能性があります。 +.SH "例" +.PP +\fB例 1 \fR簡単なプログラムのコンパイル +.RS 4 +この例では、greetingsディレクトリで\fBHello\&.java\fRソース・ファイルをコンパイルする方法を示しています。\fBHello\&.java\fRで定義されたクラスは、\fBgreetings\&.Hello\fRと呼ばれます。greetingsディレクトリは、ソース・ファイルとクラス・ファイルの両方があるパッケージ・ディレクトリで、現在のディレクトリのすぐ下にあります。これにより、デフォルトのユーザー・クラス・パスを使用できるようになります。また、\fB\-d\fRオプションを使用して別の出力先ディレクトリを指定する必要もありません。 +.sp +\fBHello\&.java\fR内のソース・コードは次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpackage greetings;\fR +\fB \fR +\fBpublic class Hello {\fR +\fB public static void main(String[] args) {\fR +\fB for (int i=0; i < args\&.length; i++) {\fR +\fB System\&.out\&.println("Hello " + args[i]);\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +greetings\&.Helloのコンパイル: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac greetings/Hello\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\&.Hello\fRの実行: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava greetings\&.Hello World Universe Everyone\fR +\fBHello World\fR +\fBHello Universe\fR +\fBHello Everyone\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fR複数のソース・ファイルのコンパイル +.RS 4 +この例では、\fBgreetings\fRパッケージのソース・ファイル\fBAloha\&.java\fR、\fBGutenTag\&.java\fR、\fBHello\&.java\fRおよび\fBHi\&.java\fRをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% javac greetings/*\&.java\fR +\fB% ls greetings\fR +\fBAloha\&.class GutenTag\&.class Hello\&.class Hi\&.class\fR +\fBAloha\&.java GutenTag\&.java Hello\&.java Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRユーザー・クラス・パスの指定 +.RS 4 +前述の例のソース・ファイルのうち1つを変更した後に、そのファイルを再コンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpwd\fR +\fB/examples\fR +\fBjavac greetings/Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\&.Hi\fRは\fBgreetings\fRパッケージ内の他のクラスを参照しているため、コンパイラはこれらの他のクラスを探す必要があります。デフォルトのユーザー・クラス・パスはパッケージ・ディレクトリを含むディレクトリであるため、前述の例は動作します。現在のディレクトリを気にせずにこのファイルを再コンパイルする場合、\fBCLASSPATH\fRを設定して、ユーザー・クラス・パスに例のディレクトリを追加します。この例では、\fB\-classpath\fRオプションを使用しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-classpath /examples /examples/greetings/Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\&.Hi\fRを変更してバナー・ユーティリティを使用するようにした場合、 そのユーティリティもユーザー・クラス・パスを通じてアクセスできるようになっている必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-classpath /examples:/lib/Banners\&.jar \e\fR +\fB /examples/greetings/Hi\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fBgreetings\fRパッケージでクラスを実行するには、プログラムは\fBgreetings\fRパッケージ、および\fBgreetings\fRクラスが使用するクラスにアクセスする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-classpath /examples:/lib/Banners\&.jar greetings\&.Hi\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fRソース・ファイルとクラス・ファイルの分離 +.RS 4 +次の例では、\fBjavac\fRを使用して、JVM 1\&.7上で実行するコードをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 \-target 1\&.7 \-bootclasspath jdk1\&.7\&.0/lib/rt\&.jar \e \fR +\fB\-extdirs "" OldCode\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-source 1\&.7\fRオプションにより、\fBOldCode\&.java\fRのコンパイルにはリリース1\&.7(または7)のJavaプログラミング言語が使用されます。\fB\-target 1\&.7\fRオプションにより、JVM 1\&.7と互換性のあるクラス・ファイルが生成されます。ほとんどの場合、\fB\-target\fRオプションの値は\fB\-source\fRオプションの値になります。この例では、\fB\-target\fRオプションを省略できます。 +.sp +\fB\-bootclasspath\fRオプションを使用して、適切なバージョンのブートストラップ・クラス(\fBrt\&.jar\fRライブラリ)を指定する必要があります。指定しない場合は、コンパイラによって次の警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 OldCode\&.java\fR +\fBwarning: [options] bootstrap class path not set in conjunction with \fR +\fB\-source 1\&.7\fR + +.fi +.if n \{\ +.RE +.\} +適切なバージョンのブートストラップ・クラスを指定しない場合、コンパイラは古い言語仕様(この例では、バージョン1\&.7のJavaプログラミング言語)を新しいブートストラップ・クラスと組み合せて使用します。その結果、存在しないメソッドへの参照が含まれていることがあるため、クラス・ファイルが古いプラットフォーム(この場合はJava SE 7)で動作しない可能性があります。 +.RE +.PP +\fB例 5 \fRクロス・コンパイル +.RS 4 +この例では、\fBjavac\fRを使用して、JVM 1\&.7上で実行するコードをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 \-target 1\&.7 \-bootclasspath jdk1\&.7\&.0/lib/rt\&.jar \e\fR +\fB \-extdirs "" OldCode\&.java\fR + +.fi +.if n \{\ +.RE +.\} +\fB \-source 1\&.7\fRオプションにより、OldCode\&.javaのコンパイルにはリリース1\&.7(または7)のJavaプログラミング言語が使用されます。\fB\-target 1\&.7\fRオプションにより、JVM 1\&.7と互換性のあるクラス・ファイルが生成されます。 +.sp +\fB\-bootclasspath\fRオプションを使用して、適切なバージョンのブートストラップ・クラス(\fBrt\&.jar\fRライブラリ)を指定する必要があります。指定しない場合は、コンパイラによって次の警告が生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavac \-source 1\&.7 OldCode\&.java\fR +\fBwarning: [options] bootstrap class path not set in conjunction with \-source 1\&.7\fR + +.fi +.if n \{\ +.RE +.\} +適切なバージョンのブートストラップ・クラスを指定しない場合、コンパイラは古い言語仕様を新しいブートストラップ・クラスと組み合せて使用します。この組合せは、存在しないメソッドへの参照が含まれていることがあるため、クラス・ファイルが古いプラットフォーム(この場合はJava SE 7)で動作しない可能性があります。この例では、コンパイラはJavaプログラミング言語のリリース1\&.7を使用します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javadoc.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javadoc.1 new file mode 100755 index 0000000..4a1edd5 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javadoc.1 @@ -0,0 +1,4657 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javadoc +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javadoc" "1" "2015å¹´3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javadoc \- Javaソース・ファイルから、APIドキュメントのHTMLページを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc\fR {\fIpackages\fR|\fIsource\-files\fR} [\fIoptions\fR] [\fI@argfiles\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIpackages\fR +.RS 4 +\fBjava\&.lang java\&.lang\&.reflect java\&.awt\fRなど、空白で区切ってドキュメント化するパッケージの名前。サブパッケージもドキュメント化する場合は、\fB\-subpackages\fRオプションを使用してパッケージを指定します。 +.sp +デフォルトでは、\fBjavadoc\fRは、現在のディレクトリおよびサブディレクトリで指定されたパッケージを探します。\fB\-sourcepath\fRオプションを使用して、パッケージを探すディレクトリのリストを指定します。 +.RE +.PP +\fIsource\-files\fR +.RS 4 +\fBClass\&.java Object\&.java Button\&.java\fRのように空白で区切った、ドキュメント化するJavaソース・ファイルの名前。デフォルトでは、\fBjavadoc\fRは、現在のディレクトリで指定されたクラスを探します。ただし、\fB/home/src/java/awt/Graphics*\&.java\fRのように、クラス・ファイルのフルパスを指定し、ワイルドカード文字を使用できます。現在のディレクトリからの相対パスも指定できます。 +.RE +.PP +\fIoptions\fR +.RS 4 +空白で区切られたコマンド行オプション。オプションを参照してください。 +.RE +.PP +\fI@argfiles\fR +.RS 4 +\fBjavadoc\fRコマンド・オプション、パッケージ名およびソース・ファイル名のリストを任意の順序で含むファイルの名前。 +.RE +.SH "説明" +.PP +\fBjavadoc\fRコマンドは、一連のJavaソース・ファイルにある宣言およびドキュメンテーション・コメントを解析し、デフォルトでは、publicクラス、protectedクラス、ネストされたクラス(匿名の内部クラスは除く)、インタフェース、コンストラクタ、メソッド、およびフィールドについて記述した一連のHTMLページを生成します。\fBjavadoc\fRコマンドは、APIドキュメントの生成や、一連のソース・ファイルの実装ドキュメントの生成に使用できます。 +.PP +\fBjavadoc\fRコマンドは、パッケージ全体、個々のソース・ファイル、またはその両方に対して実行できます。パッケージ全体のドキュメント化を行うには、\fB\-subpackages\fRオプションを使用してディレクトリおよびそのサブディレクトリを再帰的にたどるか、パッケージ名の明示的なリストを渡します。個々のソース・ファイルをドキュメント化するには、Javaソース・ファイル名のリストを渡します。簡単な例を参照してください。 +.SS "ソース・ファイルの処理" +.PP +\fBjavadoc\fRコマンドは、ソースで終わるファイル、およびソース・ファイルで説明しているその他のファイルを処理します。個々のソース・ファイル名を渡して\fBjavadoc\fRを実行する場合、どのソース・ファイルを処理するかを正確に指定できます。ただし、多くの開発者はこの方法では作業しません。パッケージ名を渡すほうが簡単だからです。ソース・ファイル名を明示的に指定しなくても、\fBjavadoc\fRコマンドは3つの方法で実行できます。パッケージ名を渡し、\fB\-subpackages\fRオプションを使用するか、またはソース・ファイル名にワイルドカードを使用することができます。これらの場合、\fBjavadoc\fRコマンドがソース・ファイルの処理を行うのは、そのファイルが次のすべての要件を満たす場合のみです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ファイル名の接頭辞(\fB\&.java\fRを削除)が有効なクラス名である。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ソース・ツリーのルートからの相対的なパス名が、区切り文字をドットに変換すると、有効なパッケージ名になる。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ文に有効なパッケージ名が含まれている。 +.RE +.PP +リンクの処理 +.PP +処理の実行中に、\fBjavadoc\fRコマンドは、その実行でドキュメント化されるパッケージ、クラス、およびメンバーの名前に対して、相互参照リンクを追加します。リンクは、次の場所に表示されます。@タグの説明については、javadocタグを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +宣言(戻り値の型、引数の型、フィールドの型)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB@see\fRタグから生成された\fI「関連項目」\fRセクション。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB{@link}\fRタグから生成されたインライン・テキスト。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB@throws\fRタグから生成された例外の名前。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +インタフェースのメンバーに対する\fI「定義」\fRリンクと、クラスのメンバーに対する\fI「オーバーライド」\fRリンク。メソッド・コメントの継承を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ、クラス、およびメンバーをリストしているサマリー表。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージおよびクラスの継承ツリー。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +索引。 +.RE +.PP +コマンド行で指定しなかったクラスについての既存のテキスト(別に生成したテキスト)に対してリンクを追加するには、\fB\-link\fRおよび\fB\-linkoffline\fRオプションを利用できます。 +.PP +処理の詳細 +.PP +\fBjavadoc\fRコマンドは実行するたびに1つの完全なドキュメントを生成します。前の実行の結果を変更または直接取り込む、増分ビルドを行いません。ただし、\fBjavadoc\fRコマンドは、他の実行の結果にリンクできます。 +.PP +\fBjavadoc\fRコマンドの実装にはJavaコンパイラが必要で、Javaコンパイラに依存しています。\fBjavadoc\fRコマンドは\fBjavac\fRコマンドの一部を呼び出し、宣言をコンパイルして、メンバーの実装を無視します。\fBjavadoc\fRコマンドは、クラス階層を含むクラスの豊富な内部表現とクラスの「使用」関係を構築し、HTMLを生成します。さらに、J\fBjavadoc\fRコマンドは、ソース・コードのドキュメンテーション・コメントから、ユーザーの提供したドキュメントも取得します。ドキュメンテーション・コメントを参照してください。 +.PP +\fBjavadoc\fRコマンドは、メソッド本体を持たない純粋なスタブ・ファイルであるソース・ファイルに対して実行できます。したがって、APIの実装前の設計の早い段階で、ドキュメンテーション・コメントを記述して\fBjavadoc\fRコメントを実行できます。 +.PP +コンパイラに依存することによって、HTML出力は、実際の実装に正確に対応します。実際の実装は、明示的なソース・コードにではなく、暗黙のソース・コードに依存する場合があります。たとえば、\fBjavadoc\fRコマンドは、コンパイル済クラス・ファイルには存在するがソース・コードには存在しないデフォルト・コンストラクタをドキュメント化します。 +.PP +多くの場合、\fBjavadoc\fRコマンドでは、ソース・ファイルのコードが不完全またはエラーを含んでいる場合でもドキュメントを生成できます。すべてのデバッグやトラブルシューティングを完了する前にドキュメントを生成できます。\fBjavadoc\fRコマンドはドキュメンテーション・コメントの基本的なチェックを行います。 +.PP +\fBjavadoc\fRコマンドは、ドキュメントの内部構造を構築する際、参照クラスをすべてロードします。このため、 +\fBjavadoc\fRコマンドは、ブートストラップ・クラス、拡張機能、またはユーザー・クラスにかかわらず、すべての参照クラスを検索できる必要があります。クラスの検出方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html)を参照してください +.PP +通常、作成するクラスは、拡張クラスとして、または\fBjavadoc\fRコマンドのクラス・パスでロードされる必要があります。 +.SS "Javadocのドックレット" +.PP +\fBjavadoc\fRコマンドの出力の内容と形式は、ドックレットを使用してカスタマイズできます。\fBjavadoc\fRコマンドには、標準ドックレットと呼ばれるデフォルトの組込みドックレットがあります。標準ドックレットは、HTML形式のAPIドキュメントを生成します。標準ドックレットを修正またはサブクラスを作成することや、HTML、XML、MIF、RTFなどの好みの出力形式を生成する独自のドックレットを記述することも可能です。 +.PP +\fB\-doclet\fRオプションでカスタム・ドックレットが指定されていない場合、\fBjavadoc\fRコマンドは、デフォルトの標準ドックレットを使用します。\fBjavadoc\fRコマンドには、使用されているドックレットに関係なく使用できるいくつかのオプションがあります。標準ドックレットでは、これらの他に、いくつかのコマンド行オプションが追加されます。オプションを参照してください。 +.SH "ソース・ファイル" +.PP +\fBjavadoc\fRコマンドは、次のタイプのソース・ファイルから出力を生成します。そのファイルは、クラスのJava言語ソース・ファイル(\fB\&.java\fR)、パッケージ・コメント・ファイル、概要コメント・ファイル、およびその他の未処理のファイルです。ここでは、ドキュメント化しないがソース・ツリーに存在する場合があるテスト・ファイルやテンプレート・ファイルについても説明します。 +.SS "クラスのソース・ファイル" +.PP +それぞれのクラスまたはインタフェース、およびそのメンバーは、独自のドキュメンテーション・コメントを持つことができ、それをソース・ファイル内に保持します。ドキュメンテーション・コメントを参照してください。 +.SS "パッケージ・コメント・ファイル" +.PP +それぞれのパッケージは、独自のドキュメンテーション・コメントを持つことができ、それを専用のソース・ファイルに保持します。その内容は、\fBjavadoc\fRコマンドによって生成されるパッケージのサマリー・ページに組み込まれます。このコメントには、通常、そのパッケージ全体に当てはまるドキュメントを記述します。 +.PP +パッケージ・コメント・ファイルを作成するには、次のいずれかのファイルにコメントを格納できます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackage\-info\&.java\fRファイルには、パッケージ宣言、パッケージ注釈、パッケージ・コメント、およびJavadocタグを格納できます。このファイルが優先されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackage\&.html\fRファイルには、パッケージ・コメントとJavadocタグのみを格納できます。パッケージ注釈は格納できません。 +.RE +.PP +各パッケージは、\fBpackage\&.html\fRファイルまたは\fBpackage\-info\&.java\fRファイルのいずれかを1つ持つことができますが、その両方を持つことはできません。このどちらかのファイルをソース・ファイルとともに、ソース・ツリー内のそのパッケージ・ディレクトリ内に配置してください。 +.PP +package\-info\&.javaファイル +.PP +\fBpackage\-info\&.java\fRファイルには、次の構造のパッケージ・コメントを含めることができます。コメントは、パッケージ宣言の前に配置されます。 +.PP +\fB注意:\fR +コメント区切り文字である\fB/**\fRおよび\fB*/\fRが存在する必要がありますが、中間の行の先頭のアスタリスクは省略可能です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * Provides the classes necessary to create an \fR +\fB * applet and the classes an applet uses \fR +\fB * to communicate with its applet context\&.\fR +\fB * <p>\fR +\fB * The applet framework involves two entities:\fR +\fB * the applet and the applet context\&.\fR +\fB * An applet is an embeddable window (see the\fR +\fB * {@link java\&.awt\&.Panel} class) with a few extra\fR +\fB * methods that the applet context can use to \fR +\fB * initialize, start, and stop the applet\&.\fR +\fB *\fR +\fB * @since 1\&.0\fR +\fB * @see java\&.awt\fR +\fB */\fR +\fBpackage java\&.lang\&.applet;\fR + +.fi +.if n \{\ +.RE +.\} +.PP +package\&.htmlファイル +.PP +\fBpackage\&.html\fRファイルには、次の構造のパッケージ・コメントを含めることができます。コメントは、\fB<body>\fR要素に配置されます。 +.PP +ファイル: +\fBjava/applet/package\&.html\fR +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<HTML>\fR +\fB<BODY>\fR +\fBProvides the classes necessary to create an applet and the \fR +\fBclasses an applet uses to communicate with its applet context\&.\fR +\fB<p>\fR +\fBThe applet framework involves two entities: the applet\fR +\fBand the applet context\&. An applet is an embeddable\fR +\fBwindow (see the {@link java\&.awt\&.Panel} class) with a\fR +\fBfew extra methods that the applet context can use to\fR +\fBinitialize, start, and stop the applet\&. \fR + +\fB@since 1\&.0 \fR +\fB@see java\&.awt\fR +\fB</BODY>\fR +\fB</HTML>\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBpackage\&.html\fRファイルは通常のHTMLファイルであり、パッケージ宣言を含んでいません。パッケージ・コメント・ファイルの内容はHTMLで記述しますが、例外が1つあります。このドキュメンテーション・コメントには、コメント区切り文字である\fB/**\fRと\fB*/\fR、または行頭のアスタリスクを含めない、という点です。コメントを書く場合は、最初の文をパッケージのサマリーとし、\fB<body>\fRタグと最初の文の間にタイトルやその他のテキストを含めないようにします。パッケージ・タグを含めることができます。すべてのブロック・タグは、主説明の後に配置する必要があります。\fB@see\fRタグをパッケージ・コメント・ファイルに追加する場合には、完全修飾名を使用する必要があります。 +.PP +コメント・ファイルの処理 +.PP +\fBjavadoc\fRコメントを実行すると、パッケージ・コメント・ファイルが検索されます。パッケージ・コメント・ファイルが見つかった場合は、\fBjavadoc\fRコマンドは次の手順を実行します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +処理できるようにコメントをコピーします。package\&.htmlの場合、\fBjavadoc\fRコマンドは、\fB<body>\fRと\fB</body>\fR +HTMLタグ間ですべてのコンテンツをコピーします。\fB<title>\fRタグ、ソース・ファイルの著作権文または他の情報を配置する\fB<head>\fRセクションを含めることができますが、これらは生成されたドキュメントに表示されません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ・タグを処理します。パッケージ・タグを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +処理したテキストを生成されたパッケージのサマリー・ページの下部に挿入します。Javaプラットフォーム、Standard Edition API仕様の概要 +(http://docs\&.oracle\&.com/javase/8/docs/api/overview\-summary\&.html)を参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージのサマリー・ページの先頭に、パッケージ・コメントの最初の文をコピーします。さらに、\fBjavadoc\fRコマンドは、概要ページのパッケージ・リストに、パッケージ名とパッケージ・コメントの最初の文を追加します。Javaプラットフォーム、Standard Edition API仕様の概要 +(http://docs\&.oracle\&.com/javase/8/docs/api/overview\-summary\&.html)を参照してください +.sp +文の終わりは、クラスやメンバーの主説明の最初の文の終わりと同じルールによって判断されます。 +.RE +.SS "概要コメント・ファイル" +.PP +ドキュメント化する各アプリケーションまたはパッケージ・セットは、独自の概要ドキュメンテーション・コメントを持つことができ、それは専用のソース・ファイルに保持されます。その内容は、\fBjavadoc\fRコマンドによって生成される概要ページに組み込まれます。このコメントには、通常、アプリケーションまたはパッケージ・セット全体に当てはまるドキュメントを記述します。 +.PP +このファイルにはoverview\&.htmlなどの名前を付けることができ、どこに配置してもかまいません。一般的な場所は、ソース・ツリーの最上部です。 +.PP +たとえば、\fBjava\&.applet\fRパッケージのソース・ファイルが/home/user/src/java/appletディレクトリに格納されている場合、概要コメント・ファイルは/home/user/src/overview\&.htmlに作成できます。 +.PP +異なるパッケージのセットに対して\fBjavadoc\fRコマンドを複数回実行する場合は、同じ1つのソース・ファイルのセットに対して複数の概要コメント・ファイルを作成できます。たとえば、内部ドキュメント用に\fB\-private\fRを指定して\fBjavadoc\fRコマンドを1回実行した後、公開ドキュメント用にそのオプションを指定しないで再度実行することができます。この場合、各概要コメント・ファイルの1文目で、そのドキュメントを公開用または内部用として記述できます。 +.PP +概要コメント・ファイルの内容は、HTMLで記述された1つの大きなドキュメンテーション・コメントです。最初の文はアプリケーションまたはパッケージのセットのサマリーとします。\fB<body>\fRタグと最初の文の間にタイトルやその他のテキストを含めないようにします。{\fB@link}\fRなどのインライン・タグを除くすべてのタグは、主説明の後に配置する必要があります。\fB@see\fRタグを追加する場合には、完全修飾名を使用する必要があります。 +.PP +\fBjavadoc\fRコマンドの実行時に、\fB\-overview\fRオプションを使用して概要コメント・ファイル名を指定します。このファイルは、パッケージ・コメント・ファイルと同じように処理されます。\fBjavadoc\fRコマンドは次の手順を実行します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB<body>\fRと\fB</body>\fRタグ間で、処理するすべてのコンテンツをコピーします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +概要タグがあれば処理します。概要タグを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +処理したテキストを生成された概要ページの下部に挿入します。JavaプラットフォームStandard Edition API仕様の概要 +(http://docs\&.oracle\&.com/javase/8/docs/api/overview\-summary\&.html)を参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +概要サマリー・ページの先頭に、概要コメントの最初の文をコピーします。 +.RE +.SS "未処理のファイル" +.PP +ソース・ファイルには、\fBjavadoc\fRコマンドによって宛先ディレクトリにコピーされる、任意のファイルを含めることができます。このようなファイルには、通常、グラフィック・ファイル、サンプルのJavaソースおよびクラス・ファイル、一般的なJavaソース・ファイルのドキュメンテーション・コメントの影響を受けない多くの内容を含む独立したHTMLファイルなどがあります。 +.PP +未処理のファイルを含めるには、doc\-filesというディレクトリにファイルを配置します。doc\-filesディレクトリは、ソース・ファイルを含む任意のパッケージ・ディレクトリのサブディレクトリになることができます。doc\-filesサブディレクトリは、パッケージごとに1つ用意できます。 +.PP +たとえば、ボタンのイメージを\fBjava\&.awt\&.Button\fRクラスのドキュメントに含める場合には、そのイメージ・ファイルを/home/user/src/java/awt/doc\-files/ディレクトリに置きます。doc\-filesディレクトリを/home/user/src/java/doc\-filesに置かないでください。javaはパッケージではないからです。ソース・ファイルを含めることもできません。 +.PP +\fBjavadoc\fRコマンドはファイルを参照しないので、未処理のファイルへのすべてのリンクは、コードに含まれている必要があります。\fBjavadoc\fRコマンドはディレクトリとそのすべての内容を宛先にコピーします。次の例では、Button\&.javaドキュメンテーション・コメントのリンクがどのように見えるかを示しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This button looks like this: \fR +\fB * <img src="doc\-files/Button\&.gif">\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.SS "テストおよびテンプレート・ファイル" +.PP +ソース・ツリーのテストおよびテンプレート・ファイルを、ソース・ファイルが存在するディレクトリまたはサブディレクトリと同じディレクトリに格納できます。テストおよびテンプレート・ファイルが処理されるのを防ぐには、\fBjavadoc\fRコマンドを実行し、明示的に個別のソース・ファイル名を渡します。 +.PP +テスト・ファイルは、有効な、コンパイル可能なソース・ファイルです。テンプレート・ファイルは、有効な、互換性のあるソース・ファイルではありませんが、多くの場合、\fB\&.java\fR接尾辞を持っています。 +.PP +テスト・ファイル +.PP +テスト・ファイルを、名前なしパッケージや、ソース・ファイルが存在するパッケージとは別のパッケージに属するようにする場合、テスト・ファイルをソース・ファイルの下のサブディレクトリに配置し、そのディレクトリに無効な名前を付けます。テスト・ファイルをソースと同じディレクトリに配置し、パッケージ名を示すコマンド行引数を指定して\fBjavadoc\fRコマンドを呼び出すと、テスト・ファイルは警告またはエラーを引き起こします。ファイルが無効な名前を持つサブディレクトリ内に存在する場合、テスト・ファイル・ディレクトリはスキップされ、エラーまたは警告は発行されません。たとえば、ソース・ファイルのテスト・ファイルをcom\&.package1に追加するには、無効なパッケージ名のサブディレクトリに配置します。次のディレクトリ名にはハイフンが含まれているため無効です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcom/package1/test\-files/\fR + +.fi +.if n \{\ +.RE +.\} +.PP +テスト・ファイルにドキュメンテーション・コメントが含まれる場合、\fBjavadoc\fRコマンドの個別の実行で、ワイルドカードを含んだテスト・ソース・ファイル名(\fBcom/package1/test\-files/*\&.java\fRなど)を渡して、テスト・ファイルのドキュメントを生成するように設定できます。 +.PP +テンプレート・ファイル +.PP +テンプレート・ファイルをソース・ディレクトリに配置するが、\fBjavadoc\fRコマンドを実行するときにエラーを生成しない場合、ファイルに\fBBuffer\-Template\&.java\fRなどの無効な名前を付けて、処理させないようにします。\fBjavadoc\fRコマンドは、接尾辞の\fB\&.java\fRが削除されると有効なクラス名になる名前を持つソース・ファイルのみを処理します。 +.SH "生成されるファイル" +.PP +デフォルトでは、\fBjavadoc\fRコマンドは、HTML形式のドキュメントを生成する標準ドックレットを使用します。標準ドックレットは、ここで説明する、基本内容ページ、相互参照ページ、サポート・ページを生成します。各HTMLページは個別のファイルに対応します。\fBjavadoc\fRコマンドは、2つのタイプのファイルを生成します。最初のタイプには、クラスおよびインタフェースに応じた名前が付けられます。2番目のタイプには、最初のタイプのファイルとの競合を防ぐために、ハイフンが含まれます(package\-summary\&.htmlなど)。 +.SS "基本内容ページ" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +記載されているクラスまたはインタフェースごとに1つのクラスまたはインタフェース・ページ(classname\&.html)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +記載されているパッケージごとに1つのパッケージ・ページ(package\-summary\&.html)。\fBjavadoc\fRコマンドは、ソース・ツリーのパッケージ・ディレクトリ内にあるpackage\&.htmlまたはpackage\-info\&.javaという名前のファイル内のHTMLテキストをすべて組み入れます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージのセット全体に対して1つの概要ページ(overview\-summary\&.html)。概要ページは、生成ドキュメントの先頭ページになります。\fBjavadoc\fRコマンドは、\fB\-overview\fRオプションで指定されたファイル内のHTMLテキストをすべて組み入れます。概要ページが作成されるのは、\fBjavadoc\fRコマンドに複数のパッケージ名を渡した場合のみです。HTMLフレームおよびオプションを参照してください。 +.RE +.SS "相互参照ページ" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージのセット全体に対して1つのクラス階層ページ(overview\-tree\&.html)。階層ページを表示するには、ナビゲーション・バーの「概要」をクリックしてから、「階層ツリー」をクリックします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージごとに1つのクラス階層ページ(package\-tree\&.html)。階層ページを表示するには、特定のパッケージ、クラス、またはインタフェースのページに移動し、「階層ツリー」をクリックしてそのパッケージの階層を表示します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージごとに1つの使用ページ(package\-use\&.html)と、クラスおよびインタフェースごとに1つずつの使用ページ(class\-use/classname\&.html)。使用ページでは、指定したクラス、インタフェース、またはパッケージの一部を使用しているパッケージ、クラス、メソッド、コンストラクタ、およびフィールドについて記述されます。たとえば、クラスまたはインタフェースAを例にすると、その使用ページには、Aのサブクラス、Aとして宣言されたフィールド、Aを返すメソッド、A型のパラメータを持つメソッドおよびコンストラクタが組み込まれます。使用ページを表示するには、パッケージ、クラス、またはインタフェースに移動し、ナビゲーション・バーの「使用」リンクをクリックします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +すべての非推奨APIとその推奨する代替をリストする非推奨APIページ(deprecated\-list\&.html)。非推奨APIは将来の実装で削除される可能性があるので使用しないでください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +定数フィールドの値用の定数フィールド値ページ(constant\-values\&.html)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +直列化された形式ページ(serialized\-form\&.html)。フィールドおよびメソッドの説明を含む、直列化可能かつ外部化可能なクラスに関する情報用のページです。このページ内の情報は、APIを使用する開発者ではなく、再実装者に必要な情報です。直列化された形式ページへアクセスするには、直列化されたクラスに移動して、そのクラス・コメントにある「関連項目」セクションで「直列化された形式」をクリックします。標準ドックレットは直列化された形式ページを生成します。このページには、Serializableを実装するすべてのクラス(publicまたは非public)が、その\fBreadObject\fRや\fBwriteObject\fRメソッド、直列化されたフィールド、および\fB@serial\fR、\fB@serialField\fR、\fB@serialData\fRタグからのドキュメンテーション・コメントとともにリストされます。直列化可能なpublicクラスを除外するには、そのクラス(またはそのパッケージ)を\fB@serial\fR +excludeでマークします。直列化可能なpackage\-privateクラスを含めるには、そのクラス(またはそのパッケージ)を\fB@serial\fR +includeでマークします。リリース1\&.4では、\fB\-private\fRオプションを指定せずに\fBjavadoc\fRコマンドを実行することにより、publicクラスおよびprivateクラスの完全に直列化された形式を生成できます。オプションを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +索引ページ(\fBindex\-*\&.html\fR)。すべてのクラス名、インタフェース名、コンストラクタ名、フィールド名、およびメソッド名がアルファベット順に並んでいます。索引ページは、Unicodeを扱えるように国際化されています。1つのファイルとして生成することも、先頭文字(英語の場合A\(enZ)ごとに別々のファイルとして生成することもできます。 +.RE +.SS "サポート・ページ" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ヘルプ・ページ(help\-doc\&.html)。ナビゲーション・バーや前述の各ページに関する説明が記載されています。デフォルトのヘルプ・ファイルを独自のカスタム・ヘルプ・ファイルでオーバーライドするには、\fB\-helpfile\fRを使用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +表示用のHTMLフレームを作成する1つのindex\&.htmlファイル。フレーム付きの先頭ページを表示するにはこのファイルをロードします。index\&.htmlファイルには、テキスト・コンテンツは含まれていません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +複数のフレーム・ファイル(\fB*\-frame\&.html\fR)。パッケージ、クラス、およびインタフェースのリストが含まれています。フレーム・ファイルはHTMLフレームを表示します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +パッケージ・リスト・ファイル(package\-list)。\fB\-link\fRおよび\fB\-linkoffline\fRオプションで使用されます。パッケージ・リスト・ファイルはテキスト・ファイルであり、どのリンクからもアクセスできません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +スタイルシート・ファイル(stylesheet\&.css)。生成されるページの一部の要素について色、フォント・ファミリ、フォント・サイズ、フォント・スタイル、および配置を制御します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +doc\-filesディレクトリ。宛先ディレクトリにコピーするイメージ、サンプル・コード、ソース・コードなどのファイルが格納されます。これらのファイルは、\fBjavadoc\fRコマンドによって処理されません。このディレクトリは、ソース・ツリーの中に存在する場合にのみ処理されます。 +.RE +.PP +オプションを参照してください。 +.SS "HTMLフレーム" +.PP +\fBjavadoc\fRコマンドは、コマンドに渡された値に基づき、最小限必要な数(2または3)のフレームを生成します。\fBjavadoc\fRコマンドに引数として1つのパッケージ名または1つのパッケージに含まれるソース・ファイルを渡す場合は、パッケージのリストが省略されます。そのかわりに、\fBjavadoc\fRコマンドは左側の列に1つのフレームを作成し、クラスのリストを表示します。複数のパッケージ名を渡した場合は、\fBjavadoc\fRコマンドは、すべてのパッケージをリストする第3のフレームと概要ページ(overview\-summary\&.html)を作成します。フレームを省略するには、「フレームなし」リンクをクリックするか、overview\-summary\&.htmlページからページ・セットを表示します。 +.SS "生成されるファイルの構造" +.PP +生成されるクラス・ファイルおよびインタフェース・ファイルは、Javaソース・ファイルおよびクラス・ファイルと同じディレクトリ階層に編成されます。1つのサブパッケージにつき1つのディレクトリ、という構造になります。 +.PP +たとえば、\fBjava\&.applet\&.Applet\fRクラス用に生成されるドキュメントは、java/applet/Applet\&.htmlに格納されます。 +.PP +生成先ディレクトリの名前が\fBapidocs\fRだとすると、\fBjava\&.applet\fRパッケージのファイルの構造は、次のとおりです。前述のように、\fIframe\fRという語を名前に含むファイルは、すべて左上または左下のフレームに表示されます。それ以外のHTMLファイルは、すべて右側のフレームに表示されます。 +.PP +ディレクトリは太字です。アスタリスク(*)は、\fBjavadoc\fRコマンドへの引数がパッケージ名ではなくソース・ファイル名である場合に省略されるファイルおよびディレクトリを示しています。引数がソース・ファイル名の場合、空のパッケージ・リストが作成されます。doc\-filesディレクトリは、ソース・ツリー内に存在する場合にのみ、生成先に作成されます。生成されるファイルを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBapidocs\fR: 最上位レベル・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +index\&.html: HTMLフレームを設定する初期ページ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +*overview\-summary\&.html: パッケージ・リストとサマリー +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +overview\-tree\&.html: すべてのパッケージのクラス階層 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +deprecated\-list\&.html: すべてのパッケージの非推奨API +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +constant\-values\&.html: すべてのパッケージの静的フィールド値 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +serialized\-form\&.html: すべてのパッケージの直列化されたフォーム +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +*overview\-frame\&.html: 左上のフレームに表示するすべてのパッケージ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +allclasses\-frame\&.html: 左下のフレームに表示するすべてのクラス +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +help\-doc\&.html: Javadocページの編成に関するヘルプ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +index\-all\&.html: +\fB\-splitindex\fRオプションなしで作成されたデフォルトの索引 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBindex\-files\fR: +\fB\-splitindex\fRオプションを指定して作成されたディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +index\-<number>\&.html: +\fB\-splitindex\fRオプションを指定して作成された索引ファイル +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-list: 外部参照を解決するためのパッケージ名 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +stylesheet\&.css: フォント、色、位置などを定義します +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjava\fR: パッケージ・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBapplet\fR: サブパッケージ・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Applet\&.html: +\fBApplet\fRクラス・ページ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +AppletContext\&.html: +\fBAppletContext\fRインタフェース +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +AppletStub\&.html: +\fBAppletStub\fRインタフェース +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +AudioClip\&.html: +\fBAudioClip\fRインタフェース +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-summary\&.html: クラスとサマリー +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-frame\&.html: 左下のフレームに表示するパッケージ・クラス +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-tree\&.html: このパッケージのクラス階層 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +package\-use\&.html: このパッケージが使用される場所 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdoc\-files\fR: イメージおよびサンプル・ファイルのディレクトリ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBclass\-use\fR: イメージおよびサンプル・ファイルの場所 +.sp +\- Applet\&.html: Appletクラスの使用 +.sp +\- AppletContext\&.html: +\fBAppletContext\fRインタフェースの使用 +.sp +\- AppletStub\&.html: +\fBAppletStub\fRインタフェースの使用 +.sp +\- AudioClip\&.html: +\fBAudioClip\fRインタフェースの使用 +.RE +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBsrc\-html\fR: ソース・コード・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjava\fR: パッケージ・ディレクトリ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBapplet\fR: サブパッケージ・ディレクトリ +.sp +\- Applet\&.html: Appletソース・コード +.sp +\- AppletContext\&.html: +\fBAppletContext\fRソース・コード +.sp +\- AppletStub\&.html: +\fBAppletStub\fRソース・コード +.sp +\- AudioClip\&.html: +\fBAudioClip\fRソース・コード +.RE +.RE +.RE +.SS "生成されるAPI宣言" +.PP +\fBjavadoc\fRコマンドは、それぞれのクラス、インタフェース、フィールド、コンストラクタ、およびメソッドの記述の最初に、そのAPI用の宣言を生成します。たとえば、\fBBoolean\fRクラスの宣言は、次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic final class Boolean\fR +\fBextends Object\fR +\fBimplements Serializable\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBBoolean\&.valueOf\fRメソッドの宣言は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static Boolean valueOf(String s)\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavadoc\fRコマンドは、修飾子\fBpublic\fR、\fBprotected\fR、\fBprivate\fR、\fBabstract\fR、\fBfinal\fR、\fBstatic\fR、\fBtransient\fR、および\fBvolatile\fRを含めることができますが、\fBsynchronized\fRおよび\fBnative\fRはできません。\fBsynchronized\fRおよび\fBnative\fR修飾子は、実装の詳細とみなされているため、API仕様には含まれません。 +.PP +APIでは、並行性セマンティクスについて、キーワード\fBsynchronized\fRに依存するのではなく、コメントの主説明としてドキュメント化する必要があります。たとえば、「1つのenumerationを複数のスレッドから並行して使用することはできない」のように記述します。ドキュメントには、これらのセマンティクスを実現する方法を記述しないでください。たとえば、\fBHashtable\fRオプションはスレッドセーフである必要がありますが、「エクスポートされるすべてのメソッドを同期化してそれを実現する」のように指定する根拠はありません。より高度な並行性のために、バケット・レベルで内部的に同期化する権限を保有しておくことをお薦めします。 +.SH "ドキュメンテーション・コメント" +.PP +このセクションでは、ソース・コードのコメントとコメントの継承について説明します。 +.SS "ソース・コード・コメント" +.PP +ソース・コードの任意のクラス、インタフェース、メソッド、コンストラクタ、またはフィールドの宣言の前に、ドキュメンテーション・コメントを記述することができます。各パッケージにもドキュメンテーション・コメントを作成できます。構文は若干異なりますが、概要にもドキュメンテーション・コメントを作成できます。ドキュメンテーション・コメントは、\fB/**\fRと、終わりを表す\fB*/\fRの間にある文字から構成されます。先頭のアスタリスクは各行で使用でき、次の項で詳しく説明します。コメントのテキストは、複数行にわたって記述できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This is the typical format of a simple documentation comment\fR +\fB * that spans two lines\&.\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +スペースを節約するには、コメントを1行に入れます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/** This comment takes up only one line\&. */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コメントの配置 +.PP +ドキュメンテーション・コメントは、クラス、インタフェース、コンストラクタ、メソッド、またはフィールド宣言の直前に配置される場合にのみ認識されます。メソッドの本体に置かれているドキュメンテーション・コメントは無視されます。\fBjavadoc\fRコマンドは、宣言文ごとに1つのドキュメンテーション・コメントしか認識しません。タグを使用できる場所を参照してください。 +.PP +よくある間違いは、クラス・コメントとクラス宣言の間に\fBimport\fR文を置いてしまうことです。\fBjavadoc\fRコマンドはクラス・コメントを無視するので、\fBimport\fR文をこの場所に配置しないでください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This is the class comment for the class Whatever\&.\fR +\fB */\fR +\fB \fR +\fBimport com\&.example; // MISTAKE \- Important not to put import statement here\fR +\fB \fR +\fBpublic class Whatever{ }\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コメントのパーツ +.PP +ドキュメンテーション・コメントには、主説明とその後に続くタグ・セクションが含まれます。主説明は、開始区切り文字\fB/**\fRで始まり、タグ・セクションまで続きます。タグ・セクションは、先頭文字が\fB@\fRの行で定義される最初のブロック・タグから始まります(先頭のアスタリスク、空白文字、先頭の区切り文字\fB/**\fRは除く)。主説明を記述せず、タグ・セクションのみのコメントを記述することもできます。主説明は、タグ・セクション以降に続けることはできません。タグの引数は、複数行にわたって記述できます。タグの数に制限はありません。何回も記述できるタグと、1回しか記述できないタグがあります。たとえば、次の\fB@see\fRタグからタグ・セクションは始まります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This sentence holds the main description for this documentation comment\&.\fR +\fB * @see java\&.lang\&.Object\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ブロックおよびインライン・タグ +.PP +タグは、\fBjavadoc\fRコマンドが処理するドキュメンテーション・コメント内の特殊なキーワードです。タグには2つのタイプがあります。1つは\fB@tag\fRタグのように表記されるブロック・タグ(スタンドアロン・タグとも呼ばれる)、もう1つは\fB{@tag}\fRタグのように中カッコで囲んで表記されるインライン・タグです。ブロック・タグが解釈されるには、行頭のアスタリスク、空白文字、区切り文字(\fB/**\fR)を除いて、行の先頭に置く必要があります。これは、\fB@\fR文字をテキスト内の別の場所で使用しても、タグの開始として解釈されないことを意味しています。\fB@\fR文字を使用して行を開始しても、それが解釈されないようにするには、HTMLエンティティ\fB@\fRを使用します。それぞれのブロック・タグには、関連付けられたテキストがあります。このテキストは、タグの後から、次のタグの前、またはドキュメンテーション・コメントの最後までの間に記述されたテキストです(タグまたはコメント区切り文字を除く)。この関連テキストは、複数行にわたって記述できます。インライン・タグは、テキストを記述できる場所であればどこにでも置くことができ、解釈されます。次の例にはブロック・タグ\fB@deprecated\fRとインライン・タグ\fB{@link}\fRが含まれています。javadocタグを参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @deprecated As of JDK 1\&.1, replaced by {@link #setBounds(int,int,int,int)}\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +HTMLでのコメントの記述 +.PP +テキストはHTMLエンティティとHTMLタグを使用してHTMLで記述される必要があります。使用するブラウザがサポートする任意のHTMLのバージョンを使用できます。標準ドックレットは、カスケーディング・スタイル・シートおよびフレームを含め、ドキュメンテーション・コメント以外の部分でHTML 3\&.2に準拠したコードを生成します。フレーム・セットのため、生成されたファイルにはHTML 4\&.0が推奨されます。 +.PP +たとえば、より小さい記号(<)およびより大きい記号(>)のエンティティは、\fB<\fRおよび\fB>\fRと記述する必要があります。同様に、アンパサンド(&)は\fB&\fRと記述する必要があります。次の例では、太字のHTMLタグ\fB<b>\fRを使用しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * This is a <b>doc</b> comment\&.\fR +\fB * @see java\&.lang\&.Object\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +.PP +先頭のアスタリスク +.PP +\fBjavadoc\fRコマンドによるドキュメンテーション・コメントの解析時に、各行の先頭にあるアスタリスク(*)文字は破棄されます。最初のアスタリスク(*)文字より前にある空白やタブも破棄されます。行頭のアスタリスクを省略した場合、インデントを保持したままでサンプル・コードを\fB<PRE>\fRタグ内のドキュメンテーション・コメントに直接貼り付けられるように、先頭の空白文字は削除されなくなります。ブラウザは、空白文字をタブよりも一律に解釈します。インデントの起点は(区切り文字\fB/**\fRまたは\fB<PRE>\fRタグではなく)左マージンになります。 +.PP +最初の文 +.PP +各ドキュメンテーション・コメントの最初の文は、宣言されているエンティティに関する簡潔かつ完全なサマリー文である必要があります。この文は、空白、タブ、または行終了文字が続く最初のピリオド、または最初のブロック・タグがある位置で終わります。最初の文は、\fBjavadoc\fRコマンドによってHTMLページの先頭にあるメンバーのサマリーの部分にコピーされます。 +.PP +複数フィールドの宣言 +.PP +Javaプラットフォームでは、1つの文で複数のフィールドを宣言できます。ただし、この文には、1つのドキュメンテーション・コメントしか記述できません。そのコメントが、すべてのフィールドに対してコピーされます。フィールドごとにドキュメンテーション・コメントを記述する必要がある場合は、各フィールドを別々の文で宣言する必要があります。たとえば、次のドキュメンテーション・コメントは、1つの宣言として記述すると不適切です。この場合は、宣言を2つに分けることをお薦めします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/** \fR +\fB * The horizontal and vertical distances of point (x,y)\fR +\fB */\fR +\fBpublic int x, y; // Avoid this \fR +\fB \fR +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavadoc\fRコマンドは、上のコードから次のようなドキュメントを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic int x\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The horizontal and vertical distances of point (x, y)\&. +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic int y\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The horizontal and vertical distances of point (x, y)\&. +.PP +ヘッダー・タグの使用 +.PP +メンバーに対してドキュメンテーション・コメントを記述するときには、\fB<H1>\fRおよび\fB<H2>\fRなどのHTML見出しタグを使用しないことをお薦めします。\fBjavadoc\fRコマンドは、完全な構造化ドキュメントを作成するので、このような構造化タグが使用されていると、生成ドキュメントの形式が悪影響を受けることがあります。ただし、クラスやパッケージのコメントでは、これらの見出しを使用して独自の構造を指定してかまいません。 +.SS "メソッド・コメントの継承" +.PP +\fBjavadoc\fRコマンドでは、クラスおよびインタフェースでメソッド・コメントを継承して、欠落したテキストを入力したり、明示的にメソッド・コメントを継承することができます。コンストラクタ、フィールド、およびネストされたクラスは、ドキュメンテーション・コメントを継承しません。 +.PP +\fB注意:\fR +ドキュメンテーション・コメントをコピーに利用するには、継承したメソッドのソース・ファイルが\fB\-sourcepath\fRオプションで指定したパスのみに置かれている必要があります。コマンド行で、クラスもパッケージも渡す必要はありません。この点はリリース1\&.3\&.\fIn\fR以前とは対照的です。これまでは、クラスがドキュメント化されるクラスであることが必要でした。 +.PP +欠落テキストの入力 +.PP +主説明、または\fB@return\fR、\fB@param\fR、\fB@throws\fRタグがメソッド・コメントから欠落している場合、\fBjavadoc\fRコマンドは、対応する主説明またはタグ・コメントを、それがオーバーライドまたは実装しているメソッド(ある場合)からコピーします。メソッド・コメントの継承を参照してください。 +.PP +特定のパラメータの\fB@param\fRタグが見つからない場合、そのパラメータのコメントが、上位の継承階層のメソッドからコピーされます。特定の例外の\fB@throws\fRタグが見つからない場合、その例外が宣言されている場合にかぎり、\fB@throws\fRタグがコピーされます。 +.PP +この動作はリリース1\&.3以前の動作とは対照的です。これまでのバージョンでは、主説明またはタグが存在すれば、コメントは一切継承されませんでした。 +.PP +javadocタグおよびオプションを参照してください。 +.PP +明示的な継承 +.PP +\fB{@inheritDoc}\fRインライン・タグをメソッドの主説明または\fB@return\fR、\fB@param\fR、\fB@throws\fRタグ・コメントに挿入します。対応する継承された主説明またはタグ・コメントは、その場所にコピーされます。 +.SS "クラスおよびインタフェースの継承" +.PP +コメントの継承は、クラスおよびインタフェースからの継承の、考えられるすべての場合に発生します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラスのメソッドがスーパークラスのメソッドをオーバーライドしている場合 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +インタフェースのメソッドがスーパーインタフェースのメソッドをオーバーライドしている場合 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラスのメソッドがインタフェースのメソッドを実装している場合 +.RE +.PP +最初の2つのケースでは、\fBjavadoc\fRコマンドは、オーバーライドしているメソッドのドキュメント内に\fI「オーバーライド」\fRという小見出しを生成します。コメントが継承されているかどうかにかかわらず、オーバーライドされているメソッドへのリンクが含まれます。 +.PP +3つ目のケース(特定のクラスのメソッドがインタフェースのメソッドを実装している場合)では、\fBjavadoc\fRコマンドは、オーバーライドしているメソッドのドキュメント内に\fI「定義」\fRという小見出しを生成します。コメントが継承されているかどうかにかかわらず、実装されているメソッドへのリンクが含まれます。 +.SS "メソッド・コメントのアルゴリズム" +.PP +メソッドにドキュメンテーション・コメントがない、または\fB{@inheritDoc}\fRタグがある場合、\fBjavadoc\fRコマンドは次のアルゴリズムを使用して適用できるコメントを検索します。アルゴリズムは、最も特定される適用可能なドキュメンテーション・コメントを探し、スーパークラスよりもインタフェースを優先するように設計されています。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +直接に実装されている(または、拡張されている)インタフェースを、メソッドの宣言で\fBimplements\fR(または\fBextends\fR)という語の後に出現する順序で、1つずつ調べます。このメソッドについて最初に見つかったドキュメンテーション・コメントを採用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +手順1でドキュメンテーション・コメントが見つからなかった場合は、直接実装されている(または、拡張されている)インタフェースのそれぞれに対して、このアルゴリズム全体を再帰的に適用します(その際の順序は、手順1でインタフェースを調べたときの順序と同じ)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +手順2でドキュメンテーション・コメントが見つからなかった場合で、このクラスが\fBObject\fR以外のクラスであるが、インタフェースではない場合は、次のように処理します。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +スーパークラスにこのメソッドについてのドキュメンテーション・コメントが記述されている場合は、そのコメントを採用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +手順3aでドキュメンテーション・コメントが見つからなかった場合は、スーパークラスに対して、このアルゴリズム全体を再帰的に適用します。 +.RE +.RE +.SH "JAVADOCタグ" +.PP +\fBjavadoc\fRコマンドは、Javaのドキュメンテーション・コメント内に埋め込まれた特別なタグを解析します。\fBjavadoc\fRタグを使用すると、完全な整形式のAPIをソース・コードから自動的に生成できます。タグはアットマーク記号(\fB@\fR)で始まり、大文字と小文字が区別されます。これらのタグは、表示されているとおりに大文字と小文字を使用して入力する必要があります。タグは、行の先頭(先頭の空白文字と省略可能なアスタリスクの後)に置く必要があります。そうしないと、テキストとして扱われます。慣例として、同じ名前のタグは1箇所にまとめます。たとえば、\fB@see\fRタグが複数ある場合は、すべて同じ場所にまとめて配置します。詳細は、タグを使用できる場所を参照してください。 +.PP +タグには、次のタイプがあります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ブロック・タグ: ブロック・タグは主説明に続くタグ・セクション内にのみ配置します。ブロック・タグは、\fI@tag\fRの形式をとります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +インライン・タグ: インライン・タグは主説明内またはブロック・タグのコメント内の任意の場所に配置します。インライン・タグは\fI{@tag}\fRのように中カッコで囲みます。 +.RE +.PP +カスタム・タグについては、\-tag tagname:Xaoptcmf:"taghead"を参照してください。タグを使用できる場所も参照してください。 +.SS "タグの説明" +.PP +@author \fIname\-text\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fB\-author\fRオプションが使用されている場合、指定した名前のテキストの作成者エントリを生成されるドキュメントに追加します。1つのドキュメンテーション・コメントに複数の\fB@author\fRタグを含めることができます。1つの\fB@author\fRタグに1つの名前を指定することも、複数の名前を指定することもできます。前者の場合は、\fBjavadoc\fRコマンドによって名前と名前の間にカンマ(,)と空白文字が挿入されます。後者の場合は、テキスト全体が解析されることなく、生成ドキュメントにコピーされます。したがって、カンマではなく、各言語に対応した名前区切り文字を使用する必要があるときに、1行に複数の名前を指定できます。JavadocツールでのDocコメントの記述方法の@authorに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@author)を参照してください。 +.RE +.PP +{@code \fItext\fR} +.RS 4 +JDK 1\&.5で導入 +.sp +\fB<code>{@literal}</code>\fRと同じです。 +.sp +テキストをHTMLマークアップまたはネストされたJavadocタグとして解釈せずに、textをコード・フォントで表示します。これにより、ドキュメンテーション・コメントでは、パラメータの型(\fB<Object>\fR)、不等号(\fB3 < 4\fR)、矢印(\fB<\-\fR)などで、通常の山カッコ(<および>)をHTMLエンティティ(\fB<\fRおよび\fB>\fR)のかわりに使用できます。たとえば、ドキュメンテーション・コメント・テキスト\fB{@code A<B>C}\fRは、\fBA<B>C\fRとして変更されずに生成されたHTMLページに表示されます。つまり、\fB<B>\fRが太字として解釈されず、そのフォントはコード・フォントになります。コード・フォントなしで同じ機能を実現するには、\fB{@literal}\fRタグを使用します。 +.RE +.PP +@deprecated \fIdeprecated\-text\fR +.RS 4 +JDK 1\&.0で導入 +.sp +このAPIは動作し続けますが、このAPIを使用しないことを薦めるコメントを追加します。\fBjavadoc\fRコマンドは、\fBdeprecated\-text\fRを主説明の前に移動してイタリックにし、その前に太字の警告「推奨されていません。」を追加します。このタグは、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、およびフィールドで有効です。 +.sp +非推奨テキストの最初の文では、そのAPIが推奨されなくなった時期と、代替として使用するAPIをユーザーに提示する必要があります。\fBjavadoc\fRコマンドは、この最初の文を、サマリー・セクションと索引にコピーします。その後の文で非推奨になった理由を説明することもできます。代替APIを指し示す\fB{@link}\fRタグ(Javadoc 1\&.2以降の場合)を含める必要があります。 +.sp +\fI@deprecated annotation\fRタグを使用してプログラム要素を非推奨にします。APIを非推奨にする方法と時期 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation\&.html)を参照してください。 +.sp +JavadocツールでのDocコメントの記述方法の@deprecatedに関する項 + +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@deprecated)も参照してください。 +.RE +.PP +{@docRoot} +.RS 4 +JDK 1\&.3で導入 +.sp +生成されるページからの、生成ドキュメントの(生成先)ルート・ディレクトリへの相対パスを表します。このタグは、著作権のページや会社のロゴなど、生成されるすべてのページから参照するファイルを組み込むときに便利です。通常は、各ページの最下部から著作権のページにリンクします。 +.sp +この\fB{@docRoot}\fRタグは、コマンド行でもドキュメンテーション・コメント内でも使用できます。このタグは、任意のタグ(\fB@return\fR、\fB@param\fRおよび\fB@deprecated\fRタグなど)のテキスト部分を含む、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、およびフィールドで有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド行で、header、footerまたはbottomが定義されている場合、\fBjavadoc \-bottom \*(Aq<a href="{@docRoot}/copyright\&.html">Copyright</a>\*(Aq\fRとなります。 +.sp +\fB{@docRoot}\fRタグをmakefile内でこのように利用する場合、一部の\fBmakefile\fRプログラムでは、中カッコ\fB{}\fR文字を特別にエスケープする必要があります。たとえば、Inprise MAKEバージョン5\&.2をWindows上で実行する場合は、\fB{{@docRoot}}\fRのように、中カッコを二重にする必要があります。\fB\-bottom\fRオプションなどのオプションへの引数を囲むのに、二重(一重ではなく)引用符も必要です(\fBhref\fR引数を囲む引用符は省略)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ドキュメンテーション・コメントでは +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * See the <a href="{@docRoot}/copyright\&.html">Copyright</a>\&.\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +このタグが必要な理由は、生成ドキュメントが、サブパッケージと同じ深さを持つ階層構造のディレクトリに格納されるからです。式: +\fB<a href="{@docRoot}/copyright\&.html">\fRは、\fBjava/lang/Object\&.java\fRの場合\fB<a href="\&.\&./\&.\&./copyright\&.html">\fRに、\fBjava/lang/ref/Reference\&.java\fRの場合\fB<a href="\&.\&./\&.\&./\&.\&./copyright\&.html">\fRに解決されます。 +.RE +.RE +.PP +@exception \fIclass\-name description\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fB@throws\fRタグと同じです。@throws class\-name descriptionを参照してください。 +.RE +.PP +{@inheritDoc} +.RS 4 +JDK 1\&.4で導入 +.sp +最も近い継承可能なクラスまたは実装可能なインタフェースから、このタグの位置にある現在のドキュメンテーション・コメントに、ドキュメントを継承(コピー)します。これにより、より汎用的なコメントを継承ツリーの上位に記述し、コピーしたテキストを使用して記述することができます。 +.sp +このタグは、ドキュメンテーション・コメントの次の位置でのみ有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +メソッドの主説明ブロック内。この場合、主説明は、上位階層のクラスまたはインタフェースからコピーされます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +メソッドの\fB@return\fR、\fB@param\fR、\fB@throws\fRタグのテキスト引数内。この場合、タグ・テキストは、上位階層の対応するタグからコピーされます。 +.RE +.sp +継承階層でコメントを見つける方法に関する説明は、メソッド・コメントの継承を参照してください。このタグが見つからない場合、コメントは、この項で説明するルールに応じて、自動的に継承されるかどうかが決まります。 +.RE +.PP +{@link \fIpackage\&.class#member label\fR} +.RS 4 +JDK 1\&.2で導入 +.sp +表示テキストlabelとともにインライン・リンクを挿入します。labelは、参照クラスの指定されたパッケージ、クラス、またはメンバーの名前のドキュメントを指し示します。このタグは、\fB@return\fR、\fB@param\fRおよび\fB@deprecated\fRタグなどの任意のタグのテキスト部分を含む、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、およびフィールドで有効です。JavadocツールでのDocコメントの記述方法の@linkに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#{@link)を参照してください。 +.sp +このタグは\fB@see\fRタグに似ています。どちらのタグも、\fBpackage\&.class#member\fRと\fBlabel\fRの参照方法と、有効な構文が同じです。主な違いは、\fB{@link}\fRタグでは、「関連項目」セクションにリンクが配置されるかわりに、インライン・リンクが生成されるという点です。インライン・テキストの他の部分と区別するために、\fB{@link}\fRタグの最初と最後に中カッコを記述します。ラベル内で右中カッコ(\fB}\fR)を使用する必要がある場合、HTMLエンティティ記法\fB}\fRを使用します。 +.sp +1つ文の中で使用できる\fB{@link}\fRタグの数に制限はありません。このタグは、ドキュメンテーション・コメントの主説明部分、または\fB@deprecated\fR、\fB@return\fR、\fB@param\fRタグなどの任意のタグのテキスト部分で使用できます。 +.sp +たとえば、次のコメントでは\fBgetComponentAt(int,int)\fRメソッドを参照しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBUse the {@link #getComponentAt(int, int) getComponentAt} method\&.\fR + +.fi +.if n \{\ +.RE +.\} +標準ドックレットでは、このコードから次のHTMLが生成されます(このコメントが同じパッケージの別のクラスを参照している場合)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBUse the <a href="Component\&.html#getComponentAt(int, int)">getComponentAt</a> method\&.\fR + +.fi +.if n \{\ +.RE +.\} +前の行は、次のようにWebページに表示されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBUse the getComponentAt method\&.\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +{@linkplain \fIpackage\&.class#member label\fR} +.RS 4 +JDK 1\&.4で導入 +.sp +\fB{@link}\fRタグと同じ動作をしますが、リンク・ラベルがコード・フォントではなくプレーン・テキストで表示される点が異なります。ラベルがプレーン・テキストで記述されていると便利です。たとえば、「\fBRefer to {@linkplain add() the overridden method}\fR\&.」は「Refer to the overridden method」と表示されます。 +.RE +.PP +{@literal \fItext\fR} +.RS 4 +JDK 1\&.5で導入 +.sp +テキストをHTMLマークアップまたはネストされたJavadocタグとして解釈せずに、textを表示します。これにより、ドキュメンテーション・コメントでは、パラメータの型(\fB<Object>\fR)、不等号(\fB3 < 4\fR)、矢印(<\-)などで、山カッコ(\fB<および>\fR)をHTMLエンティティ(\fB<\fRおよび\fB>\fR)のかわりに使用できます。たとえば、ドキュメンテーション・コメント・テキスト\fB{@literal A<B>C}\fRは、\fBA<B>C\fRとしてブラウザの生成されたHTMLページで変更されずに表示されます。\fB<B>\fRは太字として解釈されません(コード・フォントになりません)。コード・フォントで同じ機能を実現するには、\fB{@code}\fRタグを使用します。 +.RE +.PP +@param \fIparameter\-name description\fR +.RS 4 +JDK 1\&.0で導入 +.sp +「パラメータ」セクションに、指定された\fBparameter\-name\fRの後に指定されたdescriptionを続けてパラメータを追加します。ドキュメンテーション・コメントを記述するときには、descriptionを複数行にわたって記述することもできます。このタグは、メソッド、コンストラクタ、またはクラスのドキュメンテーション・コメント内でのみ有効です。JavadocツールでのDocコメントの記述方法の@paramに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@param)を参照してください。 +.sp +\fBparameter\-name\fRは、メソッドまたはコンストラクタでのパラメータの名前か、クラス、メソッドまたはコンストラクタの型パラメータの名前になります。山カッコでこのパラメータ名を囲み、型パラメータを使用することを指定します。 +.sp +クラスの型パラメータの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @param <E> Type of element stored in a list\fR +\fB */\fR +\fBpublic interface List<E> extends Collection<E> {\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +メソッドの型パラメータの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @param string the string to be converted\fR +\fB * @param type the type to convert the string to\fR +\fB * @param <T> the type of the element\fR +\fB * @param <V> the value of the element\fR +\fB */\fR +\fB<T, V extends T> V convert(String string, Class<T> type) {\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +@return \fIdescription\fR +.RS 4 +JDK 1\&.0で導入 +.sp +「戻り値」セクションを追加して、descriptionのテキストを書き込みます。このテキストでは、戻り値の型と、取り得る値の範囲について記述する必要があります。このタグは、メソッドのドキュメンテーション・コメントでのみ有効です。JavadocツールでのDocコメントの記述方法の@returnに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@return)を参照してください。 +.RE +.PP +@see \fIreference\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fI「関連項目」\fR見出しを追加して、referenceを指すリンク、またはテキスト・エントリを書き込みます。1つのドキュメンテーション・コメントには任意の数の\fB@see\fRタグを含めることができますが、それらはすべて同じ見出しの下にグループ化されます。\fB@see\fRタグには、3つのタイプの形式があります。この形式が最も一般的です。このタグは、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、またはフィールドで有効です。パッケージ、クラス、またはメンバーに対するインライン・リンクを文中に挿入する方法は、\fB{@link}\fRを参照してください。 +.sp +\fB形式1\fR。@see +\fBstring\fRタグ形式は、\fIstring\fRのテキスト・エントリを追加します。リンクは生成されません。stringは、書籍またはURLではアクセスできない情報の参照先です。\fBjavadoc\fRコマンドは、最初の文字として二重引用符(")を検索して、この形式を前述の形式と区別します。たとえば、\fB@see "The Java Programming Language"\fRは次のテキストを生成します。 +.sp +\fB関連項目\fR: +.sp +"The Java Programming Language" +.sp +\fB形式2\fR。\fB@see <a href="URL#value">label</a>\fRフォームは、\fBURL#value\fRで定義されているようにリンクを追加します。\fBURL#value\fRパラメータは、相対URLまたは絶対URLです。\fBjavadoc\fRコマンドは、最初の文字として「より小さい」記号(\fB<\fR)を検索して、この形式を他の形式と区別します。たとえば、\fB@see <a href="spec\&.html#section">Java Spec</a>\fRは、次のリンクを生成します: +.sp +\fB関連項目\fR: +.sp +Java Spec +.sp +\fB形式3\fR。\fB@see package\&.class#member label\fR形式は、表示テキスト・ラベルとともにリンクを追加します。このラベルは参照されているJava言語の指定された名前のドキュメントを指し示します。ラベルはオプションです。ラベルを省略した場合は、表示テキストのかわりに、名前が適切に短縮されて表示されます。\fB\-noqualifier\fRオプションを使用すると、この表示テキストからパッケージ名が全体的に削除されます。ラベルは、自動生成される表示テキストとは異なる表示テキストにする場合に使用します。「名前が表示される方法」を参照してください。 +.sp +Java SE 1\&.2だけは、ラベルではなく名前が\fB<code>\fR +HTMLタグ内に自動的に表示されます。Java SE 1\&.2\&.2からは、ラベルを使用するかしないかにかかわらず、\fB<code>\fRタグは常に表示テキストを囲む形で含まれます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackage\&.class#member\fRには、参照されている任意の有効なプログラム要素の名前を指定します。つまり、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、またはフィールドの名前です。ただし、メンバー名の前の文字は、シャープ記号(\fB#\fR)にする必要があります。classは、任意のトップレベルまたはネストされたクラスか、インタフェースを表します。memberは、任意のコンストラクタ、メソッドまたはフィールドを表します(ネストされたクラスまたはインタフェースではありません)。この名前が、ドキュメント化されるクラスに含まれている場合、\fBjavadoc\fRコマンドは、その名前へのリンクを作成します。外部参照クラスへのリンクを作成するには、\fB\-link\fRオプションを使用します。参照クラスに属していない名前のドキュメントを参照するには、他の2つの\fB@see\fRタグ形式のどちらかを使用します。「名前の指定」を参照してください。 +.sp +\fB注意:\fR +外部参照クラスは、コマンド行で\fBjavadoc\fRコマンドに渡されないクラスです。生成ドキュメント内で外部参照クラスにリンクしている箇所は、外部参照または外部リンクと呼ばれます。たとえば、\fBjava\&.awt package\fRに対してのみ\fBjavadoc\fRコマンドを実行した場合、\fBObject\fRなどの\fBjava\&.lang\fR内のすべてのクラスが外部参照クラスになります。\fB\-link\fRおよび\fB\-linkoffline\fRオプションを使用して、外部参照クラスへリンクします。外部参照クラスのソース・コメントは\fBjavadoc\fRコマンドの実行には使用できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBlabel\fRは、省略可能なテキストで、リンクのラベルとして表示されます。ラベルには空白を含めることができます。\fBlabel\fRを省略すると、\fBpackage\&.class\&.member\fRが、現在のクラスおよびパッケージに応じて適切に短縮されて表示されます。「名前が表示される方法」を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +空白文字が、\fBpackage\&.class#member\fRと\fBlabel\fRの間の区切り文字になります。カッコの内側の空白文字はラベルの先頭とは解釈されないため、メソッドのパラメータ間に空白文字を入れてもかまいません。 +.RE +.sp +この例では、\fB@see\fRタグ(\fBCharacter\fRクラス内)が、\fBString\fRクラスのequalsメソッドを参照しています。タグには、名前\fBString#equals(Object)\fRとラベル\fBequals\fRの両方の引数が含まれています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @see String#equals(Object) equals\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +標準ドックレットは、次のようなHTMLを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<dl>\fR +\fB<dt><b>See Also:</b>\fR +\fB<dd><a href="\&.\&./\&.\&./java/lang/String#equals(java\&.lang\&.Object)"><code>equals<code></a>\fR +\fB</dl>\fR + +.fi +.if n \{\ +.RE +.\} +前述のコードは、ブラウザに次のように表示され、ラベルは表示リンク・テキストになっています。 +.sp +\fB関連項目\fR: +.sp +equals +.RE +.PP +名前の指定 +.PP +この\fBpackage\&.class#member\fRという名前は、\fBjava\&.lang\&.String#toUpperCase()\fRのような完全修飾名にすることも、\fBString#toUpperCase()\fRや\fB#toUpperCase()\fRのような非完全修飾名にすることもできます。名前が完全修飾より短い場合は、\fBjavadoc\fRコマンドは、標準のJavaコンパイラの検索順序を使用して探します。「@seeタグの検索順序」を参照してください。名前は、メソッド引数の間など、カッコ内のスペースを含めることができます。部分的に修飾した短い名前を指定することの利点は、入力する文字数が減ることや、ソース・コードが読みやすくなることです。次のリストに様々な形式の名前を示します。ここで、\fBClass\fRにはクラスまたはインタフェースを、Typeにはクラス、インタフェース、配列、またはプリミティブを、methodにはメソッドまたはコンストラクタを、それぞれ指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\fBTypical forms for\fR\fR\fB\fB @see package\&.class#member\fR\fR\fB \fR +\fB\fBReferencing a member of the current class\fR\fR +\fB@see #field\fR +\fB@see #method(Type, Type,\&.\&.\&.)\fR +\fB@see #method(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see #constructor(Type, Type,\&.\&.\&.)\fR +\fB@see #constructor(Type argname, Type argname,\&.\&.\&.) \fR + +\fB\fBReferencing another class in the current or imported packages\fR\fR +\fB@see Class#field\fR +\fB@see Class#method(Type, Type,\&.\&.\&.)\fR +\fB@see Class#method(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see Class#constructor(Type, Type,\&.\&.\&.)\fR +\fB@see Class#constructor(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see Class\&.NestedClass\fR +\fB@see Class \fR + +\fB\fBReferencing an element in another package (fully qualified)\fR\fR +\fB@see package\&.Class#field\fR +\fB@see package\&.Class#method(Type, Type,\&.\&.\&.)\fR +\fB@see package\&.Class#method(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see package\&.Class#constructor(Type, Type,\&.\&.\&.)\fR +\fB@see package\&.Class#constructor(Type argname, Type argname,\&.\&.\&.)\fR +\fB@see package\&.Class\&.NestedClass\fR +\fB@see package\&.Class\fR +\fB@see package\fR + +.fi +.if n \{\ +.RE +.\} +.PP +前のリストに関するメモ: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +最初のタイプの形式(パッケージとクラスを省略)の場合、\fBjavadoc\fRコマンドは、現在のクラスの階層のみを検索します。つまり、現在のクラスかインタフェース、そのスーパークラスかスーパーインタフェース、またはその外側を囲んでいるクラスかインタフェースからメンバーを検索します(検索項目1\(en3)。現在のパッケージの他の部分や、他のパッケージは検索しません(検索項目4\(en5)。「@seeタグの検索順序」を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +メソッドまたはコンストラクタの入力時に、\fBgetValue\fRのようにカッコなしの名前を使用した場合、同じ名前のフィールドが存在していなければ、\fBjavadoc\fRコマンドはそのメソッドへのリンクを作成します。このメソッドがオーバーロードされている場合、\fBjavadoc\fRコマンドは、検索で最初に見つかったメソッドにリンクします。結果は前もって特定できません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ネストされたクラスは、すべての形式について、\fBouter\&.inner\fRとして指定する必要があります。単純に\fBinner\fRとはしないでください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +すでに述べたように、クラスとメンバーとの間の区切り文字としては、ドット(\fB\&.\fR)ではなくシャープ記号(\fB#\fR)を使用します。このように指定すると、\fBjavadoc\fRコマンドは、あいまいさを解決できます。ドットは、クラス、ネストされたクラス、パッケージ、およびサブパッケージを区切るためにも使用されるからです。ただし、\fBjavadoc\fRコマンドでは、あいまいさがなければドットは正しく解析されますが、警告は表示されます。 +.RE +.PP +@seeタグの検索順序 +.PP +\fBjavadoc\fRコマンドは、ソース・ファイル、パッケージ・ファイル、概要ファイルに表示される\fB@see\fRタグを処理します。後者の2つのファイルでは、完全修飾の名前を\fB@see\fRタグに指定する必要があります。ソース・ファイルでは、完全修飾の名前、または部分修飾の名前を指定できます。 +.PP +次に、\fB@see\fRタグの検索順序を示します。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +現在のクラスまたはインタフェース。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +外側を囲んでいるクラスとインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +スーパークラスとスーパーインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +現在のパッケージ。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 5.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 5." 4.2 +.\} +インポートされているパッケージ、クラス、およびインタフェース(\fBimport\fR文の順序に従って検索)。 +.RE +.PP +\fBjavadoc\fRコマンドは、各クラスについて項目1\-3を再帰的に適用しながら、一致する名前が見つかるまで検索を続けます。つまり、まず現在のクラスを検索し、次にその外側を囲んでいるクラスEを検索した後、Eのスーパークラスを検索してから、Eを囲んでいるクラスを検索します。項目4と5では、\fBjavadoc\fRコマンドが1つのパッケージ内のクラスまたはインタフェースを検索する順序は決まっていません(その順序は、個々のコンパイラによって異なります)。項目5では、\fBjavadoc\fRコマンドは、\fIjava\&.lang\fRを検索します。このパッケージは、すべてのプログラムに自動的にインポートされるからです。 +.PP +\fBjavadoc\fRコマンドは、完全修飾でないソース・ファイルで\fB@see\fRタグを見つけると、Javaコンパイラと同じ順序で指定された名前を検索します(ただし、\fBjavadoc\fRコマンドは、特定の名前空間のあいまいさを検出しません。これは、ソース・コードにこれらのエラーが存在していないことを前提としているためです)。この検索順序は、Java言語仕様で正式に定義されています。\fBjavadoc\fRコマンドは、関連するクラスとパッケージ、およびインポートされたクラスとパッケージのすべてからその名前を検索します。具体的には、次の順序で検索します。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +現在のクラスまたはインタフェース。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +外側を囲んでいるクラスとインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +スーパークラスとスーパーインタフェース(最も近いものから検索)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +現在のパッケージ。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 5.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 5." 4.2 +.\} +インポートされているパッケージ、クラス、およびインタフェース(\fBimport\fR文の順序に従って検索)。 +.RE +.PP +\fBjavadoc\fRコマンドは、必ずしもサブクラスを検索するとは限りません。また、実行中に他のパッケージのドキュメントが生成される場合でも、他のパッケージを検索しません。たとえば、\fB@see\fRタグが\fBjava\&.awt\&.event\&.KeyEvent\fRクラス内に含まれていて、\fBjava\&.awt package\fR内のある名前を参照していても、そのクラスがインポートしないかぎり\fBjavadoc\fRコマンドはそのパッケージを検索しません。 +.PP +名前が表示される方法 +.PP +\fBlabel\fRを省略すると、\fBpackage\&.class\&.member\fRが表示されます。一般に、これは現在のクラスおよびパッケージに応じて適切に短縮されます。短縮されるとは、\fBjavadoc\fRコマンドにより必要最小限の名前のみが表示されるということです。たとえば、\fBString\&.toUpperCase()\fRメソッドに、同じクラスのメンバーへの参照と他のクラスのメンバーへの参照が含まれている場合、クラス名が表示されるのは後者のケースのみです(次のリストを参照)。パッケージ名を全体的に削除するには、\fB\-noqualifier\fRオプションを使用します。 +.RS 4 +\fB参照のタイプ\fR: \fB@see\fRタグは同じクラス、同じパッケージのメンバーを参照します +.RE +.RS 4 +\fB例\fR: \fB@see String#toLowerCase()\fR +.RE +.RS 4 +\fB表示\fR: \fBtoLowerCase()\fR \- パッケージおよびクラス名を省略します +.RE +.RS 4 +.RE +.RS 4 +\fB参照のタイプ\fR: \fB@see\fRタグは別のクラス、同じパッケージのメンバーを参照します +.RE +.RS 4 +\fB例\fR: \fB@see Character#toLowerCase(char)\fR +.RE +.RS 4 +\fB表示\fR: \fBCharacter\&.toLowerCase(char)\fR \- パッケージ名を省略し、クラス名を含みます +.RE +.RS 4 +.RE +.RS 4 +\fB参照のタイプ\fR: \fB@see\fRタグは異なるクラス、異なるパッケージのメンバーを参照します +.RE +.RS 4 +\fB例\fR: \fB@see java\&.io\&.File#exists()\fR +.RE +.RS 4 +\fB表示\fR: \fBjava\&.io\&.File\&.exists()\fR \- パッケージおよびクラス名を含みます +.RE +.RS 4 +.RE +.PP +@seeタグの例 +.PP +右側のコメントは、\fB@see\fRタグが\fBjava\&.applet\&.Applet\fRなどの別のパッケージのクラス内にある場合に、名前がどのように表示されるかを示しています。JavadocツールでのDocコメントの記述方法の@seeに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@see)を参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB See also:\fR +\fB@see java\&.lang\&.String // String \fR +\fB@see java\&.lang\&.String The String class // The String class \fR +\fB@see String // String \fR +\fB@see String#equals(Object) // String\&.equals(Object) \fR +\fB@see String#equals // String\&.equals(java\&.lang\&.Object) \fR +\fB@see java\&.lang\&.Object#wait(long) // java\&.lang\&.Object\&.wait(long) \fR +\fB@see Character#MAX_RADIX // Character\&.MAX_RADIX \fR +\fB@see <a href="spec\&.html">Java Spec</a> // Java Spec \fR +\fB@see "The Java Programming Language" // "The Java Programming Language" \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB注意:\fR +\fB@se\fR\fBe\fRタグを拡張してドキュメント化されないクラスにリンクするには、\fB\-link\fRオプションを使用します。 +.PP +@serial \fIfield\-description\fR | include | exclude +.RS 4 +JDK 1\&.2で導入 +.sp +デフォルトの直列化可能フィールドのドキュメンテーション・コメントで使用します。クラスの直列化可能なフィールドおよびデータの文書化 +(http://docs\&.oracle\&.com/javase/8/docs/platform/serialization/spec/serial\-arch\&.html#5251)を参照してください +.sp +Oracleの直列化された形式の仕様にクラスを含める基準 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/serialized\-criteria\-137781\&.html)も参照してください +.sp +\fBfield\-description\fR(省略可能)では、フィールドの意味を説明し、取り得る値のリストを示す必要があります。必要な場合は、複数の行に渡って説明を記述できます。標準ドックレットは、この情報を、直列化された形式ページに追加します。相互参照ページを参照してください。 +.sp +クラスを直列化した後に直列化可能フィールドをクラスに追加した場合、主説明に、追加したバージョンを識別する文を追加する必要があります。 +.sp +\fBinclude\fRおよび\fBexclude\fR引数は、直列化された形式ページにクラスまたはパッケージを含めるか除外するかを示します。次のように機能します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSerializable\fRを実装しているpublicまたはprotectedクラスは、そのクラス(またはそのクラスが属するパッケージ)が\fB@serial exclude\fRタグでマークされていないかぎり、含められます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSerializable\fRを実装しているprivateまたはpackage\-privateクラスは、そのクラス(またはそのクラスが属するパッケージ)が\fB@serial include\fRタグでマークされていないかぎり、除外されます。 +.RE +.sp +たとえば、\fBjavax\&.swing\fRパッケージはpackage\&.htmlまたはpackage\-info\&.java内で\fB@serial\fR +\fBexclude\fRタグでマークされています。publicクラス\fBjava\&.security\&.BasicPermission\fRは\fB@serial exclude\fRタグでマークされています。package\-privateクラス\fBjava\&.util\&.PropertyPermissionCollection\fRは\fB@serial include\fRタグでマークされています。 +.sp +クラス・レベルの\fB@serial\fRタグはパッケージ・レベルの\fB@serial\fRタグをオーバーライドします。 +.RE +.PP +@serialData \fIdata\-description\fR +.RS 4 +JDK 1\&.2で導入 +.sp +データの説明値を使用して、直列化された形式でのデータの型と順序をドキュメント化します。このデータには、\fBwriteObject\fRメソッドによって書き込まれる省略可能なデータ、および\fBExternalizable\&.writeExternal\fRメソッドによって書き込まれるすべてのデータ(ベース・クラスを含む)が含まれます。 +.sp +\fB@serialData\fRタグは、\fBwriteObject\fR、\fBreadObject\fR、\fBwriteExternal\fR、\fBreadExternal\fR、\fBwriteReplace\fRおよび\fBreadResolve\fRメソッドのドキュメンテーション・コメントで使用できます。 +.RE +.PP +@serialField \fIfield\-name\fR \fIfield\-type\fR \fIfield\-description\fR +.RS 4 +JDK 1\&.2で導入 +.sp +\fBSerializable\fRクラスの\fBserialPersistentFields\fRメンバーの\fBObjectStreamField\fRコンポーネントをドキュメント化します。\fBObjectStreamField\fRコンポーネントごとに1つの\fB@serialField\fRタグを使用します。 +.RE +.PP +@since \fIsince\-text\fR +.RS 4 +JDK 1\&.1で導入 +.sp +生成ドキュメントに、指定された\fBsince\-text\fRの値の\fI「導入されたバージョン」\fR見出しを追加します。このテキストには、特別な内部構造はありません。このタグは、すべてのドキュメンテーション・コメント、つまり概要、パッケージ、クラス、インタフェース、コンストラクタ、メソッド、またはフィールドで有効です。このタグは、特定の変更または機能が、\fBsince\-text\fRの値によって指定されたソフトウェア・リリース以降、存在していることを意味します。たとえば、\fB@since 1\&.5\fRです。 +.sp +Javaプラットフォームのソース・コードの場合、\fB@since\fRタグは、JavaプラットフォームAPI仕様のバージョンを示します。ソース・コードがリファレンス実装に追加された時期を示すとは限りません。複数の\fB@since\fRタグを使用でき、複数の\fB@author\fRタグのように扱われます。プログラム要素が複数のAPIで使用される場合、複数のタグを使用できます。 +.RE +.PP +@throws \fIclass\-name\fR \fIdescription\fR +.RS 4 +JDK 1\&.2で導入 +.sp +\fB@exception\fRタグと同じ動作をします。JavadocツールでのDocコメントの記述方法の@throwsに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@exception)を参照してください +.sp +\fB@throws\fRタグは、生成ドキュメントに\fIThrows\fR小見出しを追加して、\fBclass\-name\fRおよび\fBdescription\fRテキストを書き込みます。\fIclass\-name\fRは、そのメソッドからスローされる可能性のある例外の名前です。このタグは、メソッド、コンストラクタのドキュメンテーション・コメント内でのみ有効です。このクラスが完全指定の名前で記述されていない場合、\fBjavadoc\fRコマンドは、検索順序に従ってクラスを探します。複数の\fB@throws\fRタグを、同じ例外または違う例外の指定したドキュメンテーション・コメントで使用できます。「@seeタグの検索順序」を参照してください。 +.sp +すべてのチェック済例外がドキュメント化されるようにするために、\fB@throws\fRタグがthrows節内の例外用に存在しない場合は、\fB@throws\fRタグでドキュメント化されたかのように、\fBjavadoc\fRコマンドによって例外がHTML出力に説明なしで追加されます。 +.sp +オーバーライドされるメソッド内で例外が明示的に宣言されている場合のみ、\fB@throws\fRのドキュメントがそのメソッドからサブクラスにコピーされます。インタフェース・メソッドから実装メソッドにコピーされる場合も同様です。\fB{@inheritDoc}\fRタグを使用して、\fB@throws\fRタグがドキュメンテーションを継承するように強制できます。 +.RE +.PP +{@value \fIpackage\&.class#field\fR} +.RS 4 +JDK 1\&.4で導入 +.sp +定数の値を表示します。\fB{@value}\fRタグが静的フィールドのドキュメンテーション・コメントで引数なしで使用されている場合、その定数の値を表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * The value of this constant is {@value}\&.\fR +\fB */\fR +\fBpublic static final String SCRIPT_START = "<script>"\fR + +.fi +.if n \{\ +.RE +.\} +任意のドキュメンテーション・コメント内で引数\fBpackage\&.class#field\fRありで使用された場合、\fB{@value}\fRタグは指定された定数の値を表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * Evaluates the script starting with {@value #SCRIPT_START}\&.\fR +\fB */\fR +\fBpublic String evalScript(String script) {}\fR + +.fi +.if n \{\ +.RE +.\} +引数\fBpackage\&.class#field\fRは、\fB@see\fRタグ引数と同一の形式になります。ただし、メンバーは静的フィールドである必要があります。 +.sp +これらの定数の値は「定数フィールド値」 +(http://docs\&.oracle\&.com/javase/8/docs/api/constant\-values\&.html)にも表示されます +.RE +.PP +@version \fIversion\-text\fR +.RS 4 +JDK 1\&.0で導入 +.sp +\fB\-version\fRオプションが使用されている場合、生成ドキュメントに\fI「バージョン」\fR小見出しを追加して、指定された\fBversion\-text\fRの値を書き込みます。このタグはこのコードが含まれるソフトウェアの現在のリリース番号を保持するためのものであるのに対し、\fB@since\fRタグは、このコードが導入されたリリース番号を保持します。\fBversion\-text\fRの値には、特別な内部構造はありません。JavadocツールでのDocコメントの記述方法の@versionに関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#@version)を参照してください +.sp +1つのドキュメンテーション・コメントに複数の\fB@version\fRタグを含めることができます。必要に応じて、1つの\fB@version\fRタグに1つのリリース番号を指定することも、複数のリリース番号を指定することもできます。前者の場合は、\fBjavadoc\fRコマンドによって名前と名前の間にカンマ(,)と空白文字が挿入されます。後者の場合は、テキスト全体が解析されることなく、生成ドキュメントにコピーされます。したがって、カンマではなく、各言語に対応した名前区切り文字を使用する必要があるときに、1行に複数の名前を指定できます。 +.RE +.SH "タグを使用できる場所" +.PP +ここでは、タグを使用できる場所について説明します。次のタグがすべてのドキュメンテーション・コメントで使用できます。\fB@see\fR、\fB@since\fR、\fB@deprecated\fR、\fB{@link}\fR、\fB{@linkplain}\fRおよび\fB{@docroot}\fR。 +.SS "概要タグ" +.PP +概要タグは、概要ページのドキュメンテーション・コメントで使用できるタグです(このドキュメンテーション・コメントは、通常overview\&.htmlという名前のソース・ファイル内にあります)。他のドキュメンテーション・コメントの場合と同様に、これらのタグは、主説明の後で使用する必要があります。 +.PP +\fB注意:\fR +Java SE 1\&.2では、概要ドキュメント内の\fB{@link}\fRタグにbugがあります。テキストは正しく表示されますが、リンクが設定されません。現在のところ、\fB{@docRoot}\fRタグは、概要ドキュメント内では機能しません。 +.PP +概要タグは、次のとおりです。 +.PP +@see reference || @since since\-text || @serialField field\-name field\-type field\-description || @author name\-text || @version version\-text || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.SS "パッケージ・タグ" +.PP +パッケージ・タグは、パッケージのドキュメンテーション・コメントで使用できるタグで、ドキュメンテーション・コメントはpackage\&.htmlまたはpackage\-info\&.javaという名前のソース・ファイル内にあります。ここで使用できる\fB@serial\fRタグは、\fBinclude\fRまたは\fBexclude\fR引数を指定したもののみです。 +.PP +パッケージ・タグは、次のとおりです。 +.PP +@see reference || @since since\-text || @serial field\-description | include | exclude || @author name\-text || @version version\-text || {@linkplain package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.SS "クラスおよびインタフェース・タグ" +.PP +次に、クラスまたはインタフェースのドキュメンテーション・コメントで使用できるタグを示します。\fB@serial\fRタグは、\fBinclude\fRまたは\fBexclude\fR引数を指定して、クラスまたはインタフェースのドキュメンテーション内でのみ使用できます。 +.PP +@see reference || @since since\-text || @deprecated deprecated\-text || @serial field\-description | include | exclude || @author name\-text || @version version\-text || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.PP +クラス・コメントの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * A class representing a window on the screen\&.\fR +\fB * For example:\fR +\fB * <pre>\fR +\fB * Window win = new Window(parent);\fR +\fB * win\&.show();\fR +\fB * </pre>\fR +\fB *\fR +\fB * @author Sami Shaio\fR +\fB * @version 1\&.13, 06/08/06\fR +\fB * @see java\&.awt\&.BaseWindow\fR +\fB * @see java\&.awt\&.Button\fR +\fB */\fR +\fBclass Window extends BaseWindow {\fR +\fB \&.\&.\&.\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SS "フィールド・タグ" +.PP +これらのタグは、フィールドに表示できます。 +.PP +@see reference || @since since\-text || @deprecated deprecated\-text || @serial field\-description | include | exclude || @serialField field\-name field\-type field\-description || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || {@value package\&.class#field} +.PP +フィールド・コメントの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB /**\fR +\fB * The X\-coordinate of the component\&.\fR +\fB *\fR +\fB * @see #getLocation()\fR +\fB */\fR +\fB int x = 1263732;\fR + +.fi +.if n \{\ +.RE +.\} +.SS "コンストラクタとメソッド・タグ" +.PP +次に、コンストラクタまたはメソッドのドキュメンテーション・コメントで使用できるタグを示します。ただし、\fB@return\fRはコンストラクタでは使用できず、 +\fB{@inheritDoc}\fRには制限があります。 +.PP +@see reference || @since since\-text || @deprecated deprecated\-text || @param parameter\-name description || @return description || @throws class\-name description || @exception class\-name description || @serialData data\-description || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@inheritDoc} || {@docRoot} +.PP +\fB注意:\fR +\fB@serialData\fRタグは、\fBwriteObject\fR、\fBreadObject\fR、\fBwriteExternal\fR、\fBreadExternal\fR、\fBwriteReplace\fRおよび\fBreadResolve\fRメソッドのドキュメンテーション・コメントでのみ使用できます。 +.PP +メソッド・コメントの例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * Returns the character at the specified index\&. An index \fR +\fB * ranges from <code>0</code> to <code>length() \- 1</code>\fR +\fB *\fR +\fB * @param index the index of the desired character\&.\fR +\fB * @return the desired character\&.\fR +\fB * @exception StringIndexOutOfRangeException \fR +\fB * if the index is not in the range <code>0</code> \fR +\fB * to <code>length()\-1</code>\fR +\fB * @see java\&.lang\&.Character#charValue()\fR +\fB */\fR +\fB public char charAt(int index) {\fR +\fB \&.\&.\&.\fR +\fB }\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\fBjavadoc\fRコマンドは、ドックレットを使用して出力を決定します。\fBjavadoc\fRコマンドは、\fB\-doclet\fRオプションでカスタム・ドックレットが指定されている場合以外は、デフォルトの標準ドックレットを使用します。\fBjavadoc\fRコマンドには、任意のドックレットとともに使用できるコマンド行オプションがあります。これらのオプションについては、Javadocオプションで説明します。標準ドックレットでは、この他に、いくつかの追加のコマンド行オプションが提供されます。これらのオプションについては、標準ドックレットのオプションで説明します。どのオプション名も、大文字と小文字が区別されません。ただし、オプションの引数では、大文字と小文字が区別されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javadocオプションも参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +標準ドックレットのオプションも参照してください +.RE +.PP +オプションは次のとおりです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-1\&.1 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-author +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-bootclasspath classpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-bottom text +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-breakiterator +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-charset name +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-classpath classpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-d directory +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-docencoding name +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-docfilesubdirs +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-doclet class +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-docletpath classpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-doctitle title +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-encoding +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-exclude packagename1:packagename2:\&.\&.\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-excludedocfilessubdir name1:name2 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-extdirs dirist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-footer footer +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-group groupheading packagepattern:packagepattern +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-header header +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-help +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-helpfile path\efilename +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-Jflag +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-javafx +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-keywords +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-link extdocURL +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-linkoffline extdocURL packagelistLoc +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-linksource +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-locale language_country_variant +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nocomment +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nodeprecated +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nodeprecatedlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nohelp +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-noindex +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nonavbar +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-noqualifier all | packagename1:packagename2\&.\&.\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-nosince +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-notimestamp +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-notree +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-overview path/filename +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-package +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-private +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-protected +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-public +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-quiet +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-serialwarn +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-source release +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-sourcepath sourcepathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-sourcetab tablength +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-splitindex +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-stylesheet path/filename +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-tag tagname:Xaoptcmf:"taghead" +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-subpackages package1:package2:\&.\&.\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-taglet class +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-tagletpath tagletpathlist +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-title title +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-top +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-use +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-verbose +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-version +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-windowtitle title +.RE +.PP +次のオプションは、すべてのドックレットに使用可能なコアのJavadocオプションです。標準ドックレットでは、ドックレットの他の部分を提供します。\fB\-bootclasspath\fR、\fB\-breakiterator\fR、\fB\-classpath\fR、\fB\-doclet\fR、\fB\-docletpath\fR、\fB\-encoding\fR、\-\fBexclude\fR、\fB\-extdirs\fR、\fB\-help\fR、\fB\-locale\fR、\fB\-\fR\fBoverview\fR、\fB\-package\fR、\fB\-private\fR、\fB\-protected\fR、\fB\-public\fR、\fB\-quiet\fR、\fB\-source\fR、\fB\-sourcepath\fR、\fB\-subpackages\fRおよび\fB\-verbose\fR。 +.SS "Javadocオプション" +.PP +\-overview \fIpath/filename \fR +.RS 4 + +\fBjavadoc\fRコマンドに対して、\fIpath/filename \fRで指定されたソース・ファイルから概要ドキュメント用のテキストを取得し、そのテキストを概要ページ(overview\-summary\&.html)に配置するように指定します。\fIpath/filename\fRは、現在のディレクトリからの相対パスです。 +.sp +\fBfilename\fRの値で任意の名前を使用し、pathで任意の配置先を指定できますが、通常はoverview\&.htmlという名前を付け、ソース・ツリー内の最上位パッケージ・ディレクトリを含むディレクトリに配置します。この場所に配置すると、パッケージをドキュメント化するときにpathを指定する必要がなくなります。これは、\fB\-sourcepath\fRオプションによってこのファイルが指し示されるからです。 +.sp +たとえば、\fBjava\&.lang\fRパッケージのソース・ツリーが/src/classes/java/lang/の場合、概要ファイルを/src/classes/overview\&.htmlに配置できます +.sp +実際の例を参照してください。 +.sp +\fIpath/filename\fRで指定するファイルについては、概要コメント・ファイルを参照してください。 +.sp +「概要」ページが作成されるのは、\fBjavadoc\fRコマンドに複数のパッケージ名を渡した場合のみです。詳細は、HTMLフレームを参照してください。「概要」ページのタイトルは、\fB\-doctitle\fRによって設定されます。 +.RE +.PP +\-Xdoclint:(all|none|[\-]\fI<group>\fR) +.RS 4 +不正な参照、アクセシビリティの欠落およびJavadocコメントの不足の警告をレポートし、無効なJavadoc構文および不足しているHTMLタグのエラーをレポートします。 +.sp +このオプションにより、\fBjavadoc\fRコマンドは生成された出力に含まれるすべてのドキュメント・コメントをチェックします。通常どおり、標準オプション\fB\-public\fR、\fB\-protected\fR、\fB\-package\fRおよび\fB\-private\fRで生成された出力に含む項目を選択できます。 +.sp +\fB\-Xdoclint\fRが有効になっている場合は、\fBjavac\fRコマンドと同様にメッセージで問題がレポートされます。\fBjavadoc\fRコマンドは、メッセージ、ソース・ファイルのコピーおよびエラーが検出された正確な位置を指すキャレットを出力します。メッセージは、重大度、および生成されたドキュメントがバリデータを使用して実行された場合にエラーが発生する可能性に応じて、警告またはエラーになります。たとえば、不正な参照またはJavadocコメントの欠落は、\fBjavadoc\fRコマンドが無効なHTMLを生成する原因にならないため、これらの問題は警告としてレポートされます。構文エラーまたはHTML終了タグの欠落は、\fBjavadoc\fRコマンドが無効なHTMLを生成する原因になるため、これらの問題はエラーとしてレポートされます。 +.sp +デフォルトでは、\fB\-Xdoclint\fRオプションは有効になっています。オプション\fB\-Xdoclint:none\fRで無効にします。 +.sp +\fB\-Xdoclint\fRオプションでレポートされる内容は次のオプションで変更します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint none\fR: +\fB\-Xdoclint\fRオプションを無効にします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint \fR\fIgroup\fR: +\fIgroup\fRチェックを有効にします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint all\fR: すべてのチェック・グループを有効にします。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-Xdoclint all,\fR\fI\-group\fR: +\fIgroup\fRチェック以外のすべてを有効にします。 +.RE +.sp +変数\fIgroup\fRは次のいずれかの値を持ちます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBaccessibility\fR: アクセシビリティ・チェッカで検出する問題をチェックします(たとえば、\fB<table>\fRタグで指定されるno captionまたはsummary属性)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBhtml\fR: インライン要素へのブロック要素の挿入や終了タグを必要とする要素を終了しないなど、上位レベルHTMLの問題を検出します。ルールは、HTML 4\&.01仕様から導出されます。このタイプのチェックは、\fBjavadoc\fRコマンドを有効にして、ブラウザが受け入れる可能性のあるHTMLの問題を検出します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmissing\fR: 欠落しているJavadocコメントまたはタグをチェックします(たとえば、欠落しているコメントやクラス、または欠落している\fB@return\fRタグやメソッド上の同様のタグ)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBreference\fR: JavadocタグのJava API要素の参照に関連する問題をチェックします(たとえば、\fB@see\fRで見つからない項目、または\fB@param\fRの後の不正な名前)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBsyntax\fR: エスケープされていない山カッコ(\fB<\fRおよび\fB>\fR)やアンパサンド(\fB&\fR)、無効なJavadocタグなどの下位レベルの問題を確認します。 +.RE +.sp +\fB\-Xdoclint\fRオプションを複数回指定して、複数のカテゴリのエラーと警告をチェックするオプションを有効にできます。または、前のオプションを使用して、複数のエラーおよび警告カテゴリを指定できます。たとえば、次のコマンドのいずれかを使用して、\fIfilename\fRファイル内のHTML、構文およびアクセシビリティの問題をチェックします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-Xdoclint:html \-Xdoclint:syntax \-Xdoclint:accessibility \fR\fB\fIfilename\fR\fR +\fBjavadoc \-Xdoclint:html,syntax,accessibility \fR\fB\fIfilename\fR\fR + +.fi +.if n \{\ +.RE +.\} +\fB注意:\fR +\fBjavadoc\fRコマンドでは、これらのチェックの完全性は保証されません。具体的には、完全なHTMLコンプライアンス・チェッカではありません。\-\fBXdoclint\fRオプションの目的は、\fBjavadoc\fRコマンドを有効にして一般的なエラーの大半をレポートすることです。 +.sp +\fBjavadoc\fRコマンドは、無効な入力の修正を試行せず、レポートのみ行います。 +.RE +.PP +\-public +.RS 4 +publicクラスおよびメンバーのみ表示します。 +.RE +.PP +\-protected +.RS 4 +protectedおよびpublicのクラスとメンバーのみを表示します。これがデフォルトです。 +.RE +.PP +\-package +.RS 4 +package、protected、およびpublicのクラスとメンバーのみ表示します。 +.RE +.PP +\-private +.RS 4 +すべてのクラスとメンバーを表示します。 +.RE +.PP +\-help +.RS 4 +オンライン・ヘルプを表示します。\fBjavadoc\fRと\fBドックレット\fRのコマンド行オプションがリストされます。 +.RE +.PP +\-doclet \fIclass\fR +.RS 4 +ドキュメントの生成に使用するドックレットを起動するためのクラス・ファイルを指定します。完全修飾名を使用します。このドックレットにより、出力の内容と形式が定義されます。\fB\-doclet\fRオプションが使用されていない場合、\fBjavadoc\fRコマンドは、標準ドックレットを使用してデフォルトのHTML形式を生成します。このクラスには\fBstart(Root)\fRメソッドが含まれている必要があります。この起動クラスへのパスは\fB\-docletpath\fRオプションによって定義されます。ドックレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html)を参照してください +.RE +.PP +\-docletpath \fIclasspathlist\fR +.RS 4 +\fB\-doclet\fRオプションで指定されたドックレット開始クラス・ファイル、およびそのクラスが依存するすべてのJARファイルへのパスを指定します。開始クラス・ファイルがJARファイル内にある場合、このオプションでJARファイルへのパスを指定します。絶対パスまたは現在のディレクトリからの相対パスを指定できます。\fBclasspathlist\fRに複数のパスやJARファイルが含まれる場合には、それらをSolarisの場合はコロン(:)で、Windowsの場合はセミコロン(;)でそれぞれ区切ります。目的のドックレット開始クラスがすでに検索パス内にある場合は、このオプションは不要です。ドックレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html)を参照してください +.RE +.PP +\-1\&.1 +.RS 4 +Javadoc 1\&.4から削除され、代替はありません。このオプションは、Javadoc 1\&.1によって生成されるのと同じ外見と機能を持つドキュメントを作成するためのものでした(ネストされたクラスはサポートされていません)。このオプションが必要な場合は、Javadoc 1\&.2または1\&.3をかわりに使用してください。 +.RE +.PP +\-source \fIrelease\fR +.RS 4 +受け付けるソース・コードのリリースを指定します。\fBrelease\fRパラメータには次の値を指定できます。\fBjavac\fRコマンドでコードをコンパイルするときに使用する値に対応する\fBリリース\fRの値を使用します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBリリース値: 1\&.5\fR。\fBjavadoc\fRコマンドは、JDK 1\&.5で導入された総称および他の言語機能を含むコードを受け付けます。\fB\-source\fRオプションが使用されなかった場合のコンパイラのデフォルト動作は、1\&.5のものになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBリリース値: 1\&.4\fR。\fBjavadoc\fRコマンドは、JDK 1\&.4で導入されたアサーションを含むコードを受け付けます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBリリース値: 1\&.3\fR。\fBjavadoc\fRコマンドは、JDK 1\&.3以降に導入されたアサーション、総称、または他の言語機能をサポートしません。 +.RE +.RE +.PP +\-sourcepath \fIsourcepathlist\fR +.RS 4 +パッケージ名または\fB\-subpackages\fRオプションを\fBjavadoc\fRコマンドに渡すときに、ソース・ファイルを見つけるための検索パスを指定します。 +.sp +複数のパスはコロン(:)で区切ります。 +.sp +\fBjavadoc\fRコマンドは、指定されたパス以下のすべてのサブディレクトリを検索します。このオプションを使用して、ドキュメント化されるソース・ファイルの位置のみでなく、それ自体はドキュメント化されないがドキュメント化されるソース・ファイルから継承されたコメントを持つソース・ファイルの位置も確認できます。 +.sp +\fB\-sourcepath\fRオプションを使用できるのは、\fBjavadoc\fRコマンドにパッケージ名を渡す場合のみです。\fBjavadoc\fRコマンドに渡されるソース・ファイルは検索されません。ソース・ファイルを特定するには、そのディレクトリに移動するか、「1つ以上のクラスのドキュメント化」に示すように各ファイルの前にパスを含めます。\fB\-sourcepath\fRが省略された場合、\fBjavadoc\fRコマンドは、クラス・パスを使用してソース・ファイルを検索します(\fB\-classpath\fRを参照)。デフォルトの\fB\-sourcepath\fRは、クラス・パスの値です。\fB\-classpath\fRを省略してパッケージ名を\fBjavadoc\fRコマンドに渡すと、\fBjavadoc\fRコマンドは現在のディレクトリ(およびそのサブディレクトリ)からソース・ファイルを検索します。 +.sp +\fBsourcepathlist\fRには、ドキュメント化するパッケージのソース・ツリーのルート・ディレクトリを設定します。 +.sp +たとえば、\fBcom\&.mypackage\fRという名前のパッケージをドキュメント化する場合に、そのソース・ファイルが/home/user/src/com/mypackage/*\&.javaにあるとします。ソース・パスをcom\emypackageが含まれるディレクトリ/home/user/srcに指定してから、次のように、パッケージ名を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user/src/ com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +ソース・パスの値とパッケージ名を連結して、ドットをスラッシュ(/)に変更すると、次のように、パッケージのフルパスになります。 +.sp +/home/user/src/com/mypackage +.sp +2つのソース・パスを設定するには、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user1/src:/home/user2/src com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-classpath \fIclasspathlist\fR +.RS 4 +\fBjavadoc\fRコマンドが参照クラスの検索を行うときに使用するパスを指定します。参照クラスとは、ドキュメント化されるクラスと、それらのクラスによって参照されるすべてのクラスのことです。 +.sp +複数のパスはコロン(:)で区切ります。 +.sp +\fBjavadoc\fRコマンドは、指定されたパス以下のすべてのサブディレクトリを検索します。\fBclasspathlist\fRの値を指定するときは、クラス・パスのドキュメントにある指示に従ってください。 +.sp +\fB\-sourcepath\fRが省略された場合、\fBjavadoc\fRコマンドは\fB\-classpath\fRを使用して、ソース・ファイルおよびクラス・ファイルを検索します(後方互換性のため)。ソース・ファイルとクラス・ファイルを別々のパスから検索する必要がある場合は、\fB\-sourcepath\fRと\fB\-classpath\fRの両方を使用します。 +.sp +たとえば、\fBcom\&.mypackage\fRをドキュメント化する場合に、そのソース・ファイルがディレクトリ/home/user/src/com/mypackageにあり、このパッケージが/home/user/lib内のライブラリに依存しているとき、次のように指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user/lib \-classpath /home/user/src com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +他のツールと同様に、\fB\-classpath\fRが指定されていない場合、\fBCLASSPATH\fR環境変数が設定されていれば、\fBjavadoc\fRコマンドはその環境変数を使用します。どちらも設定されていない場合、\fBjavadoc\fRコマンドは現在のディレクトリからクラスを検索します。 +.sp +\fBjavadoc\fRコマンドが\fB\-classpath\fRを使用してユーザー・クラスを検索する方法についての、拡張機能クラスやブートストラップ・クラスに関連した詳細は、クラスの検索方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html)を参照してください。 +.sp +*のベース名を含むクラス・パス要素は、\fB\&.jar\fRまたは\fB\&.JAR\fRを拡張子に持つディレクトリ内のすべてのファイルのリストを指定するのと同等とみなされます。 +.sp +たとえば、ディレクトリ\fBmydir\fRに\fBa\&.jar\fRと\fBb\&.JA\fRRが含まれている場合、クラス・パス要素\fBfoo/*\fRは\fBA\&.jar:b\&.JAR\fRに展開されますが、JARファイルの順番は未指定となります。非表示のファイルを含む、指定したディレクトリ内のすべてのJARファイルがリストに含まれます。*からなるクラス・パス・エントリは、現在のディレクトリ内のすべてのJARファイルのリストに展開されます。\fBCLASSPATH\fR環境変数も同様に展開されます。クラス・パスのワイルドカードの展開は、Java Virtual Machine (JVM)の開始前に行われます。Javaプログラムは、System\&.getenv(\fB"CLASSPATH"\fR)の呼び出しによってなど、環境を問い合せる場合を除き、展開されていないワイルドカードを参照しません。 +.RE +.PP +\-subpackages \fIpackage1:package2:\&.\&.\&.\fR +.RS 4 +ソース・ファイルから指定されたパッケージおよびそのサブパッケージ内に再帰的にドキュメントを生成します。このオプションは、ソース・コードに新しいサブパッケージを追加する際に便利です。新しいサブパッケージが自動的に組み込まれるからです。各package引数は、任意の最上位サブパッケージ(\fBjava\fRなど)または完全修飾パッケージ(\fBjavax\&.swing\fRなど)になります。ソース・ファイルを含める必要はありません。引数は、すべてのオペレーティング・システムで、コロンで区切られます。ワイルドカードは使用できません。パッケージの検索場所を指定するには、\fB\-sourcepath\fRを使用します。このオプションでは、ソース・ツリー内に存在するがパッケージに含まれないソース・ファイルを処理しません。ソース・ファイルの処理を参照してください。 +.sp +たとえば、次のコマンドは、\fBjava\fRおよび\fBjavax\&.swing\fRという名前のパッケージとこれらのサブパッケージ全部のドキュメントを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d docs \-sourcepath /home/user/src \-subpackages java:javax\&.swing \fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-exclude \fIpackagename1:packagename2:\&.\&.\&.\fR +.RS 4 +指定されたパッケージとそのサブパッケージを\fB\-subpackages\fRによって作成されたリストから無条件に除外します。過去または将来の\fB\-subpackages\fRオプションの指定によって組み込まれるパッケージも除外の対象となります。 +.sp +次の例では、\fBjava\&.io\fR、\fBjava\&.util\fR、\fBjava\&.math\fRなどは組み込まれますが、\fBjava\&.net\fRと\fBjava\&.lang\fRをルートに持つパッケージは除外されます。\fBjava\&.lang\fRのサブパッケージである\fBjava\&.lang\&.ref\fRが除外される点に注意してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /home/user/src \-subpackages java \-exclude \fR +\fB java\&.net:java\&.lang\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-bootclasspath \fIclasspathlist\fR +.RS 4 +ブート・クラスが存在するパスを指定します。ブート・クラスとは、通常、Javaプラットフォーム・クラスのことです。\fBbootclasspath\fRは、\fBjavadoc\fRコマンドがソース・ファイルとクラス・ファイルを探すときに使用する検索パスの一部です。詳細は、クラスの検出方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html)を参照してください +.sp +\fBclasspathlist\fRパラメータ内のディレクトリは、セミコロン(;)で区切る(Windowsの場合)か、コロン(:)で区切ります(Oracle Solarisの場合)。 +.RE +.PP +\-extdirs \fIdirist\fR +.RS 4 +拡張機能クラスが存在するディレクトリを指定します。拡張機能クラスとは、Java拡張機能機構を使用するすべてのクラスです。\fBextdirs\fRオプションは、\fBjavadoc\fRコマンドがソース・ファイルとクラス・ファイルを探すときに使用する検索パスの一部です。詳細は、\fB\-classpath\fRオプションを参照してください。\fBdirlist\fR内のディレクトリは、セミコロン(;)で区切る(Windowsの場合)か、コロン(:)で区切ります(Oracle Solarisの場合)。 +.RE +.PP +\-verbose +.RS 4 +\fBjavadoc\fRコマンドの実行中に詳細なメッセージを表示します。\fBverbose\fRオプションを指定しないと、ソース・ファイルのロード時、ドキュメントの生成時(ソース・ファイルごとに1つのメッセージ)、およびソート時にメッセージが表示されます。verboseオプションを指定すると、各Javaソース・ファイルの解析に要した時間(ミリ秒単位)を示す追加のメッセージが表示されます。 +.RE +.PP +\-quiet +.RS 4 +メッセージを抑制し、警告とエラーのみが表示されるようにして、これらを確認しやすくします。\fBversion\fR文字列も抑止します。 +.RE +.PP +\-breakiterator +.RS 4 +英語の場合、パッケージ、クラスまたはメンバーの主説明の最初の文の終わりを判断する際に、\fBjava\&.text\&.BreakIterator\fRの国際化された文境界を使用します。他のすべてのロケールは、英語言語というロケール固有のアルゴリズムではなく、すでに\fBBreakIterator\fRクラスを使用しています。最初の文は、パッケージ、クラス、またはメンバーのサマリーにコピーされ、アルファベット順の索引にコピーされます。JDK 1\&.2以降、\fBBreakIterator\fRクラスは、英語を除くすべての言語の文の終わりを判断するために、すでに使用されています。したがって、\fB\-breakiterator\fRオプションは、1\&.2以降では英文以外には効果がありません。英文には、次のような独自のデフォルトのアルゴリズムがあります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +英文のデフォルトの文区切りアルゴリズム。空白文字またはHTMLブロック・タグ(\fB<P>\fRなど)が続くピリオドで停止します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +breakiterator文区切りアルゴリズム。次の語が大文字で始まる場合、空白文字が続くピリオド、疑問符、または感嘆符で停止します。このアルゴリズムでは「The serial no\&. is valid」など、ほとんどの省略表記が処理されますが、「Mr\&. Smith」は処理されません。\fB\-breakiterator\fRオプションでは、HTMLタグや、数字または記号で始まる文では停止しません。HTMLタグに埋め込まれている場合でも、アルゴリズムは「\&.\&./filename」の最後のピリオドで停止します。 +.RE +.sp +Java SE 1\&.5では\fB\-breakiterator\fR警告メッセージが削除され、デフォルトの文区切りアルゴリズムは変更されていません。ソース・コードを変更せず、SE 1\&.4\&.xでの\fB\-breakiterator\fRオプションの警告を除去していない場合でも、何もする必要はありません。Java SE 1\&.5\&.0からは警告は消滅しています。 +.RE +.PP +\-locale \fIlanguage_country_variant\fR +.RS 4 +\fBjavadoc\fRコマンドがドキュメントを生成するときに使用するロケールを指定します。この引数は、\fBj\fR\fBava\&.util\&.Locale\fRドキュメントで説明しているように、\fBen_US\fR +(英語、米国)または\fBen_US_WIN\fR +(Windowsバリアント)などのロケールの名前です。 +.sp +\fB注意:\fR +\fB\-locale\fRオプションは、標準ドックレットが提供するすべてのオプション、またはその他の任意のドックレットが提供するすべてのオプションより前(左側)に指定する必要があります。そうしないと、ナビゲーション・バーが英語で表示されます。このコマンド行オプションのみ、指定する順序に依存します。標準ドックレットのオプションを参照してください。 +.sp +ロケールを指定すると、指定したロケールのリソース・ファイルが\fBjavadoc\fRコマンドによって選択されて、メッセージ(ナビゲーション・バー、リストと表の見出し、ヘルプ・ファイルの目次、stylesheet\&.cssのコメントなどの文字列)のために使用されます。また、アルファベット順にソートされるリストのソート順、および最初の文の終わりを判断するための文の区切り文字も、指定したロケールによって決まります。\fB\-locale\fRオプションは、ドキュメント化されるクラスのソース・ファイル内で指定されているドキュメンテーション・コメントのテキストのロケールを決定するものではありません。 +.RE +.PP +\-encoding +.RS 4 +ソース・ファイルのエンコーディングの名前(\fBEUCJIS/SJIS\fRなど)を指定します。このオプションが指定されていない場合は、プラットフォームのデフォルト・コンバータが使用されます。およびオプションも参照してください。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjavadoc\fRコマンドを実行するJava Runtime Environment (JRE)に、\fBflag\fRを直接渡します。たとえば、生成ドキュメントを処理するためにシステムで32MBのメモリーを確保しておく必要がある場合は、\fB\-Xmx\fRオプションを次のように呼び出します。\fBjavadoc \-J\-Xmx32m \-J\-Xms32m com\&.mypackage\fR。\fB\-Xms\fRは省略可能で、これは初期メモリーのサイズを設定するのみのオプションで、必要なメモリーの最小量がわかっている場合に便利です。 +.sp +\fBJ\fRと\fBflag\fRの間に空白文字はありません。 +.sp +使用している\fBjavadoc\fRコマンドのバージョンを確認するには\fB\-version\fRオプションを使用します。出力ストリームには標準ドックレットのバージョン番号が含まれます。Javadocコマンドの実行を参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-J\-version\fR +\fBjava version "1\&.7\&.0_09"\fR +\fBJava(TM) SE Runtime Environment (build 1\&.7\&.0_09\-b05)\fR +\fBJava HotSpot(TM) 64\-Bit Server VM (build 23\&.5\-b02, mixed mode)\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-javafx +.RS 4 +標準ドックレットに対してJavaFX拡張機能を使用して、HTMLドキュメントを生成します。生成されたドキュメントには、標準Javaドックレットで生成された他のサマリー・セクションに加えて「プロパティのサマリー」セクションが含まれています。リストされたプロパティは、各プロパティのgetterおよびsetterメソッドのセクションにリンクされます。 +.sp +getterおよびsetterメソッドに対して明示的に記載されているドキュメント・コメントがない場合、プロパティ・メソッドのドキュメント・コメントがこれらのメソッドに対して生成されたドキュメントに自動的にコピーされます。このオプションは、プロパティのデフォルト値を記述できる新しい\fB@defaultValue\fRタグも追加します。 +.sp +例: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-javafx MyClass\&.java \-d testdir\fR +.fi +.if n \{\ +.RE +.\} +.RE +.SS "標準ドックレットのオプション" +.PP +\-d \fIdirectory\fR +.RS 4 +\fBjavadoc\fRコマンドが生成されたHTMLファイルを保存する生成先ディレクトリを指定します。\fB\-d\fRオプションを省略すると、ファイルは現在のディレクトリに保存されます。\fBdirectory\fRの値には、絶対ディレクトリ、または現在の作業ディレクトリからの相対ディレクトリを指定できます。Java SE 1\&.4では、\fBjavadoc\fRコマンドを実行すると生成先ディレクトリが自動的に作成されます。 +.sp +たとえば、次の例では、\fBcom\&.mypackage\fRパッケージのドキュメントが生成され、その結果が/user/doc/ディレクトリに保存されます。\fBjavadoc \-d \fR\fB/user/doc/ \fR\fBcom\&.mypackage\fR +.RE +.PP +\-use +.RS 4 +ドキュメント化されるクラスおよびパッケージごとに1つの「使用」ページを組み込みます。このページには、その特定のクラスまたはパッケージのAPIを使用しているパッケージ、クラス、メソッド、コンストラクタ、およびフィールドが記述されます。たとえば、クラスCを例にとると、クラスCを使用しているものとしては、Cのサブクラス、Cとして宣言されているフィールド、Cを返すメソッド、および型Cのパラメータを持つメソッドとコンストラクタがあります。たとえば、\fBString\fR型用の「使用」ページを表示できます。\fBjava\&.awt\&.Font\fRクラスの\fBgetName\fRメソッドは\fBString\fR型を戻すので、\fBgetName\fRメソッドは\fBString\fRを使用し、\fBgetName\fRメソッドが\fBString\fR用の「使用」ページに表示されます。これは実装ではなくAPIの使用のみをドキュメント化します。メソッドがその実装で\fBString\fRを使用するが、引数として文字列を取らない、または文字列を返さない場合、それは\fBString\fRの使用とはみなされません。生成された「使用」ページにアクセスするには、クラスまたはパッケージに移動し、ナビゲーション・バーの\fBリンクの使用\fRをクリックします。 +.RE +.PP +\-version +.RS 4 +生成ドキュメントに、@versionのテキストを組み込みます。このテキストは、デフォルトでは省略されます。使用している\fBjavadoc\fRコマンドのバージョンを確認するには\fB\-J\-version\fRオプションを使用します。 +.RE +.PP +\-author +.RS 4 +生成ドキュメントに、\fB@author\fRのテキストを組み込みます。 +.RE +.PP +\-splitindex +.RS 4 +索引ファイルをアルファベットごとに複数のファイルに分割し、文字ごとに1つのファイルと、アルファベット以外の記号で始まる索引エントリ用に1つのファイルを作成します。 +.RE +.PP +\-windowtitle \fItitle\fR +.RS 4 +HTMLの\fB<title>\fRタグに配置するタイトルを指定します。\fBtitle\fRタグに指定したテキストは、ウィンドウのタイトルや、このページに対して作成されたブラウザのブックマーク(お気に入り)に表示されます。このタイトルにはHTMLタグを含めないでください。タイトルにHTMLタグが含まれていると、ブラウザがタグを正しく解釈できません。\fBtitle\fRタグ内の内部の二重引用符はエスケープ文字を使用してマークします。\fB\-windowtitle\fRオプションを省略すると、\fBjavadoc\fRコマンドは、\fB\-windowtitle\fRオプションのかわりに、\fB\-doctitle\fRオプションの値を使用します。たとえば、\fBjavadoc \-windowtitle "Java SE Platform" com\&.mypackage\fRです。 +.RE +.PP +\-doctitle \fItitle\fR +.RS 4 +概要サマリー・ファイルの最上部の近くに配置するタイトルを指定します。\fBtitle\fRタグに指定したテキストは中央揃えになり、レベル1の見出しとして、上部ナビゲーション・バーのすぐ下に置かれます。\fBtitle\fRタグにはHTMLタグおよび空白文字を含めることができますが、その場合、タイトルを引用符で囲む必要があります。\fBtitle\fRタグの内部で引用符を使用する場合は、エスケープする必要があります。たとえば、\fBjavadoc \-header "<b>Java Platform </b><br>v1\&.4" com\&.mypackage\&.\fRとなります。 +.RE +.PP +\-title \fItitle\fR +.RS 4 +すでに存在しません。Javadoc 1\&.2のベータ版にしか存在していませんでした。このオプションは、\fB\-doctitle\fRという名前に変更されました。名前を変更した理由は、このオプションが、ウィンドウのタイトルではなくドキュメントのタイトルを定義することを明確にするためです。 +.RE +.PP +\-header \fIheader\fR +.RS 4 +各出力ファイルの最上部に配置するヘッダー・テキストを指定します。ヘッダーは、ナビゲーション・バーの右上に配置されます。\fBheader\fRにはHTMLタグおよび空白文字を含めることができますが、その場合、\fBheader\fRを引用符で囲む必要があります。ヘッダー内部の引用符にはエスケープ文字を使用します。たとえば、\fBjavadoc \-header "<b>Java Platform </b><br>v1\&.4" com\&.mypackage\&.\fRとなります。 +.RE +.PP +\-footer \fIfooter\fR +.RS 4 +各出力ファイルの最下部に配置するフッター・テキストを指定します。\fIfooter\fRの値は、ナビゲーション・バーの右下に配置されます。\fBfooter\fRにはHTMLタグおよび空白文字を含めることができますが、その場合、\fBfooter\fRを引用符で囲む必要があります。フッター内部の引用符にはエスケープ文字を使用します。 +.RE +.PP +\-top +.RS 4 +各出力ファイルの最上部に配置するテキストを指定します。 +.RE +.PP +\-bottom \fItext\fR +.RS 4 +各出力ファイルの最下部に配置するテキストを指定します。このテキストは、下部ナビゲーション・バーより下の、ページの最下部に配置されます。テキストにはHTMLタグおよび空白文字を含めることができますが、その場合、テキストを引用符で囲む必要があります。テキスト内部の引用符にはエスケープ文字を使用します。 +.RE +.PP +\-link \fIextdocURL\fR +.RS 4 +既存のJavadocにより生成された外部参照クラスのドキュメントへのリンクを作成します。\fIextdocURL\fR引数は、リンク先として指定する、Javadocにより生成された外部ドキュメントを含むディレクトリの絶対URLまたは相対URLです。指定した\fBjavadoc\fRコマンドの実行で、複数の\fB\-link\fRオプションを指定して複数のドキュメントへのリンクを作成できます。 +.sp +このディレクトリ内にpackage\-listファイルが存在する必要があります(存在しない場合は、\fB\-linkoffline\fRオプションを使用します)。\fBjavadoc\fRコマンドは、package\-listファイルからパッケージ名を読み取った後、そのURLでこれらのパッケージにリンクします。\fBjavadoc\fRコマンドの実行時に、\fBextdocURL\fRの値が、作成された\fB<A HREF>\fRリンク内にコピーされます。したがって、\fBextdocURL\fRはファイルではなくディレクトリへのURLである必要があります。\fIextdocURL\fRに絶対リンクを使用すると、ユーザーのドキュメントを任意のWebサイト上のドキュメントにリンクできます。相対位置へリンクするのみの場合は相対リンクを使用できます。相対リンクを使用する場合、渡す値は宛先ディレクトリから、リンクされているパッケージを含むディレクトリへである必要があります(\fB\-d\fRオプションで指定)。絶対リンクを指定する場合、通常、HTTPリンクを使用します。ただし、Webサーバーを持たないファイル・システムにリンクする場合は、ファイル・リンクを使用できます。生成されたドキュメンテーションにアクセスする全員が同じファイル・システムを共有する場合にのみファイル・リンクを使用します。どの場合も、どのオペレーティング・システムでも、URLが絶対または相対のいずれでも、また\fBh\fR\fBttp:\fRまたは\fBf\fR\fBile:\fRのいずれでも、URLメモ: Uniform Resource Locators +(http://www\&.ietf\&.org/rfc/rfc1738\&.txt)に指定されているとおり、区切り文字としてスラッシュを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-link http://<host>/<directory>/<directory>/\&.\&.\&./<name>\fR +\fB\-link file://<host>/<directory>/<directory>/\&.\&.\&./<name>\fR +\fB\-link <directory>/<directory>/\&.\&.\&./<name>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-linkofflineおよび\-linkオプションの違い +.PP +次の場合に、\fB\-link\fRオプションを使用します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +外部APIドキュメントへの相対パスを使用する場合。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +外部APIドキュメントへの絶対URLを使用する場合(そのURLに接続し、読取りを行うことがシェルによって許可されている場合)。 +.RE +.PP +外部APIドキュメントへの絶対URLを使用する場合(そのURLに接続し、読取りを行うことがシェルによって許可されていない場合)は\fB\-linkoffline\fRオプションを使用します。このような状況は、ファイアウォールの内側からファイアウォールの外側にあるドキュメントにリンクしようとする場合に発生します。 +.PP +\fB例 1 \fR外部ドキュメントへの絶対リンク +.RS 4 +http://docs\&.oracle\&.com/javase/8/docs/api/index\&.htmlに示すような、\fBjava\&.lang\fR、\fBjava\&.io\fRおよびその他のJavaプラットフォーム・パッケージにリンクする場合、次のコマンドを使用します +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-link http://docs\&.oracle\&.com/javase/8/docs/api/ com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +このコマンドは、Java SEプラットフォーム・パッケージへのリンク持つ\fBcom\&.mypackage\fRパッケージのドキュメントを生成します。生成ドキュメントには、たとえばクラス\fBtrees\fR内の\fBObject\fRクラスへのリンクが含まれています。\fB\-sourcepath\fRや\fB\-d\fRなどの他のオプションは表示されません。 +.RE +.PP +\fB例 2 \fR外部ドキュメントへの相対リンク +.RS 4 +この例では、2つのパッケージがあり、そのドキュメントは\fBjavadoc\fRコマンドを複数回実行した結果生成されたものです。さらに、これらのドキュメントは相対パスで分割されています。パッケージは、APIである\fBcom\&.apipackage\fRと、SPI(サービス・プロバイダ・インタフェース)であるc\fBom\&.spipackage\fRです。ドキュメントの格納先は、docs/api/com/apipackageとdocs/spi/com/spipackageです。APIパッケージのドキュメントはすでに生成されていて、docsが現在のディレクトリである場合、APIドキュメントへのリンクを持つSPIパッケージをドキュメント化するには、次のコマンドを実行します。\fBjavadoc \-d \&./spi \-link \&.\&./api com\&.spipackage\fR +.sp +\fB\-link\fRオプションは、宛先ディレクトリ(docs/spi)からの相対パスです。 +.RE +.PP +注意 +.PP +\fB\-link\fRオプションを使用すると、コードからは参照されていても、今回の\fBjavadoc\fRの実行ではドキュメント化されないクラスにリンクできるようになります。リンクから有効なページに移動できるようにするには、それらのHTMLページがある場所を調べ、その場所を\fBextdocURL\fRに指定する必要があります。これにより、サードパーティのドキュメンテーションがjava\&.*ドキュメンテーション( +http://docs\&.oracle\&.com)へリンクすることができます。\fBjavadoc\fRコマンドで、現在の実行で生成しているドキュメンテーション内のAPIへのリンクのみを作成する場合には、\fB\-link\fRオプションを省略します。\fB\-link\fRオプションを指定しないと、\fBjavadoc\fRコマンドは外部参照のためのドキュメンテーションへのリンクを作成しません。ドキュメンテーションが存在するのかどうか、またはどこに存在するのかがわからないからです。\fB\-link\fRオプションでは、生成ドキュメンテーション内の複数の場所にリンクを作成できます。ソース・ファイルの処理を参照してください。もう1つの用途は、パッケージ・セットの間にクロスリンクを作成することです。一方のパッケージ・セットに対して\fBjavadoc\fRコマンドを実行した後、他方のパッケージ・セットに対して\fBjavadoc\fRコマンドを再度実行すると、両セット間に双方向のリンクを作成できます。 +.PP +クラスの参照方法 +.PP +表示される外部参照クラスへのリンクの場合(およびそのテキスト・ラベルだけではなく)、クラスは次の方法で参照される必要があります。メソッドの本体でクラスを参照するのみでは十分ではありません。\fBimport\fR文、宣言のいずれかで参照する必要があります。次に、クラス\fBjava\&.io\&.File\fRを参照する方法の例を示します。 +.PP +すべてのタイプのimport文の場合。ワイルドカードによるインポート、名前による明示的なインポート、または\fBjava\&.lang\&.*\fRに対する自動インポート。 +.PP +Java SE 1\&.3\&.\fIn\fRおよび1\&.2\&.\fIn\fRでは、名前による明示的なインポートのみ機能します。ワイルドカードによる\fBimport\fR文も、\fBimport java\&.lang\&.*\fRの自動インポートも機能しません。 +.PP +宣言の場合: +\fBvoid mymethod(File f) {}\fR +.PP +参照は、メソッド、コンストラクタ、フィールド、クラスまたはインタフェースの戻り型またはパラメータ・タイプ、あるいは実装、拡張またはスロー文にあります。 +.PP +重要な結果として、\fB\-link\fRオプションを使用しても、この制限のために誤って表示されないリンクが多数発生する可能性があります。テキストはハイパーテキスト・リンクが付けられずに表示されます。リンクが表示する警告から、これらのリンクを認識できます。クラスを正しく参照し、それによってリンクを追加するための最も簡単な方法はそのクラスをインポートすることです。 +.PP +パッケージ・リスト +.PP +\fB\-link\fRオプションには、\fBjavadoc\fRコマンドによって生成されるpackage\-listという名前のファイルが、\fB\-link\fRオプションに指定したURLに存在していることが必要です。package\-listファイルは、その場所にあるドキュメント化されたパッケージの名前のリストが入った単純なテキスト・ファイルです。前述の例では、\fBjavadoc\fRコマンドは、指定したURLでpackage\-listという名前のファイルを検索し、パッケージ名を読み取って、そのURLでこれらのパッケージにリンクします。 +.PP +たとえば、Java SE APIのパッケージ・リストは +http://docs\&.oracle\&.com/javase/8/docs/api/package\-listにあります。 +.PP +このパッケージ・リストは次のような内容で始まっています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\&.applet\fR +\fBjava\&.awt\fR +\fBjava\&.awt\&.color\fR +\fBjava\&.awt\&.datatransfer\fR +\fBjava\&.awt\&.dnd\fR +\fBjava\&.awt\&.event\fR +\fBjava\&.awt\&.font\fR +\fBand so on \&.\&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB\-link\fRオプションを指定せずに\fBjavadoc\fRを実行した場合、外部参照クラスに属する名前を見つけると、その名前をリンクなしで出力します。一方、\fB\-link\fRオプションを指定した場合、\fBjavadoc\fRコマンドは、指定された\fIextdocURL\fRの場所にあるpackage\-listファイルでそのパッケージ名を検索します。パッケージ名が見つかると、\fIextdocURL\fRが名前の前に付加されます。 +.PP +すべてのリンクが正しく機能するためには、外部参照のすべてのドキュメントが、指定したURLに存在する必要があります。\fBjavadoc\fRコマンドは、指定されたpackage\-listが存在するかどうかのみをチェックし、これらのページが存在するかどうかはチェックしません。 +.PP +複数のリンク +.PP +複数の\fB\-link\fRオプションを指定すると、任意の数の外部生成ドキュメントへのリンクを作成できます。Javadoc 1\&.2には、複数の\fB\-link\fRオプションを指定できないという既知の不具合があります。これはJavadoc 1\&.2\&.2で修正されました。リンクする外部ドキュメントごとに、次のように別々のリンク・オプションを指定します。\fBjavadoc \-link extdocURL1 \-link extdocURL2 \&.\&.\&. \-link extdocURLn com\&.mypackage\fR +\fIextdocURL1\fR、\fIextdocURL2\fR、\&.\fB\&.\&. extdocURLn\fRは、それぞれ外部ドキュメントのルートを指し、各ルートには、package\-listという名前のファイルが入っています。 +.PP +クロスリンク +.PP +以前に作成された複数のドキュメントをクロスリンクする場合、ブートストラップが必要になることがあります。どのドキュメントについてもpackage\-listが存在していない場合は、最初のドキュメントに対して\fBjavadoc\fRコマンドを実行する時点で、2番目のドキュメントのpackage\-listはまだ存在していません。したがって、外部リンクを作成するには、2番目のドキュメントを生成した後で、最初のドキュメントを生成しなおす必要があります。 +.PP +この場合、最初のドキュメント生成の目的は、package\-listを作成することです(パッケージ名を把握している場合は手動で作成してもかまいません)。次に、2番目のドキュメントとその外部リンクを生成します。必要な外部のpackage\-listファイルが存在しない場合は、\fBjavadoc\fRコマンドから警告が出力されます。 +.PP +\-linkoffline \fIextdocURL packagelistLoc\fR +.RS 4 +このオプションは\fB\-link\fRオプションのバリエーションです。両方とも、Javadocにより生成された外部参照クラスのドキュメントへのリンクを作成します。\fBjavadoc\fRコマンドがWeb接続を使用してドキュメントにアクセスできないとき、Web上のドキュメントにリンクするには、\fB\-link\fRo\fBffline\fRオプションを使用します。外部ドキュメントのpackage\-listファイルにアクセスできないとき、またはこのファイルが\fBextdocURL\fRで指定された場所には存在せず、\fBpackageListLoc\fRで指定できる別の場所(通常ローカル)に存在するとき、\fB\-linkoffline\fRオプションを使用します。\fBextdocURL\fRにWorld Wide Web上でしかアクセスできない場合は、\fB\-linkoffline\fRオプションを指定することにより、ドキュメントの生成時に\fBjavadoc\fRコマンドがWebに接続する必要があるという制約がなくなります。もう1つの用途は、ドキュメントを更新するための回避策として使用することです。パッケージのセット全体に対して\fBjavadoc\fRコマンドを実行した後、変更した一部のパッケージに対してのみ\fBjavadoc\fRコマンドを再度実行して、更新されたファイルを、オリジナルのセットに挿入できるようにします。次に例を示します。\fB\-linkoffline\fRオプションは引数を2つ取ります。第1引数は\fB<a href>\fRリンクに組み込まれる文字列を指定し、第2引数はpackage\-listの検索場所を\fB\-linkoffline\fRに伝えます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBextdocURL\fRの値は、リンク先として指定する、Javadocにより生成された外部ドキュメントを含むディレクトリの絶対URLまたは相対URLです。相対URLの場合、値は、生成先ディレクトリ(\fB\-d\fRオプションで指定)からリンク先となるパッケージのルートへの相対パスにする必要があります。詳細は、\fB\-link\fRオプションの\fIextdocURL\fRを参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackagelistLoc\fRの値は、外部ドキュメントのpackage\-listファイルを含むディレクトリへのパスまたはURLです。これは、URL (http:またはfile:)でもファイル・パスでもかまいません。また、絶対パスと相対パスのどちらでもかまいません。相対パスの場合は、\fBjavadoc\fRコマンドが実行される現在のディレクトリからの相対パスとして指定します。package\-listファイル名を含めないでください。 +.sp +指定した\fBjavadoc\fRコマンドの実行で、複数の\fB\-link\fRオプションを指定できます。Javadoc 1\&.2\&.2より前では、\fB\-linkfile\fRオプションは1回しか指定できませんでした。 +.RE +.RE +.PP +外部ドキュメントへの絶対リンク +.PP +http://docs\&.oracle\&.com/javase/8/docs/api/index\&.htmlに示すような、\fBjava\&.lang\fR、 +\fBjava\&.io\fRおよびその他のJava SEパッケージにリンクする必要がある場合があります。 +.PP +ただし、シェルにはWebアクセス権がありません。この場合、次を行います。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +ブラウザでpackage\-listファイルを開きます(http://docs\&.oracle\&.com/javase/8/docs/api/package\-list) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +ファイルをローカル・ディレクトリに保存し、このローカル・コピーを第2引数\fBpackagelistLoc\fRで指定します。この例では、パッケージ・リスト・ファイルはカレント・ディレクトリ(\&.)に保存されています。 +.RE +.PP +次のコマンドは、Java SEプラットフォーム・パッケージへのリンクを持つc\fBom\&.mypackage\fRパッケージのドキュメントを生成します。生成ドキュメントには、たとえばクラス\fBtrees\fR内の\fBObject\fRクラスへのリンクが含まれています。\fB\-sourcepath\fRなど、他の必要なオプションは表示されません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-linkoffline http://docs\&.oracle\&.com/javase/8/docs/api/ \&. com\&.mypackage \fR + +.fi +.if n \{\ +.RE +.\} +.PP +外部ドキュメントへの相対リンク +.PP +\fB\-linkoffline\fRを相対パスとともに使用することはあまりありません。理由は単純で、通常は\fB\-link\fRで間に合うからです。\fB\-linkoffline\fRオプションを使用する場合、通常、package\-listファイルはローカルで、相対リンクを使用する場合はリンク先のファイルもローカルなので、通常は\fB\-linkoffline\fRオプションの2つの引数に、異なるパスを指定する必要はありません。2つの引数が同一の場合、\fB\-link\fRオプションを使用できます。 +.PP +package\-listファイルの手動での作成 +.PP +package\-listファイルがまだ存在しなくても、ドキュメントのリンク先のパッケージ名がわかっている場合は、このファイルのコピーを手動で作成し、\fBpackagelistLoc\fRでそのパスを指定することができます。\fBcom\&.apipackage\fRが最初に生成された時点で\fBcom\&.spipackage\fRのパッケージ・リストが存在しないという前出のケースが一例として挙げられます。この方法は、パッケージ名はわかっているものの、まだ公開されていない、新しい外部ドキュメントにリンクするドキュメントを生成する必要がある場合に便利です。また、package\-listファイルが生成されないJavadoc 1\&.0または1\&.1で生成されたパッケージ用にpackage\-listファイルを作成する場合にも、この方法が使用できます。同様に、2つの企業が未公開のpackage\-listファイルを共有できるため、クロスリンクを設定したドキュメントを同時にリリースすることも可能になります。 +.PP +複数ドキュメントへのリンク +.PP +参照先の生成ドキュメントごとに1回、\fB\-linkoffline\fRオプションを含めることができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-linkoffline extdocURL1 packagelistLoc1 \-linkoffline extdocURL2\fR +\fBpackagelistLoc2 \&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ドキュメントの更新 +.PP +プロジェクトに何十または何百のパッケージが含まれる場合にも、\fB\-linkoffline\fRオプションを使用できます。ソース・ツリー全体ですでに\fBjavadoc\fRコマンドを実行したことがある場合、ドキュメンテーション・コメントにわずかな変更を迅速に加え、ソース・ツリーの一部で\fBjavadoc\fRコマンドを再実行することができます。2回目の実行は、ドキュメンテーション・コメントを変更し、宣言は変更しない場合にのみ正しく処理されることに注意してください。ソース・コードに対して宣言を追加、削除、または変更した場合は、索引、パッケージ・ツリー、継承されるメンバーのリスト、使用ページなどの場所で、リンクが壊れることがあります。 +.PP +まず、この新しい小規模な実行で使用する、新しい生成先ディレクトリ(updateなど)を作成します。この例では、元の生成先ディレクトリの名前はhtmlです。最も単純な例では、htmlディレクトリの親ディレクトリに移動します。\fB\-linkoffline\fRオプションの第1引数にカレント・ディレクトリ(\&.)を設定し、第2引数にpackage\-listが検索されるhtmlへの相対パスを設定し、更新するパッケージのパッケージ名のみを渡します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d update \-linkoffline \&. html com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavadoc\fRコマンドの終了後、update/com/package内の生成されたクラスのページをコピーし(概要や索引は除く)、html/com/package内の元のファイルに上書きします。 +.PP +\-linksource +.RS 4 +各ソース・ファイル(行番号付き)のHTMLバージョンを作成し、標準HTMLドキュメントからソース・ファイルへのリンクを追加します。リンクは、ソース・ファイル内に宣言されているクラス、インタフェース、コンストラクタ、メソッド、フィールドに対して作成されます。デフォルト・コンストラクタ、生成されたクラスなどに対しては作成されません。 +.sp +このオプションは、\fB\-public\fR、\fB\-package\fR、\fB\-protected\fRおよび\fB\-private\fRの各オプションとは関係なく、非公開のクラス、フィールド、非公開のメソッドの本体をはじめとする組み込まれたソース・ファイル内のすべての非公開実装の詳細を公開します。\fB\-private\fRオプションもあわせて指定しないかぎり、非公開のクラスやインタフェースの一部には、リンクを介してアクセスできないことがあります。 +.sp +各リンクは、その宣言内の識別子名の上に作成されます。たとえば、\fBButton\fRクラスのソース・コードへのリンクは、\fBButton\fRという語の上に作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic class Button extends Component implements Accessible\fR + +.fi +.if n \{\ +.RE +.\} +\fBButton\fRクラスの\fBgetLabel\fRメソッドのソース・コードへのリンクは、\fBgetLabel\fRという語の上に作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic String getLabel()\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-group groupheading \fIpackagepattern:packagepattern\fR +.RS 4 +概要ページの複数のパッケージを、指定したグループに分けて、グループごとに表を作成します。各グループは、それぞれ別の\fB\-group\fRオプションで指定します。グループは、コマンド行で指定された順序でページに表示されます。パッケージは、グループ内でアルファベット順になっています。指定した\fB\-group\fRオプションでは、\fBpackagepattern\fR式のリストに一致するパッケージが、見出しとして\fIgroupheading\fRを持つ1つの表に表示されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBgroupheading\fRには、任意のテキストを指定でき、空白を含めることができます。指定したテキストは、グループの表見出しになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpackagepattern\fRの値には、任意のパッケージ名の先頭部分とそれに続く1つのアスタリスク(*)で任意のパッケージ名を指定できます。アスタリスクは使用できる唯一のワイルドカードで、任意の文字に一致する、という意味です。1つのグループには、コロン(:)で区切って複数のパターンを含めることができます。パターンまたはパターン・リストでアスタリスクを使用する場合、パターン・リストは\fB"java\&.lang*:java\&.util"\fRのように引用符で囲む必要があります。 +.RE +.sp +\fB\-group\fRオプションを指定しない場合は、見出し\fIPackages\fRおよび適切な小見出しを持つ1つのグループに配置されます。小見出しにすべてのドキュメント化されるパッケージ(すべてのグループ)が含まれるわけではない場合、残りのパッケージは「その他のパッケージ」というサブ見出しを持つ独立したグループに入れられます。 +.sp +たとえば、次の\fBjavadoc\fRコマンドでは、3つのドキュメント化されたパッケージが\fI「コア」\fR、\fI「拡張」\fRおよび\fI「その他のパッケージ」\fRに分けられます。\fBjava\&.lang*\fRでは、最後のドット(\&.)を指定していません。\fBjava\&.lang\&.*\fRのようにドットを入れると、\fB java\&.lang\fRパッケージは除外されることになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-group "Core Packages" "java\&.lang*:java\&.util"\fR +\fB \-group "Extension Packages" "javax\&.*"\fR +\fB java\&.lang java\&.lang\&.reflect java\&.util javax\&.servlet java\&.new\fR + +.fi +.if n \{\ +.RE +.\} +\fBコア・パッケージ\fR +.sp +\fBjava\&.lang\fR +.sp +\fBjava\&.lang\&.reflect\fR +.sp +\fBjava\&.util\fR +.sp +\fB拡張機能パッケージ\fR +.sp +\fBjavax\&.servlet\fR +.sp +\fBOther Packages\fR +.sp +\fBjava\&.new\fR +.RE +.PP +\-nodeprecated +.RS 4 +推奨されないAPIをドキュメントに生成しないようにします。このオプションを指定すると、\fB\-nodeprecatedlist\fRオプションを指定した場合と同じ効果があり、ドキュメントの他の部分全体でも、推奨されないAPIが生成されません。このオプションは、コードを記述しているとき、推奨されないコードによって気を散らされたくない場合に便利です。 +.RE +.PP +\-nodeprecatedlist +.RS 4 +推奨されないAPIのリストを含むファイル(deprecated\-list\&.html)、およびナビゲーション・バーのそのページへのリンクが生成されないようにします。\fBjavadoc\fRコマンドでは、引き続き、ドキュメントの他の部分では、推奨されないAPIが生成されます。このオプションは、推奨されないAPIがソース・コードに含まれておらず、ナビゲーション・バーをすっきりと見せる場合に便利です。 +.RE +.PP +\-nosince +.RS 4 +生成ドキュメントから、\fB@since\fRタグに関連付けられた\fB「導入されたバージョン」\fRセクションを省略します。 +.RE +.PP +\-notree +.RS 4 +生成ドキュメントから、クラスおよびインタフェースの階層ページを省略します。これらのページには、ナビゲーション・バーの「階層ツリー」ボタンからアクセスできます。デフォルトでは、階層が生成されます。 +.RE +.PP +\-noindex +.RS 4 +生成ドキュメントから、索引を省略します。デフォルトでは、索引が生成されます。 +.RE +.PP +\-nohelp +.RS 4 +出力の各ページの最上部と最下部にあるナビゲーション・バーから「ヘルプ」リンクを省略します。 +.RE +.PP +\-nonavbar +.RS 4 +通常、生成されるページの最上部と最下部に表示されるナビゲーション・バー、ヘッダー、およびフッターを生成しないようにします。\fB\-nonavbar\fRオプションは\fB\-bottom\fRオプションに影響を与えません。\fB\-nonavbar\fRオプションは、印刷するためにのみファイルをPostScriptやPDFに変換する場合など、内容のみが重要で、ナビゲーションの必要がない場合に便利です。 +.RE +.PP +\-helpfile \fIpath\efilename\fR +.RS 4 +最上部および最下部のナビゲーション・バーの「ヘルプ」リンクのリンク先となる代替ヘルプ・ファイルpath\efilenameのパスを指定します。このオプションが指定されていないと、\fBjavadoc\fRコマンドは、\fBjavadoc\fRコマンド内でハードコードされているヘルプ・ファイルhelp\-doc\&.htmlを自動作成します。このオプションを使用すると、デフォルトをオーバーライドできます。ファイル名にはどんな名前でも指定でき、help\-doc\&.htmlに限定されません。\fBjavadoc\fRコマンドは、次の例のように、ナビゲーション・バー内のリンクを必要に応じて調整します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-helpfile /home/user/myhelp\&.html java\&.awt\&.\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-stylesheet \fIpath/filename \fR +.RS 4 +代替HTMLスタイルシート・ファイルのパスを指定します。このオプションが指定されていないと、\fBjavadoc\fRコマンドは、\fBjavadoc\fRコマンド内でハードコードされているスタイルシート・ファイルstylesheet\&.cssを自動作成します。このオプションを使用すると、デフォルトをオーバーライドできます。ファイル名にはどんな名前でも指定でき、stylesheet\&.cssに限定されません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-stylesheet file /home/user/mystylesheet\&.css com\&.mypackage\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-serialwarn +.RS 4 +\fB@serial\fRタグがない場合は、コンパイル時に警告を生成します。デフォルトでは、Javadoc 1\&.2\&.2以降では、直列化の警告は生成されません。以前のリリースとは逆の動作です。このオプションを使用すると、直列化の警告が表示されるので、デフォルトの直列化可能フィールドと\fBwriteExternal\fRメソッドを適切にドキュメント化するのに役立ちます。 +.RE +.PP +\-charset \fIname\fR +.RS 4 +このドキュメント用のHTML文字セットを指定します。この名前は、IANA RegistryのCharacter Sets +(http://www\&.iana\&.org/assignments/character\-sets)に示された、優先MIME名である必要があります。 +.sp +たとえば、\fBjavadoc \-charset "iso\-8859\-1" mypackage\fRは次の行を生成された各ページのヘッダーに挿入します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<META http\-equiv="Content\-Type" content="text/html; charset=ISO\-8859\-1">\fR + +.fi +.if n \{\ +.RE +.\} +この\fBMETA\fRタグは、HTML標準(4197265および4137321)のHTML Document Representation +(http://www\&.w3\&.org/TR/REC\-html40/charset\&.html#h\-5\&.2\&.2)に記載されています。 +.sp +およびオプションも参照してください。 +.RE +.PP +\-docencoding \fIname\fR +.RS 4 +生成されるHTMLファイルのエンコーディングを指定します。この名前は、IANA RegistryのCharacter Sets +(http://www\&.iana\&.org/assignments/character\-sets)に示された、優先MIME名である必要があります。 +.sp +\fB\-docencoding\fRオプションを省略し、\fB\-encoding\fRオプションを使用すると、生成されたHTMLファイルの暗号化は\fB\-encoding\fRオプションで特定されます。例: +\fBjavadoc \-docencoding "iso\-8859\-1" mypackage\fRおよびオプションも参照してください。 +.RE +.PP +\-keywords +.RS 4 +HTMLキーワード<META>タグを、クラスごとに生成されるファイルに追加します。これらのタグは、<META>タグを検索するサーチ・エンジンがページを見つける場合に役立ちます。インターネット全体を検索する検索エンジンのほとんどは<META>タグを参照しません。ページが誤用している可能性があるからです。自身のWebサイトへの検索を制限する、企業により提供される検索エンジンは、<META>タグを参照することで恩恵を受けることができます。<META>タグには、クラスの完全修飾名と、フィールドおよびメソッドの修飾されていない名前が含まれます。コンストラクタは、クラス名と同じであるため含まれません。たとえば、クラス\fBString\fRは次のキーワードで開始します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<META NAME="keywords" CONTENT="java\&.lang\&.String class">\fR +\fB<META NAME="keywords" CONTENT="CASE_INSENSITIVE_ORDER">\fR +\fB<META NAME="keywords" CONTENT="length()">\fR +\fB<META NAME="keywords" CONTENT="charAt()">\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-tag \fItagname\fR:Xaoptcmf:"\fItaghead\fR" +.RS 4 +\fBjavadoc\fRコマンドがドキュメンテーション・コメント内の引数を1つ取る単純なカスタム・ブロック・タグ\fB@tagname\fRを解釈できるようにします。これにより、\fBjavadoc\fRコマンドはタグ名のスペルチェックを行うことができるので、ソース・コード内に存在するすべてのカスタム・タグについて、\fB\-tag\fRオプションを組み込むことが重要です。今回の実行では出力されないタグは、\fBX\fRを付けて無効にします。\fB\-tag\fRオプションは、タグの見出し\fItaghead\fRを太字で出力します。その次の行には、このオプションの1つの引数で指定したテキストが続きます。ブロック・タグと同様、この引数のテキストにはインライン・タグを含めることができます。このインライン・タグも解釈されます。出力は、引数を1つ取る標準のタグ(\fB@return\fRや\fB@author\fRなど)の出力とよく似ています。\fItaghead\fRの値を省略すると、\fBtagname\fRが見出しとして表示されます。 +.sp +\fBタグの配置\fR: +\fBXaoptcmf\fR引数により、ソース・コード内でタグを配置できる場所が決まり、タグを無効にできるかどうか(\fBX\fRを使用して)が決まります。タグの配置位置を制限しない場合は\fBa\fRを指定します。それ以外の文字の組合せも可能です。 +.sp +\fBX\fR +(タグの無効化) +.sp +\fBa\fR +(すべて) +.sp +\fBo\fR +(概要) +.sp +\fBp\fR +(パッケージ) +.sp +\fBt\fR +(タイプ、つまりクラスとインタフェース) +.sp +\fBc\fR +(コンストラクタ) +.sp +\fBm\fR +(メソッド) +.sp +\fBf\fR +(フィールド) +.sp +\fBシングル・タグの例\fR: ソース・コード内の任意の位置で使用できるタグのタグ・オプションの例を示します。\fB\-tag todo:a:"To Do:"\fR +.sp +\fB@todo\fRタグをコンストラクタ、メソッドおよびフィールドとのみ使用する場合、\fB\-tag todo:cmf:"To Do:"\fRを使用します。 +.sp +最後のコロン(:)は、パラメータ区切り文字ではなく、見出しテキストの一部になっています。\fB@todo\fRタグを含む、ソース・コード用のいずれかのタグ・オプションを使用します。たとえば、\fB@todo The documentation for this method needs work\fRです。 +.sp +\fBタグ名内のコロン\fR: タグ名内でコロンを使用する場合はバックスラッシュを使用してエスケープします。次のドキュメンテーション・コメントには、\fB\-tag ejb\e\e:bean:a:"EJB Bean:"\fRオプションを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/**\fR +\fB * @ejb:bean\fR +\fB */\fR + +.fi +.if n \{\ +.RE +.\} +\fBタグ名のスペルチェック\fR: 一部の開発者が必ずしも出力しないカスタム・タグをソース・コード内に配置することがあります。この場合、ソース・コード内のすべてのタグをリストし、出力するタグを有効にし、出力しないタグを無効にする必要があります。\fBX\fRを指定するとタグは無効になります。指定しないと、タグは有効になります。これにより、\fBjavadoc\fRコマンドは、検出したタグが入力ミスなどによる不明タグであるかどうかを特定できます。このような場合に、\fBjavadoc\fRコマンドから警告が出力されます。すでに配置されている値に\fBX\fRを追加できます。こうしておけば、\fBX\fRを削除するのみでタグを有効にすることができます。たとえば、\fB@todo\fRタグを出力で抑制する場合、\fB\-tag todo:Xcmf:"To Do:"\fRを使用します。さらに簡単にする場合、\fB\-tag todo:X\fRを使用します。構文\fB\-tag todo:X\fRは、\fB@todo\fRタグがタグレットで定義されていても機能します。 +.sp +\fBタグの順序\fR: +\fB\-ta\fR\fBg\fRおよび\fB\-taglet\fRオプションの順序によって、タグの出力順が決まります。カスタム・タグと標準タグを組み合せて使用することもできます。標準タグのタグ・オプションは、順序を決定するためだけのプレースホルダです。標準タグの名前のみを取ります。標準タグの小見出しは変更できません。これを次の例に示します。\fB\-tag\fRオプションを指定しないと、\fB\-tagle\fR\fBt\fRオプションの位置により、順序が決まります。タグが両方とも存在する場合、コマンドラインの最後にある方がその順序を決定します。これは、タグやタグレットがコマンドラインに指定された順番に処理されるためです。たとえば、\fB\-taglet\fRおよび\fB\-tag\fRオプションが名前\fBtodo\fR値を持つ場合、コマンドラインに最後に指定されたものが順序を決定します。 +.sp +\fBタグの完全セットの例\fR: この例では、出力のParametersとThrowsの間にTo Doを挿入します。\fBX\fRを使用して、\fB@example\fRタグが、ソース・コード内の今回の実行では出力されないタグであることも指定します。\fB@argfile\fRタグを使用する場合は、次のように、引数ファイル内の別々の行にタグを配置できます(行の継続を示す文字は不要)。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-tag param\fR +\fB\-tag return\fR +\fB\-tag todo:a:"To Do:"\fR +\fB\-tag throws\fR +\fB\-tag see\fR +\fB\-tag example:X\fR + +.fi +.if n \{\ +.RE +.\} +\fBjavadoc\fRコマンドがドキュメンテーション・コメントを解析する際に検索されたタグのうち、標準タグでも、\fB\-tag\fRや\fB\-taglet\fRオプションで渡されたタグでもないものはすべて不明タグとみなされ、警告がスローされます。 +.sp +標準タグは、最初、デフォルトの順序でリスト内に内部的に格納されます。\fB\-tag\fRオプションを使用すると、それらのタグはこのリストに追加されます。標準タグは、デフォルトの位置から移動されます。そのため、標準タグの\fB\-tag\fRオプションを省略すると、それはデフォルトの位置に配置されたままになります。 +.sp +\fB競合の回避\fR: 固有の名前空間を作成するには、パッケージに使用されている\fBcom\&.mycompany\&.todo\fRという名前のように、ドットで区切られた名前を使用します。Oracleは、今後も名前にドットを含まない標準タグを作成します。ユーザーが作成したタグは、Oracleが定義する同じ名前のタグの動作をオーバーライドします。\fB@todo\fRという名前のタグまたはタグレットをユーザーが作成した場合、その後にOracleが同じ名前の標準タグを作成しても、そのタグまたはタグレットは常にユーザーが定義したのと同じ動作を保持します。 +.sp +\fB注釈vs\&. Javadocタグ\fR: 一般に、追加する必要のあるマークアップが、ドキュメントに影響を与えたりドキュメントを生成したりするためのものである場合、そのマークアップはJavadocタグにします。それ以外の場合は注釈にします。JavadocツールでのDocコメントの記述方法のカスタム・タグと注釈に関する項 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html#annotations)を参照してください。 +.sp +\fB\-taglet\fRオプションを使用して、より複雑なブロック・タグやカスタム・インライン・タグも作成できます。 +.RE +.PP +\-taglet \fIclass\fR +.RS 4 +そのタグのドキュメントの生成に使用するドックレットを起動するためのクラス・ファイルを指定します。\fBclass\fR値の完全修飾名を使用します。このタグレットは、カスタム・タグのテキスト引数の数も定義します。タグレットは、これらの引数を受け付け、処理し、出力を生成します。タグレットの例を使用した豊富なドキュメントについては、タグレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/taglet/overview\&.html)を参照してください。 +.sp +タグレットは、ブロックタグまたはインライン・タグで便利です。タグレットは任意の数の引数をとることができます。また、テキストを太字にする、箇条書きを作成する、テキストをファイルに書き出す、その他のプロセスを開始するなどのカスタム動作を実装できます。タグレットで指定できるのは、タグの配置場所と配置形式のみです。その他のすべての決定は、ドックレットによって行われます。タグレットを使用しても、包含クラスのリストからクラス名を削除するなどの処理は実行できません。ただし、タグのテキストをファイルに出力したり、別のプロセスをトリガーするなどの副作用は得られます。タグレットへのパスを指定するには、\fB\-tagletpath\fRオプションを使用します。次に、生成されるページのParametersとThrowsの間にTo Doタグレットを挿入する例を示します。または、\fB\-taglet\fRオプションをその\fB\-tag\fRオプションのかわりに使用することができますが、読み取りが困難になる可能性があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-taglet com\&.sun\&.tools\&.doclets\&.ToDoTaglet\fR +\fB\-tagletpath /home/taglets \fR +\fB\-tag return\fR +\fB\-tag param\fR +\fB\-tag todo\fR +\fB\-tag throws\fR +\fB\-tag see\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-tagletpath \fItagletpathlist\fR +.RS 4 +tagletクラス・ファイルを検索するための検索パスを指定します。\fBtagletpathlist\fRには、コロン(:)で区切って複数のパスを含めることができます。\fBjavadoc\fRコマンドは、指定されたパス以下のすべてのサブディレクトリを検索します。 +.RE +.PP +\-docfilesubdirs +.RS 4 +doc\-filesディレクトリのディープ・コピーを有効にします。宛先には、サブディレクトリとそのすべて内容が再帰的にコピーされます。たとえば、ディレクトリoc\-files/example/imagesとその内容がすべてコピーされます。ここでも、サブディレクトリを除外する指定が可能です。 +.RE +.PP +\-excludedocfilessubdir \fIname1:name2\fR +.RS 4 +指定された名前のdoc\-filesサブディレクトリをすべて除外します。これにより、SCCSとその他のソース・コード制御サブディレクトリのコピーを防ぎます。 +.RE +.PP +\-noqualifier all | \fIpackagename1\fR:\fIpackagename2\&.\&.\&.\fR +.RS 4 +出力されるクラス名から修飾パッケージ名を省略します。\fB\-noqualifier\fRオプションの引数は、\fBall\fR(すべてのパッケージ修飾子を省略)、または修飾子として削除するパッケージのコロン区切りリスト(ワイルドカードも可)、のいずれかとなります。クラスまたはインタフェース名が表示される位置からパッケージ名が削除されます。ソース・ファイルの処理を参照してください。 +.sp +次の例では、すべてのパッケージ修飾子を省略します。\fB\-noqualifier all\fR +.sp +次の例では、\fBjava\&.lang\fRおよび\fBjava\&.io\fRパッケージ修飾子を省略します: +\fB\-noqualifier java\&.lang:java\&.io\fR。 +.sp +次の例では、\fBjava\fRで始まるパッケージ修飾子および\fBcom\&.sun\fRサブパッケージを省略しますが、\fBjavax\fRは省略しません。\fB\-noqualifier java\&.*:com\&.sun\&.*\fR +.sp +パッケージ修飾子が前述の動作に従って表示される場合、名前は適切に短縮されます。「名前が表示される方法」を参照してください。このルールは、\fB\-noqualifier\fRオプションを使用するかどうかにかかわらず有効です。 +.RE +.PP +\-notimestamp +.RS 4 +タイムスタンプが抑制されます。各ページの先頭近くにある、生成されたHTML内のHTMLコメントでタイムスタンプが隠されます。\fB\-notimestamp\fRオプションは、\fBjavadoc\fRコマンドを2つのソース・ベースで実行し、それらの間の差分\fBdiff\fRを取得する場合に役立ちます。タイムスタンプによる\fBdiff\fRの発生を防ぐからです(そうでないとすべてのページで\fBdiff\fRになります)。タイムスタンプには\fBjavadoc\fRコマンドのリリース番号が含まれ、現在では、\fB<!\-\- Generated by javadoc (build 1\&.5\&.0_01) on Thu Apr 02 14:04:52 IST 2009 \-\->\fRのように表示されます。 +.RE +.PP +\-nocomment +.RS 4 +主説明およびすべてのタグを含むコメント本文全体を抑制し、宣言のみを生成します。このオプションにより、元は異なる目的のためだったソース・ファイルを再利用し、新しいプロジェクトの早い段階でスケルトンHTMLドキュメントを作成できるようになります。 +.RE +.PP +\-sourcetab \fItablength\fR +.RS 4 +ソース内で各タブが使用する空白文字の数を指定します。 +.RE +.SH "コマンドライン引数ファイル" +.PP +\fBjavadoc\fRコマンドを短くしたり簡潔にしたりするために、\fBjavadoc\fRコマンドに対する引数(\fB\-J\fRオプションを除く)が入った1つ以上のファイルを指定することができます。このことを利用すれば、どのオペレーティング・システム上でも、任意の長さの\fBjavadoc\fRコマンドを作成できます。 +.PP +引数ファイルには、\fBjavac\fRのオプションとソース・ファイル名を自由に組み合せて記述できます。ファイル内の各引数は、スペースまたは改行で区切ります。ファイル名に埋め込まれた空白がある場合、ファイル名全体を二重引用符で囲みます。 +.PP +引数ファイル内のファイル名は、引数ファイルの位置ではなく、現在のディレクトリに相対的となります。これらのリストでは、ワイルドカード(\fB*\fR)は使用できません。たとえば、*\&.javaとは指定できません。アットマーク(@)を使用して、ファイルを再帰的に解釈することはできません。また、\fB\-J\fRオプションもサポートされていません。このオプションは起動ツールに渡されますが、起動ツールでは引数ファイルをサポートしていないからです。 +.PP +\fBjavadoc\fRを実行するときに、各引数ファイルのパスとファイル名の先頭に@文字を付けて渡します。\fBjavadoc\fRコマンドは、アットマーク(@)文字で始まる引数を見つけると、そのファイルの内容を展開して引数リストに挿入します。 +.PP +\fB例 1 \fR単一の引数ファイル +.RS 4 +\fBargfile\fRという名前の1つの引数ファイルを使用して、すべての\fBjavadoc\fRコマンド引数を保持できます。\fBjavadoc @argfile\fR次の例に示すように、この引数ファイルには両方のファイルの内容が含まれています。 +.RE +.PP +\fB例 2 \fR2つの引数ファイル +.RS 4 +次のように、2つの引数ファイルを作成できます。\fBjavadoc\fRコマンドのオプション用に1つ、パッケージ名またはソース・ファイル名用に1つです。次のリストでは行継続文字を使用していません。 +.sp +次の内容を含む、optionsという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-d docs\-filelist \fR +\fB\-use \fR +\fB\-splitindex\fR +\fB\-windowtitle \*(AqJava SE 7 API Specification\*(Aq\fR +\fB\-doctitle \*(AqJava SE 7 API Specification\*(Aq\fR +\fB\-header \*(Aq<b>Java(TM) SE 7</b>\*(Aq\fR +\fB\-bottom \*(AqCopyright © 1993\-2011 Oracle and/or its affiliates\&. All rights reserved\&.\*(Aq\fR +\fB\-group "Core Packages" "java\&.*"\fR +\fB\-overview /java/pubs/ws/1\&.7\&.0/src/share/classes/overview\-core\&.html\fR +\fB\-sourcepath /java/pubs/ws/1\&.7\&.0/src/share/classes\fR + +.fi +.if n \{\ +.RE +.\} +次の内容を含む、packagesという名前のファイルを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcom\&.mypackage1\fR +\fBcom\&.mypackage2\fR +\fBcom\&.mypackage3\fR + +.fi +.if n \{\ +.RE +.\} +次のように、\fBjavadoc\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc @options @packages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRパスを使用した引数ファイル +.RS 4 +引数ファイルはパスを指定できますが、ファイル内のすべてのファイル名は、(\fBpath1\fRや\fBpath2\fRではなく)次のように現在の作業ディレクトリに相対的となります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc @path1/options @path2/packages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fRオプション引数 +.RS 4 +次に、\fBjavadoc\fRコマンドのオプションに対する引数を引数ファイルに格納する例を示します。長い引数を指定できるので、\fB\-bottom\fRオプションを使用します。次のようなテキスト引数を含む、bottomという名前のファイルを作成できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB<font size="\-1">\fR +\fB <a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fR +\fB Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&. <br/>\fR +\fB Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fR +\fB Other names may be trademarks of their respective owners\&.</font>\fR + +.fi +.if n \{\ +.RE +.\} +\fBjavadoc\fRコマンドを次のように実行します。\fB javadoc \-bottom @bottom @packages\fR +.sp +\fB\-bottom\fRオプションを引数ファイルの最初に含めて、次のように\fBjavadoc\fRコマンドを実行することもできます。\fBjavadoc @bottom @packages\fR +.RE +.SH "JAVADOCコマンドの実行" +.PP +\fBjavadoc\fRコマンドのリリース番号は\fBjavadoc \-J\-version\fRオプションで特定できます。出力ストリームには標準ドックレットのリリース番号が含まれます。\fB\-quiet\fRオプションで無効にできます。 +.PP +Java言語で記述されたプログラムから\fBjavadoc\fRコマンドを起動するには公開プログラマティック・インタフェースを使用します。このインタフェースは\fBcom\&.sun\&.tools\&.javadoc\&.Main\fRにあります(また\fBjavadoc\fRコマンドは再入可能です)。詳細は、標準ドックレット +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/standard\-doclet\&.html#runningprogrammatically)を参照してください。 +.PP +次の手順では、標準HTMLドックレットを呼び出します。カスタム・ドックレットを呼び出すには、\fB\-doclet\fRおよび\fB\-docletpath\fRオプションを使用しますドックレットの概要 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html)を参照してください +.SS "簡単な例" +.PP +\fBjavadoc\fRコマンドは、パッケージ全体に対して実行することも、個々のソース・ファイルに対して実行することもできます。各パッケージ名は、それぞれのパッケージ名に対応するディレクトリ名を持ちます。 +.PP +次の例では、ソース・ファイルは/home/src/java/awt/*\&.javaにあります。生成先ディレクトリは/home/htmlです。 +.PP +1つ以上のパッケージのドキュメント化 +.PP +パッケージをドキュメント化するには、そのパッケージのソース・ファイルを、そのパッケージと同じ名前のディレクトリ内に格納する必要があります。 +.PP +パッケージ名が(\fBjava\&.awt\&.color\fRのようにドットで区切られた)複数の識別子から構成されている場合、後続の各識別子が下位のサブディレクトリ(ava/awt/colorなど)に対応している必要があります。 +.PP +1つのパッケージのための複数のソース・ファイルを、異なる場所にあるそのような2つのディレクトリ・ツリーに分けて格納することもできます。ただし、その場合は\fB\-sourcepath\fRによってその両方の場所を指定する必要があります。たとえば、src1/java/awt/colorとsrc2/java/awt/color。 +.PP +ディレクトリの変更(\fBcd\fRコマンドを使用)または\fB\-sourcepath\fRオプションにより、\fBjavadoc\fRコマンドを実行できます。次の例で両方の選択肢を示します。 +.PP +\fB例 1 \fR1つ以上のパッケージから再帰的に実行 +.RS 4 +この例では\fBjavadoc\fRコマンドが任意のディレクトリから実行できるように、\fB\-sourcepath\fRを使用し、再帰的処理のために\fB\-subpackages\fR(1\&.4の新オプション)を使用します。これは、javaディレクトリのサブパッケージをたどりますが、\fBjava\&.net\fRと\fBjava\&.lang\fRをルートに持つパッケージは除外されます。\fBjava\&.lang\fRのサブパッケージである\fBjava\&.lang\&.ref\fRが除外される点に注意してください。また、他のパッケージ・ツリーを下方にたどるには、\fBjava:javax:org\&.xml\&.sax\fRのように、それらのパッケージの名前を\fB\-subpackages\fRの引数に追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src \-subpackages java \-exclude\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRルートへの移動および明示的なパッケージの実行 +.RS 4 +完全修飾されたパッケージの親ディレクトリに移動します。次に、ドキュメント化する1つ以上のパッケージの名前を指定して\fBjavadoc\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd /home/src/\fR +\fBjavadoc \-d /home/html java\&.awt java\&.awt\&.event\fR + +.fi +.if n \{\ +.RE +.\} +また、他のパッケージ・ツリーを下方にたどるには、j\fBava:javax:org\&.xml\&.sax\fRのように、それらのパッケージの名前を\fB\-subpackages\fRの引数に追加します。 +.RE +.PP +\fB例 3 \fR1つのツリーの明示的なパッケージの任意のディレクトリから実行 +.RS 4 +この場合、現在のディレクトリがどこかは問題ではありません。\fBjavadoc\fRコマンドを実行し、最上位パッケージの親ディレクトリを指定して\fB\-sourcepath\fRオプションを使用します。ドキュメント化する1つ以上のパッケージの名前を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src java\&.awt java\&.awt\&.event\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 4 \fR複数のツリーの明示的なパッケージの任意のディレクトリから実行 +.RS 4 +\fBjavadoc\fRコマンドを実行し、各ツリーのルートへのパスのコロン区切りリストを指定して\fB\-sourcepath\fRオプションを使用します。ドキュメント化する1つ以上のパッケージの名前を指定します。指定したパッケージのすべてのソース・ファイルが、1つのルート・ディレクトリの下に存在する必要はありませんが、ソース・パスで指定された場所のどこかで見つかる必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src1:/home/src2 java\&.awt java\&.awt\&.event\fR + +.fi +.if n \{\ +.RE +.\} +すべてのケースでj\fBava\&.awt\fRおよび\fBjava\&.awt\&.even\fRtパッケージ内の\fBpublic\fRおよび\fBprotected\fRクラスとインタフェースについて、HTML形式のドキュメントが生成され、指定された生成先ディレクトリにHTMLファイルが保存されます。2つ以上のパッケージが生成されているので、ドキュメントは、パッケージのリスト、クラスのリスト、およびメインのクラス・ページという3つのHTMLフレームを持つことになります。 +.RE +.PP +1つ以上のクラスのドキュメント化 +.PP +また、1つ以上のソース・ファイルを渡して、\fBjavadoc\fRコマンドを実行することもできます。\fBjavadoc\fRは、次の2つの方法のいずれかで実行できます。1つはディレクトリを変更する方法(\fBcd\fRを使用)、もう1つはソース・ファイルへのパスを完全に指定する方法です。相対パスは、現在のディレクトリを起点とします。ソース・ファイルを渡すときは、\fB\-sourcepath\fRオプションは無視されます。アスタリスク(*)のようなコマンドライン・ワイルドカードを使用すると、クラスのグループを指定できます。 +.PP +\fB例 1 \fRソース・ディレクトリに変更 +.RS 4 +ソースを保持するディレクトリに変更します。次に、ドキュメント化する1つ以上のソース・ファイルの名前を指定して\fBjavadoc\fRコマンドを実行します。 +.sp +この例では、\fBButton\fRクラスと\fBCanvas\fRクラス、および名前が\fBGraphics\fRで始まるクラスについて、HTML形式のドキュメントが生成されます。パッケージ名ではなくソース・ファイルが\fBjavadoc\fRコマンドに引数として渡されているので、ドキュメントは、クラスのリストとメイン・ページという2つのフレームを持つことになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd /home/src/java/awt\fR +\fBjavadoc \-d /home/html Button\&.java Canvas\&.java Graphics*\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fRパッケージのルート・ディレクトリに変更 +.RS 4 +これは、同じルートからの別のサブパッケージの個々のソース・ファイルをドキュメント化するのに役立ちます。パッケージのルート・ディレクトリに移り、各ソース・ファイルを、ルートからのパスとともに指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcd /home/src/\fR +\fBjavadoc \-d /home/html java/awt/Button\&.java java/applet/Applet\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fR任意のディレクトリからのファイルのドキュメント化 +.RS 4 +この場合、現在のディレクトリがどこかは問題ではありません。ドキュメント化するソース・ファイルへの絶対パス(または現在のディレクトリからの相対パス)を指定して\fBjavadoc\fRコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html /home/src/java/awt/Button\&.java\fR +\fB/home/src/java/awt/Graphics*\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +パッケージおよびクラスのドキュメント化 +.PP +パッケージ全体と個々のクラスを同時に指定してドキュメント化することもできます。次に、前述の2つの例を組み合せた例を示します。\fB\-sourcepath\fRオプションは、パッケージへのパスに対しては使用できますが、個々のクラスへのパスに対しては使用できません。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-d /home/html \-sourcepath /home/src java\&.awt\fR +\fB/home/src/java/applet/Applet\&.java\fR + +.fi +.if n \{\ +.RE +.\} +.SS "実際の例" +.PP +次のコマンドラインおよび\fBmakefile\fRバージョンの\fBjavadoc\fRコマンドをJavaプラットフォームAPIで実行します。Java SE 1\&.2で約1500個のpublicおよびprotectedクラスのドキュメントを生成するには、180MBのメモリーを使用します。どちらの例もオプションの引数で絶対パスが使用されているため、任意のディレクトリから同じ\fBjavadoc\fRコマンドを実行できます。 +.PP +コマンドラインの例 +.PP +次のコマンドは、一部のシェルに対して長すぎる可能性があります。この制限を回避するには、コマンドライン引数ファイルを使用します。または、シェル・スクリプトを記述します。 +.PP +この例では、\fBpackages\fRは処理するパッケージを含む名前で、\fBjava\&.applet\fR +\fBjava\&.lang\fRなどです。各オプションの、一重引用符で囲まれた引数の内側には、改行文字を挿入できません。たとえば、この例をコピー・アンド・ペーストする場合は、\fB\-bottom\fRオプションから改行文字を削除してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath /java/jdk/src/share/classes \e\fR +\fB\-overview /java/jdk/src/share/classes/overview\&.html \e\fR +\fB\-d /java/jdk/build/api \e\fR +\fB\-use \e\fR +\fB\-splitIndex \e\fR +\fB\-windowtitle \*(AqJava Platform, Standard Edition 7 API Specification\*(Aq \e\fR +\fB\-doctitle \*(AqJava Platform, Standard Edition 7 API Specification\*(Aq \e\fR +\fB\-header \*(Aq<b>Java(TM) SE 7</b>\*(Aq \e\fR +\fB\-bottom \*(Aq<font size="\-1">\fR +\fB<a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fR +\fBCopyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&.<br/>\fR +\fBOracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fR +\fBOther names may be trademarks of their respective owners\&.</font>\*(Aq \e\fR +\fB\-group "Core Packages" "java\&.*:com\&.sun\&.java\&.*:org\&.omg\&.*" \e\fR +\fB\-group "Extension Packages" "javax\&.*" \e\fR +\fB\-J\-Xmx180m \e \fR +\fB@packages\fR + +.fi +.if n \{\ +.RE +.\} +.PP +プログラマティック・インタフェース +.PP +Javadoc Access APIでは、新しいプロセスを実行しなくても、JavadocツールをJavaアプリケーションから直接起動できます。 +.PP +たとえば、次の文はコマンド\fBjavadoc \-d /home/html \-sourcepath /home/src \-subpackages java \-exclude java\&.net:java\&.lang com\&.example\fRと同等です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport javax\&.tools\&.DocumentationTool;\fR +\fBimport javax\&.tools\&.ToolProvider;\fR + +\fBpublic class JavaAccessSample{\fR +\fB public static void main(String[] args){\fR +\fB DocumentationTool javadoc = ToolProvider\&.getSystemDocumentationTool();\fR +\fB int rc = javadoc\&.run( null, null, null,\fR +\fB "\-d", "/home/html",\fR +\fB "\-sourcepath", "home/src",\fR +\fB "\-subpackages", "java",\fR +\fB "\-exclude", "java\&.net:java\&.lang",\fR +\fB "com\&.example");\fR +\fB }\fR +\fB }\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBrun\fRメソッドの最初の3つの引数は、入力、標準出力、および標準エラー・ストリームを指定します。\fBNull\fRは\fBSystem\&.in\fR、\fBSystem\&.out\fRおよび\fBSystem\&.err\fRそれぞれのデフォルト値です。 +.SS "makefileの例" +.PP +ここでは、GNU +\fBmakefile\fRの例を示します。\fBmakefile\fRの引数は、一重引用符で囲みます。Windows +\fBmakefile\fRの例については、Javadoc FAQの\fBmakefiles\fRのセクション +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137483\&.html#makefiles)を参照してください +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavadoc \-sourcepath $(SRCDIR) \e /* Sets path for source files */\fR +\fB \-overview $(SRCDIR)/overview\&.html \e /* Sets file for overview text */\fR +\fB \-d /java/jdk/build/api \e /* Sets destination directory */\fR +\fB \-use \e /* Adds "Use" files */\fR +\fB \-splitIndex \e /* Splits index A\-Z */\fR +\fB \-windowtitle $(WINDOWTITLE) \e /* Adds a window title */\fR +\fB \-doctitle $(DOCTITLE) \e /* Adds a doc title */\fR +\fB \-header $(HEADER) \e /* Adds running header text */\fR +\fB \-bottom $(BOTTOM) \e /* Adds text at bottom */\fR +\fB \-group $(GROUPCORE) \e /* 1st subhead on overview page */\fR +\fB \-group $(GROUPEXT) \e /* 2nd subhead on overview page */\fR +\fB \-J\-Xmx180m \e /* Sets memory to 180MB */\fR +\fB java\&.lang java\&.lang\&.reflect \e /* Sets packages to document */\fR +\fB java\&.util java\&.io java\&.net \e\fR +\fB java\&.applet\fR +\fB \fR +\fBWINDOWTITLE = \*(AqJava(TM) SE 7 API Specification\*(Aq\fR +\fBDOCTITLE = \*(AqJava(TM) Platform Standard Edition 7 API Specification\*(Aq\fR +\fBHEADER = \*(Aq<b>Java(TM) SE 7</font>\*(Aq\fR +\fBBOTTOM = \*(Aq<font size="\-1">\fR +\fB <a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fR +\fB Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&.<br/>\fR +\fB Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fR +\fB Other names may be trademarks of their respective owners\&.</font>\*(Aq\fR +\fBGROUPCORE = \*(Aq"Core Packages" "java\&.*:com\&.sun\&.java\&.*:org\&.omg\&.*"\*(Aq\fR +\fBGROUPEXT = \*(Aq"Extension Packages" "javax\&.*"\*(Aq\fR +\fBSRCDIR = \*(Aq/java/jdk/1\&.7\&.0/src/share/classes\*(Aq\fR + +.fi +.if n \{\ +.RE +.\} +.SS "注意" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-windowtitle\fRオプションを省略すると、\fBjavadoc\fRコマンドによってドキュメント・タイトルがウィンドウ・タイトルにコピーされます。\fB\-windowtitle\fRオプションのテキストは、\fB\-doctitle\fRオプションと同じですが、HTMLタグは含まれません。これは、HTMLタグが、ウィンドウ・タイトル内にそのままのテキストとして表示されるのを防ぐためです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-footer\fRオプションを省略すると、\fBjavadoc\fRコマンドによってヘッダー・テキストがフッターにコピーされます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +この例では必要ありませんが、\fB\-classpath\fRと\fB\-link\fRも重要なオプションです。 +.RE +.SH "一般的なトラブルシューティング" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjavadoc\fRコマンドは有効なクラス名を含むファイルのみを読み取ります。\fBjavadoc\fRコマンドがファイルの内容を正しく読み取っていない場合は、クラス名が有効であることを確認します。ソース・ファイルの処理を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +一般的なbugおよびトラブルシューティングのヒントについては、Javadoc FAQ +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137483\&.html)を参照してください。 +.RE +.SH "エラーと警告" +.PP +エラーおよび警告メッセージには、ファイル名と宣言行(ドキュメンテーション・コメント内の特定の行ではない)の行番号が含まれます。 +.PP +たとえば、メッセージ\fB「エラー: Class1\&.javaを読み込めません」\fRは、\fBjavadoc\fRコマンドが\fBClass1\&.jav\fR\fBa\fRを現在のディレクトリにロードしようとしていることを意味します。クラス名はそのパス(絶対または相対)で表示されます。 +.SH "環境" +.PP +CLASSPATH +.RS 4 +\fBCLASSPATH\fRは、\fBjavadoc\fRコマンドがユーザー・クラス・ファイルの検出に使用するパスを提供する環境変数です。この環境変数は、\fB\-classpath\fRオプションによってオーバーライドされます。ディレクトリはセミコロン(Windowsの場合)またはコロン(Oracle Solarisの場合)で区切ります。 +.sp +\fBWindowsの例\fR: +\fB\&.;C:\eclasses;C:\ehome\ejava\eclasses\fR +.sp +\fBOracle Solarisの例\fR: +\fB\&.:/home/classes:/usr/local/java/classes\fR +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.SH "関連ドキュメント" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Javadocテクノロジ +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/index\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラスの検出方法 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JavadocツールでのDocコメントの記述方法 +(http://www\&.oracle\&.com/technetwork/java/javase/documentation/index\-137868\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +URLメモ、Uniform Resource Locators +(http://www\&.ietf\&.org/rfc/rfc1738\&.txt) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +HTML標準、HTML Document Representation (4197265および4137321) +(http://www\&.w3\&.org/TR/REC\-html40/charset\&.html#h\-5\&.2\&.2) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javafxpackager.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javafxpackager.1 new file mode 100755 index 0000000..93b2be0 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javafxpackager.1 @@ -0,0 +1,937 @@ +'\" t +.\" Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javafxpackager +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javafxpackager" "1" "2015å¹´3月3日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javafxpackager \- \fB注意:\fR このツールの名前は\fBjavapackager\fRに変更されています。\fBjavafxpackager\&.exe\fRファイルは、将来のリリースで削除される可能性があります。\fBjavapackager\fRを使用するように、スクリプトを更新してください。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager\fR \fIcommand\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommand\fR +.RS 4 +実行する必要のあるタスク。 +.RE +.PP +options +.RS 4 +空白で区切られた1つ以上のコマンド・オプション。 +.RE +.SH "コマンド" +.PP +次のいずれかのコマンドを指定できます。コマンドの後に、そのオプションを指定します。 +.PP +\-createbss +.RS 4 +CSSファイルをバイナリ形式に変換します。 +.RE +.PP +\-createjar +.RS 4 +他のパラメータに従ってJARアーカイブを作成します。 +.RE +.PP +\-deploy +.RS 4 +再配布用のアプリケーション・パッケージを組み立てます。デプロイ・タスクでは、デフォルトでベース・アプリケーション・パッケージが生成されますが、指定すれば自己完結型アプリケーション・パッケージも生成できます。 +.RE +.PP +\-makeall +.RS 4 +1つの呼出しで、ほとんどの引数が事前定義されたコンパイル、\fBcreatejar\fRおよび\fBdeploy\fRステップを実行し、すべての該当する自己完結型アプリケーション・パッケージの生成を試行します。ソース・ファイルは\fBsrc\fRというフォルダに配置する必要があり、生成されるファイル(JAR、JNLP、HTMLおよび自己完結型アプリケーション・パッケージ)は\fBdist\fRというフォルダに出力されます。このコマンドでは最小限の構成のみが可能で、可能な限り自動化されています。 +.RE +.PP +\-signjar +.RS 4 +指定した証明書でJARファイルに署名します。 +.RE +.SH "CREATEBSSコマンドのオプション" +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "CREATEJARコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +\fB<fx:argument>\fR要素としてJNLPファイルに挿入される名前なし引数。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-manifestAttrs \fImanifest\-attributes\fR +.RS 4 +追加のマニフェスト属性の名前と値のリスト。構文: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1=value1,name2=value2,name3=value3"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-nocss2bin +.RS 4 +パッケージャはJARにコピーする前にCSSファイルをバイナリ形式に変換しません。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "DEPLOYコマンドのオプション" +.PP +\-allpermissions +.RS 4 +指定した場合、JNLPファイル内のすべてのセキュリティ権限がアプリケーションに必要になります。 +.RE +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +JNLPファイルの\fB<fx:argument>\fR要素に挿入される名前なし引数。 +.RE +.PP +\-B\fIbundler\-argument=value\fR +.RS 4 +自己完結型アプリケーションのパッケージ化に使用するバンドラへの情報を指定します。各バンドラの引数の詳細は、自己完結型アプリケーション・バンドラの引数を参照してください。 +.RE +.PP +\-callbacks +.RS 4 +生成後のHTMLでのユーザー・コールバック方式を指定します。形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1:value1,name2:value2,\&.\&.\&."\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-description \fIdescription\fR +.RS 4 +アプリケーションの説明。 +.RE +.PP +\-embedCertificates +.RS 4 +指定した場合、証明書がJNLPファイルに埋め込まれます。 +.RE +.PP +\-embedjnlp +.RS 4 +指定した場合、JNLPファイルがHTMLドキュメントに埋め込まれます。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-htmlparamfile \fIfile\fR +.RS 4 +生成されるアプリケーションをブラウザで実行する場合のパラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-isExtension +.RS 4 +指定した場合、\fBsrcfiles\fRは拡張ファイルとして処理されます。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-native \fItype\fR +.RS 4 +自己完結型アプリケーション・バンドルを生成します(可能な場合)。\fB\-B\fRオプションを使用して、使用されているバンドラへの引数を指定します。\fItype\fRを指定すると、このタイプのバンドルのみが作成されます。タイプを指定しない場合、\fBall\fRが使用されます。 +.sp +\fItype\fRには、次の値が有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBall\fR: 実行されているプラットフォームのインストーラをすべて実行し、そのアプリケーションのディスク・イメージを作成します。\fItype\fRが指定されていない場合、この値が使用されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBinstaller\fR: 実行されているプラットフォームのインストーラをすべて実行します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBimage\fR: アプリケーションのディスク・イメージを作成します。OS Xでは、イメージは\fB\&.app\fRファイルです。Linuxでは、イメージはインストールされるディレクトリです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdmg\fR: OS X用のDMGファイルを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpkg\fR: OS X用の\fB\&.pkg\fRパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmac\&.appStore\fR: Mac App Store用のパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBrpm\fR: Linux用のRPMパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdeb\fR: Linux用のDebianパッケージを生成します。 +.RE +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-templateId +.RS 4 +テンプレート処理を行うアプリケーションのアプリケーションID。 +.RE +.PP +\-templateInFilename +.RS 4 +HTMLテンプレート・ファイルの名前。プレースホルダの形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#XXXX\&.YYYY(APPID)#\fR + +.fi +.if n \{\ +.RE +.\} +APPIDはアプリケーションの識別子であり、XXXは次のいずれかです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.URL\fR +.sp +Deployment Toolkitのdtjava\&.jsの場所。デフォルトでは、この場所は次のとおりです。 +.sp +http://java\&.com/js/dtjava\&.js +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.CODE\fR +.sp +Deployment Toolkitのdtjava\&.jsを含めるスクリプト要素。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.DYNAMIC\fR +.sp +特定のプレースホルダにアプリケーションを埋め込むコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.ONLOAD\fR +.sp +\fBonload\fRフックを使用してWebページにアプリケーションを埋め込むために必要なすべてのコード(dtjava\&.jsのインクルードを除く)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.LAUNCH\&.CODE\fR +.sp +アプリケーションの起動に必要なコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.RE +.PP +\-templateOutFilename +.RS 4 +テンプレートから生成されるHTMLファイルの名前。 +.RE +.PP +\-title \fItitle\fR +.RS 4 +アプリケーションのタイトル。 +.RE +.PP +\-vendor \fIvendor\fR +.RS 4 +アプリケーションのベンダー。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.PP +\-updatemode \fIupdate\-mode\fR +.RS 4 +JNLPファイルの更新モードを設定します。 +.RE +.SH "MAKEALLコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.SH "SIGNJARコマンドのオプション" +.PP +\-alias +.RS 4 +キーの別名。 +.RE +.PP +\-keyPass +.RS 4 +キーを復元するためのパスワード。 +.RE +.PP +\-keyStore \fIfile\fR +.RS 4 +キーストア・ファイル名。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +署名するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-storePass +.RS 4 +キーストアの整合性を確認したり、ロックを解除するためのパスワード。 +.RE +.PP +\-storeType +.RS 4 +キーストアのタイプ。デフォルト値は"jks"です。 +.RE +.SH "自己完結型アプリケーション・バンドラの引数" +.PP +自己完結型アプリケーションの作成に使用されるバンドラの引数を指定するには、\fB\-deploy\fRコマンドの\fB\-B\fRオプションを使用します。各バンドラ・タイプに、独自の引数セットがあります。 +.SS "一般的なバンドラ引数" +.PP +appVersion=\fIversion\fR +.RS 4 +アプリケーション・パッケージのバージョン。一部のバンドラでは、バージョン文字列の形式が制限されます。 +.RE +.PP +classPath=\fIpath\fR +.RS 4 +アセンブルされたアプリケーション・ディレクトリへの相対的なクラス・パス。一般的に、パスはJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +icon=\fIpath\fR +.RS 4 +起動ツールおよびその他の支援ツールに使用されるデフォルト・アイコンの場所。OS Xの場合、形式は\fB\&.icns\fRである必要があります。Linuxの場合、形式は\fB\&.png\fRである必要があります。 +.RE +.PP +identifier=\fIvalue\fR +.RS 4 +\fBmac\&.CFBundleIdentifier\fRなど、他のプラットフォーム固有の値に使用されるデフォルト値。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +jvmOptions=\fIoption\fR +.RS 4 +アプリケーションの実行時にJVMに渡されるオプション。\fBjava\fRコマンドに有効なオプションを使用できます。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmOptions=\-Xmx128m \-BjvmOptions=\-Xms128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +jvmProperties=\fIproperty\fR=\fIvalue\fR +.RS 4 +アプリケーションの実行時にVMに渡されるJavaシステム・プロパティ。\fBjava\fRコマンドの\fB\-D\fRオプションに有効なプロパティを使用できます。プロパティ名とそのプロパティの値の両方を指定します。複数のプロパティを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmProperties=apiUserName=example \-BjvmProperties=apiKey=abcdef1234567890\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +mainJar=\fIfilename\fR +.RS 4 +アプリケーションのメイン・クラスを含むJARファイルの名前。一般的に、ファイル名はJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +preferencesID=\fInode\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプションを確認するために調べるプリファレンス・ノード。指定したノードは、オプション\fB\-Dapp\&.preferences\&.id\fRとして実行時にアプリケーションに渡されます。この引数は、\fBuserJVMOptions\fR引数とともに使用されます。 +.RE +.PP +runtime=\fIpath\fR +.RS 4 +パッケージ・バンドルに含めるJREまたはJDKの場所。JDKまたはJREのルート・フォルダへのファイル・パスを指定します。システム・デフォルトJREを使用するには、次の例に示すようにパスを指定しないでください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Bruntime=\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +userJvmOptions=\fIoption\fR=\fIvalue\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプション。\fBjava\fRコマンドに有効なオプションを使用できます。オプション名とそのオプションの値の両方を指定します。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BuserJvmOptions=\-Xmx=128m \-BuserJvmOptions=\-Xms=128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SS "OS Xアプリケーション・バンドラ引数" +.PP +mac\&.category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。カテゴリは、Apple Developer Webサイトにあるカテゴリ・リスト内に含まれている必要があります。 +.RE +.PP +mac\&.CFBundleIdentifier=\fIvalue\fR +.RS 4 +\fBCFBundleIdentifier\fRの情報plistに格納されている値。この値は、グローバルに一意である必要があり、文字、数字、ドットおよびダッシュのみを含む必要があります。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +mac\&.CFBundleName=\fIname\fR +.RS 4 +OS Xメニュー・バーに表示されるアプリケーションの名前。16文字未満の名前をお薦めします。デフォルトは名前属性です。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-app=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.bundle\-id\-signing\-prefix=\fIprefix\fR +.RS 4 +plistまたは既存の署名がないバイナリがバンドル内に見つかった場合に署名済バイナリに適用される接頭辞。 +.RE +.SS "OS X DMG (ディスク・イメージ)バンドラ引数" +.PP +ディスク・イメージがマウント可能になる前に、OS X DMGインストーラは、\fBlicenseFile\fRによって指定されているライセンス・ファイル(指定されている場合)を表示します。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +systemWide=\fIboolean\fR +.RS 4 +使用対象のドラッグしてインストールするターゲットを示すフラグ。アプリケーション・フォルダを表示するには、\fBtrue\fRに設定します。デスクトップ・フォルダを表示するには、\fBfalse\fRに設定します。デフォルトは\fBtrue\fRです。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.dmg\&.simple=\fIboolean\fR +.RS 4 +AppleScriptコードの実行に依存するDMGカスタマイズ手順をスキップするかどうかを示すフラグ。\fBtrue\fRに設定して、手順をスキップします。\fBtrue\fRに設定されている場合、ディスク・ウィンドウにバックグラウンド・イメージがないため、アイコンが所定の位置に移動しません。\fBsystemWide\fR引数も\fBtrue\fRに設定されている場合、ルート・アプリケーション・フォルダのシンボリック・リンクがDMGファイルに追加されます。\fBsystemWide\fR引数が\fBfalse\fRに設定されている場合、アプリケーションのみがDMGファイルに追加され、デスクトップのリンクは追加されません。 +.RE +.SS "OS X PKGバンドラ引数" +.PP +OS X PKGインストーラは、ウィザードを示し、\fBlicenseFile\fRによって指定されているライセンス・ファイルをウィザード内のページに表示します。ユーザーはアプリケーションをインストールする前に条件に同意する必要があります。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-installer=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.SS "Mac App Storeバンドラ引数" +.PP +mac\&.app\-store\-entitlements=\fIpath\fR +.RS 4 +アプリケーションが動作する資格を含むファイルの場所。ファイルは、Appleによって指定されている形式である必要があります。ファイルへのパスは、絶対条件で指定することも、\fBjavapackager\fRの呼出しに対して相対的に指定することもできます。資格を指定しない場合、アプリケーションは、通常のアプレット・サンドボックスよりもより厳しいサンドボックスで動作し、ネットワーク・ソケットおよびすべてのファイルへのアクセスが拒否されます。 +.RE +.PP +mac\&.signing\-key\-app=\fIkey\fR +.RS 4 +Mac App Storeのアプリケーション署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.signing\-key\-pkg=\fIkey\fR +.RS 4 +Mac App Storeのインストーラ署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.SS "Linux Debianバンドラ引数" +.PP +\fBlicenseFile\fRによって指定されているライセンス・ファイルは、すべてのケースにおいてユーザーに示されませんが、ファイルはアプリケーション・メタデータに含まれています。 +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +copyright=\fIstring\fR +.RS 4 +アプリケーションのコピーライト文字列。この引数は、Debianメタデータで使用されます。 +.RE +.PP +email=\fIaddress\fR +.RS 4 +DebianのMaintainerフィールドで使用される電子メール・アドレスです。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。この引数は、DebianのMaintainerフィールドで使用されます。 +.RE +.SS "Linux RPMバンドラ引数" +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。 +.RE +.SH "非推奨オプション" +.PP +次のオプションは、パッケージ化ツールで使用されておらず、存在していても無視されます。 +.PP +\-runtimeversion \fIversion\fR +.RS 4 +必要なJavaFXランタイムのバージョン。非推奨。 +.RE +.PP +\-noembedlauncher +.RS 4 +指定した場合、パッケージャはJARファイルにJavaFX起動クラスを追加しません。非推奨。 +.RE +.SH "注意" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +タスク・コマンドとともに\fB\-v \fRオプションを使用すれば、詳細な出力が有効になります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-srcdir\fRオプションをコマンドで使用できる場合は、複数回使用できます。\fB\-srcfiles\fRオプションを指定すると、引数に指定されたファイル名が、その前に指定されている\fBsrcdir\fRオプションで指定された場所で検索されます。\fB\-srcdir\fRが\fB\-srcfiles\fRの前に指定されていない場合は、\fBjavapackager\fRコマンドが実行されるディレクトリが使用されます。 +.RE +.SH "例" +.PP +\fB例 1 \fR\-createjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-createjar \-appclass package\&.ClassName\fR +\fB \-srcdir classes \-outdir out \-outfile outjar \-v\fR + +.fi +.if n \{\ +.RE +.\} +\fBclasses\fRディレクトリの内容を\fBoutjar\&.jar\fRにパッケージ化して、アプリケーション・クラスを\fBpackage\&.ClassName\fRに設定します。 +.RE +.PP +\fB例 2 \fR\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fR +\fB \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fR + +.fi +.if n \{\ +.RE +.\} +\fBoutfile\&.jnlp\fRおよび対応する\fBoutfile\&.html\fRファイルをアプリケーション\fBAppName\fRの\fBoutdir\fRに生成します。これは\fBpackage\&.ClassName\fRで開始し、34 x 43ピクセルのサイズです。 +.RE +.PP +\fB例 3 \fR\-makeallコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fR +\fB\-height 600\fR + +.fi +.if n \{\ +.RE +.\} +コンパイルを含むすべてのパッケージ化作業(\fBcreatejar\fRおよび\fBdeploy\fR)を実行します。 +.RE +.PP +\fB例 4 \fR\-signjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fR +\fB\-alias duke \-keypass **** \-srcdir dist\fR + +.fi +.if n \{\ +.RE +.\} +\fBdist\fRディレクトリにあるすべてのJARファイルに署名し、alias、\fBkeyStore\fRおよび\fBstorePass\fRを指定して証明書を添付し、署名されたJARファイルを\fBdist\fRディレクトリに戻します。 +.RE +.PP +\fB例 5 \fRバンドラ引数を伴う\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-native deb \-Bcategory=Education \-BjvmOptions=\-Xmx128m \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB \-BjvmOptions=\-Xms128m \-outdir packages \-outfile BrickBreaker \-srcdir dist \fR +\fB \-srcfiles BrickBreaker\&.jar \-appclass brickbreaker\&.Main \-name BrickBreaker \fR +\fB \-title "BrickBreaker demo"\fR + +.fi +.if n \{\ +.RE +.\} +自己完結型アプリケーションとしてBrickBreakerアプリケーションを実行するためのネイティブLinux Debianパッケージを生成します。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javah.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javah.1 new file mode 100755 index 0000000..f358e9b --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javah.1 @@ -0,0 +1,203 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javah +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javah" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javah \- JavaクラスからCヘッダーとソース・ファイルを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavah\fR [ \fIoptions\fR ] f\fIully\-qualified\-class\-name \&.\&.\&.\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIfully\-qualified\-class\-name\fR +.RS 4 +Cヘッダーとソース・ファイルに変換されるクラスの完全修飾された場所。 +.RE +.SH "説明" +.PP +\fBjavah\fRコマンドは、ネイティブ・メソッドを実装するために必要なCヘッダーとソース・ファイルを生成します。作成されたヘッダーとソース・ファイルは、ネイティブ・ソース・コードからオブジェクトのインスタンス変数を参照するためにCプログラムによって使用されます。\fB\&.h\fRファイルは、対応するクラスと一致する配置を持つ\fBstruct\fR定義を含みます。\fBstruct\fRのフィールドは、クラスのインスタンス変数に対応します。 +.PP +ヘッダー・ファイルとその中で宣言される構造体の名前はクラスの名前から派生します。\fBjavah\fRコマンドに渡されるクラスがパッケージの中にある場合、パッケージ名はヘッダー・ファイル名と構造体名の両方の先頭に付加されます。下線(_)が名前の区切り文字として使用されます。 +.PP +デフォルトでは\fBjavah\fRコマンドは、コマンド行にリストされる各クラスのヘッダー・ファイルを作成し、現在のディレクトリにファイルを置きます。ソース・ファイルを作成するには、\fB\-stubs\fRオプションを使用してください。1つのファイルの中に、リストされたすべてのクラスの結果を連結するには、\fB\-o\fRオプションを使用してください。 +.PP +Java Native Interface (JNI)はヘッダー情報またはスタブ・ファイルを必要としません。\fBjavah\fRコマンドは引き続きJNI形式のネイティブ・メソッドに必要なネイティブ・メソッド関数プロトタイプの生成に使用できます。\fBjavah\fRコマンドはデフォルトでJNI形式の出力を生成し、その結果を\fB\&.h\fRファイルに格納します。 +.SH "オプション" +.PP +\-o \fIoutputfile\fR +.RS 4 +コマンドラインにリストされたすべてのクラスに対して、結果のヘッダーまたはソース・ファイルを連結して出力ファイルに格納します。\fB\-o\fRまたは\fB\-d\fRのどちらかのみ使用できます。 +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +\fBjavah\fRがヘッダー・ファイルまたはスタブ・ファイルを保存する、ディレクトリを設定します。\fB\-d\fRまたは\fB\-o\fRのどちらかのみ使用できます。 +.RE +.PP +\-stubs +.RS 4 +\fBjavah\fRコマンドが、Javaオブジェクト・ファイルからC宣言を生成します。 +.RE +.PP +\-verbose +.RS 4 +詳細出力を指定し、作成ファイルの状態に関するメッセージを、\fBjavah\fRコマンドが\fB標準出力\fRに出力します。 +.RE +.PP +\-help +.RS 4 +\fBjavah\fRの使用方法についてのヘルプ・メッセージを出力します。 +.RE +.PP +\-version +.RS 4 +\fBjavah\fRコマンドのリリース情報を出力します。 +.RE +.PP +\-jni +.RS 4 +JNI形式のネイティブ・メソッド機能プロトタイプを含む出力ファイルを、\fBjavah\fRコマンドが作成します。これは標準出力であるため、\fB\-jni\fRの使用はオプションです。 +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +クラスを探すために\fBjavah\fRコマンドが使用するパスを指定します。デフォルトまたは\fBCLASSPATH\fR環境変数の設定をオーバーライドします。ディレクトリはOracle Solarisの場合はコロンで、Windowsの場合はセミコロンで区切られます。パスの一般的な形式は次のようになります。 +.sp +\fBOracle Solaris\fRの場合: +.sp +\&.:\fIyour\-path\fR +.sp +例: +\fB\&.:/home/avh/classes:/usr/local/java/classes\fR +.sp +\fBWindows\fRの場合: +.sp +\&.;\fIyour\-path\fR +.sp +例: +\fB\&.;C:\eusers\edac\eclasses;C:\etools\ejava\eclasses\fR +.sp +便宜上、*のベース名を含むクラス・パス要素は、\fB\&.jar\fRまたは\fB\&.JAR\fRを拡張子に持つディレクトリ内のすべてのファイルのリストを指定するのと同等とみなされます。 +.sp +たとえば、ディレクトリ\fBmydir\fRに\fBa\&.jar\fRと\fBb\&.JAR\fRが含まれている場合、クラス・パス要素\fBmydir/*\fRは\fBA\fR\fB\&.jar:b\&.JAR\fRに展開されますが、JARファイルの順番は未指定となります。このリストには、隠しファイルも含め、指定されたディレクトリ内のすべてのJARファイルが含まれます。*からなるクラス・パス・エントリは、現在のディレクトリ内のすべてのJARファイルのリストに展開されます。\fBCLASSPATH\fR環境変数も、定義時には同様に展開されます。クラス・パスのワイルドカードの展開は、Java Virtual Machine (JVM)の開始前に行われます。Javaプログラムは、環境を問い合せる場合を除き、展開されていないワイルドカードを参照しません。たとえば、\fBSystem\&.getenv("CLASSPATH")\fRをコールして問い合せる場合です。 +.RE +.PP +\-bootclasspath \fIpath\fR +.RS 4 +ブートストラップ・クラスをロードするパスを指定します。ブートストラップ・クラスは、デフォルトでは\fBjre\elib\ert\&.jar\fRおよび他のいくつかのJARファイルにある、コアJavaプラットフォームを実装するクラスです。 +.RE +.PP +\-old +.RS 4 +古いJDK 1\&.0形式のヘッダー・ファイルを生成するように指定します。 +.RE +.PP +\-force +.RS 4 +出力ファイルが常に書き込まれるように指定します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javap.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javap.1 new file mode 100755 index 0000000..5fa61dc --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javap.1 @@ -0,0 +1,348 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javap +.\" Language: Japanese +.\" Date: 2014å¹´8月8日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javap" "1" "2014å¹´8月8日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javap \- 1つ以上のクラス・ファイルを逆アセンブルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavap\fR [\fIoptions\fR] \fIclassfile\fR\&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclassfile\fR +.RS 4 +注釈の処理対象となる、空白で区切った1つ以上のクラス(DocFooter\&.classなど)。クラス・パスで検出できるクラスを、ファイル名またはURL(\fBfile:///home/user/myproject/src/DocFooter\&.class\fRなど)で指定できます。 +.RE +.SH "説明" +.PP +\fBjavap\fRコマンドは、1つまたは複数のクラス・ファイルを逆アセンブルします。その出力は指定するオプションにより異なります。オプションを指定しない場合、\fBjavap\fRコマンドは、そのパッケージ、渡されたクラスのprotectedおよびpublicのフィールドとメソッドを出力します。\fBjavap\fRコマンドはその出力を\fB標準出力\fRに表示します。 +.SH "オプション" +.PP +\-help +.br +\-\-help +.br +\-? +.RS 4 +\fBjavap\fRコマンドについてのヘルプ・メッセージを出力します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-l +.RS 4 +行番号とローカル変数表を出力します。 +.RE +.PP +\-public +.RS 4 +publicクラスおよびメンバーのみ表示します。 +.RE +.PP +\-protected +.RS 4 +protectedおよびpublicのクラスとメンバーのみを表示します。 +.RE +.PP +\-private +.br +\-p +.RS 4 +すべてのクラスとメンバーを表示します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定されたオプションをJVMに渡します。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavap \-J\-version\fR +\fBjavap \-J\-Djava\&.security\&.manager \-J\-Djava\&.security\&.policy=MyPolicy MyClassName\fR + +.fi +.if n \{\ +.RE +.\} +JVMオプションの詳細は、コマンドのマニュアルを参照してください。 +.RE +.PP +\-s +.RS 4 +内部の型シグニチャを出力します。 +.RE +.PP +\-sysinfo +.RS 4 +処理中のクラスのシステム情報(パス、サイズ、日付、MD5ハッシュ)を表示します。 +.RE +.PP +\-constants +.RS 4 +\fBstatic final\fR定数を表示します。 +.RE +.PP +\-c +.RS 4 +クラスの各メソッドのために逆アセンブルされるコード、すなわちJavaバイトコードからなる命令を表示します。 +.RE +.PP +\-verbose +.RS 4 +メソッドのスタック・サイズ、localsとargumentsの数を出力します。 +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +クラスを探すために\fBjavap\fRコマンドが使用するパスを指定します。デフォルトまたは\fBCLASSPATH\fR環境変数の設定を上書きします。 +.RE +.PP +\-bootclasspath \fIpath\fR +.RS 4 +ブートストラップ・クラスをロードするパスを指定します。ブートストラップ・クラスは、デフォルトでは\fBjre/lib/rt\&.jar\fRおよび他のいくつかのJARファイルにある、コアJavaプラットフォームを実装するクラスです。 +.RE +.PP +\-extdir \fIdirs\fR +.RS 4 +インストールされた拡張機能を検索する場所をオーバーライドします。拡張機能のデフォルト位置は\fBjava\&.ext\&.dirs\fRです。 +.RE +.SH "例" +.PP +次の\fBDocFooter\fRクラスをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.awt\&.*;\fR +\fBimport java\&.applet\&.*;\fR +\fB \fR +\fBpublic class DocFooter extends Applet {\fR +\fB String date;\fR +\fB String email;\fR +\fB \fR +\fB public void init() {\fR +\fB resize(500,100);\fR +\fB date = getParameter("LAST_UPDATED");\fR +\fB email = getParameter("EMAIL");\fR +\fB }\fR +\fB \fR +\fB public void paint(Graphics g) {\fR +\fB g\&.drawString(date + " by ",100, 15);\fR +\fB g\&.drawString(email,290,15);\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavap DocFooter\&.class\fRコマンドからの出力は次を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompiled from "DocFooter\&.java"\fR +\fBpublic class DocFooter extends java\&.applet\&.Applet {\fR +\fB java\&.lang\&.String date;\fR +\fB java\&.lang\&.String email;\fR +\fB public DocFooter();\fR +\fB public void init();\fR +\fB public void paint(java\&.awt\&.Graphics);\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjavap \-c DocFooter\&.class\fRコマンドからの出力は次を生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompiled from "DocFooter\&.java"\fR +\fBpublic class DocFooter extends java\&.applet\&.Applet {\fR +\fB java\&.lang\&.String date;\fR +\fB java\&.lang\&.String email;\fR + +\fB public DocFooter();\fR +\fB Code:\fR +\fB 0: aload_0 \fR +\fB 1: invokespecial #1 // Method\fR +\fBjava/applet/Applet\&."<init>":()V\fR +\fB 4: return \fR + +\fB public void init();\fR +\fB Code:\fR +\fB 0: aload_0 \fR +\fB 1: sipush 500\fR +\fB 4: bipush 100\fR +\fB 6: invokevirtual #2 // Method resize:(II)V\fR +\fB 9: aload_0 \fR +\fB 10: aload_0 \fR +\fB 11: ldc #3 // String LAST_UPDATED\fR +\fB 13: invokevirtual #4 // Method\fR +\fB getParameter:(Ljava/lang/String;)Ljava/lang/String;\fR +\fB 16: putfield #5 // Field date:Ljava/lang/String;\fR +\fB 19: aload_0 \fR +\fB 20: aload_0 \fR +\fB 21: ldc #6 // String EMAIL\fR +\fB 23: invokevirtual #4 // Method\fR +\fB getParameter:(Ljava/lang/String;)Ljava/lang/String;\fR +\fB 26: putfield #7 // Field email:Ljava/lang/String;\fR +\fB 29: return \fR + +\fB public void paint(java\&.awt\&.Graphics);\fR +\fB Code:\fR +\fB 0: aload_1 \fR +\fB 1: new #8 // class java/lang/StringBuilder\fR +\fB 4: dup \fR +\fB 5: invokespecial #9 // Method\fR +\fB java/lang/StringBuilder\&."<init>":()V\fR +\fB 8: aload_0 \fR +\fB 9: getfield #5 // Field date:Ljava/lang/String;\fR +\fB 12: invokevirtual #10 // Method\fR +\fB java/lang/StringBuilder\&.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;\fR +\fB 15: ldc #11 // String by \fR +\fB 17: invokevirtual #10 // Method\fR +\fB java/lang/StringBuilder\&.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;\fR +\fB 20: invokevirtual #12 // Method\fR +\fB java/lang/StringBuilder\&.toString:()Ljava/lang/String;\fR +\fB 23: bipush 100\fR +\fB 25: bipush 15\fR +\fB 27: invokevirtual #13 // Method\fR +\fB java/awt/Graphics\&.drawString:(Ljava/lang/String;II)V\fR +\fB 30: aload_1 \fR +\fB 31: aload_0 \fR +\fB 32: getfield #7 // Field email:Ljava/lang/String;\fR +\fB 35: sipush 290\fR +\fB 38: bipush 15\fR +\fB 40: invokevirtual #13 // Method\fR +\fBjava/awt/Graphics\&.drawString:(Ljava/lang/String;II)V\fR +\fB 43: return \fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdeps(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javapackager.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javapackager.1 new file mode 100755 index 0000000..47b10bb --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javapackager.1 @@ -0,0 +1,937 @@ +'\" t +.\" Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javapackager +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javapackager" "1" "2015å¹´3月3日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javapackager \- JavaおよびJavaFXアプリケーションのパッケージ化と署名に関連するタスクを実行します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager\fR \fIcommand\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommand\fR +.RS 4 +実行する必要のあるタスク。 +.RE +.PP +options +.RS 4 +空白で区切られた1つ以上のコマンド・オプション。 +.RE +.SH "コマンド" +.PP +次のいずれかのコマンドを指定できます。コマンドの後に、そのオプションを指定します。 +.PP +\-createbss +.RS 4 +CSSファイルをバイナリ形式に変換します。 +.RE +.PP +\-createjar +.RS 4 +他のパラメータに従ってJARアーカイブを作成します。 +.RE +.PP +\-deploy +.RS 4 +再配布用のアプリケーション・パッケージを組み立てます。デプロイ・タスクでは、デフォルトでベース・アプリケーション・パッケージが生成されますが、指定すれば自己完結型アプリケーション・パッケージも生成できます。 +.RE +.PP +\-makeall +.RS 4 +1つの呼出しで、ほとんどの引数が事前定義されたコンパイル、\fBcreatejar\fRおよび\fBdeploy\fRステップを実行し、すべての該当する自己完結型アプリケーション・パッケージの生成を試行します。ソース・ファイルは\fBsrc\fRというフォルダに配置する必要があり、生成されるファイル(JAR、JNLP、HTMLおよび自己完結型アプリケーション・パッケージ)は\fBdist\fRというフォルダに出力されます。このコマンドでは最小限の構成のみが可能で、可能な限り自動化されています。 +.RE +.PP +\-signjar +.RS 4 +指定した証明書でJARファイルに署名します。 +.RE +.SH "CREATEBSSコマンドのオプション" +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "CREATEJARコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +\fB<fx:argument>\fR要素としてJNLPファイルに挿入される名前なし引数。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-manifestAttrs \fImanifest\-attributes\fR +.RS 4 +追加のマニフェスト属性の名前と値のリスト。構文: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1=value1,name2=value2,name3=value3"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-nocss2bin +.RS 4 +パッケージャはJARにコピーする前にCSSファイルをバイナリ形式に変換しません。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.SH "DEPLOYコマンドのオプション" +.PP +\-allpermissions +.RS 4 +指定した場合、JNLPファイル内のすべてのセキュリティ権限がアプリケーションに必要になります。 +.RE +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-argument \fIarg\fR +.RS 4 +JNLPファイルの\fB<fx:argument>\fR要素に挿入される名前なし引数。 +.RE +.PP +\-B\fIbundler\-argument=value\fR +.RS 4 +自己完結型アプリケーションのパッケージ化に使用するバンドラへの情報を指定します。各バンドラの引数の詳細は、自己完結型アプリケーション・バンドラの引数を参照してください。 +.RE +.PP +\-callbacks +.RS 4 +生成後のHTMLでのユーザー・コールバック方式を指定します。形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1:value1,name2:value2,\&.\&.\&."\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-description \fIdescription\fR +.RS 4 +アプリケーションの説明。 +.RE +.PP +\-embedCertificates +.RS 4 +指定した場合、証明書がJNLPファイルに埋め込まれます。 +.RE +.PP +\-embedjnlp +.RS 4 +指定した場合、JNLPファイルがHTMLドキュメントに埋め込まれます。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-htmlparamfile \fIfile\fR +.RS 4 +生成されるアプリケーションをブラウザで実行する場合のパラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-isExtension +.RS 4 +指定した場合、\fBsrcfiles\fRは拡張ファイルとして処理されます。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-native \fItype\fR +.RS 4 +自己完結型アプリケーション・バンドルを生成します(可能な場合)。\fB\-B\fRオプションを使用して、使用されているバンドラへの引数を指定します。\fItype\fRを指定すると、このタイプのバンドルのみが作成されます。タイプを指定しない場合、\fBall\fRが使用されます。 +.sp +\fItype\fRには、次の値が有効です。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBall\fR: 実行されているプラットフォームのインストーラをすべて実行し、そのアプリケーションのディスク・イメージを作成します。\fItype\fRが指定されていない場合、この値が使用されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBinstaller\fR: 実行されているプラットフォームのインストーラをすべて実行します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBimage\fR: アプリケーションのディスク・イメージを作成します。OS Xでは、イメージは\fB\&.app\fRファイルです。Linuxでは、イメージはインストールされるディレクトリです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdmg\fR: OS X用のDMGファイルを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpkg\fR: OS X用の\fB\&.pkg\fRパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmac\&.appStore\fR: Mac App Store用のパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBrpm\fR: Linux用のRPMパッケージを生成します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdeb\fR: Linux用のDebianパッケージを生成します。 +.RE +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +生成されるファイルの名前(拡張子なし)。 +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +デフォルトの名前付きアプリケーション・パラメータが含まれるプロパティ・ファイル。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +パッケージ化するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-templateId +.RS 4 +テンプレート処理を行うアプリケーションのアプリケーションID。 +.RE +.PP +\-templateInFilename +.RS 4 +HTMLテンプレート・ファイルの名前。プレースホルダの形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#XXXX\&.YYYY(APPID)#\fR + +.fi +.if n \{\ +.RE +.\} +APPIDはアプリケーションの識別子であり、XXXは次のいずれかです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.URL\fR +.sp +Deployment Toolkitのdtjava\&.jsの場所。デフォルトでは、この場所は次のとおりです。 +.sp +http://java\&.com/js/dtjava\&.js +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.CODE\fR +.sp +Deployment Toolkitのdtjava\&.jsを含めるスクリプト要素。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.DYNAMIC\fR +.sp +特定のプレースホルダにアプリケーションを埋め込むコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.ONLOAD\fR +.sp +\fBonload\fRフックを使用してWebページにアプリケーションを埋め込むために必要なすべてのコード(dtjava\&.jsのインクルードを除く)。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.LAUNCH\&.CODE\fR +.sp +アプリケーションの起動に必要なコード。コードは、\fBfunction()\fRメソッドにラップされることが予想されます。 +.RE +.RE +.PP +\-templateOutFilename +.RS 4 +テンプレートから生成されるHTMLファイルの名前。 +.RE +.PP +\-title \fItitle\fR +.RS 4 +アプリケーションのタイトル。 +.RE +.PP +\-vendor \fIvendor\fR +.RS 4 +アプリケーションのベンダー。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.PP +\-updatemode \fIupdate\-mode\fR +.RS 4 +JNLPファイルの更新モードを設定します。 +.RE +.SH "MAKEALLコマンドのオプション" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +実行するアプリケーション・クラスの修飾名。 +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +依存するJARファイル名のリスト。 +.RE +.PP +\-height \fIheight\fR +.RS 4 +アプリケーションの高さ。 +.RE +.PP +\-name \fIname\fR +.RS 4 +アプリケーションの名前。 +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +実行するJavaFXプリローダー・クラスの修飾名。このオプションは、JavaFXアプリケーションにのみ使用します。ヘッドレス・アプリケーションを含むJavaアプリケーションには使用しないでください。 +.RE +.PP +\-width \fIwidth\fR +.RS 4 +アプリケーションの幅。 +.RE +.SH "SIGNJARコマンドのオプション" +.PP +\-alias +.RS 4 +キーの別名。 +.RE +.PP +\-keyPass +.RS 4 +キーを復元するためのパスワード。 +.RE +.PP +\-keyStore \fIfile\fR +.RS 4 +キーストア・ファイル名。 +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +生成された出力ファイルを受け取るディレクトリの名前。 +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +署名するファイルのベース・ディレクトリ。 +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +\fB\-srcdir\fRオプションで指定されたディレクトリ内のファイルのリスト。省略すると、ディレクトリ(この場合は必須の引数)にあるすべてのファイルが使用されます。リスト内のファイルはスペースで区切る必要があります。 +.RE +.PP +\-storePass +.RS 4 +キーストアの整合性を確認したり、ロックを解除するためのパスワード。 +.RE +.PP +\-storeType +.RS 4 +キーストアのタイプ。デフォルト値は"jks"です。 +.RE +.SH "自己完結型アプリケーション・バンドラの引数" +.PP +自己完結型アプリケーションの作成に使用されるバンドラの引数を指定するには、\fB\-deploy\fRコマンドの\fB\-B\fRオプションを使用します。各バンドラ・タイプに、独自の引数セットがあります。 +.SS "一般的なバンドラ引数" +.PP +appVersion=\fIversion\fR +.RS 4 +アプリケーション・パッケージのバージョン。一部のバンドラでは、バージョン文字列の形式が制限されます。 +.RE +.PP +classPath=\fIpath\fR +.RS 4 +アセンブルされたアプリケーション・ディレクトリへの相対的なクラス・パス。一般的に、パスはJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +icon=\fIpath\fR +.RS 4 +起動ツールおよびその他の支援ツールに使用されるデフォルト・アイコンの場所。OS Xの場合、形式は\fB\&.icns\fRである必要があります。Linuxの場合、形式は\fB\&.png\fRである必要があります。 +.RE +.PP +identifier=\fIvalue\fR +.RS 4 +\fBmac\&.CFBundleIdentifier\fRなど、他のプラットフォーム固有の値に使用されるデフォルト値。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +jvmOptions=\fIoption\fR +.RS 4 +アプリケーションの実行時にJVMに渡されるオプション。\fBjava\fRコマンドに有効なオプションを使用できます。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmOptions=\-Xmx128m \-BjvmOptions=\-Xms128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +jvmProperties=\fIproperty\fR=\fIvalue\fR +.RS 4 +アプリケーションの実行時にVMに渡されるJavaシステム・プロパティ。\fBjava\fRコマンドの\fB\-D\fRオプションに有効なプロパティを使用できます。プロパティ名とそのプロパティの値の両方を指定します。複数のプロパティを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmProperties=apiUserName=example \-BjvmProperties=apiKey=abcdef1234567890\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +mainJar=\fIfilename\fR +.RS 4 +アプリケーションのメイン・クラスを含むJARファイルの名前。一般的に、ファイル名はJARファイル・マニフェストから抽出され、他の\fBjavapackager\fRコマンドを使用している場合は設定する必要はありません。 +.RE +.PP +preferencesID=\fInode\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプションを確認するために調べるプリファレンス・ノード。指定したノードは、オプション\fB\-Dapp\&.preferences\&.id\fRとして実行時にアプリケーションに渡されます。この引数は、\fBuserJVMOptions\fR引数とともに使用されます。 +.RE +.PP +runtime=\fIpath\fR +.RS 4 +パッケージ・バンドルに含めるJREまたはJDKの場所。JDKまたはJREのルート・フォルダへのファイル・パスを指定します。システム・デフォルトJREを使用するには、次の例に示すようにパスを指定しないでください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Bruntime=\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +userJvmOptions=\fIoption\fR=\fIvalue\fR +.RS 4 +ユーザーがオーバーライドできるJVMオプション。\fBjava\fRコマンドに有効なオプションを使用できます。オプション名とそのオプションの値の両方を指定します。複数のオプションを渡すには、次の例に示すように\fB\-B\fRオプションの複数インスタンスを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BuserJvmOptions=\-Xmx=128m \-BuserJvmOptions=\-Xms=128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SS "OS Xアプリケーション・バンドラ引数" +.PP +mac\&.category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。カテゴリは、Apple Developer Webサイトにあるカテゴリ・リスト内に含まれている必要があります。 +.RE +.PP +mac\&.CFBundleIdentifier=\fIvalue\fR +.RS 4 +\fBCFBundleIdentifier\fRの情報plistに格納されている値。この値は、グローバルに一意である必要があり、文字、数字、ドットおよびダッシュのみを含む必要があります。DNS順序の反転をお薦めします(例: +\fBcom\&.example\&.application\&.my\-application\fR)。 +.RE +.PP +mac\&.CFBundleName=\fIname\fR +.RS 4 +OS Xメニュー・バーに表示されるアプリケーションの名前。16文字未満の名前をお薦めします。デフォルトは名前属性です。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-app=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.bundle\-id\-signing\-prefix=\fIprefix\fR +.RS 4 +plistまたは既存の署名がないバイナリがバンドル内に見つかった場合に署名済バイナリに適用される接頭辞。 +.RE +.SS "OS X DMG (ディスク・イメージ)バンドラ引数" +.PP +ディスク・イメージがマウント可能になる前に、OS X DMGインストーラは、\fBlicenseFile\fRによって指定されているライセンス・ファイル(指定されている場合)を表示します。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +systemWide=\fIboolean\fR +.RS 4 +使用対象のドラッグしてインストールするターゲットを示すフラグ。アプリケーション・フォルダを表示するには、\fBtrue\fRに設定します。デスクトップ・フォルダを表示するには、\fBfalse\fRに設定します。デフォルトは\fBtrue\fRです。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.PP +mac\&.dmg\&.simple=\fIboolean\fR +.RS 4 +AppleScriptコードの実行に依存するDMGカスタマイズ手順をスキップするかどうかを示すフラグ。\fBtrue\fRに設定して、手順をスキップします。\fBtrue\fRに設定されている場合、ディスク・ウィンドウにバックグラウンド・イメージがないため、アイコンが所定の位置に移動しません。\fBsystemWide\fR引数も\fBtrue\fRに設定されている場合、ルート・アプリケーション・フォルダのシンボリック・リンクがDMGファイルに追加されます。\fBsystemWide\fR引数が\fBfalse\fRに設定されている場合、アプリケーションのみがDMGファイルに追加され、デスクトップのリンクは追加されません。 +.RE +.SS "OS X PKGバンドラ引数" +.PP +OS X PKGインストーラは、ウィザードを示し、\fBlicenseFile\fRによって指定されているライセンス・ファイルをウィザード内のページに表示します。ユーザーはアプリケーションをインストールする前に条件に同意する必要があります。 +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +mac\&.signing\-key\-developer\-id\-installer=\fIkey\fR +.RS 4 +開発者IDまたはGatekeeper署名に使用する署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。 +.RE +.SS "Mac App Storeバンドラ引数" +.PP +mac\&.app\-store\-entitlements=\fIpath\fR +.RS 4 +アプリケーションが動作する資格を含むファイルの場所。ファイルは、Appleによって指定されている形式である必要があります。ファイルへのパスは、絶対条件で指定することも、\fBjavapackager\fRの呼出しに対して相対的に指定することもできます。資格を指定しない場合、アプリケーションは、通常のアプレット・サンドボックスよりもより厳しいサンドボックスで動作し、ネットワーク・ソケットおよびすべてのファイルへのアクセスが拒否されます。 +.RE +.PP +mac\&.signing\-key\-app=\fIkey\fR +.RS 4 +Mac App Storeのアプリケーション署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.signing\-key\-pkg=\fIkey\fR +.RS 4 +Mac App Storeのインストーラ署名キーの名前。Apple Developer Webサイトから標準のキーをインポートした場合、そのキーがデフォルトで使用されます。キーを識別できない場合、アプリケーションは署名されません。 +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +アプリケーションのバージョン番号は内部的に使用されます。値は1つ以上3つ以下の整数である必要があり、1\&.3や2\&.0\&.1のようにピリオド(\&.)で区切ります。値は、\fBappVersion\fR引数の値と異なる可能性があります。\fBappVersion\fR引数が有効な値で指定され、\fBmac\&.CFBundleVersion\fR引数が指定されていない場合、\fBappVersion\fR値が使用されます。どちらの引数も指定されていない場合、\fB100\fRがバージョン番号として使用されます。このバージョンが既存のアプリケーションのアップグレードである場合、値は以前のバージョン番号より大きくする必要があります。 +.RE +.SS "Linux Debianバンドラ引数" +.PP +\fBlicenseFile\fRによって指定されているライセンス・ファイルは、すべてのケースにおいてユーザーに示されませんが、ファイルはアプリケーション・メタデータに含まれています。 +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +copyright=\fIstring\fR +.RS 4 +アプリケーションのコピーライト文字列。この引数は、Debianメタデータで使用されます。 +.RE +.PP +email=\fIaddress\fR +.RS 4 +DebianのMaintainerフィールドで使用される電子メール・アドレスです。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。この引数は、DebianのMaintainerフィールドで使用されます。 +.RE +.SS "Linux RPMバンドラ引数" +.PP +category=\fIcategory\fR +.RS 4 +アプリケーションのカテゴリ。例は、http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.htmlを参照してください。 +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +バンドラによって表示または記録される使用許諾契約(EULA)の場所。パスは、パッケージ・アプリケーション・リソースに相対的です(例: +\fB\-BlicenseFile=COPYING\fR)。 +.RE +.PP +licenseType=\fItype\fR +.RS 4 +\fB\-BlicenseType=Proprietary\fRまたは\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fRなどのライセンス・タイプの短縮名。 +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +アプリケーションを提供する会社、組織または個人。 +.RE +.SH "非推奨オプション" +.PP +次のオプションは、パッケージ化ツールで使用されておらず、存在していても無視されます。 +.PP +\-runtimeversion \fIversion\fR +.RS 4 +必要なJavaFXランタイムのバージョン。非推奨。 +.RE +.PP +\-noembedlauncher +.RS 4 +指定した場合、パッケージャはJARファイルにJavaFX起動クラスを追加しません。非推奨。 +.RE +.SH "注意" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +タスク・コマンドとともに\fB\-v \fRオプションを使用すれば、詳細な出力が有効になります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-srcdir\fRオプションをコマンドで使用できる場合は、複数回使用できます。\fB\-srcfiles\fRオプションを指定すると、引数に指定されたファイル名が、その前に指定されている\fBsrcdir\fRオプションで指定された場所で検索されます。\fB\-srcdir\fRが\fB\-srcfiles\fRの前に指定されていない場合は、\fBjavapackager\fRコマンドが実行されるディレクトリが使用されます。 +.RE +.SH "例" +.PP +\fB例 1 \fR\-createjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-createjar \-appclass package\&.ClassName\fR +\fB \-srcdir classes \-outdir out \-outfile outjar \-v\fR + +.fi +.if n \{\ +.RE +.\} +\fBclasses\fRディレクトリの内容を\fBoutjar\&.jar\fRにパッケージ化して、アプリケーション・クラスを\fBpackage\&.ClassName\fRに設定します。 +.RE +.PP +\fB例 2 \fR\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fR +\fB \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fR + +.fi +.if n \{\ +.RE +.\} +\fBoutfile\&.jnlp\fRおよび対応する\fBoutfile\&.html\fRファイルをアプリケーション\fBAppName\fRの\fBoutdir\fRに生成します。これは\fBpackage\&.ClassName\fRで開始し、34 x 43ピクセルのサイズです。 +.RE +.PP +\fB例 3 \fR\-makeallコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fR +\fB\-height 600\fR + +.fi +.if n \{\ +.RE +.\} +コンパイルを含むすべてのパッケージ化作業(\fBcreatejar\fRおよび\fBdeploy\fR)を実行します。 +.RE +.PP +\fB例 4 \fR\-signjarコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fR +\fB\-alias duke \-keypass **** \-srcdir dist\fR + +.fi +.if n \{\ +.RE +.\} +\fBdist\fRディレクトリにあるすべてのJARファイルに署名し、alias、\fBkeyStore\fRおよび\fBstorePass\fRを指定して証明書を添付し、署名されたJARファイルを\fBdist\fRディレクトリに戻します。 +.RE +.PP +\fB例 5 \fRバンドラ引数を伴う\-deployコマンドの使用 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-native deb \-Bcategory=Education \-BjvmOptions=\-Xmx128m \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB \-BjvmOptions=\-Xms128m \-outdir packages \-outfile BrickBreaker \-srcdir dist \fR +\fB \-srcfiles BrickBreaker\&.jar \-appclass brickbreaker\&.Main \-name BrickBreaker \fR +\fB \-title "BrickBreaker demo"\fR + +.fi +.if n \{\ +.RE +.\} +自己完結型アプリケーションとしてBrickBreakerアプリケーションを実行するためのネイティブLinux Debianパッケージを生成します。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javaws.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javaws.1 new file mode 100755 index 0000000..9442992 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/javaws.1 @@ -0,0 +1,215 @@ +'\" t +.\" Copyright (c) 2003, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javaws +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Web Startツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javaws" "1" "2013å¹´11月21日" "JDK 8" "Java Web Startツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +javaws \- Java Web Startを起動します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavaws\fR [ \fIrun\-options\fR ] \fIjnlp\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavaws\fR [ \fIcontrol\-options\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIrun\-options\fR +.RS 4 +コマンド行\fB実行オプション\fR。\fB実行オプション\fRは任意の順序で指定できます。実行オプションを参照してください。 +.RE +.PP +\fIjnlp\fR +.RS 4 +JNLP (Java Network Launching Protocol)ファイルのパスまたはURL (Uniform Resource Locator)のどちらか。 +.RE +.PP +\fI制御オプション\fR +.RS 4 +コマンド行\fB制御オプション\fR。\fB制御オプション\fRは任意の順序で指定できます。制御オプションを参照してください。 +.RE +.SH "説明" +.PP +\fB注意:\fR +\fBjavaws\fRコマンドは、Oracle Solarisでは使用できません。 +.PP +\fBjavaws\fRコマンドは、JNLPのリファレンス実装であるJava Web Startを起動します。Java Web Startは、ネットワーク上で動作するJavaアプリケーションおよびアプレットを起動します。 +.PP +JNLPファイルが指定されると、\fBjavaws\fRコマンドはJNLPファイルで指定したJavaアプリケーションまたはアプレットを起動します。 +.PP +\fBjavaws\fR起動ツールには、現在のリリースでサポートされている1組のオプションがあります。ただし、これらのオプションは将来のリリースでは削除される可能性があります。 +.SH "実行オプション" +.PP +\-offline +.RS 4 +Java Web Startをオフライン・モードで実行します。 +.RE +.PP +\-Xnosplash +.RS 4 +初期スプラッシュ画面を表示しません。 +.RE +.PP +\-open \fIarguments\fR +.RS 4 +このオプションを指定すると、JNLPファイル内の引数が\fB\-open\fR +\fBarguments\fRに置き換わります。 +.RE +.PP +\-print \fIarguments\fR +.RS 4 +このオプションを指定すると、JNLPファイル内の引数が\fB\-print\fR +\fBarguments\fRに置き換わります。 +.RE +.PP +\-online +.RS 4 +オンライン・モードを使用します。これは、デフォルトの動作です。 +.RE +.PP +\-wait +.RS 4 +\fBjavaws\fRプロセスは、アプリケーションが終了するまで終了しません。Windowsプラットフォーム上では、このオプションは説明したとおりに機能しません。 +.RE +.PP +\-verbose +.RS 4 +追加の出力を表示します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineにoptionを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.PP +\-system +.RS 4 +アプリケーションをシステム・キャッシュのみから実行します。 +.RE +.SH "制御オプション" +.PP +\-viewer +.RS 4 +Javaコントロール・パネルでキャッシュ・ビューアを表示します。 +.RE +.PP +\-clearcache +.RS 4 +インストールされていないすべてのアプリケーションをキャッシュから削除します。 +.RE +.PP +\-userConfig \fIproperty\-name\fR +.RS 4 +指定されたデプロイメント・プロパティをクリアします。 +.RE +.PP +\-userConfig \fIproperty\-name property\-value\fR +.RS 4 +指定されたデプロイメント・プロパティを指定された値に設定します。 +.RE +.PP +\-uninstall +.RS 4 +キャッシュからすべてのアプリケーションを削除します。 +.RE +.PP +\-uninstall \fIjnlp\fR +.RS 4 +キャッシュからアプリケーションを削除します。 +.RE +.PP +\-print \fIimport\-options \fRjnlp +.RS 4 +キャッシュにアプリケーションをインポートします。 +.RE +.SH "インポート・オプション" +.PP +\-silent +.RS 4 +サイレント・モードでインポートします(ユーザー・インタフェースは表示されません)。 +.RE +.PP +\-system +.RS 4 +システム・キャッシュにアプリケーションをインポートします。 +.RE +.PP +\-codebase \fIurl\fR +.RS 4 +指定したコードベースからリソースを取得します。 +.RE +.PP +\-shortcut +.RS 4 +ユーザーがプロンプトを受け入れればショートカットをインストールします。このオプションは、 +\fB\-silent\fRオプションも使用しないと効果がありません。 +.RE +.PP +\-association +.RS 4 +ユーザーがプロンプトを受け入れればアソシエーションをインストールします。このオプションは、 +\fB\-silent\fRオプションも使用しないと効果がありません。 +.RE +.PP +\fB注意:\fR\fBjavaws \-shortcut \-uninstall\fR +.SH "ファイル" +.PP +ユーザーおよびシステム・キャッシュならびにdeployment\&.propertiesファイルの詳細は、デプロイメント構成ファイルおよびプロパティ +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jweb/jcp/properties\&.html)を参照してください +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java Web Start +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javaws/index\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jcmd.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jcmd.1 new file mode 100755 index 0000000..6fea90d --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jcmd.1 @@ -0,0 +1,139 @@ +'\" t +.\" Copyright (c) 2012, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jcmd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jcmd" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jcmd \- 実行中のJava Virtual Machine (JVM)に診断コマンド・リクエストを送信します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR [\fB\-l\fR|\fB\-h\fR|\fB\-help\fR] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fBPerfCounter\&.print\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fB\-f\fR \fIfilename\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fIcommand\fR[ \fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.SH "説明" +.PP +\fBjcmd\fRユーティリティは、JVMに診断コマンド・リクエストを送信するために使用されます。これはJVMが稼働しているのと同じマシンで使用し、JVMの起動に使用したものと同じ有効ユーザーおよびグループ識別子を持っている必要があります。 +.PP +\fB注意:\fR +リモート・マシンから、または別の識別子で診断コマンドを起動するには、\fBcom\&.sun\&.management\&.DiagnosticCommandMBean\fRインタフェースを使用できます。\fBDiagnosticCommandMBean\fRインタフェースの詳細は、http://docs\&.oracle\&.com/javase/8/docs/jre/api/management/extension/com/sun/management/DiagnosticCommandMBean\&.htmlにあるAPIドキュメントを参照してください。 +.PP +\fBjcmd\fRを引数なしまたは\fB\- l\fRオプションを指定して実行した場合は、実行中のJavaプロセス識別子のリストが、メイン・クラスおよびプロセスの起動に使用されたコマンド行引数とともに出力されます。\fB\-h\fRまたは\fB\-help\fRオプションを指定して\fBjcmd\fRを実行すると、ツールのヘルプ・メッセージが出力されます。 +.PP +プロセス識別子(\fIpid\fR)またはメイン・クラス(\fImain\-class\fR)を最初の引数として指定した場合、\fBjcmd\fRは、識別子を指定した場合はJavaプロセスに、メイン・クラスの名前を指定した場合はすべてのJavaプロセスに診断コマンド・リクエストを送信します。プロセス識別子として\fB0\fRを指定して、すべての使用可能なJavaプロセスに診断コマンド・リクエストを送信することもできます。診断コマンド・リクエストとして、次のいずれかを使用します。 +.PP +Perfcounter\&.print +.RS 4 +指定したJavaプロセスで使用可能なパフォーマンス・カウンタが出力されます。パフォーマンス・カウンタのリストはJavaプロセスによって異なる場合があります。 +.RE +.PP +\-f \fIfilename\fR +.RS 4 +診断コマンドを読み取り、指定したJavaプロセスに送信するファイルの名前。\fB\-f\fRオプションでのみ使用します。ファイル内の各コマンドは、1行で記述する必要があります。番号記号(\fB#\fR)で始まる行は無視されます。すべての行が読み取られるか、\fBstop\fRキーワードを含む行が読み取られると、ファイルの処理が終了します。 +.RE +.PP +\fIcommand\fR [\fIarguments\fR] +.RS 4 +指定されたJavaプロセスに送信するコマンド。指定したプロセスで使用できる診断コマンドのリストは、このプロセスに対して\fBhelp\fRコマンドを送信すれば表示されます。各診断コマンドに独自の引数セットがあります。コマンドの説明、構文および使用可能な引数のリストを表示するには、\fBhelp\fRコマンドの引数としてコマンド名を使用します。 +.sp +\fB注意:\fR +引数にスペースが含まれている場合は、一重引用符または二重引用符(\fB\*(Aq\fRまたは\fB"\fR)で囲む必要があります。加えて、オペレーティング・システム・シェルが引用符を処理しないように、バックスラッシュ(\fB\e\fR)で一重引用符または二重引用符をエスケープする必要があります。または、これらの引数を一重引用符で囲んでから、二重引用符で囲むこともできます(または二重引用符で囲んでから、一重引用符で囲む)。 +.RE +.SH "オプション" +.PP +各オプションは互いに排他的です。 +.PP +\-f \fIfilename\fR +.RS 4 +指定されたファイルからコマンドを読み取ります。このオプションは、最初の引数としてプロセス識別子またはメイン・クラスを指定する場合にのみ使用できます。ファイル内の各コマンドは、1行で記述する必要があります。番号記号(\fB#\fR)で始まる行は無視されます。すべての行が読み取られるか、\fBstop\fRキーワードを含む行が読み取られると、ファイルの処理が終了します。 +.RE +.PP +\-h +.br +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-l +.RS 4 +実行中のJavaプロセス識別子のリストをメイン・クラスおよびコマンド行引数とともに出力します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jconsole.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jconsole.1 new file mode 100755 index 0000000..e43a76a --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jconsole.1 @@ -0,0 +1,139 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jconsole +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaトラブルシューティング、プロファイリング、モニタリングおよび管理ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jconsole" "1" "2013å¹´11月21日" "JDK 8" "Javaトラブルシューティング、プロファイリング、モニタリン" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jconsole \- Javaアプリケーションを監視および管理するためのグラフィカル・コンソールを開始します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjconsole\fR [ \fIoptions\fR ] [ connection \&.\&.\&. ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +connection = \fIpid\fR | \fIhost\fR:\fIport\fR | \fIjmxURL\fR +.RS 4 +\fBpid\fR値はローカルのJava Virtual Machine (JVM)のプロセスIDです。JVMは\fBjconsole\fRコマンドを実行しているユーザーIDと同じユーザーIDで実行する必要があります。\fBhost:port\fR値はJVMが動作しているホスト・システムの名前と、JVMが開始したときにシステム・プロパティ\fBcom\&.sun\&.management\&.jmxremote\&.port\fRで指定したポート番号です。\fBjmxUrl\fR値は、JMXServiceURLで記述されている、接続されるJMXエージェントのアドレスです。 +.sp +\fBconnection\fRパラメータの詳細は、JMXテクノロジを使用したモニタリングおよび管理 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/agent\&.html)を参照してください +.sp +\fBJMXServiceURL\fRクラスの説明( +http://docs\&.oracle\&.com/javase/8/docs/api/javax/management/remote/JMXServiceURL\&.html)も参照してください +.RE +.SH "説明" +.PP +\fBjconsole\fRコマンドは、ローカル・マシンまたはリモート・マシン上のJavaアプリケーションと仮想マシンの監視と管理を行うグラフィカル・コンソール・ツールを起動します。 +.PP +Windows上では、\fBjconsole\fRコマンドはコンソール・ウィンドウと関連付けられていません。ただし、\fBjconsole\fRコマンドが失敗すると、エラー情報を示すダイアログ・ボックスが表示されます。 +.SH "オプション" +.PP +\-interval\fI=n\fR +.RS 4 +更新間隔を\fIn\fR秒に設定します(デフォルトは4秒)。 +.RE +.PP +\-notile +.RS 4 +最初にウィンドウをタイリングしません(複数接続の場合)。 +.RE +.PP +\-pluginpath \fIplugins\fR +.RS 4 +\fBJConsole\fRプラグインを検索するディレクトリまたはJARファイルのリストを指定します。\fIplugins\fRパスには\fBMETA\-INF/services/com\&.sun\&.tools\&.jconsole\&.JConsolePlugin\fRという名前のプロバイダ構成ファイルを含んでいる必要があり、これにはプラグインごとに1行が含まれています。その行は\fBcom\&.sun\&.tools\&.jconsole\&.JConsolePlugin\fRクラスを実装しているクラスの完全修飾クラス名を指定します。 +.RE +.PP +\-version +.RS 4 +リリース情報を表示して終了します。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjconsole\fRコマンドを実行したJVMに\fBflag\fRを渡します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JConsoleの使用 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/jconsole\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JMXテクノロジを使用したモニタリングおよび管理 + +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/agent\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBJMXServiceURL\fRクラスの説明( +http://docs\&.oracle\&.com/javase/8/docs/api/javax/management/remote/JMXServiceURL\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jdb.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jdb.1 new file mode 100755 index 0000000..a989b83 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jdb.1 @@ -0,0 +1,370 @@ +'\" t +.\" Copyright (c) 1995, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jdb +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jdb" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jdb \- Javaプラットフォーム・プログラムのbugを検出および修正します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdb\fR [\fIoptions\fR] [\fIclassname\fR] [\fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclass\fRname +.RS 4 +デバッグするメイン・クラスの名前。 +.RE +.PP +\fIarguments\fR +.RS 4 +classの\fBmain()\fRメソッドに渡す引数。 +.RE +.SH "説明" +.PP +Javaデバッガ(JDB)は、Javaクラス用の簡単なコマンド行デバッガです。\fBjdb\fRコマンドとそのオプションはJDBを呼び出します。\fBjdb\fRコマンドは、JDBA (Java Platform Debugger Architecture)を視覚的に実行し、ローカルまたはリモートのJava Virtual Machine (JVM)の検査とデバッグを行うことができます。Java Platform Debugger Architecture (JDBA) +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jpda/index\&.html)を参照してください。 +.SS "JDBセッションの開始" +.PP +JDBセッションを開始するには様々な方法があります。最も頻繁に使用されるのは、デバッグするアプリケーションのメイン・クラスを使用して、JDBから新しいJVMを起動する方法です。コマンド行で、\fBjava\fRコマンドのかわりに\fBjdb\fRコマンドを入力します。たとえば、アプリケーションのメイン・クラスが\fBMyClass\fRの場合は、JDB環境でデバッグするときに次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdb MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この方法で起動すると、\fBjdb\fRコマンドは、指定されたパラメータを使用して2つ目のJVMを呼び出します。次に、指定されたクラスをロードして、クラスの最初の命令を実行する前にJVMを停止させます。 +.PP +\fBjdb\fRコマンドのもう1つの使用方法は、すでに実行中のJVMにjdbを接続することです。\fBjdb\fRコマンドが接続するVMを、その実行中に起動するための構文を次に示します。これは、インプロセス・デバッグ用ライブラリをロードし、接続の種類を指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-agentlib:jdwp=transport=dt_socket,server=y,suspend=n MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコマンドを使用して、\fBjdb\fRコマンドをJVMに接続できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdb \-attach 8000\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この場合、\fBjdb\fRコマンドは新しいJVMを起動するかわりに既存のJVMに接続されるため、\fBjdb\fRコマンド行に\fBMyClass\fR引数は指定しません。 +.PP +デバッガをJVMに接続するには他にも様々な方法があり、すべて\fBjdb\fRコマンドでサポートされています。接続オプションについては、Java Platform Debugger Architectureのドキュメントを参照してください。 +.SS "基本jdbコマンド" +.PP +基本的な\fBjdb\fRコマンドの一覧を示します。JDBがサポートするコマンドはこれ以外にもあり、それらは\fB\-help\fRオプションを使用して表示できます。 +.PP +helpまたは? +.RS 4 +\fBhelp\fRまたは\fB?\fRコマンドは、認識されたコマンドのリストに簡潔な説明を付けて表示します。 +.RE +.PP +run +.RS 4 +JDBを起動してブレークポイントを設定したあとに、\fBrun\fRコマンドを使用して、デバッグするアプリケーションの実行を開始できます。\fBrun\fRコマンドは、既存のVMに接続している場合とは異なり、デバッグするアプリケーションが\fBjdb\fRから起動したときにのみ使用できます。 +.RE +.PP +cont +.RS 4 +ブレークポイント、例外、またはステップ実行の後で、デバッグするアプリケーションの実行を継続します。 +.RE +.PP +print +.RS 4 +Javaオブジェクトおよびプリミティブ値を表示します。プリミティブ型の変数またはフィールドの場合には、実際の値が出力されます。オブジェクトの場合には、短い説明が出力されます。オブジェクトの詳細を取得する方法を探すには、dumpコマンドを参照してください。 +.sp +\fB注意:\fR +ローカル変数を表示するには、含んでいるクラスが\fBjavac \-g\fRオプションを使用してコンパイルされている必要があります。 +.sp +\fBprint\fRコマンドは、次に示すような、メソッド呼出しを使用したものなど、多くの簡単なJava式をサポートします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBprint MyClass\&.myStaticField\fR +\fBprint myObj\&.myInstanceField\fR +\fBprint i + j + k (i, j, k are primities and either fields or local variables)\fR +\fBprint myObj\&.myMethod() (if myMethod returns a non\-null)\fR +\fBprint new java\&.lang\&.String("Hello")\&.length()\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +dump +.RS 4 +プリミティブ値の場合、\fBdump\fRコマンドは\fBprint\fRコマンドと同一です。オブジェクトの場合、\fBdump\fRコマンドでは、オブジェクト内に定義されている各フィールドの現在の値が出力されます。staticフィールドとinstanceフィールドが出力されます。\fBdump\fRコマンドでは、\fBprint\fRコマンドと同じ式がサポートされます。 +.RE +.PP +threads +.RS 4 +現在実行中のスレッドを一覧表示します。スレッドごとに、名前と現在の状態、および他のコマンドに使用できるインデックスが出力されます。この例では、スレッド・インデックスは4であり、スレッドは\fBjava\&.lang\&.Thread\fRのインスタンスで、スレッドの名前は\fBmain\fRであり、現在実行中です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB4\&. (java\&.lang\&.Thread)0x1 main running\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +thread +.RS 4 +現在のスレッドにするスレッドを選択します。多くの\fBjdb\fRコマンドは、現在のスレッドの設定に基づいて実行されます。スレッドは、threadsコマンドで説明したスレッド・インデックスとともに指定します。 +.RE +.PP +where +.RS 4 +引数を指定しないで\fBwhere\fRコマンドを実行すると、現在のスレッドのスタックがダンプされます。\fBwhere\fR +\fBall\fRコマンドは、現在のスレッド・グループにあるスレッドのスタックをすべてダンプします。\fBwhere\fR +\fBthreadindex\fRコマンドは、指定されたスレッドのスタックをダンプします。 +.sp +現在のスレッドが(ブレークポイントか\fBsuspend\fRコマンドによって)中断している場合は、ローカル変数とフィールドは\fBprint\fRコマンドと\fBdump\fRコマンドで表示できます。\fBup\fRコマンドと\fBdown\fRコマンドで、どのスタック・フレームを現在のスタック・フレームにするかを選ぶことができます。 +.RE +.SS "ブレークポイント" +.PP +ブレークポイントは、行番号またはメソッドの最初の命令でJDBに設定できます。次に例を示します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド\fBstop at MyClass:22\fRは、\fBMyClass\fRが含まれるソース・ファイルの22行目の最初の命令にブレークポイントを設定します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド\fBstop in java\&.lang\&.String\&.length\fRは、メソッド\fBjava\&.lang\&.String\&.length\fRの先頭にブレークポイントを設定します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +コマンド\fBstop in MyClass\&.<clinit>\fRは、\fB<clinit>\fRを使用して、\fBMyClass\fRの静的初期化コードを特定します。 +.RE +.PP +メソッドがオーバーロードされている場合には、メソッドの引数の型も指定して、ブレークポイントに対して適切なメソッドが選択されるようにする必要があります。たとえば、\fBMyClass\&.myMethod(int,java\&.lang\&.String)\fRまたは\fBMyClass\&.myMethod()\fRと指定します。 +.PP +\fBclear\fRコマンドは、\fBclear MyClass:45\fRのような構文を使用してブレークポイントを削除します。\fBclear\fRを使用するか、引数を指定しないで\fBstop\fRコマンドを使用すると、現在設定されているすべてのブレークポイントが表示されます。\fBcont\fRコマンドは実行を継続します。 +.SS "ステップ実行" +.PP +\fBstep\fRコマンドは、現在のスタック・フレームまたは呼び出されたメソッド内で、次の行を実行します。\fBnext\fRコマンドは、現在のスタック・フレームの次の行を実行します。 +.SS "例外" +.PP +スローしているスレッドの呼出しスタック上のどこにも\fBcatch\fR文がない場合に例外が発生すると、JVMは通常、例外トレースを出力して終了します。ただし、JDB環境で実行している場合は、違反のスロー時にJDBに制御が戻ります。次に、\fBjdb\fRコマンドを使用して例外の原因を診断します。 +.PP +たとえば、\fBcatch java\&.io\&.FileNotFoundException\fRまたは\fBcatch\fR +\fBmypackage\&.BigTroubleException\fRのように\fBcatch\fRコマンドを使用すると、デバッグされたアプリケーションは、他の例外がスローされたときに停止します。例外が特定のクラスまたはサブクラスのインスタンスの場合は、アプリケーションは例外がスローされた場所で停止します。 +.PP +\fBignore\fRコマンドを使用すると、以前の\fBcatch\fRコマンドの効果が無効になります。\fBignore\fRコマンドでは、デバッグされるJVMは特定の例外を無視せず、デバッガのみを無視します。 +.SH "オプション" +.PP +コマンド行で\fBjava\fRコマンドのかわりに\fBjdb\fRコマンドを使用する場合、\fBjdb\fRコマンドは、\fB\-D\fR、\fB\-classpath\fR、\fB\-X\fRなど、\fBjava\fRコマンドと同じ数のオプションを受け入れます。\fBjdb\fRコマンドは、その他に次のリストにあるオプションを受け入れます。 +.PP +デバッグを行うJVMにデバッガを接続するための代替機構を提供するために、その他のオプションがサポートされています。これらの接続の代替に関する詳細なドキュメントは、Java Platform Debugger Architecture (JPDA) +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jpda/index\&.html)を参照してください +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.PP +\-sourcepath \fIdir1:dir2: \&. \&. \&.\fR +.RS 4 +指定されたパスを使用して、ソース・ファイルを検索します。このオプションが指定されていない場合は、デフォルト・パスのドット(\&.)が使用されます。 +.RE +.PP +\-attach \fIaddress\fR +.RS 4 +デフォルトの接続機構を使用して、実行中のJVMにデバッガを接続します。 +.RE +.PP +\-listen \fIaddress\fR +.RS 4 +実行中のJVMが標準のコネクタを使用して指定されたアドレスに接続するのを待機します。 +.RE +.PP +\-launch +.RS 4 +デバッグするアプリケーションをJDBの起動後ただちに起動します。\fB\-launch\fRオプションにより、\fBrun\fRコマンドが必要なくなります。デバッグするアプリケーションは、起動後、初期アプリケーション・クラスがロードされる直前に停止します。その時点で、必要なブレークポイントを設定し、\fBcont\fRコマンドを使用して実行を継続できます。 +.RE +.PP +\-listconnectors +.RS 4 +このJVMで利用できるコネクタを一覧表示します。 +.RE +.PP +\-connect connector\-name:\fIname1=value1\fR +.RS 4 +一覧表示された引数の値と指定のコネクタを使用してターゲットJVMに接続します。 +.RE +.PP +\-dbgtrace [\fIflags\fR] +.RS 4 +\fBjdb\fRコマンドのデバッグの情報を出力します。 +.RE +.PP +\-tclient +.RS 4 +Java HotSpot VMクライアント内でアプリケーションを実行します。 +.RE +.PP +\-tserver +.RS 4 +Java HotSpot VMサーバー内でアプリケーションを実行します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +JVMに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "デバッグ対象のプロセスに転送されるオプション" +.PP +\-v \-verbose[:\fIclass\fR|gc|jni] +.RS 4 +冗長モードにします。 +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +システム・プロパティを設定します。 +.RE +.PP +\-classpath \fIdir\fR +.RS 4 +クラスを検索するための、コロンで区切って指定されたディレクトリのリスト。 +.RE +.PP +\-X\fIoption\fR +.RS 4 +非標準ターゲットJVMオプションです。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jdeps.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jdeps.1 new file mode 100755 index 0000000..b290ae2 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jdeps.1 @@ -0,0 +1,375 @@ +'\" t +.\" Copyright (c) 2013, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jdeps +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jdeps" "1" "2013å¹´11月21日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jdeps \- Javaクラス依存性アナライザ。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjdeps\fR [\fIoptions\fR] \fIclasses\fR \&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclasses\fR +.RS 4 +分析するクラスの名前。クラス・パスで検出できるクラスを、ファイル名、ディレクトリまたはJARファイルで指定できます。 +.RE +.SH "説明" +.PP +\fBjdeps\fRコマンドは、Javaクラス・ファイルのパッケージレベルまたはクラスレベルの依存性を示します。入力クラスには、\fB\&.class\fRファイルのパス名、ディレクトリ、JARファイル、またはすべてのクラス・ファイルを分析するための完全修飾クラス名を指定できます。オプションにより出力が決定します。デフォルトでは、\fBjdeps\fRはシステム出力に依存関係を出力します。DOT言語で依存関係を生成できます(\fB\-dotoutput\fRオプションを参照)。 +.SH "オプション" +.PP +\-dotoutput <\fIdir\fR> +.RS 4 +DOTファイル出力の宛先ディレクトリ。指定した場合、\fBjdeps\fRは<\fIarchive\-file\-name\fR>\&.dotという名前の分析済アーカイブごとに依存関係をリストする1つのdotファイルを生成し、アーカイブ間の依存関係をリストするsummary\&.dotという名前のサマリー・ファイルも生成します。 +.RE +.PP +\-s +.br +\-summary +.RS 4 +依存関係のサマリーのみを出力します。 +.RE +.PP +\-v +.br +\-verbose +.RS 4 +すべてのクラスレベルの依存関係を出力します。 +.RE +.PP +\-verbose:package +.RS 4 +同じアーカイブ内の依存関係を除き、パッケージレベルの依存関係を出力します。 +.RE +.PP +\-verbose:class +.RS 4 +同じアーカイブ内の依存関係を除き、クラスレベルの依存関係を出力します。 +.RE +.PP +\-cp <\fIpath\fR> +.br +\-classpath <\fIpath\fR> +.RS 4 +クラス・ファイルの検索場所を指定します。 +.sp +クラス・パスの設定 も参照してください。 +.RE +.PP +\-p <\fIpkg name\fR> +.br +\-package <\fIpkg name\fR> +.RS 4 +指定したパッケージの依存関係を検出します。異なるパッケージに対してこのオプションを複数回指定できます。\fB\-p\fRオプションと\fB\-e\fRオプションを同時に指定することはできません。 +.RE +.PP +\-e <\fIregex\fR> +.br +\-regex <\fIregex\fR> +.RS 4 +指定した正規表現パターンと一致するパッケージの依存関係を検出します。\fB\-p\fRオプションと\fB\-e\fRオプションを同時に指定することはできません。 +.RE +.PP +\-include <\fIregex\fR> +.RS 4 +分析をパターンに一致するクラスに制限します。このオプションは、分析するクラスのリストをフィルタします。依存関係にパターンを適用する\fB\-p\fRおよび\fB\-e\fRとともに使用できます。 +.RE +.PP +\-jdkinternals +.RS 4 +JDKの内部APIのクラスレベルの依存関係を検出します。デフォルトでは、\fB\-include\fRオプションを指定しないかぎり、\fB\-classpath\fRオプションおよび入力ファイルに指定されたすべてのクラスを分析します。このオプションは、\fB\-p\fRオプション、\fB\-e\fRオプションおよび\fB\-s\fRオプションとともに使用できません。 +.sp +\fB警告\fR: JDKの内部APIは、今後のリリースでアクセスできなくなる可能性があります。 +.RE +.PP +\-P +.br +\-profile +.RS 4 +パッケージを含むプロファイルまたはファイルを表示します。 +.RE +.PP +\-apionly +.RS 4 +フィールド・タイプ、メソッド・パラメータ・タイプ、戻りタイプ、チェックされた例外タイプを含むパブリック・クラスの\fBpublic\fRおよび\fBprotected\fRメンバーの署名からの依存関係など、分析をAPIに制限します。 +.RE +.PP +\-R +.br +\-recursive +.RS 4 +すべての依存関係を再帰的に走査します。 +.RE +.PP +\-version +.RS 4 +バージョン情報を出力します。 +.RE +.PP +\-h +.br +\-? +.br +\-help +.RS 4 +\fBjdeps\fRに関するヘルプ・メッセージを出力します。 +.RE +.SH "例" +.PP +Notepad\&.jarの依存関係の分析。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps demo/jfc/Notepad/Notepad\&.jar\fR +\fB \fR +\fBdemo/jfc/Notepad/Notepad\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB <unnamed> (Notepad\&.jar)\fR +\fB \-> java\&.awt \fR +\fB \-> java\&.awt\&.event \fR +\fB \-> java\&.beans \fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.net \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.logging \fR +\fB \-> javax\&.swing \fR +\fB \-> javax\&.swing\&.border \fR +\fB \-> javax\&.swing\&.event \fR +\fB \-> javax\&.swing\&.text \fR +\fB \-> javax\&.swing\&.tree \fR +\fB \-> javax\&.swing\&.undo \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\-Pまたは\-profileオプションを使用して、メモ帳が依存するプロファイルを表示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-profile demo/jfc/Notepad/Notepad\&.jar \fR +\fBdemo/jfc/Notepad/Notepad\&.jar \-> /usr/java/jre/lib/rt\&.jar (Full JRE)\fR +\fB <unnamed> (Notepad\&.jar)\fR +\fB \-> java\&.awt Full JRE\fR +\fB \-> java\&.awt\&.event Full JRE\fR +\fB \-> java\&.beans Full JRE\fR +\fB \-> java\&.io compact1\fR +\fB \-> java\&.lang compact1\fR +\fB \-> java\&.net compact1\fR +\fB \-> java\&.util compact1\fR +\fB \-> java\&.util\&.logging compact1\fR +\fB \-> javax\&.swing Full JRE\fR +\fB \-> javax\&.swing\&.border Full JRE\fR +\fB \-> javax\&.swing\&.event Full JRE\fR +\fB \-> javax\&.swing\&.text Full JRE\fR +\fB \-> javax\&.swing\&.tree Full JRE\fR +\fB \-> javax\&.swing\&.undo Full JRE\fR + +.fi +.if n \{\ +.RE +.\} +.PP +tools\&.jarファイル内の\fBcom\&.sun\&.tools\&.jdeps\&.Main\fRクラスなど、特定のクラスパス内の特定のクラスの直接依存関係の分析。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fR +\fBlib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB com\&.sun\&.tools\&.jdeps (tools\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB\-verbose:class\fRオプションを使用して、クラスレベル依存関係を検索するか\fB\-v\fRまたは\fB\-verbose\fRオプションを使用して同じJARファイルからの依存関係を含めます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-verbose:class \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fR +\fB \fR +\fBlib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB com\&.sun\&.tools\&.jdeps\&.Main (tools\&.jar)\fR +\fB \-> java\&.io\&.PrintWriter \fR +\fB \-> java\&.lang\&.Exception \fR +\fB \-> java\&.lang\&.Object \fR +\fB \-> java\&.lang\&.String \fR +\fB \-> java\&.lang\&.System \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB\-R\fRまたは\fB\-recursive\fRオプションを使用して、\fBcom\&.sun\&.tools\&.jdeps\&.Main\fRクラスの推移的な依存関係を分析します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-R \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fR +\fBlib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB com\&.sun\&.tools\&.classfile (tools\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.lang\&.reflect \fR +\fB \-> java\&.nio\&.charset \fR +\fB \-> java\&.nio\&.file \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.regex \fR +\fB com\&.sun\&.tools\&.jdeps (tools\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.nio\&.file \fR +\fB \-> java\&.nio\&.file\&.attribute \fR +\fB \-> java\&.text \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.jar \fR +\fB \-> java\&.util\&.regex \fR +\fB \-> java\&.util\&.zip \fR +\fB/usr/java/jre/lib/jce\&.jar \-> /usr/java/jre/lib/rt\&.jar\fR +\fB javax\&.crypto (jce\&.jar)\fR +\fB \-> java\&.io \fR +\fB \-> java\&.lang \fR +\fB \-> java\&.lang\&.reflect \fR +\fB \-> java\&.net \fR +\fB \-> java\&.nio \fR +\fB \-> java\&.security \fR +\fB \-> java\&.security\&.cert \fR +\fB \-> java\&.security\&.spec \fR +\fB \-> java\&.util \fR +\fB \-> java\&.util\&.concurrent \fR +\fB \-> java\&.util\&.jar \fR +\fB \-> java\&.util\&.regex \fR +\fB \-> java\&.util\&.zip \fR +\fB \-> javax\&.security\&.auth \fR +\fB \-> sun\&.security\&.jca JDK internal API (rt\&.jar)\fR +\fB \-> sun\&.security\&.util JDK internal API (rt\&.jar)\fR +\fB javax\&.crypto\&.spec (jce\&.jar)\fR +\fB \-> java\&.lang \fR +\fB \-> java\&.security\&.spec \fR +\fB \-> java\&.util \fR +\fB/usr/java/jre/lib/rt\&.jar \-> /usr/java/jre/lib/jce\&.jar\fR +\fB java\&.security (rt\&.jar)\fR +\fB \-> javax\&.crypto\fR + +.fi +.if n \{\ +.RE +.\} +.PP +メモ帳デモの依存関係のdotファイルを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ jdeps \-dotoutput dot demo/jfc/Notepad/Notepad\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBjdeps\fRは、\fB\-dotoutput\fRオプションで指定されたdotディレクトリに<\fIfilename\fR>\&.dotという名前のdotファイルを特定のJARファイルごとに作成し、JARファイル間の依存関係をリストするsummary\&.dotという名前のサマリー・ファイルも作成します +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB$ cat dot/Notepad\&.jar\&.dot \fR +\fBdigraph "Notepad\&.jar" {\fR +\fB // Path: demo/jfc/Notepad/Notepad\&.jar\fR +\fB "<unnamed>" \-> "java\&.awt";\fR +\fB "<unnamed>" \-> "java\&.awt\&.event";\fR +\fB "<unnamed>" \-> "java\&.beans";\fR +\fB "<unnamed>" \-> "java\&.io";\fR +\fB "<unnamed>" \-> "java\&.lang";\fR +\fB "<unnamed>" \-> "java\&.net";\fR +\fB "<unnamed>" \-> "java\&.util";\fR +\fB "<unnamed>" \-> "java\&.util\&.logging";\fR +\fB "<unnamed>" \-> "javax\&.swing";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.border";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.event";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.text";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.tree";\fR +\fB "<unnamed>" \-> "javax\&.swing\&.undo";\fR +\fB}\fR +\fB \fR +\fB$ cat dot/summary\&.dot\fR +\fBdigraph "summary" {\fR +\fB "Notepad\&.jar" \-> "rt\&.jar";\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javap(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jhat.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jhat.1 new file mode 100755 index 0000000..114fd33 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jhat.1 @@ -0,0 +1,197 @@ +'\" t +.\" Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jhat +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jhat" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jhat \- Javaヒープを分析します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjhat\fR [ \fIoptions\fR ] \fIheap\-dump\-file\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIheap\-dump\-file\fR +.RS 4 +ブラウズ対象となるJavaバイナリ・ヒープ・ダンプ・ファイル。複数のヒープ・ダンプを含むダンプ・ファイルの場合、\fBmyfile\&.hprof#3\fRのようにファイル名の後に\fB#<number>\fRを付加することで、ファイル内の特定のダンプを指定できます。 +.RE +.SH "説明" +.PP +\fBjhat\fRコマンドはJavaヒープ・ダンプ・ファイルを解析し、Webサーバーを開始します。\fBjhat\fRコマンドを使用して、お気に入りのブラウザでヒープ・ダンプを参照できます。\fBjhat\fRコマンドは、既知のクラス\fBMyClass\fRのすべてのインスタンスを表示するなどの事前設計済の問合せやObject Query Language (OQL)をサポートします。ヒープ・ダンプの問合せを除き、OQLはSQLに似ています。OQLのヘルプには、\fBjhat\fRコマンドによって表示されるOQLヘルプ・ページからアクセスできます。デフォルト・ポートを使用する場合、OQLのヘルプはhttp://localhost:7000/oqlhelp/で利用可能です。 +.PP +Javaのヒープ・ダンプを生成するには、次のいくつかの方法があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjmap \-dump\fRオプションを使用して実行時にヒープ・ダンプを取得します。jmap(1)を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBjconsole\fRオプションを使用して\fBHotSpotDiagnosticMXBean\fR経由で実行時にヒープ・ダンプを取得します。jconsole(1)および\fBHotSpotDiagnosticMXBean\fRのインタフェースの説明( +http://docs\&.oracle\&.com/javase/8/docs/jre/api/management/extension/com/sun/management/HotSpotDiagnosticMXBean\&.html)を参照してください。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ヒープ・ダンプは、\fB\-XX:+HeapDumpOnOutOfMemoryError\fR +Java Virtual Machine (JVM)オプションを指定することで、\fBOutOfMemoryError\fRがスローされたときに生成されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBhprof\fRコマンドを使用します。HPROF: Heap/CPUプロファイリング・ツール +(http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/hprof\&.html)を参照してください +.RE +.SH "オプション" +.PP +\-stack false|true +.RS 4 +オブジェクト割当呼出しスタックの追跡を無効にします。ヒープ・ダンプ内で割当サイト情報が使用できない場合、このフラグを\fBfalse\fRに設定する必要があります。デフォルトは\fBtrue\fRです。 +.RE +.PP +\-refs false|true +.RS 4 +オブジェクトへの参照の追跡を無効にします。デフォルトは\fBtrue\fRです。デフォルトでは、ヒープ内のすべてのオブジェクトについて、バックポインタ(指定されたオブジェクトをポイントしているオブジェクト。参照者または受信参照とも呼ばれる)が計算されます。 +.RE +.PP +\-port \fIport\-number\fR +.RS 4 +\fBjhat\fRのHTTPサーバーのポートを設定します。デフォルトは7000です。 +.RE +.PP +\-exclude \fIexclude\-file\fR +.RS 4 +到達可能なオブジェクトの問合せから除外する必要があるデータ・メンバーの一覧を含むファイルを指定します。たとえば、このファイルに\fBjava\&.lang\&.String\&.value\fRが含まれていた場合、特定のオブジェクト\fBo\fRから到達可能なオブジェクトのリストを計算する際に、\fBjava\&.lang\&.String\&.value\fRフィールドに関連する参照パスが考慮されなくなります。 +.RE +.PP +\-baseline \fIexclude\-file\fR +.RS 4 +ベースラインとなるヒープ・ダンプを指定します。両方のヒープ・ダンプ内で同じオブジェクトIDを持つオブジェクトは新規ではないとしてマークされます。他のオブジェクトは新規としてマークされます。これは、異なる2つのヒープ・ダンプを比較する際に役立ちます。 +.RE +.PP +\-debug \fIint\fR +.RS 4 +このツールのデバッグ・レベルを設定します。レベル0はデバッグ出力がないことを意味します。より大きな値を設定すると、より冗長なモードになります。 +.RE +.PP +\-version +.RS 4 +リリース番号をレポートして終了します +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjhat\fRコマンドを実行しているJava Virtual Machineに\fBflag\fRを渡します。たとえば、512Mバイトの最大ヒープ・サイズを使用するには、\fB\-J\-Xmx512m\fRとします。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jmap(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jconsole(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +HPROF: Heap/CPUプロファイリング・ツール +(http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/hprof\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jinfo.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jinfo.1 new file mode 100755 index 0000000..97af9e2 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jinfo.1 @@ -0,0 +1,169 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jinfo +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jinfo" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jinfo \- 構成情報を生成します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjinfo\fR [ \fIoption\fR ] \fIpid\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjinfo\fR [ \fIoption \fR] \fIexecutable core\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjinfo\fR [ \fIoption \fR] \fI[ servier\-id ] remote\-hostname\-or\-IP\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIオプション\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIpid\fR +.RS 4 +構成情報が出力されるプロセスID。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +構成情報が出力されるコア・ファイル。 +.RE +.PP +\fIremote\-hostname\-or\-IP\fR +.RS 4 +リモート・デバッグ・サーバーの\fBホスト名\fRまたは\fBIP\fRアドレス。jsadebugd(1)を参照してください。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のリモート・ホストで実行している場合の、オプション固有のID。 +.RE +.SH "説明" +.PP +\fBjinfo\fRコマンドは、指定されたJavaプロセスやコア・ファイルまたはリモート・デバッグ・サーバーのJava構成情報を出力します。構成情報には、Javaシステム・プロパティとJava仮想マシン(JVM)のコマンドライン・フラグが含まれています。指定されたプロセスが64ビットJVM上で実行されている場合、\fB\-J\-d64\fRオプションを指定する必要がある場合があります。次に例を示します。\fBjinfo\fR +\fB\-J\-d64 \-sysprops pid\fR。 +.PP +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。\fBdbgeng\&.dll\fRが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。\fBPATH\fR環境変数には、ターゲット・プロセスによって使用されるjvm\&.dllの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。たとえば、\fBset PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fRです。 +.SH "オプション" +.PP +no\-option +.RS 4 +コマンド行フラグを、システム・プロパティ名と値のペアとともに出力します。 +.RE +.PP +\-flag \fIname\fR +.RS 4 +指定されたコマンドライン・フラグの名前と値を出力します。 +.RE +.PP +\-flag \fI[+|\-]name\fR +.RS 4 +指定されたブール型のコマンドライン・フラグを有効または無効にします。 +.RE +.PP +\-flag \fIname=value\fR +.RS 4 +指定されたコマンドライン・フラグを指定された値に設定します。 +.RE +.PP +\-flags +.RS 4 +JVMに渡されるコマンドライン・フラグを出力します。 +.RE +.PP +\-sysprops +.RS 4 +Javaシステム・プロパティを名前と値のペアとして出力します。 +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jjs.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jjs.1 new file mode 100755 index 0000000..b461c49 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jjs.1 @@ -0,0 +1,415 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jjs +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: 基本ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jjs" "1" "2015å¹´3月3日" "JDK 8" "基本ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jjs \- Nashornエンジンを呼び出します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\fBjjs\fR\fR\fB [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIscript\-files\fR\fR\fB] [\-\- \fR\fB\fIarguments\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +空白文字で区切られた、\fBjjs\fRコマンドの1つ以上のオプション。詳細は、オプションを参照してください。 +.RE +.PP +\fIscript\-files\fR +.RS 4 +空白文字で区切られた、Nashornを使用して解釈する1つ以上のスクリプト・ファイル。ファイルが指定されない場合は、対話型シェルが起動されます。 +.RE +.PP +\fIarguments\fR +.RS 4 +二重ハイフン・マーカー(\fB\-\-\fR)の後のすべての値が、引数としてスクリプトまたは対話型シェルに渡されます。これらの値には\fBarguments\fRプロパティを使用してアクセスできます(Example 3を参照してください)。 +.RE +.SH "説明" +.PP +\fBjjs\fRコマンド行ツールを使用してNashornエンジンを呼び出します。これを使用して、1つまたは複数のスクリプト・ファイルを解釈したり、対話型シェルを実行することができます。 +.SH "オプション" +.PP +\fBjjs\fRコマンドのオプションはスクリプトがNashornによって解釈される条件を制御します。 +.PP +\-ccs=\fIsize\fR +.br +\-\-class\-cache\-size=\fIsize\fR +.RS 4 +クラス・キャッシュ・サイズをバイト単位で設定します。キロバイト(KB)を示すために\fBk\fRまたは\fBK\fRの文字を追加し、メガバイト(MB)を示すために\fBm\fRまたは\fBM\fRの文字を追加し、ギガバイト(GB)を示すために\fBg\fRまたは\fBG\fRを追加します。デフォルトでは、クラス・キャッシュ・サイズは50バイトに設定されます。次の例は、1024バイト(1 KB)に設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-css=100\fR +\fB\-css=1k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-co +.br +\-\-compile\-only +.RS 4 +スクリプトを実行せずにコンパイルします。 +.RE +.PP +\-cp \fIpath\fR +.br +\-classpath \fIpath\fR +.RS 4 +サポートするクラスへのパスを指定します。複数のパスを設定するには、このオプションを繰り返すか、または各パスをコロン(:)で区切ります。 +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +プロパティ名に値を割り当てることで、スクリプトに渡すシステム・プロパティを設定します。次の例で、対話型モードでNashornを呼び出して、\fBmyValue\fRを\fBmyKey\fRという名前のプロパティに割り当てる方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-DmyKey=myValue\fR\fR +\fBjjs> \fR\fB\fBjava\&.lang\&.System\&.getProperty("myKey")\fR\fR +\fBmyValue\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを繰り返し使用すると、複数のプロパティを設定できます。 +.RE +.PP +\-d=\fIpath\fR +.br +\-\-dump\-debug\-dir=\fIpath\fR +.RS 4 +クラス・ファイルをダンプするディレクトリへのパスを指定します。 +.RE +.PP +\-\-debug\-lines +.RS 4 +クラス・ファイル内の行番号表を生成します。デフォルトでは、このオプションは有効になっています。無効にするには\fB\-\-debug\-lines=false\fRを指定します。 +.RE +.PP +\-\-debug\-locals +.RS 4 +クラス・ファイル内のローカル変数を生成します。 +.RE +.PP +\-doe +.br +\-\-dump\-on\-error +.RS 4 +エラーが発生したときに、フル・スタック・トレースを提供します。デフォルトでは、簡単なエラー・メッセージのみが出力されます。 +.RE +.PP +\-\-early\-lvalue\-error +.RS 4 +無効な左辺値式が早期エラーとして(つまり、コードが解析されるときに)報告されます。デフォルトでは、このオプションは有効になっています。無効にするには\fB\-\-early\-lvalue\-error=false\fRを指定します。無効な場合、無効な左辺値式はコードが実行されるまで報告されません。 +.RE +.PP +\-\-empty\-statements +.RS 4 +空の文をJavaの抽象構文ツリーに保存します。 +.RE +.PP +\-fv +.br +\-\-fullversion +.RS 4 +完全なNashornバージョン文字列を出力します。 +.RE +.PP +\-\-function\-statement\-error +.RS 4 +関数の宣言が文として使用されるとエラー・メッセージが出力されます。 +.RE +.PP +\-\-function\-statement\-warning +.RS 4 +関数の宣言が文として使用されると警告メッセージが出力されます。 +.RE +.PP +\-fx +.RS 4 +スクリプトをJavaFXアプリケーションとして起動します。 +.RE +.PP +\-h +.br +\-help +.RS 4 +オプションのリストとその説明を出力します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定した\fBjava\fR起動オプションをJVMに渡します。次の例で、対話型モードでNashornを呼び出して、JVMによって使用される最大メモリーを4 GBに設定する方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-J\-Xmx4g\fR\fR +\fBjjs> \fR\fB\fBjava\&.lang\&.Runtime\&.getRuntime()\&.maxMemory()\fR\fR +\fB3817799680\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +このオプションを繰り返し使用すると、複数の\fBjava\fRコマンド・オプションを渡すことができます。 +.RE +.PP +\-\-language=[es5] +.RS 4 +ECMAScript言語バージョンを指定します。デフォルトのバージョンはES5です。 +.RE +.PP +\-\-lazy\-compilation +.RS 4 +レイジー・コード生成戦略(つまり、スクリプト全体が一度にコンパイルされない)を有効にします。このオプションは試験的なものです。 +.RE +.PP +\-\-loader\-per\-compile +.RS 4 +コンパイルごとに新しいクラス・ローダーを作成します。デフォルトでは、このオプションは有効になっています。無効にするには\fB\-\-loader\-per\-compile=false\fRを指定します。 +.RE +.PP +\-\-log=\fIsubsystem\fR:\fIlevel\fR +.RS 4 +指定されたサブシステムに対して、特定のレベルでロギングを実行します。カンマで区切って複数のサブシステムのロギング・レベルを指定できます。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-\-log=fields:finest,codegen:info\fR +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-\-optimistic\-types=[true|false] +.RS 4 +再コンパイルの最適化を解除してオプティミスティック・タイプ仮定を有効または無効にします。オプティミスティック・タイプを使用した実行によって最終的な速度が向上しますが、ウォームアップ時間が増える場合があります。 +.RE +.PP +\-\-package=\fIname\fR +.RS 4 +生成されたクラス・ファイルを追加するパッケージを指定します。 +.RE +.PP +\-\-parse\-only +.RS 4 +コンパイルせずにコードを解析します。 +.RE +.PP +\-\-print\-ast +.RS 4 +抽象構文ツリーを出力します。 +.RE +.PP +\-\-print\-code +.RS 4 +バイトコードを出力します。 +.RE +.PP +\-\-print\-lower\-ast +.RS 4 +掘り下げた抽象構文ツリーを出力します。 +.RE +.PP +\-\-print\-lower\-parse +.RS 4 +掘り下げた解析ツリーを出力します。 +.RE +.PP +\-\-print\-no\-newline +.RS 4 +その他の\fB\-\-print*\fRオプションで強制的に1行で出力します。 +.RE +.PP +\-\-print\-parse +.RS 4 +解析ツリーを出力します。 +.RE +.PP +\-\-print\-symbols +.RS 4 +記号表を出力します。 +.RE +.PP +\-pcs +.br +\-\-profile\-callsites +.RS 4 +呼び出しサイトのプロファイル・データをダンプします。 +.RE +.PP +\-scripting +.RS 4 +シェルのスクリプト機能を有効にします。 +.RE +.PP +\-\-stderr=\fIfilename\fR|\fIstream\fR|\fItty\fR +.RS 4 +標準エラー・ストリームを指定したファイル、ストリーム(たとえば\fBstdout\fR)に、またはテキスト端末にリダイレクトします。 +.RE +.PP +\-\-stdout=\fIfilename\fR|\fIstream\fR|\fItty\fR +.RS 4 +標準出力ストリームを指定したファイル、ストリーム(たとえば\fBstderr\fR)に、またはテキスト端末にリダイレクトします。 +.RE +.PP +\-strict +.RS 4 +標準(ECMAScript Edition 5\&.1)への準拠を強化するstrictモードを有効にし、これにより共通のコーディング・エラーを簡単に検出できるようになります。 +.RE +.PP +\-t=\fIzone\fR +.br +\-timezone=\fIzone\fR +.RS 4 +スクリプトの実行に対し指定したタイムゾーンを設定します。OSで設定されたタイムゾーンをオーバーライドし、\fBDate\fRオブジェクトで使用されます。 +.RE +.PP +\-tcs=\fIparameter\fR +.br +\-\-trace\-callsites=\fIparameter\fR +.RS 4 +呼出しサイトのトレースのモードを有効にします。使用可能なパラメータは、次のとおりです。 +.PP +miss +.RS 4 +呼出しサイトのミスをトレースします。 +.RE +.PP +enterexit +.RS 4 +呼出しサイトへの出入りをトレースします。 +.RE +.PP +objects +.RS 4 +オブジェクトのプロパティを出力します。 +.RE +.RE +.PP +\-\-verify\-code +.RS 4 +バイトコードを実行する前に検証します。 +.RE +.PP +\-v +.br +\-version +.RS 4 +Nashornバージョン文字列を出力します。 +.RE +.PP +\-xhelp +.RS 4 +コマンドライン・オプションの拡張ヘルプを出力します。 +.RE +.SH "例" +.PP +\fB例 1 \fRNashornを使用したスクリプトの実行 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjjs script\&.js\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 2 \fR対話型モードでのNashornの実行 +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs\fR\fR +\fBjjs> \fR\fB\fBprintln("Hello, World!")\fR\fR +\fBHello, World!\fR +\fBjjs> \fR\fB\fBquit()\fR\fR +\fB>>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fB例 3 \fRNashornへの引数の渡し +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-\- a b c\fR\fR +\fBjjs> \fR\fB\fBarguments\&.join(", ")\fR\fR +\fBa, b, c\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "関連項目" +.PP +\fBjrunscript\fR +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jmap.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jmap.1 new file mode 100755 index 0000000..4d558e6 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jmap.1 @@ -0,0 +1,192 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jmap +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jmap" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jmap \- プロセスやコア・ファイルまたはリモート・デバッグ・サーバーの、共用オブジェクト・メモリー・マップまたはヒープ・メモリーの詳細を出力します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjmap\fR [ \fIoptions\fR ] \fIpid\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjmap\fR [ \fIoptions\fR ] \fIexecutable\fR \fIcore\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjmap\fR [ \fIoptions\fR ] [ \fIpid\fR ] \fIserver\-id\fR@ ] \fIremote\-hostname\-or\-IP\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIpid\fR +.RS 4 +出力するメモリー・マップのプロセスID。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +出力するメモリー・マップのコア・ファイル。 +.RE +.PP +\fIremote\-hostname\-or\-IP\fR +.RS 4 +リモート・デバッグ・サーバーの\fBホスト名\fRまたは\fBIP\fRアドレス。jsadebugd(1)を参照してください。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のリモート・ホストで実行している場合の、オプション固有のID。 +.RE +.SH "説明" +.PP +\fBjmap\fRコマンドは、指定されたプロセスやコア・ファイルまたはリモート・デバッグ・サーバーの、共用オブジェクト・メモリー・マップまたはヒープ・メモリーの詳細を出力します。指定されたプロセスが64ビットJava Virtual Machine (JVM)上で実行されている場合、\fB\-J\-d64\fRオプションを指定する必要がある場合があります。次に例を示します。\fBjmap\fR +\fB\-J\-d64 \-heap pid\fR。 +.PP +\fB注意:\fR +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。\fBdbgeng\&.dll\fRファイルが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。\fBPATH\fR環境変数には、ターゲット・プロセスによって使用される\fBjvm\&.dll\fRの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。次に例を示します。\fBset PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR。 +.SH "オプション" +.PP +<no option> +.RS 4 +オプションを使用しない場合、\fBjmap\fRコマンドは共用オブジェクト・マッピングを出力します。ターゲットJVMにロードされた共用オブジェクトごとに、開始アドレス、マッピングのサイズおよび共用オブジェクト・ファイルのフルパスが出力されます。この動作は、Oracle Solaris +\fBpmap\fRユーティリティと類似しています。 +.RE +.PP +\-dump:[live,] format=b, file=\fIfilename\fR +.RS 4 +Javaヒープを\fBhprof\fRバイナリ形式で\fBfilename\fRにダンプします。\fBlive\fRサブオプションはオプションですが、指定した場合、ヒープ内のアクティブなオブジェクトのみがダンプされます。ヒープ・ダンプを参照するには、jhat(1)コマンドを使用して生成されたファイルを読み取ります。 +.RE +.PP +\-finalizerinfo +.RS 4 +ファイナライズを待っているオブジェクトに関する情報を出力します。 +.RE +.PP +\-heap +.RS 4 +使用されているガベージ・コレクションのヒープ・サマリー、ヘッダー構成、および世代関連のヒープ使用状況を出力します。さらに、internされた文字列の数とサイズも出力されます。 +.RE +.PP +\-histo[:live] +.RS 4 +ヒープのヒストグラムを出力します。Javaクラスごとに、オブジェクトの数、バイト単位でのメモリー・サイズ、および完全修飾クラス名が出力されます。JVMの内部クラス名はアスタリスク(*)の接頭辞を付けて出力されます。\fBlive\fRサブオプションが指定された場合、アクティブなオブジェクトのみがカウントされます。 +.RE +.PP +\-clstats +.RS 4 +Javaヒープの、クラス・ローダー関連の統計データを出力します。クラス・ローダーごとに、その名前、状態、アドレス、親クラス・ローダー、およびクラス・ローダーがロードしたクラスの数とサイズが出力されます。 +.RE +.PP +\-F +.RS 4 +強制します。PIDが応答しないときに、このオプションを\fBjmap \-dump\fRまたは\fBjmap \-histo\fRオプションとともに使用します。このモードでは、\fBlive\fRサブオプションはサポートされません。 +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBjmap\fRコマンドを実行しているJava Virtual Machineに\fBflag\fRを渡します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jhat(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jps.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jps.1 new file mode 100755 index 0000000..76a96ec --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jps.1 @@ -0,0 +1,251 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jps +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: モニタリング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jps" "1" "2013å¹´11月21日" "JDK 8" "モニタリング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jps \- ターゲット・システム上で計測されたJava仮想マシン(JVM)を一覧表示します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps\fR [ \fIoptions\fR ] [ \fIhostid\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIhostid\fR +.RS 4 +プロセス・レポートを生成するホストの識別子。\fBhostid\fRには、通信プロトコル、ポート番号、実装に固有な他のデータを指定したオプション・コンポーネントを含めることができます。ホスト識別子を参照してください。 +.RE +.SH "説明" +.PP +\fBjps\fRコマンドは、ターゲット・システム上で計測されたJava HotSpot VMを一覧表示します。このコマンドで表示できるレポート情報は、アクセス権を持ったJVMに関するものに限定されます。 +.PP +\fBhostid\fRを指定せずに\fBjps\fRコマンドを実行した場合、ローカル・ホストで計測されたJVMが検索されます。\fBhostid\fRを指定して起動した場合、指定されたプロトコルとポートを使用して、指定されたホスト上のJVMを検索します。\fBjstatd\fRプロセスがターゲット・ホスト上で実行されていると想定されます。 +.PP +\fBjps\fRコマンドは、ターゲット・システムで計測された各JVMについて、ローカルVM識別子、つまり\fBlvmid\fRをレポートします。\fBlvmid\fRは、一般的にはJVMプロセスに対するオペレーティング・システムのプロセス識別子ですが、必ずしもそうであるとは限りません。オプションを指定しない場合、\fBjps\fRによって、各Javaアプリケーションの\fBlvmid\fRが一覧表示され、それぞれにアプリケーションのクラス名またはJARファイル名が簡単な形式で示されます。この簡単な形式のクラス名とJARファイル名では、クラスのパッケージ情報またはJARファイル・パス情報が省略されています。 +.PP +\fBjps\fRコマンドは、Java起動ツールを使用してmainメソッドに渡されるクラス名と引数を検索します。独自の起動ツールを使用してターゲットJVMを起動した場合は、\fBmain\fRメソッドに渡されるクラス名またはJARファイル名と引数は利用できません。この場合、\fBjps\fRコマンドは、\fBmain\fRメソッドに渡されるクラス名またはJARファイル名と引数に対して、文字列\fBUnknown\fRを出力します。 +.PP +\fBjps\fRコマンドで生成されるJVMのリストは、このコマンドを実行するプリンシパルに与えられたアクセス権に基づき、制限される場合があります。このコマンドは、オペレーティング・システム独自のアクセス制御機構による決定に基づいて、プリンシパルにアクセス権が与えられているJVMのみを一覧表示します。 +.SH "オプション" +.PP +\fBjps\fRコマンドでは、コマンドの出力を変更するオプションが多数サポートされています。将来、これらのオプションは、変更または廃止される可能性があります。 +.PP +\-q +.RS 4 +クラス名、JARファイル名、および\fBmain\fRメソッドに渡された引数の出力を抑制し、ローカルVM識別子の一覧のみを生成します。 +.RE +.PP +\-m +.RS 4 +\fBmain\fRメソッドに渡される引数を出力します。この出力は、組み込まれているJVMに対して\fBnull\fRになることもあります。 +.RE +.PP +\-l +.RS 4 +アプリケーションの\fBmain\fRクラスのフル・パッケージ名、またはアプリケーションのJARファイルへのフルパス名を出力します。 +.RE +.PP +\-v +.RS 4 +JVMに渡される引数を表示します。 +.RE +.PP +\-V +.RS 4 +クラス名、JARファイル名、およびmaiメソッドに渡された引数の出力を抑制し、ローカルVM識別子の一覧のみを生成します。 +.RE +.PP +\-J\fBoption\fR +.RS 4 +JVMに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されている\fBオプション\fRを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "ホスト識別子" +.PP +ホスト識別子、つまり\fBhostid\fRは、ターゲット・システムを示す文字列です。\fBhostid\fR文字列の構文は、URIの構文に対応しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][[//]hostname][:port][/servername]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fIprotocol\fR +.RS 4 +通信プロトコルです。\fBprotocol\fRが省略され、\fBhostname\fRが指定されていない場合、デフォルトのプロトコルが、プラットフォーム固有の最適化されたローカル・プロトコルになります。プロトコルが省略され、ホスト名が指定されている場合は、デフォルト・プロトコルは\fBrmi\fRになります。 +.RE +.PP +hostname +.RS 4 +ターゲット・ホストを示すホスト名またはIPアドレスです。\fBhostname\fRパラメータが省略されている場合は、ターゲット・ホストはローカル・ホストになります。 +.RE +.PP +port +.RS 4 +リモート・サーバーと通信するためのデフォルト・ポートです。\fBhostname\fRパラメータが省略されているか、\fBprotocol\fRパラメータが、最適化されたローカル・プロトコルを指定している場合、\fBport\fRパラメータは無視されます。それ以外の場合、\fBport\fRパラメータの扱いは、実装によって異なります。デフォルトの +\fBrmi\fRプロトコルの場合、\fBport\fRパラメータは、リモート・ホスト上のrmiregistryのポート番号を示します。\fBport\fRパラメータが省略されているか、\fBprotocol\fRパラメータが\fBrmi\fRを示している場合、デフォルトのrmiregistryポート(1099)が使用されます。 +.RE +.PP +servername +.RS 4 +このパラメータの扱いは、実装によって異なります。最適化されたローカル・プロトコルの場合、このフィールドは無視されます。\fBrmi\fRプロトコルの場合、このパラメータは、リモート・ホスト上のRMIリモート・オブジェクトの名前を示す文字列になります。詳細は、\fBjstatd\fRコマンドの\fB\-n\fRオプションを参照してください。 +.RE +.SH "出力フォーマット" +.PP +\fBjps\fRコマンドの出力は、次のパターンに従います。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBlvmid [ [ classname | JARfilename | "Unknown"] [ arg* ] [ jvmarg* ] ]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +すべての出力トークンは空白文字で区切られます。\fBarg\fR値の中で空白を使用すると、実際の定位置パラメータに引数をマッピングしようとするときに、あいまいになります。 +.PP +\fB注意:\fR +将来のリリースでこの形式は変更される可能性があるため、\fBjps\fRの出力を解析するスクリプトは作成しないことをお薦めします。\fBjps\fR出力を解析するスクリプトを作成すると、このツールの将来のリリースで、作成したスクリプトの変更が必要になる可能性があります。 +.SH "例" +.PP +この項では、\fBjps\fRコマンドの例を示します。 +.PP +ローカル・ホスト上で計測されたJVMを一覧表示する場合: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps\fR +\fB18027 Java2Demo\&.JAR\fR +\fB18032 jps\fR +\fB18005 jstat\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、リモート・ホスト上で計測されたJVMを一覧表示します。この例では、\fBjstat\fRサーバーと、その内部RMIレジストリまたは別の外部rmiregistryプロセスのいずれかが、リモート・ホストのデフォルト・ポート(ポート1099)で実行されていると想定しています。また、ローカル・ホストが、リモート・ホストへの有効なアクセス権を持っていることも想定しています。この例には、\fB\-l\fRオプションも含まれ、クラス名またはJARファイル名を詳細な形式で出力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps \-l remote\&.domain\fR +\fB3002 /opt/jdk1\&.7\&.0/demo/jfc/Java2D/Java2Demo\&.JAR\fR +\fB2857 sun\&.tools\&.jstatd\&.jstatd\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、RMIレジストリにデフォルトではないポートを使用して、リモート・ホスト上で計測されたJVMを一覧表示します。この例では、内部RMIレジストリがポート2002にバインドされた\fBjstatd\fRサーバーが、リモート・ホスト上で実行されていると想定しています。また、\fB\-m\fRオプションを使用して、一覧表示されたそれぞれのJavaアプリケーションの\fBmain\fRメソッドに渡される引数を組み込んでいます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjps \-m remote\&.domain:2002\fR +\fB3002 /opt/jdk1\&.7\&.0/demo/jfc/Java2D/Java2Demo\&.JAR\fR +\fB3102 sun\&.tools\&.jstatd\&.jstatd \-p 2002\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstatd(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jrunscript.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jrunscript.1 new file mode 100755 index 0000000..9beb79e --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jrunscript.1 @@ -0,0 +1,194 @@ +'\" t +.\" Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jrunscript +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: スクリプティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jrunscript" "1" "2013å¹´11月21日" "JDK 8" "スクリプティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jrunscript \- 対話型モードとバッチ・モードをサポートするコマンド行スクリプト・シェルを実行します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript\fR [\fIoptions\fR] [\fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIarguments\fR +.RS 4 +引数を使用する場合、オプションまたはコマンド名の直後に記述してください。引数を参照してください。 +.RE +.SH "説明" +.PP +\fBjrunscript\fRコマンドは、言語に依存しないコマンド行スクリプト・シェルです。\fBjrunscript\fRは、対話型(read\-eval\-print)モードとバッチ(\fB\-f\fRオプション)・モードの両方のスクリプト実行をサポートします。デフォルトの使用言語はJavaScriptですが、\fB\-l\fRオプションを使用すれば他の言語も指定できます。\fBjrunscript\fRコマンドは、Javaとスクリプト言語との通信を使用して探求的なプログラミング・スタイルをサポートします。 +.SH "オプション" +.PP +\-classpath \fIpath\fR +.RS 4 +スクリプトがアクセスする必要のあるクラス・ファイルの場所を示します。 +.RE +.PP +\-cp \fIpath\fR +.RS 4 +\fB\-classpath\fR +\fIpath\fRと同じです。 +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +Javaのシステム・プロパティを設定します。 +.RE +.PP +\-J\fIflag\fR +.RS 4 +\fBflag\fRを、\fBjrunscript\fRコマンドが実行されているJava仮想マシンに直接渡します。 +.RE +.PP +\-I \fIlanguage\fR +.RS 4 +指定されたスクリプト言語を使用します。デフォルトではJavaScriptが使用されます。他のスクリプト言語を使用するには、\fB\-cp\fRまたは\fB\-classpath\fRオプションを使用して、対応するスクリプト・エンジンのJARファイルを指定する必要があります。 +.RE +.PP +\-e \fIscript\fR +.RS 4 +指定されたスクリプトを評価します。このオプションを使用すれば、コマンドラインにすべてが指定された1行スクリプトを実行できます。 +.RE +.PP +\-encoding \fIencoding\fR +.RS 4 +スクリプト・ファイルの読取り時に使用する文字エンコーディングを指定します。 +.RE +.PP +\-f \fIscript\-file\fR +.RS 4 +指定されたスクリプト・ファイル(バッチ・モード)を評価します。 +.RE +.PP +\-f \- +.RS 4 +標準入力からスクリプトを読み取り、それを評価します(対話型モード)。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-? +.RS 4 +ヘルプ・メッセージを表示して終了します。 +.RE +.PP +\-q +.RS 4 +利用可能なすべてのスクリプト・エンジンを一覧表示したあと、終了します。 +.RE +.SH "引数" +.PP +argumentsが存在していて、かつ\fB\-e\fR、\fB\-f\fRのいずれのオプションも使用されなかった場合、最初の引数がスクリプト・ファイルとなり、他の引数が存在する場合はスクリプトに渡されます。argumentsと、\fB\-e\fRまたは\fB\-f\fRオプションが使用されている場合、すべてのargumentsがスクリプトに渡されます。arguments、\fB\-e\fR、\fB\-f\fRがどれも存在しなかった場合は、対話型モードが使用されます。スクリプトからスクリプト引数を使用するには、\fBarguments\fRという名前の\fBString\fR配列型のエンジン変数を使用します。 +.SH "例" +.SS "インライン・スクリプトの実行" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript \-e "print(\*(Aqhello world\*(Aq)"\fR +\fBjrunscript \-e "cat(\*(Aqhttp://www\&.example\&.com\*(Aq)"\fR + +.fi +.if n \{\ +.RE +.\} +.SS "指定された言語の使用およびスクリプト・ファイルの評価" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript \-l js \-f test\&.js\fR + +.fi +.if n \{\ +.RE +.\} +.SS "対話型モード" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript\fR +\fBjs> print(\*(AqHello World\en\*(Aq);\fR +\fBHello World\fR +\fBjs> 34 + 55\fR +\fB89\&.0\fR +\fBjs> t = new java\&.lang\&.Thread(function() { print(\*(AqHello World\en\*(Aq); })\fR +\fBThread[Thread\-0,5,main]\fR +\fBjs> t\&.start()\fR +\fBjs> Hello World\fR +\fB \fR +\fBjs>\fR + +.fi +.if n \{\ +.RE +.\} +.SS "スクリプト引数を指定したスクリプト・ファイルの実行" +.PP +test\&.jsファイルはスクリプト・ファイルです。\fBarg1\fR、\fBarg2\fRおよび\fBarg3\fRの各引数がスクリプトに渡されます。スクリプトはarguments配列を使用してこれらの引数にアクセスできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrunscript test\&.js arg1 arg2 arg3\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.PP +JavaScriptを使用している場合、ユーザー定義スクリプトを評価する前に、\fBjrunscript\fRコマンドによって特定の組込み関数およびオブジェクトが初期化されます(これらについては、次のjrunscript JavaScript組込みのAPI仕様に記載されています)。 +.PP +http://docs\&.oracle\&.com/javase/7/docs/technotes/tools/share/jsdocs/overview\-summary\&.html +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jsadebugd.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jsadebugd.1 new file mode 100755 index 0000000..116ee71 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jsadebugd.1 @@ -0,0 +1,155 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jsadebugd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jsadebugd" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jsadebugd \- Javaプロセスまたはコア・ファイルに接続し、デバッグ・サーバーとして機能します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjsadebugd\fR \fIpid\fR [ \fIserver\-id\fR ] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjsadebugd\fR \fIexecutable\fR \fIcore\fR [ \fIserver\-id\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIpid\fR +.RS 4 +デバッグ・サーバーが接続するプロセスのプロセスIDです。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。単一のプロセスに接続できるデバッグ・サーバーのインスタンスは、1つに制限されます。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +デバッグ・サーバーを接続するコア・ファイルです。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のマシン上で実行されている場合に必要になる、オプションの一意のIDです。このIDは、リモート・クライアントが、接続先のデバッグ・サーバーを特定するために使用する必要があります。このIDは、単一のマシン内で一意にする必要があります。 +.RE +.SH "説明" +.PP +\fBjsadebugd\fRコマンドは、Javaプロセスまたはコア・ファイルに接続し、デバッグ・サーバーとして機能します。\fBjstack\fR、\fBjmap\fRおよび\fBjinfo\fRなどのリモート・クライアントは、Java Remote Method Invocation (RMI)を使用しているサーバーに接続できます。\fBjsadebugd\fRコマンドを起動する前に、\fBrmiregistry\fRコマンドでRMIレジストリを次のように起動します。\fI$JAVA_HOME\fRはJDKのインストール・ディレクトリです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry \-J\-Xbootclasspath/p:$JAVA_HOME/lib/sajdi\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.PP +RMIレジストリが起動していない場合、\fBjsadebugd\fRコマンドはRMIレジストリを標準(1099)ポートで内部で起動します。デバッグ・サーバーは、\fBSIGINT\fRを送信することにより停止できます。SIGINTを送信するには、\fB[Ctrl] + [C]\fRを押します。 +.PP +\fB注意:\fR +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。\fBdbgeng\&.dll\fRが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。\fBPATH\fR環境変数には、ターゲット・プロセスによって使用されるjvm\&.dllの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。例: +\fBs\fR\fBet PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jinfo(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jmap(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstack(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstack.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstack.1 new file mode 100755 index 0000000..4e6f606 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstack.1 @@ -0,0 +1,194 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstack +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: トラブルシューティング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstack" "1" "2013å¹´11月21日" "JDK 8" "トラブルシューティング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jstack \- Javaプロセス、コア・ファイルまたはリモート・デバッグ・サーバーに対するJavaスレッドのスタック・トレースを出力します。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstack\fR [ \fIoptions\fR ] \fIpid\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstack\fR [ \fIoptions\fR ] \fIexecutable\fR \fIcore\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstack\fR [ \fIoptions\fR ] [ \fIserver\-id\fR@ ] \fIremote\-hostname\-or\-IP\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIpid\fR +.RS 4 +出力するスタック・トレースのプロセスIDです。プロセスはJavaプロセスである必要があります。マシン上で実行しているJavaプロセスの一覧を取得するには、jps(1)コマンドを使用します。 +.RE +.PP +\fI実行可能ファイル\fR +.RS 4 +コア・ダンプの作成元のJava実行可能ファイル。 +.RE +.PP +\fIコア\fR +.RS 4 +出力するスタック・トレースのコア・ファイルです。 +.RE +.PP +\fIremote\-hostname\-or\-IP\fR +.RS 4 +リモート・デバッグ・サーバーの\fBホスト名\fRまたは\fBIP\fRアドレス。jsadebugd(1)を参照してください。 +.RE +.PP +\fIserver\-id\fR +.RS 4 +複数のデバッグ・サーバーが同一のリモート・ホストで実行している場合の、オプション固有のID。 +.RE +.SH "説明" +.PP +\fBjstack\fRコマンドは、指定されたJavaプロセス、コア・ファイルまたはリモート・デバッグ・サーバーに対するJavaスレッドのJavaスタック・トレースを出力します。Javaフレームごとに、フルクラス名、メソッド名、バイトコード・インデックス(bci)、および行番号(利用可能な場合)が出力されます。\fB\-m\fRオプションを使用すると、\fBjstack\fRコマンドは、すべてのスレッドのJavaフレームとネイティブ・フレームの両方を、プログラム・カウンタ(PC)とともに出力します。ネイティブ・フレームごとに、PCに最も近いネイティブ・シンボル(利用可能な場合)が出力されます。C++分解名は分解解除されません。C++名を分解解除するには、このコマンドの出力を\fBc++filt\fRにパイプします。指定されたプロセスが64ビットJava仮想マシン上で実行されている場合は、\fB\-J\-d64\fRオプションを指定する必要があります(例: +\fBjstack \-J\-d64 \-m pid\fR)。 +.PP +\fB注意\fR +このユーティリティはサポート対象外であり、将来のJDKのリリースでは利用できなくなる可能性があります。dbgeng\&.dllファイルが存在していないWindowsシステムでは、Debugging Tools For Windowsをインストールしないとこれらのツールが正常に動作しません。また、\fBPATH\fR環境変数には、ターゲット・プロセスによって使用されるjvm\&.dllの場所、またはクラッシュ・ダンプ・ファイルが生成された場所が含まれるようにしてください。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBset PATH=<jdk>\ejre\ebin\eclient;%PATH%\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-F +.RS 4 +\fBjstack\fR +[\fB\-l\fR] +\fBpid\fRが応答しない場合にスタック・ダンプを強制します。 +.RE +.PP +\-l +.RS 4 +長形式のリスト。所有\fBjava\&.util\&.concurrent\fRの所有できるシンクロナイザの一覧など、ロックについての追加情報を印刷します。http://docs\&.oracle\&.com/javase/8/docs/api/java/util/concurrent/locks/AbstractOwnableSynchronizer\&.htmlにある +\fBAbstractOwnableSynchronizer\fRクラス記述を参照してください +.RE +.PP +\-m +.RS 4 +JavaおよびネイティブC/C++フレームの両方を持つ混合モードのスタック・トレースを出力します。 +.RE +.PP +\-h +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージが出力されます。 +.RE +.SH "既知の不具合" +.PP +混合モードのスタック・トレースでは、\fB\-m\fRオプションはリモート・デバッグ・サーバーでは機能しません。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +pstack(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +C++filt(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstat.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstat.1 new file mode 100755 index 0000000..b30b1ab --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstat.1 @@ -0,0 +1,625 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstat +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: モニタリング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstat" "1" "2015å¹´3月3日" "JDK 8" "モニタリング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jstat \- Java Virtual Machine (JVM)の統計をモニターします。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat\fR [ \fIgeneralOption\fR | \fIoutputOptions vmid\fR [ \fIinterval\fR[s|ms] [ \fIcount \fR] ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIgeneralOption\fR +.RS 4 +単独で使用する一般的なコマンド行オプションです(\fB\-help\fRまたは\fB\-options\fR)。一般的なオプションを参照してください。 +.RE +.PP +\fIoutputOptions\fR +.RS 4 +単一の\fBstatOption\fRと\fB\-t\fR、\fB\-h\fRおよび\fB\-J\fRのいずれかのオプションで構成される1つ以上の出力オプション。出力オプションを参照してください。 +.RE +.PP +\fIvmid\fR +.RS 4 +ターゲットJVMを示す文字列である仮想マシン識別子です。一般的な構文は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][//]lvmid[@hostname[:port]/servername]\fR + +.fi +.if n \{\ +.RE +.\} +\fBvmid\fR文字列の構文は、URIの構文に対応しています。\fBvmid\fR文字列は、ローカルJVMを表す単純な整数から、通信プロトコル、ポート番号、および他の実装固有の値を示す複雑な構造まで、様々に異なります。仮想マシン識別子を参照してください。 +.RE +.PP +\fIinterval\fR [s|ms] +.RS 4 +秒(s)またはミリ秒(ms)のうち指定した単位でのサンプリング間隔です。デフォルトの単位はミリ秒です。正の整数にする必要があります。指定した場合、\fBjstat\fRコマンドは各間隔で出力を生成します。 +.RE +.PP +\fIcount\fR +.RS 4 +表示するサンプル数です。デフォルト値は無限で、ターゲットJVMが終了するまで、または\fBjstat\fRコマンドが終了するまで、\fBjstat\fRコマンドは統計データを表示します。この値は、正の整数である必要があります。 +.RE +.SH "説明" +.PP +\fBjstat\fRコマンドは、設置されているJava HotSpot VMのパフォーマンス統計データを表示します。ターゲットJVMは、仮想マシン識別子または\fBvmid\fRオプションによって識別されます。 +.SH "仮想マシン識別子" +.PP +\fBvmid\fR文字列の構文は、URIの構文に対応しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][//]lvmid[@hostname[:port]/servername]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fIprotocol\fR +.RS 4 +通信プロトコルです。\fIprotocol\fR値が省略され、ホスト名が指定されていない場合、デフォルトのプロトコルが、プラットフォーム固有の最適化されたローカル・プロトコルになります。\fIprotocol\fR値が省略され、ホスト名が指定されている場合は、デフォルト・プロトコルは\fBrmi\fRになります。 +.RE +.PP +\fIlvmid\fR +.RS 4 +ターゲットJVMのローカル仮想マシン識別子です。\fBlvmid\fRは、システム上のJVMを一意に識別するプラットフォーム固有の値です。\fBlvmid\fRは、仮想マシン識別子の唯一の必須要素です。\fBlvmid\fRは、一般的にはターゲットJVMプロセスに対するオペレーティング・システムのプロセス識別子ですが、必ずしもそうであるとは限りません。\fBjps\fRコマンドを使用して、\fBlvmid\fRを特定できます。また、Solaris、LinuxおよびOS Xプラットフォームでは\fBps\fRコマンドを使用して、WindowsではWindowsタスク・マネージャを使用して、\fBlvmid\fRを特定できます。 +.RE +.PP +\fIhostname\fR +.RS 4 +ターゲット・ホストを示すホスト名またはIPアドレスです。\fIhostname\fR値が省略されている場合は、ターゲット・ホストはローカル・ホストになります。 +.RE +.PP +\fIport\fR +.RS 4 +リモート・サーバーと通信するためのデフォルト・ポートです。\fIhostname\fR値が省略されているか、最適化されたローカル・プロトコルが\fIprotocol\fR値に指定されている場合、\fIport\fR値は無視されます。それ以外の場合、\fBport\fRパラメータの扱いは、実装によって異なります。デフォルトの\fBrmi\fRプロトコルの場合、ポート値は、リモート・ホスト上のrmiregistryのポート番号を示します。\fIport\fR値が省略され、\fIprotocol\fR値で\fBrmi\fRが指定されている場合、デフォルトのrmiregistryポート(1099)が使用されます。 +.RE +.PP +\fIservername\fR +.RS 4 +\fBservername\fRパラメータの扱いは、実装によって異なります。最適化されたローカル・プロトコルの場合、このフィールドは無視されます。\fBrmi\fRプロトコルの場合、これは、リモート・ホスト上のRMIリソース・オブジェクトの名前を表します。 +.RE +.SH "オプション" +.PP +\fBjstat\fRコマンドは、一般的なオプションと出力オプションの2つのタイプのオプションをサポートしています。一般的なオプションを使用した場合、\fBjstat\fRコマンドは簡単な使用率およびバージョン情報を表示します。出力オプションによって、統計データ出力の内容と形式が決まります。 +.PP +すべてのオプションとその機能は、将来のリリースで変更または廃止される可能性があります。 +.SS "一般的なオプション" +.PP +いずれかの一般的なオプションを指定した場合、他のオプションまたはパラメータは一切指定できません。 +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.PP +\-options +.RS 4 +Staticオプションのリストを表示します。出力オプションを参照してください。 +.RE +.SS "出力オプション" +.PP +一般的なオプションを指定しない場合に、出力オプションを指定できます。出力オプションは、\fBjstat\fRコマンドの出力の内容と形式を決定し、単一の\fBstatOption\fRといずれかの出力オプション(\fB\-h\fR、\fB\-t\fRおよび\fB\-J\fR)で構成されます。\fBstatOption\fRは最初に記述する必要があります。 +.PP +出力は、各列が空白で区切られた表の形式になります。タイトルを含むヘッダー行によって、各列の意味がわかります。ヘッダーの表示頻度を設定するには、\fB\-h\fRオプションを使用します。列のヘッダー名は、様々なオプション間で一貫性が保たれています。一般に、2つのオプションで同じ名前の列が使用されていれば、2つの列のデータ・ソースは同じです。 +.PP +\fB\-t\fRオプションを使用すると、Timestampというラベルの付いたタイムスタンプの列が、出力の最初の列として表示されます。Timestamp列には、ターゲットJVMの起動からの経過時間が、秒単位で表示されます。タイムスタンプの精度は、様々な要因によって異なり、大量の負荷のかかったシステムでのスレッド・スケジュールの遅延により変動します。 +.PP +intervalおよびcountパラメータを使用して、\fBjstat\fRコマンドがその出力を表示する頻度と回数をそれぞれ指定します。 +.PP +\fB注意:\fR +将来のリリースでこの形式は変更される可能性があるため、\fBjstat\fRコマンドの出力を解析するスクリプトは作成しなでください。\fBjstat\fRコマンドの出力を解析するスクリプトを作成する場合は、このツールの将来のリリースで、そのスクリプトを変更する必要があることに留意してください。 +.PP +\-\fIstatOption\fR +.RS 4 +\fBjstat\fRコマンドが表示する統計データ情報を指定します。次に、利用可能なオプションの一覧を示します。特定のプラットフォーム・インストールのオプションを一覧表示するには、一般的なオプションの\fB\-options\fRを使用します。Statオプションおよび出力を参照してください。 +.sp +\fBclass\fR: クラス・ローダーの動作に関する統計データを表示します。 +.sp +\fBcompiler\fR: Java HotSpot VM Just\-in\-Timeコンパイラの動作に関する統計データを表示します。 +.sp +\fBgc\fR: ガベージ・コレクトされたヒープの動作に関する統計データを表示します。 +.sp +\fBgccapacity\fR: 世代ごとの容量と対応する領域に関する統計データを表示します。 +.sp +\fBgccause\fR: ガベージ・コレクション統計データのサマリー(\fB\-gcutil\fRと同じ)と、直前および現在(適用可能な場合)のガベージ・コレクション・イベントの原因を表示します。 +.sp +\fBgcnew\fR: New世代の動作に関する統計データを表示します。 +.sp +\fBgcnewcapacity\fR: New世代のサイズと対応する領域に関する統計データを表示します。 +.sp +\fBgcold\fR: Old世代の動作とメタスペースに関する統計データを表示します。 +.sp +\fBgcoldcapacity\fR: Old世代のサイズに関する統計データを表示します。 +.sp +\fBgcmetacapacity\fR: メタスペースのサイズに関する統計データを表示します。 +.sp +\fBgcutil\fR: ガベージ・コレクションのサマリーに関する統計データを表示します。 +.sp +\fBprintcompilation\fR: Java HotSpot VMコンパイル・メソッドの統計データを表示します。 +.RE +.PP +\-h \fIn\fR +.RS 4 +\fIn\fRサンプル(出力行)ごとに列ヘッダーを表示します。ここで、\fIn\fRは正の整数値です。デフォルト値は0です。この場合、データの最初の行の上に列ヘッダーが表示されます。 +.RE +.PP +\-t +.RS 4 +タイムスタンプ列を出力の最初の列として表示します。タイムスタンプは、ターゲットJVMの起動時からの経過時間です。 +.RE +.PP +\-J\fIjavaOption\fR +.RS 4 +\fBjavaOption\fRをJavaアプリケーション起動ツールに渡します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。オプションの完全なリストについては、java(1)を参照してください。 +.RE +.SS "Statオプションおよび出力" +.PP +次の情報は、\fBjstat\fRコマンドが各\fIstatOption\fRについて出力する列をまとめたものです。 +.PP +\-class \fIoption\fR +.RS 4 +クラス・ローダーの統計データ。 +.sp +\fBLoaded\fR: ロードされたクラスの数。 +.sp +\fBBytes\fR: ロードされたKBの数。 +.sp +\fBUnloaded\fR: アンロードされたクラスの数。 +.sp +\fBBytes\fR: アンロードされたKBの数。 +.sp +\fBTime\fR: クラスのロードやアンロード処理に要した時間。 +.RE +.PP +\-compiler \fIoption\fR +.RS 4 +Java HotSpot VM Just\-in\-Timeコンパイラの統計データ。 +.sp +\fBCompiled\fR: 実行されたコンパイル・タスクの数。 +.sp +\fBFailed\fR: 失敗したコンパイル・タスクの数。 +.sp +\fBInvalid\fR: 無効にされたコンパイル・タスクの数。 +.sp +\fBTime\fR: コンパイル・タスクの実行に要した時間。 +.sp +\fBFailedType\fR: 最後に失敗したコンパイルのコンパイル・タイプ。 +.sp +\fBFailedMethod\fR: 最後に失敗したコンパイルのクラス名とメソッド。 +.RE +.PP +\-gc \fIoption\fR +.RS 4 +ガベージ・コレクトされたヒープの統計データ。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBS0U\fR: Survivor領域0の使用率(KB)。 +.sp +\fBS1U\fR: Survivor領域1の使用率(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBEU\fR: Eden領域の使用率(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBOU\fR: Old領域の使用率(KB)。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBMU\fR: メタスペースの使用率(KB)。 +.sp +\fBCCSC\fR: 圧縮されたクラス領域の容量(KB)。 +.sp +\fBCCSU\fR: 使用されている圧縮されたクラス領域(KB)。 +.sp +\fBYGC\fR: 若い世代のガベージ・コレクション・イベントの数。 +.sp +\fBYGCT\fR: 若い世代のガベージ・コレクション時間。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gccapacity \fIoption\fR +.RS 4 +メモリー・プール世代および領域容量。 +.sp +\fBNGCMN\fR: New世代の最小容量(KB)。 +.sp +\fBNGCMX\fR: New世代の最大容量(KB)。 +.sp +\fBNGC\fR: New世代の現在の容量(KB)。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBOGCMN\fR: Old世代の最小容量(KB)。 +.sp +\fBOGCMX\fR: Old世代の最大容量(KB)。 +.sp +\fBOGC\fR: Old世代の現在の容量(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBMCMN\fR: メタスペースの最小容量(KB)。 +.sp +\fBMCMX\fR: メタスペースの最大容量(KB)。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBCCSMN\fR: 圧縮されたクラス領域の最小容量(KB)。 +.sp +\fBCCSMX\fR: 圧縮されたクラス領域の最大容量(KB)。 +.sp +\fBCCSC\fR: 圧縮されたクラス領域の容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.RE +.PP +\-gccause \fIoption\fR +.RS 4 +このオプションは、\fB\-gcutil\fRオプションと同じガベージ・コレクション統計データのサマリーを表示しますが、最後のガベージ・コレクション・イベントと(適用可能な場合は)現在のガベージ・コレクション・イベントの原因が含まれます。\fB\-gcutil\fRで一覧表示される列のほか、このオプションでは次の列が追加されます。 +.sp +\fBLGCC\fR: 最後のガベージ・コレクションの原因 +.sp +\fBGCC\fR: 現在のガベージ・コレクションの原因 +.RE +.PP +\-gcnew \fIoption\fR +.RS 4 +New世代の統計データ。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBS0U\fR: Survivor領域0の使用率(KB)。 +.sp +\fBS1U\fR: Survivor領域1の使用率(KB)。 +.sp +\fBTT\fR: 殿堂入りしきい値。 +.sp +\fBMTT\fR: 最大殿堂入りしきい値。 +.sp +\fBDSS\fR: 適切なSurvivorサイズ(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBEU\fR: Eden領域の使用率(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBYGCT\fR: 若い世代のガベージ・コレクション時間。 +.RE +.PP +\-gcnewcapacity \fIoption\fR +.RS 4 +New世代領域サイズの統計データ。 +.sp +\fBNGCMN\fR: New世代の最小容量(KB)。 +.sp +\fBNGCMX\fR: New世代の最大容量(KB)。 +.sp +\fBNGC\fR: New世代の現在の容量(KB)。 +.sp +\fBS0CMX\fR: Survivor領域0の最大容量(KB)。 +.sp +\fBS0C\fR: Survivor領域0の現在の容量(KB)。 +.sp +\fBS1CMX\fR: Survivor領域1の最大容量(KB)。 +.sp +\fBS1C\fR: Survivor領域1の現在の容量(KB)。 +.sp +\fBECMX\fR: Eden領域の最大容量(KB)。 +.sp +\fBEC\fR: Eden領域の現在の容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.RE +.PP +\-gcold \fIoption\fR +.RS 4 +OldおよびPermanent世代の統計データ。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBMU\fR: メタスペースの使用率(KB)。 +.sp +\fBCCSC\fR: 圧縮されたクラス領域の容量(KB)。 +.sp +\fBCCSU\fR: 使用されている圧縮されたクラス領域(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBOU\fR: Old領域の使用率(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gcoldcapacity \fIoption\fR +.RS 4 +Old世代の統計データ。 +.sp +\fBOGCMN\fR: Old世代の最小容量(KB)。 +.sp +\fBOGCMX\fR: Old世代の最大容量(KB)。 +.sp +\fBOGC\fR: Old世代の現在の容量(KB)。 +.sp +\fBOC\fR: Old領域の現在の容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gcmetacapacity \fIoption\fR +.RS 4 +Permanent世代の統計データ。 +.sp +\fBMCMN\fR: メタスペースの最小容量(KB)。 +.sp +\fBMCMX\fR: メタスペースの最大容量(KB)。 +.sp +\fBMC\fR: メタスペースの容量(KB)。 +.sp +\fBCCSMN\fR: 圧縮されたクラス領域の最小容量(KB)。 +.sp +\fBCCSMX\fR: 圧縮されたクラス領域の最大容量(KB)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-gcutil \fIoption\fR +.RS 4 +ガベージ・コレクション統計データのサマリー +.sp +\fBS0\fR: Survivor領域0の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBS1\fR: Survivor領域1の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBE\fR: Eden領域の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBO\fR: Old領域の使用率(現在の容量に対するパーセンテージ)。 +.sp +\fBM\fR: メタスペースの使用率(領域の現在の容量に対するパーセンテージ)。 +.sp +\fBCCS\fR: 圧縮されたクラス領域の使用率(パーセンテージ)。 +.sp +\fBYGC\fR: 若い世代のGCイベント数。 +.sp +\fBYGCT\fR: 若い世代のガベージ・コレクション時間。 +.sp +\fBFGC\fR: フルGCイベント数。 +.sp +\fBFGCT\fR: フルガベージ・コレクション時間。 +.sp +\fBGCT\fR: ガベージ・コレクション総時間。 +.RE +.PP +\-printcompilation \fIoption\fR +.RS 4 +Java HotSpot VMコンパイル・メソッドの統計データ。 +.sp +\fBCompiled\fR: 最近コンパイルされたメソッドで実行されたコンパイル・タスクの数。 +.sp +\fBSize\fR: 最近コンパイルされたメソッドのバイト・コードのバイト数。 +.sp +\fBType\fR: 最近コンパイルされたメソッドのコンパイル・タイプ。 +.sp +\fBMethod\fR: 最近コンパイルされたメソッドを特定するクラス名とメソッド名。クラス名では、名前空間の区切り文字として、ドット(\&.)のかわりにスラッシュ(/)が使用されます。メソッド名は、指定されたクラス内のメソッドです。これらの2つのフィールドの形式は、HotSpot +\fB\-XX:+PrintCompilation\fRオプションと対応しています。 +.RE +.SH "例" +.PP +この項では、21891の\fIlvmid\fRを持つローカルJVMをモニタリングする例を示します。 +.SS "gcutilオプション" +.PP +この例では、lvmid 21891に接続して、250ミリ秒間隔で7つのサンプルを取得し、\-\fBgcutil\fRオプションでの指定に従って出力を表示します。 +.PP +この例の出力は、若い世代のコレクションが3番目と4番目のサンプル間で行われたことを示しています。コレクションには0\&.078秒かかっており、オブジェクトがEden領域(E)からOld領域(O)に昇格したため、Old領域の使用率は66\&.80%から68\&.19%に増加しています。Survivor領域は、コレクション前は97\&.02%が使用されていましたが、コレクション後の使用は91\&.03%です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcutil 21891 250 7\fR +\fB S0 S1 E O M CCS YGC YGCT FGC FGCT GCT \fR +\fB 0\&.00 97\&.02 70\&.31 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 0\&.00 97\&.02 86\&.23 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 0\&.00 97\&.02 96\&.53 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 91\&.03 0\&.00 1\&.98 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 15\&.82 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 17\&.80 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 17\&.80 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +.fi +.if n \{\ +.RE +.\} +.SS "列ヘッダー文字列の繰返し" +.PP +この例では、lvmid 21891に接続して、250ミリ秒間隔でサンプルを取得し、\fB\-gcnew\fRオプションでの指定に従って出力を表示します。さらに、\fB\-h3\fRオプションを使用して、データが3行表示されるごとに列ヘッダーを出力します。 +.PP +この例では、ヘッダー文字列の繰返しが表示されているほか、2番目と3番目のサンプル間でYoung GCが行われたことがわかります。この継続時間は0\&.001秒でした。このコレクションでは、Survivor領域0の使用率(S0U)が適切なSurvivorサイズ(DSS)を超過することになるアクティブ・データが検出されました。この結果、オブジェクトは、Old世代(この出力には非表示)へ昇格され、殿堂入りしきい値(TT)が、31から2へ降格されました。 +.PP +別のコレクションが、5番目と6番目のサンプル間で行われています。このコレクションでは、Survivorがほとんど見られず、殿堂入りしきい値を31に戻しました。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcnew \-h3 21891 250\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 0\&.0 31\&.7 31 31 32\&.0 512\&.0 178\&.6 249 0\&.203\fR +\fB 64\&.0 64\&.0 0\&.0 31\&.7 31 31 32\&.0 512\&.0 355\&.5 249 0\&.203\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 21\&.9 250 0\&.204\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 245\&.9 250 0\&.204\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 421\&.1 250 0\&.204\fR +\fB 64\&.0 64\&.0 0\&.0 19\&.0 31 31 32\&.0 512\&.0 84\&.4 251 0\&.204\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 0\&.0 19\&.0 31 31 32\&.0 512\&.0 306\&.7 251 0\&.204\fR + +.fi +.if n \{\ +.RE +.\} +.SS "サンプルごとのタイムスタンプの挿入" +.PP +この例では、lvmid21891へ接続し、250ミリ秒間隔で3つのサンプルを取得しています。\fB\-t\fRオプションを使用して、最初の列にサンプルごとのタイムスタンプを表示しています。 +.PP +Timestamp列には、ターゲットJVMの起動時からの経過時間が、秒単位でレポートされています。さらに、\fB\-gcoldcapacity\fR出力では、割当リクエストまたは昇格リクエストあるいはその両方を満たすためにヒープが拡張するたびに、Old世代の容量(OGC)とOld領域の容量(OC)とが増加していることがわかります。81番目のフル・ガベージ・コレクション(FGC)の後、Old世代の容量(OGC)は11,696KBから13,820KBに増加しました。この世代(および領域)の最大容量は、60,544KB (OGCMX)なので、まだ拡張できる余裕が残されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBTimestamp OGCMN OGCMX OGC OC YGC FGC FGCT GCT\fR +\fB 150\&.1 1408\&.0 60544\&.0 11696\&.0 11696\&.0 194 80 2\&.874 3\&.799\fR +\fB 150\&.4 1408\&.0 60544\&.0 13820\&.0 13820\&.0 194 81 2\&.938 3\&.863\fR +\fB 150\&.7 1408\&.0 60544\&.0 13820\&.0 13820\&.0 194 81 2\&.938 3\&.863\fR + +.fi +.if n \{\ +.RE +.\} +.SS "リモートJVMのインストゥルメンテーションのモニター" +.PP +この例は、\fB\-gcutil\fRオプションを使用して、remote\&.domainというシステム上のlvmid 40496に接続し、サンプルを秒単位で無期限に取得しています。 +.PP +lvmidは、リモート・ホストの名前と結合されて、\fB40496@remote\&.domain\fRの\fIvmid\fRを構成しています。結果として、このvmidは、\fBrmi\fRプロトコルを使用して、リモート・ホスト上のデフォルトの\fBjstatd\fRサーバーと通信します。\fBjstatd\fRサーバーは、\fBrmiregistry\fRコマンドを使用して、\fBrmiregistry\fRコマンドのデフォルトのポート(ポート1099)にバインドされた\fBremote\&.domain\fRに配置されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcutil 40496@remote\&.domain 1000\fR +\fB\fI\&.\&.\&. output omitted\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstatd(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstatd.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstatd.1 new file mode 100755 index 0000000..d92ff23 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jstatd.1 @@ -0,0 +1,259 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstatd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: モニタリング・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstatd" "1" "2013å¹´11月21日" "JDK 8" "モニタリング・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jstatd \- Java仮想マシン(JVM)をモニターし、リモート・モニタリング・ツールがJVMに接続できるようにします。このコマンドは試験的なもので、サポートされていません。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd\fR [ \fIoptions\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +\fBjstatd\fRコマンドは、計測されたJava HotSpot VMの作成と終了をモニターし、ローカル・システム上で実行されているJVMに、リモート・モニタリング・ツールが接続できるようにするためのインタフェースを提供するRMIサーバー・アプリケーションです。 +.PP +\fBjstatd\fRサーバーでは、ローカル・ホストにRMIレジストリが必要になります。\fBjstatd\fRサーバーはデフォルト・ポートで、または\fB\-p\fR +\fBport\fRオプションで指定したポートで、RMIレジストリに接続しようとします。RMIレジストリが見つからない場合、\fB\-p\fR +\fBport\fRオプションで指定されたポート、または\fB\-p\fR +\fBport\fRオプションが省略されている場合は、デフォルトRMIレジストリにバインドされた\fBjstatd\fRアプリケーション内に、1つのRMIレジストリが作成されます。内部RMIレジストリの作成は、\fB\-nr\fRオプションを指定することによって中止できます。 +.SH "オプション" +.PP +\-nr +.RS 4 +既存のRMIレジストリが見つからない場合、\fBjstatd\fRプロセス内に内部RMIレジストリを作成しないようにします。 +.RE +.PP +\-p \fIport\fR +.RS 4 +RMIレジストリがあると予想されるポート番号です。見つからない場合は、\fB\-nr\fRオプションが指定されていなければ作成されます。 +.RE +.PP +\-n \fIrminame\fR +.RS 4 +RMIレジストリにおいて、リモートRMIオブジェクトがバインドされる名前です。デフォルト名は\fBJStatRemoteHost\fRです。複数の\fBjstatd\fRサーバーが同じホスト上で起動している場合、各サーバーのエクスポートしたRMIオブジェクトの名前は、このオプションを指定することによって、一意の名前にすることができます。ただし、このオプションを使用する場合、モニタリング・クライアントの\fBhostid\fRおよび\fBvmid\fR文字列に、その一意のサーバー名を含める必要があります。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +JVMに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されている\fBオプション\fRを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "セキュリティ" +.PP +\fBjstatd\fRサーバーは、適切なネイティブ・アクセス権を持つJVMのみをモニターできます。したがって、\fBjstatd\fRプロセスは、ターゲットJVMと同じユーザー資格証明で実行されている必要があります。Solaris、LinuxおよびOS Xオペレーティング・システムにおけるrootユーザーなどの一部のユーザー資格証明は、システム上の任意のJVMによってエクスポートされたインストゥルメンテーションへのアクセス権を持っています。このような資格証明で実行されている\fBjstatd\fRプロセスは、システム上のすべてのJVMをモニターできますが、セキュリティ上の別の問題が起こります。 +.PP +\fBjstatd\fRサーバーには、リモート・クライアントの認証機能がありません。そのため、\fBjstatd\fRサーバー・プロセスを実行すると、\fBjstatd\fRプロセスがアクセス権を持つすべてのJVMによるインストゥルメンテーションのエクスポートを、ネットワーク上のすべてのユーザーに公開することになります。この無防備な状態は、環境によっては望ましくない場合があるので、特に本番環境またはセキュアでないネットワークでは、\fBjstatd\fRプロセスを起動する前に、ローカル・セキュリティ・ポリシーを検討する必要があります。 +.PP +\fBjstatd\fRサーバーは、他のセキュリティ・マネージャがインストールされていない場合には、\fBRMISecurityPolicy\fRのインスタンスをインストールします。そのため、セキュリティ・ポリシー・ファイルを指定する必要があります。ポリシー・ファイルは、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.htmlにある +「デフォルトのPolicyの実装とポリシー・ファイルの構文」に準拠している必要があります +.PP +次のポリシー・ファイルでは、セキュリティ例外を発生せずに\fBjstatd\fRサーバーを実行できます。このポリシーは、すべてのコード・ベースへのあらゆるアクセス権を認めるポリシーよりも自由度が低いですが、\fBjstatd\fRサーバーを実行するために最低限必要なアクセス権のみを認めるポリシーよりも自由度が高くなっています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBgrant codebase "file:${java\&.home}/\&.\&./lib/tools\&.jar" { \fR +\fB permission java\&.security\&.AllPermission;\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +.PP +このポリシー設定を使用するには、このテキストを\fBjstatd\&.all\&.policy\fRというファイルにコピーし、次のように\fBjstatd\fRサーバーを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=jstatd\&.all\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.PP +より厳しいセキュリティを実施するサイトの場合、カスタム・ポリシー・ファイルを使用して、特定の信頼できるホストまたはネットワークにアクセスを制限することができます。ただし、このような方法は、IPアドレスの盗聴攻撃を受けやすくなります。セキュリティの問題について、カスタマイズしたポリシー・ファイルでも対処できない場合は、\fBjstatd\fRサーバーを実行せずに、\fBjstat\fRと\fBjps\fRツールをローカルで使用することが最も安全な方法になります。 +.SH "リモート・インタフェース" +.PP +\fBjstatd\fRプロセスがエクスポートするインタフェースは、独自に開発したものであり変更される予定です。ユーザーおよび開発者は、このインタフェースへの書込みを行わないでください。 +.SH "例" +.PP +次に、\fBjstatd\fRコマンドの例を示します。\fBjstatd\fRスクリプトによって、サーバーはバックグラウンドで自動的に起動します。 +.SS "内部RMIレジストリ" +.PP +この例は、内部RMIレジストリを使用した\fBjstatd\fRセッションの起動方法を表しています。この例では、デフォルトのRMIレジストリ・ポート(ポート1099)には、他のサーバーはバインドされていないと想定しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.SS "外部RMIレジストリ" +.PP +この例は、外部RMIレジストリを使用した\fBjstatd\fRセッションの起動を表しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry&\fR +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例では、ポート2020の外部RMIレジストリを使用して\fBjstatd\fRセッションを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjrmiregistry 2020&\fR +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy \-p 2020\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例では、ポート2020の外部RMIレジストリを使用して、\fBAlternateJstatdServerName\fRにバインドされている\fBjstatd\fRセッションを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry 2020&\fR +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy \-p 2020\fR +\fB \-n AlternateJstatdServerName\fR + +.fi +.if n \{\ +.RE +.\} +.SS "インプロセスRMIレジストリの作成の停止" +.PP +この例では、外部RMIレジストリがない場合に作成しない\fBjstatd\fRセッションを起動します。この例では、RMIレジストリがすでに実行されていると想定しています。RMIレジストリが実行されていない場合、エラー・メッセージが表示されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy \-nr\fR + +.fi +.if n \{\ +.RE +.\} +.SS "RMIロギングの有効化" +.PP +この例では、RMIロギング機能を有効化して\fBjstatd\fRセッションを起動します。この方法は、トラブルシューティングまたはサーバー活動のモニタリングに役立ちます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstatd \-J\-Djava\&.security\&.policy=all\&.policy\fR +\fB \-J\-Djava\&.rmi\&.server\&.logCalls=true\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jvisualvm.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jvisualvm.1 new file mode 100755 index 0000000..3a3abcb --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/jvisualvm.1 @@ -0,0 +1,107 @@ +'\" t +.\" Copyright (c) 2008, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jvisualvm +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaトラブルシューティング、プロファイリング、モニタリングおよび管理ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jvisualvm" "1" "2013å¹´11月21日" "JDK 8" "Javaトラブルシューティング、プロファイリング、モニタリン" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +jvisualvm \- Javaアプリケーションを視覚的に監視、トラブルシュートおよびプロファイルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjvisualvm\fR [ \fIoptions\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +Java VisualVMは、指定されたJava Virtual Machine (JVM)でJavaテクノロジ・ベースのアプリケーション(Javaアプリケーション)が実行されているときに、そのJavaアプリケーションに関する詳細な情報を提供する直感的なグラフィカル・ユーザー・インタフェースです。Java VisualVMという名前は、Java VisualVMがJVMソフトウェアに関する情報を視覚的に提供するという事実に由来しています。 +.PP +Java VisualVMは、いくつかのモニタリング、トラブルシューティングおよびプロファイリング・ユーティリティを1つのツールに統合します。たとえば、スタンドアロン・ツール\fBjmap\fR、\fBjinfo\fR、\fBjstat\fRおよび\fBjstack\fRで提供されている機能のほとんどが、Java VisualVMに組み込まれています。\fBjconsole\fRコマンドによって提供される一部の機能など、他の機能はオプションのプラグインとして追加できます。 +.PP +Java VisualVMは、Javaアプリケーションの開発者がアプリケーションのトラブルシューティングを行ったり、アプリケーションのパフォーマンスを監視および改善したりするのに役立ちます。Java VisualVMを使用すると、開発者はヒープ・ダンプの生成および解析、メモリー・リークの特定、ガベージ・コレクションの実行および監視、およびメモリーとCPUの簡易プロファイリングの実行が可能になります。プラグインでJava VisualVMの機能を拡張できます。たとえば、\fBjconsole\fRコマンドのほとんどの機能は、「MBean」タブおよびJConsole Plug\-in Wrapperプラグインを介して使用できます。標準のJava VisualVMプラグインのカタログから選択するには、Java VisualVMメニューの\fB「ツール」\fR、\fB「プラグイン」\fRを選択します。 +.PP +Java VisualVMを起動するには、次のコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB% jvisualvm <options>\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +次のオプションは、Java VisualVMを起動したときに実行可能になります。 +.PP +\-J\fIjvm_option\fR +.RS 4 +この\fBjvm_option\fRをJVMソフトウェアに渡します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java VisualVM開発者のサイト +http://visualvm\&.java\&.net/ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java SEドキュメントのJava VisualVM +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/visualvm/index\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/keytool.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/keytool.1 new file mode 100755 index 0000000..9b84d04 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/keytool.1 @@ -0,0 +1,2229 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: keytool +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: セキュリティ・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "keytool" "1" "2015å¹´3月3日" "JDK 8" "セキュリティ・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +keytool \- 暗号化鍵、X\&.509証明書チェーンおよび信頼できる証明書を含むキーストア(データベース)を管理します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool\fR [\fIcommands\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommands\fR +.RS 4 +コマンドを参照してください。これらのコマンドは、次のようにタスク別に分類されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +キーストアへのデータの作成または追加 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-gencert +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-genkeypair +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-genseckey +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-importcert +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-importpassword +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +別のキーストアの内容のインポート +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-importkeystore +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書リクエストの生成 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-certreq +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +データのエクスポート +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-exportcert +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +データの表示 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-list +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-printcert +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-printcertreq +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-printcrl +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +キーストアの管理 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-storepasswd +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-keypasswd +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-delete +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-changealias +.RE +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ヘルプの表示 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\-help +.RE +.RE +.RE +.SH "説明" +.PP +\fBkeytool\fRコマンドは、鍵と証明書を管理するためのユーティリティです。これにより、ユーザーは自分の公開鍵と秘密鍵のペアおよび関連する証明書を管理し、デジタル署名を使用した自己認証(他のユーザーまたはサービスに対して自分自身を認証すること)や、データの整合性と証明書に関するサービスを利用することができます。\fBkeytool\fRコマンドでは、通信しているピアの公開鍵をキャッシュすることもできます(証明書のフォームで)。 +.PP +証明書とは、あるエンティティ(人物、会社など)からのデジタル署名付きの文書のことです。証明書には、他のあるエンティティの公開鍵(およびその他の情報)が特別な値を持っていることが書かれています。(証明書を参照してください。)データにデジタル署名が付いている場合は、デジタル署名を検証することで、データの整合性およびデータが本物であることをチェックできます。データの整合性とは、データが変更されたり、改変されたりしていないことを意味します。また、データが本物であるとは、そのデータが、データを作成して署名したと称する人物から渡されたデータであることを意味します。 +.PP +また、\fBkeytool\fRコマンドを使用すれば、対称暗号化/復号化(DES)で使用される秘密鍵およびパスフレーズを管理することもできます。 +.PP +\fBkeytool\fRコマンドは、鍵と証明書をキーストアに格納します。キーストアの別名を参照してください。 +.SH "コマンドとオプションに関する注意" +.PP +様々なコマンドとその説明については、コマンドを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +どのコマンド名およびオプション名にも先頭にマイナス記号(\-)が付きます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +各コマンドのオプションは任意の順序で指定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +イタリックになっていないすべての項目、または中カッコか角カッコで囲まれているすべての項目は、そのとおりに指定する必要があります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションを囲む中カッコは、そのオプションをコマンド行で指定しなかった場合に、デフォルト値が使用されることを意味します。オプションのデフォルト値を参照してください。中カッコは、\fB\-v\fR、\fB\-rfc\fRおよび\fB\-J\fRオプションを囲むためにも使用されますが、これらのオプションはコマンド行で指定された場合にのみ意味を持ちます。指定されていない場合以外、デフォルト値はありません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションを囲む角カッコは、そのオプションをコマンド行で指定しなかった場合に、値の入力を求められることを意味します。\fB\-keypass\fRオプションの場合、オプションをコマンド行で指定しなかった場合は、\fBkeytool\fRコマンドがまずキーストアのパスワードを使用して非公開/秘密鍵の復元を試みます。この試みが失敗した場合、\fBkeytool\fRコマンドにより、非公開/秘密鍵のパスワードの入力を求められます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +イタリックの項目の実際の値(オプションの値)は、指定する必要があります。たとえば、\fB\-printcert\fRコマンドの形式は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-printcert {\-file \fR\fB\fIcert_file\fR\fR\fB} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +\fB\-printcert\fRコマンドを指定する場合は、\fIcert_file\fRを実際のファイル名で置き換えます。例: +\fBkeytool \-printcert \-file VScert\&.cer\fR +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +オプションの値に空白(スペース)が含まれている場合は、値を引用符で囲む必要があります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-help\fRオプションがデフォルトです。\fBkeytool\fRコマンドは、\fBkeytool \-help\fRと同じです。 +.RE +.SH "オプションのデフォルト値" +.PP +次の例で、様々なオプション値のデフォルト値を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-alias "mykey"\fR +\fB \fR +\fB\-keyalg\fR +\fB "DSA" (when using \-genkeypair)\fR +\fB "DES" (when using \-genseckey)\fR +\fB \fR +\fB\-keysize\fR +\fB 2048 (when using \-genkeypair and \-keyalg is "RSA")\fR +\fB 1024 (when using \-genkeypair and \-keyalg is "DSA")\fR +\fB 256 (when using \-genkeypair and \-keyalg is "EC")\fR +\fB 56 (when using \-genseckey and \-keyalg is "DES")\fR +\fB 168 (when using \-genseckey and \-keyalg is "DESede")\fR +\fB \fR +\fB\-validity 90\fR +\fB \fR +\fB\-keystore <the file named \&.keystore in the user\*(Aqs home directory>\fR +\fB \fR +\fB\-storetype <the value of the "keystore\&.type" property in the\fR +\fB security properties file, which is returned by the static\fR +\fB getDefaultType method in java\&.security\&.KeyStore>\fR +\fB \fR +\fB\-file\fR +\fB stdin (if reading)\fR +\fB stdout (if writing)\fR +\fB \fR +\fB\-protected false\fR + +.fi +.if n \{\ +.RE +.\} +.PP +公開/秘密鍵ペアの生成において、署名アルゴリズム(\fB\-sigalg\fRオプション)は、基になる秘密鍵のアルゴリズムから派生します。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +基になる秘密鍵がDSAタイプである場合は、\fB\-sigalg\fRオプションのデフォルト値はSHA1withDSAになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +基になる秘密鍵がRSAタイプである場合は、\fB\-sigalg\fRオプションのデフォルト値はSHA256withRSAになります。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +基になる秘密鍵がECタイプである場合は、\fB\-sigalg\fRオプションのデフォルト値はSHA256withECDSAになります。 +.RE +.PP +\fB\-keyalg\fRおよび\fB\-sigalg\fR引数の完全なリストについては、 +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppAの「Java Cryptography Architecture (JCA) Reference Guide」を参照してください。 +.SH "一般オプション" +.PP +\fB\-v\fRオプションは、\fB\-help\fRコマンドを除くすべてのコマンドで使用できます。\fB\-v\fRオプションを指定した場合、コマンドは冗長モードで実行され、詳細な情報が出力されます。 +.PP +任意のコマンドで指定できる\fB\-Jjavaoption\fR引数もあります。\fB\-Jjavaoption\fRを指定した場合、指定された\fBjavaoption\fR文字列がJavaインタプリタに直接渡されます。このオプションには、空白を含めることはできません。このオプションは、実行環境またはメモリー使用を調整する場合に便利です。指定できるインタプリタ・オプションを一覧表示するには、コマンド行で\fBjava \-h\fRまたは\fBjava \-X\fRと入力してください。 +.PP +次のオプションは、キーストアに対する操作を行うすべてのコマンドで指定できます。 +.PP +\-storetype \fIstoretype\fR +.RS 4 +この修飾子は、インスタンスを生成するキーストアのタイプを指定します。 +.RE +.PP +\-keystore \fIkeystore\fR +.RS 4 +キーストアの場所を指定します。 +.sp +特定の\fBkeytool\fRコマンドを実行する際に、JKS +\fBstoretype\fRが使用され、かつキーストア・ファイルがまだ存在していなかった場合、新しいキーストア・ファイルが作成されます。たとえば、\fBkeytool \-genkeypair\fRの呼出し時に\fB\-keystore\fRオプションが指定されなかった場合、\fB\&.keystore\fRという名前のデフォルト・キーストア・ファイルがユーザーのホーム・ディレクトリ内にまだ存在していなければ、そこに作成されます。同様に、\fB\-keystore ks_file\fRというオプションが指定されてもそのks_fileが存在しなかった場合、そのファイルが作成されます。JKS +\fBstoretype\fRの詳細は、\fIの\fRKeyStoreの実装キーストアの別名に関する項を参照してください。 +.sp +\fB\-keystore\fRオプションからの入力ストリームは、\fBKeyStore\&.load\fRメソッドに渡されます。URLとして\fBNONE\fRが指定されている場合は、nullのストリームが\fBKeyStore\&.load\fRメソッドに渡されます。\fBNONE\fRは、KeyStoreがファイルベースではない場合に指定してください。たとえば、ハードウェア・トークン・デバイス上に存在している場合などです。 +.RE +.PP +\-storepass[:\fIenv\fR| :\fIfile\fR] argument +.RS 4 +キーストアの整合性を保護するために使用するパスワードを指定します。 +.sp +修飾子\fBenv\fRまたは\fBfile\fRを指定しない場合、パスワードの値は\fBargument\fRになります。この値は、6文字以上にする必要があります。それ以外の場合、パスワードは次のようにして取得されます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBenv\fR: +\fBargument\fRという名前の環境変数からパスワードを取得します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBfile\fR: argumentという名前のファイルからパスワードを取得します。 +.RE +.sp +\fB注意:\fR +\fB\-keypass\fR、\fB\-srckeypass\fR、\-\fBdestkeypass\fR、\fB\-srcstorepass\fR、\fB\-deststorepass\fRなどのパスワードを必要とするその他のオプションはすべて、\fIenv\fRおよび\fIfile\fR修飾子を受け付けます。パスワード・オプションと修飾子は、必ずコロン(:)で区切ってください。 +.sp +パスワードは、キーストアの内容にアクセスするすべてのコマンドで使用されます。この種のコマンドを実行するときに、コマンド行で\fB\-storepass\fRオプションを指定しなかった場合は、パスワードの入力を求められます。 +.sp +キーストアから情報を取得する場合、パスワードは省略可能です。パスワードが指定されていない場合は、取得した情報の整合性を検証できず、警告が表示されます。 +.RE +.PP +\-providerName \fIprovider_name\fR +.RS 4 +セキュリティ・プロパティ・ファイル内に含まれる暗号化サービス・プロバイダ名を特定するために使用されます。 +.RE +.PP +\-providerClass \fIprovider_class_name\fR +.RS 4 +暗号化サービス・プロバイダがセキュリティ・プロパティ・ファイルに指定されていないときは、そのマスター・クラス・ファイルの名前を指定するときに使用されます。 +.RE +.PP +\-providerArg \fIprovider_arg\fR +.RS 4 +\fB\-providerClass\fRオプションとともに使用され、\fBprovider_class_name\fRのコンストラクタのオプションの文字列入力引数を表します。 +.RE +.PP +\-protected +.RS 4 +\fBtrue\fRまたは\fBfalse\fRのいずれか。パスワードを専用PINリーダーなどの保護された認証パス経由で指定する必要がある場合は、この値を\fBtrue\fRに指定する必要があります。\fB\-importkeystore\fRコマンドには2つのキーストアが関連しているため、ソース・キーストアと宛先キーストアにそれぞれ次の2つのオプション、\fB\-srcprotected\fRと\-\fBdestprotected\fRが用意されています。 +.RE +.PP +\-ext \fI{name{:critical} {=value}}\fR +.RS 4 +X\&.509証明書エクステンションを示します。このオプションを\fB\-genkeypair\fRおよび\fB\-gencert\fRで使用して、生成される証明書または\fB\-certreq\fRにエクステンションを埋め込み、証明書リクエストでリクエストされるエクステンションを示すことができます。このオプションは複数回指定できます。\fBname\fR引数には、サポートされているエクステンション名(名前付きエクステンションを参照)または任意のOID番号を指定できます。指定されている場合、\fBvalue\fR引数はエクステンションの引数を指します。\fIvalue\fRを省略した場合、エクステンションのデフォルト値またはエクステンションが引数を必要としないことを示します。\fB:critical\fR修飾子が指定された場合、エクステンションの\fBisCritical\fR属性は\fBtrue\fRで、指定されない場合は\fBfalse\fRです。\fB:critical\fRのかわりに\fB:c\fRを使用できます。 +.RE +.SH "名前付きエクステンション" +.PP +\fBkeytool\fRコマンドは、次の名前のエクステンションをサポートしています。名前の大/小文字は区別されません。 +.PP +BCまたはBasicContraints +.RS 4 +\fB値\fR: 完全な形式は、\fBca:{true|false}[,pathlen:<len>]\fRまたは\fB<len>\fR(\fBca:true,pathlen:<len>\fRの短縮形)です。<\fBlen\fR>を省略すると、\fBca:true\fRの意味になります。 +.RE +.PP +KUまたはKeyUsage +.RS 4 +\fB値\fR: +\fBusage\fR(\fBusage\fR)*、\fIusage\fRには\fBdigitalSignature\fR、\fBnonRepudiation\fR +(contentCommitment)、\fBkeyEncipherment\fR、\fBdataEncipherment\fR、\fBkeyAgreement\fR、\fBkeyCertSign\fR、\fBcRLSign\fR、\fBencipherOnly\fR、\fBdecipherOnly\fRのいずれかを指定できます。\fIusage\fR引数は、不明確にならないかぎり、最初の数文字(\fBdigitalSignature\fRの場合は\fBdig\fR)またはキャメルケース・スタイル(\fBdigitalSignature\fRの場合は\fBdS\fR、\fBcRLSign\fRの場合は\fBcRLS\fR)で省略表記できます。\fBusage\fR値は、大文字と小文字が区別されます。 +.RE +.PP +EKUまたはExtendedKeyUsage +.RS 4 +\fB値\fR: +\fBusage\fR(\fBusage\fR)*、\fIusage\fRには\fBanyExtendedKeyUsage\fR、\fBserverAuth\fR、\fBclientAuth\fR、\fBcodeSigning\fR、\fBemailProtection\fR、\fBtimeStamping\fR、\fBOCSPSigning\fRまたは任意の\fIOID文字列\fRのいずれかを指定できます。\fIusage\fR引数は、不明確にならないかぎり、最初の数文字またはキャメルケース・スタイルで省略表記できます。\fBusage\fR値は、大文字と小文字が区別されます。 +.RE +.PP +SANまたはSubjectAlternativeName +.RS 4 +\fB値\fR: +\fBtype\fR:\fBvalue\fR(t\fBype:value\fR)*、\fBtype\fRには\fBEMAIL\fR、\fBURI\fR、\fBDNS\fR、\fBIP\fRまたは\fBOID\fRを指定できます。\fBvalue\fR引数は、\fBtype\fRの文字列形式の値です。 +.RE +.PP +IANまたはIssuerAlternativeName +.RS 4 +\fB値\fR: +\fBSubjectAlternativeName\fRと同じです。 +.RE +.PP +SIAまたはSubjectInfoAccess +.RS 4 +\fB値\fR: +\fBmethod\fR:\fBlocation\-type\fR:\fBlocation\-value\fR +(\fBmethod:location\-type\fR:\fBlocation\-value\fR)*、\fBmethod\fRには\fBtimeStamping\fR、\fBcaRepository\fRまたは任意のOIDを指定できます。\fBlocation\-type\fRおよび\fBlocation\-value\fR引数には、\fBSubjectAlternativeName\fRエクステンションでサポートされる任意の\fBtype\fR:\fBvalue\fRを指定できます。 +.RE +.PP +AIAまたはAuthorityInfoAccess +.RS 4 +\fB値\fR: +\fBSubjectInfoAccess\fRと同じです。\fBmethod\fR引数には、\fBocsp\fR、\fBcaIssuers\fRまたは任意のOIDを指定できます。 +.RE +.PP +\fBname\fRがOIDの場合、OCTET STRINGタイプと長さのバイトを除外したエクステンションについては、値は\fBextnValue\fRの16進ダンプのDERエンコーディングです。HEX文字列では、標準の16進数(0\-9、a\-f、A\-F)以外の文字は無視されます。したがって、01:02:03:04と01020304の両方とも同一の値として受け付けられます。値がない場合、エクステンションの値フィールドは空になります。 +.PP +\fB\-gencert\fRでのみ使用する\fBhonored\fRという特別な名前は、証明書リクエストに含まれるエクステンションを優先する方法を示します。この名前の値は、\fBall\fR(リクエストされるすべてのエクステンションが優先される)、\fBname{:[critical|non\-critical]}\fR(名前付きのエクステンションが優先されるが、別の\fBisCritical\fR属性を使用する)、および\fB\-name\fR(\fBall\fRとともに使用し、例外を示す)のカンマ区切りリストです。デフォルトでは、リクエストされるエクステンションは優先されません。 +.PP +\fB\-ext honored\fRオプションに加え、別の名前の、またはOID +\fB\-ext\fRのオプションを指定した場合は、このエクステンションが、すでに優先されているエクステンションに追加されます。ただし、この名前(またはOID)を優先される値でも使用した場合は、その値と重要性がリクエストに含まれるものをオーバーライドします。 +.PP +\fBsubjectKeyIdentifier\fRエクステンションは常に作成されます。自己署名でない証明書の場合は、\fBauthorityKeyIdentifier\fRが作成されます。 +.PP +\fB注意:\fR +ユーザーは、エクステンション(および証明書の他のフィールド)の組合せによっては、インターネットの標準に準拠しない場合があることに注意してください。証明書の準拠に関する警告を参照してください。 +.SH "コマンド" +.PP +\-gencert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-rfc} {\-infile \fR\fB\fIinfile\fR\fR\fB} {\-outfile \fR\fB\fIoutfile\fR\fR\fB} {\-alias \fR\fB\fIalias\fR\fR\fB} {\-sigalg \fR\fB\fIsigalg\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-dname \fR\fB\fIdname\fR\fR\fB} {\-startdate \fR\fB\fIstartdate\fR\fR\fB {\-ext \fR\fB\fIext\fR\fR\fB}* {\-validity \fR\fB\fIvalDays\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-providername \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +証明書リクエスト・ファイル(\fBkeytool\fR +\fB\-certreq\fRコマンドで作成可能)に対するレスポンスとして証明書を生成します。このコマンドは、\fIinfile\fRから(省略した場合は、標準入力から)リクエストを読み込み、別名の秘密鍵を使用してそのリクエストに署名して、X\&.509証明書を\fIoutfile\fRに(省略した場合は、標準出力に)出力します。\fB\-rfc\fRを指定した場合、出力形式はBASE64符号化のPEMになります。それ以外の場合は、バイナリDERが作成されます。 +.sp +\fBsigalg\fR値には、証明書に署名を付けるときに使用するアルゴリズムを指定します。\fBstartdate\fR引数は、証明書の有効開始日時です。\fBvalDays\fR引数は、証明書の有効日数を示します。 +.sp +\fBdname\fRを指定すると、生成される証明書の主体として使用されます。それ以外の場合は、証明書リクエストからの名前が使用されます。 +.sp +\fBext\fR値は、証明書に埋め込まれるX\&.509エクステンションを示します。\fB\-ext\fRの構文については、一般オプションを参照してください。 +.sp +\fB\-gencert\fRオプションを使用すると、証明書チェーンを作成できます。次の例では、\fBe1\fRという証明書を作成します。この証明書の証明書チェーンには、3つの証明書が含まれています。 +.sp +次のコマンドは、\fBca\fR、\fBca1\fR、\fBca2\fRおよび\fBe1\fRの4つの鍵ペアを作成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-alias ca \-dname CN=CA \-genkeypair\fR +\fBkeytool \-alias ca1 \-dname CN=CA \-genkeypair\fR +\fBkeytool \-alias ca2 \-dname CN=CA \-genkeypair\fR +\fBkeytool \-alias e1 \-dname CN=E1 \-genkeypair\fR + +.fi +.if n \{\ +.RE +.\} +次の2つのコマンドは、署名付き証明書のチェーンを作成します。\fBca\fRは\fBca1\fRに署名し、\fBca1\fRは\fBca2\fRに署名します。すべて自己発行です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-alias ca1 \-certreq |\fR +\fB keytool \-alias ca \-gencert \-ext san=dns:ca1 |\fR +\fB keytool \-alias ca1 \-importcert\fR + +\fBkeytool \-alias ca2 \-certreq |\fR +\fB $KT \-alias ca1 \-gencert \-ext san=dns:ca2 |\fR +\fB $KT \-alias ca2 \-importcert\fR + +.fi +.if n \{\ +.RE +.\} +次のコマンドは、証明書\fBe1\fRを作成してファイル\fBe1\&.cert\fRに格納します。この証明書は\fBca2\fRによって署名されます。その結果、\fBe1\fRの証明書チェーンには\fBca\fR、\fBca1\fRおよび\fBca2\fRが含まれることになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-alias e1 \-certreq | keytool \-alias ca2 \-gencert > e1\&.cert\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-genkeypair +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-keyalg \fR\fB\fIkeyalg\fR\fR\fB} {\-keysize \fR\fB\fIkeysize\fR\fR\fB} {\-sigalg \fR\fB\fIsigalg\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-dname \fR\fB\fIdname\fR\fR\fB] [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-startdate \fR\fB\fIvalue\fR\fR\fB} {\-ext \fR\fB\fIext\fR\fR\fB}*\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-validity \fR\fB\fIvalDays\fR\fR\fB} {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +鍵のペア(公開鍵および関連する秘密鍵)を生成します。公開鍵はX\&.509 v3自己署名証明書でラップされます。証明書は、単一の要素を持つ証明書チェーンとして格納されます。この証明書チェーンと秘密鍵は、aliasで特定される新しいキーストア・エントリに格納されます。 +.sp +\fBkeyalg\fR値は鍵ペアの生成に使用するアルゴリズムを、\fBkeysize\fR値は生成する各鍵のサイズを、それぞれ指定します。\fBsigalg\fR値は、自己署名証明書に署名を付けるために使用するアルゴリズムを指定します。このアルゴリズムは\fBkeyalg\fR値と互換性がある必要があります。 +.sp +\fBdname\fR値には、\fBalias\fR値に関連付け、自己署名証明書のissuerフィールドとsubjectフィールドとして使用するX\&.500識別名を指定します。コマンド行で識別名を指定しなかった場合は、識別名の入力を求められます。 +.sp +\fBkeypass\fR値には、生成される鍵のペアのうち、秘密鍵を保護するのに使用するパスワードを指定します。パスワードを指定しなかった場合は、パスワードの入力を求められます。このとき、[Return]キーを押すと、キーストアのパスワードと同じパスワードが鍵のパスワードに設定されます。\fBkeypass\fR値は、6文字以上にする必要があります。 +.sp +\fBstartdate\fR値には、証明書の発行時刻を指定します。これは、X\&.509証明書の「Validity」フィールドの「Not Before」値とも呼ばれます。 +.sp +オプションの値は、次の2つの形式のいずれかで設定できます。 +.sp +\fB([+\-]nnn[ymdHMS])+\fR +.sp +\fB[yyyy/mm/dd] [HH:MM:SS]\fR +.sp +最初の形式では、発行時刻は、指定される値の分、現在の時刻から移ります。指定される値は、一連の下位の値を連結したものになります。下位の各値で、プラス記号(「+」)は時間が進むことを、マイナス記号(「\-」)は時間が戻ることを意味しています。移る時間は\fBnnn\fRで、単位は年、月、日、時間、分または秒です(それぞれ、1文字の\fBy\fR、\fBm\fR、\fBd\fR、\fBH\fR、\fBM\fRまたは\fBS\fR」で示されています)。下位の各値で\fBjava\&.util\&.GregorianCalendar\&.add(int field, int amount)\fRメソッドを使用することで、発行時刻の追加の値が左から右へ計算されます。たとえば、指定すると、発行時刻は次のようになります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCalendar c = new GregorianCalendar();\fR +\fBc\&.add(Calendar\&.YEAR, \-1);\fR +\fBc\&.add(Calendar\&.MONTH, 1);\fR +\fBc\&.add(Calendar\&.DATE, \-1);\fR +\fBreturn c\&.getTime()\fR + +.fi +.if n \{\ +.RE +.\} +2番目の形式では、ユーザーは、年/月/日と時間:分:秒の2つの部分で厳密な開始時刻を設定します(地元の時間帯を使用)。ユーザーは、1つの部分のみを指定できます。これは、もう1つの部分は現在の日付(または時刻)と同じになるということです。ユーザーは、形式の定義に示されているように、桁数を厳密に指定する必要があります(短い場合は0で埋めます)。日付と時刻の両方が指定された状態で、2つの部分の間に空白文字が1つ(1つのみ)あります。時間は常に24時間形式で指定してください。 +.sp +オプションを指定しないと、開始日付は現在の時刻になります。オプションは、最大で1回指定できます。 +.sp +\fBvalDays\fRの値には、証明書の有効日数を指定します(\fB\-startdate\fRで指定された日付、または\fB\-startdate\fRが指定されていない場合は現在の日付から始まります)。 +.sp +このコマンドは、以前のリリースでは\fB\-genkey\fRという名前でした。このリリースでは、引き続き古い名前がサポートされています。今後は、新しい名前\fB\-genkeypair\fRが優先されます。 +.RE +.PP +\-genseckey +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-keyalg \fR\fB\fIkeyalg\fR\fR\fB} {\-keysize \fR\fB\fIkeysize\fR\fR\fB} [\-keypass \fR\fB\fIkeypass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +秘密鍵を生成し、それを新しい\fBKeyStore\&.SecretKeyEntry\fR(\fBalias\fRで特定される)内に格納します。 +.sp +\fBkeyalg\fR値は鍵ペアの生成に使用するアルゴリズムを、\fBkeysize\fR値は生成する各鍵のサイズを、それぞれ指定します。\fBkeypass\fR値は、秘密鍵を保護するパスワードです。パスワードを指定しなかった場合は、パスワードの入力を求められます。このとき、[Return]キーを押すと、\fBkeystore\fRのパスワードと同じパスワードが鍵のパスワードに設定されます。\fBkeypass\fR値は、6文字以上にする必要があります。 +.RE +.PP +\-importcert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-file \fR\fB\fIcert_file\fR\fR\fB} [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-noprompt} {\-trustcacerts}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +ファイル\fBcert_file\fRから証明書または証明書チェーン(証明書チェーンの場合は、PKCS#7形式の応答または一連のX\&.509証明書で提供されるもの)を読み込み、\fBalias\fRによって特定される\fBkeystore\fRエントリに格納します。ファイルが指定されていない場合は、\fBstdin\fRから証明書または証明書チェーンを読み込みます。 +.sp +\fBkeytool\fRコマンドでは、X\&.509 v1、v2、v3の証明書、およびPKCS#7形式の証明書から構成されているPKCS#7形式の証明書チェーンをインポートできます。インポートするデータは、バイナリ符号化方式、または出力可能符号化方式(Base64符号化とも呼ばれる)のどちらかで提供する必要があります。出力可能符号化方式は、インターネットRFC 1421証明書符号化規格で定義されています。この符号化方式の場合、証明書は\fB\-\fR\fB\-\-\-\-BEGIN\fRで始まる文字列で開始され、\fB\-\-\-\-\-END\fRで始まる文字列で終了する必要があります。 +.sp +証明書は、信頼できる証明書のリストに追加するため、および認証局(CA)に証明書署名リクエストを送信した結果としてCAから受信した証明書応答をインポートするため(\fBの\fR\-certreqコマンドオプションを参照)という2つの理由でインポートします。 +.sp +どちらのタイプのインポートを行うかは、\fB\-alias\fRオプションの値によって指定します。別名がキー・エントリをポイントしない場合、\fBkeytool\fRコマンドはユーザーが信頼できる証明書エントリを追加しようとしているものとみなします。この場合、別名がキーストア内に存在していないことが必要です。別名がすでに存在している場合、その別名の信頼できる証明書がすでに存在することになるので、\fBkeytool\fRコマンドはエラーを出力し、証明書のインポートを行いません。別名がキー・エントリをポイントする場合、\fBkeytool\fRコマンドはユーザーが証明書応答をインポートしようとしているものとみなします。 +.RE +.PP +\-importpassword +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +パスフレーズをインポートし、\fBalias\fRで識別される新規\fBKeyStore\&.SecretKeyEntry\fRに格納します。パスフレーズは、標準入力ストリームを介して提供できます。または、ユーザーにそのプロンプトが表示されます。\fBkeypass\fRは、インポートされるパスフレーズの保護に使用されるパスワードです。パスワードを指定しなかった場合は、パスワードの入力を求められます。このとき、[Return]キーを押すと、\fBkeystore\fRのパスワードと同じパスワードが鍵のパスワードに設定されます。\fBkeypass\fRは、6文字以上にする必要があります。 +.RE +.PP +\-importkeystore +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-srcstoretype \fR\fB\fIsrcstoretype\fR\fR\fB} {\-deststoretype \fR\fB\fIdeststoretype\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-srcstorepass \fR\fB\fIsrcstorepass\fR\fR\fB] [\-deststorepass \fR\fB\fIdeststorepass\fR\fR\fB] {\-srcprotected}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-destprotected} \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-srcalias \fR\fB\fIsrcalias\fR\fR\fB {\-destalias \fR\fB\fIdestalias\fR\fR\fB} [\-srckeypass \fR\fB\fIsrckeypass\fR\fR\fB]} \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-destkeypass \fR\fB\fIdestkeypass\fR\fR\fB] {\-noprompt}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-srcProviderName \fR\fB\fIsrc_provider_name\fR\fR\fB} {\-destProviderName \fR\fB\fIdest_provider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +ソース・キーストアからターゲット・キーストアへ、単一のエントリまたはすべてのエントリをインポートします。 +.sp +\fB\-srcalias\fRオプションが指定された場合、このコマンドは、その別名で特定される単一のエントリをターゲット・キーストアにインポートします。\fBdestalias\fR経由でターゲット別名が指定されなかった場合、\fBsrcalias\fRがターゲット別名として使用されます。ソースのエントリがパスワードで保護されていた場合、\fBsrckeypass\fRを使用してそのエントリが回復されます。\fIsrckeypass\fRが指定されなかった場合、\fBkeytool\fRコマンドは\fBsrcstorepass\fRを使用してそのエントリを回復しようとします。\fBsrcstorepass\fRが指定されなかったか正しくなかった場合、ユーザーはパスワードの入力を求められます。ターゲットのエントリは\fBdestkeypass\fRによって保護されます。\fBdestkeypass\fRが指定されなかった場合、ターゲット・エントリはソース・エントリのパスワードによって保護されます。たとえば、ほとんどのサード・パーティ・ツールでは、PKCS #12キーストアで\fBstorepass\fRと\fBkeypass\fRが同じである必要があります。これらのツールのPKCS #12キーストアを作成する場合は、常に\fB\-destkeypass\fRと\fB\-deststorepass\fRが同じになるように指定します。 +.sp +\fB\-srcalias\fRオプションが指定されなかった場合、ソース・キーストア内のすべてのエントリがターゲット・キーストア内にインポートされます。各ターゲット・エントリは対応するソース・エントリの別名の下に格納されます。ソースのエントリがパスワードで保護されていた場合、\fBsrcstorepass\fRを使用してそのエントリが回復されます。\fBsrcstorepass\fRが指定されなかったか正しくなかった場合、ユーザーはパスワードの入力を求められます。ソース・キーストア内のあるエントリ・タイプがターゲット・キーストアでサポートされていない場合や、あるエントリをターゲット・キーストアに格納する際にエラーが発生した場合、ユーザーはそのエントリをスキップして処理を続行するか、または中止するかの選択を求められます。ターゲット・エントリはソース・エントリのパスワードによって保護されます。 +.sp +ターゲット別名がターゲット・キーストア内にすでに存在していた場合、ユーザーは、そのエントリを上書きするか、あるいは異なる別名の下で新しいエントリを作成するかの選択を求められます。 +.sp + +\fB\-noprompt\fRオプションを指定した場合、ユーザーは新しいターゲット別名の入力を求められません。既存のエントリがそのターゲット別名で上書きされます。インポートできないエントリはスキップされ、警告が出力されます。 +.RE +.PP +\-printcertreq +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-file \fR\fB\fIfile\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +PKCS#10形式の証明書リクエストの内容を出力します。このリクエストは、\fBkeytool\fR +\fB\-certreq\fRコマンドで生成できます。このコマンドは、ファイルからリクエストを読み取ります。ファイルが存在しない場合、リクエストは標準入力から読み取られます。 +.RE +.PP +\-certreq +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-dname \fR\fB\fIdname\fR\fR\fB} {\-sigalg \fR\fB\fIsigalg\fR\fR\fB} {\-file \fR\fB\fIcertreq_file\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +PKCS#10形式を使用して証明書署名リクエスト(CSR)を生成します。 +.sp +CSRは、証明書発行局(CA)に送信することを目的としたものです。CAは、証明書要求者を(通常はオフラインで)認証し、証明書または証明書チェーンを送り返します。この証明書または証明書チェーンは、キーストア内の既存の証明書チェーン(最初は1つの自己署名証明書から構成される)に置き換えて使用します。 +.sp +aliasに関連付けられた秘密鍵は、PKCS#10証明書リクエストを作成するのに使用されます。秘密鍵にアクセスするには、正しいパスワードを指定する必要があります。コマンド行で\fBkeypass\fRを指定しておらず、秘密鍵のパスワードがキーストアのパスワードと異なる場合は、秘密鍵のパスワードの入力を求められます。\fBdname\fRが指定されている場合は、それがCSRで主体として使用されます。それ以外の場合は、別名に関連付けられたX\&.500識別名が使用されます。 +.sp +\fBsigalg\fR値には、CSRに署名を付けるときに使用するアルゴリズムを指定します。 +.sp +CSRは、ファイルcertreq_fileに格納されます。ファイルが指定されていない場合は、\fBstdout\fRにCSRが出力されます。 +.sp +CAからのレスポンスをインポートするには、\fBimportcert\fRコマンドを使用します。 +.RE +.PP +\-exportcert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-file \fR\fB\fIcert_file\fR\fR\fB} {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-rfc} {\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fIalias\fRに関連付けられた証明書をキーストアから読み込み、ファイルcert_fileに格納します。ファイルが指定されていない場合は、\fBstdout\fRに証明書が出力されます。 +.sp +デフォルトでは、証明書はバイナリ符号化で出力されます。\fB\-rfc\fRオプションが指定されている場合、出力可能符号化方式の出力はインターネットRFC 1421証明書符号化規格で定義されます。 +.sp +\fBalias\fRが、信頼できる証明書を参照している場合は、該当する証明書が出力されます。それ以外の場合、\fBalias\fRは、関連付けられた証明書チェーンを持つ鍵エントリを参照します。この場合は、チェーン内の最初の証明書が返されます。この証明書は、\fBalias\fRによって表されるエンティティの公開鍵を認証する証明書です。 +.sp +このコマンドは、以前のリリースでは\fB\-export\fRという名前でした。このリリースでは、引き続き古い名前がサポートされています。今後は、新しい名前\fB\-exportcert\fRが優先されます。 +.RE +.PP +\-list +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v | \-rfc} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fBalias\fRで特定されるキーストア・エントリの内容を\fBstdout\fRに出力します。\fBalias\fRが指定されていない場合は、キーストア全体の内容が表示されます。 +.sp +このコマンドは、デフォルトでは証明書のSHA1フィンガープリントを表示します。 +\fB\-v\fRオプションが指定されている場合は、所有者、発行者、シリアル番号、拡張機能などの付加的な情報とともに、人間が読むことのできる形式で証明書が表示されます。\fB\-rfc\fRオプションが指定されている場合は、出力可能符号化方式で証明書の内容が出力されます。出力可能符号化方式は、インターネットRFC 1421証明書符号化規格で定義されています。 +.sp +\fB\-v\fRオプションと\fB\-rfc\fRオプションを同時に指定することはできません。 +.RE +.PP +\-printcert +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-file \fR\fB\fIcert_file\fR\fR\fB | \-sslserver \fR\fB\fIhost\fR\fR\fB[:\fR\fB\fIport\fR\fR\fB]} {\-jarfile \fR\fB\fIJAR_file\fR\fR\fB {\-rfc} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +ファイルcert_file、host:portにあるSSLサーバー、または署名付きJARファイル\fBJAR_file\fR(\fB\-jarfile\fRオプションを指定)から証明書を読み込み、人間が読むことのできる形式で証明書の内容を表示します。ポートが指定されていない場合は、標準のHTTPSポート443が想定されます。\fB\-sslserver\fRおよび\-fileオプションを同時に指定することはできません。それ以外の場合、エラーが報告されます。オプションが指定されていない場合は、\fBstdin\fRから証明書を読み込みます。 +.sp +\fB\-rfc\fRが指定されている場合、\fBkeytool\fRコマンドは、インターネットRFC 1421証明書符号化標準で定義されているように、PEMモードで証明書を出力します。インターネットRFC 1421証明書符号化規格を参照してください。 +.sp +ファイルまたは\fBstdin\fRから証明書を読み込む場合、その証明書は、インターネットRFC 1421証明書符号化標準で定義されているように、バイナリ符号化方式または出力可能符号化方式で表示できます。 +.sp +SSLサーバーがファイアウォールの背後にある場合は、\fB\-J\-Dhttps\&.proxyHost=proxyhost\fRおよび\fB\-J\-Dhttps\&.proxyPort=proxyport\fRオプションをコマンド行で指定して、プロキシ・トンネリングを使用できます。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide\&.htmlの +「Java Secure Socket Extension (JSSE) Reference Guide」を参照してください +.sp +\fB注意:\fR +このオプションはキーストアとは関係なく使用できます。 +.RE +.PP +\-printcrl +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-file \fR\fB\fIcrl_\fR\fR\fB {\-v}\fR +.fi +.if n \{\ +.RE +.\} +ファイル\fBcrl_\fRから証明書失効リスト(CRL)を読み込みます。CRLは、発行したCAによって失効されたデジタル証明書のリストです。CAは、\fBcrl_\fRを生成します。 +.sp +\fB注意:\fR +このオプションはキーストアとは関係なく使用できます。 +.RE +.PP +\-storepasswd +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-new \fR\fB\fInew_storepass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +キーストアの内容の整合性を保護するために使用するパスワードを変更します。\fBnew_storepass\fRには、新しいパスワードを指定します。new_storepassは、6文字以上である必要があります。 +.RE +.PP +\-keypasswd +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} [\-keypass \fR\fB\fIold_keypass\fR\fR\fB] [\-new \fR\fB\fInew_keypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fBalias\fRによって特定される非公開/秘密鍵を保護するためのパスワードを、\fBold_keypass\fRから\fBnew_keypass\fRに変更します。new_keypassは、6文字以上である必要があります。 +.sp +コマンド行で\fB\-keypass\fRオプションを指定しておらず、鍵のパスワードがキーストアのパスワードと異なる場合は、鍵のパスワードの入力を求められます。 +.sp +コマンド行で\fB\-new\fRオプションを指定しなかった場合は、新しいパスワードの入力を求められます。 +.RE +.PP +\-delete +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[\-alias \fR\fB\fIalias\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB} {\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerName \fR\fB\fIprovider_name\fR\fR\fB} \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-v} {\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +\fBalias\fRによって特定されるエントリをキーストアから削除します。コマンド行で別名を指定しなかった場合は、別名の入力を求められます。 +.RE +.PP +\-changealias +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-alias \fR\fB\fIalias\fR\fR\fB} [\-destalias \fR\fB\fIdestalias\fR\fR\fB] [\-keypass \fR\fB\fIkeypass\fR\fR\fB] {\-storetype \fR\fB\fIstoretype\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-keystore \fR\fB\fIkeystore\fR\fR\fB} [\-storepass \fR\fB\fIstorepass\fR\fR\fB] {\-providerName \fR\fB\fIprovider_name\fR\fR\fB}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-providerClass \fR\fB\fIprovider_class_name\fR\fR\fB {\-providerArg \fR\fB\fIprovider_arg\fR\fR\fB}} {\-v}\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB{\-protected} {\-Jjavaoption}\fR +.fi +.if n \{\ +.RE +.\} +指定された\fBalias\fRから新しい別名\fBdestalias\fRへ、既存のキーストア・エントリを移動します。ターゲット別名を指定しなかった場合、ターゲット別名の入力を求められます。元のエントリがエントリ・パスワードで保護されていた場合、\fB\-keypass\fRオプションでそのパスワードを指定できます。鍵パスワードが指定されなかった場合、\fBstorepass\fR(指定された場合)がまず試みられます。その試みが失敗すると、ユーザーはパスワードの入力を求められます。 +.RE +.PP +\-help +.RS 4 +基本的なコマンドとそのオプションの一覧を表示します。 +.sp +特定のコマンドの詳細を参照するには、次のように入力してください: +\fBkeytool \-command_name \-help\fR。\fBcommand_name\fRはコマンドの名前です。 +.RE +.SH "例" +.PP +この例では、公開/秘密鍵のペアおよび信頼できるエンティティからの証明書を管理するためのキーストアを作成する手順を示します。 +.SS "鍵のペアの生成" +.PP +まず、キーストアを作成して鍵のペアを生成します。単一行に入力する、次のようなコマンドを使用できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-dname "cn=Mark Jones, ou=Java, o=Oracle, c=US"\fR +\fB \-alias business \-keypass <new password for private key>\fR +\fB \-keystore /working/mykeystore\fR +\fB \-storepass <new password for keystore> \-validity 180\fR + +.fi +.if n \{\ +.RE +.\} +.PP +コマンドは、workingディレクトリに\fBmykeystore\fRという名前のキーストアを作成し(キーストアはまだ存在していないと仮定)、作成したキーストアに、\fB<new password for keystore>\fRで指定したパスワードを割り当てます。生成する公開鍵と秘密鍵のペアに対応するエンティティの「識別名」は、通称がMark Jones、組織単位がJava、組織がOracle、2文字の国番号がUSです。公開鍵と秘密鍵のサイズはどちらも1024ビットで、鍵の作成にはデフォルトのDSA鍵生成アルゴリズムを使用します。 +.PP +このコマンドは、デフォルトのSHA1withDSA署名アルゴリズムを使用して、公開鍵と識別名情報を含む自己署名証明書を作成します。証明書の有効期間は180日です。証明書は、別名\fBbusiness\fRで特定されるキーストア・エントリ内の秘密鍵に関連付けられます。秘密鍵には、\fB<new password for private key>\fRで指定したパスワードが割り当てられます。 +.PP +オプションのデフォルト値を使用する場合、コマンドは大幅に短くなります。この場合、オプションは不要です。デフォルト値を持つオプションでは、オプションを指定しなければデフォルト値が使用されます。必須値の入力を求められます。使用可能な値は次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この場合は、\fBmykey\fRという別名でキーストア・エントリが作成され、新しく生成された鍵のペア、および90日間有効な証明書がこのエントリに格納されます。このエントリは、ホーム・ディレクトリ内の\fB\&.keystore\fRという名前のキーストアに置かれます。キーストアは、まだ存在していない場合に作成されます。識別名情報、キーストアのパスワードおよび秘密鍵のパスワードの入力を求められます。 +.PP +以降では、オプションを指定しないで\fB\-genkeypair\fRコマンドを実行したものとして例を示します。情報の入力を求められた場合は、最初に示した\fB\-genkeypair\fRコマンドの値を入力したものとします。たとえば識別名には\fBcn=Mark Jones\fR、\fBou=Java\fR、\fBo=Oracle\fR、\fBc=US\fRと指定します。 +.SS "CAからの署名付き証明書のリクエスト" +.PP +自己署名証明書を作成する鍵のペアの生成。証明書に証明書発行局(CA)の署名が付いていれば、他のユーザーから証明書が信頼される可能性も高くなります。CAの署名を取得するには、まず、証明書署名リクエスト(CSR)を生成します。たとえば、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-certreq \-file MarkJ\&.csr\fR + +.fi +.if n \{\ +.RE +.\} +.PP +CSR(デフォルト別名\fBmykey\fRによって特定されるエンティティのCSR)が作成され、MarkJ\&.csrという名前のファイルに置かれます。このファイルをCA (VeriSignなど)に提出します。CAは要求者を(通常はオフラインで)認証し、要求者の公開鍵を認証した署名付きの証明書を送り返します。場合によっては、CAが証明書のチェーンを返すこともあります。証明書のチェーンでは、各証明書がチェーン内のその前の署名者の公開鍵を認証します。 +.SS "CAからの証明書のインポート" +.PP +作成した自己署名証明書は、証明書チェーンで置き換える必要があります。証明書チェーンでは、各証明書が、「ルート」CAを起点とするチェーン内の次の証明書の署名者の公開鍵を認証します。 +.PP +CAからの証明書応答をインポートするには、キーストアか、\fBcacerts\fRキーストア・ファイル内に1つ以上の信頼できる証明書がある必要があります。コマンドの\fB\-importcert\fRを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明応答が証明書チェーンの場合は、チェーンの最上位証明書が必要です。CAの公開鍵を認証するルートCA証明書。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書応答が単一の証明書の場合は、発行CA(署名した)の証明書が必要です。その証明書が自己署名でない場合は、その署名者の証明書が必要であり、このようにして自己署名ルート証明書が必要になります。 +.RE +.PP +\fBcacerts\fRキーストア・ファイルは、いくつかのVeriSignルートCA証明書を含んだ状態で出荷されているので、VeriSignの証明書を、信頼できる証明書としてキーストア内にインポートする必要がない場合があります。ただし、他のCAに対して署名付き証明書をリクエストしていて、このCAの公開鍵を認証する証明書が、\fBcacerts\fRにまだ追加されていない場合は、該当するCAからの証明書を、「信頼できる証明書」としてインポートする必要があります。 +.PP +通常、CAからの証明書は、自己署名証明書、または他のCAによって署名された証明書です(後者の場合は、該当する他のCAの公開鍵を認証する証明書が必要)。ABC, Inc\&.,がCAで、ABCから自己署名証明書であるA\fBBCCA\&.cer\fRという名前のファイルを取得したとします(この証明書はCAの公開鍵を認証します)。信頼できる証明書として証明書をインポートするときは、証明書が有効であることを確認する必要があります。まず、証明書の内容を表示し\fBkeytool \-printcert\fRコマンドを使用するか、または\fB\-noprompt\fRオプションを指定しないで\fBkeytool \-importcert\fRコマンドを使用し、表示された証明書のフィンガープリントが、期待されるフィンガープリントと一致するかどうかを確認します。証明書を送信した人物に連絡し、この人物が提示した(または安全な公開鍵のリポジトリによって提示される)フィンガープリントと、上のコマンドで表示されたフィンガープリントとを比較します。フィンガープリントが一致すれば、送信途中で他の何者か(攻撃者など)による証明書のすり替えが行われていないことを確認できます。送信途中でこの種の攻撃が行われていた場合、チェックを行わずに証明書をインポートすると、攻撃者によって署名されたすべてのものを信頼することになります。 +.PP +証明書が有効であると信頼する場合は、次のコマンドでキーストアに追加できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importcert \-alias abc \-file ABCCA\&.cer\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ABCCA\&.cerファイルのデータを含む信頼できる証明書のエントリがキーストア内に作成され、該当するエントリに\fBabc\fRという別名が割り当てられます。 +.SS "CAからの証明書応答のインポート" +.PP +証明書署名リクエストの提出先のCAの公開鍵を認証する証明書をインポートした後は(または同種の証明書がすでにcacertsファイル内に存在している場合は)、証明応答をインポートし、自己署名証明書を証明書チェーンで置き換えることができます。このチェーンは、CAの応答がチェーンの場合に、リクエストに対するレスポンスとしてCAから送り返された証明書チェーンです。また、CAの応答が単一の証明書の場合は、この証明応答と、インポート先のキーストア内または\fBcacerts\fRキーストアファイル内にすでに存在する信頼できる証明書とを使用して構築した証明書チェーンです。 +.PP +たとえば、証明書署名リクエストをVeriSignに送信する場合、送り返された証明書の名前がVSMarkJ\&.cerだとすると、次のようにして応答をインポートできます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importcert \-trustcacerts \-file VSMarkJ\&.cer\fR + +.fi +.if n \{\ +.RE +.\} +.SS "公開鍵を認証する証明書のエクスポート" +.PP +\fBjarsigner\fRコマンドを使用してJava Archive (JAR)ファイルに署名する場合、このファイルを使用するクライアントは署名を認証する必要があります。クライアントが署名を認証する方法の1つに、まず自分の公開鍵の証明書を信頼できるエントリとしてクライアントのキーストアにインポートする方法があります。 +.PP +そのためには、証明書をエクスポートして、クライアントに提供します。例として、次のコマンドを使用して、MJ\&.cerという名前のファイルに証明書をコピーできます。このコマンドでは、エントリに別名\fBmykey\fRがあると仮定しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-exportcert \-alias mykey \-file MJ\&.cer\fR + +.fi +.if n \{\ +.RE +.\} +.PP +証明書と署名付きJARファイルを入手したクライアントは、\fBjarsigner\fRコマンドを使用して署名を認証できます。 +.SS "キーストアのインポート" +.PP +コマンド\fBimportkeystore\fRを使用すれば、あるキーストアの全体を別のキーストア内にインポートできます。これは、鍵や証明書といったソースキーストア内のすべてのエントリが、単一のコマンドを使用してターゲットキーストア内にインポートされることを意味します。このコマンドを使用すれば、異なるタイプのキーストア内に含まれるエントリをインポートすることができます。インポート時には、ターゲット・キーストア内の新しいエントリはすべて、元と同じ別名および(秘密鍵や秘密鍵の場合は)保護用パスワードを持ちます。ソースキーストア内の非公開/秘密鍵をリカバリできない場合、\fBkeytool\fRコマンドはユーザーにパスワードの入力を求めます。このコマンドは、別名の重複を検出すると、ユーザーに新しい別名の入力を求めます。ユーザーは、新しい別名を指定することも、単純に既存の別名の上書きを\fBkeytool\fRコマンドに許可することもできます。 +.PP +たとえば、通常のJKSタイプのキーストアkey\&.jks内のエントリをPKCS#11タイプのハードウェア・ベースのキーストア内にインポートするには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importkeystore\fR +\fB \-srckeystore key\&.jks \-destkeystore NONE\fR +\fB \-srcstoretype JKS \-deststoretype PKCS11\fR +\fB \-srcstorepass <src keystore password>\fR +\fB \-deststorepass <destination keystore pwd>\fR + +.fi +.if n \{\ +.RE +.\} +.PP +また、\fBimportkeystore\fRコマンドを使用すれば、あるソース・キーストア内の単一のエントリをターゲット・キーストアにインポートすることもできます。この場合は、前例のオプションに加えて、インポートする別名を指定する必要があります。\fB\-srcalias\fRオプションを指定する場合には、ターゲット別名もコマンドラインから指定できるほか、秘密/秘密鍵の保護用パスワードやターゲット保護用パスワードも指定できます。その方法を示すコマンドを次に示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-importkeystore\fR +\fB \-srckeystore key\&.jks \-destkeystore NONE\fR +\fB \-srcstoretype JKS \-deststoretype PKCS11\fR +\fB \-srcstorepass <src keystore password>\fR +\fB \-deststorepass <destination keystore pwd>\fR +\fB \-srcalias myprivatekey \-destalias myoldprivatekey\fR +\fB \-srckeypass <source entry password>\fR +\fB \-destkeypass <destination entry password>\fR +\fB \-noprompt\fR + +.fi +.if n \{\ +.RE +.\} +.SS "SSLサーバーの証明書の生成" +.PP +次に、3つのエンティティ、つまりルートCA(\fBroot\fR)、中間CA(\fBca\fR)およびSSLサーバー(\fBserver\fR)用の鍵ペアと証明書を生成する\fBkeytool\fRコマンドを示します。すべての証明書を同じキーストアに格納するようにしてください。これらの例では、RSAが推奨される鍵のアルゴリズムです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-keystore root\&.jks \-alias root \-ext bc:c\fR +\fBkeytool \-genkeypair \-keystore ca\&.jks \-alias ca \-ext bc:c\fR +\fBkeytool \-genkeypair \-keystore server\&.jks \-alias server\fR +\fB \fR +\fBkeytool \-keystore root\&.jks \-alias root \-exportcert \-rfc > root\&.pem\fR +\fB \fR +\fBkeytool \-storepass <storepass> \-keystore ca\&.jks \-certreq \-alias ca |\fR +\fB keytool \-storepass <storepass> \-keystore root\&.jks\fR +\fB \-gencert \-alias root \-ext BC=0 \-rfc > ca\&.pem\fR +\fBkeytool \-keystore ca\&.jks \-importcert \-alias ca \-file ca\&.pem\fR +\fB \fR +\fBkeytool \-storepass <storepass> \-keystore server\&.jks \-certreq \-alias server |\fR +\fB keytool \-storepass <storepass> \-keystore ca\&.jks \-gencert \-alias ca\fR +\fB \-ext ku:c=dig,kE \-rfc > server\&.pem\fR +\fBcat root\&.pem ca\&.pem server\&.pem |\fR +\fB keytool \-keystore server\&.jks \-importcert \-alias server\fR + +.fi +.if n \{\ +.RE +.\} +.SH "用語" +.PP +キーストア +.RS 4 +キーストアは、暗号化の鍵と証明書を格納するための機能です。 +.RE +.PP +キーストアのエントリ +.RS 4 +キーストアには異なるタイプのエントリを含めることができます。\fBkeytool\fRコマンドで最も適用範囲の広いエントリ・タイプは、次の2つです。 +.sp +\fB鍵のエントリ\fR +\- 各エントリは、非常に重要な暗号化の鍵の情報を保持します。この情報は、許可していないアクセスを防ぐために、保護された形で格納されます。一般に、この種のエントリとして格納される鍵は、秘密鍵か、対応する公開鍵の証明書チェーンを伴う秘密鍵です。証明書チェーンを参照してください。\fBkeytool\fRコマンドがこの両方のタイプのエントリを処理できるのに対し、\fBjarsigner\fRツールは後者のタイプのエントリ、つまり秘密鍵とそれに関連付けられた証明書チェーンのみを処理します。 +.sp +\fB信頼できる証明書のエントリ\fR: 各エントリは、第三者からの公開鍵証明書を1つ含んでいます。このエントリは、信頼できる証明書と呼ばれます。それは、証明書内の公開鍵が、証明書のSubject(所有者)によって特定されるアイデンティティに由来するものであることを、キーストアの所有者が信頼するからです。証明書の発行者は、証明書に署名を付けることによって、その内容を保証します。 +.RE +.PP +キーストアの別名 +.RS 4 +キーストアのすべてのエントリ(鍵および信頼できる証明書エントリ)は、一意の別名を介してアクセスされます。 +.sp +別名を指定するのは、\fB\-genseckey\fRコマンドを使用して秘密鍵を生成したり、\fB\-genkeypair\fRコマンドを使用して鍵ペア(公開鍵と秘密鍵)を生成したり、\fB\-importcert\fRコマンドを使用して証明書または証明書チェーンを信頼できる証明書のリストに追加するなど、特定のエンティティをキーストアに追加する場合です。これ以後、\fBkeytool\fRコマンドでエンティティを参照する場合は、このときに指定した別名を使用する必要があります。 +.sp +たとえば、\fBduke\fRという別名を使用して新しい公開鍵と秘密鍵のペアを生成し、公開鍵を自己署名証明書でラップするとします。この場合は、次のコマンドを実行します。証明書チェーンを参照してください。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-alias duke \-keypass dukekeypasswd\fR + +.fi +.if n \{\ +.RE +.\} +この例では、初期パスワードとして\fBdukekeypasswd\fRを指定しています。以後、別名\fBduke\fRに関連付けられた秘密鍵にアクセスするコマンドを実行するときは、このパスワードが必要になります。Dukeの秘密鍵のパスワードをあとから変更するには、次のコマンドを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-keypasswd \-alias duke \-keypass dukekeypasswd \-new newpass\fR + +.fi +.if n \{\ +.RE +.\} +パスワードが、\fBdukekeypasswd\fRから\fBnewpass\fRに変更されます。テスト目的の場合、またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。必要なパスワードのオプションをコマンド行で指定しなかった場合は、パスワードの入力を求められます。 +.RE +.PP +キーストアの実装 +.RS 4 +\fBjava\&.security\fRパッケージで提供されている\fBKeyStore\fRクラスは、キーストア内の情報へのアクセスおよび情報の変更を行うための、明確に定義されたインタフェースを提供します。キーストアの固定実装としては、それぞれが特定のタイプのキーストアを対象とする複数の異なる実装が存在可能です。 +.sp +現在、\fBkeytool\fRと\fBjarsigner\fRの2つのコマンド行ツールと、Policy Toolという名前のGUIベースのツールが、キーストアの実装を使用しています。\fBKeyStore\fRクラスは\fBpublic\fRであるため、ユーザーはKeyStoreを使用した他のセキュリティ・アプリケーションも作成できます。 +.sp +キーストアには、Oracleが提供する組込みのデフォルトの実装があります。これは、JKSという名前の独自のキーストア・タイプ(形式)を利用するもので、キーストアをファイルとして実装しています。この実装では、個々の秘密鍵は個別のパスワードによって保護され、キーストア全体の整合性も(秘密鍵とは別の)パスワードによって保護されます。 +.sp +キーストアの実装は、プロバイダベースです。具体的には、\fBKeyStore\fRによって提供されるアプリケーション・インタフェースがサービス・プロバイダ・インタフェース(SPI)に基づいて実装されます。つまり、対応する\fBKeystoreSpi\fR抽象クラス(これも\fBjava\&.security\fRパッケージに含まれています)があり、このクラスが、プロバイダが実装する必要のあるService Provider Interfaceのメソッドを定義しています。ここで、\fIプロバイダ\fRとは、Java Security APIによってアクセス可能なサービスのサブセットに対し、その固定実装を提供するパッケージまたはパッケージの集合のことです。キーストアの実装を提供するには、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/HowToImplAProvider\&.htmlにある +Java暗号化アーキテクチャのプロバイダの実装方法で説明しているように、クライアントはプロバイダを実装し、\fBKeystoreSpi\fRサブクラスの実装を提供する必要があります。 +.sp +アプリケーションでは、\fBKeyStore\fRクラスが提供する\fBgetInstance\fRファクトリ・メソッドを使用することで、様々なプロバイダから異なるタイプのキーストアの実装を選択できます。キーストアのタイプは、キーストア情報の格納形式とデータ形式を定義するとともに、キーストア内の非公開/秘密鍵とキーストアの整合性を保護するために使用されるアルゴリズムを定義します。異なるタイプのキーストアの実装には、互換性はありません。 +.sp +\fBkeytool\fRコマンドは、任意のファイルベースのキーストア実装で動作します。コマンド行で渡されたキーストアの場所をファイル名として扱って、\fBFileInputStream\fRに変換し、ここからキーストア情報をロードします。\fBjarsigner\fRおよび\fBpolicytool\fRコマンドは、URLで指定できる任意の場所からキーストアを読み取ることができます。 +.sp +\fBkeytool\fRと\fBjarsigner\fRの場合、\fB\-storetype\fRオプションを使用してコマンド行でキーストアのタイプを指定できます。Policy Toolの場合は、「キーストア」メニューによってキーストアのタイプを指定できます。 +.sp +ユーザーがキーストアのタイプを明示的に指定しなかった場合、セキュリティ・プロパティ・ファイルで指定された\fBkeystore\&.type\fRプロパティの値に基づいて、ツールによってキーストアの実装が選択されます。このセキュリティ・プロパティ・ファイルは\fBjava\&.security\fRと呼ばれ、Windowsではセキュリティ・プロパティ・ディレクトリ\fBjava\&.home\elib\esecurity\fR、Oracle Solarisでは\fBjava\&.home/lib/security\fRにあります。\fBjava\&.home\fRは、実行時環境のディレクトリです。\fBjre\fRディレクトリは、SDKまたはJava Runtime Environment (JRE)の最上位のディレクトリにあります。 +.sp +各ツールは、\fBkeystore\&.type\fRの値を取得し、この値で指定されたタイプのキーストアを実装しているプロバイダが見つかるまで、現在インストールされているすべてのプロバイダを調べます。そのプロバイダからのキーストアの実装を使用します。\fBKeyStore\fRクラスに定義されているstaticメソッド\fBgetDefaultType\fRを使用すると、アプリケーションやアプレットから\fBkeystore\&.type\fRプロパティの値を取得できます。次のコードは、デフォルトのキーストア・タイプ(\fBkeystore\&.type\fRプロパティで指定されたタイプ)のインスタンスを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBKeyStore keyStore = KeyStore\&.getInstance(KeyStore\&.getDefaultType());\fR + +.fi +.if n \{\ +.RE +.\} +デフォルトのキーストア・タイプは\fBjks\fRで、これはOracleが提供する独自のタイプのキーストアの実装です。これは、セキュリティ・プロパティ・ファイル内の次の行によって指定されています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=jks\fR + +.fi +.if n \{\ +.RE +.\} +各ツールでデフォルト以外のキーストアの実装を使用するには、上の行を変更して別のキーストアのタイプを指定します。たとえば、\fBpkcs12\fRと呼ばれるキーストアのタイプのキーストアの実装を提供するプロバイダ・パッケージがある場合、行を次のように変更します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeystore\&.type=pkcs12\fR + +.fi +.if n \{\ +.RE +.\} +\fB注意:\fR +キーストアのタイプの指定では、大文字と小文字は区別されません。たとえば、JKSとjksは同じものとして扱われます。 +.RE +.PP +証明書 +.RS 4 +証明書(公開鍵証明書)とは、あるエンティティ(発行者)からのデジタル署名付きの文書のことです。証明書には、他のあるエンティティ(署名者)の公開鍵(およびその他の情報)が特別な値を持っていることが書かれています。次の用語は、証明書に関連しています。 +.sp +\fB公開鍵\fR: 公開鍵は、特定のエンティティに関連付けられた数です。公開鍵は、該当するエンティティとの間に信頼できる関係を持つ必要があるすべての人に対して公開することを意図したものです。公開鍵は、署名を検証するのに使用されます。 +.sp +\fBデジタル署名\fR: データがデジタル署名されると、そのデータは、エンティティのアイデンティティと、そのエンティティがデータの内容について知っていることを証明書する署名とともに格納されます。エンティティの秘密鍵を使用してデータに署名を付けると、データの偽造は不可能になります。 +.sp +\fBアイデンティティ\fR: エンティティをアドレス指定する既知の方法。システムによっては、公開鍵をアイデンティティにするものがあります。公開鍵の他にも、Oracle Solaris UIDや電子メール・アドレス、X\&.509識別名など、様々なものをアイデンティティとすることができます。 +.sp +\fB署名\fR: 署名は、なんらかのデータを基にエンティティの秘密鍵を使用して計算されます。署名者、証明書の場合は発行者とも呼ばれます。 +.sp +\fB秘密鍵\fR: 秘密鍵は特定のエンティティのみが知っている数のことで、この数のことを、そのエンティティの秘密鍵といいます。秘密鍵は、他に知られないように秘密にしておくことが前提になっています。秘密鍵と公開鍵は、すべての公開鍵暗号化システムで対になって存在しています。DSAなどの典型的な公開鍵暗号化システムの場合、1つの秘密鍵は正確に1つの公開鍵に対応します。秘密鍵は、署名を計算するのに使用されます。 +.sp +\fBエンティティ\fR: エンティティは、人、組織、プログラム、コンピュータ、企業、銀行など、一定の度合いで信頼の対象となる様々なものを指します。 +.sp +公開鍵暗号化では、ユーザーの公開鍵にアクセスする必要があります。大規模なネットワーク環境では、互いに通信しているエンティティ間で以前の関係が引続き確立されていると仮定したり、使用されているすべての公開鍵を収めた信頼できるリポジトリが存在すると仮定したりすることは不可能です。このような公開鍵の配布に関する問題を解決するために証明書が考案されました。現在では、証明書発行局(CA)が信頼できる第三者として機能します。CAは、他のエンティティの証明書に署名する(発行する)行為を、信頼して任されているエンティティ(企業など)です。CAは法律上の契約に拘束されるので、有効かつ信頼できる証明書のみを作成するものとして扱われます。VeriSign、Thawte、Entrustをはじめ、多くの公的な証明書発行局が存在します。 +.sp +Microsoftの認証サーバー、EntrustのCA製品などを所属組織内で利用すれば、独自の証明書発行局を運営することも可能です。\fBkeytool\fRコマンドを使用すると、証明書の表示、インポートおよびエクスポートを行うことができます。また、自己署名証明書を生成することもできます。 +.sp +現在、\fBkeytool\fRコマンドはX\&.509証明書を対象にしています。 +.RE +.PP +X\&.509証明書 +.RS 4 +X\&.509規格では、証明書に含める情報が定義されており、この情報を証明書に書き込む方法(データ形式)についても記述されています。証明書のすべてのデータは、ASN\&.1/DERと呼ばれる2つの関連規格を使用して符号化されます。Abstract Syntax Notation 1はデータについて記述しています。Definite Encoding Rulesは、データの保存および転送の方法について記述しています。 +.sp +すべてのX\&.509証明書は、署名の他に次のデータを含んでいます。 +.sp +\fBバージョン\fR: 証明書に適用されるX\&.509規格のバージョンを特定します。証明書に指定できる情報は、バージョンによって異なります。今のところ、3つのバージョンが定義されています。\fBkeytool\fRコマンドでは、v1、v2、v3の証明書をインポートおよびエクスポートできます。v3の証明書を生成します。 +.sp +X\&.509 Version 1は、1988年から利用されて広く普及しており、最も一般的です。 +.sp +X\&.509 Version 2では、Subjectや発行者の名前をあとで再利用できるようにするために、Subjectと発行者の一意識別子の概念が導入されました。ほとんどの証明書プロファイル文書では、名前を再使用しないことと、証明書で一意の識別子を使用しないことが、強く推奨されています。Version 2の証明書は、広くは使用されていません。 +.sp +X\&.509 Version 3は最も新しい(1996å¹´)規格で、エクステンションの概念をサポートしています。エクステンションは誰でも定義することができ、証明書に含めることができます。一般的なエクステンションとしては、KeyUsage(\fB署名専用\fRなど、鍵の使用を特定の目的に制限する)、AlternativeNames(DNS名、電子メール・アドレス、IPアドレスなど、他のアイデンティティを公開鍵に関連付けることができる)などがあります。エクステンションには、criticalというマークを付けて、そのエクステンションのチェックと使用を義務づけることができます。たとえば、criticalとマークされ、\fBkeyCertSign\fRが設定されたKeyUsageエクステンションが証明書に含まれている場合、この証明書をSSL通信中に提示すると、証明書が拒否されます。これは、証明書のエクステンションによって、関連する秘密鍵が証明書の署名専用として指定されており、SSLでは使用できないためです。 +.sp +\fBシリアル番号\fR: 証明書を作成したエンティティは、そのエンティティが発行する他の証明書と区別するために、証明書にシリアル番号を割り当てます。この情報は、様々な方法で使用されます。たとえば、証明書が取り消されると、シリアル番号が証明書失効リスト(CRL)に格納されます。 +.sp +\fB証明書アルゴリズム識別子\fR: 証明書に署名を付けるときにCAが使用したアルゴリズムを特定します。 +.sp +\fB発行者名\fR: 証明書に署名を付けたエンティティのX\&.500識別名です。X\&.500識別名を参照してください。通常はCAです。この証明書を使用することは、証明書に署名を付けたエンティティを信頼することを意味します。ルートつまりトップレベルのCAの証明書など、場合によっては発行者が自身の証明書に署名を付けることがあります。 +.sp +\fB有効期間\fR: 各証明書は限られた期間のみ有効です。この期間は開始の日時と終了の日時によって指定され、数秒の短い期間から100年という長期にわたることもあります。選択される有効期間は、証明書への署名に使用される秘密鍵の強度や証明書に支払う金額など、様々な要因で異なります。有効期間は、関連する秘密鍵が損われない場合に、エンティティが公開鍵を信頼できると期待される期間です。 +.sp +\fB主体名\fR: 証明書で公開鍵を認証するエンティティの名前。この名前はX\&.500標準を使用するので、インターネット全体で一意なものと想定されます。これは、エンティティのX\&.500識別名(DN)です。X\&.500識別名を参照してください。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=Java Duke, OU=Java Software Division, O=Oracle Corporation, C=US\fR + +.fi +.if n \{\ +.RE +.\} +これらはそれぞれ主体の通称(CN)、組織単位(OU)、組織(O)、国(C)を表します。 +.sp +\fB主体の公開鍵情報\fR: 名前を付けられたエンティティの公開鍵とアルゴリズム識別子です。アルゴリズム識別子では、公開鍵に対して使用されている公開鍵暗号化システムおよび関連する鍵パラメータが指定されています。 +.RE +.PP +証明書チェーン +.RS 4 +\fBkeytool\fRコマンドでは、秘密鍵および関連する証明書チェーンを含むキーストアの鍵エントリを作成し、管理することができます。このようなエントリでは、秘密鍵に対応する公開鍵は、チェーンの最初の証明書に含まれています。 +.sp +鍵を初めて作成すると、自己署名証明書という1つの要素のみを含むチェーンが開始されます。コマンドの\fB\-genkeypair\fRを参照してください。自己署名証明書は発行者(署名者)が主体と同じです。主体は、その公開鍵が証明書によって認証されるエンティティです。\fB\-genkeypair\fRコマンドを呼び出して新しい公開鍵と秘密鍵のペアを作成すると、公開鍵は常に自己署名証明書でラップされます。 +.sp +この後、証明書署名リクエスト(CSR)が\fB\-certreq\fRコマンドで生成されて、CSRが証明書発行局(CA)に送信されると、CAからのレスポンスが\fB\-importcert\fRでインポートされ、元の自己署名証明書は証明書チェーンによって置き換えられます。\fBの\fR\-certreq\fBおよび\fR\-importcertコマンドオプションを参照してください。チェーンの最後にあるのは、Subjectの公開鍵を認証したCAが発行した証明書(応答)です。チェーン内のその前の証明書は、CAの公開鍵を認証する証明書です。 +.sp +CAの公開鍵を認証する証明書は、多くの場合、自己署名証明書(つまりCAが自身の公開鍵を認証した証明書)であり、これはチェーンの最初の証明書になります。場合によっては、CAが証明書のチェーンを返すこともあります。この場合、チェーン内の最後の証明書(CAによって署名され、鍵エントリの公開鍵を認証する証明書)に変わりはありませんが、チェーン内のその前の証明書は、CSRの送信先のCAとは別のCAによって署名され、CSRの送信先のCAの公開鍵を認証する証明書になります。チェーン内のその前の証明書は、次のCAの鍵を認証する証明書になります。以下同様に、自己署名された「ルート」証明書に達するまでチェーンが続きます。したがって、チェーン内の(最初の証明書以後の)各証明書では、チェーン内の次の証明書の署名者の公開鍵が認証されていることになります。 +.sp +多くのCAは、チェーンをサポートせずに発行済の証明書のみを返します。特に、中間のCAが存在しないフラットな階層構造の場合は、その傾向が顕著です。このような場合は、キーストアにすでに格納されている信頼できる証明書情報から、証明書チェーンを確立する必要があります。 +.sp +別の応答形式(PKCS#7で定義されている形式)では、発行済証明書に加え、証明書チェーンのサポートが含まれています。\fBkeytool\fRコマンドでは、どちらの応答形式も扱うことができます。 +.sp +トップレベル(ルート)CAの証明書は、自己署名証明書です。ただし、ルートの公開鍵への信頼は、ルート証明書自体からではなく、新聞など他のソースから取得されます。これは、VeriSignルートCAなどの識別名を使用して、誰でも自己署名型証明書を生成できるためです。ルートCAの公開鍵は広く知られています。ルートCAの公開鍵を証明書に格納する理由は、証明書という形式にすることで多くのツールから利用できるようになるからにすぎません。つまり、証明書は、ルートCAの公開鍵を運ぶ「媒体」として利用されるのみです。ルートCAの証明書をキーストアに追加するときは、\fB\-printcert\fRオプションを使用して、その前に証明書の内容を表示し、表示されたフィンガープリントと、新聞やルートCAのWebページなどから入手した既知のフィンガープリントとを比較する必要があります。 +.RE +.PP +cacerts証明書ファイル +.RS 4 +\fBcacerts\fRという名前の証明書ファイルは、Windowsではセキュリティ・プロパティ・ディレクトリ\fBjava\&.home\elib\esecurity\fR、Oracle Solarisでは\fBjava\&.home/lib/security\fRに置かれています。\fBjava\&.home\fRは、実行環境のディレクトリ(SDKの\fBjre\fRディレクトリまたはJREの最上位ディレクトリ)です。 +.sp +\fBcacerts\fRファイルは、CAの証明書を含む、システム全体のキーストアです。システム管理者は、キーストア・タイプに\fBjks\fRを指定することで、\fBkeytool\fRコマンドを使用してこのファイルの構成と管理を行うことができます。\fBcacerts\fRキーストア・ファイルは、ルートCA証明書のデフォルト・セットを含んだ状態で出荷されています。デフォルトの証明書を一覧表示するには、次のコマンドを使用します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-list \-keystore java\&.home/lib/security/cacerts\fR + +.fi +.if n \{\ +.RE +.\} +\fBcacerts\fRキーストア・ファイルの初期パスワードは、\fBchangeit\fRです。システム管理者は、SDKのインストール後、このファイルのパスワードとデフォルト・アクセス権を変更する必要があります。 +.sp +\fB注意:\fR +\fBcacerts\fRファイルを確認することが重要です。\fBcacerts\fRファイル内のCAは、署名および他のエンティティへの証明書発行のためのエンティティとして信頼されるため、\fBcacerts\fRファイルの管理は慎重に行う必要があります。\fBcacerts\fRファイルには、信頼するCAの証明書のみが含まれている必要があります。ユーザーは、自身の責任において、\fBcacerts\fRファイルにバンドルされている信頼できるルートCA証明書を検証し、信頼性に関する独自の決定を行います。 +.sp +信頼できないCA証明書を\fBcacerts\fRファイルから削除するには、\fBkeytool\fRコマンドの\fBdelete\fRオプションを使用します。\fBcacerts\fRファイルはJREのインストール・ディレクトリにあります。このファイルを編集するアクセス権がない場合は、システム管理者に連絡してください +.RE +.PP +インターネットRFC 1421証明書符号化規格 +.RS 4 +多くの場合、証明書は、バイナリ符号化ではなく、インターネットRFC 1421規格で定義されている出力可能符号化方式を使用して格納されます。Base 64符号化とも呼ばれるこの証明書形式では、電子メールやその他の機構を通じて、他のアプリケーションに証明書を容易にエクスポートできます。 +.sp +\fB\-importcert\fRと\fB\-printcert\fRコマンドでは、この形式の証明書とバイナリ符号化の証明書を読み込むことができます。\fB\-exportcert\fRコマンドでは、デフォルトでバイナリ符号化の証明書が出力されます。ただし、\fB\-rfc\fRオプションを指定した場合は、出力可能符号化方式の証明書が出力されます。 +.sp +\fB\-list\fRコマンドでは、デフォルトで証明書のSHA1フィンガープリントが出力されます。\fB\-v\fRオプションが指定されている場合、証明書は人が理解できる形式で出力されます。\fB\-rfc\fRオプションが指定されている場合、証明書は出力可能符号化方式で出力されます。 +.sp +出力可能符号化方式で符号化された証明書は、次のテキストで始まり、次のテキストで終了します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\-\fR + +\fBencoded certificate goes here\&. \fR + +\fB\-\-\-\-\-END CERTIFICATE\-\-\-\-\-\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +X\&.500識別名 +.RS 4 +X\&.500識別名は、エンティティを特定するために使用されます。たとえば、X\&.509証明書の\fBsubject\fRフィールドと\fBissuer\fR(署名者)フィールドで指定される名前は、X\&.500識別名です。\fBkeytool\fRコマンドは、次のサブパートをサポートしています。 +.sp +\fBcommonName\fR: Susan Jonesなど、人の通称。 +.sp +\fBorganizationUnit\fR: 小さな組織(部、課など)の名称。Purchasingなどです。 +.sp +\fBlocalityName\fR: 地域(都市)名。Palo Altoなど。 +.sp +\fBstateName\fR: 州名または地方名。Californiaなど。 +.sp +\fBcountry\fR: 2文字の国コード。CHなど。 +.sp +識別名文字列を\fB\-dname\fRオプションの値として指定する場合(たとえば\fB\-genkeypair\fRコマンドに)、文字列は次の形式にする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=cName, OU=orgUnit, O=org, L=city, S=state, C=countryCode\fR + +.fi +.if n \{\ +.RE +.\} +イタリックの項目は、実際に指定する値を表します。短縮形のキーワードの意味は、次のとおりです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=commonName\fR +\fBOU=organizationUnit\fR +\fBO=organizationName\fR +\fBL=localityName\fR +\fBS=stateName\fR +\fBC=country\fR + +.fi +.if n \{\ +.RE +.\} +次に示すのは、識別名文字列の例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=Mark Smith, OU=Java, O=Oracle, L=Cupertino, S=California, C=US\fR + +.fi +.if n \{\ +.RE +.\} +この文字列を使用したコマンドの例です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBkeytool \-genkeypair \-dname "CN=Mark Smith, OU=Java, O=Oracle, L=Cupertino,\fR +\fBS=California, C=US" \-alias mark\fR + +.fi +.if n \{\ +.RE +.\} +キーワードの短縮形では、大文字と小文字は区別されません。たとえば、CN、cnおよびCnは、どれも同じものとして扱われます。 +.sp +一方、キーワードの指定順序には意味があり、各サブコンポーネントは上に示した順序で指定する必要があります。ただし、サブコンポーネントをすべて指定する必要はありません。たとえば、次のように一部のサブコンポーネントのみを指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCN=Steve Meier, OU=Java, O=Oracle, C=US\fR + +.fi +.if n \{\ +.RE +.\} +識別名文字列の値にカンマが含まれる場合に、コマンドラインで文字列を指定するときには、次のようにカンマをバックスラッシュ文字(\e)でエスケープする必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBcn=Peter Schuster, ou=Java\e, Product Development, o=Oracle, c=US\fR + +.fi +.if n \{\ +.RE +.\} +識別名文字列をコマンドラインで指定する必要はありません。識別名を必要とするコマンドを実行するときに、コマンドラインで識別名を指定しなかった場合は、各サブコンポーネントの入力を求められます。この場合は、カンマをバックスラッシュ(\e)でエスケープする必要はありません。 +.RE +.SH "警告" +.SS "信頼できる証明書のインポート警告" +.PP +\fB重要\fR: 信頼できる証明書として証明書をインポートする前に、証明書の内容を慎重に調べてください。 +.PP +Windowsの例: +.PP +まず、\fB\-noprompt\fRオプションを指定せずに\fB\-printcert\fRコマンドまたは\fB\-importcert\fRコマンドを使用して、証明書を表示します。表示された証明書のフィンガープリントが、期待されるフィンガープリントと一致することを確認します。たとえば、証明書が送られてきて、この証明書を\fB\etmp\ecert\fRという名前でファイルに格納しているとします。この場合は、信頼できる証明書のリストにこの証明書を追加する前に、\fB\-printcert\fRコマンドを実行してフィンガープリントを表示できます。たとえば、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB keytool \-printcert \-file \etmp\ecert\fR +\fB Owner: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Issuer: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Serial Number: 59092b34\fR +\fB Valid from: Thu Sep 25 18:01:13 PDT 1997 until: Wed Dec 24 17:01:13 PST 1997\fR +\fB Certificate Fingerprints:\fR +\fB MD5: 11:81:AD:92:C8:E5:0E:A2:01:2E:D4:7A:D7:5F:07:6F\fR +\fB SHA1: 20:B6:17:FA:EF:E5:55:8A:D0:71:1F:E8:D6:9D:C0:37:13:0E:5E:FE\fR +\fB SHA256: 90:7B:70:0A:EA:DC:16:79:92:99:41:FF:8A:FE:EB:90:\fR +\fB 17:75:E0:90:B2:24:4D:3A:2A:16:A6:E4:11:0F:67:A4\fR +.fi +.if n \{\ +.RE +.\} +.PP +Oracle Solarisの例: +.PP +まず、\fB\-noprompt\fRオプションを指定せずに\fB\-printcert\fRコマンドまたは\fB\-importcert\fRコマンドを使用して、証明書を表示します。表示された証明書のフィンガープリントが、期待されるフィンガープリントと一致することを確認します。たとえば、あるユーザーから証明書が送られてきて、この証明書を\fB/tmp/cert\fRという名前でファイルに格納しているとします。この場合は、信頼できる証明書のリストにこの証明書を追加する前に、\fB\-printcert\fRコマンドを実行してフィンガープリントを表示できます。たとえば、次のようにします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB keytool \-printcert \-file /tmp/cert\fR +\fB Owner: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Issuer: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fR +\fB Serial Number: 59092b34\fR +\fB Valid from: Thu Sep 25 18:01:13 PDT 1997 until: Wed Dec 24 17:01:13 PST 1997\fR +\fB Certificate Fingerprints:\fR +\fB MD5: 11:81:AD:92:C8:E5:0E:A2:01:2E:D4:7A:D7:5F:07:6F\fR +\fB SHA1: 20:B6:17:FA:EF:E5:55:8A:D0:71:1F:E8:D6:9D:C0:37:13:0E:5E:FE\fR +\fB SHA256: 90:7B:70:0A:EA:DC:16:79:92:99:41:FF:8A:FE:EB:90:\fR +\fB 17:75:E0:90:B2:24:4D:3A:2A:16:A6:E4:11:0F:67:A4\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次に、証明書を送信した人物に連絡し、この人物が提示したフィンガープリントと、上のコマンドで表示されたフィンガープリントとを比較します。フィンガープリントが一致すれば、送信途中で他の何者か(攻撃者など)による証明書のすり替えが行われていないことを確認できます。送信途中でこの種の攻撃が行われていた場合、チェックを行わずに証明書をインポートすると、攻撃者によって署名されたすべてのもの(攻撃的意図を持つクラス・ファイルを含んだJARファイルなど)を信頼することになります。 +.PP +\fB注意:\fR +証明書をインポートする前に\fB\-printcert\fRコマンドを実行する必要はありません。キーストア内の信頼できる証明書のリストに証明書を追加する前に、\fB\-importcert\fRコマンドによって証明書の情報が表示され、確認を求めるメッセージが表示されるためです。ユーザーはインポート操作を停止できます。ただし、これを実行できるのは、\fB\-noprompt\fRオプションを指定せずに\fB\-importcert\fRコマンドを呼び出す場合のみです。\fB\-noprompt\fRオプションが指定されている場合、ユーザーとの対話は行われません。 +.SS "パスワード警告" +.PP +キーストアに対する操作を行うほとんどのコマンドでは、ストアのパスワードが必要です。また、一部のコマンドでは、非公開/秘密鍵のパスワードが必要になることがあります。パスワードはコマンド行で指定できます(\fB\-storepass\fRオプションと\fB\-keypass\fRオプションを使用)。ただし、テスト目的の場合、またはセキュアなシステムを使用している場合以外は、コマンド行やスクリプトでパスワードを指定しないでください。必要なパスワードのオプションをコマンド行で指定しなかった場合は、パスワードの入力を求められます。 +.SS "証明書の準拠に関する警告" +.PP +インターネット標準RFC 5280では、X\&.509証明書の準拠に関するプロファイルが定義されており、証明書のフィールドおよびエクステンションに有効な値および値の組合せが記載されています。標準については、 +http://tools\&.ietf\&.org/rfc/rfc5280\&.txtを参照してください +.PP +\fBkeytool\fRコマンドでは、これらのルールすべてが適用されるわけではないため、標準に準拠しない証明書を生成できます。標準に準拠しない証明書は、JREや他のアプリケーションで拒否されることがあります。ユーザーは、\fB\-dname\fRや\fB\-ext\fRなどで適正なオプションを指定するようにしてください。 +.SH "注意" +.SS "新しい信頼できる証明書のインポート" +.PP +\fBkeytool\fRコマンドは、キーストアに証明書を追加する前に、キーストア内にすでに存在する信頼できる証明書を使用して、インポートする証明書から(ルートCAの)自己署名証明書に至るまでの信頼のチェーンの構築を試みます。 +.PP +\fB\-trustcacerts\fRオプションを指定した場合、追加の証明書は信頼できるすなわち\fBcacerts\fRという名前のファイルに含まれる証明書のチェーンとみなされます。 +.PP +\fBkeytool\fRコマンドが、インポートする証明書から自己署名証明書(キーストアまたは\fBcacerts\fRファイルに含まれている自己署名証明書)に至るまでの信頼のパスの構築に失敗した場合は、インポートする証明書の情報を表示し、ユーザーに確認を求めます。この場合は、表示された証明書のフィンガープリントと、他のなんらかの(信頼できる)情報源(証明書の所有者など)から入手したフィンガープリントとを比較します。信頼できる証明書として証明書をインポートするときは、証明書が有効であることを慎重に確認する必要があります。信頼できる証明書のインポート警告を参照してください。インポート操作は、証明書を確認する時点で中止できます。\fB\-noprompt\fRオプションが指定されている場合、ユーザーとの対話は行われません。 +.SS "証明書応答のインポート" +.PP +証明書応答をインポートするときは、キーストア内の信頼できる証明書、および(\fB\-trustcacert\fR\fBs\fRオプションが指定されている場合は)\fBcacerts\fRキーストア・ファイルで構成された証明書を使用して証明書応答が検査されます。cacerts証明書ファイルを参照してください。 +.PP +証明書応答が信頼できるかどうかを決定する方法は次のとおりです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書応答が単一のX\&.509証明書である場合、\fBkeytool\fRコマンドは、証明書応答から(ルートCAの)自己署名証明書に至るまでの信頼チェーンの確立を試みます。証明書応答と、証明書応答の認証に使用される証明書の階層構造は、aliasの新しい証明書チェーンを形成します。信頼チェーンが確立されない場合、証明書応答はインポートされません。この場合、\fBkeytool\fRコマンドは証明書を出力せず、ユーザーに検証を求めるプロンプトを表示します。ユーザーが証明書応答の信頼性を判断するのは非常に難しいためです。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +証明書応答がPKCS#7形式の証明書チェーンまたは一連のX\&.509証明書である場合、チェーンは、ユーザーの証明書が最初に、0以上のCA証明書がその次にくるように並べられます。チェーンが自己署名のルートCA証明書で終わり、\fB \-trustcacerts\fRオプションが指定されている場合、\fBkeytool\fRコマンドは、その証明書と、キーストア内または\fBcacerts\fRキーストア・ファイル内の信頼できるすべての証明書を照合しようとします。チェーンが自己署名のルートCA証明書で終わっておらず、\fB\-trustcacerts\fRオプションが指定されている場合、\fBkeytool\fRコマンドは、キーストア内または\fBcacerts\fRキーストア・ファイル内の信頼できる証明書から自己署名のルートCA証明書を見つけてそれをチェーンの末尾に追加しようとします。その証明書が見つからず、\fB\-noprompt\fRオプションが指定されていない場合は、チェーン内の最後の証明書の情報が出力され、ユーザーは確認を求められます。 +.RE +.PP +証明書応答内の公開鍵が\fBalias\fRですでに格納されているユーザーの公開鍵に一致した場合、古い証明書チェーンが応答内の新しい証明書チェーンで置き換えられます。以前の証明書チェーンを有効な\fBkeypass\fRで置き換えることができるのは、エントリの秘密鍵を保護するためのパスワードを指定した場合のみです。パスワードを指定しておらず、秘密鍵のパスワードがキーストアのパスワードと異なる場合は、秘密鍵のパスワードの入力を求められます。 +.PP +このコマンドは、以前のリリースでは\fB\-import\fRという名前でした。このリリースでは、引き続き古い名前がサポートされています。今後は、新しい名前\fB\-importcert\fRが優先されます。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jarsigner(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/tutorial/security/index\&.htmlにある +「コース: Java SEのセキュリティ機能」 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/native2ascii.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/native2ascii.1 new file mode 100755 index 0000000..1c7c319 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/native2ascii.1 @@ -0,0 +1,81 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: native2ascii +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: 国際化ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "native2ascii" "1" "2013å¹´11月21日" "JDK 8" "国際化ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +native2ascii \- サポートされている任意の文字エンコーディングの文字を含むファイルを、ASCIIおよびUnicodeでエスケープされたファイルに変換して(またはその逆)、ローカライズ可能なアプリケーションを作成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBnative2ascii\fR [ \fIinputfile\fR ] [ \fIoutputfile\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIinputfile\fR +.RS 4 +ASCIIに変換するエンコードされたファイル。 +.RE +.PP +\fIoutputfile\fR +.RS 4 +変換されたASCIIファイル。 +.RE +.SH "説明" +.PP +\fBnative2ascii\fRコマンドは、ASCII文字セットに含まれないすべての文字にUnicodeエスケープ(\fB\eu\fR\fIxxxx\fR)表記法を使用して、Java Runtime Environment (JRE)でサポートされているエンコードされたファイルを、ASCIIでエンコードされたファイルに変換します。このプロセスは、ISO\-8859\-1文字セットに含まれない文字が含まれているプロパティ・ファイルで必要です。このツールは、その逆の変換を実行することもできます。 +.PP +\fBoutputfile\fR値を省略した場合、標準出力に出力されます。さらに、\fBinputfile\fR値を省略した場合、標準入力から入力されます。 +.SH "オプション" +.PP +\-reverse +.RS 4 +逆の処理を行います。つまり、ISO\-8859\-1でUnicodeエスケープを使用してエンコードされたファイルを、JREでサポートされる文字エンコーディングのファイルに変換します。 +.RE +.PP +\-encoding \fIencoding_name\fR +.RS 4 +変換処理で使用する文字エンコーディングの名前を指定します。このオプションが存在しない場合は、デフォルトの文字エンコーディング(\fBjava\&.nio\&.charset\&.Charset\&.defaultCharset\fRメソッドで定義された)が使用されます。\fBencoding_name\fR文字列は、JREでサポートされている文字エンコーディングの名前にする必要があります。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/intl/encoding\&.doc\&.htmlにある +「サポートされているエンコーディング」を参照してください +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machine (JVM)に\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/orbd.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/orbd.1 new file mode 100755 index 0000000..7a37084 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/orbd.1 @@ -0,0 +1,266 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: orbd +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "orbd" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +orbd \- CORBA環境のサーバーにある永続オブジェクトをクライアントから検索して呼び出せるようにします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBorbd\fR [ \fIoptions\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +\fBorbd\fRコマンドを使用すると、CORBA環境のサーバーにある永続オブジェクトをクライアントから透過的に検索して呼び出すことができます。orbdツールに含まれるサーバー・マネージャを使用すると、クライアントはCORBA環境でサーバー上にある永続オブジェクトを透過的に検索して呼び出すことができます。永続サーバーは、ネーミング・サービスに永続オブジェクト参照を発行する際、サーバーのポート番号のかわりにORBDのポート番号をオブジェクト参照に含めます。永続オブジェクト参照のオブジェクト参照にORBDポート番号を含めることには、次のような利点があります。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +ネーミング・サービスにあるオブジェクト参照が、サーバーのライフ・サイクルと無関係になります。たとえば、オブジェクト参照は、初めてインストールされたときはネーミング・サービスのサーバーによってネーミング・サービスに発行されますが、その後は、サーバーの開始またはシャットダウンの回数にかかわらず、呼び出したクライアントにORBDが正しいオブジェクト参照を返します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クライアントは一度のみネーミング・サービスのオブジェクト参照をルックアップする必要がありますが、その後はサーバーのライフ・サイクルによる変更とは無関係にこの参照を利用することができます。 +.RE +.PP +ORBDのサーバー・マネージャにアクセスするには、\fBservertool\fRを使用してサーバーを起動する必要があります。servertoolは、アプリケーション・プログラマが、永続サーバーの登録、登録解除、起動および停止を行うためのコマンド行インタフェースです。サーバー・マネージャの詳細は、サーバー・マネージャを参照してください。 +.PP +\fBorbd\fRを起動すると、ネーミング・サービスも起動されます。ネーミング・サービスの詳細。ネーミング・サービスの起動と停止を参照してください。 +.SH "オプション" +.PP +\-ORBInitialPort \fInameserverport\fR +.RS 4 +必須。ネーム・サーバーを起動するポートの番号を指定します。\fBorbd\fRは、起動されると、このポート上で着信リクエストをリスニングします。Oracle Solarisソフトウェアでは、1024より小さいポートでプロセスを開始する場合、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。 +.RE +.SS "必須でないオプション" +.PP +\-port \fIport\fR +.RS 4 +ORBDを起動するポートを指定します。このポートで、永続オブジェクトに対するリクエストをORBDが受け取ります。このポートのデフォルト値は1049です。このポート番号は、永続Interoperable Object References (IOR)のポート・フィールドに追加されます。 +.RE +.PP +\-defaultdb \fIdirectory\fR +.RS 4 +ORBD永続格納ディレクトリ\fBorb\&.db\fRが作成されるベース・ディレクトリを指定します。このオプションが指定されていない場合、デフォルト値は\fB\&./orb\&.db\fRになります。 +.RE +.PP +\-serverPollingTime \fImilliseconds\fR +.RS 4 +\fBservertool\fRを使用して登録された永続サーバーが正常に動作していることをORBDが確認する間隔を指定します。デフォルト値は1000ミリ秒です。\fBmilliseconds\fRに指定する値は、有効な正の整数にする必要があります。 +.RE +.PP +\-serverStartupDelay milliseconds +.RS 4 +\fBservertool\fRを使用して登録された永続サーバーを再起動してから、位置転送の例外を送信するまでのORBDの待機時間を指定します。デフォルト値は1000ミリ秒です。\fBmilliseconds\fRに指定する値は、有効な正の整数にする必要があります。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SS "ネーミング・サービスの起動と停止" +.PP +ネーミング・サービスは、CORBAオブジェクトにネーミングを可能にするCORBAサービスです。ネーミングは名前をオブジェクト参照にバインドすることにより可能になります。ネーム・バインディングをネーミング・サービスに格納すれば、クライアントが名前を指定して目的のオブジェクト参照を取得できるようになります。 +.PP +クライアントまたはサーバーを実行する前に、ORBDを起動します。ORBDには、永続ネーミング・サービスおよび一時ネーミング・サービスが組み込まれています。これらはどちらもCOSネーミング・サービスの実装です。 +.PP +永続ネーミング・サービスは、ネーミング・コンテキストに対して永続性を提供します。つまり、この情報は、サービスの停止や起動後にも維持され、サービスに障害が発生した場合でも回復できます。ORBDを再起動すると、永続ネーミング・サービスはネーミング・コンテキストのグラフを復元し、すべてのクライアントとサーバーの名前のバインディングがそのまま(永続的に)保持されるようにします。 +.PP +後方互換性のため、旧リリースのJDKに同梱されていた一時ネーミング・サービス\fBtnameserv\fRが、今回のリリースのJava SEにも同梱されています。一時ネーム・サービスでは、ネーム・サービスの実行中にのみネーミング・コンテキストが保持されます。サービスが中断されると、ネーミング・コンテキスト・グラフは失われます。 +.PP +\fB\-ORBInitialPort\fR引数は、\fBorbd\fRの必須のコマンド行引数で、ネーミング・サービスが実行されるポートの番号を設定するために使用されます。次の手順では、Java IDL Object Request Broker Daemon用にポート1050を使用できることを前提としています。Oracle Solarisソフトウェアを使用する場合、1024より小さいポートでプロセスを開始するには、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。必要であれば別のポートに変更してください。 +.PP +Solaris、LinuxまたはOS Xコマンド・シェルから\fBorbd\fRを開始するには、次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBorbd \-ORBInitialPort 1050&\fR + +.fi +.if n \{\ +.RE +.\} +.PP +WindowsのMS\-DOSシステム・プロンプトでは、次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBstart orbd \-ORBInitialPort 1050\fR + +.fi +.if n \{\ +.RE +.\} +.PP +これでORBDが実行され、サーバーとクライアントのアプリケーションを実行できるようになります。クライアントとサーバーのアプリケーションは、実行時に、ネーミング・サービスが実行されているポートの番号(必要な場合はさらにマシン名)を認識している必要があります。これを実現する1つの方法は、次のコードをアプリケーションに追加することです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBProperties props = new Properties();\fR +\fBprops\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fR +\fBprops\&.put("org\&.omg\&.CORBA\&.ORBInitialHost", "MyHost");\fR +\fBORB orb = ORB\&.init(args, props);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例では、ネーミング・サービスは、ホスト\fBMyHost\fRのポート1050上で実行されます。別の方法として、コマンド行からサーバーまたはクライアントのアプリケーションを実行するときに、ポート番号またはマシン名あるいはその両方を指定する方法もあります。たとえば、次のコマンド行オプションを使用して、\fBHelloApplication\fRを起動できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava HelloApplication \-ORBInitialPort 1050 \-ORBInitialHost MyHost\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーミング・サービスを停止するには、適切なオペレーティング・システム・コマンドを使用します。たとえば、Oracle Solaris上で\fBpkill\fR +\fBorbd\fRを実行したり、\fBorbd\fRが動作中のDOSウィンドウで\fB[Ctrl]+[C]\fRキーを押します。一時ネーミング・サービスの場合は、サービスが終了されると、ネーミング・サービスに登録された名前が消去される場合があります。Java IDLネーム・サービスは、明示的に停止されるまで実行されます。 +.PP +ORBDに付属するネーミング・サービスの詳細は、 +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.htmlの「Naming Service」を参照してください +.SH "サーバー・マネージャ" +.PP +ORBDのサーバー・マネージャにアクセスして、永続サーバーを実行するには、\fBservertool\fRを使用してサーバーを起動する必要があります。servertoolは、アプリケーション・プログラマが、永続サーバーの登録、登録解除、起動および停止を行うためのコマンド行インタフェースです。\fBservertool\fRを使用してサーバーを起動する場合は、\fBorbd\fRが実行されている場所と同じポートとホストで起動する必要があります。サーバーを異なるポートで実行すると、ローカル・コンテキスト用にデータベースに保存されている情報が無効になり、サービスが正しく動作しません。 +.PP +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlExample\&.htmlの +「Java IDL: The "Hello World" Example」を参照してください +.PP +この例では、チュートリアルの手順に従って\fBidlj\fRコンパイラと\fBjavac\fRコンパイラを実行します。ORBDのサーバー・マネージャを実行するには、次の手順に従ってアプリケーションを実行します。 +.PP +\fBorbd\fRを起動します。 +.PP +Solaris、LinuxまたはOS Xコマンド・シェルで、次のように入力します: +\fBorbd \-ORBInitialPort 1050\fR +.PP +MS\-DOSシステム・プロンプト(Windows)で次のように入力します: +\fBs\fR\fBtart orbd \-ORBInitialPort 105\fR\fB0\fR +.PP +ポート1050はネーム・サーバーを実行するポートです。\fB\-ORBInitialPort\fRオプションは必須コマンド行引数です。Oracle Solarisソフトウェアを使用する場合、1024より小さいポートでプロセスを開始するには、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。 +.PP +\fBservertool\fRを起動します: +\fBservertool \-ORBInitialPort 1050\fR。 +.PP +前回の手順とネーム・サーバー(\fBorbd\fR)のポートが同じであることを確認します。たとえば\fB\-ORBInitialPort 1050\&.\fRのようになります。\fBservertool\fRは、ネーム・サーバーと同じポート上で起動する必要があります。 +.PP +\fBservertool\fRコマンドライン・インタフェースで、\fBservertool\fRプロンプトから\fBHello\fRサーバーを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBservertool > register \-server HelloServer \-classpath \&. \-applicationName\fR +\fB HelloServerApName\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBservertool\fRによってサーバーが登録されて、\fBHelloServerApName\fRという名前がサーバーに割り当てられ、登録されているすべてのサーバー一覧とともにサーバーIDが表示されます。他の端末ウィンドウまたはプロンプトからクライアント・アプリケーションを実行します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava HelloClient \-ORBInitialPort 1050 \-ORBInitialHost localhost\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例の\fB\-ORBInitialHost localhost\fRは省略することができます。ネーム・サーバーが\fBHello\fRクライアントとして同一ホスト上で動作しているからです。ネーム・サーバーが別のホストで実行されている場合は、\-\fBORBInitialHost nameserverhost\fRオプションを使用してIDLネーム・サーバーが実行されているホストを指定します。前の手順で行われたとおりにネーム・サーバー(\fBorbd\fR)ポートを指定します(例: +\fB\-ORBInitialPort 1050\fR)。ORBDのサーバー・マネージャの操作が終了したら、ネーム・サーバー(\fBorbd\fR)と\fBservertool\fRを停止するか終了してください。MS\-DOSプロンプトで\fBorbd\fRをシャットダウンするには、サーバーを実行しているウィンドウを選択して\fB[Ctrl]+[C]\fRキーを押します。 +.PP +Oracle Solarisから\fBorbd\fRをシャットダウンするには、プロセスを検索して、\fBkill\fRコマンドで終了します。サーバーを明示的に停止するまでは、呼出し待機状態が続きます。\fBservertool\fRをシャットダウンするには、\fBquit\fRと入力してキーボードの\fB[Enter]\fRキーを押します。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +servertool(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.htmlの +「Naming Service」 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/pack200.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/pack200.1 new file mode 100755 index 0000000..fdd0517 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/pack200.1 @@ -0,0 +1,354 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: pack200 +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "pack200" "1" "2013å¹´11月21日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +pack200 \- WebデプロイメントのためにJARファイルをpack200圧縮ファイルにパッケージします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200\fR [\fIoptions\fR] \fIoutput\-file\fR \fIJAR\-file\fR +.fi +.if n \{\ +.RE +.\} +.PP +オプションは任意の順序で指定できます。コマンド行またはpropertiesファイルに指定された最後のオプションが、それ以前に指定されたすべてのオプションより優先されます。 +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIoutput\-file\fR +.RS 4 +出力ファイルの名前。 +.RE +.PP +\fIJAR\-file\fR +.RS 4 +入力ファイルの名前。 +.RE +.SH "説明" +.PP +\fBpack200\fRコマンドは、Java gzipコンプレッサを使用してJARファイルをpack200圧縮ファイルに変換するJavaアプリケーションです。pack200ファイルは高圧縮のファイルで、直接デプロイでき、帯域幅の節約やダウンロード時間の短縮が可能です。 +.PP +\fBpack200\fRコマンドには、圧縮エンジンの設定や微調整を行うオプションがあります。一般的な使用方法を次の例に示します。\fBmyarchive\&.pack\&.gz\fRがデフォルトの\fBpack200\fRコマンド設定で作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 myarchive\&.pack\&.gz myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-r +.br +\-\-repack +.RS 4 +JARファイルをパックした後アンパックして、JARファイルを生成します。生成されたファイルは\fBjarsigner\fR(1)ツールの入力ファイルとして使用できます。次の例では、myarchive\&.jarファイルをパックした後、アンパックします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 \-\-repack myarchive\-packer\&.jar myarchive\&.jar\fR +\fBpack200 \-\-repack myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +次の例では、入力ファイル内のファイルの順序を保持します。 +.RE +.PP +\-g +.br +\-\-no\-gzip +.RS 4 +\fBpack200\fRファイルを生成します。このオプションを指定するときは、適切な圧縮ツールを使用する必要があります。また、ターゲット・システムでは、対応する圧縮解除ツールを使用する必要があります。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 \-\-no\-gzip myarchive\&.pack myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-G +.br +\-\-strip\-debug +.RS 4 +出力からデバッグ属性を削除します。これには、\fBSourceFile\fR、\fBLineNumberTable\fR、\fBLocalVariableTable\fR、\fBLocalVariableTypeTable\fRが含まれます。これらの属性を削除すれば、ダウンロードとインストールのサイズは小さくなりますが、デバッガの機能は制限されます。 +.RE +.PP +\-\-keep\-file\-order +.RS 4 +入力ファイル内のファイルの順序を保持します。これは、デフォルトの動作です。 +.RE +.PP +\-O +.br +\-\-no\-keep\-file\-order +.RS 4 +パック・ツールは、すべての要素を並べ替えて送信します。パック・ツールは、JARディレクトリ名を削除してダウンロード・サイズを削減することもできます。ただし、インデックスなど、特定のJARファイルの最適化機能が正常に動作しなくなることがあります。 +.RE +.PP +\-S\fIvalue\fR +.br +\-\-segment\-limit=\fIvalue\fR +.RS 4 +この値は、各アーカイブ・セグメントの予想ターゲット・サイズ\fIN\fR +(バイト単位)です。単一の入力ファイルの必要サイズが\fIN\fRバイトを超えると、独立したセグメントが割り当てられます。特殊なケースとして、値が\fB\-1\fRの場合は、すべての入力ファイルを含む大きな単一のセグメントが生成され、値が0の場合は、クラスごとにセグメントが1つずつ生成されます。アーカイブ・セグメントが大きくなると、断片化が少なくなり圧縮率が高くなりますが、その処理には多くのメモリーが必要です。 +.sp +各セグメントのサイズは、セグメントに変換されるそれぞれの入力ファイルのサイズのほか、その名前と他の送信されるプロパティのサイズを計算して推測されます。 +.sp +デフォルトは\-1です。つまり、パック・ツールは単一のセグメント出力ファイルを作成します。極端に大きな出力ファイルが生成される場合には、入力ファイルをセグメント化(分割)してより小さなJARにすることを強くお薦めします。 +.sp +この制限が課されていない10 MBのJARパック・ファイルは通常、約10%小さくパックされます。しかし、パック・ツールでより大きなJavaヒープ(セグメントの制限の約10倍)を必要とする場合もあります。 +.RE +.PP +\-E\fIvalue\fR +.br +\-\-effort=\fIvalue\fR +.RS 4 +単一の10進数値を指定した場合、パック・ツールは、指定された圧縮率でアーカイブを圧縮します。レベル1の場合は、比較的短い圧縮時間で多少大きめのファイルが生成されますが、レベル9の場合は、非常に長い時間がかかるものの、より圧縮率の高いファイルが生成されます。特殊な値0を指定した場合は、\fBpack200\fRコマンドは元のJARファイルを圧縮なしで直接コピーします。JSR 200標準では、すべての解凍プログラムが、この特別な場合をアーカイブ全体のパススルーと解釈するように規定しています。 +.sp +デフォルトは5です。この場合、標準的な時間で適切な圧縮が行われます。 +.RE +.PP +\-H\fIvalue\fR +.br +\-\-deflate\-hint=\fIvalue\fR +.RS 4 +入力情報を保存するというデフォルト値をオーバーライドします。転送されるアーカイブのサイズは大きくなる場合があります。指定可能な値は、\fBtrue\fR、\fBfalse\fRまたは\fBkeep\fRです。 +.sp +\fBvalue\fRが\fBtrue\fRまたはfalseの場合、\fBpacker200\fRコマンドは指定に従ってデフレーション・ヒントを出力アーカイブに設定します。アーカイブ要素の個々のデフレーション・ヒントは転送されません。 +.sp +\fBkeep\fR値は、入力JARで確認されたデフレーション・ヒントを保持します。これがデフォルトです。 +.RE +.PP +\-m\fIvalue\fR +.br +\-\-modification\-time=\fIvalue\fR +.RS 4 +指定可能な値は\fBlatest\fRと\fBkeep\fRです。 +.sp +値が最新の場合、パック・ツールは、元のアーカイブの使用可能なすべてのエントリのうちの最終更新時刻か、そのセグメントの使用可能なすべてのエントリの最終更新時刻を特定しようとします。この単一の値はセグメントの一部として転送され、各セグメントの全エントリに適用されます。この場合、すべてのインストール・ファイルに単一の日付が設定されるという問題はありますが、アーカイブの転送サイズを少し小さくすることができます。 +.sp +値が\fBkeep\fRの場合、入力JARで確認された変更時間が保持されます。これがデフォルトです。 +.RE +.PP +\-P\fIfile\fR +.br +\-\-pass\-file=\fIfile\fR +.RS 4 +ファイルを圧縮せず、バイト単位で転送するように指定します。このオプションを繰返し使用して、複数のファイルを指定できます。システム・ファイル・セパレータがJARファイル・セパレータのスラッシュ(/)に置き換えられる点を除き、パス名の変換は行われません。結果として得られるファイル名は、文字列として正確にJARファイルでの出現と一致している必要があります。\fBfile\fRにディレクトリ名を指定した場合、そのディレクトリ内のすべてのファイルが転送されます。 +.RE +.PP +\-U\fIaction\fR +.br +\-\-unknown\-attribute=\fIaction\fR +.RS 4 +デフォルトの動作をオーバーライドします。つまり、不明な属性を含むクラス・ファイルが、指定した\fBaction\fRによって渡されます。アクションとして指定可能な値は、\fBerror\fR、\fBstrip\fRまたは\fBpass\fRです。 +.sp +値が\fBerror\fRの場合、\fBpack200\fRコマンド操作全体が失敗して適切な説明が表示されます。 +.sp +値が\fBstrip\fRの場合、属性は削除されます。Java Virtual Machine (JVM)必須属性を削除すると、クラス・ローダーの障害が発生することがあります。 +.sp +値が\fBpass\fRの場合、クラス全体が1つのリソースとして転送されます。 +.RE +.PP +\-C\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-class\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +次のオプションを参照してください。 +.RE +.PP +\-F\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-field\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +次のオプションを参照してください。 +.RE +.PP +\-M\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-method\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +次のオプションを参照してください。 +.RE +.PP +\-D\fIattribute\-name\fR=\fIlayout\fR +.br +\-\-code\-attribute=\fIattribute\-name\fR=\fIaction\fR +.RS 4 +前述の4つのオプションでは、クラス・エンティティに\fBclass\-attribute\fR、\fBfield\-attribute\fR、\fBmethod\-attribute\fRおよび\fBcode\-attribute\fRなどの属性のレイアウトを指定できます。\fIattribute\-name\fRには、これからレイアウトまたはアクションを定義する属性の名前を指定します。\fIaction\fRとして指定可能な値は、\fBsome\-layout\-string\fR、\fBerror\fR、\fBstrip\fR、\fBpass\fRです。 +.sp +\fBsome\-layout\-string\fR: レイアウト言語はJSR 200仕様で定義されています。例: +\fB\-\-class\-attribute=SourceFile=RUH\fR。 +.sp +値が\fBerror\fRの場合、\fBpack200\fR操作が失敗して説明が表示されます。 +.sp +値が\fBstrip\fRの場合、属性が出力から削除されます。VM必須属性を削除するとクラス・ローダーの障害が発生することがあります。たとえば、\fB\-\-class\-attribute=CompilationID=pass\fRというこの属性を含むクラス・ファイルを転送します。パック・ツールは、その他のアクションを行いません。 +.sp +値が\fBpass\fRの場合、クラス全体が1つのリソースとして転送されます。 +.RE +.PP +\-f \fIpack\&.properties\fR +.br +\-\-config\-file=\fIpack\&.properties\fR +.RS 4 +コマンド行に、パック・ツールを初期化するためのJavaプロパティが含まれている構成ファイルを指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpack200 \-f pack\&.properties myarchive\&.pack\&.gz myarchive\&.jar\fR +\fBmore pack\&.properties\fR +\fB# Generic properties for the packer\&.\fR +\fBmodification\&.time=latest\fR +\fBdeflate\&.hint=false\fR +\fBkeep\&.file\&.order=false\fR +\fB# This option will cause the files bearing new attributes to\fR +\fB# be reported as an error rather than passed uncompressed\&.\fR +\fBunknown\&.attribute=error\fR +\fB# Change the segment limit to be unlimited\&.\fR +\fBsegment\&.limit=\-1\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-v +.br +\-\-verbose +.RS 4 +最小限のメッセージを出力します。このオプションを複数指定すると、より長いメッセージが作成されます。 +.RE +.PP +\-q +.br +\-\-quiet +.RS 4 +メッセージを表示せずに動作するように指定します。 +.RE +.PP +\-l\fIfilename\fR +.br +\-\-log\-file=\fIfilename\fR +.RS 4 +出力メッセージのログ・ファイルを指定します。 +.RE +.PP +\-? +.br +\-h +.br +\-\-help +.RS 4 +このコマンドに関するヘルプ情報を出力します。 +.RE +.PP +\-V +.br +\-\-version +.RS 4 +このコマンドに関するバージョン情報を出力します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +指定されたオプションをJava Virtual Machineに渡します。詳細は、java(1)コマンドのリファレンス・ページを参照してください。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。 +.RE +.SH "終了ステータス" +.PP +次の終了値が返されます: 正常終了の場合は0、エラーが発生した場合は0より大きい値。 +.SH "注意" +.PP +このコマンドと\fBpack\fR(1)を混同しないでください。\fBpack\fRおよび\fBpack200\fRコマンドは、別々の製品です。 +.PP +JDKに付属するJava SE API仕様との相違が見つかった場合には、仕様を優先してください。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +unpack200(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jarsigner(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/policytool.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/policytool.1 new file mode 100755 index 0000000..749a8fd --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/policytool.1 @@ -0,0 +1,158 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: policytool +.\" Language: Japanese +.\" Date: 2015å¹´3月3日 +.\" SectDesc: セキュリティ・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "policytool" "1" "2015å¹´3月3日" "JDK 8" "セキュリティ・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +policytool \- ユーティリティGUI経由で取得したユーザー入力に基づいて、プレーン・テキストのポリシー・ファイルを読み書きします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpolicytool\fR [ \fB\-file\fR ] [ \fIfilename\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\-file +.RS 4 +ポリシー・ファイルを読み込むように\fBpolicytool\fRに指示します。 +.RE +.PP +\fIfilename\fR +.RS 4 +ロードするファイルの名前。 +.RE +.PP +\fB例\fR: +.PP +ポリシー・ツール管理ユーティリティを実行します: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpolicytool\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBpolicytool\fRコマンドを実行し、指定されたファイルをロードします: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpolicytool \-file \fR\fB\fImypolicyfile\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SH "説明" +.PP +\fBpolicytool\fRコマンドは、管理者のGUIを呼び出します。これにより、システム管理者はローカル・ポリシー・ファイルの内容を管理できるようになります。ポリシー・ファイルは\fB\&.policy\fR拡張子を持つプレーンテキスト・ファイルで、ドメイン別にリモート・リクエスタを権限オブジェクトにマップします。詳細は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.htmlにある +「Default Policy Implementation and Policy File Syntax」を参照してください +.SH "オプション" +.PP +\-file +.RS 4 +ポリシー・ファイルを読み込むように\fBpolicytool\fRに指示します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Default Policy Implementation and Policy File Syntax」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Policy File Creation and Management」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyGuide\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Permissions in Java SE Development Kit (JDK)」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/permissions\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Java Security Overview」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/overview/jsoverview\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Java Cryptography Architecture (JCA) Reference Guide」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmic.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmic.1 new file mode 100755 index 0000000..1bf2417 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmic.1 @@ -0,0 +1,338 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: rmic +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "rmic" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +rmic \- Java Remote Method Protocol (JRMP)またはInternet Inter\-Orb protocol (IIOP)を使用するリモート・オブジェクトのスタブ、スケルトンおよびTieクラスを生成します。Object Management Group (OMG)インタフェース定義言語(IDL)も生成します +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmic\fR [ \fIoptions\fR ] \fIpackage\-qualified\-class\-names\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行\fBオプション\fR。オプションを参照してください。 +.RE +.PP +\fIpackage\-qualified\-class\-names\fR +.RS 4 +パッケージを含むクラス名。例: +\fBjava\&.awt\&.Color\fR。 +.RE +.SH "説明" +.PP +\fB非推奨に関する注意:\fR +Java Remote Method Protocol (JRMP)スタブおよびスケルトンの静的な生成のサポートは非推奨になりました。動的に生成されるJRMPスタブをかわりに使用して、JRMPベースのアプリケーションにこのツールを使用する必要性をなくすことをお薦めします。詳細は、\fBjava\&.rmi\&.server\&.UnicastRemoteObject\fR仕様(http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/server/UnicastRemoteObject\&.html)を参照してください。 +.PP +\fBrmic\fRコンパイラは、Java Remote Method Protocol (JRMP)とスタブおよびTieクラス・ファイル(IIOPプロトコル)を使用して、リモート・オブジェクトのスタブおよびスケルトン・クラス・ファイルを生成します。リモート・オブジェクトの実装クラスであるこれらのクラス・ファイルは、Javaプログラミング言語のクラスをコンパイルしたときに生成されます。リモート実装クラスは、\fBjava\&.rmi\&.Remote\fRインタフェースを実装するクラスです。\fBrmic\fRコマンドでのクラス名は、そのクラスが\fBjavac\fRコマンドでコンパイルが成功していて、かつ完全修飾パッケージ名である必要があります。たとえば、次に示すクラス・ファイル名\fBHelloImpl\fRで\fBrmic\fRコマンドを実行すると、helloサブディレクトリ(クラスのパッケージの名前の付いた)に\fBHelloImpl_Stub\&.class \fRファイルが作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmic hello\&.HelloImpl\fR + +.fi +.if n \{\ +.RE +.\} +.PP +リモート・オブジェクトのスケルトンはJRMPプロトコル・サーバー側のエンティティで、リモート・オブジェクト実装を呼び出すメソッドを含みます。 +.PP +リモート・オブジェクトのTieは、スケルトンと同様にサーバー側のエンティティですが、IIOPプロトコルを使用してクライアントと通信します。 +.PP +スタブとは、リモート・オブジェクトのクライアント側での代理です。スタブは、リモート・オブジェクトのメソッド呼出しを、実物のリモート・オブジェクトが常駐するサーバーと通信する役割を持ちます。したがって、クライアントのリモート・オブジェクトへの参照は、実際はローカル・スタブへの参照となります。 +.PP +デフォルトで\fBrmic\fRコマンドは、1\&.2 JRMPスタブ・プロトコル・バージョンのみを使用するスタブ・クラスを生成します。これは、\fB\-v1\&.2\fRオプションを指定した場合と同じ動作です。リリース5\&.0以前では\fB\-vcompat\fRオプションがデフォルトでした。IIOPプロトコル用のスタブおよびTieクラスを生成するには\fB\-iiop\fRオプションを使用します。オプションを参照してください。 +.PP +スタブはリモート・インタフェースのみを実装し、リモート・オブジェクトが実装するローカル・インタフェースは実装していません。JRMPスタブはリモート・オブジェクトが実装するリモート・インタフェースと同じものを実装しているので、クライアントは、キャストや型チェックにJavaプログラミング言語に組み込まれた演算子を使用することができます。IIOPの場合は、\fBPortableRemoteObject\&.narrow\fRメソッドを使用する必要があります。 +.SH "オプション" +.PP +\-bootclasspath \fIpath\fR +.RS 4 +ブートストラップ・クラス・ファイルの位置をオーバーライドします。 +.RE +.PP +\-classpath path +.RS 4 +\fBrmic\fRコマンドがクラスを探すためのパスを指定します。このオプションは、デフォルトや\fBCLASSPATH\fR環境変数設定をオーバーライドします。ディレクトリはコロンで分割します。パスの一般的な形式は\fB\&.:<your_path>\fRです。例: +\fB\&.:/usr/local/java/classes\fR +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +生成されたクラス階層の出力先ディレクトリのルートを指定します。このオプションを使用すると、スタブ、スケルトン、およびTieファイルを格納するディレクトリを指定できます。たとえば、次のコマンドはMyClassから導出されたスタブおよびスケルトン・クラスをディレクトリ/java/classes/exampleclassに格納します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmic \-d /java/classes exampleclass\&.MyClass\fR + +.fi +.if n \{\ +.RE +.\} +\fB\-d\fRオプションが指定されていない場合、デフォルトの動作は\fB\-d\fRが指定されていた場合と同じです。ターゲット・クラスのパッケージ階層が現在のディレクトリに作成され、stub/tie/skeletonファイルが格納されます。以前のリリースの\fBrmic\fRコマンドでは、\fB\-d\fRが指定されていない場合は、パッケージ階層は作成されず、出力ファイルはすべて現在のディレクトリに直接格納されていました。 +.RE +.PP +\-extdirs \fIpath\fR +.RS 4 +インストール済拡張機能の位置をオーバーライドします。 +.RE +.PP +\-g +.RS 4 +ローカル変数を含むすべてのデバッグ情報を生成します。デフォルトでは、行番号情報のみ生成されます。 +.RE +.PP +\-idl +.RS 4 +\fBrmic\fRコマンドによって、指定したクラスおよび参照されたクラスのOMG IDLが生成されます。IDLでは、プログラミング言語に依存せずに、宣言するだけでオブジェクトのAPIを指定することができます。IDLは、メソッドおよびデータの仕様として使用します。CORBAバインディングを提供する任意の言語で、メソッドおよびデータの作成および呼出しを行うことができます。これらの言語には、JavaおよびC++が含まれています。http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.htmlの +「Java IDL: IDL to Java Language Mapping」を参照してください +.sp +\fB\-idl\fRオプションを使用するときには、他のオプションも指定できます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +既存のスタブ/Tie/IDLが入力クラスよりも新しい場合でも、\fB\-always\fRまたは\fB\-alwaysgenerate\fRオプションは再生成を強制します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-factory\fRオプションは、生成されたIDLで\fBfactory\fRキーワードを使用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +J\fBavaPackage[\&.class]\fR +\fBtoIDLModule\fRの\fB\-idlModule\fRは\fBIDLEntity\fRパッケージ・マッピングを指定します。例: +\fB\-idlModule\fR +\fBmy\&.module my::real::idlmod\fR +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-idlFile\fR +\fBfromJavaPackage[\&.class] toIDLFile\fRは\fBIDLEntity\fRファイル・マッピングを指定します。例: +\fB\-idlFile test\&.pkg\&.X TEST16\&.idl\fR +.RE +.RE +.PP +\-iiop +.RS 4 +\fBrmic\fRコマンドによって、JRMPのスタブとスケルトン・クラスのかわりに、IIOPのスタブとTieクラスが生成されます。スタブ・クラスは、リモート・オブジェクトのローカル・プロキシで、クライアントからサーバーに呼出しを送信するときに使用されます。各リモート・インタフェースにはスタブ・クラスが必要です。スタブ・クラスによってリモート・インタフェースが実装されます。クライアントでリモート・オブジェクトを参照するときは、スタブを参照することになります。タイ・クラスは、サーバー側で着呼を処理し、その呼出しを適切な実装クラスにディスパッチするときに使用されます。各実装クラスには、タイ・クラスが必要です。 +.sp +\fB\-iiop\fRを使用して\fBrmic\fRコマンドを呼び出すと、次の命名規則に準拠したスタブとTieが生成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB_<implementationName>_stub\&.class\fR +\fB_<interfaceName>_tie\&.class\fR + +.fi +.if n \{\ +.RE +.\} +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-iiop\fRオプションを使用するときには、他のオプションも指定できます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +既存のスタブ/Tie/IDLが入力クラスよりも新しい場合でも、\fB\-always\fRまたは\fB\-alwaysgenerate\fRオプションは再生成を強制します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-nolocalstubs\fRオプションでは、同じプロセスのクライアントとサーバーに最適化されたスタブは作成されません。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-noValueMethods\fRオプションは\fB\-idl\fRオプションとともに使用する必要があります。\fB\-noValueMethods\fRオプションは、送信されるIDLに\fBvaluetype\fRメソッドおよび初期化子を追加できないようにします。このメソッドおよび初期化子は、valuetypeの場合はオプションです。\fB\-idl\fRオプションとともに\fB\-noValueMethods\fRオプションを指定しないかぎり生成されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-poa\fRオプションは継承を\fBorg\&.omg\&.CORBA_2_3\&.portable\&.ObjectImpl\fRから\fBorg\&.omg\&.PortableServer\&.Servant\fRに変更します。ポータブル・オブジェクト・アダプタ(POA)の\fBPortableServer\fRモジュールは、ネイティブの\fBServant\fR型を定義します。Javaプログラミング言語では、\fBServant\fR型はJavaの\fBorg\&.omg\&.PortableServer\&.Servant\fRクラスにマップされます。これは、すべてのPOAサーバント実装のベース・クラスとして機能し、アプリケーション・プログラマが呼び出すことのできるいくつかのメソッド、およびPOAによって呼び出され、サーバントの動作を制御するためにユーザーがオーバーライドできるメソッドを提供します。OMG IDL to Java Language Mapping Specification、CORBA V 2\&.3\&.1 ptc/00\-01\-08\&.pdfに準拠しています。 +.RE +.RE +.PP +\-J +.RS 4 +Javaコマンドとともに使用して、\fB\-J\fRオプションは\fB\-J\fRの後ろに続く引数をJavaインタプリタに渡します(\fB\-J\fRと引数の間にスペースは入れません)。 +.RE +.PP +\-keep or \-keepgenerated +.RS 4 +スタブ、スケルトン、またはTieクラスのために生成された\fB\&.java\fRソース・ファイルを保持し、\fB\&.class\fRファイルと同じディレクトリに書き込みます。 +.RE +.PP +\-nowarn +.RS 4 +警告をオフにします。\fB\-nowarn\fRオプションが使用される場合。コンパイラは警告を表示しません。 +.RE +.PP +\-nowrite +.RS 4 +コンパイルしたクラスをファイル・システムに書き込みません。 +.RE +.PP +\-vcompat (非推奨) +.RS 4 +1\&.1と1\&.2の両方のJRMPスタブ・プロトコル・バージョンと互換性のあるスタブおよびスケルトン・クラスを作成します。5\&.0以前のリリースではこのオプションがデフォルトでした。生成されたスタブ・クラスは、JDK 1\&.1仮想マシンにロードされると1\&.1スタブ・プロトコル・バージョンを使用し、JDK 1\&.2以降の仮想マシンにロードされると1\&.2スタブ・プロトコル・バージョンを使用します。生成されたスケルトン・クラスでは、1\&.1と1\&.2の両方のスタブ・プロトコル・バージョンをサポートします。生成されたクラスは両方の操作モードをサポートするために、サイズが大きくなります。注意:このオプションは非推奨になりました。説明を参照してください。 +.RE +.PP +\-verbose +.RS 4 +コンパイラやリンカーが、コンパイルされているクラスやロードされているクラス・ファイルについてのメッセージを表示するようにします。 +.RE +.PP +\-v1\&.1 (非推奨) +.RS 4 +1\&.1 JRMPスタブ・プロトコル・バージョンのみのスタブおよびスケルトン・クラスを生成します。\fB\-v1\&.1\fRオプションを使用できるのは、JDK 1\&.1から\fBrmic\fRコマンドで生成され、アップグレードできない(さらにダイナミック・クラス・ローディングを使用していない)、既存の静的デプロイされたスタブ・クラスに対し、直列化互換性のあるスタブ・クラスを生成する場合のみです。注意:このオプションは非推奨になりました。説明を参照してください。 +.RE +.PP +\-v1\&.2 (非推奨) +.RS 4 +(デフォルト)1\&.2 JRMPスタブ・プロトコル・バージョンのみのスタブ・クラスを生成します。スケルトン・クラスは1\&.2スタブ・プロトコル・バージョンで使用できないため、スケルトン・クラスは生成されません。生成されたスタブ・クラスは、JDK 1\&.1仮想マシンにロードされても動作しません。注意:このオプションは非推奨になりました。説明を参照してください。 +.RE +.SH "環境変数" +.PP +CLASSPATH +.RS 4 +ユーザー定義クラスへのパスをシステムに指定します。ディレクトリはコロンで区切られます。例: +\fB\&.:/usr/local/java/classes\fR +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラス・パスの設定 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmid.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmid.1 new file mode 100755 index 0000000..bfaa24d --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmid.1 @@ -0,0 +1,354 @@ +'\" t +.\" Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: rmid +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "rmid" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +rmid \- 起動システム・デーモンを開始すると、オブジェクトをJava Virtual Machine(VM)に登録してアクティブ化できるようになります。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.SH "説明" +.PP +\fBrmid\fRコマンドは、起動システム・デーモンを開始します。起動システム・デーモンを開始してからでないと、アクティブ化可能オブジェクトをアクティブ化システムに登録したり、JVM内でアクティブ化したりすることができません。アクティブ化可能なオブジェクトを使用するプログラムの作成方法の詳細は、\fIアクティブ化の使用\fRに関するチュートリアル(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi/activation/overview\&.html)を参照してください +.PP +\fBrmid\fRコマンドを実行し、次のようにセキュリティ・ポリシー・ファイルを指定して、デーモンを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBrmid\fRコマンドのOracleの実装を実行する場合、デフォルトでは、セキュリティ・ポリシー・ファイルを指定する必要があります。それは、\fBrmid\fRコマンドが起動グループ用にJVMを起動するために各\fBActivationGroupDesc\fR内の情報を使用できるかどうかを検証できるようにするためです特に、\fBActivationGroupDesc\fRコンストラクタに渡される\fBCommandEnvironment\fRや任意のプロパティによって指定されるコマンドおよびオプションは、\fBrmid\fRコマンドのセキュリティ・ポリシー・ファイルの中で明示的に許可することが必要になりました。\fBsun\&.rmi\&.activation\&.execPolicy\fRプロパティの値は、起動グループ用にJVMを起動するために\fBActivationGroupDesc\fR内の情報を使用できるかどうかを判断するときに\fBrmid\fRコマンドが使用するポリシーを決定します。詳細は、\-J\-Dsun\&.rmi\&.activation\&.execPolicy=policyオプションの説明を参照してください。 +.PP +\fBrmid\fRコマンドを実行すると、デフォルト・ポート1098でアクティベータと内部レジストリが起動され、\fBActivationSystem\fRがこの内部レジストリ内の名前\fBjava\&.rmi\&.activation\&.ActivationSystem\fRにバインドされます。 +.PP +レジストリに他のポートを指定するには、\fBrmid\fRコマンドの実行時に\fB\-port\fRオプションを指定する必要があります。たとえば、次のコマンドは、レジストリのデフォルト・ポート1099で、起動システム・デーモンとレジストリを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-J\-Djava\&.security\&.policy=rmid\&.policy \-port 1099\fR + +.fi +.if n \{\ +.RE +.\} +.SH "必要に応じてRMIDを開始" +.PP +\fBrmid\fRをコマンドラインから開始するには、\fBinetd\fR(Oracle Solarisの場合)、または\fBxinetd\fR(Linuxの場合)を構成して\fBrmid\fRを必要に応じて開始する方法もあります。 +.PP +RMIDを開始すると、\fBSystem\&.inheritedChannel\fRメソッドを呼び出して、継承されたチャンネル(\fBinetd\fR/\fBxinetd\fRから継承)を取得しようとします。継承されたチャンネルがnullであるか、\fBjava\&.nio\&.channels\&.ServerSocketChannel\fRのインスタンスでなかった場合、RMIDはそのチャンネルは\fBinetd\fR/\fBxinetd\fRによって起動されたものではないと判断し、前述のように起動します。 +.PP +継承されたチャンネルが\fBServerSocketChannel\fRインスタンスである場合は、RMIDはエクスポートするリモート・オブジェクト、つまり\fBjava\&.rmi\&.activation\&.ActivationSystem\fRがバインドされているレジストリと\fBjava\&.rmi\&.activation\&.Activator\fRリモート・オブジェクトに対するリクエストを受信するサーバー・ソケットとして、\fBServerSocketChannel\fRから取得した\fBjava\&.net\&.ServerSocket\fRを使用します。このモードでは、RMIDの動作は、次のことを除いて、コマンドラインから起動した場合と同じです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSystem\&.err\fRに対する出力は、ファイルにリダイレクトされる。このファイルは\fBjava\&.io\&.tmpdir\fRシステム・プロパティで指定されるディレクトリ(通常は\fB/var/tmp\fRまたは\fB/tmp\fR)にある。ファイル名の接頭辞は\fBrmid\-err\fRで、接尾辞は\fBtmp\fRである。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-port\fRオプションは使用できません。このオプションが指定されている場合、RMIDはエラー・メッセージが表示されて終了します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-log\fRオプションは必須。このオプションが指定されていない場合、RMIDはエラー・メッセージが表示されて終了します。 +.RE +.PP +必要に応じてサービスを開始するように構成する方法の詳細は、\fBinetd\fR +(Oracle Solarisの場合)、または\fBxinetd\fR +(Linux)のマニュアル・ページを参照してください。 +.SH "オプション" +.PP +\-C\fIオプション\fR +.RS 4 +\fBrmid\fRコマンドの子プロセス(起動グループ)が作成されたときに、それぞれの子プロセスにコマンド行引数として渡されるオプションを指定します。たとえば、次のように指定すると、起動システム・デーモンによって生成される各仮想マシンにプロパティを渡すことができます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-C\-Dsome\&.property=value\fR + +.fi +.if n \{\ +.RE +.\} +コマンド行引数を子プロセスに渡す機能は、デバッグを行う場合に便利です。たとえば、次のコマンドでは、すべての子JVMでserver\-callロギングが可能です。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-C\-Djava\&.rmi\&.server\&.logCalls=true\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\fIoption\fR +.RS 4 +RMIDを実行しているJavaインタプリタに渡すオプションを指定します。たとえば、\fBrmid\fRコマンドが\fBrmid\&.policy\fRという名前のポリシー・ファイルを使用するように指定するには、\fBrmid\fRのコマンド行で\fB\-J\fRオプションを使用して、\fBjava\&.security\&.policy\fRプロパティを定義します。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmid \-J\-Djava\&.security\&.policy\-rmid\&.policy\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-J\-Dsun\&.rmi\&.activation\&.execPolicy=\fIpolicy\fR +.RS 4 +起動グループが実行されることになるJVMの起動に使用するコマンドおよびコマンド行オプションをチェックするために、RMIDが採用するポリシーを指定します。このオプションは、Java RMI起動デーモンのOracleの実装のみに存在することに注意してください。コマンド行にこのプロパティを指定しない場合、結果は\fB\-J\-Dsun\&.rmi\&.activation\&.execPolicy=default\fRを指定した場合と同じになります。\fBpolicy\fRに指定可能な値は、\fBdefault\fR、\fBpolicyClassName\fRまたは\fBnone\fRです。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +デフォルト +.sp +\fBdefault\fRまたは未指定値の\fBexecPolicy\fRの場合、\fBrmid\fRコマンドが実行できるのは、\fBrmid\fRコマンドが使用するセキュリティ・ポリシー・ファイルの中で、実行する権限が\fBrmid\fRに与えられているコマンドおよびコマンド行オプションのみです。デフォルトの実行ポリシーで使用できるのは、デフォルトの起動グループ実装のみです。 +.sp +\fBrmid\fRコマンドは、起動グループ用のJVMを起動するときに、そのグループについて登録された起動グループ記述子である\fBActivationGroupDesc\fR内の情報を使用します。グループ記述子は、\fBActivationGroupDesc\&.CommandEnvironment\fRを指定します(省略可能)。これには、起動グループを開始するコマンドと、そのコマンド行に追加できるコマンド行オプションが含まれています。デフォルトでは、\fBrmid\fRコマンドは\fBjava\&.home\fRにある\fBjava\fRコマンドを使用します。グループ記述子には、コマンド行にオプションとして追加されるプロパティ・オーバーライドも含まれます(\fB\-D<property>=<value>\fRとして定義されます)。\fBcom\&.sun\&.rmi\&.rmid\&.ExecPermission\fR権限は\fBrmid\fRコマンドに、起動グループを開始するためにグループ記述子の\fBCommandEnvironment\fRで指定されたコマンドを実行する権限を付与します。\fBcom\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR権限は起動グループの開始時に、グループ記述子でプロパティ・オーバーライドとして、または\fBCommandEnvironment\fRでオプションとして指定されたコマンド行オプションを、\fBrmid\fRコマンドが使用することを許可します。\fBrmid\fRコマンドに様々なコマンドおよびオプションを実行する権限を付与する場合、権限\fBExecPermission\fRおよび\fBExecOptionPermission\fRをすべてのコード・ソースに付与する必要があります。 +.sp +\fBExecPermission\fR +.sp +\fBExecPermission\fRクラスは、起動グループを開始するために\fBrmid\fRコマンドが特定のコマンドを実行する権限を表します。 +.sp +\fB構文\fR: +\fBExecPermission\fRの名前は、\fBrmid\fRコマンドに実行を許可するコマンドのパス名です。スラッシュ(/)およびアスタリスク(*)で終わるパス名は、そのディレクトリに含まれるすべてのファイルを示します。スラッシュはファイル区切り文字\fBFile\&.separatorChar\fRです。スラッシュ(/)およびマイナス符号(\-)で終わるパス名は、そのディレクトリに含まれるすべてのファイルとサブディレクトリ(再帰的に)を示します。特殊なトークン\fB<<ALL FILES>>\fRで構成されるパス名は、どのファイルとも一致します。 +.sp +パス名にアスタリスク(*)を指定した場合は、現在のディレクトリ内のすべてのファイルを示します。パス名にマイナス符号(\-)を指定した場合は、現在のディレクトリ内のすべてのファイルおよび(再帰的に)現在のディレクトリに含まれるすべてのファイルとサブディレクトリを示します。 +.sp +\fBExecOptionPermission\fR +.sp +\fBExecOptionPermission\fRクラスは、起動グループを開始するときに\fBrmid\fRコマンドで特定のコマンド行オプションを使用できる権限を表します。\fBExecOptionPermission\fRの名前は、コマンド行オプションの値です。 +.sp +\fB構文\fR: オプションでは、ワイルドカードが限定的にサポートされます。アスタリスクは、ワイルドカード・マッチを表します。アスタリスク(*)は、オプション名そのものとして使用できます。つまり、任意のオプションを表すことができます。また、オプション名の末尾に使用することもできます。ただし、ドット(\&.)か等号(=)の直後にアスタリスク(*)を指定する必要があります。 +.sp +例: +\fB*\fRや\fB\-Dmydir\&.*\fRや\fB\-Da\&.b\&.c=*\fRは有効ですが、\fB*mydir\fRや\fB\-Da*b\fRや\fBab*\fRは無効です。 +.sp +\fBrmidのポリシー・ファイル\fR +.sp +\fBrmid\fRコマンドに様々なコマンドおよびオプションを実行する権限を許可する場合は、権限\fBExecPermission\fRおよび\fBExecOptionPermission\fRをすべてのコード・ソースに付与する必要があります(汎用的に)。これらの権限をチェックするのは\fBrmid\fRコマンドのみなので、これらの権限を汎用的に付与しても安全です。 +.sp +\fBrmid\fRコマンドに各種の実行権限を付与するポリシー・ファイルの例を、次に示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBgrant {\fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR +\fB "/files/apps/java/jdk1\&.7\&.0/solaris/bin/java";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR +\fB "/files/apps/rmidcmds/*";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR +\fB "\-Djava\&.security\&.policy=/files/policies/group\&.policy";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR +\fB "\-Djava\&.security\&.debug=*";\fR +\fB \fR +\fB permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR +\fB "\-Dsun\&.rmi\&.*";\fR +\fB};\fR + +.fi +.if n \{\ +.RE +.\} +最初に付与されている権限は、\fBrmid\fRコマンドに対し、パス名により明示的に指定される\fBjava\fRコマンドの1\&.7\&.0リリースの実行を許可します。デフォルトでは、\fBjava\&.home\fRにあるバージョンの\fBjava\fRコマンドを使用します。\fBrmid\fRコマンドが使用するのと同じバージョンが使用されるため、そのコマンドは、ポリシー・ファイルで指定する必要はありません。2番目の権限は、\fBrmid\fRコマンドに対して、ディレクトリ\fB/files/apps/rmidcmds\fR内の任意のコマンドの実行権限を許可します。 +.sp +3番目に付与されている権限\fBExecOptionPermission\fRは、\fBrmid\fRコマンドに対して、セキュリティ・ポリシー・ファイルを\fB/files/policies/group\&.policy\fRとして定義している起動グループの開始を許可します。次の権限は、起動グループが\fBjava\&.security\&.debug property\fRを使用することを許可しています。最後の権限は、起動グループが\fBsun\&.rmi property\fR名の階層内の任意のプロパティを使用することを許可しています。 +.sp +ポリシー・ファイルを指定して\fBrmid\fRコマンドを起動するには、\fBrmid\fRのコマンド行で\fBjava\&.security\&.policy\fRプロパティを指定する必要があります。次に例を示します。 +.sp +\fBrmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fR\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +<policyClassName> +.sp +デフォルトの動作では十分な柔軟性が得られない場合、管理者は、\fBrmid\fRの起動時に、\fBcheckExecCommand\fRメソッドが所属するクラスの名前を指定して、\fBrmid\fRコマンドが実行するコマンドをチェックすることができます。 +.sp +\fBpolicyClassName\fRには、引数なしのコンストラクタを持ち、次のような\fBcheckExecCommand\fRメソッドを実装しているpublicクラスを指定します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB public void checkExecCommand(ActivationGroupDesc desc, String[] command)\fR +\fB throws SecurityException;\fR + +.fi +.if n \{\ +.RE +.\} +起動グループを開始する前に、\fBrmid\fRコマンドは、ポリシーの\fBcheckExecCommand\fRメソッドを呼び出します。このとき、起動グループの記述子と、起動グループを開始するための完全なコマンドを含む配列をそのメソッドに渡します。\fBcheckExecCommand\fRが\fBSecurityException\fRをスローすると、\fBrmid\fRコマンドはその起動グループを開始せず、オブジェクトの起動を試行している呼出し側には\fBActivationException\fRがスローされます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +none +.sp +\fBsun\&.rmi\&.activation\&.execPolicy\fRプロパティの値が\fBnone\fRの場合、\fBrmid\fRコマンドは、起動グループを開始するコマンドをまったく検証しません。 +.RE +.RE +.PP +\-log \fIdir\fR +.RS 4 +起動システム・デーモンがデータベースおよび関連情報を書き込むのに使用するディレクトリの名前を指定します。デフォルトでは、\fBrmid\fRコマンドを実行したディレクトリに、logというログ・ディレクトリが作成されます。 +.RE +.PP +\-port \fIport\fR +.RS 4 +レジストリが使用するポートを指定します。起動システム・デーモンは、このレジストリの中で、\fBjava\&.rmi\&.activation\&.ActivationSystem\fRという名前で\fBActivationSystem\fRをバインドします。ローカル・マシン上の\fBActivationSystem\fRは、次のように\fBNaming\&.lookup\fRメソッドを呼び出すことによって取得できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.rmi\&.*; \fR +\fB import java\&.rmi\&.activation\&.*;\fR +\fB \fR +\fB ActivationSystem system; system = (ActivationSystem)\fR +\fB Naming\&.lookup("//:port/java\&.rmi\&.activation\&.ActivationSystem");\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-stop +.RS 4 +\fB\-port\fRオプションによって指定されたポートの、現在の\fBrmid\fRコマンドの呼出しを停止します。ポートが指定されていない場合は、このオプションはポート1098で実行されている\fBrmid\fRの呼出しを停止します。 +.RE +.SH "環境変数" +.PP +CLASSPATH +.RS 4 +ユーザー定義クラスへのパスをシステムに指定します。ディレクトリはコロンで区切られます。例: +\fB\&.:/usr/local/java/classes\fR +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +クラス・パスの設定 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmiregistry.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmiregistry.1 new file mode 100755 index 0000000..781645e --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/rmiregistry.1 @@ -0,0 +1,116 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: rmiregistry +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "rmiregistry" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +rmiregistry \- 現在のホストの指定したポート上にリモート・オブジェクト・レジストリを開始します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry\fR [ \fIport\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIport\fR +.RS 4 +リモート・オブジェクト・レジストリを開始する現在のホスト上の\fBport\fRの数。 +.RE +.SH "説明" +.PP +\fBrmiregistry\fRコマンドは、現在のホストの指定したポート上にリモート・オブジェクト・レジストリを作成し、開始します。portの指定を省略した場合、レジストリはポート1099で開始します。\fBrmiregistry\fRコマンドに、出力機能はありません。通常、これはバックグラウンドで実行されます。次に例を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBrmiregistry &\fR + +.fi +.if n \{\ +.RE +.\} +.PP +リモート・オブジェクト・レジストリは、ブートストラップのネーム・サービスです。同一ホストのRMIサーバーが、リモート・オブジェクトを名前にバインドするために使用されます。次に、ローカルおよびリモート・ホストのクライアントはリモート・オブジェクトを検索し、リモート・メソッドの呼出しを行います。 +.PP +レジストリは、一般的に、最初のリモート・オブジェクトの位置を指定します。そこで、アプリケーションはメソッドを呼び出す必要があります。その後、そのオブジェクトはアプリケーション指定のサポートを提供し、他のオブジェクトを探します。 +.PP +\fBjava\&.rmi\&.registry\&.LocateRegistry\fRクラスのメソッドは、ローカル・ホスト、またはローカル・ホストとポートで動作するレジストリを取得するために使用されます。 +.PP +\fBjava\&.rmi\&.Naming\fRクラスのURLベース・メソッドはレジストリに対して操作を実行し、任意のホストおよびローカル・ホストでのリモート・オブジェクトの検索に使用できます。単純名(文字列)をリモート・オブジェクトにバインドし、新しい名前をリモート・オブジェクトに再バインドし(古いバインドをオーバーライド)、リモート・オブジェクトをアンバインドし、レジストリにバインドされているURLをリスト表示します。 +.SH "オプション" +.PP +\-J +.RS 4 +Javaオプションとともに使用して、\fB\-J\fRの後ろに続くオプションをJavaインタプリタに引き渡します(\fB\-J\fRとオプションの間にスペースは入れません)。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB「java\&.rmi\&.registry\&.LocateRegistry」\fR(http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/registry/LocateRegistry\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB「java\&.rmi\&.Naming class description」\fR(http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/Naming\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/schemagen.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/schemagen.1 new file mode 100755 index 0000000..a79ddbc --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/schemagen.1 @@ -0,0 +1,142 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: schemagen +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "schemagen" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +schemagen \- Javaクラス内で参照されているネームスペースごとにスキーマを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBschemagen\fR [ \fIoptions\fR ] \fIjava\-files\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIjava\-files\fR +.RS 4 +処理するJavaクラス・ファイル。 +.RE +.SH "説明" +.PP +スキーマ・ジェネレータは、Javaクラス内で参照されているネームスペースごとに1つのスキーマ・ファイルを作成します。現在、生成されるスキーマ・ファイルの名前は制御できません。スキーマ・ファイル名を制御する場合は、http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/schemagenTask\&.htmlにある +「Using SchemaGen with Ant」を参照してください +.PP +プラットフォームのbinディレクトリにある適切な\fBschemagen\fRシェル・スクリプトを使用して、スキーマ・ジェネレータを起動します。現在のスキーマ・ジェネレータは、Javaソース・ファイルとクラス・ファイルのいずれも処理できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBschemagen\&.sh Foo\&.java Bar\&.java \&.\&.\&.\fR +\fBNote: Writing schema1\&.xsd\fR + +.fi +.if n \{\ +.RE +.\} +.PP +javaファイルが他のクラスを参照している場合、それらのクラスにシステム\fBCLASSPATH\fR環境変数でアクセスできる必要があります。または、クラス・パス・オプションを指定して\fBschemagen\fRコマンド行で指定する必要があります。オプションを参照してください。参照されるファイルにアクセスできない、または参照されるファイルが指定されていない場合、スキーマの生成時にエラーが表示されます。 +.SH "オプション" +.PP +\-d \fIpath\fR +.RS 4 +\fBschemagen\fRコマンドがプロセッサ生成および\fBjavac\fR生成クラス・ファイルを配置する場所。 +.RE +.PP +\-cp \fIpath\fR +.RS 4 +\fBschemagen\fRコマンドがユーザー指定ファイルを配置する場所。 +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +\fBschemagen\fRコマンドがユーザー指定ファイルを配置する場所。 +.RE +.PP +\-encoding \fIencoding\fR +.RS 4 +\fBapt\fRまたは\fBjavac\fRコマンドの呼出しに使用するエンコーディングを指定します。 +.RE +.PP +\-episode \fIfile\fR +.RS 4 +コンパイルごとにエピソード・ファイルを生成します。 +.RE +.PP +\-version +.RS 4 +リリース情報を表示します。 +.RE +.PP +\-help +.RS 4 +ヘルプ・メッセージを表示します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Using SchemaGen with Ant + +(http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/schemagenTask\&.html) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java Architecture for XML Binding (JAXB) + +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/xml/jaxb/index\&.html) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/serialver.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/serialver.1 new file mode 100755 index 0000000..469515d --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/serialver.1 @@ -0,0 +1,129 @@ +'\" t +.\" Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: serialver +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Remote Method Invocation (RMI)ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "serialver" "1" "2013å¹´11月21日" "JDK 8" "Remote Method Invocation (RMI)" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +serialver \- 指定したクラスのシリアル・バージョンUIDを戻します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBserialver\fR [ \fIoptions\fR ] [ \fIclassnames\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIclassnames\fR +.RS 4 +\fBserialVersionUID\fRを戻すクラスです。 +.RE +.SH "説明" +.PP +\fBserialver\fRコマンドは、1つ以上のクラスの\fBserialVersionUID\fRを、展開しているクラスへコピーするのに適した形式で返します。引数なしで呼び出された場合、\fBserialver\fRコマンドは使用率行を出力します。 +.SH "オプション" +.PP +\-classpath \fIpath\-files\fR +.RS 4 +アプリケーションのクラスおよびリソースの検索パスを設定します。クラスとリソースをコロン(:)で区切ります。 +.RE +.PP +\-show +.RS 4 +簡単なユーザー・インタフェースを表示します。完全指定のクラス名を入力して、Enterキーか「表示」ボタンを押し、\fBserialVersionUID\fRを表示します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。optionには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "注意" +.PP +\fBserialver\fRコマンドは、指定されたクラスをその仮想マシン内に読み込んで初期化しますが、デフォルトではセキュリティ・マネージャの設定は行いません。信頼できないクラスとともに\fBserialver\fRコマンドを実行する場合には、次のオプションを使用してセキュリティ・マネージャを設定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-J\-Djava\&.security\&.manager\fR + +.fi +.if n \{\ +.RE +.\} +.PP +必要であれば、次のオプションを使用してセキュリティ・ポリシーを指定できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-J\-Djava\&.security\&.policy=<policy file>\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +policytool(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://docs\&.oracle\&.com/javase/8/docs/api/java/io/ObjectStreamClass\&.htmlにある +\fBjava\&.io\&.ObjectStream\fRクラス記述 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/servertool.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/servertool.1 new file mode 100755 index 0000000..bdcb783 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/servertool.1 @@ -0,0 +1,182 @@ +'\" t +.\" Copyright (c) 2001, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: servertool +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "servertool" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +servertool \- 開発者が永続サーバーを登録、登録解除、起動、停止するための使いやすいユーザー・インタフェースを提供します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBservertool\fR \-ORBInitialPort \fInameserverport\fR [ \fIoptions\fR ] [ \fIcommands \fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +commands +.RS 4 +コマンド行コマンド。コマンドを参照してください。 +.RE +.PP +\fBservertool\fR\fBservertool >\fR\fBservertool >\fR +.SH "説明" +.PP +\fBservertool\fRコマンドは、開発者が永続サーバーを登録、登録解除、起動、停止するためのコマンド行インタフェースを提供します。コマンド行コマンドを使用すると、サーバーに関する様々な統計情報を取得できます。コマンドを参照してください。 +.SH "オプション" +.PP +\-ORBInitialHost \fInameserverhost\fR +.RS 4 +このオプションは必須です。ネーム・サーバーが実行され、着信リクエストをリスニングするホスト・マシンを指定します。\fBnameserverhost\fR値は、\fBorb\fRが実行され、リクエストをリスニングしているポートを指定する必要があります。このオプションを指定しない場合、値はデフォルトで\fBlocalhost\fRに設定されます。\fBorbd\fRと\fBservertool\fRが異なるマシン上で実行されている場合は、\fBorbd\fRが実行されているホストの名前またはIPアドレスを指定する必要があります。 +.sp +\fB注意:\fR +Oracle Solarisでは、1024より小さいポート上でプロセスを開始するには、rootユーザーになる必要があります。\fBnameserverport\fR値には、1024以上のポート番号を使用することをお薦めします。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "コマンド" +.PP +\fBservertool\fRコマンドは、コマンド行コマンドを使用して、または使用せずに起動できます。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBservertool\fRの起動時にコマンドを指定しなかった場合、コマンド行ツールにコマンド入力を求める\fBservertool\fRプロンプトが表示されます: +\fBservertool >\fR。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBservertool\fRの起動時にコマンドを指定した場合、Java IDL Server Toolが起動してコマンドを実行し、終了します。 +.RE +.PP +register \-server \fIserver\-class\-name\fR \-classpath \fIclasspath\-to\-server\fR [ \-applicationName \fIapplication\-name\fR \-args \fIargs\-to\-server\fR \-vmargs \fIflags\-for\-JVM\fR ] +.RS 4 +Object Request Broker Daemon (ORBD)に新規永続サーバーを登録します。サーバーが未登録の場合、登録してアクティブ化します。このコマンドによって、\fB\-server\fRオプションで識別されるサーバーの\fBメイン\fR・クラス内でインストール・メソッドが呼び出されます。このインストール・メソッドは、\fBpublic static void install(org\&.omg\&.CORBA\&.ORB)\fRになっている必要があります。インストール・メソッドはオプションであり、開発者はデータベース・スキーマの作成など独自のサーバー・インストール動作を指定できます。 +.RE +.PP +unregister \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR +.RS 4 +サーバーIDまたはアプリケーション名で、サーバーをORBDから登録解除します。このコマンドによって、\fB\-server\fRオプションで識別されるサーバーの\fBメイン\fR・クラス内でアンインストール・メソッドが呼び出されます。 +\fBuninstall\fRメソッドは、\fBpublic static void uninstall(org\&.omg\&.CORBA\&.ORB)\fRになっている必要があります。\fBuninstall\fRメソッドはオプションであり、開発者は\fBinstall\fRメソッドの動作の取消など、独自のサーバー・アンインストール動作を指定できます。 +.RE +.PP +getserverid \-applicationName \fIapplication\-name\fR +.RS 4 +\fBapplication\-name\fR値に対応するサーバーIDを返します。 +.RE +.PP +list +.RS 4 +ORBDに登録されているすべての永続サーバーに関する情報を一覧表示します。 +.RE +.PP +listappnames +.RS 4 +現在ORBDに登録されているすべてのサーバーのアプリケーション名を一覧表示します。 +.RE +.PP +listactive +.RS 4 +ORBDによって起動され、現在実行されているすべての永続サーバーに関する情報を一覧表示します。 +.RE +.PP +locate \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR [ \-endpointType \fIendpointType\fR ] +.RS 4 +登録されたサーバーで作成したすべてのORBの特定のタイプについてエンドポイント(ポート)を検出します。サーバーが実行されていない場合、アクティブ化されます。\fBendpointType\fR値が指定されていない場合、サーバーのORBごとに関連付けられているplainタイプまたはnon\-protectedタイプのエンドポイントが返されます。 +.RE +.PP +locateperorb \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR [ \-orbid \fIORB\-name\fR ] +.RS 4 +登録されたサーバーの特定のObject Request Broker (ORB)で登録されたエンドポイント(ポート)を検出します。サーバーが実行されていない場合、アクティブ化されます。\fBorbid\fRが指定されていない場合、デフォルト値の\fB""\fRが\fBorbid\fRに割り当てられます。ORBが空文字列の\fBorbid\fRで作成されている場合、登録したポートがすべて返されます。 +.RE +.PP +orblist \-serverid \fIserver\-id\fR | \-applicationName \fIapplication\-name\fR +.RS 4 +サーバー上に定義されたORBの\fBORBId\fRを一覧表示します。\fBORBId\fRはサーバーで作成されたORBの文字列名です。サーバーが実行されていない場合、アクティブ化されます。 +.RE +.PP +shutdown \-serverid \fIserver\-id\fR | \-applicationName application\-name +.RS 4 +ORBDに登録されたアクティブなサーバーを停止します。このコマンドの実行中に、\fB\-serverid\fRパラメータまたは\fB\-applicationName\fRパラメータで指定されたクラス内に定義された\fBshutdown\fRメソッドも呼び出されてサーバー・プロセスを停止します。 +.RE +.PP +startup \-serverid \fIserver\-id\fR | \-applicationName application\-name +.RS 4 +ORBDに登録されたサーバーを起動またはアクティブ化します。サーバーが実行されていない場合、このコマンドがサーバーを起動します。サーバーがすでに実行されている場合は、エラー・メッセージが表示されます。 +.RE +.PP +help +.RS 4 +\fBservertool\fRコマンドを介してサーバーが利用できるすべてのコマンドをリストします。 +.RE +.PP +quit +.RS 4 +\fBservertool\fRコマンドを終了します。 +.RE +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +orbd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/tnameserv.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/tnameserv.1 new file mode 100755 index 0000000..20e104c --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/tnameserv.1 @@ -0,0 +1,427 @@ +'\" t +.\" Copyright (c) 1999, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: tnameserv +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java IDLおよびRMI-IIOPツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "tnameserv" "1" "2013å¹´11月21日" "JDK 8" "Java IDLおよびRMI-IIOPツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +tnameserv \- インタフェース定義言語(IDL)。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserve\fR \fB\-ORBInitialPort\fR [ \fInameserverport\fR ] +.fi +.if n \{\ +.RE +.\} +.PP +\-ORBInitialPort \fInameserverport\fR +.RS 4 +ネーミング・サービスがORBの\fBresolve_initial_references\fRメソッドと\fBlist_initial_references\fRメソッドの実装に使用するブートストラップ・プロトコルをリスニングする初期ポートです。 +.RE +.SH "説明" +.PP +Java IDLには、Object Request Broker Daemon (ORBD)が含まれます。ORBDは、ブートストラップ・サービス、一時ネーミング・サービス、永続ネーミング・サービスおよびサーバー・マネージャを含むデーモン・プロセスです。Java IDLのすべてのチュートリアルではORBDを使用していますが、一時ネーミング・サービスを使用する例では、\fBorbd\fRのかわりに\fBtnameserv\fRを使用できます。 +.PP +orbd(1)http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html +にあるまたは「Naming Service」を参照してください。 +.PP +CORBAのCOS (Common Object Services)ネーミング・サービスは、ファイル・システムがファイルに対してディレクトリ構造を提供しているのと同じように、オブジェクト参照に対してツリー構造のディレクトリを提供します。Java IDLの一時ネーム・サービスである\fBtnameserv\fRは、COSネーム・サービスの仕様を単純な形で実装したものです。 +.PP +オブジェクト参照はネームスペースに名前で格納され、オブジェクト参照と名前のペアは、それぞれネーム・バインディングと呼ばれます。ネーム・バインディングはネーミング・コンテキストに組み込むことができます。ネーミング・コンテキストはネーム・バインディングであり、ファイル・システムのサブディレクトリと同じ編成機能を持ちます。すべてのバインディングは初期ネーミング・コンテキストの下に格納されます。初期ネーミング・コンテキストは、ネームスペースの唯一の永続バインディングです。Java IDLネーミング・サービス・プロセスを停止して再起動すると、残りのネームスペースは失われます。 +.PP +アプレットまたはアプリケーションからCOSネーミング・サービスを使用するためには、そのORBがネーミング・サービスが動作しているホストのポートを知っているか、そのネーミング・サービスの初期ネーミング・コンテキスト文字列にアクセスできる必要があります。ネーム・サービスは、Java IDLのネーム・サービスでもその他のCOS準拠のネーム・サービスでもかまいません。 +.SS "ネーミング・サービスの起動" +.PP +Java IDLネーム・サービスは、ネーム・サービスを使用するアプリケーションまたはアプレットより前に起動しておく必要があります。Java IDL製品をインストールすると、Java IDLネーミング・サービスを起動するスクリプト(Oracle Solaris: +\fBtnameserv\fR)または実行可能ファイル(Windows: +\fBtnameserv\&.exe\fR)が作成されます。バックグラウンドで動作するように、ネーム・サービスを起動してください。 +.PP +特に指定しない場合、Java IDLネーミング・サービスは、ORBの\fBresolve_initial_references\fRメソッドと\fBlist_initial_references methods\fRメソッドの実装に使用するブートストラップ・プロトコルに対してポート900でリスニングします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserv \-ORBInitialPort nameserverport&\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーム・サーバー・ポートを指定しない場合、デフォルトでポート900が使用されます。Oracle Solarisソフトウェアの実行時、1024より小さいポートでプロセスを開始する場合は、rootユーザーになる必要があります。このため、1024以上のポート番号を使用することをお薦めします。1050のように別のポートを指定し、ネーム・サービスをバックグラウンドで実行するには、Solaris、LinuxまたはOS Xコマンド・シェルで次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserv \-ORBInitialPort 1050&\fR + +.fi +.if n \{\ +.RE +.\} +.PP +WindowsのMS\-DOSシステム・プロンプトでは、次のように入力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBstart tnameserv \-ORBInitialPort 1050\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーム・サーバーのクライアントには、新しいポート番号を知らせる必要があります。これを行うには、ORBオブジェクトの作成時に\fBorg\&.omg\&.CORBA\&.ORBInitialPort\fRプロパティに新しいポート番号を設定します。 +.SS "異なるホスト上でのサーバーとクライアントの実行" +.PP +Java IDLとRMI\-IIOPのほとんどのチュートリアルでは、ネーミング・サービス、サーバーおよびクライアントはすべて開発用のマシン上で実行されます。実際にデプロイメントする場合には、クライアントとサーバーを、ネーミング・サービスとは異なるホスト・マシン上で実行することが多くなります。 +.PP +クライアントとサーバーがネーム・サービスを見つけるには、クライアントとサーバーが、ネーム・サービスが実行されているポートの番号とホストを認識している必要があります。そのためには、クライアントとサーバーのファイル内の\fBorg\&.omg\&.CORBA\&.ORBInitialPort\fRプロパティと\fBorg\&.omg\&.CORBA\&.ORBInitialHost\fRプロパティをネーム・サービスが実行されているポートの番号とマシンの名前に設定します。この例は、「Getting Started Using RMI\-IIOP」 +(http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi\-iiop/rmiiiopexample\&.html)に示されています +.PP +コマンド行オプション\fB\-ORBInitialPort nameserverport#\fRと\fB\-ORBInitialHost nameserverhostname\fRを使用して、クライアントとサーバーに対してネーミング・サービスを探す場所を指定することもできます。コマンド行オプションを使用してこれを行う方法の1つの例は、http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/tutorial/jidl2machines\&.htmlの「Java IDL: The Hello World Example on Two Machines」 +を参照してください +.PP +たとえば、一時ネーム・サービス\fBtnameserv\fRが、ホスト\fBnameserverhost\fRのポート1050上で実行されているとします。さらに、クライアントがホスト\fBclienthost\fR上で実行され、サーバーはホスト\fBserverhost\fR上で実行されているとします。 +.PP +ホスト\fBnameserverhost\fR上で\fBtnameserv\fRを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBtnameserv \-ORBInitialPort 1050\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBserverhost\fR上でサーバーを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava Server \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fR + +.fi +.if n \{\ +.RE +.\} +.PP + +\fBclienthost\fR上でクライアントを起動します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava Client \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fR + +.fi +.if n \{\ +.RE +.\} +.SS "ネーミング・サービスの停止" +.PP +Java IDLネーミング・サービスを停止するには、Solaris、LinuxまたはOS Xの場合は、\fBkill\fRなどのオペレーティング・システムのコマンドを使用し、Windowsの場合は、\fB[Ctrl]+[C]\fRキーを使用します。ネーミング・サービスを明示的に停止するまでは、呼出し待機状態が続きます。サービスを終了させると、Java IDLネーム・サービスに登録されている名前は失われます。 +.SH "オプション" +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineに\fBoption\fRを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "例" +.SS "ネームスペースへのオブジェクトの追加" +.PP +次の例では、ネームスペースに名前を追加する方法を示します。このサンプル・プログラムは、このままの状態で完全に動作する一時ネーム・サービス・クライアントで、次のような単純なツリーを作成するものです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBInitial Naming Context\fR +\fB plans\fR +\fB Personal\fR +\fB calendar\fR +\fB schedule\fR + +.fi +.if n \{\ +.RE +.\} +.PP +この例で、\fBplans\fRはオブジェクト参照、\fBPersonal\fRは\fBcalendar\fRと\fBschedule\fRの2つのオブジェクト参照を含むネーミング・コンテキストです。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.util\&.Properties;\fR +\fBimport org\&.omg\&.CORBA\&.*;\fR +\fBimport org\&.omg\&.CosNaming\&.*;\fR +\fB \fR +\fBpublic class NameClient {\fR + +\fB public static void main(String args[]) {\fR + +\fB try {\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーミング・サービスの起動で、\fBnameserver\fRはポート1050で起動されました。次のコードで、このポート番号をクライアント・システムに知らせます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB Properties props = new Properties();\fR +\fB props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fR +\fB ORB orb = ORB\&.init(args, props);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、初期ネーミング・コンテキストを取得し、それを\fBctx\fRに代入します。2行目では、\fBctx\fRをダミーのオブジェクト参照\fBobjref\fRにコピーします。このobjrefには、あとで様々な名前を割り当ててネームスペースに追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NamingContext ctx =\fR +\fB NamingContextHelper\&.narrow(\fR +\fB orb\&.resolve_initial_references("NameService"));\fR +\fB NamingContext objref = ctx;\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、\fBtext\fRタイプの名前\fBplans\fRを作成し、それをダミーのオブジェクト参照にバインドします。その後、\fBrebind\fRメソッドを使用して初期ネーミング・コンテキストの下に\fBplans\fRを追加しています。\fBrebind\fRメソッドを使用すれば、\fBbind\fRメソッドを使用した場合に発生する例外を発生させずに、このプログラムを何度も繰返し実行できます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NameComponent nc1 = new NameComponent("plans", "text");\fR +\fB NameComponent[] name1 = {nc1};\fR +\fB ctx\&.rebind(name1, objref);\fR +\fB System\&.out\&.println("plans rebind successful!");\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、\fBdirectory\fRタイプの\fBPersonal\fRというネーミング・コンテキストを作成します。その結果得られるオブジェクト参照\fBctx2\fRを\fBname\fRにバインドし、初期ネーミング・コンテキストに追加します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NameComponent nc2 = new NameComponent("Personal", "directory");\fR +\fB NameComponent[] name2 = {nc2};\fR +\fB NamingContext ctx2 = ctx\&.bind_new_context(name2);\fR +\fB System\&.out\&.println("new naming context added\&.\&.");\fR + +.fi +.if n \{\ +.RE +.\} +.PP +残りのコードでは、ダミーのオブジェクト参照を\fBschedule\fRと\fBcalendar\fRという名前でネーミング・コンテキスト\fBPersonal\fR(\fBctx2\fR)にバインドします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NameComponent nc3 = new NameComponent("schedule", "text");\fR +\fB NameComponent[] name3 = {nc3};\fR +\fB ctx2\&.rebind(name3, objref);\fR +\fB System\&.out\&.println("schedule rebind successful!");\fR +\fB \fR +\fB NameComponent nc4 = new NameComponent("calender", "text");\fR +\fB NameComponent[] name4 = {nc4};\fR +\fB ctx2\&.rebind(name4, objref);\fR +\fB System\&.out\&.println("calender rebind successful!");\fR +\fB } catch (Exception e) {\fR +\fB e\&.printStackTrace(System\&.err);\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SS "ネームスペースの参照" +.PP +次のサンプル・プログラムでは、ネームスペースをブラウズする方法を示します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.util\&.Properties;\fR +\fBimport org\&.omg\&.CORBA\&.*;\fR +\fBimport org\&.omg\&.CosNaming\&.*;\fR +\fB \fR +\fBpublic class NameClientList {\fR + +\fB public static void main(String args[]) {\fR + +\fB try {\fR + +.fi +.if n \{\ +.RE +.\} +.PP +ネーミング・サービスの起動で、\fBnameserver\fRはポート1050で起動されました。次のコードで、このポート番号をクライアント・システムに知らせます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB Properties props = new Properties();\fR +\fB props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fR +\fB ORB orb = ORB\&.init(args, props);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、初期ネーミング・コンテキストを取得しています。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB NamingContext nc =\fR +\fB NamingContextHelper\&.narrow(\fR +\fB orb\&.resolve_initial_references("NameService"));\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBlist\fRメソッドは、ネーミング・コンテキストのバインディングをリストします。この場合、最大1000個までのバインディングが初期ネーミング・コンテキストから\fBBindingListHolder\fRに返されます。残りのバインディングは、\fBBindingIteratorHolder\fRに返されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB BindingListHolder bl = new BindingListHolder();\fR +\fB BindingIteratorHolder blIt= new BindingIteratorHolder();\fR +\fB nc\&.list(1000, bl, blIt);\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次のコードでは、返された\fBBindingListHolder\fRからバインディングの配列を取得します。バインディングがない場合は、プログラムが終了します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB Binding bindings[] = bl\&.value;\fR +\fB if (bindings\&.length == 0) return;\fR + +.fi +.if n \{\ +.RE +.\} +.PP +残りのコードでは、バインディングに対してループ処理を行い、名前を出力します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB for (int i=0; i < bindings\&.length; i++) {\fR +\fB \fR +\fB // get the object reference for each binding\fR +\fB org\&.omg\&.CORBA\&.Object obj = nc\&.resolve(bindings[i]\&.binding_name);\fR +\fB String objStr = orb\&.object_to_string(obj);\fR +\fB int lastIx = bindings[i]\&.binding_name\&.length\-1;\fR +\fB \fR +\fB // check to see if this is a naming context\fR +\fB if (bindings[i]\&.binding_type == BindingType\&.ncontext) {\fR +\fB System\&.out\&.println("Context: " +\fR +\fB bindings[i]\&.binding_name[lastIx]\&.id);\fR +\fB } else {\fR +\fB System\&.out\&.println("Object: " +\fR +\fB bindings[i]\&.binding_name[lastIx]\&.id);\fR +\fB }\fR +\fB }\fR +\fB } catch (Exception e) {\fR +\fB e\&.printStackTrace(System\&.err)\fR +\fB }\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +orbd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/unpack200.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/unpack200.1 new file mode 100755 index 0000000..1425257 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/unpack200.1 @@ -0,0 +1,186 @@ +'\" t +.\" Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: unpack200 +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Javaデプロイメント・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "unpack200" "1" "2013å¹´11月21日" "JDK 8" "Javaデプロイメント・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +unpack200 \- \fBpack200\fR(1)で作成されたパック・ファイルを、WebデプロイメントのためにJARファイルに変換します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBunpack200\fR [ \fIoptions\fR ] input\-file \fIJAR\-file\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIinput\-file\fR +.RS 4 +入力ファイルの名前。pack200 gzipファイルかpack200ファイルを指定できます。入力ファイルには、\fBpack200\fR(1)で作成されたJARファイルを指定することもできます(手間は\fB0\fRです)。この場合、入力ファイルの内容はPack2000マーカーで出力JARファイルにコピーされます。 +.RE +.PP +\fIJAR\-file\fR +.RS 4 +出力JARファイル名。 +.RE +.SH "説明" +.PP +\fBunpack200\fRコマンドは、\fBpack200\fR\fB(1)\fRで作成されたパック・ファイルをJARファイルに変換するネイティブ実装です。一般的な使用方法は次のとおりです。次の例では、デフォルトの\fBunpack200\fRコマンド設定で、\fBmyarchive\&.jar\fRファイルが\fBmyarchive\&.pack\&.gz\fRから作成されます。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBunpack200 myarchive\&.pack\&.gz myarchive\&.jar\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-Hvalue \-\-deflate\-hint=\fIvalue\fR +.RS 4 +JARファイル内のすべてのエントリに\fBtrue\fR、\fBfalse\fRまたは\fBkeep\fRのデフレーションを設定します。デフォルト・モードは\fBkeep\fRです。値が\fBtrue\fRまたは\fBfalse\fR場合、\fB\-\-deflate=hint\fRオプションはデフォルトの動作をオーバーライドして、出力JARファイル内のすべてのエントリのデフレーション・モードが設定されます。 +.RE +.PP +\-r \-\-remove\-pack\-file +.RS 4 +入力パック・ファイルを削除します。 +.RE +.PP +\-v \-\-verbose +.RS 4 +最小限のメッセージが表示されます。このオプションの複数の仕様には、より詳細なメッセージが表示されます。 +.RE +.PP +\-q \-\-quiet +.RS 4 +メッセージを表示せずに動作するように指定します。 +.RE +.PP +\-lfilename \-\-log\-file=\fIfilename\fR +.RS 4 +出力メッセージが記録されるログ・ファイルを指定します。 +.RE +.PP +\-? \-h \-\-help +.RS 4 +\fBunpack200\fRコマンドに関するヘルプ情報を出力します。 +.RE +.PP +\-V \-\-version +.RS 4 +\fBunpack200\fRコマンドに関するバージョン情報を出力します。 +.RE +.PP +\-J\fIoption\fR +.RS 4 +Java Virtual Machineにoptionを渡します。\fBoption\fRには、Javaアプリケーション起動ツールのリファレンス・ページに記載されているオプションを1つ指定します。たとえば、\fB\-J\-Xms48m\fRと指定すると、スタートアップ・メモリーは48MBに設定されます。java(1)を参照してください。 +.RE +.SH "注意" +.PP +このコマンドと\fBunpack\fRコマンドを混同しないでください。これらは別製品です。 +.PP +JDKに付属するJava SE API仕様との相違が見つかった場合には、仕様を優先してください。 +.SH "終了ステータス" +.PP +次の終了値が返されます: 正常終了の場合は0、エラーが発生した場合は0より大きい値。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +pack200(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jarsigner(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Compression Formats for Network Deployment」 + +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jweb/networking/compression_formats\&.html +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +「Java SE Technical Documentation」 +(http://docs\&.oracle\&.com/javase/) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/wsgen.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/wsgen.1 new file mode 100755 index 0000000..d5e51f4 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/wsgen.1 @@ -0,0 +1,215 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: wsgen +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "wsgen" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +wsgen \- Webサービスのエンドポイント実装(SEI)クラスを読取り、Webサービスのデプロイメントと呼出しに必要なすべてのアーティファクトを生成します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen\fR [ \fIoptions\fR ] \fISEI\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fISEI\fR +.RS 4 +読み取るWebサービスのエンドポイント実装クラス(SEI)です。 +.RE +.SH "説明" +.PP +\fBwsgen\fRコマンドは、JAX\-WS Webサービスで使用されるJAX\-WSポータブル・アーティファクトを生成します。このツールは、Webサービスのエンドポイント・クラスを読取り、Webサービスのデプロイメントと呼出しに必要なすべてのアーティファクトを生成します。JAXWS 2\&.1\&.1 RIでは\fBwsgen\fR +Antタスクも提供されます。 +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsgenant\&.htmlのJAX\-WS (wsgen)ページのToolsタブを参照してください。 +.PP +\fBwsgen\fRコマンドを起動するには、次を行います。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBexport JAXWS_HOME=/pathto/jaxws\-ri\fR +\fB$JAXWS_HOME/bin/wsgen\&.sh \-help\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-classpath \fIpath\fR +.RS 4 +入力クラス・ファイルの場所。 +.RE +.PP +\-cp \fIpath\fR +.RS 4 +入力クラス・ファイルの場所。 +.RE +.PP +\-d \fIdirectory\fR +.RS 4 +生成された出力ファイルを格納する場所。 +.RE +.PP +\-extension +.RS 4 +ベンダー拡張を使用可能にします。拡張を使用すると、アプリケーションの移植性が失われたり、他の実装と連携できなくなる可能性があります。 +.RE +.PP +\-help +.RS 4 +\fBwsgen\fRコマンドに関するヘルプ・メッセージを表示します。 +.RE +.PP +\-keep +.RS 4 +生成されたファイルを保存します。 +.RE +.PP +\-r \fIdirectory\fR +.RS 4 +このオプションを\fB\-wsdl\fRオプションとともに使用して、WSDLなど生成されたリソース・ファイルを配置する場所を指定します。 +.RE +.PP +\-s \fIdirectory\fR +.RS 4 +生成されたソース・ファイルを格納する場所。 +.RE +.PP +\-verbose +.RS 4 +コンパイラ・メッセージを表示します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-wsdl [ :protocol ] +.RS 4 +エンドポイントをデプロイする前に確認するWSDLファイルを生成するオプション・コマンド。WSDLファイルには、サービスを呼び出す方法、パラメータに必要な値、返されるデータ構造についてのコンピュータで読取り可能な記述が含まれます。 +.sp +デフォルトでは\fBwsgen\fRコマンドはWSDLファイルを生成しません。\fBprotocol\fR値は省略可能であり、WSDLバインディング(\fBwsdl:binding\fR)で使用するプロトコルを指定するために使用されます。有効なプロトコルは、\fBsoap1\&.1\fRと\fBXsoap1\&.2\fRです。デフォルトは\fBsoap1\&.1\fRです。\fBXsoap1\&.2\fRプロトコルは標準ではないため、\fB\-extension\fRオプションとともにのみ使用可能です。 +.RE +.PP +\-servicename \fIname\fR +.RS 4 +\fB\-wsdl\fRオプションとともにのみ使用して、WSDLで生成される特定のWSDLサービス(\fBwsdl:service\fR)名を指定します。例: +\fB\-servicename "{http://mynamespace/}MyService"\fR。 +.RE +.PP +\-portname \fIname\fR +.RS 4 +\fB\-wsdl\fRオプションとともにのみ使用して、WSDLで生成される特定のWSDLポート(\fBwsdl:port\fR)名を指定します。例: +\fB\-portname "{http://mynamespace/}MyPort"\fR。 +.RE +.SH "例" +.PP +次の例では、Stockディレクトリ内に\fB@WebService\fR注釈を持つ\fBStockService\fRのラッパー・クラスを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen \-d stock \-cp myclasspath stock\&.StockService\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、SOAP 1\&.1 WSDLおよび\fB@WebService\fR注釈を持つ\fBstock\&.StockService\fRクラスのスキーマを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen \-wsdl \-d stock \-cp myclasspath stock\&.StockService\fR + +.fi +.if n \{\ +.RE +.\} +.PP +次の例では、SOAP 1\&.2 WSDLを生成します。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsgen \-wsdl:Xsoap1\&.2 \-d stock \-cp myclasspath stock\&.StockService \fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fB注意:\fR +サービスのデプロイ時にJAXWS実行時環境でWSDLが生成されるため、開発時にWSDLを生成する必要はありません。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +wsimport(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsgenant\&.htmlの +JAX\-WS (wsgen)ページのToolsタブを参照してください。 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/wsimport.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/wsimport.1 new file mode 100755 index 0000000..9a6ba38 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/wsimport.1 @@ -0,0 +1,318 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: wsimport +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "wsimport" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +wsimport \- Webアプリケーション・アーカイブ(WAR)ファイルにパッケージできるJAX\-WSポータブル・アーティファクトを生成して、Antタスクを指定します。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsimport\fR [ \fIoptions\fR ] \fIwsdl\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +\fIwsdl\fR +.RS 4 +Webサービスを呼び出す方法、パラメータに必要な値、返されるデータ構造についてのコンピュータで読取り可能な記述が含まれまるファイルです。 +.RE +.SH "説明" +.PP +\fBwsimport\fRコマンドは、次のJAX\-WSポータブル・アーティファクトを生成します。これらのアーティファクトは、デプロイするWSDLおよびスキーマ・ドキュメントおよびエンドポイント実装とともに、WARファイルにパッケージできます。\fBwsimport\fRコマンドでは\fBwsimport\fR +Antタスクも提供されます。 +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlのWsimport Ant TaskページのToolsタブを参照してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +サービス・エンドポイント・インタフェース(SEI) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +サービス +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +例外クラスは\fBwsdl:fault\fRからマップされます(存在する場合) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非同期レスポンスBeanはレスポンス\fBwsdl:message\fRから派生します(存在する場合) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +JAXBが生成する値タイプ(スキーマのタイプからマップされたJavaクラス) +.RE +.PP +\fBwsgen\fRコマンドを起動するには、次を行います。 +.PP +\fBOracle Solaris/Linux\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB/bin/wsimport\&.sh \-help\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fBWindows\fRの場合: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\ebin\ewsimport\&.bat \-help\fR + +.fi +.if n \{\ +.RE +.\} +.SH "オプション" +.PP +\-d \fIdirectory\fR +.RS 4 +生成される出力ファイルを格納する場所を指定します。 +.RE +.PP +\-b \fIpath\fR +.RS 4 +外部JAX\-WSまたはJAXBバインディング・ファイルを指定します。\fB\-b\fRオプションで複数のJAX\-WSおよびJAXBバインディング・ファイルを指定できます。これらのファイルを使用して、パッケージ名、Bean名などをカスタマイズできます。JAX\-WSおよびJAXBバインディング・ファイルの詳細は、 +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlのWSDL CustomizationのUsers Guideタブを参照してください +.RE +.PP +\-B \fIjaxbOption\fR +.RS 4 +JAXBスキーマ・コンパイラに\fBjaxbOption\fRオプションを渡します。 +.RE +.PP +\-catalog +.RS 4 +外部エンティティ参照を解決するカタログ・ファイルを指定します。\fB\-catalog\fRオプションは、TR9401、XCatalog、OASIS XML Catalogの各形式をサポートしています。http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/catalog\-support\&.htmlの +Catalog SupportページのUsers Guideタブを参照してください。 +.RE +.PP +\-extension +.RS 4 +ベンダー拡張を使用可能にします。拡張を使用すると、アプリケーションの移植性が失われたり、他の実装と連携できなくなる可能性があります。 +.RE +.PP +\-help +.RS 4 +\fBwsimport\fRコマンドに関するヘルプ・メッセージを表示します。 +.RE +.PP +\-httpproxy: \fIhost\fR:\fIport\fR +.RS 4 +HTTPプロキシ・サーバーを指定します。デフォルトは8080です。 +.RE +.PP +\-keep +.RS 4 +生成されたファイルを保持します +.RE +.PP +\-p \fIname\fR +.RS 4 +ターゲット・パッケージ\fIname\fRを指定して、WSDLおよびスキーマ・バインディングのカスタマイズ、および仕様部で定義されたデフォルトのアルゴリズムをオーバーライドします。 +.RE +.PP +\-s \fIdirectory\fR +.RS 4 +生成されるソース・ファイルを格納する場所を指定します +.RE +.PP +\-verbose +.RS 4 +コンパイラ・メッセージを表示します。 +.RE +.PP +\-version +.RS 4 +リリース情報を出力します。 +.RE +.PP +\-wsdllocation \fIlocation\fR +.RS 4 +\fB@WebServiceClient\&.wsdlLocation\fRの値を指定します。 +.RE +.PP +\-target +.RS 4 +指定されたJAX\-WS仕様バージョンに従って、コードを生成します。バージョン2\&.0では、JAX\-WS 2\&.0仕様に準拠したコードを生成します。 +.RE +.PP +\-quiet +.RS 4 +\fBwsimport\fRコマンド出力を抑制します。 +.RE +.PP +\fB\-b\fRオプションを使用して、複数の\fBJAX\-WS\fRおよび\fBJAXB\fRバインディング・ファイルを指定できます。これらのファイルを使用して、パッケージ名やBean名など、様々なものをカスタマイズできます。\fBJAX\-WS\fRおよび\fBJAXB\fRバインディング・ファイルの詳細は、 +https://jax\-ws\&.java\&.net/nonav/2\&.1\&.2/docs/customizations\&.htmlのカスタマイズ・ドキュメントを参照してください +.SH "非標準オプション" +.PP +\-XadditionalHeaders +.RS 4 +リクエストまたはレスポンス・メッセージにバインドされないヘッダーをJavaメソッドのパラメータにマップします +.RE +.PP +\-Xauthfile \fIfile\fR +.RS 4 +認証情報を含むファイルを指定するWSDL URIです。このURIの形式は次のとおりです。 +.sp +http://\fIuser\-name\fR:\fBpassword\fR@\fIhost\-name\fR/\fIweb\-service\-name\fR>?wsdl\&. +.RE +.PP +\-Xdebug +.RS 4 +デバッグ情報を出力します +.RE +.PP +\-Xno\-addressing\-databinding +.RS 4 +W3C EndpointReferenceTypeとJavaのバインディングを有効にします。 +.RE +.PP +\-Xnocompile +.RS 4 +生成されたJavaファイルをコンパイルしません +.RE +.SH "例" +.PP +次の例では、Javaアーティファクトを生成し、\fBhttp://stockquote\&.example\&.com/quote?wsdl\fRをインポートしてアーティファクトをコンパイルします。 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBwsimport \-p stockquote http://stockquote\&.example\&.com/quote?wsdl\fR + +.fi +.if n \{\ +.RE +.\} +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +wsgen(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlの +Wsimport Ant TaskページのToolsタブ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/catalog\-support\&.htmlの +Catalog SupportページのUsers Guideタブ +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jax\-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.htmlの +WSDL CustomizationページのUsers Guideタブ +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/xjc.1 b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/xjc.1 new file mode 100755 index 0000000..e9a04e0 --- /dev/null +++ b/jdk-1.8.0.281/man/ja_JP.UTF-8/man1/xjc.1 @@ -0,0 +1,325 @@ +'\" t +.\" Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: xjc +.\" Language: Japanese +.\" Date: 2013å¹´11月21日 +.\" SectDesc: Java Webサービス・ツール +.\" Software: JDK 8 +.\" Arch: 汎用 +.\" Part Number: E58104-01 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "xjc" "1" "2013å¹´11月21日" "JDK 8" "Java Webサービス・ツール" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "名前" +xjc \- XMLスキーマ・ファイルを完全注釈付きのJavaクラスにコンパイルします。 +.SH "概要" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBxjc\fR [ \fIoptions\fR ] \fBschema\fR \fIfile/URL/dir/jar\fR \&.\&.\&. [\fB\-b\fR \fIbindinfo\fR ] \&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +コマンド行オプション。オプションを参照してください。 +.RE +.PP +schema \fIfile/URL/dir/jar \&.\&.\&.\fR +.RS 4 +XMLスキーマ・ファイルの場所。\fBdir\fRが指定されている場合は、すべてのスキーマ・ファイルがコンパイルされます。\fBjar\fRが指定されている場合は、\fB/META\-INF/sun\-jaxb\&.episode\fRバインディング・ファイルがコンパイルされます。 +.RE +.PP +\-b \fIbindinfo\fR +.RS 4 +バインディング・ファイルの場所。 +.RE +.SH "説明" +.PP +プラットフォームのbinディレクトリにある適切な\fBxjc\fRシェル・スクリプトを使用して、バインディング・コンパイラを起動します。バインディング・コンパイラを実行するAntタスクもあります。http://jaxb\&.java\&.net/nonav/2\&.1\&.3/docs/xjcTask\&.htmlの +Using the XJC with Antを参照してください +.SH "オプション" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非標準オプションも参照してください +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +非推奨で削除されたオプションも参照してください +.RE +.PP +\-nv +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、ソース・スキーマを処理する前に厳密な検証を実行します。このオプションを使用すると、厳密なスキーマ検証か無効になります。これは、バインディング・コンパイラが検証を一切実行しないということではありません。より厳密でない検証を実行するということです。 +.RE +.PP +\-extension +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、JAXB仕様のCompatibilityの章で説明されているルールを厳密に強制します。付録E\&.2には、JAXB v1\&.0で完全にはサポートされていない一連のW3C XMLスキーマ機能が定義されています。場合によっては、このスイッチで有効になる\fB\-extension\fRモードでそれらの機能が使用できる場合があります。また、デフォルトの厳密なモードでは、仕様に定義されているバインディング・カスタマイズのみが使用できます。\fB\-extension\fRスイッチを指定すれば、JAXB Vendor Extensionを使用できます。 +.RE +.PP +\-b \fIfile\fR +.RS 4 +処理する外部バインディング・ファイルを1つまたは複数指定します。バインディング・ファイルごとに\fB\-b\fRスイッチを指定する必要があります。外部バインディング・ファイルの構文は柔軟です。複数のスキーマのカスタマイズが含まれる1つのバインディング・ファイルを使用したり、それらのカスタマイズを複数のバインディング・ファイルに分割したりできます。次に例を示します。\fBxjc schema1\&.xsd schema2\&.xsd schema3\&.xsd \-b bindings123\&.xjb\fR +\fBxjc schema1\&.xsd schema2\&.xsd schema3\&.xsd \-b bindings1\&.xjb \-b bindings2\&.xjb \-b bindings3\&.xjb\fRまた、コマンドラインにスキーマ・ファイルとバインディング・ファイルを指定する順番は任意です。 +.RE +.PP +\-d \fIdir\fR +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、Javaコンテンツ・クラスを現在のディレクトリに生成します。このオプションを使用すると、代替出力ディレクトリを指定できます。出力ディレクトリはすでに存在している必要があります。XJCバインディング・コンパイラでは作成されません。 +.RE +.PP +\-p \fIpkg\fR +.RS 4 +このコマンドライン・オプションでターゲット・パッケージを指定した場合、その指定内容は、パッケージ名に対するすべてのバインディング・カスタマイズや、仕様で規定されているデフォルトのパッケージ名アルゴリズムよりも優先されます。 +.RE +.PP +\-httpproxy \fIproxy\fR +.RS 4 +\fI[user[:password]@]proxyHost[:proxyPort]\fR形式でHTTPまたはHTTPSプロキシを指定します。古い\fB\-host\fRおよび\fB\-port\fRオプションは、下位互換性のために引き続きRIでサポートされますが、非推奨となりました。このオプションで指定されたパスワードは、topコマンドを使用する他のユーザーが表示できる引数です。セキュリティを高めるには、\fB\-httpproxyfile\fRを使用してください。 +.RE +.PP +\-httpproxyfile file +.RS 4 +ファイルを使用して、HTTPまたはHTTPSプロキシを指定します。形式は\fB\-httpproxy\fRオプションと同じですが、このファイル内に指定されたパスワードを他のユーザーが表示することはできません。 +.RE +.PP +\-classpath arg +.RS 4 +\fIjxb:javaType\fRおよびxjc:\fIsuperClass\fRカスタマイズが使用するクライアント・アプリケーションのクラス・ファイルの検索場所を指定します。 +.RE +.PP +\-catalog file +.RS 4 +外部エンティティ参照を解決するカタログ・ファイルを指定します。TR9401、XCatalogおよびOASIS XML Catalogの各形式がサポートされます。http://xerces\&.apache\&.org/xml\-commons/components/resolver/resolver\-article\&.htmlの +XML Entity and URI Resolversを参照してください +.RE +.PP +\-readOnly +.RS 4 +デフォルトでは、XJCバインディング・コンパイラは、生成するJavaソース・ファイルを書込みから保護しません。このオプションを使用すると、XJCバインディング・コンパイラは生成されるJavaソースを強制的に読取り専用にします。 +.RE +.PP +\-npa +.RS 4 +\fB**/package\-info\&.java\fRへのパッケージ・レベルの注釈の生成を抑制します。このスイッチを使用して生成するコードでは、これらの注釈が他の生成済クラスに内部化されます。 +.RE +.PP +\-no\-header +.RS 4 +多少のメモとタイムスタンプを含むファイル・ヘッダー・コメントの生成を抑制します。これを使用すると、生成されたコードと\fBdiff\fRコマンドとの互換性がより強くなります。 +.RE +.PP +\-target 2\&.0 +.RS 4 +JAXB 2\&.1機能に依存するコードを生成しないようにします。これにより、生成されたコードをJAXB 2\&.0ランタイム環境(Java SE 6など)で実行できるようになります。 +.RE +.PP +\-xmlschema +.RS 4 +入力スキーマをW3C XMLスキーマとして扱います(デフォルト)。このスイッチを指定しない場合、入力スキーマはW3C XMLスキーマと同じように扱われます。 +.RE +.PP +\-relaxing +.RS 4 +入力スキーマをRELAX NGとして扱います(試験的および未サポート)。RELAX NGスキーマのサポートはJAXB Vendor Extensionとして提供されています。 +.RE +.PP +\-relaxing\-compact +.RS 4 +入力スキーマをRELAX NG圧縮構文として処理します(試験的および未サポート)。RELAX NGスキーマのサポートはJAXB Vendor Extensionとして提供されています。 +.RE +.PP +\-dtd +.RS 4 +入力スキーマをXML DTDとして扱います(試験的および未サポート)。RELAX NGスキーマのサポートはJAXB Vendor Extensionとして提供されています。 +.RE +.PP +\-wsdl +.RS 4 +入力をWSDLとして扱い、その内部のスキーマをコンパイルします(試験的および未サポート)。 +.RE +.PP +\-quiet +.RS 4 +進捗情報や警告など、コンパイラの出力を抑制します。 +.RE +.PP +\-verbose +.RS 4 +情報メッセージを出力したり特定のエラー発生時にスタック・トレースを表示したりするなど、きわめて冗長になります。 +.RE +.PP +\-help +.RS 4 +コンパイラ・スイッチのサマリーを表示します。 +.RE +.PP +\-version +.RS 4 +コンパイラのバージョン情報を表示します。 +.RE +.PP +\fIschema file/URL/dir\fR +.RS 4 +コンパイル対象となる1つまたは複数のスキーマ・ファイルを指定します。ディレクトリを指定する場合、\fBxjc\fRコマンドはすべてのスキーマ・ファイルをスキャンしてコンパイルします。 +.RE +.SS "非標準オプション" +.PP +\-XLocator +.RS 4 +生成されたコードでは、非整列化の後にJava Beanインスタンスに含まれるソースXMLに関するSAX Locator情報が公開されます。 +.RE +.PP +\-Xsync\-methods +.RS 4 +生成されたすべてのメソッド・シグニチャに\fBsynchronized\fRキーワードが含められます。 +.RE +.PP +\-mark\-generated +.RS 4 +生成されたコードに注釈\fB@javax\&.annotation\&.Generated\fRを付けます。 +.RE +.PP +\-episode file +.RS 4 +コンパイルごとに指定されたエピソード・ファイルを生成します。 +.RE +.SS "非推奨で削除されたオプション" +.PP +\-host & \-port +.RS 4 +これらのオプションは\fB\-httpproxy\fRオプションで置き換えられました。これらのオプションは、後方互換性を確保するためにサポートされますが、ドキュメントには記載されず、将来のリリースで削除される可能性もあります。 +.RE +.PP +\-use\-runtime +.RS 4 +JAXB 2\&.0仕様では、移植性のあるランタイム環境が定義されたため、JAXB RIが\fB**/impl/runtime \fRパッケージを生成する必要がなくなりました。このため、このスイッチは不要となり、削除されました。 +.RE +.PP +\-source +.RS 4 +\fB\-source\fR互換性スイッチは、JAXB 2\&.0の最初のEarly Access版で導入されました。このスイッチはJAXB 2\&.0の今後のリリースから削除されます。1\&.0\&.xコードを生成する必要がある場合は、1\&.0\&.xコード・ベースのインストールを使用してください。 +.RE +.SH "コンパイラの制限" +.PP +通常は、関連するすべてのスキーマを、同じバインディング・コンパイラ・スイッチを指定して1つの単位としてコンパイルするのが最も安全です。\fBxjc\fRコマンドの実行時には、次の制限リストに留意してください。これらの問題のほとんどは、\fBxjc\fRコマンドを何度か呼び出して複数のスキーマをコンパイルする場合にのみ当てはまります。 +.PP +複数のスキーマを同時にコンパイルする場合は、ターゲットのJavaパッケージ名に次の優先順位のルールが適用されることに注意してください。 +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +\fB\-p\fRオプションが最も優先されます。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +\fIjaxb:package\fRのカスタマイズ。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +\fBtargetNamespace\fRが宣言されている場合は、\fBt\fR\fBargetNamespace\fRを仕様で定義されているJavaパッケージ名のアルゴリズムに適用します。 +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +\fBtargetNamespace\fRが宣言されていない場合は、\fBgenerated\fRという名前のハードコードされたパッケージを使用します。 +.RE +.PP +1つのネームスペースが複数の\fIjaxb:schemaBindings\fRを持つことはできないため、異なるJavaパッケージにコンパイラされる同一ターゲット・ネームスペースが2つのスキーマを持つことはできません。 +.PP +同じJavaパッケージにコンパイラされるスキーマはすべて、同時にXJCバインディング・コンパイラに送信される必要があります。別々にコンパイルすると、予想どおりに機能しません。 +.PP +複数のスキーマ・ファイルにまたがる要素置換グループは、同時にコンパイルする必要があります。 +.SH "関連項目" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/xjc\&.htmlの +Binding Compiler (xjc) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +http://www\&.oracle\&.com/technetwork/articles/javase/index\-140168\&.htmlの +Java Architecture for XML Binding (JAXB) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/appletviewer.1 b/jdk-1.8.0.281/man/man1/appletviewer.1 new file mode 100755 index 0000000..adfb3b0 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/appletviewer.1 @@ -0,0 +1,69 @@ +'\" t +.\" Copyright (c) 1995, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Basic Tools +.\" Title: appletviewer.1 +.\" +.if n .pl 99999 +.TH appletviewer 1 "21 November 2013" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +appletviewer \- Runs applets outside of a web browser\&. +.SH SYNOPSIS +.sp +.nf + +\fBappletviewer\fR [\fIoptions\fR] \fIurl\fR\&.\&.\&. +.fi +.sp +.TP +\fIoptions\fR +The command-line options separated by spaces\&. See Options\&. +.TP +\fIurl\fR +The location of the documents or resources to be displayed\&. You can specify multiple URLs separated by spaces\&. +.SH DESCRIPTION +The \f3appletviewer\fR command connects to the documents or resources designated by \fIurls\fR and displays each applet referenced by the documents in its own window\&. If the documents referred to by urls do not reference any applets with the \f3OBJECT\fR, \f3EMBED\fR, or \f3APPLET\fR tag, then the \f3appletviewer\fR command does nothing\&. For details about the HTML tags that the \f3appletviewer\fR command supports, see AppletViewer Tags at http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/appletviewertags\&.html +.PP +The \f3appletviewer\fR command requires encoded URLs according to the escaping mechanism defined in RFC2396\&. Only encoded URLs are supported\&. However, file names must be unencoded, as specified in RFC2396\&. +.PP +\fINote:\fR The \f3appletviewer\fR command is intended for development purposes only\&. For more information, see About Sample/Test Applications and Code at http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/aboutCodeSamples\&.html +.SH OPTIONS +.TP +-debug +.br +Starts the Applet Viewer in the Java debugger with the \f3jdb\fR command to debug the applets in the document\&. +.TP +-encoding \fIencoding-name\fR +.br +Specifies the input HTML file encoding name\&. +.TP +-J\fIjavaoption\fR +.br +Passes the string \f3javaoption\fR as a single argument to the Java interpreter, which runs the Applet Viewer\&. The argument should not contain spaces\&. Multiple argument words must all begin with the prefix \f3-J\fR\&. This is useful for adjusting the compiler\&'s execution environment or memory usage\&. +.PP +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/extcheck.1 b/jdk-1.8.0.281/man/man1/extcheck.1 new file mode 100755 index 0000000..1308bb5 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/extcheck.1 @@ -0,0 +1,70 @@ +'\" t +.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Basic Tools +.\" Title: extcheck.1 +.\" +.if n .pl 99999 +.TH extcheck 1 "21 November 2013" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +extcheck \- Detects version conflicts between a target Java Archive (JAR) file and currently installed extension JAR files\&. +.SH SYNOPSIS +.sp +.nf + +\fBextcheck\fR [\fIoptions\fR] \fItargetfile\&.jar\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fItargetfile\&.jar\fR +The target JAR file against which the currently installed extension JAR files are compared to detect version conflicts\&. +.SH DESCRIPTION +The \f3extcheck\fR command checks a specified JAR file for title and version conflicts with any extensions installed in the Java SE SDK\&. Before installing an extension, you can use this utility to see whether the same or a more recent version of the extension is already installed\&. +.PP +The \f3extcheck\fR command compares the Specification-title and Specification-version headers in the manifest of the \f3targetfile\&.jar\fR file against the corresponding headers in all JAR files currently installed in the extension directory\&. By default, the extension directory is \f3jre/lib/ext\fR on Oracle Solaris and \f3\ejre\elib\eext\fR on Windows\&. The \f3extcheck\fR command compares version numbers in the same way as the \f3java\&.lang\&.Package\&.isCompatibleWith\fR method\&. +.PP +If no conflict is detected, then the return code is 0\&. +.PP +If the manifest of any JAR file in the extensions directory has the same \f3Specification-title\fR and the same or a newer \f3Specification-version\fR number, then a non-zero error code is returned\&. A non-zero error code is also returned when \f3targetfile\&.jar\fR does not have the \f3Specification-title\fR or \f3Specification-version\fR attributes in its manifest file\&. +.SH OPTIONS +.TP +-verbose +.br +Lists JAR files in the extension directory as they are checked\&. Additionally, manifest attributes of the target JAR file and any conflicting JAR files are also reported\&. +.TP +-J\fIoption\fR +.br +Passes \fIoption\fR to the Java Virtual Machine (JVM), where option is one of the options described on the reference page for the Java launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jar(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/idlj.1 b/jdk-1.8.0.281/man/man1/idlj.1 new file mode 100755 index 0000000..23f0054 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/idlj.1 @@ -0,0 +1,547 @@ +'\" t +.\" Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java IDL and RMI-IIOP Tools +.\" Title: idlj.1 +.\" +.if n .pl 99999 +.TH idlj 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +idlj \- Generates Java bindings for a specified Interface Definition Language (IDL) file\&. +.SH SYNOPSIS +.sp +.nf + +\fBidlj\fR [ \fIoptions\fR ] \fIidlfile\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. Options can appear in any order, but must precede the \f3idlfile\fR\&. +.TP +\fIidlfile\fR +The name of a file that contains Interface Definition Language (IDL) definitions\&. +.SH DESCRIPTION +The IDL-to-Java Compiler generates the Java bindings for a specified IDL file\&. For binding details, see Java IDL: IDL to Java Language Mapping at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.html +.PP +Some earlier releases of the IDL-to-Java compiler were named \f3idltojava\fR\&. +.SS EMIT\ CLIENT\ AND\ SERVER\ BINDINGS +The following \f3idlj\fR command generates an IDL file named \f3My\&.idl\fR with client-side bindings\&. +.sp +.nf +\f3idlj My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +The previous syntax is equivalent to the following: +.sp +.nf +\f3idlj \-fclient My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +The next example generates the server-side bindings, and includes the client-side bindings plus the skeleton, all of which are POA (Inheritance Model)\&. +.sp +.nf +\f3idlg \-fserver My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +If you want to generate both client and server-side bindings, then use one of the following (equivalent) commands: +.sp +.nf +\f3idlj \-fclient \-fserver My\&.idl\fP +.fi +.nf +\f3idlj \-fall My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +There are two possible server-side models: the Portal Servant Inheritance Model and the Tie Model\&. See Tie Delegation Model\&. +.PP +\f3Portable Servant Inheritance Model\fR\&. The default server-side model is the Portable Servant Inheritance Model\&. Given an interface \f3My\fR defined in \f3My\&.idl\fR, the file \f3MyPOA\&.java\fR is generated\&. You must provide the implementation for the \f3My\fR interface, and the \f3My\fR interface must inherit from the \f3MyPOA\fR class\&. \f3MyPOA\&.java\fR is a stream-based skeleton that extends the \f3org\&.omg\&.PortableServer\&.Servant\fR class at http://docs\&.oracle\&.com/javase/8/docs/api/org/omg/PortableServer/Servant\&.html The \f3My\fR interface implements the \f3callHandler\fR interface and the operations interface associated with the IDL interface the skeleton implements\&.The \f3PortableServer\fR module for the Portable Object Adapter (POA) defines the native \f3Servant\fR type\&. See Portable Object Adapter (POA) at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/POA\&.html In the Java programming language, the \f3Servant\fR type is mapped to the Java \f3org\&.omg\&.PortableServer\&.Servant\fR class\&. It serves as the base class for all POA servant implementations and provides a number of methods that can be called by the application programmer, and methods that are called by the POA and that can be overridden by the user to control aspects of servant behavior\&.Another option for the Inheritance Model is to use the \f3-oldImplBase\fR flag to generate server-side bindings that are compatible with releases of the Java programming language before Java SE 1\&.4\&. The -\f3oldImplBase\fR flag is nonstandard, and these APIs are deprecated\&. You would use this flag only for compatibility with existing servers written in Java SE 1\&.3\&. In that case, you would need to modify an existing make file to add the \f3-oldImplBase\fR flag to the \f3idlj\fR compiler\&. Otherwise POA-based server-side mappings are generated\&. To generate server-side bindings that are backward compatible, do the following: +.sp +.nf +\f3idlj \-fclient \-fserver \-oldImplBase My\&.idl\fP +.fi +.nf +\f3idlj \-fall \-oldImplBase My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +Given an interface \f3My\fR defined in \f3My\&.idl\fR, the file \f3_MyImplBase\&.java\fR is generated\&. You must provide the implementation for the \f3My\fR interface, and the \f3My\fR interface must inherit from the \f3_MyImplBase\fR class\&. +.PP +\f3Tie Delegation Model\fR\&. The other server-side model is called the Tie Model\&. This is a delegation model\&. Because it is not possible to generate ties and skeletons at the same time, they must be generated separately\&. The following commands generate the bindings for the Tie Model: +.sp +.nf +\f3idlj \-fall My\&.idl\fP +.fi +.nf +\f3idlj \-fallTIE My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +For the \f3My\fR interface, the second command generates \f3MyPOATie\&.java\fR\&. The constructor to the \f3MyPOATie\fR class takes a delegate\&. In this example, using the default POA model, the constructor also needs a POA\&. You must provide the implementation for the delegate, but it does not have to inherit from any other class, only the interface \f3MyOperations\fR\&. To use it with the ORB, you must wrap your implementation within the \f3MyPOATie\fR class, for example: +.sp +.nf +\f3ORB orb = ORB\&.init(args, System\&.getProperties());\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// Get reference to rootpoa & activate the POAManager\fP +.fi +.nf +\f3POA rootpoa = (POA)orb\&.resolve_initial_references("RootPOA");\fP +.fi +.nf +\f3rootpoa\&.the_POAManager()\&.activate();\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// create servant and register it with the ORB\fP +.fi +.nf +\f3MyServant myDelegate = new MyServant();\fP +.fi +.nf +\f3myDelegate\&.setORB(orb); \fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// create a tie, with servant being the delegate\&.\fP +.fi +.nf +\f3MyPOATie tie = new MyPOATie(myDelegate, rootpoa);\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// obtain the objectRef for the tie\fP +.fi +.nf +\f3My ref = tie\&._this(orb);\fP +.fi +.nf +\f3\fR +.fi +.sp +You might want to use the Tie model instead of the typical Inheritance model when your implementation must inherit from some other implementation\&. Java allows any number of interface inheritance, but there is only one slot for class inheritance\&. If you use the inheritance model, then that slot is used up\&. With the Tie Model, that slot is freed up for your own use\&. The drawback is that it introduces a level of indirection: one extra method call occurs when a method is called\&. +.PP +For server-side generation, Tie model bindings that are compatible with versions of the IDL to Java language mapping in versions earlier than Java SE 1\&.4\&. +.sp +.nf +\f3idlj \-oldImplBase \-fall My\&.idl\fP +.fi +.nf +\f3idlj \-oldImplBase \-fallTIE My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +For the \f3My\fR interface, the this generates \f3My_Tie\&.java\fR\&. The constructor to the \f3My_Tie\fR class takes an \f3impl\fR object\&. You must provide the implementation for \f3impl\fR, but it does not have to inherit from any other class, only the interface \f3HelloOperations\fR\&. But to use it with the ORB, you must wrap your implementation within \f3My_Tie\fR, for example: +.sp +.nf +\f3ORB orb = ORB\&.init(args, System\&.getProperties());\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// create servant and register it with the ORB\fP +.fi +.nf +\f3MyServant myDelegate = new MyServant();\fP +.fi +.nf +\f3myDelegate\&.setORB(orb); \fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// create a tie, with servant being the delegate\&.\fP +.fi +.nf +\f3MyPOATie tie = new MyPOATie(myDelegate);\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3// obtain the objectRef for the tie\fP +.fi +.nf +\f3My ref = tie\&._this(orb);\fP +.fi +.nf +\f3\fR +.fi +.sp +.SS SPECIFY\ ALTERNATE\ LOCATIONS\ FOR\ EMITTED\ FILES +If you want to direct the emitted files to a directory other than the current directory, then call the compiler this way: \f3i\fR\f3dlj -td /altdir My\&.idl\fR\&. +.PP +For the \f3My\fR interface, the bindings are emitted to \f3/altdir/My\&.java\fR, etc\&., instead of \f3\&./My\&.java\fR\&. +.SS SPECIFY\ ALTERNATE\ LOCATIONS\ FOR\ INCLUDE\ FILES +If the \f3My\&.idl\fR file includes another \f3idl\fR file, \f3MyOther\&.idl\fR, then the compiler assumes that the \f3MyOther\&.idl\fR file resides in the local directory\&. If it resides in \f3/includes\fR, for example, then you call the compiler with the following command: +.sp +.nf +\f3idlj \-i /includes My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +If \f3My\&.idl\fR also included \f3Another\&.idl\fR that resided in \f3/moreIncludes\fR, for example, then you call the compiler with the following command: +.sp +.nf +\f3idlj \-i /includes \-i /moreIncludes My\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +Because this form of \f3include\fR can become long, another way to indicate to the compiler where to search for included files is provided\&. This technique is similar to the idea of an environment variable\&. Create a file named idl\&.config in a directory that is listed in your \f3CLASSPATH\fR variable\&. Inside of \f3idl\&.config\fR, provide a line with the following form: +.sp +.nf +\f3includes=/includes;/moreIncludes\fP +.fi +.nf +\f3\fR +.fi +.sp +The compiler will find this file and read in the includes list\&. Note that in this example the separator character between the two directories is a semicolon (;)\&. This separator character is platform dependent\&. On the Windows platform, use a semicolon, on the Unix platform, use a colon, and so on\&. +.SS EMIT\ BINDINGS\ FOR\ INCLUDE\ FILES +By default, only those interfaces, structures, and so on, that are defined in the \f3idl\fR file on the command line have Java bindings generated for them\&. The types defined in included files are not generated\&. For example, assume the following two \f3idl\fR files: +.sp +.nf +\f3My\&.idl file:\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3#include <MyOther\&.idl>\fP +.fi +.nf +\f3interface My\fP +.fi +.nf +\f3{\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3MyOther\&.idl file:\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3interface MyOther\fP +.fi +.nf +\f3{\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fR +.fi +.sp +There is a caveat to the default rule\&. Any \f3#include\fR statements that appear at the global scope are treated as described\&. These \f3#include\fR statements can be thought of as import statements\&. The \f3#include\fR statements that appear within an enclosed scope are treated as true \f3#include\fR statements, which means that the code within the included file is treated as though it appeared in the original file and, therefore, Java bindings are emitted for it\&. Here is an example: +.sp +.nf +\f3My\&.idl file:\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3#include <MyOther\&.idl>\fP +.fi +.nf +\f3interface My\fP +.fi +.nf +\f3{\fP +.fi +.nf +\f3 #include <Embedded\&.idl>\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3MyOther\&.idl file:\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3interface MyOther\fP +.fi +.nf +\f3{\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3Embedded\&.idl\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3enum E {one, two, three};\fP +.fi +.nf +\f3\fR +.fi +.sp +Run\f3idlj My\&.idl\fRto generate the following list of Java files\&. Notice that \f3MyOther\&.java\fR is not generated because it is defined in an import-like \f3#include\fR\&. But \f3E\&.java\fR was generated because it was defined in a true \f3#include\fR\&. Notice that because the \f3Embedded\&.idl\fR file is included within the scope of the interface \f3My\fR, it appears within the scope of \f3My\fR (in \f3MyPackage\fR)\&. If the \f3-emitAll\fR flag had been used, then all types in all included files would have been emitted\&. +.sp +.nf +\f3\&./MyHolder\&.java\fP +.fi +.nf +\f3\&./MyHelper\&.java\fP +.fi +.nf +\f3\&./_MyStub\&.java\fP +.fi +.nf +\f3\&./MyPackage\fP +.fi +.nf +\f3\&./MyPackage/EHolder\&.java\fP +.fi +.nf +\f3\&./MyPackage/EHelper\&.java\fP +.fi +.nf +\f3\&./MyPackage/E\&.java\fP +.fi +.nf +\f3\&./My\&.java\fP +.fi +.nf +\f3\fR +.fi +.sp +.SS INSERT\ PACKAGE\ PREFIXES +Suppose that you work for a company named ABC that has constructed the following IDL file: +.sp +.nf +\f3Widgets\&.idl file:\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3module Widgets\fP +.fi +.nf +\f3{\fP +.fi +.nf +\f3 interface W1 {\&.\&.\&.};\fP +.fi +.nf +\f3 interface W2 {\&.\&.\&.};\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fR +.fi +.sp +If you run this file through the IDL-to-Java compiler, then the Java bindings for W1 and W2 are placed within the \f3Widgets\fR package\&. There is an industry convention that states that a company\&'s packages should reside within a package named \f3com\&.<company name>\fR\&. To follow this convention, the package name should be \f3com\&.abc\&.Widgets\fR\&. To place this package prefix onto the Widgets module, execute the following: +.sp +.nf +\f3idlj \-pkgPrefix Widgets com\&.abc Widgets\&.idl\fP +.fi +.nf +\f3\fR +.fi +.sp +If you have an IDL file that includes Widgets\&.idl, then the \f3-pkgPrefix\fR flag must appear in that command also\&. If it does not, then your IDL file will be looking for a \f3Widgets\fR package rather than a \f3com\&.abc\&.Widgets\fR package\&. +.PP +If you have a number of these packages that require prefixes, then it might be easier to place them into the idl\&.config file described previously\&. Each package prefix line should be of the form: \f3PkgPrefix\&.<type>=<prefix>\fR\&. The line for the previous example would be \f3PkgPrefix\&.Widgets=com\&.abc\fR\&. This option does not affect the Repository ID\&. +.SS DEFINE\ SYMBOLS\ BEFORE\ COMPILATION +You might need to define a symbol for compilation that is not defined within the IDL file, perhaps to include debugging code in the bindings\&. The command \f3idlj -d MYDEF My\&.idl\fRis equivalent to putting the line \f3#define MYDEF\fR inside My\&.idl\&. +.SS PRESERVE\ PREEXISTING\ BINDINGS +If the Java binding files already exist, then the \f3-keep\fR flag keeps the compiler from overwriting them\&. The default is to generate all files without considering that they already exist\&. If you have customized those files (which you should not do unless you are very comfortable with their contents), then the \f3-keep\fR option is very useful\&. The command \f3idlj -keep My\&.idl\fR emits all client-side bindings that do not already exist\&. +.SS VIEW\ COMPILATION\ PROGRESS +The IDL-to-Java compiler generates status messages as it progresses through its phases of execution\&. Use the \f3-v\fR option to activate the verbose mode: \f3idlj -v My\&.idl\fR\&. +.PP +By default the compiler does not operate in verbose mode +.SS DISPLAY\ VERSION\ INFORMATION +To display the build version of the IDL-to-Java compiler, specify the \f3-version\fR option on the command-line: \f3idlj -version\fR\&. +.PP +Version information also appears within the bindings generated by the compiler\&. Any additional options appearing on the command-line are ignored\&. +.SH OPTIONS +.TP +-d \fIsymbol\fR +.br +This is equivalent to the following line in an IDL file: +.sp +.nf +\f3#define \fIsymbol\fR\fP +.fi +.nf +\f3\fR +.fi +.sp + +.TP +-demitAll +.br +Emit all types, including those found in \f3#include\fR files\&. +.TP +-fside +.br +Defines what bindings to emit\&. The \f3side\fR parameter can be \f3client\fR, \f3server\fR, \f3serverTIE\fR, \f3all\fR, or \f3allTIE\fR\&. The \f3-fserverTIE\fR and \f3-fallTIE\fR options cause delegate model skeletons to be emitted\&. Defaults to \f3-fclient\fR when the flag is not specified\&. +.TP +-i \fIinclude-path\fR +.br +By default, the current directory is scanned for included files\&. This option adds another directory\&. +.TP +-i \fIkeep\fR +.br +If a file to be generated already exists, then do not overwrite it\&. By default it is overwritten\&. +.TP +-noWarn +.br +Suppress warning messages\&. +.TP +-oldImplBase +.br +Generates skeletons compatible with pre-1\&.4 JDK ORBs\&. By default, the POA Inheritance Model server-side bindings are generated\&. This option provides backward-compatibility with earlier releases of the Java programming language by generating server-side bindings that are \f3ImplBase\fR Inheritance Model classes\&. +.TP +-pkgPrefix \fItype\fR\fIprefix\fR +.br +Wherever \f3type\fR is encountered at file scope, prefix the generated Java package name with \f3prefix\fR for all files generated for that type\&. The type is the simple name of either a top-level module, or an IDL type defined outside of any module\&. +.TP +-pkgTranslate \fItype\fR\fIpackage\fR +.br +Whenever the module name type is encountered in an identifier, replace it in the identifier with package for all files in the generated Java package\&. Note that \f3pkgPrefix\fR changes are made first\&. The type value is the simple name of either a top-level module, or an IDL type defined outside of any module and must match the full package name exactly\&. + +If more than one translation matches an identifier, then the longest match is chosen as shown in the following example: + +\fICommand\fR: +.sp +.nf +\f3pkgTranslate type pkg \-pkgTranslate type2\&.baz pkg2\&.fizz\fP +.fi +.nf +\f3\fR +.fi +.sp + + +\fIResulting Translation\fR: +.sp +.nf +\f3type => pkg\fP +.fi +.nf +\f3type\&.ext => pkg\&.ext\fP +.fi +.nf +\f3type\&.baz => pkg2\&.fizz\fP +.fi +.nf +\f3type2\&.baz\&.pkg => pkg2\&.fizz\&.pkg\fP +.fi +.nf +\f3\fR +.fi +.sp + + +The following package names \f3org\fR, \f3org\fR\&.o\f3mg\fR, or any subpackages of \f3org\&.omg\fR cannot be translated\&. Any attempt to translate these packages results in uncompilable code, and the use of these packages as the first argument after \f3-pkgTranslate\fR is treated as an error\&. +.TP +-skeletonName \fIxxx%yyy\fR +.br +Use \f3xxx%yyy\fR as the pattern for naming the skeleton\&. The defaults are: \f3%POA\fR for the \f3POA\fR base class (\f3-fserver\fR or \f3-fall\fR), and \f3_%ImplBase\fR for the \f3oldImplBase\fR class (-\f3oldImplBase\fR) and (\f3-fserver\fR or \f3-fall\fR))\&. +.TP +-td \fIdir\fR +.br +Use \fIdir\fR for the output directory instead of the current directory\&. +.TP +-tieName \fIxxx%yyy\fR +.br +Use \f3xxx%yyy\fR according to the pattern\&. The defaults are: \f3%POA\fR for the \f3POA\fR base class (\f3-fserverTie or -fallTie\fR), and \f3_%Tie\fR for the \f3oldImplBase\fR tie class (-\f3oldImplBase\fR) and (\f3-fserverTie\fR or \f3-fallTie\fR)) +.TP +-nowarn, -verbose +.br +Displays release information and terminates\&. +.TP +-version +.br +Displays release information and terminates\&. +.SH RESTRICTIONS +Escaped identifiers in the global scope cannot have the same spelling as IDL primitive types, \f3Object\fR, or \f3ValueBase\fR\&. This is because the symbol table is preloaded with these identifiers\&. Allowing them to be redefined would overwrite their original definitions\&. Possible permanent restriction\&. +.PP +The \f3fixed\fR IDL type is not supported\&. +.SH KNOWN\ PROBLEMS +No import is generated for global identifiers\&. If you call an unexported local \f3impl\fR object, then you do get an exception, but it seems to be due to a \f3NullPointerException\fR in the \f3ServerDelegate\fR DSI code\&. +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jar.1 b/jdk-1.8.0.281/man/man1/jar.1 new file mode 100755 index 0000000..feafb51 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jar.1 @@ -0,0 +1,464 @@ +'\" t +.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Basic Tools +.\" Title: jar.1 +.\" +.if n .pl 99999 +.TH jar 1 "21 November 2013" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jar \- Manipulates Java Archive (JAR) files\&. +.SH SYNOPSIS +Create JAR file +.sp +.nf + +\fBjar c\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.sp + +Update JAR file +.sp +.nf + +\fBjar u\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.sp + +Extract JAR file +.sp +.nf + +\fBjar\fR \fBx\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.sp + +List Contents of JAR file +.sp +.nf + +\fBjar\fR \fBt\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.sp + +Add Index to JAR file +.sp +.nf + +\fBjar\fR \fBi\fR \fIjarfile\fR [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] +.fi +.sp +.SH DESCRIPTION +The \f3jar\fR command is a general-purpose archiving and compression tool, based on ZIP and the ZLIB compression format\&. However, the \f3jar\fR command was designed mainly to package Java applets or applications into a single archive\&. When the components of an applet or application (files, images and sounds) are combined into a single archive, they can be downloaded by a Java agent (such as a browser) in a single HTTP transaction, rather than requiring a new connection for each piece\&. This dramatically improves download times\&. The \f3jar\fR command also compresses files, which further improves download time\&. The \f3jar\fR command also allows individual entries in a file to be signed by the applet author so that their origin can be authenticated\&. A JAR file can be used as a class path entry, whether or not it is compressed\&. +.PP +The syntax for the \f3jar\fR command resembles the syntax for the \f3tar\fR command\&. It has several operation modes, defined by one of the mandatory \fIoperation arguments\fR\&. Other arguments are either \fIoptions\fR that modify the behavior of the operation, or \fIoperands\fR required to perform the operation\&. +.SH OPERATION\ ARGUMENTS +When using the \f3jar\fR command, you have to select an operation to be performed by specifying one of the following operation arguments\&. You can mix them up with other one-letter options on the command line, but usually the operation argument is the first argument specified\&. +.TP +c +Create a new JAR archive\&. +.TP +i +Generate index information for a JAR archive\&. +.TP +t +List the contents of a JAR archive\&. +.TP +u +Update a JAR archive\&. +.TP +x +Extract files from a JAR archive\&. +.SH OPTIONS +Use the following options to customize how the JAR file is created, updated, extracted, or viewed: +.TP +e +Sets the class specified by the \fIentrypoint\fR operand to be the entry point\f3\fR for a standalone Java application bundled into an executable JAR file\&. The use of this option creates or overrides the \f3Main-Class\fR attribute value in the manifest file\&. The \f3e\fR option can be used when creating (\f3c\fR) or updating (\f3u\fR) the JAR file\&. + +For example, the following command creates the \f3Main\&.jar\fR archive with the \f3Main\&.class\fR file where the \f3Main-Clas\fRs attribute value in the manifest is set to \f3Main\fR: +.sp +.nf +\f3jar cfe Main\&.jar Main Main\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The Java Runtime Environment (JRE) can directly call this application by running the following command: +.sp +.nf +\f3java \-jar Main\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp + + +If the entry point class name is in a package, then it could use either the dot (\&.) or slash (/) as the delimiter\&. For example, if \f3Main\&.class\fR is in a package called \f3mydir\fR, then the entry point can be specified in one of the following ways: +.sp +.nf +\f3jar \-cfe Main\&.jar mydir/Main mydir/Main\&.class\fP +.fi +.nf +\f3jar \-cfe Main\&.jar mydir\&.Main mydir/Main\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Note + +Specifying both \f3m\fR and \f3e\fR options together when a particular manifest also contains the \f3Main-Class\fR attribute results in an ambiguous \f3Main-Class\fR specification\&. The ambiguity leads to an error and the \f3jar\fR command creation or update operation is terminated\&. +.TP +f +Sets the file specified by the \fI\fR\fIjarfile\fR operand to be the name of the JAR file that is created (\f3c\fR), updated (\f3u\fR), extracted (\f3x\fR) from, or viewed (\f3t\fR)\&. Omitting the \f3f\fR option and the \fIjarfile\fR operand instructs the \f3jar\fR command to accept the JAR file name from \f3stdin\fR (for \f3x\fR and \f3t\fR) or send the JAR \f3\fRfile to \f3stdout\fR (for \f3c\fR and \f3u\fR)\&. +.TP +m +Includes names and values of attributes from the file specified by the \f3manifest\fR operand in the manifest file of the \f3jar\fR command (located in the archive at \f3META-INF/MANIFEST\&.MF\fR)\&. The \f3jar\fR command adds the attribute\(cqs name and value to the JAR file unless an entry already exists with the same name, in which case the \f3jar\fR command updates the value of the attribute\&. The \f3m\fR option can be used when creating (\f3c\fR) or updating (\f3u\fR) the JAR file\&. + +You can add special-purpose name-value attribute pairs to the manifest that are not contained in the default manifest file\&. For example, you can add attributes that specify vendor information, release information, package sealing, or to make JAR-bundled applications executable\&. For examples of using the \f3m\fR option, see Packaging Programs at http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.html +.TP +M +Does not create a manifest file entry (for \f3c\fR and \f3u\fR), or delete a manifest file entry when one exists (for \f3u\fR)\&. The \f3M\fR option can be used when creating (\f3c\fR) or updating (\f3u\fR) the JAR file\&. +.TP +n +When creating (\f3c\fR) a JAR file, this option normalizes the archive so that the content is not affected by the packing and unpacking operations of the pack200(1) command\&. Without this normalization, the signature of a signed JAR can become invalid\&. +.TP +v +Generates verbose output to standard output\&. See Examples\&. +.TP +0 +(Zero) Creates (\f3c\fR) or updates (\f3u\fR) the JAR file without using ZIP compression\&. +.TP +-C \fIdir\fR +.br +When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, this option temporarily changes the directory while processing files specified by the \fIfile\fR operands\&. Its operation is intended to be similar to the \f3-C\fR option of the UNIX \f3tar\fR utility\&.For example, the following command changes to the \f3classes\fR directory and adds the \f3Bar\&.class\fR file from that directory to \f3my\&.jar\fR: +.sp +.nf +\f3jar uf my\&.jar \-C classes Bar\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following command changes to the \f3classes\fR directory and adds to \f3my\&.jar\fR all files within the classes directory (without creating a \f3classes\fR directory in the JAR file), then changes back to the original directory before changing to the \f3bin\fR directory to add \f3Xyz\&.class\fR to \f3my\&.jar\fR\&. +.sp +.nf +\f3jar uf my\&.jar \-C classes \&. \-C bin Xyz\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp + + +If \f3classes\fR contained files \f3bar1\fR and \f3bar2\fR, then the JAR file will contain the following after running the previous command: +.sp +.nf +\f3% \fIjar tf my\&.jar\fR\fP +.fi +.nf +\f3META\-INF/\fP +.fi +.nf +\f3META\-INF/MANIFEST\&.MF\fP +.fi +.nf +\f3bar1\fP +.fi +.nf +\f3bar2\fP +.fi +.nf +\f3Xyz\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +\fI\fR-J\fIoption\fR +Sets the specified JVM option to be used when the JRE runs the JAR file\&. JVM options are described on the reference page for the java(1) command\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. +.SH OPERANDS +The following operands are recognized by the \f3jar\fR command\&. +.TP +\fIfile\fR +When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, the \fIfile\fR operand defines the path and name of the file or directory that should be added to the archive\&. When extracting (\f3x\fR) or listing the contents (\f3t\fR) of a JAR file, the \fIfile\fR operand defines the path and name of the file to be extrated or listed\&. At least one valid file or directory must be specified\&. Separate multiple \fIfile\fR operands with spaces\&. If the \fIentrypoint\fR, \fIjarfile\fR, or \fImanifest\fR operands are used, the \fIfile\fR operands must be specified after them\&. +.TP +\fIentrypoint\fR +When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, the \fIentrypoint\fR operand defines the name of the class that should be the entry point\f3\fR for a standalone Java application bundled into an executable JAR file\&. The \fIentrypoint\fR operand must be specified if the \f3e\fR option is present\&. +.TP +\fIjarfile\fR +Defines the name of the file to be created (\f3c\fR), updated (\f3u\fR), extracted (\f3x\fR), or viewed (\f3t\fR)\&. The \fIjarfile\fR operand must be specified if the \f3f\fR option is present\&. Omitting the \f3f\fR option and the \fIjarfile\fR operand instructs the \f3jar\fR command to accept the JAR file name from \f3stdin\fR (for \f3x\fR and \f3t\fR) or send the JAR \f3\fRfile to \f3stdout\fR (for \f3c\fR and \f3u\fR)\&. + +When indexing (\f3i\fR) a JAR file, specify the \fIjarfile\fR operand without the \f3f\fR option\&. +.TP +\fImanifest\fR +When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, the \fImanifest\fR operand defines the preexisting manifest files with names and values of attributes to be included in \f3MANIFEST\&.MF\fR in the JAR file\&. The \fImanifest\fR operand must be specified if the \f3f\fR option is present\&. +.TP +\fI@arg-file\fR +To shorten or simplify the \f3jar\fR command, you can specify arguments in a separate text file and pass it to the \f3jar\fR command with the at sign (@) as a prefix\&. When the \f3jar\fR command encounters an argument beginning with the at sign, it expands the contents of that file into the argument list\&. + +An argument file can include options and arguments of the \f3jar\fR command (except the \f3-J\fR options, because they are passed to the launcher, which does not support argument files)\&. The arguments within a file can be separated by spaces or newline characters\&. File names within an argument file are relative to the current directory from which you run the \f3jar\fR command, not relative to the location of the argument file\&. Wild cards, such as the asterisk (*), that might otherwise be expanded by the operating system shell, are not expanded\&. + +The following example, shows how to create a \f3classes\&.list\fR file with names of files from the current directory output by the \f3find\fR command: +.sp +.nf +\f3find \&. \-name \&'*\&.class\&' \-print > classes\&.list\fP +.fi +.nf +\f3\fP +.fi +.sp + + +You can then execute the \f3jar\fR command and pass the \f3classes\&.list\fR file to it using the \fI@arg-file\fR syntax: +.sp +.nf +\f3jar cf my\&.jar @classes\&.list\fP +.fi +.nf +\f3\fP +.fi +.sp + + +An argument file can be specified with a path, but any file names inside the argument file that have relative paths are relative to the current working directory of the \f3jar\fR command, not to the path passed in, for example: +.sp +.nf +\f3jar @dir/classes\&.list\fP +.fi +.nf +\f3\fP +.fi +.sp + +.SH NOTES +The \f3e\fR, \f3f\fR, and \f3m\fR options must appear in the same order on the command line as the \fIentrypoint\fR, \fIjarfile\fR, and \fImanifest\fR operands, for example: +.sp +.nf +\f3jar cmef myManifestFile MyMainClass myFile\&.jar *\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH EXAMPLES +\f3Example 1 Adding All Files From the Current Directory With Verbose Output\fR +.sp +.nf +\f3% ls\fP +.fi +.nf +\f31\&.au Animator\&.class monkey\&.jpg\fP +.fi +.nf +\f32\&.au Wave\&.class spacemusic\&.au\fP +.fi +.nf +\f33\&.au at_work\&.gif\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3% jar cvf bundle\&.jar *\fP +.fi +.nf +\f3added manifest\fP +.fi +.nf +\f3adding: 1\&.au(in = 2324) (out= 67)(deflated 97%)\fP +.fi +.nf +\f3adding: 2\&.au(in = 6970) (out= 90)(deflated 98%)\fP +.fi +.nf +\f3adding: 3\&.au(in = 11616) (out= 108)(deflated 99%)\fP +.fi +.nf +\f3adding: Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fP +.fi +.nf +\f3adding: Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fP +.fi +.nf +\f3adding: at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fP +.fi +.nf +\f3adding: monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fP +.fi +.nf +\f3adding: spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 2 Adding Files From Subdirectories\fR +.sp +.nf +\f3% ls \-F\fP +.fi +.nf +\f3audio/ classes/ images/\fP +.fi +.nf +\f3% jar cvf bundle\&.jar audio classes images\fP +.fi +.nf +\f3added manifest\fP +.fi +.nf +\f3adding: audio/(in = 0) (out= 0)(stored 0%)\fP +.fi +.nf +\f3adding: audio/1\&.au(in = 2324) (out= 67)(deflated 97%)\fP +.fi +.nf +\f3adding: audio/2\&.au(in = 6970) (out= 90)(deflated 98%)\fP +.fi +.nf +\f3adding: audio/3\&.au(in = 11616) (out= 108)(deflated 99%)\fP +.fi +.nf +\f3adding: audio/spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fP +.fi +.nf +\f3adding: classes/(in = 0) (out= 0)(stored 0%)\fP +.fi +.nf +\f3adding: classes/Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fP +.fi +.nf +\f3adding: classes/Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fP +.fi +.nf +\f3adding: images/(in = 0) (out= 0)(stored 0%)\fP +.fi +.nf +\f3adding: images/monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fP +.fi +.nf +\f3adding: images/at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3% ls \-F\fP +.fi +.nf +\f3audio/ bundle\&.jar classes/ images/\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 3 Listing the Contents of JAR\fR +.sp +.nf +\f3% jar tf bundle\&.jar\fP +.fi +.sp +.sp +.nf +\f3META\-INF/\fP +.fi +.nf +\f3META\-INF/MANIFEST\&.MF\fP +.fi +.nf +\f3audio/1\&.au\fP +.fi +.nf +\f3audio/2\&.au\fP +.fi +.nf +\f3audio/3\&.au\fP +.fi +.nf +\f3audio/spacemusic\&.au\fP +.fi +.nf +\f3classes/Animator\&.class\fP +.fi +.nf +\f3classes/Wave\&.class\fP +.fi +.nf +\f3images/monkey\&.jpg\fP +.fi +.nf +\f3images/at_work\&.gif\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 4 Adding an Index\fR +.PP +Use the \f3i\fR option when you split the interdependent classes for a stock trade application into three JAR files: \f3main\&.jar\fR, \f3buy\&.jar\fR, and \f3sell\&.jar\fR\&. If you specify the \f3Class-Path\fR attribute in the \f3main\&.jar\fR manifest, then you can use the \f3i\fR option to speed up the class loading time for your application: +.sp +.nf +\f3Class\-Path: buy\&.jar sell\&.jar\fP +.fi +.nf +\f3jar i main\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp +An \f3INDEX\&.LIST\fR file is inserted to the \f3META-INF\fR directory\&. This enables the application class loader to download the specified JAR files when it is searching for classes or resources\&. +.PP +The application class loader uses the information stored in this file for efficient class loading\&. To copy directories, first compress files in \f3dir1\fR to \f3stdout\fR, then pipeline and extract from \f3stdin\fR to \f3dir2\fR (omitting the \f3-f\fR option from both \f3jar\fR commands): +.sp +.nf +\f3(cd dir1; jar c \&.) | (cd dir2; jar x)\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +pack200(1)\&. +.TP 0.2i +\(bu +The JAR section of The Java Tutorials at http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jarsigner.1 b/jdk-1.8.0.281/man/man1/jarsigner.1 new file mode 100755 index 0000000..788e5af --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jarsigner.1 @@ -0,0 +1,788 @@ +'\" t +.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Security Tools +.\" Title: jarsigner.1 +.\" +.if n .pl 99999 +.TH jarsigner 1 "21 November 2013" "JDK 8" "Security Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jarsigner \- Signs and verifies Java Archive (JAR) files\&. +.SH SYNOPSIS +.sp +.nf + +\fBjarsigner\fR [ \fIoptions\fR ] \fIjar\-file\fR \fIalias\fR +.fi +.nf + +\fBjarsigner\fR \fB\-verify\fR [ \fIoptions\fR ] \fIjar\-file\fR [\fIalias \&.\&.\&.\fR] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +-verify +.br +The \f3-verify\fR option can take zero or more keystore alias names after the JAR file name\&. When the \f3-verify\fR option is specified, the \f3jarsigner\fR command checks that the certificate used to verify each signed entry in the JAR file matches one of the keystore aliases\&. The aliases are defined in the keystore specified by \f3-keystore\fR or the default keystore\&. + +If you also specified the \f3-strict\fR option, and the \f3jarsigner\fR command detected severe warnings, the message, "jar verified, with signer errors" is displayed\&. +.TP +\fIjar-file\fR +The JAR file to be signed\&. + +If you also specified the \f3-strict\fR option, and the \f3jarsigner\fR command detected severe warnings, the message, "jar signed, with signer errors" is displayed\&. +.TP +\fIalias\fR +The aliases are defined in the keystore specified by \f3-keystore\fR or the default keystore\&. +.SH DESCRIPTION +The \f3jarsigner\fR tool has two purposes: +.TP 0.2i +\(bu +To sign Java Archive (JAR) files\&. +.TP 0.2i +\(bu +To verify the signatures and integrity of signed JAR files\&. +.PP +The JAR feature enables the packaging of class files, images, sounds, and other digital data in a single file for faster and easier distribution\&. A tool named \f3jar\fR enables developers to produce JAR files\&. (Technically, any zip file can also be considered a JAR file, although when created by the \f3jar\fR command or processed by the \f3jarsigner\fR command, JAR files also contain a \f3META-INF/MANIFEST\&.MF\fR file\&.) +.PP +A digital signature is a string of bits that is computed from some data (the data being signed) and the private key of an entity (a person, company, and so on)\&. Similar to a handwritten signature, a digital signature has many useful characteristics: +.TP 0.2i +\(bu +Its authenticity can be verified by a computation that uses the public key corresponding to the private key used to generate the signature\&. +.TP 0.2i +\(bu +It cannot be forged, assuming the private key is kept secret\&. +.TP 0.2i +\(bu +It is a function of the data signed and thus cannot be claimed to be the signature for other data as well\&. +.TP 0.2i +\(bu +The signed data cannot be changed\&. If the data is changed, then the signature cannot be verified as authentic\&. +.PP +To generate an entity\&'s signature for a file, the entity must first have a public/private key pair associated with it and one or more certificates that authenticate its public key\&. A certificate is a digitally signed statement from one entity that says that the public key of another entity has a particular value\&. +.PP +The \f3jarsigner\fR command uses key and certificate information from a keystore to generate digital signatures for JAR files\&. A keystore is a database of private keys and their associated X\&.509 certificate chains that authenticate the corresponding public keys\&. The \f3keytool\fR command is used to create and administer keystores\&. +.PP +The \f3jarsigner\fR command uses an entity\&'s private key to generate a signature\&. The signed JAR file contains, among other things, a copy of the certificate from the keystore for the public key corresponding to the private key used to sign the file\&. The \f3jarsigner\fR command can verify the digital signature of the signed JAR file using the certificate inside it (in its signature block file)\&. +.PP +The \f3jarsigner\fR command can generate signatures that include a time stamp that lets a systems or deployer (including Java Plug-in) to check whether the JAR file was signed while the signing certificate was still valid\&. In addition, APIs allow applications to obtain the timestamp information\&. +.PP +At this time, the \f3jarsigner\fR command can only sign JAR files created by the \f3jar\fR command or zip files\&. JAR files are the same as zip files, except they also have a \f3META-INF/MANIFEST\&.MF\fR file\&. A \f3META-INF/MANIFEST\&.MF\fR file is created when the \f3jarsigner\fR command signs a zip file\&. +.PP +The default \f3jarsigner\fR command behavior is to sign a JAR or zip file\&. Use the \f3-verify\fR option to verify a signed JAR file\&. +.PP +The \f3jarsigner\fR command also attempts to validate the signer\&'s certificate after signing or verifying\&. If there is a validation error or any other problem, the command generates warning messages\&. If you specify the \f3-strict\fR option, then the command treats severe warnings as errors\&. See Errors and Warnings\&. +.SS KEYSTORE\ ALIASES +All keystore entities are accessed with unique aliases\&. +.PP +When you use the \f3jarsigner\fR command to sign a JAR file, you must specify the alias for the keystore entry that contains the private key needed to generate the signature\&. For example, the following command signs the JAR file named \f3MyJARFile\&.jar\fR with the private key associated with the alias \f3duke\fR in the keystore named \f3mystore\fR in the \f3working\fR directory\&. Because no output file is specified, it overwrites \f3MyJARFile\&.jar\fR with the signed JAR file\&. +.sp +.nf +\f3jarsigner \-keystore /working/mystore \-storepass <keystore password>\fP +.fi +.nf +\f3 \-keypass <private key password> MyJARFile\&.jar duke\fP +.fi +.nf +\f3\fR +.fi +.sp +Keystores are protected with a password, so the store password must be specified\&. You are prompted for it when you do not specify it on the command line\&. Similarly, private keys are protected in a keystore with a password, so the private key\&'s password must be specified, and you are prompted for the password when you do not specify it on the command line and it is not the same as the store password\&. +.SS KEYSTORE\ LOCATION +The \f3jarsigner\fR command has a \f3-keystore\fR option for specifying the URL of the keystore to be used\&. The keystore is by default stored in a file named \f3\&.keystore\fR in the user\&'s home directory, as determined by the \f3user\&.home\fR system property\&. +.PP +On Oracle Solaris systems, \f3user\&.home\fR defaults to the user\&'s home directory\&. +.PP +The input stream from the \f3-keystore\fR option is passed to the \f3KeyStore\&.load\fR method\&. If \f3NONE\fR is specified as the URL, then a null stream is passed to the \f3KeyStore\&.load\fR method\&. \f3NONE\fR should be specified when the \f3KeyStore\fR class is not file based, for example, when it resides on a hardware token device\&. +.SS KEYSTORE\ IMPLEMENTATION +The \f3KeyStore\fR class provided in the \f3java\&.security\fR package supplies a number of well-defined interfaces to access and modify the information in a keystore\&. You can have multiple different concrete implementations, where each implementation is for a particular type of keystore\&. +.PP +Currently, there are two command-line tools that use keystore implementations (\f3keytool\fR and \f3jarsigner\fR), and a GUI-based tool named Policy Tool\&. Because the \f3KeyStore\fR class is publicly available, JDK users can write additional security applications that use it\&. +.PP +There is a built-in default implementation provided by Oracle that implements the keystore as a file, that uses a proprietary keystore type (format) named JKS\&. The built-in implementation protects each private key with its individual password and protects the integrity of the entire keystore with a (possibly different) password\&. +.PP +Keystore implementations are provider-based, which means the application interfaces supplied by the \f3KeyStore\fR class are implemented in terms of a Service Provider Interface (SPI)\&. There is a corresponding abstract \f3KeystoreSpi\fR class, also in the \f3java\&.security package\fR, that defines the Service Provider Interface methods that providers must implement\&. The term provider refers to a package or a set of packages that supply a concrete implementation of a subset of services that can be accessed by the Java Security API\&. To provide a keystore implementation, clients must implement a provider and supply a \f3KeystoreSpi\fR subclass implementation, as described in How to Implement a Provider in the Java Cryptography Architecture at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/HowToImplAProvider\&.html +.PP +Applications can choose different types of keystore implementations from different providers, with the \f3getInstance\fR factory method in the \f3KeyStore\fR class\&. A keystore type defines the storage and data format of the keystore information and the algorithms used to protect private keys in the keystore and the integrity of the keystore itself\&. Keystore implementations of different types are not compatible\&. +.PP +The \f3jarsigner\fR and \f3policytool\fR commands can read file-based keystores from any location that can be specified using a URL\&. In addition, these commands can read non-file-based keystores such as those provided by MSCAPI on Windows and PKCS11 on all platforms\&. +.PP +For the \f3jarsigner\fR and \f3keytool\fR commands, you can specify a keystore type at the command line with the \f3-storetype\fR option\&. For Policy Tool, you can specify a keystore type with the \fIEdit\fR command in the \fIKeyStore\fR menu\&. +.PP +If you do not explicitly specify a keystore type, then the tools choose a keystore implementation based on the value of the \f3keystore\&.type\fR property specified in the security properties file\&. The security properties file is called \f3java\&.security\fR, and it resides in the JDK security properties directory, \f3java\&.home/lib/security\fR, where \f3java\&.home\fR is the runtime environment\&'s directory\&. The \f3jre\fR directory in the JDK or the top-level directory of the Java Runtime Environment (JRE)\&. +.PP +Each tool gets the \f3keystore\&.type\fR value and then examines all the installed providers until it finds one that implements keystores of that type\&. It then uses the keystore implementation from that provider\&. +.PP +The \f3KeyStore\fR class defines a static method named \f3getDefaultType\fR that lets applications and applets retrieve the value of the \f3keystore\&.type\fR property\&. The following line of code creates an instance of the default keystore type as specified in the \f3keystore\&.type property\fR: +.sp +.nf +\f3KeyStore keyStore = KeyStore\&.getInstance(KeyStore\&.getDefaultType());\fP +.fi +.nf +\f3\fR +.fi +.sp +The default keystore type is \f3jks\fR (the proprietary type of the keystore implementation provided by Oracle)\&. This is specified by the following line in the security properties file: +.sp +.nf +\f3keystore\&.type=jks\fP +.fi +.nf +\f3\fR +.fi +.sp +Case does not matter in keystore type designations\&. For example, \f3JKS\fR is the same as \f3jks\fR\&. +.PP +To have the tools use a keystore implementation other than the default, change that line to specify a different keystore type\&. For example, if you have a provider package that supplies a keystore implementation for a keystore type called \f3pkcs12\fR, then change the line to the following: +.sp +.nf +\f3keystore\&.type=pkcs12\fP +.fi +.nf +\f3\fR +.fi +.sp +\fINote:\fR If you use the PKCS 11 provider package, then see "KeyTool" and "JarSigner" in Java PKCS #11 Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/p11guide\&.html +.SS SUPPORTED\ ALGORITHMS +By default, the \f3jarsigner\fR command signs a JAR file using one of the following algorithms: +.TP 0.2i +\(bu +Digital Signature Algorithm (DSA) with the SHA1 digest algorithm +.TP 0.2i +\(bu +RSA algorithm with the SHA256 digest algorithm +.TP 0.2i +\(bu +Elliptic Curve (EC) cryptography algorithm with the SHA256 with Elliptic Curve Digital Signature Algorithm (ECDSA)\&. +.PP +If the signer\&'s public and private keys are DSA keys, then \f3jarsigner\fR signs the JAR file with the \f3SHA1withDSA\fR algorithm\&. If the signer\&'s keys are RSA keys, then \f3jarsigner\fR attempts to sign the JAR file with the \f3SHA256withRSA\fR algorithm\&. If the signer\&'s keys are EC keys, then \f3jarsigner\fR signs the JAR file with the \f3SHA256withECDSA\fR algorithm\&. +.PP +These default signature algorithms can be overridden using the \f3-sigalg\fR option\&. +.SS THE\ SIGNED\ JAR\ FILE +When the \f3jarsigner\fR command is used to sign a JAR file, the output signed JAR file is exactly the same as the input JAR file, except that it has two additional files placed in the META-INF directory: +.TP 0.2i +\(bu +A signature file with an \f3\&.SF\fR extension +.TP 0.2i +\(bu +A signature block file with a \f3\&.DSA\fR, \f3\&.RSA\fR, or \f3\&.EC\fR extension +.PP +The base file names for these two files come from the value of the \f3-sigFile\fR option\&. For example, when the option is \f3-sigFile MKSIGN\fR, the files are named \f3MKSIGN\&.SF\fR and \f3MKSIGN\&.DSA\fR +.PP +If no \f3-sigfile\fR option appears on the command line, then the base file name for the \f3\&.SF\fR and \f3\&.DSA\fR files is the first 8 characters of the alias name specified on the command line, all converted to uppercase\&. If the alias name has fewer than 8 characters, then the full alias name is used\&. If the alias name contains any characters that are not allowed in a signature file name, then each such character is converted to an underscore (_) character in forming the file name\&. Valid characters include letters, digits, underscores, and hyphens\&. +.PP +Signature File + +A signature file (\f3\&.SF\fR file) looks similar to the manifest file that is always included in a JAR file when the \f3jarsigner\fR command is used to sign the file\&. For each source file included in the JAR file, the \f3\&.SF\fR file has three lines, such as in the manifest file, that list the following: +.TP 0.2i +\(bu +File name +.TP 0.2i +\(bu +Name of the digest algorithm (SHA) +.TP 0.2i +\(bu +SHA digest value +.PP +In the manifest file, the SHA digest value for each source file is the digest (hash) of the binary data in the source file\&. In the \f3\&.SF\fR file, the digest value for a specified source file is the hash of the three lines in the manifest file for the source file\&. +.PP +The signature file, by default, includes a header with a hash of the whole manifest file\&. The header also contains a hash of the manifest header\&. The presence of the header enables verification optimization\&. See JAR File Verification\&. +.PP +Signature Block File + +The \f3\&.SF\fR file is signed and the signature is placed in the signature block file\&. This file also contains, encoded inside it, the certificate or certificate chain from the keystore that authenticates the public key corresponding to the private key used for signing\&. The file has the extension \f3\&.DSA\fR, \f3\&.RSA\fR, or \f3\&.EC\fR, depending on the digest algorithm used\&. +.SS SIGNATURE\ TIME\ STAMP +The \f3jarsigner\fR command can generate and store a signature time stamp when signing a JAR file\&. In addition, \f3jarsigner\fR supports alternative signing mechanisms\&. This behavior is optional and is controlled by the user at the time of signing through these options\&. See Options\&. +.sp +.nf +\f3\-tsa \fIurl\fR\fP +.fi +.nf +\f3\-tsacert \fIalias\fR\fP +.fi +.nf +\f3\-altsigner \fIclass\fR\fP +.fi +.nf +\f3\-altsignerpath \fIclasspathlist\fR\fP +.fi +.nf +\f3\-tsapolicyid \fIpolicyid\fR\fP +.fi +.nf +\f3\fR +.fi +.sp +.SS JAR\ FILE\ VERIFICATION +A successful JAR file verification occurs when the signatures are valid, and none of the files that were in the JAR file when the signatures were generated have changed since then\&. JAR file verification involves the following steps: +.TP 0.4i +1\&. +Verify the signature of the \f3\&.SF\fR file\&. + +The verification ensures that the signature stored in each signature block (\f3\&.DSA\fR) file was generated using the private key corresponding to the public key whose certificate (or certificate chain) also appears in the \f3\&.DSA\fR file\&. It also ensures that the signature is a valid signature of the corresponding signature (\f3\&.SF\fR) file, and thus the \f3\&.SF\fR file was not tampered with\&. +.TP 0.4i +2\&. +Verify the digest listed in each entry in the \f3\&.SF\fR file with each corresponding section in the manifest\&. + +The \f3\&.SF\fR file by default includes a header that contains a hash of the entire manifest file\&. When the header is present, the verification can check to see whether or not the hash in the header matches the hash of the manifest file\&. If there is a match, then verification proceeds to the next step\&. + +If there is no match, then a less optimized verification is required to ensure that the hash in each source file information section in the \f3\&.SF\fR file equals the hash of its corresponding section in the manifest file\&. See Signature File\&. + +One reason the hash of the manifest file that is stored in the \f3\&.SF\fR file header might not equal the hash of the current manifest file is that one or more files were added to the JAR file (with the \f3jar\fR tool) after the signature and \f3\&.SF\fR file were generated\&. When the \f3jar\fR tool is used to add files, the manifest file is changed by adding sections to it for the new files, but the \f3\&.SF\fR file is not changed\&. A verification is still considered successful when none of the files that were in the JAR file when the signature was generated have been changed since then\&. This happens when the hashes in the non-header sections of the \f3\&.SF\fR file equal the hashes of the corresponding sections in the manifest file\&. +.TP 0.4i +3\&. +Read each file in the JAR file that has an entry in the \f3\&.SF\fR file\&. While reading, compute the file\&'s digest and compare the result with the digest for this file in the manifest section\&. The digests should be the same or verification fails\&. + +If any serious verification failures occur during the verification process, then the process is stopped and a security exception is thrown\&. The \f3jarsigner\fR command catches and displays the exception\&. +.PP +\fINote:\fR You should read any addition warnings (or errors if you specified the \f3-strict\fR option), as well as the content of the certificate (by specifying the \f3-verbose\fR and \f3-certs\fR options) to determine if the signature can be trusted\&. +.SS MULTIPLE\ SIGNATURES\ FOR\ A\ JAR\ FILE +A JAR file can be signed by multiple people by running the \f3jarsigner\fR command on the file multiple times and specifying the alias for a different person each time, as follows: +.sp +.nf +\f3jarsigner myBundle\&.jar susan\fP +.fi +.nf +\f3jarsigner myBundle\&.jar kevin\fP +.fi +.nf +\f3\fR +.fi +.sp +When a JAR file is signed multiple times, there are multiple \f3\&.SF\fR and \f3\&.DSA\fR files in the resulting JAR file, one pair for each signature\&. In the previous example, the output JAR file includes files with the following names: +.sp +.nf +\f3SUSAN\&.SF\fP +.fi +.nf +\f3SUSAN\&.DSA\fP +.fi +.nf +\f3KEVIN\&.SF\fP +.fi +.nf +\f3KEVIN\&.DSA\fP +.fi +.sp +.SH OPTIONS +The following sections describe the various \f3jarsigner\fR options\&. Be aware of the following standards: +.TP 0.2i +\(bu +All option names are preceded by a minus sign (-)\&. +.TP 0.2i +\(bu +The options can be provided in any order\&. +.TP 0.2i +\(bu +Items that are in italics or underlined (option values) represent the actual values that must be supplied\&. +.TP 0.2i +\(bu +The \f3-storepass\fR, \f3-keypass\fR, \f3-sigfile\fR, \f3-sigalg\fR, \f3-digestalg\fR, \f3-signedjar\fR, and TSA-related options are only relevant when signing a JAR file; they are not relevant when verifying a signed JAR file\&. The \f3-keystore\fR option is relevant for signing and verifying a JAR file\&. In addition, aliases are specified when signing and verifying a JAR file\&. +.TP +-keystore \fIurl\fR +.br +Specifies the URL that tells the keystore location\&. This defaults to the file \f3\&.keystore\fR in the user\&'s home directory, as determined by the \f3user\&.home\fR system property\&. + +A keystore is required when signing\&. You must explicitly specify a keystore when the default keystore does not exist or if you want to use one other than the default\&. + +A keystore is not required when verifying, but if one is specified or the default exists and the \f3-verbose\fR option was also specified, then additional information is output regarding whether or not any of the certificates used to verify the JAR file are contained in that keystore\&. + +The \f3-keystore\fR argument can be a file name and path specification rather than a URL, in which case it is treated the same as a file: URL, for example, the following are equivalent: +.sp +.nf +\f3\-keystore \fIfilePathAndName\fR\fP +.fi +.nf +\f3\-keystore file:\fIfilePathAndName\fR\fP +.fi +.nf +\f3\fR +.fi +.sp + + +If the Sun PKCS #11 provider was configured in the \f3java\&.security\fR security properties file (located in the JRE\&'s \f3$JAVA_HOME/lib/security directory\fR), then the \f3keytool\fR and \f3jarsigner\fR tools can operate on the PKCS #11 token by specifying these options: +.sp +.nf +\f3\-keystore NONE\fP +.fi +.nf +\f3\-storetype PKCS11\fP +.fi +.nf +\f3\fR +.fi +.sp + + +For example, the following command lists the contents of the configured PKCS#11 token: +.sp +.nf +\f3keytool \-keystore NONE \-storetype PKCS11 \-list\fP +.fi +.nf +\f3\fR +.fi +.sp + +.TP +-storetype \fIstoretype\fR +.br +Specifies the type of keystore to be instantiated\&. The default keystore type is the one that is specified as the value of the \f3keystore\&.type\fR property in the security properties file, which is returned by the static \f3getDefaultType\fR method in \f3java\&.security\&.KeyStore\fR\&. + +The PIN for a PCKS #11 token can also be specified with the \f3-storepass\fR option\&. If none is specified, then the \f3keytool\fR and \f3jarsigner\fR commands prompt for the token PIN\&. If the token has a protected authentication path (such as a dedicated PIN-pad or a biometric reader), then the \f3-protected\fR option must be specified and no password options can be specified\&. +.TP +-storepass[:env | :file] \fIargument\fR +.br +Specifies the password that is required to access the keystore\&. This is only needed when signing (not verifying) a JAR file\&. In that case, if a \f3-storepass\fR option is not provided at the command line, then the user is prompted for the password\&. + +If the modifier \f3env\fR or \f3file\fR is not specified, then the password has the value \fIargument\fR\&. Otherwise, the password is retrieved as follows: +.RS +.TP 0.2i +\(bu +\f3env\fR: Retrieve the password from the environment variable named \f3argument\fR\&. +.TP 0.2i +\(bu +\f3file\fR: Retrieve the password from the file named \f3argument\fR\&. +.RE + + +\fINote:\fR The password should not be specified on the command line or in a script unless it is for testing purposes, or you are on a secure system\&. +.TP +-keypass [:env | :file] \fIargument\fR +.br +Specifies the password used to protect the private key of the keystore entry addressed by the alias specified on the command line\&. The password is required when using \f3jarsigner\fR to sign a JAR file\&. If no password is provided on the command line, and the required password is different from the store password, then the user is prompted for it\&. + +If the modifier \f3env\fR or \f3file\fR is not specified, then the password has the value \f3argument\fR\&. Otherwise, the password is retrieved as follows: +.RS +.TP 0.2i +\(bu +\f3env\fR: Retrieve the password from the environment variable named \f3argument\fR\&. +.TP 0.2i +\(bu +\f3file\fR: Retrieve the password from the file named \f3argument\fR\&. +.RE + + +\fINote:\fR The password should not be specified on the command line or in a script unless it is for testing purposes, or you are on a secure system\&. +.TP +-sigfile \fIfile\fR +.br +Specifies the base file name to be used for the generated \f3\&.SF\fR and \f3\&.DSA\fR files\&. For example, if file is \f3DUKESIGN\fR, then the generated \f3\&.SF\fR and \f3\&.DSA\fR files are named \f3DUKESIGN\&.SF\fR and \f3DUKESIGN\&.DSA\fR, and placed in the \f3META-INF\fR directory of the signed JAR file\&. + +The characters in the file must come from the set \f3a-zA-Z0-9_-\fR\&. Only letters, numbers, underscore, and hyphen characters are allowed\&. All lowercase characters are converted to uppercase for the \f3\&.SF\fR and \f3\&.DSA\fR file names\&. + +If no \f3-sigfile\fR option appears on the command line, then the base file name for the \f3\&.SF\fR and \f3\&.DSA\fR files is the first 8 characters of the alias name specified on the command line, all converted to upper case\&. If the alias name has fewer than 8 characters, then the full alias name is used\&. If the alias name contains any characters that are not valid in a signature file name, then each such character is converted to an underscore (_) character to form the file name\&. +.TP +-sigalg \fIalgorithm\fR +.br +Specifies the name of the signature algorithm to use to sign the JAR file\&. + +For a list of standard signature algorithm names, see "Appendix A: Standard Names" in the Java Cryptography Architecture (JCA) Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppA + +This algorithm must be compatible with the private key used to sign the JAR file\&. If this option is not specified, then \f3SHA1withDSA\fR, \f3SHA256withRSA\fR, or \f3SHA256withECDSA\fR are used depending on the type of private key\&. There must either be a statically installed provider supplying an implementation of the specified algorithm or the user must specify one with the \f3-providerClass\fR option; otherwise, the command will not succeed\&. +.TP +-digestalg \fIalgorithm\fR +.br +Specifies the name of the message digest algorithm to use when digesting the entries of a JAR file\&. + +For a list of standard message digest algorithm names, see "Appendix A: Standard Names" in the Java Cryptography Architecture (JCA) Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppA + +If this option is not specified, then \f3SHA256\fR is used\&. There must either be a statically installed provider supplying an implementation of the specified algorithm or the user must specify one with the \f3-providerClass\fR option; otherwise, the command will not succeed\&. +.TP +-certs +.br +If the \f3-certs\fR option appears on the command line with the \f3-verify\fR and \f3-verbose\fR options, then the output includes certificate information for each signer of the JAR file\&. This information includes the name of the type of certificate (stored in the \f3\&.DSA\fR file) that certifies the signer\&'s public key, and if the certificate is an X\&.509 certificate (an instance of the \f3java\&.security\&.cert\&.X509Certificate\fR), then the distinguished name of the signer\&. + +The keystore is also examined\&. If no keystore value is specified on the command line, then the default keystore file (if any) is checked\&. If the public key certificate for a signer matches an entry in the keystore, then the alias name for the keystore entry for that signer is displayed in parentheses\&. +.TP +-certchain \fIfile\fR +.br +Specifies the certificate chain to be used when the certificate chain associated with the private key of the keystore entry that is addressed by the alias specified on the command line is not complete\&. This can happen when the keystore is located on a hardware token where there is not enough capacity to hold a complete certificate chain\&. The file can be a sequence of concatenated X\&.509 certificates, or a single PKCS#7 formatted data block, either in binary encoding format or in printable encoding format (also known as Base64 encoding) as defined by the Internet RFC 1421 standard\&. See Internet RFC 1421 Certificate Encoding Standard and http://tools\&.ietf\&.org/html/rfc1421\&. +.TP +-verbose +.br +When the \f3-verbose\fR option appears on the command line, it indicates verbose mode, which causes \f3jarsigner\fR to output extra information about the progress of the JAR signing or verification\&. +.TP +-internalsf +.br +In the past, the \f3\&.DSA\fR (signature block) file generated when a JAR file was signed included a complete encoded copy of the \f3\&.SF\fR file (signature file) also generated\&. This behavior has been changed\&. To reduce the overall size of the output JAR file, the \f3\&.DSA\fR file by default does not contain a copy of the \f3\&.SF\fR file anymore\&. If \f3-internalsf\fR appears on the command line, then the old behavior is utilized\&. This option is useful for testing\&. In practice, do not use the \f3-internalsf\fR option because it incurs higher overhead\&. +.TP +-sectionsonly +.br +If the \f3-sectionsonly\fR option appears on the command line, then the \f3\&.SF\fR file (signature file) generated when a JAR file is signed does not include a header that contains a hash of the whole manifest file\&. It contains only the information and hashes related to each individual source file included in the JAR file\&. See Signature File\&. + +By default, this header is added, as an optimization\&. When the header is present, whenever the JAR file is verified, the verification can first check to see whether the hash in the header matches the hash of the whole manifest file\&. When there is a match, verification proceeds to the next step\&. When there is no match, it is necessary to do a less optimized verification that the hash in each source file information section in the \f3\&.SF\fR file equals the hash of its corresponding section in the manifest file\&. See JAR File Verification\&. + +The \f3-sectionsonly\fR option is primarily used for testing\&. It should not be used other than for testing because using it incurs higher overhead\&. +.TP +-protected +.br +Values can be either \f3true\fR or \f3false\fR\&. Specify \f3true\fR when a password must be specified through a protected authentication path such as a dedicated PIN reader\&. +.TP +-providerClass \fIprovider-class-name\fR +.br +Used to specify the name of cryptographic service provider\&'s master class file when the service provider is not listed in the \f3java\&.security\fR security properties file\&. + +Used with the \f3-providerArg ConfigFilePath\fR option, the \f3keytool\fR and \f3jarsigner\fR tools install the provider dynamically and use \fIConfigFilePath\fR for the path to the token configuration file\&. The following example shows a command to list a \f3PKCS #11\fR keystore when the Oracle PKCS #11 provider was not configured in the security properties file\&. +.sp +.nf +\f3jarsigner \-keystore NONE \-storetype PKCS11 \e\fP +.fi +.nf +\f3 \-providerClass sun\&.security\&.pkcs11\&.SunPKCS11 \e\fP +.fi +.nf +\f3 \-providerArg /mydir1/mydir2/token\&.config \e\fP +.fi +.nf +\f3 \-list\fP +.fi +.nf +\f3\fR +.fi +.sp + +.TP +-providerName \fIproviderName\fR +.br +If more than one provider was configured in the \f3java\&.security\fR security properties file, then you can use the \f3-providerName\fR option to target a specific provider instance\&. The argument to this option is the name of the provider\&. + +For the Oracle PKCS #11 provider, \fIproviderName\fR is of the form \f3SunPKCS11-\fR\fITokenName\fR, where \fITokenName\fR is the name suffix that the provider instance has been configured with, as detailed in the configuration attributes table\&. For example, the following command lists the contents of the \f3PKCS #11\fR keystore provider instance with name suffix \f3SmartCard\fR: +.sp +.nf +\f3jarsigner \-keystore NONE \-storetype PKCS11 \e\fP +.fi +.nf +\f3 \-providerName SunPKCS11\-SmartCard \e\fP +.fi +.nf +\f3 \-list\fP +.fi +.nf +\f3\fR +.fi +.sp + +.TP +-J\fIjavaoption\fR +.br +Passes through the specified \fIjavaoption\fR string directly to the Java interpreter\&. The \f3jarsigner\fR command is a wrapper around the interpreter\&. This option should not contain any spaces\&. It is useful for adjusting the execution environment or memory usage\&. For a list of possible interpreter options, type \f3java -h\fR or \f3java -X\fR at the command line\&. +.TP +-tsa \fIurl\fR +.br +If \f3-tsa http://example\&.tsa\&.url\fR appears on the command line when signing a JAR file then a time stamp is generated for the signature\&. The URL, \f3http://example\&.tsa\&.url\fR, identifies the location of the Time Stamping Authority (TSA) and overrides any URL found with the \f3-tsacert\fR option\&. The \f3-tsa\fR option does not require the TSA public key certificate to be present in the keystore\&. + +To generate the time stamp, \f3jarsigner\fR communicates with the TSA with the Time-Stamp Protocol (TSP) defined in RFC 3161\&. When successful, the time stamp token returned by the TSA is stored with the signature in the signature block file\&. +.TP +-tsacert \fIalias\fR +.br +When \f3-tsacert alias\fR appears on the command line when signing a JAR file, a time stamp is generated for the signature\&. The alias identifies the TSA public key certificate in the keystore that is in effect\&. The entry\&'s certificate is examined for a Subject Information Access extension that contains a URL identifying the location of the TSA\&. + +The TSA public key certificate must be present in the keystore when using the \f3-tsacert\fR option\&. +.TP +-tsapolicyid \fIpolicyid\fR +.br +Specifies the object identifier (OID) that identifies the policy ID to be sent to the TSA server\&. If this option is not specified, no policy ID is sent and the TSA server will choose a default policy ID\&. + +Object identifiers are defined by X\&.696, which is an ITU Telecommunication Standardization Sector (ITU-T) standard\&. These identifiers are typically period-separated sets of non-negative digits like \f31\&.2\&.3\&.4\fR, for example\&. +.TP +-altsigner \fIclass\fR +.br +This option specifies an alternative signing mechanism\&. The fully qualified class name identifies a class file that extends the \f3com\&.sun\&.jarsigner\&.ContentSigner\fR abstract class\&. The path to this class file is defined by the \f3-altsignerpath\fR option\&. If the \f3-altsigner\fR option is used, then the \f3jarsigner\fR command uses the signing mechanism provided by the specified class\&. Otherwise, the \f3jarsigner\fR command uses its default signing mechanism\&. + +For example, to use the signing mechanism provided by a class named \f3com\&.sun\&.sun\&.jarsigner\&.AuthSigner\fR, use the jarsigner option \f3-altsigner com\&.sun\&.jarsigner\&.AuthSigner\fR\&. +.TP +-altsignerpath \fIclasspathlist\fR +.br +Specifies the path to the class file and any JAR file it depends on\&. The class file name is specified with the \f3-altsigner\fR option\&. If the class file is in a JAR file, then this option specifies the path to that JAR file\&. + +An absolute path or a path relative to the current directory can be specified\&. If \fIclasspathlist\fR contains multiple paths or JAR files, then they should be separated with a colon (:) on Oracle Solaris and a semicolon (;) on Windows\&. This option is not necessary when the class is already in the search path\&. + +The following example shows how to specify the path to a JAR file that contains the class file\&. The JAR file name is included\&. +.sp +.nf +\f3\-altsignerpath /home/user/lib/authsigner\&.jar\fP +.fi +.nf +\f3\fR +.fi +.sp + + +The following example shows how to specify the path to the JAR file that contains the class file\&. The JAR file name is omitted\&. +.sp +.nf +\f3\-altsignerpath /home/user/classes/com/sun/tools/jarsigner/\fP +.fi +.nf +\f3\fR +.fi +.sp + +.TP +-strict +.br +During the signing or verifying process, the command may issue warning messages\&. If you specify this option, the exit code of the tool reflects the severe warning messages that this command found\&. See Errors and Warnings\&. +.TP +-verbose \fIsuboptions\fR +.br +For the verifying process, the \f3-verbose\fR option takes suboptions to determine how much information is shown\&. If the \f3-certs\fR option is also specified, then the default mode (or suboption \f3all\fR) displays each entry as it is being processed, and after that, the certificate information for each signer of the JAR file\&. If the \f3-certs\fR and the \f3-verbose:grouped\fR suboptions are specified, then entries with the same signer info are grouped and displayed together with their certificate information\&. If \f3-certs\fR and the \f3-verbose:summary\fR suboptions are specified, then entries with the same signer information are grouped and displayed together with their certificate information\&. Details about each entry are summarized and displayed as \fIone entry (and more)\fR\&. See Examples\&. +.SH ERRORS\ AND\ WARNINGS +During the signing or verifying process, the \f3jarsigner\fR command may issue various errors or warnings\&. +.PP +If there is a failure, the \f3jarsigner\fR command exits with code 1\&. If there is no failure, but there are one or more severe warnings, the \f3jarsigner\fR command exits with code 0 when the \f3-strict\fR option is \fInot\fR specified, or exits with the OR-value of the warning codes when the \f3-strict\fR is specified\&. If there is only informational warnings or no warning at all, the command always exits with code 0\&. +.PP +For example, if a certificate used to sign an entry is expired and has a KeyUsage extension that does not allow it to sign a file, the \f3jarsigner\fR command exits with code 12 (=4+8) when the \f3-strict\fR option is specified\&. +.PP +\fINote:\fR Exit codes are reused because only the values from 0 to 255 are legal on Unix-based operating systems\&. +.PP +The following sections describes the names, codes, and descriptions of the errors and warnings that the \f3jarsigner\fR command can issue\&. +.SS FAILURE +Reasons why the \f3jarsigner\fR command fails include (but are not limited to) a command line parsing error, the inability to find a keypair to sign the JAR file, or the verification of a signed JAR fails\&. +.TP +failure +Code 1\&. The signing or verifying fails\&. +.SS SEVERE\ WARNINGS +\fINote:\fR Severe warnings are reported as errors if you specify the \f3-strict\fR option\&. +.PP +Reasons why the \f3jarsigner\fR command issues a severe warning include the certificate used to sign the JAR file has an error or the signed JAR file has other problems\&. +.TP +hasExpiredCert +Code 4\&. This jar contains entries whose signer certificate has expired\&. +.TP +notYetValidCert +Code 4\&. This jar contains entries whose signer certificate is not yet valid\&. +.TP +chainNotValidated +Code 4\&. This jar contains entries whose certificate chain cannot be correctly validated\&. +.TP +badKeyUsage +Code 8\&. This jar contains entries whose signer certificate\&'s KeyUsage extension doesn\&'t allow code signing\&. +.TP +badExtendedKeyUsage +Code 8\&. This jar contains entries whose signer certificate\&'s ExtendedKeyUsage extension doesn\&'t allow code signing\&. +.TP +badNetscapeCertType +Code 8\&. This jar contains entries whose signer certificate\&'s NetscapeCertType extension doesn\&'t allow code signing\&. +.TP +hasUnsignedEntry +Code 16\&. This jar contains unsigned entries which have not been integrity-checked\&. +.TP +notSignedByAlias +Code 32\&. This jar contains signed entries which are not signed by the specified alias(es)\&. +.TP +aliasNotInStore +Code 32\&. This jar contains signed entries that are not signed by alias in this keystore\&. +.SS INFORMATIONAL\ WARNINGS +Informational warnings include those that are not errors but regarded as bad practice\&. They do not have a code\&. +.TP +hasExpiringCert +This jar contains entries whose signer certificate will expire within six months\&. +.TP +noTimestamp +This jar contains signatures that does not include a timestamp\&. Without a timestamp, users may not be able to validate this JAR file after the signer certificate\&'s expiration date (\f3YYYY-MM-DD\fR) or after any future revocation date\&. +.SH EXAMPLES +.SS SIGN\ A\ JAR\ FILE +Use the following command to sign bundle\&.jar with the private key of a user whose keystore alias is \f3jane\fR in a keystore named \f3mystore\fR in the \f3working\fR directory and name the signed JAR file \f3sbundle\&.jar\fR: +.sp +.nf +\f3jarsigner \-keystore /working/mystore\fP +.fi +.nf +\f3 \-storepass <keystore password>\fP +.fi +.nf +\f3 \-keypass <private key password>\fP +.fi +.nf +\f3 \-signedjar sbundle\&.jar bundle\&.jar jane\fP +.fi +.nf +\f3\fR +.fi +.sp +There is no \f3-sigfile\fR specified in the previous command so the generated \f3\&.SF\fR and \f3\&.DSA\fR files to be placed in the signed JAR file have default names based on the alias name\&. They are named \f3JANE\&.SF\fR and \f3JANE\&.DSA\fR\&. +.PP +If you want to be prompted for the store password and the private key password, then you could shorten the previous command to the following: +.sp +.nf +\f3jarsigner \-keystore /working/mystore\fP +.fi +.nf +\f3 \-signedjar sbundle\&.jar bundle\&.jar jane\fP +.fi +.nf +\f3\fR +.fi +.sp +If the keystore is the default keystore (\&.keystore in your home directory), then you do not need to specify a keystore, as follows: +.sp +.nf +\f3jarsigner \-signedjar sbundle\&.jar bundle\&.jar jane\fP +.fi +.nf +\f3\fR +.fi +.sp +If you want the signed JAR file to overwrite the input JAR file (bundle\&.jar), then you do not need to specify a \f3-signedjar\fR option, as follows: +.sp +.nf +\f3jarsigner bundle\&.jar jane\fP +.fi +.nf +\f3\fR +.fi +.sp +.SS VERIFY\ A\ SIGNED\ JAR\ FILE +To verify a signed JAR file to ensure that the signature is valid and the JAR file was not been tampered with, use a command such as the following: +.sp +.nf +\f3jarsigner \-verify sbundle\&.jar\fP +.fi +.nf +\f3\fR +.fi +.sp +When the verification is successful, \f3jar verified\fR is displayed\&. Otherwise, an error message is displayed\&. You can get more information when you use the \f3-verbose\fR option\&. A sample use of \f3jarsigner\fR with the\f3-verbose\fR option follows: +.sp +.nf +\f3jarsigner \-verify \-verbose sbundle\&.jar\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 198 Fri Sep 26 16:14:06 PDT 1997 META\-INF/MANIFEST\&.MF\fP +.fi +.nf +\f3 199 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.SF\fP +.fi +.nf +\f3 1013 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.DSA\fP +.fi +.nf +\f3 smk 2752 Fri Sep 26 16:12:30 PDT 1997 AclEx\&.class\fP +.fi +.nf +\f3 smk 849 Fri Sep 26 16:12:46 PDT 1997 test\&.class\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 s = signature was verified\fP +.fi +.nf +\f3 m = entry is listed in manifest\fP +.fi +.nf +\f3 k = at least one certificate was found in keystore\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 jar verified\&.\fP +.fi +.nf +\f3\fR +.fi +.sp +.SS VERIFICATION\ WITH\ CERTIFICATE\ INFORMATION +If you specify the \f3-certs\fR option with the \f3-verify\fR and \f3-verbose\fR options, then the output includes certificate information for each signer of the JAR file\&. The information includes the certificate type, the signer distinguished name information (when it is an X\&.509 certificate), and in parentheses, the keystore alias for the signer when the public key certificate in the JAR file matches the one in a keystore entry, for example: +.sp +.nf +\f3jarsigner \-keystore /working/mystore \-verify \-verbose \-certs myTest\&.jar\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 198 Fri Sep 26 16:14:06 PDT 1997 META\-INF/MANIFEST\&.MF\fP +.fi +.nf +\f3 199 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.SF\fP +.fi +.nf +\f3 1013 Fri Sep 26 16:22:10 PDT 1997 META\-INF/JANE\&.DSA\fP +.fi +.nf +\f3 208 Fri Sep 26 16:23:30 PDT 1997 META\-INF/JAVATEST\&.SF\fP +.fi +.nf +\f3 1087 Fri Sep 26 16:23:30 PDT 1997 META\-INF/JAVATEST\&.DSA\fP +.fi +.nf +\f3 smk 2752 Fri Sep 26 16:12:30 PDT 1997 Tst\&.class\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 X\&.509, CN=Test Group, OU=Java Software, O=Oracle, L=CUP, S=CA, C=US (javatest)\fP +.fi +.nf +\f3 X\&.509, CN=Jane Smith, OU=Java Software, O=Oracle, L=cup, S=ca, C=us (jane)\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 s = signature was verified\fP +.fi +.nf +\f3 m = entry is listed in manifest\fP +.fi +.nf +\f3 k = at least one certificate was found in keystore\fP +.fi +.nf +\f3\fR +.fi +.nf +\f3 jar verified\&.\fP +.fi +.nf +\f3\fR +.fi +.sp +If the certificate for a signer is not an X\&.509 certificate, then there is no distinguished name information\&. In that case, just the certificate type and the alias are shown\&. For example, if the certificate is a PGP certificate, and the alias is \f3bob\fR, then you would get: \f3PGP, (bob)\fR\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jar(1) +.TP 0.2i +\(bu +keytool(1) +.TP 0.2i +\(bu +Trail: Security Features in Java SE at http://docs\&.oracle\&.com/javase/tutorial/security/index\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/java.1 b/jdk-1.8.0.281/man/man1/java.1 new file mode 100755 index 0000000..4d4cb26 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/java.1 @@ -0,0 +1,4427 @@ +'\" t +.\" Copyright (c) 1994, 2017, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: java +.\" Language: English +.\" Date: 03 March 2015 +.\" SectDesc: Basic Tools +.\" Software: JDK 8 +.\" Arch: generic +.\" Part Number: E38209-04 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "java" "1" "03 March 2015" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +java \- Launches a Java application\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\fR [\fIoptions\fR] \fIclassname\fR [\fIargs\fR] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava\fR [\fIoptions\fR] \fB\-jar\fR \fIfilename\fR [\fIargs\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +Command\-line options separated by spaces\&. See Options\&. +.RE +.PP +\fIclassname\fR +.RS 4 +The name of the class to be launched\&. +.RE +.PP +\fIfilename\fR +.RS 4 +The name of the Java Archive (JAR) file to be called\&. Used only with the +\fB\-jar\fR +option\&. +.RE +.PP +\fIargs\fR +.RS 4 +The arguments passed to the +\fBmain()\fR +method separated by spaces\&. +.RE +.SH "DESCRIPTION" +.PP +The +\fBjava\fR +command starts a Java application\&. It does this by starting the Java Runtime Environment (JRE), loading the specified class, and calling that class\*(Aqs +\fBmain()\fR +method\&. The method must be declared +\fIpublic\fR +and +\fIstatic\fR, it must not return any value, and it must accept a +\fBString\fR +array as a parameter\&. The method declaration has the following form: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBpublic static void main(String[] args)\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The +\fBjava\fR +command can be used to launch a JavaFX application by loading a class that either has a +\fBmain()\fR +method or that extends +\fBjavafx\&.application\&.Application\fR\&. In the latter case, the launcher constructs an instance of the +\fBApplication\fR +class, calls its +\fBinit()\fR +method, and then calls the +\fBstart(javafx\&.stage\&.Stage)\fR +method\&. +.PP +By default, the first argument that is not an option of the +\fBjava\fR +command is the fully qualified name of the class to be called\&. If the +\fB\-jar\fR +option is specified, its argument is the name of the JAR file containing class and resource files for the application\&. The startup class must be indicated by the +\fBMain\-Class\fR +manifest header in its source code\&. +.PP +The JRE searches for the startup class (and other classes used by the application) in three sets of locations: the bootstrap class path, the installed extensions, and the user\(cqs class path\&. +.PP +Arguments after the class file name or the JAR file name are passed to the +\fBmain()\fR +method\&. +.SH "OPTIONS" +.PP +The +\fBjava\fR +command supports a wide range of options that can be divided into the following categories: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Standard Options +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Non\-Standard Options +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Advanced Runtime Options +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Advanced JIT Compiler Options +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Advanced Serviceability Options +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Advanced Garbage Collection Options +.RE +.PP +Standard options are guaranteed to be supported by all implementations of the Java Virtual Machine (JVM)\&. They are used for common actions, such as checking the version of the JRE, setting the class path, enabling verbose output, and so on\&. +.PP +Non\-standard options are general purpose options that are specific to the Java HotSpot Virtual Machine, so they are not guaranteed to be supported by all JVM implementations, and are subject to change\&. These options start with +\fB\-X\fR\&. +.PP +Advanced options are not recommended for casual use\&. These are developer options used for tuning specific areas of the Java HotSpot Virtual Machine operation that often have specific system requirements and may require privileged access to system configuration parameters\&. They are also not guaranteed to be supported by all JVM implementations, and are subject to change\&. Advanced options start with +\fB\-XX\fR\&. +.PP +To keep track of the options that were deprecated or removed in the latest release, there is a section named Deprecated and Removed Options at the end of the document\&. +.PP +Boolean options are used to either enable a feature that is disabled by default or disable a feature that is enabled by default\&. Such options do not require a parameter\&. Boolean +\fB\-XX\fR +options are enabled using the plus sign (\fB\-XX:+\fR\fIOptionName\fR) and disabled using the minus sign (\fB\-XX:\-\fR\fIOptionName\fR)\&. +.PP +For options that require an argument, the argument may be separated from the option name by a space, a colon (:), or an equal sign (=), or the argument may directly follow the option (the exact syntax differs for each option)\&. If you are expected to specify the size in bytes, you can use no suffix, or use the suffix +\fBk\fR +or +\fBK\fR +for kilobytes (KB), +\fBm\fR +or +\fBM\fR +for megabytes (MB), +\fBg\fR +or +\fBG\fR +for gigabytes (GB)\&. For example, to set the size to 8 GB, you can specify either +\fB8g\fR, +\fB8192m\fR, +\fB8388608k\fR, or +\fB8589934592\fR +as the argument\&. If you are expected to specify the percentage, use a number from 0 to 1 (for example, specify +\fB0\&.25\fR +for 25%)\&. +.SS "Standard Options" +.PP +These are the most commonly used options that are supported by all implementations of the JVM\&. +.PP +\-agentlib:\fIlibname\fR[=\fIoptions\fR] +.RS 4 +Loads the specified native agent library\&. After the library name, a comma\-separated list of options specific to the library can be used\&. +.sp +If the option +\fB\-agentlib:foo\fR +is specified, then the JVM attempts to load the library named +\fBlibfoo\&.so\fR +in the location specified by the +\fBLD_LIBRARY_PATH\fR +system variable (on OS X this variable is +\fBDYLD_LIBRARY_PATH\fR)\&. +.sp +The following example shows how to load the heap profiling tool (HPROF) library and get sample CPU information every 20 ms, with a stack depth of 3: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-agentlib:hprof=cpu=samples,interval=20,depth=3\fR + +.fi +.if n \{\ +.RE +.\} +The following example shows how to load the Java Debug Wire Protocol (JDWP) library and listen for the socket connection on port 8000, suspending the JVM before the main class loads: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-agentlib:jdwp=transport=dt_socket,server=y,address=8000\fR + +.fi +.if n \{\ +.RE +.\} +For more information about the native agent libraries, refer to the following: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The +\fBjava\&.lang\&.instrument\fR +package description at http://docs\&.oracle\&.com/javase/8/docs/api/java/lang/instrument/package\-summary\&.html +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Agent Command Line Options in the JVM Tools Interface guide at http://docs\&.oracle\&.com/javase/8/docs/platform/jvmti/jvmti\&.html#starting +.RE +.RE +.PP +\-agentpath:\fIpathname\fR[=\fIoptions\fR] +.RS 4 +Loads the native agent library specified by the absolute path name\&. This option is equivalent to +\fB\-agentlib\fR +but uses the full path and file name of the library\&. +.RE +.PP +\-client +.RS 4 +Selects the Java HotSpot Client VM\&. The 64\-bit version of the Java SE Development Kit (JDK) currently ignores this option and instead uses the Server JVM\&. +.sp +For default JVM selection, see Server\-Class Machine Detection at +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/server\-class\&.html +.RE +.PP +\-D\fIproperty\fR=\fIvalue\fR +.RS 4 +Sets a system property value\&. The +\fIproperty\fR +variable is a string with no spaces that represents the name of the property\&. The +\fIvalue\fR +variable is a string that represents the value of the property\&. If +\fIvalue\fR +is a string with spaces, then enclose it in quotation marks (for example +\fB\-Dfoo="foo bar"\fR)\&. +.RE +.PP +\-d32 +.RS 4 +Runs the application in a 32\-bit environment\&. If a 32\-bit environment is not installed or is not supported, then an error will be reported\&. By default, the application is run in a 32\-bit environment unless a 64\-bit system is used\&. +.RE +.PP +\-d64 +.RS 4 +Runs the application in a 64\-bit environment\&. If a 64\-bit environment is not installed or is not supported, then an error will be reported\&. By default, the application is run in a 32\-bit environment unless a 64\-bit system is used\&. +.sp +Currently only the Java HotSpot Server VM supports 64\-bit operation, and the +\fB\-server\fR +option is implicit with the use of +\fB\-d64\fR\&. The +\fB\-client\fR +option is ignored with the use of +\fB\-d64\fR\&. This is subject to change in a future release\&. +.RE +.PP +\-disableassertions[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.br +\-da[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.RS 4 +Disables assertions\&. By default, assertions are disabled in all packages and classes\&. +.sp +With no arguments, +\fB\-disableassertions\fR +(\fB\-da\fR) disables assertions in all packages and classes\&. With the +\fIpackagename\fR +argument ending in +\fB\&.\&.\&.\fR, the switch disables assertions in the specified package and any subpackages\&. If the argument is simply +\fB\&.\&.\&.\fR, then the switch disables assertions in the unnamed package in the current working directory\&. With the +\fIclassname\fR +argument, the switch disables assertions in the specified class\&. +.sp +The +\fB\-disableassertions\fR +(\fB\-da\fR) option applies to all class loaders and to system classes (which do not have a class loader)\&. There is one exception to this rule: if the option is provided with no arguments, then it does not apply to system classes\&. This makes it easy to disable assertions in all classes except for system classes\&. The +\fB\-disablesystemassertions\fR +option enables you to disable assertions in all system classes\&. +.sp +To explicitly enable assertions in specific packages or classes, use the +\fB\-enableassertions\fR +(\fB\-ea\fR) option\&. Both options can be used at the same time\&. For example, to run the +\fBMyClass\fR +application with assertions enabled in package +\fBcom\&.wombat\&.fruitbat\fR +(and any subpackages) but disabled in class +\fBcom\&.wombat\&.fruitbat\&.Brickbat\fR, use the following command: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-ea:com\&.wombat\&.fruitbat\&.\&.\&. \-da:com\&.wombat\&.fruitbat\&.Brickbat MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-disablesystemassertions +.br +\-dsa +.RS 4 +Disables assertions in all system classes\&. +.RE +.PP +\-enableassertions[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.br +\-ea[:[\fIpackagename\fR]\&.\&.\&.|:\fIclassname\fR] +.RS 4 +Enables assertions\&. By default, assertions are disabled in all packages and classes\&. +.sp +With no arguments, +\fB\-enableassertions\fR +(\fB\-ea\fR) enables assertions in all packages and classes\&. With the +\fIpackagename\fR +argument ending in +\fB\&.\&.\&.\fR, the switch enables assertions in the specified package and any subpackages\&. If the argument is simply +\fB\&.\&.\&.\fR, then the switch enables assertions in the unnamed package in the current working directory\&. With the +\fIclassname\fR +argument, the switch enables assertions in the specified class\&. +.sp +The +\fB\-enableassertions\fR +(\fB\-ea\fR) option applies to all class loaders and to system classes (which do not have a class loader)\&. There is one exception to this rule: if the option is provided with no arguments, then it does not apply to system classes\&. This makes it easy to enable assertions in all classes except for system classes\&. The +\fB\-enablesystemassertions\fR +option provides a separate switch to enable assertions in all system classes\&. +.sp +To explicitly disable assertions in specific packages or classes, use the +\fB\-disableassertions\fR +(\fB\-da\fR) option\&. If a single command contains multiple instances of these switches, then they are processed in order before loading any classes\&. For example, to run the +\fBMyClass\fR +application with assertions enabled only in package +\fBcom\&.wombat\&.fruitbat\fR +(and any subpackages) but disabled in class +\fBcom\&.wombat\&.fruitbat\&.Brickbat\fR, use the following command: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-ea:com\&.wombat\&.fruitbat\&.\&.\&. \-da:com\&.wombat\&.fruitbat\&.Brickbat MyClass\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-enablesystemassertions +.br +\-esa +.RS 4 +Enables assertions in all system classes\&. +.RE +.PP +\-help +.br +\-? +.RS 4 +Displays usage information for the +\fBjava\fR +command without actually running the JVM\&. +.RE +.PP +\-jar \fIfilename\fR +.RS 4 +Executes a program encapsulated in a JAR file\&. The +\fIfilename\fR +argument is the name of a JAR file with a manifest that contains a line in the form +\fBMain\-Class:\fR\fIclassname\fR +that defines the class with the +\fBpublic static void main(String[] args)\fR +method that serves as your application\*(Aqs starting point\&. +.sp +When you use the +\fB\-jar\fR +option, the specified JAR file is the source of all user classes, and other class path settings are ignored\&. +.sp +For more information about JAR files, see the following resources: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The Java Archive (JAR) Files guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jar/index\&.html +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Lesson: Packaging Programs in JAR Files at + +http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.html +.RE +.RE +.PP +\-javaagent:\fIjarpath\fR[=\fIoptions\fR] +.RS 4 +Loads the specified Java programming language agent\&. For more information about instrumenting Java applications, see the +\fBjava\&.lang\&.instrument\fR +package description in the Java API documentation at http://docs\&.oracle\&.com/javase/8/docs/api/java/lang/instrument/package\-summary\&.html +.RE +.PP +\-jre\-restrict\-search +.RS 4 +Includes user\-private JREs in the version search\&. +.RE +.PP +\-no\-jre\-restrict\-search +.RS 4 +Excludes user\-private JREs from the version search\&. +.RE +.PP +\-server +.RS 4 +Selects the Java HotSpot Server VM\&. The 64\-bit version of the JDK supports only the Server VM, so in that case the option is implicit\&. +.sp +For default JVM selection, see Server\-Class Machine Detection at +http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/server\-class\&.html +.RE +.PP +\-showversion +.RS 4 +Displays version information and continues execution of the application\&. This option is equivalent to the +\fB\-version\fR +option except that the latter instructs the JVM to exit after displaying version information\&. +.RE +.PP +\-splash:\fIimgname\fR +.RS 4 +Shows the splash screen with the image specified by +\fIimgname\fR\&. For example, to show the +\fBsplash\&.gif\fR +file from the +\fBimages\fR +directory when starting your application, use the following option: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-splash:images/splash\&.gif\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-verbose:class +.RS 4 +Displays information about each loaded class\&. +.RE +.PP +\-verbose:gc +.RS 4 +Displays information about each garbage collection (GC) event\&. +.RE +.PP +\-verbose:jni +.RS 4 +Displays information about the use of native methods and other Java Native Interface (JNI) activity\&. +.RE +.PP +\-version +.RS 4 +Displays version information and then exits\&. This option is equivalent to the +\fB\-showversion\fR +option except that the latter does not instruct the JVM to exit after displaying version information\&. +.RE +.PP +\-version:\fIrelease\fR +.RS 4 +Specifies the release version to be used for running the application\&. If the version of the +\fBjava\fR +command called does not meet this specification and an appropriate implementation is found on the system, then the appropriate implementation will be used\&. +.sp +The +\fIrelease\fR +argument specifies either the exact version string, or a list of version strings and ranges separated by spaces\&. A +\fIversion string\fR +is the developer designation of the version number in the following form: +\fB1\&.\fR\fIx\fR\fB\&.0_\fR\fIu\fR +(where +\fIx\fR +is the major version number, and +\fIu\fR +is the update version number)\&. A +\fIversion range\fR +is made up of a version string followed by a plus sign (\fB+\fR) to designate this version or later, or a part of a version string followed by an asterisk (\fB*\fR) to designate any version string with a matching prefix\&. Version strings and ranges can be combined using a space for a logical +\fIOR\fR +combination, or an ampersand (\fB&\fR) for a logical +\fIAND\fR +combination of two version strings/ranges\&. For example, if running the class or JAR file requires either JRE 6u13 (1\&.6\&.0_13), or any JRE 6 starting from 6u10 (1\&.6\&.0_10), specify the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-version:"1\&.6\&.0_13 1\&.6* & 1\&.6\&.0_10+"\fR + +.fi +.if n \{\ +.RE +.\} +Quotation marks are necessary only if there are spaces in the +\fIrelease\fR +parameter\&. +.sp +For JAR files, the preference is to specify version requirements in the JAR file manifest rather than on the command line\&. +.RE +.SS "Non\-Standard Options" +.PP +These options are general purpose options that are specific to the Java HotSpot Virtual Machine\&. +.PP +\-X +.RS 4 +Displays help for all available +\fB\-X\fR +options\&. +.RE +.PP +\-Xbatch +.RS 4 +Disables background compilation\&. By default, the JVM compiles the method as a background task, running the method in interpreter mode until the background compilation is finished\&. The +\fB\-Xbatch\fR +flag disables background compilation so that compilation of all methods proceeds as a foreground task until completed\&. +.sp +This option is equivalent to +\fB\-XX:\-BackgroundCompilation\fR\&. +.RE +.PP +\-Xbootclasspath:\fIpath\fR +.RS 4 +Specifies a list of directories, JAR files, and ZIP archives separated by colons (:) to search for boot class files\&. These are used in place of the boot class files included in the JDK\&. +.sp +Do not deploy applications that use this option to override a class in +\fBrt\&.jar\fR, because this violates the JRE binary code license\&. +.RE +.PP +\-Xbootclasspath/a:\fIpath\fR +.RS 4 +Specifies a list of directories, JAR files, and ZIP archives separated by colons (:) to append to the end of the default bootstrap class path\&. +.sp +Do not deploy applications that use this option to override a class in +\fBrt\&.jar\fR, because this violates the JRE binary code license\&. +.RE +.PP +\-Xbootclasspath/p:\fIpath\fR +.RS 4 +Specifies a list of directories, JAR files, and ZIP archives separated by colons (:) to prepend to the front of the default bootstrap class path\&. +.sp +Do not deploy applications that use this option to override a class in +\fBrt\&.jar\fR, because this violates the JRE binary code license\&. +.RE +.PP +\-Xcheck:jni +.RS 4 +Performs additional checks for Java Native Interface (JNI) functions\&. Specifically, it validates the parameters passed to the JNI function and the runtime environment data before processing the JNI request\&. Any invalid data encountered indicates a problem in the native code, and the JVM will terminate with an irrecoverable error in such cases\&. Expect a performance degradation when this option is used\&. +.RE +.PP +\-Xcomp +.RS 4 +Forces compilation of methods on first invocation\&. By default, the Client VM (\fB\-client\fR) performs 1,000 interpreted method invocations and the Server VM (\fB\-server\fR) performs 10,000 interpreted method invocations to gather information for efficient compilation\&. Specifying the +\fB\-Xcomp\fR +option disables interpreted method invocations to increase compilation performance at the expense of efficiency\&. +.sp +You can also change the number of interpreted method invocations before compilation using the +\fB\-XX:CompileThreshold\fR +option\&. +.RE +.PP +\-Xdebug +.RS 4 +Does nothing\&. Provided for backward compatibility\&. +.RE +.PP +\-Xdiag +.RS 4 +Shows additional diagnostic messages\&. +.RE +.PP +\-Xfuture +.RS 4 +Enables strict class\-file format checks that enforce close conformance to the class\-file format specification\&. Developers are encouraged to use this flag when developing new code because the stricter checks will become the default in future releases\&. +.RE +.PP +\-Xint +.RS 4 +Runs the application in interpreted\-only mode\&. Compilation to native code is disabled, and all bytecode is executed by the interpreter\&. The performance benefits offered by the just in time (JIT) compiler are not present in this mode\&. +.RE +.PP +\-Xinternalversion +.RS 4 +Displays more detailed JVM version information than the +\fB\-version\fR +option, and then exits\&. +.RE +.PP +\-Xloggc:\fIfilename\fR +.RS 4 +Sets the file to which verbose GC events information should be redirected for logging\&. The information written to this file is similar to the output of +\fB\-verbose:gc\fR +with the time elapsed since the first GC event preceding each logged event\&. The +\fB\-Xloggc\fR +option overrides +\fB\-verbose:gc\fR +if both are given with the same +\fBjava\fR +command\&. +.sp +Example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xloggc:garbage\-collection\&.log\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-Xmaxjitcodesize=\fIsize\fR +.RS 4 +Specifies the maximum code cache size (in bytes) for JIT\-compiled code\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default maximum code cache size is 240 MB; if you disable tiered compilation with the option +\fB\-XX:\-TieredCompilation\fR, then the default size is 48 MB: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmaxjitcodesize=240m\fR + +.fi +.if n \{\ +.RE +.\} +This option is equivalent to +\fB\-XX:ReservedCodeCacheSize\fR\&. +.RE +.PP +\-Xmixed +.RS 4 +Executes all bytecode by the interpreter except for hot methods, which are compiled to native code\&. +.RE +.PP +\-Xmn\fIsize\fR +.RS 4 +Sets the initial and maximum size (in bytes) of the heap for the young generation (nursery)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. +.sp +The young generation region of the heap is used for new objects\&. GC is performed in this region more often than in other regions\&. If the size for the young generation is too small, then a lot of minor garbage collections will be performed\&. If the size is too large, then only full garbage collections will be performed, which can take a long time to complete\&. Oracle recommends that you keep the size for the young generation between a half and a quarter of the overall heap size\&. +.sp +The following examples show how to set the initial and maximum size of young generation to 256 MB using various units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmn256m\fR +\fB\-Xmn262144k\fR +\fB\-Xmn268435456\fR + +.fi +.if n \{\ +.RE +.\} +Instead of the +\fB\-Xmn\fR +option to set both the initial and maximum size of the heap for the young generation, you can use +\fB\-XX:NewSize\fR +to set the initial size and +\fB\-XX:MaxNewSize\fR +to set the maximum size\&. +.RE +.PP +\-Xms\fIsize\fR +.RS 4 +Sets the initial size (in bytes) of the heap\&. This value must be a multiple of 1024 and greater than 1 MB\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. +.sp +The following examples show how to set the size of allocated memory to 6 MB using various units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xms6291456\fR +\fB\-Xms6144k\fR +\fB\-Xms6m\fR + +.fi +.if n \{\ +.RE +.\} +If you do not set this option, then the initial size will be set as the sum of the sizes allocated for the old generation and the young generation\&. The initial size of the heap for the young generation can be set using the +\fB\-Xmn\fR +option or the +\fB\-XX:NewSize\fR +option\&. +.RE +.PP +\-Xmx\fIsize\fR +.RS 4 +Specifies the maximum size (in bytes) of the memory allocation pool in bytes\&. This value must be a multiple of 1024 and greater than 2 MB\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default value is chosen at runtime based on system configuration\&. For server deployments, +\fB\-Xms\fR +and +\fB\-Xmx\fR +are often set to the same value\&. See the section "Ergonomics" in +\fIJava SE HotSpot Virtual Machine Garbage Collection Tuning Guide\fR +at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.html\&. +.sp +The following examples show how to set the maximum allowed size of allocated memory to 80 MB using various units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xmx83886080\fR +\fB\-Xmx81920k\fR +\fB\-Xmx80m\fR + +.fi +.if n \{\ +.RE +.\} +The +\fB\-Xmx\fR +option is equivalent to +\fB\-XX:MaxHeapSize\fR\&. +.RE +.PP +\-Xnoclassgc +.RS 4 +Disables garbage collection (GC) of classes\&. This can save some GC time, which shortens interruptions during the application run\&. +.sp +When you specify +\fB\-Xnoclassgc\fR +at startup, the class objects in the application will be left untouched during GC and will always be considered live\&. This can result in more memory being permanently occupied which, if not used carefully, will throw an out of memory exception\&. +.RE +.PP +\-Xprof +.RS 4 +Profiles the running program and sends profiling data to standard output\&. This option is provided as a utility that is useful in program development and is not intended to be used in production systems\&. +.RE +.PP +\-Xrs +.RS 4 +Reduces the use of operating system signals by the JVM\&. +.sp +Shutdown hooks enable orderly shutdown of a Java application by running user cleanup code (such as closing database connections) at shutdown, even if the JVM terminates abruptly\&. +.sp +The JVM catches signals to implement shutdown hooks for unexpected termination\&. The JVM uses +\fBSIGHUP\fR, +\fBSIGINT\fR, and +\fBSIGTERM\fR +to initiate the running of shutdown hooks\&. +.sp +The JVM uses a similar mechanism to implement the feature of dumping thread stacks for debugging purposes\&. The JVM uses +\fBSIGQUIT\fR +to perform thread dumps\&. +.sp +Applications embedding the JVM frequently need to trap signals such as +\fBSIGINT\fR +or +\fBSIGTERM\fR, which can lead to interference with the JVM signal handlers\&. The +\fB\-Xrs\fR +option is available to address this issue\&. When +\fB\-Xrs\fR +is used, the signal masks for +\fBSIGINT\fR, +\fBSIGTERM\fR, +\fBSIGHUP\fR, and +\fBSIGQUIT\fR +are not changed by the JVM, and signal handlers for these signals are not installed\&. +.sp +There are two consequences of specifying +\fB\-Xrs\fR: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBSIGQUIT\fR +thread dumps are not available\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +User code is responsible for causing shutdown hooks to run, for example, by calling +\fBSystem\&.exit()\fR +when the JVM is to be terminated\&. +.RE +.RE +.PP +\-Xshare:\fImode\fR +.RS 4 +Sets the class data sharing (CDS) mode\&. Possible +\fImode\fR +arguments for this option include the following: +.PP +auto +.RS 4 +Use CDS if possible\&. This is the default value for Java HotSpot 32\-Bit Client VM\&. +.RE +.PP +on +.RS 4 +Require the use of CDS\&. Print an error message and exit if class data sharing cannot be used\&. +.RE +.PP +off +.RS 4 +Do not use CDS\&. This is the default value for Java HotSpot 32\-Bit Server VM, Java HotSpot 64\-Bit Client VM, and Java HotSpot 64\-Bit Server VM\&. +.RE +.PP +dump +.RS 4 +Manually generate the CDS archive\&. Specify the application class path as described in "Setting the Class Path "\&. +.sp +You should regenerate the CDS archive with each new JDK release\&. +.RE +.RE +.PP +\-XshowSettings:\fIcategory\fR +.RS 4 +Shows settings and continues\&. Possible +\fIcategory\fR +arguments for this option include the following: +.PP +all +.RS 4 +Shows all categories of settings\&. This is the default value\&. +.RE +.PP +locale +.RS 4 +Shows settings related to locale\&. +.RE +.PP +properties +.RS 4 +Shows settings related to system properties\&. +.RE +.PP +vm +.RS 4 +Shows the settings of the JVM\&. +.RE +.RE +.PP +\-Xss\fIsize\fR +.RS 4 +Sets the thread stack size (in bytes)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate KB, +\fBm\fR +or +\fBM\fR +to indicate MB, +\fBg\fR +or +\fBG\fR +to indicate GB\&. The default value depends on the platform: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/ARM (32\-bit): 320 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/i386 (32\-bit): 320 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/x64 (64\-bit): 1024 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OS X (64\-bit): 1024 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/i386 (32\-bit): 320 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/x64 (64\-bit): 1024 KB +.RE +.sp +The following examples set the thread stack size to 1024 KB in different units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Xss1m\fR +\fB\-Xss1024k\fR +\fB\-Xss1048576\fR + +.fi +.if n \{\ +.RE +.\} +This option is equivalent to +\fB\-XX:ThreadStackSize\fR\&. +.RE +.PP +\-Xusealtsigs +.RS 4 +Use alternative signals instead of +\fBSIGUSR1\fR +and +\fBSIGUSR2\fR +for JVM internal signals\&. This option is equivalent to +\fB\-XX:+UseAltSigs\fR\&. +.RE + +.PP +\-Xverify:\fImode\fR +.RS 4 +Sets the mode of the bytecode verifier\&. Bytecode verification ensures that class files are properly formed and satisfy the constraints listed in section 4.10, "Verification of class Files" in the \fIThe Java Virtual Machine Specification\fR: +.sp +https://docs\&.oracle.com/javase/specs/jvms/se8/html/jvms-4\&.html#jvms-4\&.10 +.sp +Do not turn off verification as this reduces the protection provided by Java and could cause problems due to ill-formed class files\&. +.sp +Possible +\fImode\fR +arguments for this option include the following: +.PP +remote +.RS 4 +Verifies all bytecodes not loaded by the bootstrap class loader\&. This is the default behavior if you do not specify the +\fB\-Xverify\fR +option\&. +.RE +.PP +all +.RS 4 +Enables verification of all bytecodes\&. +.RE +.PP +none +.RS 4 +Disables verification of all bytecodes\&. Use of +\fB\-Xverify:none\fR +is unsupported\&. +.RE +.RE +.SS "Advanced Runtime Options" +.PP +These options control the runtime behavior of the Java HotSpot VM\&. +.PP +\-XX:+CheckEndorsedAndExtDirs +.RS 4 +Enables the option to prevent the +\fBjava\fR +command from running a Java application if it uses the endorsed\-standards override mechanism or the extension mechanism\&. This option checks if an application is using one of these mechanisms by checking the following: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The +\fBjava\&.ext\&.dirs\fR +or +\fBjava\&.endorsed\&.dirs\fR +system property is set\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The +\fBlib/endorsed\fR +directory exists and is not empty\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The +\fBlib/ext\fR +directory contains any JAR files other than those of the JDK\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The system\-wide platform\-specific extension directory contains any JAR files\&. +.RE +.RE +.PP +\-XX:+DisableAttachMechanism +.RS 4 +Enables the option that disables the mechanism that lets tools attach to the JVM\&. By default, this option is disabled, meaning that the attach mechanism is enabled and you can use tools such as +\fBjcmd\fR, +\fBjstack\fR, +\fBjmap\fR, and +\fBjinfo\fR\&. +.RE +.PP +\-XX:ErrorFile=\fIfilename\fR +.RS 4 +Specifies the path and file name to which error data is written when an irrecoverable error occurs\&. By default, this file is created in the current working directory and named +\fBhs_err_pid\fR\fIpid\fR\fB\&.log\fR +where +\fIpid\fR +is the identifier of the process that caused the error\&. The following example shows how to set the default log file (note that the identifier of the process is specified as +\fB%p\fR): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ErrorFile=\&./hs_err_pid%p\&.log\fR + +.fi +.if n \{\ +.RE +.\} +The following example shows how to set the error log to +\fB/var/log/java/java_error\&.log\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ErrorFile=/var/log/java/java_error\&.log\fR + +.fi +.if n \{\ +.RE +.\} +If the file cannot be created in the specified directory (due to insufficient space, permission problem, or another issue), then the file is created in the temporary directory for the operating system\&. The temporary directory is +\fB/tmp\fR\&. +.RE +.PP +\-XX:+FailOverToOldVerifier +.RS 4 +Enables automatic failover to the old verifier when the new type checker fails\&. By default, this option is disabled and it is ignored (that is, treated as disabled) for classes with a recent bytecode version\&. You can enable it for classes with older versions of the bytecode\&. +.RE +.PP +\-XX:+FlightRecorder +.RS 4 +Enables the use of the Java Flight Recorder (JFR) during the runtime of the application\&. This is a commercial feature that works in conjunction with the +\fB\-XX:+UnlockCommercialFeatures\fR +option as follows: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-XX:+UnlockCommercialFeatures \-XX:+FlightRecorder\fR + +.fi +.if n \{\ +.RE +.\} +If this option is not provided, Java Flight Recorder can still be enabled in a running JVM by providing the appropriate +\fBjcmd\fR +diagnostic commands\&. +.RE +.PP +\-XX:\-FlightRecorder +.RS 4 +Disables the use of the Java Flight Recorder (JFR) during the runtime of the application\&. This is a commercial feature that works in conjunction with the +\fB\-XX:+UnlockCommercialFeatures\fR +option as follows: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-XX:+UnlockCommercialFeatures \-XX:\-FlightRecorder\fR + +.fi +.if n \{\ +.RE +.\} +If this option is provided, Java Flight Recorder cannot be enabled in a running JVM\&. +.RE +.PP +\-XX:FlightRecorderOptions=\fIparameter\fR=\fIvalue\fR +.RS 4 +Sets the parameters that control the behavior of JFR\&. This is a commercial feature that works in conjunction with the +\fB\-XX:+UnlockCommercialFeatures\fR +option\&. This option can be used only when JFR is enabled (that is, the +\fB\-XX:+FlightRecorder\fR +option is specified)\&. +.sp +The following list contains all available JFR parameters: +.PP +defaultrecording={true|false} +.RS 4 +Specifies whether the recording is a continuous background recording or if it runs for a limited time\&. By default, this parameter is set to +\fBfalse\fR +(recording runs for a limited time)\&. To make the recording run continuously, set the parameter to +\fBtrue\fR\&. +.RE +.PP +disk={true|false} +.RS 4 +Specifies whether JFR should write a continuous recording to disk\&. By default, this parameter is set to +\fBfalse\fR +(continuous recording to disk is disabled)\&. To enable it, set the parameter to +\fBtrue\fR, and also set +\fBdefaultrecording=true\fR\&. +.RE +.PP +dumponexit={true|false} +.RS 4 +Specifies whether a dump file of JFR data should be generated when the JVM terminates in a controlled manner\&. By default, this parameter is set to +\fBfalse\fR +(dump file on exit is not generated)\&. To enable it, set the parameter to +\fBtrue\fR, and also set +\fBdefaultrecording=true\fR\&. +.sp +The dump file is written to the location defined by the +\fBdumponexitpath\fR +parameter\&. +.RE +.PP +dumponexitpath=\fIpath\fR +.RS 4 +Specifies the path and name of the dump file with JFR data that is created when the JVM exits in a controlled manner if you set the +\fBdumponexit=true\fR +parameter\&. Setting the path makes sense only if you also set +\fBdefaultrecording=true\fR\&. +.sp +If the specified path is a directory, the JVM assigns a file name that shows the creation date and time\&. If the specified path includes a file name and if that file already exists, the JVM creates a new file by appending the date and time stamp to the specified file name\&. +.RE +.PP +globalbuffersize=\fIsize\fR +.RS 4 +Specifies the total amount of primary memory (in bytes) used for data retention\&. Append +\fBk\fR +or +\fBK\fR, to specify the size in KB, +\fBm\fR +or +\fBM\fR +to specify the size in MB, +\fBg\fR +or +\fBG\fR +to specify the size in GB\&. By default, the size is set to 462848 bytes\&. +.RE +.PP +loglevel={quiet|error|warning|info|debug|trace} +.RS 4 +Specify the amount of data written to the log file by JFR\&. By default, it is set to +\fBinfo\fR\&. +.RE +.PP +maxage=\fItime\fR +.RS 4 +Specifies the maximum age of disk data to keep for the default recording\&. Append +\fBs\fR +to specify the time in seconds, +\fBm\fR +for minutes, +\fBh\fR +for hours, or +\fBd\fR +for days (for example, specifying +\fB30s\fR +means 30 seconds)\&. By default, the maximum age is set to 15 minutes (\fB15m\fR)\&. +.sp +This parameter is valid only if you set the +\fBdisk=true\fR +parameter\&. +.RE +.PP +maxchunksize=\fIsize\fR +.RS 4 +Specifies the maximum size (in bytes) of the data chunks in a recording\&. Append +\fBk\fR +or +\fBK\fR, to specify the size in KB, +\fBm\fR +or +\fBM\fR +to specify the size in MB, +\fBg\fR +or +\fBG\fR +to specify the size in GB\&. By default, the maximum size of data chunks is set to 12 MB\&. +.RE +.PP +maxsize=\fIsize\fR +.RS 4 +Specifies the maximum size (in bytes) of disk data to keep for the default recording\&. Append +\fBk\fR +or +\fBK\fR, to specify the size in KB, +\fBm\fR +or +\fBM\fR +to specify the size in MB, +\fBg\fR +or +\fBG\fR +to specify the size in GB\&. By default, the maximum size of disk data is not limited, and this parameter is set to 0\&. +.sp +This parameter is valid only if you set the +\fBdisk=true\fR +parameter\&. +.RE +.PP +repository=\fIpath\fR +.RS 4 +Specifies the repository (a directory) for temporary disk storage\&. By default, the system\(cqs temporary directory is used\&. +.RE +.PP +samplethreads={true|false} +.RS 4 +Specifies whether thread sampling is enabled\&. Thread sampling occurs only if the sampling event is enabled along with this parameter\&. By default, this parameter is enabled\&. +.RE +.PP +settings=\fIpath\fR +.RS 4 +Specifies the path and name of the event settings file (of type JFC)\&. By default, the +\fBdefault\&.jfc\fR +file is used, which is located in +\fBJAVA_HOME/jre/lib/jfr\fR\&. +.RE +.PP +stackdepth=\fIdepth\fR +.RS 4 +Stack depth for stack traces by JFR\&. By default, the depth is set to 64 method calls\&. The maximum is 2048, minimum is 1\&. +.RE +.PP +threadbuffersize=\fIsize\fR +.RS 4 +Specifies the per\-thread local buffer size (in bytes)\&. Append +\fBk\fR +or +\fBK\fR, to specify the size in KB, +\fBm\fR +or +\fBM\fR +to specify the size in MB, +\fBg\fR +or +\fBG\fR +to specify the size in GB\&. Higher values for this parameter allow more data gathering without contention to flush it to the global storage\&. It can increase application footprint in a thread\-rich environment\&. By default, the local buffer size is set to 5 KB\&. +.RE +.sp +You can specify values for multiple parameters by separating them with a comma\&. For example, to instruct JFR to write a continuous recording to disk, and set the maximum size of data chunks to 10 MB, specify the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:FlightRecorderOptions=defaultrecording=true,disk=true,maxchunksize=10M\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:LargePageSizeInBytes=\fIsize\fR +.RS 4 +On Solaris, sets the maximum size (in bytes) for large pages used for Java heap\&. The +\fIsize\fR +argument must be a power of 2 (2, 4, 8, 16, \&.\&.\&.)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. By default, the size is set to 0, meaning that the JVM chooses the size for large pages automatically\&. +.sp +The following example illustrates how to set the large page size to 4 megabytes (MB): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:LargePageSizeInBytes=4m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxDirectMemorySize=\fIsize\fR +.RS 4 +Sets the maximum total size (in bytes) of the New I/O (the +\fBjava\&.nio\fR +package) direct\-buffer allocations\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. By default, the size is set to 0, meaning that the JVM chooses the size for NIO direct\-buffer allocations automatically\&. +.sp +The following examples illustrate how to set the NIO size to 1024 KB in different units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxDirectMemorySize=1m\fR +\fB\-XX:MaxDirectMemorySize=1024k\fR +\fB\-XX:MaxDirectMemorySize=1048576\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NativeMemoryTracking=\fImode\fR +.RS 4 +Specifies the mode for tracking JVM native memory usage\&. Possible +\fImode\fR +arguments for this option include the following: +.PP +off +.RS 4 +Do not track JVM native memory usage\&. This is the default behavior if you do not specify the +\fB\-XX:NativeMemoryTracking\fR +option\&. +.RE +.PP +summary +.RS 4 +Only track memory usage by JVM subsystems, such as Java heap, class, code, and thread\&. +.RE +.PP +detail +.RS 4 +In addition to tracking memory usage by JVM subsystems, track memory usage by individual +\fBCallSite\fR, individual virtual memory region and its committed regions\&. +.RE +.RE +.PP +\-XX:ObjectAlignmentInBytes=\fIalignment\fR +.RS 4 +Sets the memory alignment of Java objects (in bytes)\&. By default, the value is set to 8 bytes\&. The specified value should be a power of two, and must be within the range of 8 and 256 (inclusive)\&. This option makes it possible to use compressed pointers with large Java heap sizes\&. +.sp +The heap size limit in bytes is calculated as: +.sp +\fB4GB * ObjectAlignmentInBytes\fR +.sp +Note: As the alignment value increases, the unused space between objects will also increase\&. As a result, you may not realize any benefits from using compressed pointers with large Java heap sizes\&. +.RE +.PP +\-XX:OnError=\fIstring\fR +.RS 4 +Sets a custom command or a series of semicolon\-separated commands to run when an irrecoverable error occurs\&. If the string contains spaces, then it must be enclosed in quotation marks\&. +.sp +The following example shows how the +\fB\-XX:OnError\fR +option can be used to run the +\fBgcore\fR +command to create the core image, and the debugger is started to attach to the process in case of an irrecoverable error (the +\fB%p\fR +designates the current process): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:OnError="gcore %p;dbx \- %p"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:OnOutOfMemoryError=\fIstring\fR +.RS 4 +Sets a custom command or a series of semicolon\-separated commands to run when an +\fBOutOfMemoryError\fR +exception is first thrown\&. If the string contains spaces, then it must be enclosed in quotation marks\&. For an example of a command string, see the description of the +\fB\-XX:OnError\fR +option\&. +.RE +.PP +\-XX:+PerfDataSaveToFile +.RS 4 +If enabled, saves +jstat(1) binary data when the Java application exits\&. This binary data is saved in a file named +\fBhsperfdata_\fR\fI<pid>\fR, where +\fI<pid>\fR +is the process identifier of the Java application you ran\&. Use +\fBjstat\fR +to display the performance data contained in this file as follows: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-class file:///\fR\fB\fI<path>\fR\fR\fB/hsperfdata_\fR\fB\fI<pid>\fR\fR +\fBjstat \-gc file:///\fR\fB\fI<path>\fR\fR\fB/hsperfdata_\fR\fB\fI<pid>\fR\fR +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+PrintCommandLineFlags +.RS 4 +Enables printing of ergonomically selected JVM flags that appeared on the command line\&. It can be useful to know the ergonomic values set by the JVM, such as the heap space size and the selected garbage collector\&. By default, this option is disabled and flags are not printed\&. +.RE +.PP +\-XX:+PrintNMTStatistics +.RS 4 +Enables printing of collected native memory tracking data at JVM exit when native memory tracking is enabled (see +\fB\-XX:NativeMemoryTracking\fR)\&. By default, this option is disabled and native memory tracking data is not printed\&. +.RE +.PP +\-XX:+RelaxAccessControlCheck +.RS 4 +Decreases the amount of access control checks in the verifier\&. By default, this option is disabled, and it is ignored (that is, treated as disabled) for classes with a recent bytecode version\&. You can enable it for classes with older versions of the bytecode\&. +.RE +.PP +\-XX:+ResourceManagement +.RS 4 +Enables the use of Resource Management during the runtime of the application\&. +.sp +This is a commercial feature that requires you to also specify the +\fB\-XX:+UnlockCommercialFeatures\fR +option as follows: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-XX:+ResourceManagement\fR +.RE +.PP +\-XX:ResourceManagementSampleInterval=\fIvalue\fR (milliseconds) +.RS 4 +Sets the parameter that controls the sampling interval for Resource Management measurements, in milliseconds\&. +.sp +This option can be used only when Resource Management is enabled (that is, the +\fB\-XX:+ResourceManagement\fR +option is specified)\&. +.RE +.PP +\-XX:SharedArchiveFile=\fIpath\fR +.RS 4 +Specifies the path and name of the class data sharing (CDS) archive file +.RE +.PP +\-XX:SharedClassListFile=\fIfile_name\fR +.RS 4 +Specifies the text file that contains the names of the class files to store in the class data sharing (CDS) archive\&. This file contains the full name of one class file per line, except slashes (\fB/\fR) replace dots (\fB\&.\fR)\&. For example, to specify the classes +\fBjava\&.lang\&.Object\fR +and +\fBhello\&.Main\fR, create a text file that contains the following two lines: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava/lang/Object\fR +\fBhello/Main\fR + +.fi +.if n \{\ +.RE +.\} +The class files that you specify in this text file should include the classes that are commonly used by the application\&. They may include any classes from the application, extension, or bootstrap class paths\&. +.RE +.PP +\-XX:+ShowMessageBoxOnError +.RS 4 +Enables displaying of a dialog box when the JVM experiences an irrecoverable error\&. This prevents the JVM from exiting and keeps the process active so that you can attach a debugger to it to investigate the cause of the error\&. By default, this option is disabled\&. +.RE +.PP +\-XX:StartFlightRecording=\fIparameter\fR=\fIvalue\fR +.RS 4 +Starts a JFR recording for the Java application\&. This is a commercial feature that works in conjunction with the +\fB\-XX:+UnlockCommercialFeatures\fR +option\&. This option is equivalent to the +\fBJFR\&.start\fR +diagnostic command that starts a recording during runtime\&. You can set the following parameters when starting a JFR recording: +.PP +compress={true|false} +.RS 4 +Specifies whether to compress the JFR recording log file (of type JFR) on the disk using the +\fBgzip\fR +file compression utility\&. This parameter is valid only if the +\fBfilename\fR +parameter is specified\&. By default it is set to +\fBfalse\fR +(recording is not compressed)\&. To enable compression, set the parameter to +\fBtrue\fR\&. +.RE +.PP +defaultrecording={true|false} +.RS 4 +Specifies whether the recording is a continuous background recording or if it runs for a limited time\&. By default, this parameter is set to +\fBfalse\fR +(recording runs for a limited time)\&. To make the recording run continuously, set the parameter to +\fBtrue\fR\&. +.RE +.PP +delay=\fItime\fR +.RS 4 +Specifies the delay between the Java application launch time and the start of the recording\&. Append +\fBs\fR +to specify the time in seconds, +\fBm\fR +for minutes, +\fBh\fR +for hours, or +\fBd\fR +for days (for example, specifying +\fB10m\fR +means 10 minutes)\&. By default, there is no delay, and this parameter is set to 0\&. +.RE +.PP +dumponexit={true|false} +.RS 4 +Specifies whether a dump file of JFR data should be generated when the JVM terminates in a controlled manner\&. By default, this parameter is set to +\fBfalse\fR +(dump file on exit is not generated)\&. To enable it, set the parameter to +\fBtrue\fR\&. +.sp +The dump file is written to the location defined by the +\fBfilename\fR +parameter\&. +.sp +Example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:StartFlightRecording=name=test,filename=D:\etest\&.jfr,dumponexit=true\fR +.fi +.if n \{\ +.RE +.\} +.RE +.PP +duration=\fItime\fR +.RS 4 +Specifies the duration of the recording\&. Append +\fBs\fR +to specify the time in seconds, +\fBm\fR +for minutes, +\fBh\fR +for hours, or +\fBd\fR +for days (for example, specifying +\fB5h\fR +means 5 hours)\&. By default, the duration is not limited, and this parameter is set to 0\&. +.RE +.PP +filename=\fIpath\fR +.RS 4 +Specifies the path and name of the JFR recording log file\&. +.RE +.PP +name=\fIidentifier\fR +.RS 4 +Specifies the identifier for the JFR recording\&. By default, it is set to +\fBRecording x\fR\&. +.RE +.PP +maxage=\fItime\fR +.RS 4 +Specifies the maximum age of disk data to keep for the default recording\&. Append +\fBs\fR +to specify the time in seconds, +\fBm\fR +for minutes, +\fBh\fR +for hours, or +\fBd\fR +for days (for example, specifying +\fB30s\fR +means 30 seconds)\&. By default, the maximum age is set to 15 minutes (\fB15m\fR)\&. +.RE +.PP +maxsize=\fIsize\fR +.RS 4 +Specifies the maximum size (in bytes) of disk data to keep for the default recording\&. Append +\fBk\fR +or +\fBK\fR, to specify the size in KB, +\fBm\fR +or +\fBM\fR +to specify the size in MB, +\fBg\fR +or +\fBG\fR +to specify the size in GB\&. By default, the maximum size of disk data is not limited, and this parameter is set to 0\&. +.RE +.PP +settings=\fIpath\fR +.RS 4 +Specifies the path and name of the event settings file (of type JFC)\&. By default, the +\fBdefault\&.jfc\fR +file is used, which is located in +\fBJAVA_HOME/jre/lib/jfr\fR\&. +.RE +.sp +You can specify values for multiple parameters by separating them with a comma\&. For example, to save the recording to test\&.jfr in the current working directory, and instruct JFR to compress the log file, specify the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:StartFlightRecording=filename=test\&.jfr,compress=true\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:ThreadStackSize=\fIsize\fR +.RS 4 +Sets the thread stack size (in bytes)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default value depends on the platform: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/ARM (32\-bit): 320 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/i386 (32\-bit): 320 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Linux/x64 (64\-bit): 1024 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +OS X (64\-bit): 1024 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/i386 (32\-bit): 320 KB +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Oracle Solaris/x64 (64\-bit): 1024 KB +.RE +.sp +The following examples show how to set the thread stack size to 1024 KB in different units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ThreadStackSize=1m\fR +\fB\-XX:ThreadStackSize=1024k\fR +\fB\-XX:ThreadStackSize=1048576\fR + +.fi +.if n \{\ +.RE +.\} +This option is equivalent to +\fB\-Xss\fR\&. +.RE +.PP +\-XX:+TraceClassLoading +.RS 4 +Enables tracing of classes as they are loaded\&. By default, this option is disabled and classes are not traced\&. +.RE +.PP +\-XX:+TraceClassLoadingPreorder +.RS 4 +Enables tracing of all loaded classes in the order in which they are referenced\&. By default, this option is disabled and classes are not traced\&. +.RE +.PP +\-XX:+TraceClassResolution +.RS 4 +Enables tracing of constant pool resolutions\&. By default, this option is disabled and constant pool resolutions are not traced\&. +.RE +.PP +\-XX:+TraceClassUnloading +.RS 4 +Enables tracing of classes as they are unloaded\&. By default, this option is disabled and classes are not traced\&. +.RE +.PP +\-XX:+TraceLoaderConstraints +.RS 4 +Enables tracing of the loader constraints recording\&. By default, this option is disabled and loader constraints recording is not traced\&. +.RE +.PP +\-XX:+UnlockCommercialFeatures +.RS 4 +Enables the use of commercial features\&. Commercial features are included with Oracle Java SE Advanced or Oracle Java SE Suite packages, as defined on the +\fIJava SE Products\fR +page at http://www\&.oracle\&.com/technetwork/java/javase/terms/products/index\&.html +.sp +By default, this option is disabled and the JVM runs without the commercial features\&. Once they were enabled for a JVM process, it is not possible to disable their use for that process\&. +.sp +If this option is not provided, commercial features can still be unlocked in a running JVM by using the appropriate +\fBjcmd\fR +diagnostic commands\&. +.RE +.PP +\-XX:+UseAltSigs +.RS 4 +Enables the use of alternative signals instead of +\fBSIGUSR1\fR +and +\fBSIGUSR2\fR +for JVM internal signals\&. By default, this option is disabled and alternative signals are not used\&. This option is equivalent to +\fB\-Xusealtsigs\fR\&. +.RE +.PP +\-XX:+UseAppCDS +.RS 4 +Enables application class data sharing (AppCDS)\&. To use AppCDS, you must also specify values for the options +\fB\-XX:SharedClassListFile\fR +and +\fB\-XX:SharedArchiveFile\fR +during both CDS dump time (see the option +\fB\-Xshare:dump\fR) and application run time\&. +.sp +This is a commercial feature that requires you to also specify the +\fB\-XX:+UnlockCommercialFeatures\fR +option\&. This is also an experimental feature; it may change in future releases\&. +.sp +See "Application Class Data Sharing"\&. +.RE +.PP +\-XX:\-UseBiasedLocking +.RS 4 +Disables the use of biased locking\&. Some applications with significant amounts of uncontended synchronization may attain significant speedups with this flag enabled, whereas applications with certain patterns of locking may see slowdowns\&. For more information about the biased locking technique, see the example in Java Tuning White Paper at http://www\&.oracle\&.com/technetwork/java/tuning\-139912\&.html#section4\&.2\&.5 +.sp +By default, this option is enabled\&. +.RE +.PP +\-XX:\-UseCompressedOops +.RS 4 +Disables the use of compressed pointers\&. By default, this option is enabled, and compressed pointers are used when Java heap sizes are less than 32 GB\&. When this option is enabled, object references are represented as 32\-bit offsets instead of 64\-bit pointers, which typically increases performance when running the application with Java heap sizes less than 32 GB\&. This option works only for 64\-bit JVMs\&. +.sp +It is also possible to use compressed pointers when Java heap sizes are greater than 32GB\&. See the +\fB\-XX:ObjectAlignmentInBytes\fR +option\&. +.RE +.PP +\-XX:+UseHugeTLBFS +.RS 4 +This option for Linux is the equivalent of specifying +\fB\-XX:+UseLargePages\fR\&. This option is disabled by default\&. This option pre\-allocates all large pages up\-front, when memory is reserved; consequently the JVM cannot dynamically grow or shrink large pages memory areas; see +\fB\-XX:UseTransparentHugePages\fR +if you want this behavior\&. +.sp +For more information, see "Large Pages"\&. +.RE +.PP +\-XX:+UseLargePages +.RS 4 +Enables the use of large page memory\&. By default, this option is disabled and large page memory is not used\&. +.sp +For more information, see "Large Pages"\&. +.RE +.PP +\-XX:+UseMembar +.RS 4 +Enables issuing of membars on thread state transitions\&. This option is disabled by default on all platforms except ARM servers, where it is enabled\&. (It is recommended that you do not disable this option on ARM servers\&.) +.RE +.PP +\-XX:+UsePerfData +.RS 4 +Enables the +\fBperfdata\fR +feature\&. This option is enabled by default to allow JVM monitoring and performance testing\&. Disabling it suppresses the creation of the +\fBhsperfdata_userid\fR +directories\&. To disable the +\fBperfdata\fR +feature, specify +\fB\-XX:\-UsePerfData\fR\&. +.RE +.PP +\-XX:+UseTransparentHugePages +.RS 4 +On Linux, enables the use of large pages that can dynamically grow or shrink\&. This option is disabled by default\&. You may encounter performance problems with transparent huge pages as the OS moves other pages around to create huge pages; this option is made available for experimentation\&. +.sp +For more information, see "Large Pages"\&. +.RE +.PP +\-XX:+AllowUserSignalHandlers +.RS 4 +Enables installation of signal handlers by the application\&. By default, this option is disabled and the application is not allowed to install signal handlers\&. +.RE +.SS "Advanced JIT Compiler Options" +.PP +These options control the dynamic just\-in\-time (JIT) compilation performed by the Java HotSpot VM\&. +.PP +\-XX:+AggressiveOpts +.RS 4 +Enables the use of aggressive performance optimization features, which are expected to become default in upcoming releases\&. By default, this option is disabled and experimental performance features are not used\&. +.RE +.PP +\-XX:AllocateInstancePrefetchLines=\fIlines\fR +.RS 4 +Sets the number of lines to prefetch ahead of the instance allocation pointer\&. By default, the number of lines to prefetch is set to 1: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocateInstancePrefetchLines=1\fR + +.fi +.if n \{\ +.RE +.\} +Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:AllocatePrefetchDistance=\fIsize\fR +.RS 4 +Sets the size (in bytes) of the prefetch distance for object allocation\&. Memory about to be written with the value of new objects is prefetched up to this distance starting from the address of the last allocated object\&. Each Java thread has its own allocation point\&. +.sp +Negative values denote that prefetch distance is chosen based on the platform\&. Positive values are bytes to prefetch\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default value is set to \-1\&. +.sp +The following example shows how to set the prefetch distance to 1024 bytes: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchDistance=1024\fR + +.fi +.if n \{\ +.RE +.\} +Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:AllocatePrefetchInstr=\fIinstruction\fR +.RS 4 +Sets the prefetch instruction to prefetch ahead of the allocation pointer\&. Only the Java HotSpot Server VM supports this option\&. Possible values are from 0 to 3\&. The actual instructions behind the values depend on the platform\&. By default, the prefetch instruction is set to 0: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchInstr=0\fR + +.fi +.if n \{\ +.RE +.\} +Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:AllocatePrefetchLines=\fIlines\fR +.RS 4 +Sets the number of cache lines to load after the last object allocation by using the prefetch instructions generated in compiled code\&. The default value is 1 if the last allocated object was an instance, and 3 if it was an array\&. +.sp +The following example shows how to set the number of loaded cache lines to 5: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchLines=5\fR + +.fi +.if n \{\ +.RE +.\} +Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:AllocatePrefetchStepSize=\fIsize\fR +.RS 4 +Sets the step size (in bytes) for sequential prefetch instructions\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. By default, the step size is set to 16 bytes: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:AllocatePrefetchStepSize=16\fR + +.fi +.if n \{\ +.RE +.\} +Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:AllocatePrefetchStyle=\fIstyle\fR +.RS 4 +Sets the generated code style for prefetch instructions\&. The +\fIstyle\fR +argument is an integer from 0 to 3: +.PP +0 +.RS 4 +Do not generate prefetch instructions\&. +.RE +.PP +1 +.RS 4 +Execute prefetch instructions after each allocation\&. This is the default parameter\&. +.RE +.PP +2 +.RS 4 +Use the thread\-local allocation block (TLAB) watermark pointer to determine when prefetch instructions are executed\&. +.RE +.PP +3 +.RS 4 +Use BIS instruction on SPARC for allocation prefetch\&. +.RE +.sp +Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:+BackgroundCompilation +.RS 4 +Enables background compilation\&. This option is enabled by default\&. To disable background compilation, specify +\fB\-XX:\-BackgroundCompilation\fR +(this is equivalent to specifying +\fB\-Xbatch\fR)\&. +.RE +.PP +\-XX:CICompilerCount=\fIthreads\fR +.RS 4 +Sets the number of compiler threads to use for compilation\&. By default, the number of threads is set to 2 for the server JVM, to 1 for the client JVM, and it scales to the number of cores if tiered compilation is used\&. The following example shows how to set the number of threads to 2: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CICompilerCount=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CodeCacheMinimumFreeSpace=\fIsize\fR +.RS 4 +Sets the minimum free space (in bytes) required for compilation\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. When less than the minimum free space remains, compiling stops\&. By default, this option is set to 500 KB\&. The following example shows how to set the minimum free space to 1024 MB: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CodeCacheMinimumFreeSpace=1024m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CompileCommand=\fIcommand\fR,\fImethod\fR[,\fIoption\fR] +.RS 4 +Specifies a command to perform on a method\&. For example, to exclude the +\fBindexOf()\fR +method of the +\fBString\fR +class from being compiled, use the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,java/lang/String\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +Note that the full class name is specified, including all packages and subpackages separated by a slash (\fB/\fR)\&. For easier cut and paste operations, it is also possible to use the method name format produced by the +\fB\-XX:+PrintCompilation\fR +and +\fB\-XX:+LogCompilation\fR +options: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,java\&.lang\&.String::indexOf\fR + +.fi +.if n \{\ +.RE +.\} +If the method is specified without the signature, the command will be applied to all methods with the specified name\&. However, you can also specify the signature of the method in the class file format\&. In this case, you should enclose the arguments in quotation marks, because otherwise the shell treats the semicolon as command end\&. For example, if you want to exclude only the +\fBindexOf(String)\fR +method of the +\fBString\fR +class from being compiled, use the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand="exclude,java/lang/String\&.indexOf,(Ljava/lang/String;)I"\fR + +.fi +.if n \{\ +.RE +.\} +You can also use the asterisk (*) as a wildcard for class and method names\&. For example, to exclude all +\fBindexOf()\fR +methods in all classes from being compiled, use the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=exclude,*\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +The commas and periods are aliases for spaces, making it easier to pass compiler commands through a shell\&. You can pass arguments to +\fB\-XX:CompileCommand\fR +using spaces as separators by enclosing the argument in quotation marks: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand="exclude java/lang/String indexOf"\fR + +.fi +.if n \{\ +.RE +.\} +Note that after parsing the commands passed on the command line using the +\fB\-XX:CompileCommand\fR +options, the JIT compiler then reads commands from the +\fB\&.hotspot_compiler\fR +file\&. You can add commands to this file or specify a different file using the +\fB\-XX:CompileCommandFile\fR +option\&. +.sp +To add several commands, either specify the +\fB\-XX:CompileCommand\fR +option multiple times, or separate each argument with the newline separator (\fB\en\fR)\&. The following commands are available: +.PP +break +.RS 4 +Set a breakpoint when debugging the JVM to stop at the beginning of compilation of the specified method\&. +.RE +.PP +compileonly +.RS 4 +Exclude all methods from compilation except for the specified method\&. As an alternative, you can use the +\fB\-XX:CompileOnly\fR +option, which allows to specify several methods\&. +.RE +.PP +dontinline +.RS 4 +Prevent inlining of the specified method\&. +.RE +.PP +exclude +.RS 4 +Exclude the specified method from compilation\&. +.RE +.PP +help +.RS 4 +Print a help message for the +\fB\-XX:CompileCommand\fR +option\&. +.RE +.PP +inline +.RS 4 +Attempt to inline the specified method\&. +.RE +.PP +log +.RS 4 +Exclude compilation logging (with the +\fB\-XX:+LogCompilation\fR +option) for all methods except for the specified method\&. By default, logging is performed for all compiled methods\&. +.RE +.PP +option +.RS 4 +This command can be used to pass a JIT compilation option to the specified method in place of the last argument (\fIoption\fR)\&. The compilation option is set at the end, after the method name\&. For example, to enable the +\fBBlockLayoutByFrequency\fR +option for the +\fBappend()\fR +method of the +\fBStringBuffer\fR +class, use the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileCommand=option,java/lang/StringBuffer\&.append,BlockLayoutByFrequency\fR + +.fi +.if n \{\ +.RE +.\} +You can specify multiple compilation options, separated by commas or spaces\&. +.RE +.PP +print +.RS 4 +Print generated assembler code after compilation of the specified method\&. +.RE +.PP +quiet +.RS 4 +Do not print the compile commands\&. By default, the commands that you specify with the \-\fBXX:CompileCommand\fR +option are printed; for example, if you exclude from compilation the +\fBindexOf()\fR +method of the +\fBString\fR +class, then the following will be printed to standard output: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompilerOracle: exclude java/lang/String\&.indexOf\fR + +.fi +.if n \{\ +.RE +.\} +You can suppress this by specifying the +\fB\-XX:CompileCommand=quiet\fR +option before other +\fB\-XX:CompileCommand\fR +options\&. +.RE +.RE +.PP +\-XX:CompileCommandFile=\fIfilename\fR +.RS 4 +Sets the file from which JIT compiler commands are read\&. By default, the +\fB\&.hotspot_compiler\fR +file is used to store commands performed by the JIT compiler\&. +.sp +Each line in the command file represents a command, a class name, and a method name for which the command is used\&. For example, this line prints assembly code for the +\fBtoString()\fR +method of the +\fBString\fR +class: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBprint java/lang/String toString\fR + +.fi +.if n \{\ +.RE +.\} +For more information about specifying the commands for the JIT compiler to perform on methods, see the +\fB\-XX:CompileCommand\fR +option\&. +.RE +.PP +\-XX:CompileOnly=\fImethods\fR +.RS 4 +Sets the list of methods (separated by commas) to which compilation should be restricted\&. Only the specified methods will be compiled\&. Specify each method with the full class name (including the packages and subpackages)\&. For example, to compile only the +\fBlength()\fR +method of the +\fBString\fR +class and the +\fBsize()\fR +method of the +\fBList\fR +class, use the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java/lang/String\&.length,java/util/List\&.size\fR + +.fi +.if n \{\ +.RE +.\} +Note that the full class name is specified, including all packages and subpackages separated by a slash (\fB/\fR)\&. For easier cut and paste operations, it is also possible to use the method name format produced by the +\fB\-XX:+PrintCompilation\fR +and +\fB\-XX:+LogCompilation\fR +options: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java\&.lang\&.String::length,java\&.util\&.List::size\fR + +.fi +.if n \{\ +.RE +.\} +Although wildcards are not supported, you can specify only the class or package name to compile all methods in that class or package, as well as specify just the method to compile methods with this name in any class: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileOnly=java/lang/String\fR +\fB\-XX:CompileOnly=java/lang\fR +\fB\-XX:CompileOnly=\&.length\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CompileThreshold=\fIinvocations\fR +.RS 4 +Sets the number of interpreted method invocations before compilation\&. By default, in the server JVM, the JIT compiler performs 10,000 interpreted method invocations to gather information for efficient compilation\&. For the client JVM, the default setting is 1,500 invocations\&. This option is ignored when tiered compilation is enabled; see the option +\fB\-XX:+TieredCompilation\fR\&. The following example shows how to set the number of interpreted method invocations to 5,000: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CompileThreshold=5000\fR + +.fi +.if n \{\ +.RE +.\} +You can completely disable interpretation of Java methods before compilation by specifying the +\fB\-Xcomp\fR +option\&. +.RE +.PP +\-XX:+DoEscapeAnalysis +.RS 4 +Enables the use of escape analysis\&. This option is enabled by default\&. To disable the use of escape analysis, specify +\fB\-XX:\-DoEscapeAnalysis\fR\&. Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:InitialCodeCacheSize=\fIsize\fR +.RS 4 +Sets the initial code cache size (in bytes)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default value is set to 500 KB\&. The initial code cache size should be not less than the system\*(Aqs minimal memory page size\&. The following example shows how to set the initial code cache size to 32 KB: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialCodeCacheSize=32k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+Inline +.RS 4 +Enables method inlining\&. This option is enabled by default to increase performance\&. To disable method inlining, specify +\fB\-XX:\-Inline\fR\&. +.RE +.PP +\-XX:InlineSmallCode=\fIsize\fR +.RS 4 +Sets the maximum code size (in bytes) for compiled methods that should be inlined\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. Only compiled methods with the size smaller than the specified size will be inlined\&. By default, the maximum code size is set to 1000 bytes: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InlineSmallCode=1000\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+LogCompilation +.RS 4 +Enables logging of compilation activity to a file named +\fBhotspot\&.log\fR +in the current working directory\&. You can specify a different log file path and name using the +\fB\-XX:LogFile\fR +option\&. +.sp +By default, this option is disabled and compilation activity is not logged\&. The +\fB\-XX:+LogCompilation\fR +option has to be used together with the +\fB\-XX:UnlockDiagnosticVMOptions\fR +option that unlocks diagnostic JVM options\&. +.sp +You can enable verbose diagnostic output with a message printed to the console every time a method is compiled by using the +\fB\-XX:+PrintCompilation\fR +option\&. +.RE +.PP +\-XX:MaxInlineSize=\fIsize\fR +.RS 4 +Sets the maximum bytecode size (in bytes) of a method to be inlined\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. By default, the maximum bytecode size is set to 35 bytes: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxInlineSize=35\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxNodeLimit=\fInodes\fR +.RS 4 +Sets the maximum number of nodes to be used during single method compilation\&. By default, the maximum number of nodes is set to 65,000: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxNodeLimit=65000\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxTrivialSize=\fIsize\fR +.RS 4 +Sets the maximum bytecode size (in bytes) of a trivial method to be inlined\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. By default, the maximum bytecode size of a trivial method is set to 6 bytes: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxTrivialSize=6\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+OptimizeStringConcat +.RS 4 +Enables the optimization of +\fBString\fR +concatenation operations\&. This option is enabled by default\&. To disable the optimization of +\fBString\fR +concatenation operations, specify +\fB\-XX:\-OptimizeStringConcat\fR\&. Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:+PrintAssembly +.RS 4 +Enables printing of assembly code for bytecoded and native methods by using the external +\fBdisassembler\&.so\fR +library\&. This enables you to see the generated code, which may help you to diagnose performance issues\&. +.sp +By default, this option is disabled and assembly code is not printed\&. The +\fB\-XX:+PrintAssembly\fR +option has to be used together with the +\fB\-XX:UnlockDiagnosticVMOptions\fR +option that unlocks diagnostic JVM options\&. +.RE +.PP +\-XX:+PrintCompilation +.RS 4 +Enables verbose diagnostic output from the JVM by printing a message to the console every time a method is compiled\&. This enables you to see which methods actually get compiled\&. By default, this option is disabled and diagnostic output is not printed\&. +.sp +You can also log compilation activity to a file by using the +\fB\-XX:+LogCompilation\fR +option\&. +.RE +.PP +\-XX:+PrintInlining +.RS 4 +Enables printing of inlining decisions\&. This enables you to see which methods are getting inlined\&. +.sp +By default, this option is disabled and inlining information is not printed\&. The +\fB\-XX:+PrintInlining\fR +option has to be used together with the +\fB\-XX:+UnlockDiagnosticVMOptions\fR +option that unlocks diagnostic JVM options\&. +.RE +.PP +\-XX:ReservedCodeCacheSize=\fIsize\fR +.RS 4 +Sets the maximum code cache size (in bytes) for JIT\-compiled code\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default maximum code cache size is 240 MB; if you disable tiered compilation with the option +\fB\-XX:\-TieredCompilation\fR, then the default size is 48 MB\&. This option has a limit of 2 GB; otherwise, an error is generated\&. The maximum code cache size should not be less than the initial code cache size; see the option +\fB\-XX:InitialCodeCacheSize\fR\&. This option is equivalent to +\fB\-Xmaxjitcodesize\fR\&. +.RE +.PP +\-XX:RTMAbortRatio=\fIabort_ratio\fR +.RS 4 +The RTM abort ratio is specified as a percentage (%) of all executed RTM transactions\&. If a number of aborted transactions becomes greater than this ratio, then the compiled code will be deoptimized\&. This ratio is used when the +\fB\-XX:+UseRTMDeopt\fR +option is enabled\&. The default value of this option is 50\&. This means that the compiled code will be deoptimized if 50% of all transactions are aborted\&. +.RE +.PP +\-XX:RTMRetryCount=\fInumber_of_retries\fR +.RS 4 +RTM locking code will be retried, when it is aborted or busy, the number of times specified by this option before falling back to the normal locking mechanism\&. The default value for this option is 5\&. The +\fB\-XX:UseRTMLocking\fR +option must be enabled\&. +.RE +.PP +\-XX:\-TieredCompilation +.RS 4 +Disables the use of tiered compilation\&. By default, this option is enabled\&. Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:+UseAES +.RS 4 +Enables hardware\-based AES intrinsics for Intel, AMD, and SPARC hardware\&. Intel Westmere (2010 and newer), AMD Bulldozer (2011 and newer), and SPARC (T4 and newer) are the supported hardware\&. UseAES is used in conjunction with UseAESIntrinsics\&. +.RE +.PP +\-XX:+UseAESIntrinsics +.RS 4 +UseAES and UseAESIntrinsics flags are enabled by default and are supported only for Java HotSpot Server VM 32\-bit and 64\-bit\&. To disable hardware\-based AES intrinsics, specify +\fB\-XX:\-UseAES \-XX:\-UseAESIntrinsics\fR\&. For example, to enable hardware AES, use the following flags: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:+UseAES \-XX:+UseAESIntrinsics\fR + +.fi +.if n \{\ +.RE +.\} +To support UseAES and UseAESIntrinsics flags for 32\-bit and 64\-bit use +\fB\-server\fR +option to choose Java HotSpot Server VM\&. These flags are not supported on Client VM\&. +.RE +.PP +\-XX:+UseCodeCacheFlushing +.RS 4 +Enables flushing of the code cache before shutting down the compiler\&. This option is enabled by default\&. To disable flushing of the code cache before shutting down the compiler, specify +\fB\-XX:\-UseCodeCacheFlushing\fR\&. +.RE +.PP +\-XX:+UseCondCardMark +.RS 4 +Enables checking of whether the card is already marked before updating the card table\&. This option is disabled by default and should only be used on machines with multiple sockets, where it will increase performance of Java applications that rely heavily on concurrent operations\&. Only the Java HotSpot Server VM supports this option\&. +.RE +.PP +\-XX:+UseRTMDeopt +.RS 4 +Auto\-tunes RTM locking depending on the abort ratio\&. This ratio is specified by +\fB\-XX:RTMAbortRatio\fR +option\&. If the number of aborted transactions exceeds the abort ratio, then the method containing the lock will be deoptimized and recompiled with all locks as normal locks\&. This option is disabled by default\&. The +\fB\-XX:+UseRTMLocking\fR +option must be enabled\&. +.RE +.PP +\-XX:+UseRTMLocking +.RS 4 +Generate Restricted Transactional Memory (RTM) locking code for all inflated locks, with the normal locking mechanism as the fallback handler\&. This option is disabled by default\&. Options related to RTM are only available for the Java HotSpot Server VM on x86 CPUs that support Transactional Synchronization Extensions (TSX)\&. +.sp +RTM is part of Intel\*(Aqs TSX, which is an x86 instruction set extension and facilitates the creation of multithreaded applications\&. RTM introduces the new instructions +\fBXBEGIN\fR, +\fBXABORT\fR, +\fBXEND\fR, and +\fBXTEST\fR\&. The +\fBXBEGIN\fR +and +\fBXEND\fR +instructions enclose a set of instructions to run as a transaction\&. If no conflict is found when running the transaction, the memory and register modifications are committed together at the +\fBXEND\fR +instruction\&. The +\fBXABORT\fR +instruction can be used to explicitly abort a transaction and the +\fBXEND\fR +instruction to check if a set of instructions are being run in a transaction\&. +.sp +A lock on a transaction is inflated when another thread tries to access the same transaction, thereby blocking the thread that did not originally request access to the transaction\&. RTM requires that a fallback set of operations be specified in case a transaction aborts or fails\&. An RTM lock is a lock that has been delegated to the TSX\*(Aqs system\&. +.sp +RTM improves performance for highly contended locks with low conflict in a critical region (which is code that must not be accessed by more than one thread concurrently)\&. RTM also improves the performance of coarse\-grain locking, which typically does not perform well in multithreaded applications\&. (Coarse\-grain locking is the strategy of holding locks for long periods to minimize the overhead of taking and releasing locks, while fine\-grained locking is the strategy of trying to achieve maximum parallelism by locking only when necessary and unlocking as soon as possible\&.) Also, for lightly contended locks that are used by different threads, RTM can reduce false cache line sharing, also known as cache line ping\-pong\&. This occurs when multiple threads from different processors are accessing different resources, but the resources share the same cache line\&. As a result, the processors repeatedly invalidate the cache lines of other processors, which forces them to read from main memory instead of their cache\&. +.RE +.PP +\-XX:+UseSHA +.RS 4 +Enables hardware\-based intrinsics for SHA crypto hash functions for SPARC hardware\&. +\fBUseSHA\fR +is used in conjunction with the +\fBUseSHA1Intrinsics\fR, +\fBUseSHA256Intrinsics\fR, and +\fBUseSHA512Intrinsics\fR +options\&. +.sp +The +\fBUseSHA\fR +and +\fBUseSHA*Intrinsics\fR +flags are enabled by default, and are supported only for Java HotSpot Server VM 64\-bit on SPARC T4 and newer\&. +.sp +This feature is only applicable when using the +\fBsun\&.security\&.provider\&.Sun\fR +provider for SHA operations\&. +.sp +To disable all hardware\-based SHA intrinsics, specify +\fB\-XX:\-UseSHA\fR\&. To disable only a particular SHA intrinsic, use the appropriate corresponding option\&. For example: +\fB\-XX:\-UseSHA256Intrinsics\fR\&. +.RE +.PP +\-XX:+UseSHA1Intrinsics +.RS 4 +Enables intrinsics for SHA\-1 crypto hash function\&. +.RE +.PP +\-XX:+UseSHA256Intrinsics +.RS 4 +Enables intrinsics for SHA\-224 and SHA\-256 crypto hash functions\&. +.RE +.PP +\-XX:+UseSHA512Intrinsics +.RS 4 +Enables intrinsics for SHA\-384 and SHA\-512 crypto hash functions\&. +.RE +.PP +\-XX:+UseSuperWord +.RS 4 +Enables the transformation of scalar operations into superword operations\&. This option is enabled by default\&. To disable the transformation of scalar operations into superword operations, specify +\fB\-XX:\-UseSuperWord\fR\&. Only the Java HotSpot Server VM supports this option\&. +.RE +.SS "Advanced Serviceability Options" +.PP +These options provide the ability to gather system information and perform extensive debugging\&. +.PP +\-XX:+ExtendedDTraceProbes +.RS 4 +Enables additional +\fBdtrace\fR +tool probes that impact the performance\&. By default, this option is disabled and +\fBdtrace\fR +performs only standard probes\&. +.RE +.PP +\-XX:+HeapDumpOnOutOfMemory +.RS 4 +Enables the dumping of the Java heap to a file in the current directory by using the heap profiler (HPROF) when a +\fBjava\&.lang\&.OutOfMemoryError\fR +exception is thrown\&. You can explicitly set the heap dump file path and name using the +\fB\-XX:HeapDumpPath\fR +option\&. By default, this option is disabled and the heap is not dumped when an +\fBOutOfMemoryError\fR +exception is thrown\&. +.RE +.PP +\-XX:HeapDumpPath=\fIpath\fR +.RS 4 +Sets the path and file name for writing the heap dump provided by the heap profiler (HPROF) when the +\fB\-XX:+HeapDumpOnOutOfMemoryError\fR +option is set\&. By default, the file is created in the current working directory, and it is named +\fBjava_pid\fR\fIpid\fR\fB\&.hprof\fR +where +\fIpid\fR +is the identifier of the process that caused the error\&. The following example shows how to set the default file explicitly (\fB%p\fR +represents the current process identificator): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:HeapDumpPath=\&./java_pid%p\&.hprof\fR + +.fi +.if n \{\ +.RE +.\} +The following example shows how to set the heap dump file to +\fB/var/log/java/java_heapdump\&.hprof\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:HeapDumpPath=/var/log/java/java_heapdump\&.hprof\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:LogFile=\fIpath\fR +.RS 4 +Sets the path and file name where log data is written\&. By default, the file is created in the current working directory, and it is named +\fBhotspot\&.log\fR\&. +.sp +The following example shows how to set the log file to +\fB/var/log/java/hotspot\&.log\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:LogFile=/var/log/java/hotspot\&.log\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+PrintClassHistogram +.RS 4 +Enables printing of a class instance histogram after a +\fBControl+C\fR +event (\fBSIGTERM\fR)\&. By default, this option is disabled\&. +.sp +Setting this option is equivalent to running the +\fBjmap \-histo\fR +command, or the +\fBjcmd \fR\fIpid\fR\fB GC\&.class_histogram\fR +command, where +\fIpid\fR +is the current Java process identifier\&. +.RE +.PP +\-XX:+PrintConcurrentLocks +.RS 4 +Enables printing of locks after a event\&. By default, this option is disabled\&. +.sp +Enables printing of +\fBjava\&.util\&.concurrent\fR +locks after a +\fBControl+C\fR +event (\fBSIGTERM\fR)\&. By default, this option is disabled\&. +.sp +Setting this option is equivalent to running the +\fBjstack \-l\fR +command or the +\fBjcmd \fR\fIpid\fR\fB Thread\&.print \-l\fR +command, where +\fIpid\fR +is the current Java process identifier\&. +.RE +.PP +\-XX:+UnlockDiagnosticVMOptions +.RS 4 +Unlocks the options intended for diagnosing the JVM\&. By default, this option is disabled and diagnostic options are not available\&. +.RE +.SS "Advanced Garbage Collection Options" +.PP +These options control how garbage collection (GC) is performed by the Java HotSpot VM\&. +.PP +\-XX:+AggressiveHeap +.RS 4 +Enables Java heap optimization\&. This sets various parameters to be optimal for long\-running jobs with intensive memory allocation, based on the configuration of the computer (RAM and CPU)\&. By default, the option is disabled and the heap is not optimized\&. +.RE +.PP +\-XX:+AlwaysPreTouch +.RS 4 +Enables touching of every page on the Java heap during JVM initialization\&. This gets all pages into the memory before entering the +\fBmain()\fR +method\&. The option can be used in testing to simulate a long\-running system with all virtual memory mapped to physical memory\&. By default, this option is disabled and all pages are committed as JVM heap space fills\&. +.RE +.PP +\-XX:+CMSClassUnloadingEnabled +.RS 4 +Enables class unloading when using the concurrent mark\-sweep (CMS) garbage collector\&. This option is enabled by default\&. To disable class unloading for the CMS garbage collector, specify +\fB\-XX:\-CMSClassUnloadingEnabled\fR\&. +.RE +.PP +\-XX:CMSExpAvgFactor=\fIpercent\fR +.RS 4 +Sets the percentage of time (0 to 100) used to weight the current sample when computing exponential averages for the concurrent collection statistics\&. By default, the exponential averages factor is set to 25%\&. The following example shows how to set the factor to 15%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSExpAvgFactor=15\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:CMSInitiatingOccupancyFraction=\fIpercent\fR +.RS 4 +Sets the percentage of the old generation occupancy (0 to 100) at which to start a CMS collection cycle\&. The default value is set to \-1\&. Any negative value (including the default) implies that +\fB\-XX:CMSTriggerRatio\fR +is used to define the value of the initiating occupancy fraction\&. +.sp +The following example shows how to set the occupancy fraction to 20%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSInitiatingOccupancyFraction=20\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+CMSScavengeBeforeRemark +.RS 4 +Enables scavenging attempts before the CMS remark step\&. By default, this option is disabled\&. +.RE +.PP +\-XX:CMSTriggerRatio=\fIpercent\fR +.RS 4 +Sets the percentage (0 to 100) of the value specified by +\fB\-XX:MinHeapFreeRatio\fR +that is allocated before a CMS collection cycle commences\&. The default value is set to 80%\&. +.sp +The following example shows how to set the occupancy fraction to 75%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:CMSTriggerRatio=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:ConcGCThreads=\fIthreads\fR +.RS 4 +Sets the number of threads used for concurrent GC\&. The default value depends on the number of CPUs available to the JVM\&. +.sp +For example, to set the number of threads for concurrent GC to 2, specify the following option: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ConcGCThreads=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+DisableExplicitGC +.RS 4 +Enables the option that disables processing of calls to +\fBSystem\&.gc()\fR\&. This option is disabled by default, meaning that calls to +\fBSystem\&.gc()\fR +are processed\&. If processing of calls to +\fBSystem\&.gc()\fR +is disabled, the JVM still performs GC when necessary\&. +.RE +.PP +\-XX:+ExplicitGCInvokesConcurrent +.RS 4 +Enables invoking of concurrent GC by using the +\fBSystem\&.gc()\fR +request\&. This option is disabled by default and can be enabled only together with the +\fB\-XX:+UseConcMarkSweepGC\fR +option\&. +.RE +.PP +\-XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses +.RS 4 +Enables invoking of concurrent GC by using the +\fBSystem\&.gc()\fR +request and unloading of classes during the concurrent GC cycle\&. This option is disabled by default and can be enabled only together with the +\fB\-XX:+UseConcMarkSweepGC\fR +option\&. +.RE +.PP +\-XX:G1HeapRegionSize=\fIsize\fR +.RS 4 +Sets the size of the regions into which the Java heap is subdivided when using the garbage\-first (G1) collector\&. The value can be between 1 MB and 32 MB\&. The default region size is determined ergonomically based on the heap size\&. +.sp +The following example shows how to set the size of the subdivisions to 16 MB: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:G1HeapRegionSize=16m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+G1PrintHeapRegions +.RS 4 +Enables the printing of information about which regions are allocated and which are reclaimed by the G1 collector\&. By default, this option is disabled\&. +.RE +.PP +\-XX:G1ReservePercent=\fIpercent\fR +.RS 4 +Sets the percentage of the heap (0 to 50) that is reserved as a false ceiling to reduce the possibility of promotion failure for the G1 collector\&. By default, this option is set to 10%\&. +.sp +The following example shows how to set the reserved heap to 20%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:G1ReservePercent=20\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:InitialHeapSize=\fIsize\fR +.RS 4 +Sets the initial size (in bytes) of the memory allocation pool\&. This value must be either 0, or a multiple of 1024 and greater than 1 MB\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default value is chosen at runtime based on system configuration\&. See the section "Ergonomics" in +\fIJava SE HotSpot Virtual Machine Garbage Collection Tuning Guide\fR +at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.html\&. +.sp +The following examples show how to set the size of allocated memory to 6 MB using various units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialHeapSize=6291456\fR +\fB\-XX:InitialHeapSize=6144k\fR +\fB\-XX:InitialHeapSize=6m\fR + +.fi +.if n \{\ +.RE +.\} +If you set this option to 0, then the initial size will be set as the sum of the sizes allocated for the old generation and the young generation\&. The size of the heap for the young generation can be set using the +\fB\-XX:NewSize\fR +option\&. +.RE +.PP +\-XX:InitialSurvivorRatio=\fIratio\fR +.RS 4 +Sets the initial survivor space ratio used by the throughput garbage collector (which is enabled by the +\fB\-XX:+UseParallelGC\fR +and/or \-\fBXX:+UseParallelOldGC\fR +options)\&. Adaptive sizing is enabled by default with the throughput garbage collector by using the +\fB\-XX:+UseParallelGC\fR +and +\fB\-XX:+UseParallelOldGC\fR +options, and survivor space is resized according to the application behavior, starting with the initial value\&. If adaptive sizing is disabled (using the +\fB\-XX:\-UseAdaptiveSizePolicy\fR +option), then the +\fB\-XX:SurvivorRatio\fR +option should be used to set the size of the survivor space for the entire execution of the application\&. +.sp +The following formula can be used to calculate the initial size of survivor space (S) based on the size of the young generation (Y), and the initial survivor space ratio (R): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBS=Y/(R+2)\fR + +.fi +.if n \{\ +.RE +.\} +The 2 in the equation denotes two survivor spaces\&. The larger the value specified as the initial survivor space ratio, the smaller the initial survivor space size\&. +.sp +By default, the initial survivor space ratio is set to 8\&. If the default value for the young generation space size is used (2 MB), the initial size of the survivor space will be 0\&.2 MB\&. +.sp +The following example shows how to set the initial survivor space ratio to 4: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitialSurvivorRatio=4\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:InitiatingHeapOccupancyPercent=\fIpercent\fR +.RS 4 +Sets the percentage of the heap occupancy (0 to 100) at which to start a concurrent GC cycle\&. It is used by garbage collectors that trigger a concurrent GC cycle based on the occupancy of the entire heap, not just one of the generations (for example, the G1 garbage collector)\&. +.sp +By default, the initiating value is set to 45%\&. A value of 0 implies nonstop GC cycles\&. The following example shows how to set the initiating heap occupancy to 75%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:InitiatingHeapOccupancyPercent=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxGCPauseMillis=\fItime\fR +.RS 4 +Sets a target for the maximum GC pause time (in milliseconds)\&. This is a soft goal, and the JVM will make its best effort to achieve it\&. By default, there is no maximum pause time value\&. +.sp +The following example shows how to set the maximum target pause time to 500 ms: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxGCPauseMillis=500\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxHeapSize=\fIsize\fR +.RS 4 +Sets the maximum size (in byes) of the memory allocation pool\&. This value must be a multiple of 1024 and greater than 2 MB\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. The default value is chosen at runtime based on system configuration\&. For server deployments, +\fB\-XX:InitialHeapSize\fR +and +\fB\-XX:MaxHeapSize\fR +are often set to the same value\&. See the section "Ergonomics" in +\fIJava SE HotSpot Virtual Machine Garbage Collection Tuning Guide\fR +at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/gctuning/index\&.html\&. +.sp +The following examples show how to set the maximum allowed size of allocated memory to 80 MB using various units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxHeapSize=83886080\fR +\fB\-XX:MaxHeapSize=81920k\fR +\fB\-XX:MaxHeapSize=80m\fR + +.fi +.if n \{\ +.RE +.\} +On Oracle Solaris 7 and Oracle Solaris 8 SPARC platforms, the upper limit for this value is approximately 4,000 MB minus overhead amounts\&. On Oracle Solaris 2\&.6 and x86 platforms, the upper limit is approximately 2,000 MB minus overhead amounts\&. On Linux platforms, the upper limit is approximately 2,000 MB minus overhead amounts\&. +.sp +The +\fB\-XX:MaxHeapSize\fR +option is equivalent to +\fB\-Xmx\fR\&. +.RE +.PP +\-XX:MaxHeapFreeRatio=\fIpercent\fR +.RS 4 +Sets the maximum allowed percentage of free heap space (0 to 100) after a GC event\&. If free heap space expands above this value, then the heap will be shrunk\&. By default, this value is set to 70%\&. +.sp +The following example shows how to set the maximum free heap ratio to 75%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxHeapFreeRatio=75\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxMetaspaceSize=\fIsize\fR +.RS 4 +Sets the maximum amount of native memory that can be allocated for class metadata\&. By default, the size is not limited\&. The amount of metadata for an application depends on the application itself, other running applications, and the amount of memory available on the system\&. +.sp +The following example shows how to set the maximum class metadata size to 256 MB: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxMetaspaceSize=256m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MaxNewSize=\fIsize\fR +.RS 4 +Sets the maximum size (in bytes) of the heap for the young generation (nursery)\&. The default value is set ergonomically\&. +.RE +.PP +\-XX:MaxTenuringThreshold=\fIthreshold\fR +.RS 4 +Sets the maximum tenuring threshold for use in adaptive GC sizing\&. The largest value is 15\&. The default value is 15 for the parallel (throughput) collector, and 6 for the CMS collector\&. +.sp +The following example shows how to set the maximum tenuring threshold to 10: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MaxTenuringThreshold=10\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:MetaspaceSize=\fIsize\fR +.RS 4 +Sets the size of the allocated class metadata space that will trigger a garbage collection the first time it is exceeded\&. This threshold for a garbage collection is increased or decreased depending on the amount of metadata used\&. The default size depends on the platform\&. +.RE +.PP +\-XX:MinHeapFreeRatio=\fIpercent\fR +.RS 4 +Sets the minimum allowed percentage of free heap space (0 to 100) after a GC event\&. If free heap space falls below this value, then the heap will be expanded\&. By default, this value is set to 40%\&. +.sp +The following example shows how to set the minimum free heap ratio to 25%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:MinHeapFreeRatio=25\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NewRatio=\fIratio\fR +.RS 4 +Sets the ratio between young and old generation sizes\&. By default, this option is set to 2\&. The following example shows how to set the young/old ratio to 1: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:NewRatio=1\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:NewSize=\fIsize\fR +.RS 4 +Sets the initial size (in bytes) of the heap for the young generation (nursery)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. +.sp +The young generation region of the heap is used for new objects\&. GC is performed in this region more often than in other regions\&. If the size for the young generation is too low, then a large number of minor GCs will be performed\&. If the size is too high, then only full GCs will be performed, which can take a long time to complete\&. Oracle recommends that you keep the size for the young generation between a half and a quarter of the overall heap size\&. +.sp +The following examples show how to set the initial size of young generation to 256 MB using various units: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:NewSize=256m\fR +\fB\-XX:NewSize=262144k\fR +\fB\-XX:NewSize=268435456\fR + +.fi +.if n \{\ +.RE +.\} +The +\fB\-XX:NewSize\fR +option is equivalent to +\fB\-Xmn\fR\&. +.RE +.PP +\-XX:ParallelGCThreads=\fIthreads\fR +.RS 4 +Sets the number of threads used for parallel garbage collection in the young and old generations\&. The default value depends on the number of CPUs available to the JVM\&. +.sp +For example, to set the number of threads for parallel GC to 2, specify the following option: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:ParallelGCThreads=2\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+ParallelRefProcEnabled +.RS 4 +Enables parallel reference processing\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintAdaptiveSizePolicy +.RS 4 +Enables printing of information about adaptive generation sizing\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGC +.RS 4 +Enables printing of messages at every GC\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGCApplicationConcurrentTime +.RS 4 +Enables printing of how much time elapsed since the last pause (for example, a GC pause)\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGCApplicationStoppedTime +.RS 4 +Enables printing of how much time the pause (for example, a GC pause) lasted\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGCDateStamps +.RS 4 +Enables printing of a date stamp at every GC\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGCDetails +.RS 4 +Enables printing of detailed messages at every GC\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGCTaskTimeStamps +.RS 4 +Enables printing of time stamps for every individual GC worker thread task\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintGCTimeStamps +.RS 4 +Enables printing of time stamps at every GC\&. By default, this option is disabled\&. +.RE +.PP +\-XX:+PrintStringDeduplicationStatistics +.RS 4 +Prints detailed deduplication statistics\&. By default, this option is disabled\&. See the +\fB\-XX:+UseStringDeduplication\fR +option\&. +.RE +.PP +\-XX:+PrintTenuringDistribution +.RS 4 +Enables printing of tenuring age information\&. The following is an example of the output: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBDesired survivor size 48286924 bytes, new threshold 10 (max 10)\fR +\fB\- age 1: 28992024 bytes, 28992024 total\fR +\fB\- age 2: 1366864 bytes, 30358888 total\fR +\fB\- age 3: 1425912 bytes, 31784800 total\fR +\fB\&.\&.\&.\fR + +.fi +.if n \{\ +.RE +.\} +Age 1 objects are the youngest survivors (they were created after the previous scavenge, survived the latest scavenge, and moved from eden to survivor space)\&. Age 2 objects have survived two scavenges (during the second scavenge they were copied from one survivor space to the next)\&. And so on\&. +.sp +In the preceding example, 28 992 024 bytes survived one scavenge and were copied from eden to survivor space, 1 366 864 bytes are occupied by age 2 objects, etc\&. The third value in each row is the cumulative size of objects of age n or less\&. +.sp +By default, this option is disabled\&. +.RE +.PP +\-XX:+ScavengeBeforeFullGC +.RS 4 +Enables GC of the young generation before each full GC\&. This option is enabled by default\&. Oracle recommends that you +\fIdo not\fR +disable it, because scavenging the young generation before a full GC can reduce the number of objects reachable from the old generation space into the young generation space\&. To disable GC of the young generation before each full GC, specify +\fB\-XX:\-ScavengeBeforeFullGC\fR\&. +.RE +.PP +\-XX:SoftRefLRUPolicyMSPerMB=\fItime\fR +.RS 4 +Sets the amount of time (in milliseconds) a softly reachable object is kept active on the heap after the last time it was referenced\&. The default value is one second of lifetime per free megabyte in the heap\&. The +\fB\-XX:SoftRefLRUPolicyMSPerMB\fR +option accepts integer values representing milliseconds per one megabyte of the current heap size (for Java HotSpot Client VM) or the maximum possible heap size (for Java HotSpot Server VM)\&. This difference means that the Client VM tends to flush soft references rather than grow the heap, whereas the Server VM tends to grow the heap rather than flush soft references\&. In the latter case, the value of the +\fB\-Xmx\fR +option has a significant effect on how quickly soft references are garbage collected\&. +.sp +The following example shows how to set the value to 2\&.5 seconds: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:SoftRefLRUPolicyMSPerMB=2500\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:StringDeduplicationAgeThreshold=\fIthreshold\fR +.RS 4 +\fBString\fR +objects reaching the specified age are considered candidates for deduplication\&. An object\*(Aqs age is a measure of how many times it has survived garbage collection\&. This is sometimes referred to as tenuring; see the +\fB\-XX:+PrintTenuringDistribution\fR +option\&. Note that +\fBString\fR +objects that are promoted to an old heap region before this age has been reached are always considered candidates for deduplication\&. The default value for this option is +\fB3\fR\&. See the +\fB\-XX:+UseStringDeduplication\fR +option\&. +.RE +.PP +\-XX:SurvivorRatio=\fIratio\fR +.RS 4 +Sets the ratio between eden space size and survivor space size\&. By default, this option is set to 8\&. The following example shows how to set the eden/survivor space ratio to 4: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:SurvivorRatio=4\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:TargetSurvivorRatio=\fIpercent\fR +.RS 4 +Sets the desired percentage of survivor space (0 to 100) used after young garbage collection\&. By default, this option is set to 50%\&. +.sp +The following example shows how to set the target survivor space ratio to 30%: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:TargetSurvivorRatio=30\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:TLABSize=\fIsize\fR +.RS 4 +Sets the initial size (in bytes) of a thread\-local allocation buffer (TLAB)\&. Append the letter +\fBk\fR +or +\fBK\fR +to indicate kilobytes, +\fBm\fR +or +\fBM\fR +to indicate megabytes, +\fBg\fR +or +\fBG\fR +to indicate gigabytes\&. If this option is set to 0, then the JVM chooses the initial size automatically\&. +.sp +The following example shows how to set the initial TLAB size to 512 KB: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-XX:TLABSize=512k\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-XX:+UseAdaptiveSizePolicy +.RS 4 +Enables the use of adaptive generation sizing\&. This option is enabled by default\&. To disable adaptive generation sizing, specify +\fB\-XX:\-UseAdaptiveSizePolicy\fR +and set the size of the memory allocation pool explicitly (see the +\fB\-XX:SurvivorRatio\fR +option)\&. +.RE +.PP +\-XX:+UseCMSInitiatingOccupancyOnly +.RS 4 +Enables the use of the occupancy value as the only criterion for initiating the CMS collector\&. By default, this option is disabled and other criteria may be used\&. +.RE +.PP +\-XX:+UseConcMarkSweepGC +.RS 4 +Enables the use of the CMS garbage collector for the old generation\&. Oracle recommends that you use the CMS garbage collector when application latency requirements cannot be met by the throughput (\fB\-XX:+UseParallelGC\fR) garbage collector\&. The G1 garbage collector (\fB\-XX:+UseG1GC\fR) is another alternative\&. +.sp +By default, this option is disabled and the collector is chosen automatically based on the configuration of the machine and type of the JVM\&. When this option is enabled, the +\fB\-XX:+UseParNewGC\fR +option is automatically set and you should not disable it, because the following combination of options has been deprecated in JDK 8: +\fB\-XX:+UseConcMarkSweepGC \-XX:\-UseParNewGC\fR\&. +.RE +.PP +\-XX:+UseG1GC +.RS 4 +Enables the use of the garbage\-first (G1) garbage collector\&. It is a server\-style garbage collector, targeted for multiprocessor machines with a large amount of RAM\&. It meets GC pause time goals with high probability, while maintaining good throughput\&. The G1 collector is recommended for applications requiring large heaps (sizes of around 6 GB or larger) with limited GC latency requirements (stable and predictable pause time below 0\&.5 seconds)\&. +.sp +By default, this option is disabled and the collector is chosen automatically based on the configuration of the machine and type of the JVM\&. +.RE +.PP +\-XX:+UseGCOverheadLimit +.RS 4 +Enables the use of a policy that limits the proportion of time spent by the JVM on GC before an +\fBOutOfMemoryError\fR +exception is thrown\&. This option is enabled, by default and the parallel GC will throw an +\fBOutOfMemoryError\fR +if more than 98% of the total time is spent on garbage collection and less than 2% of the heap is recovered\&. When the heap is small, this feature can be used to prevent applications from running for long periods of time with little or no progress\&. To disable this option, specify +\fB\-XX:\-UseGCOverheadLimit\fR\&. +.RE +.PP +\-XX:+UseNUMA +.RS 4 +Enables performance optimization of an application on a machine with nonuniform memory architecture (NUMA) by increasing the application\*(Aqs use of lower latency memory\&. By default, this option is disabled and no optimization for NUMA is made\&. The option is only available when the parallel garbage collector is used (\fB\-XX:+UseParallelGC\fR)\&. +.RE +.PP +\-XX:+UseParallelGC +.RS 4 +Enables the use of the parallel scavenge garbage collector (also known as the throughput collector) to improve the performance of your application by leveraging multiple processors\&. +.sp +By default, this option is disabled and the collector is chosen automatically based on the configuration of the machine and type of the JVM\&. If it is enabled, then the +\fB\-XX:+UseParallelOldGC\fR +option is automatically enabled, unless you explicitly disable it\&. +.RE +.PP +\-XX:+UseParallelOldGC +.RS 4 +Enables the use of the parallel garbage collector for full GCs\&. By default, this option is disabled\&. Enabling it automatically enables the +\fB\-XX:+UseParallelGC\fR +option\&. +.RE +.PP +\-XX:+UseParNewGC +.RS 4 +Enables the use of parallel threads for collection in the young generation\&. By default, this option is disabled\&. It is automatically enabled when you set the +\fB\-XX:+UseConcMarkSweepGC\fR +option\&. Using the +\fB\-XX:+UseParNewGC\fR +option without the +\fB\-XX:+UseConcMarkSweepGC\fR +option was deprecated in JDK 8\&. +.RE +.PP +\-XX:+UseSerialGC +.RS 4 +Enables the use of the serial garbage collector\&. This is generally the best choice for small and simple applications that do not require any special functionality from garbage collection\&. By default, this option is disabled and the collector is chosen automatically based on the configuration of the machine and type of the JVM\&. +.RE +.PP +\-XX:+UseSHM +.RS 4 +On Linux, enables the JVM to use shared memory to setup large pages\&. +.sp +For more information, see "Large Pages"\&. +.RE +.PP +\-XX:+UseStringDeduplication +.RS 4 +Enables string deduplication\&. By default, this option is disabled\&. To use this option, you must enable the garbage\-first (G1) garbage collector\&. See the +\fB\-XX:+UseG1GC\fR +option\&. +.sp +\fIString deduplication\fR +reduces the memory footprint of +\fBString\fR +objects on the Java heap by taking advantage of the fact that many +\fBString\fR +objects are identical\&. Instead of each +\fBString\fR +object pointing to its own character array, identical +\fBString\fR +objects can point to and share the same character array\&. +.RE +.PP +\-XX:+UseTLAB +.RS 4 +Enables the use of thread\-local allocation blocks (TLABs) in the young generation space\&. This option is enabled by default\&. To disable the use of TLABs, specify +\fB\-XX:\-UseTLAB\fR\&. +.RE +.SS "Deprecated and Removed Options" +.PP +These options were included in the previous release, but have since been considered unnecessary\&. +.PP +\-Xincgc +.RS 4 +Enables incremental garbage collection\&. This option was deprecated in JDK 8 with no replacement\&. +.RE +.PP +\-Xrun\fIlibname\fR +.RS 4 +Loads the specified debugging/profiling library\&. This option was superseded by the +\fB\-agentlib\fR +option\&. +.RE +.PP +\-XX:CMSIncrementalDutyCycle=\fIpercent\fR +.RS 4 +Sets the percentage of time (0 to 100) between minor collections that the concurrent collector is allowed to run\&. This option was deprecated in JDK 8 with no replacement, following the deprecation of the +\fB\-XX:+CMSIncrementalMode\fR +option\&. +.RE +.PP +\-XX:CMSIncrementalDutyCycleMin=\fIpercent\fR +.RS 4 +Sets the percentage of time (0 to 100) between minor collections that is the lower bound for the duty cycle when +\fB\-XX:+CMSIncrementalPacing\fR +is enabled\&. This option was deprecated in JDK 8 with no replacement, following the deprecation of the +\fB\-XX:+CMSIncrementalMode\fR +option\&. +.RE +.PP +\-XX:+CMSIncrementalMode +.RS 4 +Enables the incremental mode for the CMS collector\&. This option was deprecated in JDK 8 with no replacement, along with other options that start with +\fBCMSIncremental\fR\&. +.RE +.PP +\-XX:CMSIncrementalOffset=\fIpercent\fR +.RS 4 +Sets the percentage of time (0 to 100) by which the incremental mode duty cycle is shifted to the right within the period between minor collections\&. This option was deprecated in JDK 8 with no replacement, following the deprecation of the +\fB\-XX:+CMSIncrementalMode\fR +option\&. +.RE +.PP +\-XX:+CMSIncrementalPacing +.RS 4 +Enables automatic adjustment of the incremental mode duty cycle based on statistics collected while the JVM is running\&. This option was deprecated in JDK 8 with no replacement, following the deprecation of the +\fB\-XX:+CMSIncrementalMode\fR +option\&. +.RE +.PP +\-XX:CMSIncrementalSafetyFactor=\fIpercent\fR +.RS 4 +Sets the percentage of time (0 to 100) used to add conservatism when computing the duty cycle\&. This option was deprecated in JDK 8 with no replacement, following the deprecation of the +\fB\-XX:+CMSIncrementalMode\fR +option\&. +.RE +.PP +\-XX:CMSInitiatingPermOccupancyFraction=\fIpercent\fR +.RS 4 +Sets the percentage of the permanent generation occupancy (0 to 100) at which to start a GC\&. This option was deprecated in JDK 8 with no replacement\&. +.RE +.PP +\-XX:MaxPermSize=\fIsize\fR +.RS 4 +Sets the maximum permanent generation space size (in bytes)\&. This option was deprecated in JDK 8, and superseded by the +\fB\-XX:MaxMetaspaceSize\fR +option\&. +.RE +.PP +\-XX:PermSize=\fIsize\fR +.RS 4 +Sets the space (in bytes) allocated to the permanent generation that triggers a garbage collection if it is exceeded\&. This option was deprecated un JDK 8, and superseded by the +\fB\-XX:MetaspaceSize\fR +option\&. +.RE +.PP +\-XX:+UseSplitVerifier +.RS 4 +Enables splitting of the verification process\&. By default, this option was enabled in the previous releases, and verification was split into two phases: type referencing (performed by the compiler) and type checking (performed by the JVM runtime)\&. This option was deprecated in JDK 8, and verification is now split by default without a way to disable it\&. +.RE +.PP +\-XX:+UseStringCache +.RS 4 +Enables caching of commonly allocated strings\&. This option was removed from JDK 8 with no replacement\&. +.RE +.SH "PERFORMANCE TUNING EXAMPLES" +.PP +The following examples show how to use experimental tuning flags to either optimize throughput or to provide lower response time\&. +.PP +\fBExample 1 \fRTuning for Higher Throughput +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-d64 \-server \-XX:+AggressiveOpts \-XX:+UseLargePages \-Xmn10g \-Xms26g \-Xmx26g\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fBExample 2 \fRTuning for Lower Response Time +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjava \-d64 \-XX:+UseG1GC \-Xms26g Xmx26g \-XX:MaxGCPauseMillis=500 \-XX:+PrintGCTimeStamp\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "LARGE PAGES" +.PP +Also known as huge pages, large pages are memory pages that are significantly larger than the standard memory page size (which varies depending on the processor and operating system)\&. Large pages optimize processor Translation\-Lookaside Buffers\&. +.PP +A Translation\-Lookaside Buffer (TLB) is a page translation cache that holds the most\-recently used virtual\-to\-physical address translations\&. TLB is a scarce system resource\&. A TLB miss can be costly as the processor must then read from the hierarchical page table, which may require multiple memory accesses\&. By using a larger memory page size, a single TLB entry can represent a larger memory range\&. There will be less pressure on TLB, and memory\-intensive applications may have better performance\&. +.PP +However, large pages page memory can negatively affect system performance\&. For example, when a large mount of memory is pinned by an application, it may create a shortage of regular memory and cause excessive paging in other applications and slow down the entire system\&. Also, a system that has been up for a long time could produce excessive fragmentation, which could make it impossible to reserve enough large page memory\&. When this happens, either the OS or JVM reverts to using regular pages\&. +.SS "Large Pages Support" +.PP +Solaris and Linux support large pages\&. +.sp +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBSolaris\fR +.RS 4 +.PP +Solaris 9 and later include Multiple Page Size Support (MPSS); no additional configuration is necessary\&. See http://www\&.oracle\&.com/technetwork/server\-storage/solaris10/overview/solaris9\-features\-scalability\-135663\&.html\&. +.RE +.sp +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBLinux\fR +.RS 4 +.PP +The 2\&.6 kernel supports large pages\&. Some vendors have backported the code to their 2\&.4\-based releases\&. To check if your system can support large page memory, try the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# cat /proc/meminfo | grep Huge\fR +\fBHugePages_Total: 0\fR +\fBHugePages_Free: 0\fR +\fBHugepagesize: 2048 kB\fR + +.fi +.if n \{\ +.RE +.\} +.PP +If the output shows the three "Huge" variables, then your system can support large page memory but it needs to be configured\&. If the command prints nothing, then your system does not support large pages\&. To configure the system to use large page memory, login as +\fBroot\fR, and then follow these steps: +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +If you are using the option +\fB\-XX:+UseSHM\fR +(instead of +\fB\-XX:+UseHugeTLBFS\fR), then increase the +\fBSHMMAX\fR +value\&. It must be larger than the Java heap size\&. On a system with 4 GB of physical RAM (or less), the following will make all the memory sharable: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# echo 4294967295 > /proc/sys/kernel/shmmax\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +If you are using the option +\fB\-XX:+UseSHM\fR +or +\fB\-XX:+UseHugeTLBFS\fR, then specify the number of large pages\&. In the following example, 3 GB of a 4 GB system are reserved for large pages (assuming a large page size of 2048kB, then 3 GB = 3 * 1024 MB = 3072 MB = 3072 * 1024 kB = 3145728 kB and 3145728 kB / 2048 kB = 1536): +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB# echo 1536 > /proc/sys/vm/nr_hugepages\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Note that the values contained in +\fB/proc\fR +will reset after you reboot your system, so may want to set them in an initialization script (for example, +\fBrc\&.local\fR +or +\fBsysctl\&.conf\fR)\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +If you configure (or resize) the OS kernel parameters +\fB/proc/sys/kernel/shmmax\fR +or +\fB/proc/sys/vm/nr_hugepages\fR, Java processes may allocate large pages for areas in addition to the Java heap\&. These steps can allocate large pages for the following areas: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Java heap +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +Code cache +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +The marking bitmap data structure for the parallel GC +.RE +.sp +Consequently, if you configure the +\fBnr_hugepages\fR +parameter to the size of the Java heap, then the JVM can fail in allocating the code cache areas on large pages because these areas are quite large in size\&. +.RE +T} +.TE +.sp 1 +.sp .5v +.RE +.RE +.SH "APPLICATION CLASS DATA SHARING" +.PP +Application Class Data Sharing (AppCDS) extends CDS (see https://docs\&.oracle\&.com/javase/8/docs/technotes/guides/vm/class\-data\-sharing\&.html) to enable classes from the standard extensions directories (specified by the system property +\fBjava\&.ext\&.dirs\fR; see https://docs\&.oracle\&.com/javase/8/docs/technotes/guides/extensions/spec\&.html) and the application class path (see "Setting the Class Path ") to be placed in the shared archive\&. AppCDS reduces the footprint and decreases start\-up time of your applications provided that a substantial number of classes are loaded from the application class path\&. +.PP +This is a commercial feature that requires you to also specify the +\fB\-XX:+UnlockCommercialFeatures\fR +option\&. This is also an experimental feature; it may change in future releases\&. +.SS "Creating a Shared Archive File, and Running an Application with It" +.PP +The following steps create a shared archive file that contains all the classes used by the +\fBtest\&.Hello\fR +application\&. The last step runs the application with the shared archive file\&. +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +Create a list of all classes used by the +\fBtest\&.Hello\fR +application\&. The following command creates a file named +\fBhello\&.classlist\fR +that contains a list of all classes used by this application: +.sp +\fBjava \-Xshare:off \-XX:+UnlockCommercialFeatures \-XX:DumpLoadedClassList=hello\&.classlist \-XX:+UseAppCDS \-cp hello\&.jar test\&.Hello\fR +.sp +Note that the +\fB\-cp\fR +parameter must contain only JAR files; the +\fB\-XX:+UseAppCDS\fR +option does not support class paths that contain directory names\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +Create a shared archive, named +\fBhello\&.jsa\fR, that contains all the classes in +\fBhello\&.classlist\fR: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-Xshare:dump \-XX:+UseAppCDS \-XX:SharedArchiveFile=hello\&.jsa \-XX:SharedClassListFile=hello\&.classlist \-cp hello\&.jar\fR +.sp +Note that the +\fB\-cp\fR +parameter used at archive creation time must be the same as (or a prefix of) the +\fB\-cp\fR +used at run time\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +Run the application +\fBtest\&.Hello\fR +with the shared archive +\fBhello\&.jsa\fR: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-Xshare:on \-XX:+UseAppCDS \-XX:SharedArchiveFile=hello\&.jsa \-cp hello\&.jar test\&.Hello\fR +.sp +Ensure that you have specified the option +\fB\-Xshare:on\fR +or \-\fBXshare:auto\fR\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +Verify that the +\fBtest\&.Hello\fR +application is using the class contained in the +\fBhello\&.jsa\fR +shared archive: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-Xshare:on \-XX:+UseAppCDS \-XX:SharedArchiveFile=hello\&.jsa \-cp hello\&.jar \-verbose:class test\&.Hello\fR +.sp +The output of this command should contain the following text: +.sp +\fBLoaded test\&.Hello from shared objects file by sun/misc/Launcher$AppClassLoader\fR +.RE +.SS "Sharing a Shared Archive across Multiple Application Processes" +.PP +You can share the same archive file across multiple applications processes that have the exact same class path or share a common class path prefix\&. This reduces memory usage as the archive is memory\-mapped into the address space of the processes\&. The operating system automatically shares the read\-only pages across these processes\&. +.PP +The following steps create a shared archive that both applications +\fBHello\fR +and +\fBHi\fR +can use\&. +.sp +.RS 4 +.ie n \{\ +\h'-04' 1.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 1." 4.2 +.\} +Create a list of all classes used by the +\fBHello\fR +application and another list for the +\fBHi\fR +application: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-XX:DumpLoadedClassList=hello\&.classlist \-XX:+UseAppCDS \-cp common\&.jar:hello\&.jar Hello\fR +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-XX:DumpLoadedClassList=hi\&.classlist \-XX:+UseAppCDS \-cp common\&.jar:hi\&.jar Hi\fR +.sp +Note that because the +\fBHello\fR +and +\fBHi\fR +applications share a common class path prefix (both of their class paths start with +\fBcommon\&.jar\fR), these two applications can share a shared archive file\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 2.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 2." 4.2 +.\} +Create a single list of classes used by all the applications that will share the shared archive file\&. +.sp +The following commands combine the files +\fBhello\&.classlist\fR +and +\fBhi\&.classlist\fR +to one file, +\fBcommon\&.classlist\fR: +.sp +\fBcat hello\&.classlist hi\&.classlist > common\&.classlist\fR +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 3.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 3." 4.2 +.\} +Create a shared archive, named +\fBcommon\&.jsa\fR, that contains all the classes in +\fBcommon\&.classlist\fR: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-Xshare:dump \-XX:SharedArchiveFile=common\&.jsa \-XX:+UseAppCDS \-XX:SharedClassListFile=common\&.classlist \-cp common\&.jar\fR +.sp +The value of the +\fB\-cp\fR +parameter is the common class path prefix shared by the +\fBHello\fR +and +\fBHi\fR +applications\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04' 4.\h'+01'\c +.\} +.el \{\ +.sp -1 +.IP " 4." 4.2 +.\} +Run the +\fBHello\fR +and +\fBHi\fR +applications with the same shared archive: +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-Xshare:on \-XX:SharedArchiveFile=common\&.jsa \-XX:+UseAppCDS \-cp common\&.jar:hello\&.jar Hello\fR +.sp +\fBjava \-XX:+UnlockCommercialFeatures \-Xshare:on \-XX:SharedArchiveFile=common\&.jsa \-XX:+UseAppCDS \-cp common\&.jar:hi\&.jar Hi\fR +.RE +.SH "EXIT STATUS" +.PP +The following exit values are typically returned by the launcher when the launcher is called with the wrong arguments, serious errors, or exceptions thrown by the JVM\&. However, a Java application may choose to return any value by using the API call +\fBSystem\&.exit(exitValue)\fR\&. The values are: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB0\fR: Successful completion +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB>0\fR: An error occurred +.RE +.SH "SEE ALSO" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jar(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstat(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javac.1 b/jdk-1.8.0.281/man/man1/javac.1 new file mode 100755 index 0000000..db8de02 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javac.1 @@ -0,0 +1,1349 @@ +'\" t +.\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 03 March 2015 +.\" SectDesc: Basic Tools +.\" Title: javac.1 +.\" +.if n .pl 99999 +.TH javac 1 "03 March 2015" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +javac \- Reads Java class and interface definitions and compiles them into bytecode and class files\&. +.SH SYNOPSIS +.sp +.nf + +\fBjavac\fR [ \fIoptions\fR ] [ \fIsourcefiles\fR ] [ \fIclasses\fR] [ \fI@argfiles\fR ] +.fi +.sp +Arguments can be in any order: +.TP +\fIoptions\fR +Command-line options\&. See Options\&. +.TP +\fIsourcefiles\fR +One or more source files to be compiled (such as \f3MyClass\&.java\fR)\&. +.TP +\fIclasses\fR +One or more classes to be processed for annotations (such as \f3MyPackage\&.MyClass\fR)\&. +.TP +\fI@argfiles\fR +One or more files that list options and source files\&. The \f3-J\fR options are not allowed in these files\&. See Command-Line Argument Files\&. +.SH DESCRIPTION +The \f3javac\fR command reads class and interface definitions, written in the Java programming language, and compiles them into bytecode class files\&. The \f3javac\fR command can also process annotations in Java source files and classes\&. +.PP +There are two ways to pass source code file names to \f3javac\fR\&. +.TP 0.2i +\(bu +For a small number of source files, list the file names on the command line\&. +.TP 0.2i +\(bu +For a large number of source files, list the file names in a file that is separated by blanks or line breaks\&. Use the list file name preceded by an at sign (@) with the \f3javac\fR command\&. +.PP +Source code file names must have \&.java suffixes, class file names must have \&.class suffixes, and both source and class files must have root names that identify the class\&. For example, a class called \f3MyClass\fR would be written in a source file called \f3MyClass\&.java\fR and compiled into a bytecode class file called \f3MyClass\&.class\fR\&. +.PP +Inner class definitions produce additional class files\&. These class files have names that combine the inner and outer class names, such as \f3MyClass$MyInnerClass\&.class\fR\&. +.PP +Arrange source files in a directory tree that reflects their package tree\&. For example, if all of your source files are in \f3/workspace\fR, then put the source code for \f3com\&.mysoft\&.mypack\&.MyClass\fR in \f3/workspace/com/mysoft/mypack/MyClass\&.java\fR\&. +.PP +By default, the compiler puts each class file in the same directory as its source file\&. You can specify a separate destination directory with the \f3-d\fR option\&. +.SH OPTIONS +The compiler has a set of standard options that are supported on the current development environment\&. An additional set of nonstandard options are specific to the current virtual machine and compiler implementations and are subject to change in the future\&. Nonstandard options begin with the \f3-X\fR option\&. +.TP 0.2i +\(bu +See also Cross-Compilation Options +.TP 0.2i +\(bu +See also Nonstandard Options +.SS STANDARD\ OPTIONS +.TP +-A\fIkey\fR[\fI=value\fR] +.br +Specifies options to pass to annotation processors\&. These options are not interpreted by \f3javac\fR directly, but are made available for use by individual processors\&. The \f3key\fR value should be one or more identifiers separated by a dot (\&.)\&. +.TP +-cp \fIpath\fR or -classpath \fIpath\fR +.br +Specifies where to find user class files, and (optionally) annotation processors and source files\&. This class path overrides the user class path in the \f3CLASSPATH\fR environment variable\&. If neither \f3CLASSPATH\fR, \f3-cp\fR nor \f3-classpath\fR is specified, then the user \fIclass path\fR is the current directory\&. See Setting the Class Path\&. + +If the \f3-sourcepath\fR option is not specified, then the user class path is also searched for source files\&. + +If the \f3-processorpath\fR option is not specified, then the class path is also searched for annotation processors\&. +.TP +-Djava\&.ext\&.dirs=\fIdirectories\fR +.br +Overrides the location of installed extensions\&. +.TP +-Djava\&.endorsed\&.dirs=\fIdirectories\fR +.br +Overrides the location of the endorsed standards path\&. +.TP +-d \fIdirectory\fR +.br +Sets the destination directory for class files\&. The directory must already exist because \f3javac\fR does not create it\&. If a class is part of a package, then \f3javac\fR puts the class file in a subdirectory that reflects the package name and creates directories as needed\&. + +If you specify \f3-d\fR\f3/home/myclasses\fR and the class is called \f3com\&.mypackage\&.MyClass\fR, then the class file is \f3/home/myclasses/com/mypackage/MyClass\&.class\fR\&. + +If the \fI-d\fR option is not specified, then \f3javac\fR puts each class file in the same directory as the source file from which it was generated\&. + +\fINote:\fR The directory specified by the \fI-d\fR option is not automatically added to your user class path\&. +.TP +-deprecation +.br +Shows a description of each use or override of a deprecated member or class\&. Without the \f3-deprecation\fR option, \f3javac\fR shows a summary of the source files that use or override deprecated members or classes\&. The \f3-deprecation\fR option is shorthand for \f3-Xlint:deprecation\fR\&. +.TP +-encoding \fIencoding\fR +.br +Sets the source file encoding name, such as EUC-JP and UTF-8\&. If the \f3-encoding\fR option is not specified, then the platform default converter is used\&. +.TP +-endorseddirs \fIdirectories\fR +.br +Overrides the location of the endorsed standards path\&. +.TP +-extdirs \fIdirectories\fR +.br +Overrides the location of the \f3ext\fR directory\&. The directories variable is a colon-separated list of directories\&. Each JAR file in the specified directories is searched for class files\&. All JAR files found become part of the class path\&. + +If you are cross-compiling (compiling classes against bootstrap and extension classes of a different Java platform implementation), then this option specifies the directories that contain the extension classes\&. See Cross-Compilation Options for more information\&. +.TP +-g +.br +Generates all debugging information, including local variables\&. By default, only line number and source file information is generated\&. +.TP +-g:none +.br +Does not generate any debugging information\&. +.TP +-g:[\fIkeyword list\fR] +.br +Generates only some kinds of debugging information, specified by a comma separated list of keywords\&. Valid keywords are: +.RS +.TP +source +Source file debugging information\&. +.TP +lines +Line number debugging information\&. +.TP +vars +Local variable debugging information\&. +.RE + +.TP +-help +.br +Prints a synopsis of standard options\&. +.TP +-implicit:[\fIclass, none\fR] +.br +Controls the generation of class files for implicitly loaded source files\&. To automatically generate class files, use \f3-implicit:class\fR\&. To suppress class file generation, use \f3-implicit:none\fR\&. If this option is not specified, then the default is to automatically generate class files\&. In this case, the compiler issues a warning if any such class files are generated when also doing annotation processing\&. The warning is not issued when the \f3-implicit\fR option is set explicitly\&. See Searching for Types\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine (JVM), where option is one of the options described on the reference page for the Java launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. + +\fINote:\fR The \fICLASSPATH\fR, \f3-classpath\fR, \f3-bootclasspath\fR, and \f3-extdirs\fR options do not specify the classes used to run \f3javac\fR\&. Trying to customize the compiler implementation with these options and variables is risky and often does not accomplish what you want\&. If you must customize the complier implementation, then use the \f3-J\fR option to pass options through to the underlying \f3\fRJava launcher\&. +.TP +-nowarn +.br +Disables warning messages\&. This option operates the same as the \f3-Xlint:none\fR option\&. +.TP +-parameters +.br +Stores formal parameter names of constructors and methods in the generated class file so that the method \f3java\&.lang\&.reflect\&.Executable\&.getParameters\fR from the Reflection API can retrieve them\&. +.TP +-proc: [\fInone\fR, \fIonly\fR] +.br +Controls whether annotation processing and compilation are done\&. \f3-proc:none\fR means that compilation takes place without annotation processing\&. \f3-proc:only\fR means that only annotation processing is done, without any subsequent compilation\&. +.TP +-processor \fIclass1\fR [,\fIclass2\fR,\fIclass3\fR\&.\&.\&.] +.br +Names of the annotation processors to run\&. This bypasses the default discovery process\&. +.TP +-processorpath \fIpath\fR +.br +Specifies where to find annotation processors\&. If this option is not used, then the class path is searched for processors\&. +.TP +-s \fIdir\fR +.br +Specifies the directory where to place the generated source files\&. The directory must already exist because \f3javac\fR does not create it\&. If a class is part of a package, then the compiler puts the source file in a subdirectory that reflects the package name and creates directories as needed\&. + +If you specify \f3-s /home/mysrc\fR and the class is called \f3com\&.mypackage\&.MyClass\fR, then the source file is put in \f3/home/mysrc/com/mypackage/MyClass\&.java\fR\&. +.TP +-source \fIrelease\fR +.br +Specifies the version of source code accepted\&. The following values for \f3release\fR are allowed: +.RS +.TP +1\&.3 +The compiler does not support assertions, generics, or other language features introduced after Java SE 1\&.3\&. +.TP +1\&.4 +The compiler accepts code containing assertions, which were introduced in Java SE 1\&.4\&. +.TP +1\&.5 +The compiler accepts code containing generics and other language features introduced in Java SE 5\&. +.TP +5 +Synonym for 1\&.5\&. +.TP +1\&.6 +No language changes were introduced in Java SE 6\&. However, encoding errors in source files are now reported as errors instead of warnings as in earlier releases of Java Platform, Standard Edition\&. +.TP +6 +Synonym for 1\&.6\&. +.TP +1\&.7 +The compiler accepts code with features introduced in Java SE 7\&. +.TP +7 +Synonym for 1\&.7\&. +.TP +1\&.8 +This is the default value\&. The compiler accepts code with features introduced in Java SE 8\&. +.TP +8 +Synonym for 1\&.8\&. +.RE + +.TP +-sourcepath \fIsourcepath\fR +.br +Specifies the source code path to search for class or interface definitions\&. As with the user class path, source path entries are separated by colons (:) on Oracle Solaris and semicolons on Windows and can be directories, JAR archives, or ZIP archives\&. If packages are used, then the local path name within the directory or archive must reflect the package name\&. + +\fINote:\fR Classes found through the class path might be recompiled when their source files are also found\&. See Searching for Types\&. +.TP +-verbose +.br +Uses verbose output, which includes information about each class loaded and each source file compiled\&. +.TP +-version +.br +Prints release information\&. +.TP +-werror +.br +Terminates compilation when warnings occur\&. +.TP +-X +.br +Displays information about nonstandard options and exits\&. +.SS CROSS-COMPILATION\ OPTIONS +By default, classes are compiled against the bootstrap and extension classes of the platform that \f3javac\fR shipped with\&. But \f3javac\fR also supports cross-compiling, where classes are compiled against a bootstrap and extension classes of a different Java platform implementation\&. It is important to use the \f3-bootclasspath\fR and \f3-extdirs\fR options when cross-compiling\&. +.TP +-target \fIversion\fR +.br +Generates class files that target a specified release of the virtual machine\&. Class files will run on the specified target and on later releases, but not on earlier releases of the JVM\&. Valid targets are 1\&.1, 1\&.2, 1\&.3, 1\&.4, 1\&.5 (also 5), 1\&.6 (also 6), 1\&.7 (also 7), and 1\&.8 (also 8)\&. + +The default for the \f3-target\fR option depends on the value of the \f3-source\fR option: +.RS +.TP 0.2i +\(bu +If the \f3-source\fR option is not specified, then the value of the \f3-target\fR option is 1\&.8 +.TP 0.2i +\(bu +If the \f3-source\fR option is 1\&.2, then the value of the \f3-target\fR option is 1\&.4 +.TP 0.2i +\(bu +If the \f3-source\fR option is 1\&.3, then the value of the \f3-target\fR option is 1\&.4 +.TP 0.2i +\(bu +If the \f3-source\fR option is 1\&.5, then the value of the \f3-target\fR option is 1\&.8 +.TP 0.2i +\(bu +If the \f3-source\fR option is 1\&.6, then the value of the \f3-target\fR is option 1\&.8 +.TP 0.2i +\(bu +If the \f3-source\fR option is 1\&.7, then the value of the \f3-target\fR is option 1\&.8 +.TP 0.2i +\(bu +For all other values of the \f3-source\fR option, the value of the \f3-target\fR option is the value of the \f3-source\fR option\&. +.RE + +.TP +-bootclasspath \fIbootclasspath\fR +.br +Cross-compiles against the specified set of boot classes\&. As with the user class path, boot class path entries are separated by colons (:) and can be directories, JAR archives, or ZIP archives\&. +.SS COMPACT\ PROFILE\ OPTION +Beginning with JDK 8, the \f3javac\fR compiler supports compact profiles\&. With compact profiles, applications that do not require the entire Java platform can be deployed and run with a smaller footprint\&. The compact profiles feature could be used to shorten the download time for applications from app stores\&. This feature makes for more compact deployment of Java applications that bundle the JRE\&. This feature is also useful in small devices\&. +.PP +The supported profile values are \f3compact1\fR, \f3compact2\fR, and \f3compact3\fR\&. These are additive layers\&. Each higher-numbered compact profile contains all of the APIs in profiles with smaller number names\&. +.TP +-profile +.br +When using compact profiles, this option specifies the profile name when compiling\&. For example: +.sp +.nf +\f3javac \-profile compact1 Hello\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp + + +javac does not compile source code that uses any Java SE APIs that is not in the specified profile\&. Here is an example of the error message that results from attempting to compile such source code: +.sp +.nf +\f3cd jdk1\&.8\&.0/bin\fP +.fi +.nf +\f3\&./javac \-profile compact1 Paint\&.java\fP +.fi +.nf +\f3Paint\&.java:5: error: Applet is not available in profile \&'compact1\&'\fP +.fi +.nf +\f3import java\&.applet\&.Applet;\fP +.fi +.nf +\f3\fP +.fi +.sp + + +In this example, you can correct the error by modifying the source to not use the \f3Applet\fR class\&. You could also correct the error by compiling without the -profile option\&. Then the compilation would be run against the full set of Java SE APIs\&. (None of the compact profiles include the \f3Applet\fR class\&.) + +An alternative way to compile with compact profiles is to use the \f3-bootclasspath\fR option to specify a path to an \f3rt\&.jar\fR file that specifies a profile\&'s image\&. Using the \f3-profile\fR option instead does not require a profile image to be present on the system at compile time\&. This is useful when cross-compiling\&. +.SS NONSTANDARD\ OPTIONS +.TP +-Xbootclasspath/p:\fIpath\fR +.br +Adds a suffix to the bootstrap class path\&. +.TP +-Xbootclasspath/a:\fIpath\fR +.br +Adds a prefix to the bootstrap class path\&. +.TP +-Xbootclasspath/:\fIpath\fR +.br +Overrides the location of the bootstrap class files\&. +.TP +-Xdoclint:[-]\fIgroup\fR [\fI/access\fR] +.br +Enables or disables specific groups of checks, where \fIgroup\fR is one of the following values: \f3accessibility\fR, \f3syntax\fR, \f3reference\fR, \f3html\fR or \f3missing\fR\&. For more information about these groups of checks see the \f3-Xdoclint\fR option of the \f3javadoc\fR command\&. The \f3-Xdoclint\fR option is disabled by default in the \f3javac\fR command\&. + +The variable \fIaccess\fR specifies the minimum visibility level of classes and members that the \f3-Xdoclint\fR option checks\&. It can have one of the following values (in order of most to least visible) : \f3public\fR, \f3protected\fR, \f3package\fR and \f3private\fR\&. For example, the following option checks classes and members (with all groups of checks) that have the access level protected and higher (which includes protected, package and public): +.sp +.nf +\f3\-Xdoclint:all/protected\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following option enables all groups of checks for all access levels, except it will not check for HTML errors for classes and members that have access level package and higher (which includes package and public): +.sp +.nf +\f3\-Xdoclint:all,\-html/package\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-Xdoclint:none +.br +Disables all groups of checks\&. +.TP +-Xdoclint:all[\fI/access\fR] +.br +Enables all groups of checks\&. +.TP +-Xlint +.br +\fI\fREnables all recommended warnings\&. In this release, enabling all available warnings is recommended\&. +.TP +-Xlint:all +.br +\fI\fREnables all recommended warnings\&. In this release, enabling all available warnings is recommended\&. +.TP +-Xlint:none +.br +Disables all warnings\&. +.TP +-Xlint:\fIname\fR +.br +Disables warning name\&. See Enable or Disable Warnings with the -Xlint Option for a list of warnings you can disable with this option\&. +.TP +-Xlint:\fI-name\fR +.br +Disables warning name\&. See Enable or Disable Warnings with the -Xlint Option with the \f3-Xlint\fR option to get a list of warnings that you can disable with this option\&. +.TP +-Xmaxerrs \fInumber\fR +.br +Sets the maximum number of errors to print\&. +.TP +-Xmaxwarns \fInumber\fR +.br +Sets the maximum number of warnings to print\&. +.TP +-Xstdout \fIfilename\fR +.br +Sends compiler messages to the named file\&. By default, compiler messages go to \f3System\&.err\fR\&. +.TP +-Xprefer:[\fInewer,source\fR] +.br +Specifies which file to read when both a source file and class file are found for a type\&. (See Searching for Types)\&. If the \f3-Xprefer:newer\fR option is used, then it reads the newer of the source or class file for a type (default)\&. If the \f3-Xprefer:source\fR option is used, then it reads the source file\&. Use -\f3Xprefer:source\fR when you want to be sure that any annotation processors can access annotations declared with a retention policy of \f3SOURCE\fR\&. +.TP +-Xpkginfo:[\fIalways\fR,\fIlegacy\fR,\fInonempty\fR] +.br +Control whether javac generates \f3package-info\&.class\fR files from package-info\&.java files\&. Possible mode arguments for this option include the following\&. +.RS +.TP +always +Always generate a \f3package-info\&.class\fR file for every \f3package-info\&.java\fR file\&. This option may be useful if you use a build system such as Ant, which checks that each \f3\&.java\fR file has a corresponding \f3\&.class\fR file\&. +.TP +legacy +Generate a \f3package-info\&.class\fR file only if package-info\&.java contains annotations\&. Don\&'t generate a \f3package-info\&.class\fR file if package-info\&.java only contains comments\&. + +\fINote:\fR A \f3package-info\&.class\fR file might be generated but be empty if all the annotations in the package-info\&.java file have \f3RetentionPolicy\&.SOURCE\fR\&. +.TP +nonempty +Generate a \f3package-info\&.class\fR file only if package-info\&.java contains annotations with \f3RetentionPolicy\&.CLASS\fR or \f3RetentionPolicy\&.RUNTIME\fR\&. +.RE + +.TP +-Xprint +.br +Prints a textual representation of specified types for debugging purposes\&. Perform neither annotation processing nor compilation\&. The format of the output could change\&. +.TP +-XprintProcessorInfo +.br +Prints information about which annotations a processor is asked to process\&. +.TP +-XprintRounds +.br +Prints information about initial and subsequent annotation processing rounds\&. +.SH ENABLE\ OR\ DISABLE\ WARNINGS\ WITH\ THE\ -XLINT\ OPTION +Enable warning \fIname\fR with the \f3-Xlint:name\fR option, where \f3name\fR is one of the following warning names\&. Note that you can disable a warning with the \f3-Xlint:-name:\fR option\&. +.TP +cast +Warns about unnecessary and redundant casts, for example: +.sp +.nf +\f3String s = (String) "Hello!"\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +classfile +Warns about issues related to class file contents\&. +.TP +deprecation +Warns about the use of deprecated items, for example: +.sp +.nf +\f3java\&.util\&.Date myDate = new java\&.util\&.Date();\fP +.fi +.nf +\f3int currentDay = myDate\&.getDay();\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The method \f3java\&.util\&.Date\&.getDay\fR has been deprecated since JDK 1\&.1 +.TP +dep-ann +Warns about items that are documented with an \f3@deprecated\fR Javadoc comment, but do not have a \f3@Deprecated\fR annotation, for example: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * @deprecated As of Java SE 7, replaced by {@link #newMethod()}\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3public static void deprecatedMethood() { }\fP +.fi +.nf +\f3public static void newMethod() { }\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +divzero +Warns about division by the constant integer 0, for example: +.sp +.nf +\f3int divideByZero = 42 / 0;\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +empty +Warns about empty statements after \f3if\fRstatements, for example: +.sp +.nf +\f3class E {\fP +.fi +.nf +\f3 void m() {\fP +.fi +.nf +\f3 if (true) ;\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +fallthrough +Checks the switch blocks for fall-through cases and provides a warning message for any that are found\&. Fall-through cases are cases in a switch block, other than the last case in the block, whose code does not include a break statement, allowing code execution to fall through from that case to the next case\&. For example, the code following the case 1 label in this switch block does not end with a break statement: +.sp +.nf +\f3switch (x) {\fP +.fi +.nf +\f3case 1:\fP +.fi +.nf +\f3 System\&.out\&.println("1");\fP +.fi +.nf +\f3 // No break statement here\&.\fP +.fi +.nf +\f3case 2:\fP +.fi +.nf +\f3 System\&.out\&.println("2");\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +If the \f3-Xlint:fallthrough\fR option was used when compiling this code, then the compiler emits a warning about possible fall-through into case, with the line number of the case in question\&. +.TP +finally +Warns about \f3finally\fR clauses that cannot complete normally, for example: +.sp +.nf +\f3public static int m() {\fP +.fi +.nf +\f3 try {\fP +.fi +.nf +\f3 throw new NullPointerException();\fP +.fi +.nf +\f3 } catch (NullPointerException(); {\fP +.fi +.nf +\f3 System\&.err\&.println("Caught NullPointerException\&.");\fP +.fi +.nf +\f3 return 1;\fP +.fi +.nf +\f3 } finally {\fP +.fi +.nf +\f3 return 0;\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The compiler generates a warning for the \f3finally\fR block in this example\&. When the \f3int\fR method is called, it returns a value of 0\&. A \f3finally\fR block executes when the \f3try\fR block exits\&. In this example, when control is transferred to the \f3catch\fR block, the \f3int\fR method exits\&. However, the \f3finally\fR block must execute, so it is executed, even though control was transferred outside the method\&. +.TP +options +Warns about issues that related to the use of command-line options\&. See Cross-Compilation Options\&. +.TP +overrides +Warns about issues regarding method overrides\&. For example, consider the following two classes: +.sp +.nf +\f3public class ClassWithVarargsMethod {\fP +.fi +.nf +\f3 void varargsMethod(String\&.\&.\&. s) { }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3public class ClassWithOverridingMethod extends ClassWithVarargsMethod {\fP +.fi +.nf +\f3 @Override\fP +.fi +.nf +\f3 void varargsMethod(String[] s) { }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The compiler generates a warning similar to the following:\&. +.sp +.nf +\f3warning: [override] varargsMethod(String[]) in ClassWithOverridingMethod \fP +.fi +.nf +\f3overrides varargsMethod(String\&.\&.\&.) in ClassWithVarargsMethod; overriding\fP +.fi +.nf +\f3method is missing \&'\&.\&.\&.\&'\fP +.fi +.nf +\f3\fP +.fi +.sp + + +When the compiler encounters a \f3varargs\fR method, it translates the \f3varargs\fR formal parameter into an array\&. In the method \f3ClassWithVarargsMethod\&.varargsMethod\fR, the compiler translates the \f3varargs\fR formal parameter \f3String\&.\&.\&. s\fR to the formal parameter \f3String[] s\fR, an array, which matches the formal parameter of the method \f3ClassWithOverridingMethod\&.varargsMethod\fR\&. Consequently, this example compiles\&. +.TP +path +Warns about invalid path elements and nonexistent path directories on the command line (with regard to the class path, the source path, and other paths)\&. Such warnings cannot be suppressed with the \f3@SuppressWarnings\fR annotation, for example: +.sp +.nf +\f3javac \-Xlint:path \-classpath /nonexistentpath Example\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +processing +Warn about issues regarding annotation processing\&. The compiler generates this warning when you have a class that has an annotation, and you use an annotation processor that cannot handle that type of exception\&. For example, the following is a simple annotation processor: + +\fISource file AnnocProc\&.java\fR: +.sp +.nf +\f3import java\&.util\&.*;\fP +.fi +.nf +\f3import javax\&.annotation\&.processing\&.*;\fP +.fi +.nf +\f3import javax\&.lang\&.model\&.*;\fP +.fi +.nf +\f3import\&.javaz\&.lang\&.model\&.element\&.*;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3@SupportedAnnotationTypes("NotAnno")\fP +.fi +.nf +\f3public class AnnoProc extends AbstractProcessor {\fP +.fi +.nf +\f3 public boolean process(Set<? extends TypeElement> elems, RoundEnvironment renv){\fP +.fi +.nf +\f3 return true;\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 public SourceVersion getSupportedSourceVersion() {\fP +.fi +.nf +\f3 return SourceVersion\&.latest();\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\fISource file AnnosWithoutProcessors\&.java\fR: +.sp +.nf +\f3@interface Anno { }\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3@Anno\fP +.fi +.nf +\f3class AnnosWithoutProcessors { }\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following commands compile the annotation processor \f3AnnoProc\fR, then run this annotation processor against the source file \f3AnnosWithoutProcessors\&.java\fR: +.sp +.nf +\f3javac AnnoProc\&.java\fP +.fi +.nf +\f3javac \-cp \&. \-Xlint:processing \-processor AnnoProc \-proc:only AnnosWithoutProcessors\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp + + +When the compiler runs the annotation processor against the source file \f3AnnosWithoutProcessors\&.java\fR, it generates the following warning: +.sp +.nf +\f3warning: [processing] No processor claimed any of these annotations: Anno\fP +.fi +.nf +\f3\fP +.fi +.sp + + +To resolve this issue, you can rename the annotation defined and used in the class \f3AnnosWithoutProcessors\fR from \f3Anno\fR to \f3NotAnno\fR\&. +.TP +rawtypes +Warns about unchecked operations on raw types\&. The following statement generates a \f3rawtypes\fR warning: +.sp +.nf +\f3void countElements(List l) { \&.\&.\&. }\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following example does not generate a \f3rawtypes\fR warning +.sp +.nf +\f3void countElements(List<?> l) { \&.\&.\&. }\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\f3List\fR is a raw type\&. However, \f3List<?>\fR is an unbounded wildcard parameterized type\&. Because \f3List\fR is a parameterized interface, always specify its type argument\&. In this example, the \f3List\fR formal argument is specified with an unbounded wildcard (\f3?\fR) as its formal type parameter, which means that the \f3countElements\fR method can accept any instantiation of the \f3List\fR interface\&. +.TP +Serial +Warns about missing \f3serialVersionUID\fR definitions on serializable classes, for example: +.sp +.nf +\f3public class PersistentTime implements Serializable\fP +.fi +.nf +\f3{\fP +.fi +.nf +\f3 private Date time;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 public PersistentTime() {\fP +.fi +.nf +\f3 time = Calendar\&.getInstance()\&.getTime();\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 public Date getTime() {\fP +.fi +.nf +\f3 return time;\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The compiler generates the following warning: +.sp +.nf +\f3warning: [serial] serializable class PersistentTime has no definition of\fP +.fi +.nf +\f3serialVersionUID\fP +.fi +.nf +\f3\fP +.fi +.sp + + +If a serializable class does not explicitly declare a field named \f3serialVersionUID\fR, then the serialization runtime environment calculates a default \f3serialVersionUID\fR value for that class based on various aspects of the class, as described in the Java Object Serialization Specification\&. However, it is strongly recommended that all serializable classes explicitly declare \f3serialVersionUID\fR values because the default process of computing \f3serialVersionUID\fR vales is highly sensitive to class details that can vary depending on compiler implementations, and as a result, might cause an unexpected \f3InvalidClassExceptions\fR during deserialization\&. To guarantee a consistent \f3serialVersionUID\fR value across different Java compiler implementations, a serializable class must declare an explicit \f3serialVersionUID\fR value\&. +.TP +static +Warns about issues relating to the use of statics, for example: +.sp +.nf +\f3class XLintStatic {\fP +.fi +.nf +\f3 static void m1() { }\fP +.fi +.nf +\f3 void m2() { this\&.m1(); }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The compiler generates the following warning: +.sp +.nf +\f3warning: [static] static method should be qualified by type name, \fP +.fi +.nf +\f3XLintStatic, instead of by an expression\fP +.fi +.nf +\f3\fP +.fi +.sp + + +To resolve this issue, you can call the \f3static\fR method \f3m1\fR as follows: +.sp +.nf +\f3XLintStatic\&.m1();\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Alternately, you can remove the \f3static\fR keyword from the declaration of the method \f3m1\fR\&. +.TP +try +Warns about issues relating to use of \f3try\fR blocks, including try-with-resources statements\&. For example, a warning is generated for the following statement because the resource \f3ac\fR declared in the \f3try\fR block is not used: +.sp +.nf +\f3try ( AutoCloseable ac = getResource() ) { // do nothing}\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +unchecked +Gives more detail for unchecked conversion warnings that are mandated by the Java Language Specification, for example: +.sp +.nf +\f3List l = new ArrayList<Number>();\fP +.fi +.nf +\f3List<String> ls = l; // unchecked warning\fP +.fi +.nf +\f3\fP +.fi +.sp + + +During type erasure, the types \f3ArrayList<Number>\fR and \f3List<String>\fR become \f3ArrayList\fR and \f3List\fR, respectively\&. + +The \f3ls\fR command has the parameterized type \f3List<String>\fR\&. When the \f3List\fR referenced by \f3l\fR is assigned to \f3ls\fR, the compiler generates an unchecked warning\&. At compile time, the compiler and JVM cannot determine whether \f3l\fR refers to a \f3List<String>\fR type\&. In this case, \f3l\fR does not refer to a \f3List<String>\fR type\&. As a result, heap pollution occurs\&. + +A heap pollution situation occurs when the \f3List\fR object \f3l\fR, whose static type is \f3List<Number>\fR, is assigned to another \f3List\fR object, \f3ls\fR, that has a different static type, \f3List<String>\fR\&. However, the compiler still allows this assignment\&. It must allow this assignment to preserve backward compatibility with releases of Java SE that do not support generics\&. Because of type erasure, \f3List<Number>\fR and \f3List<String>\fR both become \f3List\fR\&. Consequently, the compiler allows the assignment of the object \f3l\fR\f3,\fR which has a raw type of \f3List\fR, to the object \f3ls\fR\&. +.TP +varargs +Warns about unsafe usages of variable arguments (\f3varargs\fR) methods, in particular, those that contain non-reifiable arguments, for example: +.sp +.nf +\f3public class ArrayBuilder {\fP +.fi +.nf +\f3 public static <T> void addToList (List<T> listArg, T\&.\&.\&. elements) {\fP +.fi +.nf +\f3 for (T x : elements) {\fP +.fi +.nf +\f3 listArg\&.add(x);\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\fINote:\fR A non-reifiable type is a type whose type information is not fully available at runtime\&. + +The compiler generates the following warning for the definition of the method \f3ArrayBuilder\&.addToList\fR +.sp +.nf +\f3warning: [varargs] Possible heap pollution from parameterized vararg type T\fP +.fi +.nf +\f3\fP +.fi +.sp + + +When the compiler encounters a varargs method, it translates the \f3varargs\fR formal parameter into an array\&. However, the Java programming language does not permit the creation of arrays of parameterized types\&. In the method \f3ArrayBuilder\&.addToList\fR, the compiler translates the \f3varargs\fR formal parameter \f3T\&.\&.\&.\fR elements to the formal parameter \f3T[]\fR elements, an array\&. However, because of type erasure, the compiler converts the \f3varargs\fR formal parameter to \f3Object[]\fR elements\&. Consequently, there is a possibility of heap pollution\&. +.SH COMMAND-LINE\ ARGUMENT\ FILES +To shorten or simplify the \f3javac\fR command, you can specify one or more files that contain arguments to the \f3javac\fR command (except \f3-J\fR options)\&. This enables you to create \f3javac\fR commands of any length on any operating system\&. +.PP +An argument file can include \f3javac\fR options and source file names in any combination\&. The arguments within a file can be separated by spaces or new line characters\&. If a file name contains embedded spaces, then put the whole file name in double quotation marks\&. +.PP +File Names within an argument file are relative to the current directory, not the location of the argument file\&. Wild cards (*) are not allowed in these lists (such as for specifying \f3*\&.java\fR)\&. Use of the at sign (@) to recursively interpret files is not supported\&. The \f3-J\fR options are not supported because they are passed to the launcher, which does not support argument files\&. +.PP +When executing the \f3javac\fR command, pass in the path and name of each argument file with the at sign (@) leading character\&. When the \f3javac\fR command encounters an argument beginning with the at sign (@), it expands the contents of that file into the argument list\&. +.PP +\f3Example 1 Single Argument File\fR +.PP +You could use a single argument file named \f3argfile\fR to hold all \f3javac\fR arguments: +.sp +.nf +\f3javac @argfile\fP +.fi +.nf +\f3\fP +.fi +.sp +This argument file could contain the contents of both files shown in Example 2 +.PP +\f3Example 2 Two Argument Files\fR +.PP +You can create two argument files: one for the \f3javac\fR options and the other for the source file names\&. Note that the following lists have no line-continuation characters\&. +.PP +Create a file named options that contains the following: +.sp +.nf +\f3\-d classes\fP +.fi +.nf +\f3\-g\fP +.fi +.nf +\f3\-sourcepath /java/pubs/ws/1\&.3/src/share/classes\fP +.fi +.nf +\f3\fP +.fi +.sp +Create a file named classes that contains the following: +.sp +.nf +\f3MyClass1\&.java\fP +.fi +.nf +\f3MyClass2\&.java\fP +.fi +.nf +\f3MyClass3\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +Then, run the \f3javac\fR command as follows: +.sp +.nf +\f3javac @options @classes\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 3 Argument Files with Paths\fR +.PP +The argument files can have paths, but any file names inside the files are relative to the current working directory (not \f3path1\fR or \f3path2\fR): +.sp +.nf +\f3javac @path1/options @path2/classes\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH ANNOTATION\ PROCESSING +The \f3javac\fR command provides direct support for annotation processing, superseding the need for the separate annotation processing command, \f3apt\fR\&. +.PP +The API for annotation processors is defined in the \f3javax\&.annotation\&.processing\fR and j\f3avax\&.lang\&.model\fR packages and subpackages\&. +.SS HOW\ ANNOTATION\ PROCESSING\ WORKS +Unless annotation processing is disabled with the \f3-proc:none\fR option, the compiler searches for any annotation processors that are available\&. The search path can be specified with the \f3-processorpath\fR option\&. If no path is specified, then the user class path is used\&. Processors are located by means of service provider-configuration files named \f3META-INF/services/javax\&.annotation\&.processing\fR\&.Processor on the search path\&. Such files should contain the names of any annotation processors to be used, listed one per line\&. Alternatively, processors can be specified explicitly, using the \f3-processor\fR option\&. +.PP +After scanning the source files and classes on the command line to determine what annotations are present, the compiler queries the processors to determine what annotations they process\&. When a match is found, the processor is called\&. A processor can claim the annotations it processes, in which case no further attempt is made to find any processors for those annotations\&. After all of the annotations are claimed, the compiler does not search for additional processors\&. +.PP +If any processors generate new source files, then another round of annotation processing occurs: Any newly generated source files are scanned, and the annotations processed as before\&. Any processors called on previous rounds are also called on all subsequent rounds\&. This continues until no new source files are generated\&. +.PP +After a round occurs where no new source files are generated, the annotation processors are called one last time, to give them a chance to complete any remaining work\&. Finally, unless the \f3-proc:only\fR option is used, the compiler compiles the original and all generated source files\&. +.SS IMPLICITLY\ LOADED\ SOURCE\ FILES +To compile a set of source files, the compiler might need to implicitly load additional source files\&. See Searching for Types\&. Such files are currently not subject to annotation processing\&. By default, the compiler gives a warning when annotation processing occurred and any implicitly loaded source files are compiled\&. The \f3-implicit\fR option provides a way to suppress the warning\&. +.SH SEARCHING\ FOR\ TYPES +To compile a source file, the compiler often needs information about a type, but the type definition is not in the source files specified on the command line\&. The compiler needs type information for every class or interface used, extended, or implemented in the source file\&. This includes classes and interfaces not explicitly mentioned in the source file, but that provide information through inheritance\&. +.PP +For example, when you create a subclass \f3java\&.applet\&.Applet\fR, you are also using the ancestor classes of \f3Applet\fR: \f3java\&.awt\&.Panel\fR, \f3java\&.awt\&.Container\fR, \f3java\&.awt\&.Component\fR, and \f3java\&.lang\&.Object\fR\&. +.PP +When the compiler needs type information, it searches for a source file or class file that defines the type\&. The compiler searches for class files first in the bootstrap and extension classes, then in the user class path (which by default is the current directory)\&. The user class path is defined by setting the \f3CLASSPATH\fR environment variable or by using the \f3-classpath\fR option\&. +.PP +If you set the \f3-sourcepath\fR option, then the compiler searches the indicated path for source files\&. Otherwise, the compiler searches the user class path for both class files and source files\&. +.PP +You can specify different bootstrap or extension classes with the \f3-bootclasspath\fR and the \f3-extdirs\fR options\&. See Cross-Compilation Options\&. +.PP +A successful type search may produce a class file, a source file, or both\&. If both are found, then you can use the \f3-Xprefer\fR option to instruct the compiler which to use\&. If \f3newer\fR is specified, then the compiler uses the newer of the two files\&. If \f3source\fR is specified, the compiler uses the source file\&. The default is \f3newer\fR\&. +.PP +If a type search finds a source file for a required type, either by itself, or as a result of the setting for the \f3-Xprefer\fR option, then the compiler reads the source file to get the information it needs\&. By default the compiler also compiles the source file\&. You can use the \f3-implicit\fR option to specify the behavior\&. If \f3none\fR is specified, then no class files are generated for the source file\&. If \f3class\fR is specified, then class files are generated for the source file\&. +.PP +The compiler might not discover the need for some type information until after annotation processing completes\&. When the type information is found in a source file and no \f3-implicit\fR option is specified, the compiler gives a warning that the file is being compiled without being subject to annotation processing\&. To disable the warning, either specify the file on the command line (so that it will be subject to annotation processing) or use the \f3-implicit\fR option to specify whether or not class files should be generated for such source files\&. +.SH PROGRAMMATIC\ INTERFACE +The \f3javac\fR command supports the new Java Compiler API defined by the classes and interfaces in the \f3javax\&.tools\fR package\&. +.SS EXAMPLE +To compile as though providing command-line arguments, use the following syntax: +.sp +.nf +\f3JavaCompiler javac = ToolProvider\&.getSystemJavaCompiler();\fP +.fi +.nf +\f3\fP +.fi +.sp +The example writes diagnostics to the standard output stream and returns the exit code that \f3javac\fR would give when called from the command line\&. +.PP +You can use other methods in the \f3javax\&.tools\&.JavaCompiler\fR interface to handle diagnostics, control where files are read from and written to, and more\&. +.SS OLD\ INTERFACE +\fINote:\fR This API is retained for backward compatibility only\&. All new code should use the newer Java Compiler API\&. +.PP +The \f3com\&.sun\&.tools\&.javac\&.Main\fR class provides two static methods to call the compiler from a program: +.sp +.nf +\f3public static int compile(String[] args);\fP +.fi +.nf +\f3public static int compile(String[] args, PrintWriter out);\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3args\fR parameter represents any of the command-line arguments that would typically be passed to the compiler\&. +.PP +The \f3out\fR parameter indicates where the compiler diagnostic output is directed\&. +.PP +The \f3return\fR value is equivalent to the \f3exit\fR value from \f3javac\fR\&. +.PP +\fINote:\fR All other classes and methods found in a package with names that start with \f3com\&.sun\&.tools\&.javac\fR (subpackages of \f3com\&.sun\&.tools\&.javac\fR) are strictly internal and subject to change at any time\&. +.SH EXAMPLES +\f3Example 1 Compile a Simple Program\fR +.PP +This example shows how to compile the \f3Hello\&.java\fR source file in the greetings directory\&. The class defined in \f3Hello\&.java\fR is called \f3greetings\&.Hello\fR\&. The greetings directory is the package directory both for the source file and the class file and is underneath the current directory\&. This makes it possible to use the default user class path\&. It also makes it unnecessary to specify a separate destination directory with the \f3-d\fR option\&. +.PP +The source code in \f3Hello\&.java\fR: +.sp +.nf +\f3package greetings;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3public class Hello {\fP +.fi +.nf +\f3 public static void main(String[] args) {\fP +.fi +.nf +\f3 for (int i=0; i < args\&.length; i++) {\fP +.fi +.nf +\f3 System\&.out\&.println("Hello " + args[i]);\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp +Compile greetings\&.Hello: +.sp +.nf +\f3javac greetings/Hello\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +Run \f3greetings\&.Hello\fR: +.sp +.nf +\f3java greetings\&.Hello World Universe Everyone\fP +.fi +.nf +\f3Hello World\fP +.fi +.nf +\f3Hello Universe\fP +.fi +.nf +\f3Hello Everyone\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 2 Compile Multiple Source Files\fR +.PP +This example compiles the \f3Aloha\&.java\fR, \f3GutenTag\&.java\fR, \f3Hello\&.java\fR, and \f3Hi\&.java\fR source files in the \f3greetings\fR package\&. +.sp +.nf +\f3% javac greetings/*\&.java\fP +.fi +.nf +\f3% ls greetings\fP +.fi +.nf +\f3Aloha\&.class GutenTag\&.class Hello\&.class Hi\&.class\fP +.fi +.nf +\f3Aloha\&.java GutenTag\&.java Hello\&.java Hi\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 3 Specify a User Class Path\fR +.PP +After changing one of the source files in the previous example, recompile it: +.sp +.nf +\f3pwd\fP +.fi +.nf +\f3/examples\fP +.fi +.nf +\f3javac greetings/Hi\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +Because \f3greetings\&.Hi\fR refers to other classes in the \f3greetings\fR package, the compiler needs to find these other classes\&. The previous example works because the default user class path is the directory that contains the package directory\&. If you want to recompile this file without concern for which directory you are in, then add the examples directory to the user class path by setting \f3CLASSPATH\fR\&. This example uses the \f3-classpath\fR option\&. +.sp +.nf +\f3javac \-classpath /examples /examples/greetings/Hi\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +If you change \f3greetings\&.Hi\fR to use a banner utility, then that utility also needs to be accessible through the user class path\&. +.sp +.nf +\f3javac \-classpath /examples:/lib/Banners\&.jar \e\fP +.fi +.nf +\f3 /examples/greetings/Hi\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +To execute a class in the \f3greetings\fR package, the program needs access to the \f3greetings\fR package, and to the classes that the \f3greetings\fR classes use\&. +.sp +.nf +\f3java \-classpath /examples:/lib/Banners\&.jar greetings\&.Hi\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 4 Separate Source Files and Class Files\fR +.PP +The following example uses \f3javac\fR to compile code that runs on JVM 1\&.7\&. +.sp +.nf +\f3javac \-source 1\&.7 \-target 1\&.7 \-bootclasspath jdk1\&.7\&.0/lib/rt\&.jar \e \fP +.fi +.nf +\f3\-extdirs "" OldCode\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3-source 1\&.7\fR option specifies that release 1\&.7 (or 7) of the Java programming language be used to compile \f3OldCode\&.java\fR\&. The option \f3-target 1\&.7\fR option ensures that the generated class files are compatible with JVM 1\&.7\&. Note that in most cases, the value of the \f3-target\fR option is the value of the \f3-source\fR option; in this example, you can omit the \f3-target\fR option\&. +.PP +You must specify the \f3-bootclasspath\fR option to specify the correct version of the bootstrap classes (the \f3rt\&.jar\fR library)\&. If not, then the compiler generates a warning: +.sp +.nf +\f3javac \-source 1\&.7 OldCode\&.java\fP +.fi +.nf +\f3warning: [options] bootstrap class path not set in conjunction with \fP +.fi +.nf +\f3\-source 1\&.7\fP +.fi +.nf +\f3\fP +.fi +.sp +If you do not specify the correct version of bootstrap classes, then the compiler uses the old language rules (in this example, it uses version 1\&.7 of the Java programming language) combined with the new bootstrap classes, which can result in class files that do not work on the older platform (in this case, Java SE 7) because reference to nonexistent methods can get included\&. +.PP +\f3Example 5 Cross Compile\fR +.PP +This example uses \f3javac\fR to compile code that runs on JVM 1\&.7\&. +.sp +.nf +\f3javac \-source 1\&.7 \-target 1\&.7 \-bootclasspath jdk1\&.7\&.0/lib/rt\&.jar \e\fP +.fi +.nf +\f3 \-extdirs "" OldCode\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +The\f3-source 1\&.7\fR option specifies that release 1\&.7 (or 7) of the Java programming language to be used to compile OldCode\&.java\&. The \f3-target 1\&.7\fR option ensures that the generated class files are compatible with JVM 1\&.7\&. +.PP +You must specify the \f3-bootclasspath\fR option to specify the correct version of the bootstrap classes (the \f3rt\&.jar\fR library)\&. If not, then the compiler generates a warning: +.sp +.nf +\f3javac \-source 1\&.7 OldCode\&.java\fP +.fi +.nf +\f3warning: [options] bootstrap class path not set in conjunction with \-source 1\&.7\fP +.fi +.nf +\f3\fP +.fi +.sp +If you do not specify the correct version of bootstrap classes, then the compiler uses the old language rules combined with the new bootstrap classes\&. This combination can result in class files that do not work on the older platform (in this case, Java SE 7) because reference to nonexistent methods can get included\&. In this example, the compiler uses release 1\&.7 of the Java programming language\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +jdb(1) +.TP 0.2i +\(bu +javah(1) +.TP 0.2i +\(bu +javadoc(1) +.TP 0.2i +\(bu +jar(1) +.TP 0.2i +\(bu +jdb(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javadoc.1 b/jdk-1.8.0.281/man/man1/javadoc.1 new file mode 100755 index 0000000..57fd7da --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javadoc.1 @@ -0,0 +1,2984 @@ +'\" t +.\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 03 March 2015 +.\" SectDesc: Basic Tools +.\" Title: javadoc.1 +.\" +.if n .pl 99999 +.TH javadoc 1 "03 March 2015" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +javadoc \- Generates HTML pages of API documentation from Java source files\&. +.SH SYNOPSIS +.sp +.nf + +\fBjavadoc\fR {\fIpackages\fR|\fIsource\-files\fR} [\fIoptions\fR] [\fI@argfiles\fR] +.fi +.sp +.TP +\fIpackages\fR +Names of packages that you want to document, separated by spaces, for example \f3java\&.lang java\&.lang\&.reflect java\&.awt\fR\&. If you want to also document the subpackages, use the \f3-subpackages\fR option to specify the packages\&. + +By default, \f3javadoc\fR looks for the specified packages in the current directory and subdirectories\&. Use the \f3-sourcepath\fR option to specify the list of directories where to look for packages\&. +.TP +\fIsource-files\fR +Names of Java source files that you want to document, separated by spaces, for example \f3Class\&.java Object\&.java Button\&.java\fR\&. By default, \f3javadoc\fR looks for the specified classes in the current directory\&. However, you can specify the full path to the class file and use wildcard characters, for example \f3/home/src/java/awt/Graphics*\&.java\fR\&. You can also specify the path relative to the current directory\&. +.TP +\fIoptions\fR +Command-line options, separated by spaces\&. See Options\&. +.TP +\fI@argfiles\fR +Names of files that contain a list of \f3javadoc\fR command options, package names and source file names in any order\&. +.SH DESCRIPTION +The \f3javadoc\fR command parses the declarations and documentation comments in a set of Java source files and produces a corresponding set of HTML pages that describe (by default) the public and protected classes, nested classes (but not anonymous inner classes), interfaces, constructors, methods, and fields\&. You can use the \f3javadoc\fR command to generate the API documentation or the implementation documentation for a set of source files\&. +.PP +You can run the \f3javadoc\fR command on entire packages, individual source files, or both\&. When documenting entire packages, you can either use the \f3-subpackages\fR option to recursively traverse a directory and its subdirectories, or to pass in an explicit list of package names\&. When you document individual source files, pass in a list of Java source file names\&. See Simple Examples\&. +.SS PROCESS\ SOURCE\ FILES +The \f3javadoc\fR command processes files that end in source and other files described in Source Files\&. If you run the \f3javadoc\fR command by passing in individual source file names, then you can determine exactly which source files are processed\&. However, that is not how most developers want to work, because it is simpler to pass in package names\&. The \f3javadoc\fR command can be run three ways without explicitly specifying the source file names\&. You can pass in package names, use the \f3-subpackages\fR option, or use wild cards with source file names\&. In these cases, the \f3javadoc\fR command processes a source file only when the file fulfills all of the following requirements: +.TP 0.2i +\(bu +The file name prefix (with \f3\&.java\fR removed) is a valid class name\&. +.TP 0.2i +\(bu +The path name relative to the root of the source tree is a valid package name after the separators are converted to dots\&. +.TP 0.2i +\(bu +The package statement contains the valid package name\&. +.PP +Processing Links + +During a run, the \f3javadoc\fR command adds cross-reference links to package, class, and member names that are being documented as part of that run\&. Links appear in the following places\&. See Javadoc Tags for a description of the @ tags\&. +.TP 0.2i +\(bu +Declarations (return types, argument types, and field types)\&. +.TP 0.2i +\(bu +\fISee Also\fR sections that are generated from \f3@see\fR tags\&. +.TP 0.2i +\(bu +Inline text generated from \f3{@link}\fR tags\&. +.TP 0.2i +\(bu +Exception names generated from \f3@throws\fR tags\&. +.TP 0.2i +\(bu +\fISpecified by\fR links to interface members and \fIOverrides\fR links to class members\&. See Method Comment Inheritance\&. +.TP 0.2i +\(bu +Summary tables listing packages, classes and members\&. +.TP 0.2i +\(bu +Package and class inheritance trees\&. +.TP 0.2i +\(bu +The index\&. +.PP +You can add links to existing text for classes not included on the command line (but generated separately) by way of the \f3-link\fR and \f3-linkoffline\fR options\&. +.PP +Processing Details + +The \f3javadoc\fR command produces one complete document every time it runs\&. It does not do incremental builds that modify or directly incorporate the results from earlier runs\&. However, the \f3javadoc\fR command can link to results from other runs\&. +.PP +The \f3javadoc\fR command implementation requires and relies on the Java compiler\&. The \f3javadoc\fR command calls part of the \f3javac\fR command to compile the declarations and ignore the member implementations\&. The \f3javadoc\fR command builds a rich internal representation of the classes that includes the class hierarchy and use relationships to generate the HTML\&. The \f3javadoc\fR command also picks up user-supplied documentation from documentation comments in the source code\&. See Documentation Comments\&. +.PP +The \f3javadoc\fR command runs on source files that are pure stub files with no method bodies\&. This means you can write documentation comments and run the \f3javadoc\fR command in the early stages of design before API implementation\&. +.PP +Relying on the compiler ensures that the HTML output corresponds exactly with the actual implementation, which may rely on implicit, rather than explicit, source code\&. For example, the \f3javadoc\fR command documents default constructors that are present in the compiled class files but not in the source code\&. +.PP +In many cases, the \f3javadoc\fR command lets you generate documentation for source files with incomplete or erroneous code\&. You can generate documentation before all debugging and troubleshooting is done\&. The \f3javadoc\fR command does primitive checking of documentation comments\&. +.PP +When the \f3javadoc\fR command builds its internal structure for the documentation, it loads all referenced classes\&. Because of this, the \f3javadoc\fR command must be able to find all referenced classes, whether bootstrap classes, extensions, or user classes\&. See How Classes Are Found at http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html +.PP +Typically, classes you create must either be loaded as an extension or in the \f3javadoc\fR command class path\&. +.SS JAVADOC\ DOCLETS +You can customize the content and format of the \f3javadoc\fR command output with doclets\&. The \f3javadoc\fR command has a default built-in doclet, called the standard doclet, that generates HTML-formatted API documentation\&. You can modify or make a subclass of the standard doclet, or write your own doclet to generate HTML, XML, MIF, RTF or whatever output format you want\&. +.PP +When a custom doclet is not specified with the \f3-doclet\fR option, the \f3javadoc\fR command uses the default standard doclet\&. The \f3javadoc\fR command has several options that are available regardless of which doclet is being used\&. The standard doclet adds a supplementary set of command-line options\&. See Options\&. +.SH SOURCE\ FILES +The \f3javadoc\fR command generates output that originates from the following types of source files: Java language source files for classes (\f3\&.java\fR), package comment files, overview comment files, and miscellaneous unprocessed files\&. This section also describes test files and template files that can also be in the source tree, but that you want to be sure not to document\&. +.SS CLASS\ SOURCE\ FILES +Each class or interface and its members can have their own documentation comments contained in a source file\&. See Documentation Comments\&. +.SS PACKAGE\ COMMENT\ FILES +Each package can have its own documentation comment, contained in its own source file, that the \f3javadoc\fR command merges into the generated package summary page\&. You typically include in this comment any documentation that applies to the entire package\&. +.PP +To create a package comment file, you can place your comments in one of the following files: +.TP 0.2i +\(bu +The \f3package-info\&.java\fR file can contain the package declaration, package annotations, package comments, and Javadoc tags\&. This file is preferred\&. +.TP 0.2i +\(bu +The \f3package\&.html\fR file contains only package comments and Javadoc tags\&. No package annotations\&. +.PP +A package can have a single \f3package\&.html\fR file or a single \f3package-info\&.java\fR file, but not both\&. Place either file in the package directory in the source tree with your source files\&. +.PP +The package-info\&.java File + +The \f3package-info\&.java\fR file can contain a package comment of the following structure\&. The comment is placed before the package declaration\&. +.PP +\fINote:\fR The comment separators \f3/**\fR and \f3*/\fR must be present, but the leading asterisks on the intermediate lines can be left off\&. +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * Provides the classes necessary to create an \fP +.fi +.nf +\f3 * applet and the classes an applet uses \fP +.fi +.nf +\f3 * to communicate with its applet context\&.\fP +.fi +.nf +\f3 * <p>\fP +.fi +.nf +\f3 * The applet framework involves two entities:\fP +.fi +.nf +\f3 * the applet and the applet context\&.\fP +.fi +.nf +\f3 * An applet is an embeddable window (see the\fP +.fi +.nf +\f3 * {@link java\&.awt\&.Panel} class) with a few extra\fP +.fi +.nf +\f3 * methods that the applet context can use to \fP +.fi +.nf +\f3 * initialize, start, and stop the applet\&.\fP +.fi +.nf +\f3 *\fP +.fi +.nf +\f3 * @since 1\&.0\fP +.fi +.nf +\f3 * @see java\&.awt\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3package java\&.lang\&.applet;\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +The package\&.html File + +The \f3package\&.html\fR file can contain a package comment of the following structure\&. The comment is placed in the \f3<body>\fR element\&. +.PP +File: \f3java/applet/package\&.html\fR +.sp +.nf +\f3<HTML>\fP +.fi +.nf +\f3<BODY>\fP +.fi +.nf +\f3Provides the classes necessary to create an applet and the \fP +.fi +.nf +\f3classes an applet uses to communicate with its applet context\&.\fP +.fi +.nf +\f3<p>\fP +.fi +.nf +\f3The applet framework involves two entities: the applet\fP +.fi +.nf +\f3and the applet context\&. An applet is an embeddable\fP +.fi +.nf +\f3window (see the {@link java\&.awt\&.Panel} class) with a\fP +.fi +.nf +\f3few extra methods that the applet context can use to\fP +.fi +.nf +\f3initialize, start, and stop the applet\&. \fP +.fi +.nf +\f3\fP +.fi +.nf +\f3@since 1\&.0 \fP +.fi +.nf +\f3@see java\&.awt\fP +.fi +.nf +\f3</BODY>\fP +.fi +.nf +\f3</HTML>\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3package\&.html\fR file is a typical HTML file and does not include a package declaration\&. The content of the package comment file is written in HTML with one exception\&. The documentation comment should not include the comment separators \f3/**\fR and \f3*/\fR or leading asterisks\&. When writing the comment, make the first sentence a summary about the package, and do not put a title or any other text between the \f3<body>\fR tag and the first sentence\&. You can include package tags\&. All block tags must appear after the main description\&. If you add an \f3@see\fR tag in a package comment file, then it must have a fully qualified name\&. +.PP +Processing the Comment File + +When the \f3javadoc\fR command runs, it searches for the package comment file\&. If the package comment file is found, then the \f3javadoc\fR command does the following: +.TP 0.2i +\(bu +Copies the comment for processing\&. For package\&.html, the \f3javadoc\fR command copies all content between the \f3<body>\fR and \f3</body>\fR HTML tags\&. You can include a \f3<head>\fR section to put a \f3<title>\fR tag, source file copyright statement, or other information, but none of these appear in the generated documentation\&. +.TP 0.2i +\(bu +Processes the package tags\&. See Package Tags\&. +.TP 0.2i +\(bu +Inserts the processed text at the bottom of the generated package summary page\&. See Java Platform, Standard Edition API Specification Overview at http://docs\&.oracle\&.com/javase/8/docs/api/overview-summary\&.html +.TP 0.2i +\(bu +Copies the first sentence of the package comment to the top of the package summary page\&. The \f3javadoc\fR command also adds the package name and this first sentence to the list of packages on the overview page\&. See Java Platform, Standard Edition API Specification Overview at http://docs\&.oracle\&.com/javase/8/docs/api/overview-summary\&.html + +The end of the sentence is determined by the same rules used for the end of the first sentence of class and member main descriptions\&. +.SS OVERVIEW\ COMMENT\ FILES +Each application or set of packages that you are documenting can have its own overview documentation comment that is kept in its own source file, that the \f3javadoc\fR command merges into the generated overview page\&. You typically include in this comment any documentation that applies to the entire application or set of packages\&. +.PP +You can name the file anything you want such as overview\&.html and place it anywhere\&. A typical location is at the top of the source tree\&. +.PP +For example, if the source files for the \f3java\&.applet\fR package are contained in the /home/user/src/java/applet directory, then you could create an overview comment file at /home/user/src/overview\&.html\&. +.PP +You can have multiple overview comment files for the same set of source files in case you want to run the \f3javadoc\fR command multiple times on different sets of packages\&. For example, you could run the \f3javadoc\fR command once with \f3-private\fR for internal documentation and again without that option for public documentation\&. In this case, you could describe the documentation as public or internal in the first sentence of each overview comment file\&. +.PP +The content of the overview comment file is one big documentation comment that is written in HTML\&. Make the first sentence a summary about the application or set of packages\&. Do not put a title or any other text between the \f3<body>\fR tag and the first sentence\&. All tags except inline tags, such as an {\f3@link}\fR tag, must appear after the main description\&. If you add an \f3@see\fR tag, then it must have a fully qualified name\&. +.PP +When you run the \f3javadoc\fR command, specify the overview comment file name with the \f3-overview\fR option\&. The file is then processed similarly to that of a package comment file\&. The \f3javadoc\fR command does the following: +.TP 0.2i +\(bu +Copies all content between the \f3<body>\fR and \f3</body>\fR tags for processing\&. +.TP 0.2i +\(bu +Processes the overview tags that are present\&. See Overview Tags\&. +.TP 0.2i +\(bu +Inserts the processed text at the bottom of the generated overview page\&. See Java Platform Standard Edition API Specification Overview at http://docs\&.oracle\&.com/javase/8/docs/api/overview-summary\&.html +.TP 0.2i +\(bu +Copies the first sentence of the overview comment to the top of the overview summary page\&. +.SS UNPROCESSED\ FILES +Your source files can include any files that you want the \f3javadoc\fR command to copy to the destination directory\&. These files usually include graphic files, example Java source and class files, and self-standing HTML files with a lot of content that would overwhelm the documentation comment of a typical Java source file\&. +.PP +To include unprocessed files, put them in a directory called doc-files\&. The doc-files directory can be a subdirectory of any package directory that contains source files\&. You can have one doc-files subdirectory for each package\&. +.PP +For example, if you want to include the image of a button in the \f3java\&.awt\&.Button\fR class documentation, then place the image file in the /home/user/src/java/awt/doc-files/ directory\&. Do not place the doc-files directory at /home/user/src/java/doc-files, because java is not a package\&. It does not contain any source files\&. +.PP +All links to the unprocessed files must be included in the code because the \f3javadoc\fR command does not look at the files\&. The \f3javadoc\fR command copies the directory and all of its contents to the destination\&. The following example shows how the link in the Button\&.java documentation comment might look: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * This button looks like this: \fP +.fi +.nf +\f3 * <img src="doc\-files/Button\&.gif">\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS TEST\ AND\ TEMPLATE\ FILES +You can store test and template files in the source tree in the same directory with or in a subdirectory of the directory where the source files reside\&. To prevent test and template files from being processed, run the \f3javadoc\fR command and explicitly pass in individual source file names\&. +.PP +Test files are valid, compilable source files\&. Template files are not valid, compatible source files, but they often have the \f3\&.java\fR suffix\&. +.PP +Test Files + +If you want your test files to belong to either an unnamed package or to a package other than the package that the source files are in, then put the test files in a subdirectory underneath the source files and give the directory an invalid name\&. If you put the test files in the same directory with the source and call the \f3javadoc\fR command with a command-line argument that indicates its package name, then the test files cause warnings or errors\&. If the files are in a subdirectory with an invalid name, then the test file directory is skipped and no errors or warnings are issued\&. For example, to add test files for source files in com\&.package1, put them in a subdirectory in an invalid package name\&. The following directory name is invalid because it contains a hyphen: +.sp +.nf +\f3com/package1/test\-files/\fP +.fi +.nf +\f3\fP +.fi +.sp +If your test files contain documentation comments, then you can set up a separate run of the \f3javadoc\fR command to produce test file documentation by passing in their test source file names with wild cards, such as \f3com/package1/test-files/*\&.java\fR\&. +.PP +Template Files + +If you want a template file to be in the source directory, but not generate errors when you execute the \f3javadoc\fR command, then give it an invalid file name such as \f3Buffer-Template\&.java\fR to prevent it from being processed\&. The \f3javadoc\fR command only processes source files with names, when stripped of the \f3\&.java\fR suffix, that are valid class names\&. +.SH GENERATED\ FILES +By default, the \f3javadoc\fR command uses a standard doclet that generates HTML-formatted documentation\&. The standard doclet generates basic content, cross-reference, and support pages described here\&. Each HTML page corresponds to a separate file\&. The \f3javadoc\fR command generates two types of files\&. The first type is named after classes and interfaces\&. The second type contain hyphens (such as package-summary\&.html) to prevent conflicts with the first type of file\&. +.SS BASIC\ CONTENT\ PAGES +.TP 0.2i +\(bu +One class or interface page (classname\&.html) for each class or interface being documented\&. +.TP 0.2i +\(bu +One package page (package-summary\&.html) for each package being documented\&. The \f3javadoc\fR command includes any HTML text provided in a file with the name package\&.html or package-info\&.java in the package directory of the source tree\&. +.TP 0.2i +\(bu +One overview page (overview-summary\&.html) for the entire set of packages\&. The overview page is the front page of the generated document\&. The \f3javadoc\fR command includes any HTML text provided in a file specified by the \f3-overview\fR option\&. The Overview page is created only when you pass two or more package names into the \f3javadoc\fR command\&. See HTML Frames and Options\&. +.SS CROSS-REFERENCE\ PAGES +.TP 0.2i +\(bu +One class hierarchy page for the entire set of packages (overview-tree\&.html)\&. To view the hierarchy page, click \fIOverview\fR in the navigation bar and click \fITree\fR\&. +.TP 0.2i +\(bu +One class hierarchy page for each package (package-tree\&.html) To view the hierarchy page, go to a particular package, class, or interface page, and click \fITree\fR to display the hierarchy for that package\&. +.TP 0.2i +\(bu +One use page for each package (package-use\&.html) and a separate use page for each class and interface (class-use/classname\&.html)\&. The use page describes what packages, classes, methods, constructors and fields use any part of the specified class, interface, or package\&. For example, given a class or interface A, its use page includes subclasses of A, fields declared as A, methods that return A, and methods and constructors with parameters of type A\&. To view the use page, go to the package, class, or interface and click the \fIUse\fR link in the navigation bar\&. +.TP 0.2i +\(bu +A deprecated API page (deprecated-list\&.html) that lists all deprecated APIs and their suggested replacements\&. Avoid deprecated APIs because they can be removed in future implementations\&. +.TP 0.2i +\(bu +A constant field values page (constant-values\&.html) for the values of static fields\&. +.TP 0.2i +\(bu +A serialized form page (serialized-form\&.html) that provides information about serializable and externalizable classes with field and method descriptions\&. The information on this page is of interest to reimplementors, and not to developers who want to use the API\&. To access the serialized form page, go to any serialized class and click \fISerialized Form\fR in the See Also section of the class comment\&. The standard doclet generates a serialized form page that lists any class (public or non-public) that implements Serializable with its \f3readObject\fR and \f3writeObject\fR methods, the fields that are serialized, and the documentation comments from the \f3@serial\fR, \f3@serialField\fR, and \f3@serialData\fR tags\&. Public serializable classes can be excluded by marking them (or their package) with \f3@serial\fR exclude, and package-private serializable classes can be included by marking them (or their package) with an \f3@serial\fR include\&. As of Release 1\&.4, you can generate the complete serialized form for public and private classes by running the \f3javadoc\fR command without specifying the \f3-private\fR option\&. See Options\&. +.TP 0.2i +\(bu +An index page (\f3index-*\&.html\fR) of all class, interface, constructor, field and method names, in alphabetical order\&. The index page is internationalized for Unicode and can be generated as a single file or as a separate file for each starting character (such as A\(enZ for English)\&. +.SS SUPPORT\ PAGES +.TP 0.2i +\(bu +A help page (help-doc\&.html) that describes the navigation bar and the previous pages\&. Use \f3-helpfile\fR to override the default help file with your own custom help file\&. +.TP 0.2i +\(bu +One index\&.html file that creates the HTML frames for display\&. Load this file to display the front page with frames\&. The index\&.html file contains no text content\&. +.TP 0.2i +\(bu +Several frame files (\f3*-frame\&.html\fR) that contains lists of packages, classes, and interfaces\&. The frame files display the HTML frames\&. +.TP 0.2i +\(bu +A package list file (package-list) that is used by the \f3-link\fR and \f3-linkoffline\fR options\&. The package list file is a text file that is not reachable through links\&. +.TP 0.2i +\(bu +A style sheet file (stylesheet\&.css) that controls a limited amount of color, font family, font size, font style, and positioning information on the generated pages\&. +.TP 0.2i +\(bu +A doc-files directory that holds image, example, source code, or other files that you want copied to the destination directory\&. These files are not processed by the \f3javadoc\fR command\&. This directory is not processed unless it exists in the source tree\&. +.PP +See Options\&. +.SS HTML\ FRAMES +The \f3javadoc\fR command generates the minimum number of frames (two or three) necessary based on the values passed to the command\&. It omits the list of packages when you pass a single package name or source files that belong to a single package as an argument to the \f3javadoc\fR command\&. Instead, the \f3javadoc\fR command creates one frame in the left-hand column that displays the list of classes\&. When you pass two or more package names, the \f3javadoc\fR command creates a third frame that lists all packages and an overview page (overview-summary\&.html)\&. To bypass frames, click the \fINo Frames\fR link or enter the page set from the overview-summary\&.html page\&. +.SS GENERATED\ FILE\ STRUCTURE +The generated class and interface files are organized in the same directory hierarchy that Java source files and class files are organized\&. This structure is one directory per subpackage\&. +.PP +For example, the document generated for the \f3java\&.applet\&.Applet\fR class would be located at java/applet/Applet\&.html\&. +.PP +The file structure for the \f3java\&.applet\fR package follows, assuming that the destination directory is named \f3apidocs\fR\&. All files that contain the word \fIframe\fR appear in the upper-left or lower-left frames, as noted\&. All other HTML files appear in the right-hand frame\&. +.PP +Directories are bold\&. The asterisks (*) indicate the files and directories that are omitted when the arguments to the \f3javadoc\fR command are source file names rather than package names\&. When arguments are source file names, an empty package list is created\&. The doc-files directory is not created in the destination unless it exists in the source tree\&. See Generated Files\&. +.TP 0.2i +\(bu +\fIapidocs\fR: Top-level directory +.RS +.TP 0.2i +\(bu +index\&.html: Initial Page that sets up HTML frames +.TP 0.2i +\(bu +*overview-summary\&.html: Package list with summaries +.TP 0.2i +\(bu +overview-tree\&.html: Class hierarchy for all packages +.TP 0.2i +\(bu +deprecated-list\&.html: Deprecated APIs for all packages +.TP 0.2i +\(bu +constant-values\&.html: Static field values for all packages +.TP 0.2i +\(bu +serialized-form\&.html: Serialized forms for all packages +.TP 0.2i +\(bu +*overview-frame\&.html: All packages for display in upper-left frame +.TP 0.2i +\(bu +allclasses-frame\&.html: All classes for display in lower-left frame +.TP 0.2i +\(bu +help-doc\&.html: Help about Javadoc page organization +.TP 0.2i +\(bu +index-all\&.html: Default index created without \f3-splitindex\fR option +.TP 0.2i +\(bu +\fIindex-files\fR: Directory created with \f3-splitindex\fR option +.RS +.TP 0.2i +\(bu +index-<number>\&.html: Index files created with \f3-splitindex\fR option +.RE + +.TP 0.2i +\(bu +package-list: Package names for resolving external references +.TP 0.2i +\(bu +stylesheet\&.css: Defines fonts, colors, positions, and so on +.RE + +.TP 0.2i +\(bu +\fIjava\fR: Package directory +.RS +.TP 0.2i +\(bu +\fIapplet\fR: Subpackage directory +.RS +.TP 0.2i +\(bu +Applet\&.html: \f3Applet\fR class page +.TP 0.2i +\(bu +AppletContext\&.html: \f3AppletContext\fR interface +.TP 0.2i +\(bu +AppletStub\&.html: \f3AppletStub\fR interface +.TP 0.2i +\(bu +AudioClip\&.html: \f3AudioClip\fR interface +.TP 0.2i +\(bu +package-summary\&.html: Classes with summaries +.TP 0.2i +\(bu +package-frame\&.html: Package classes for display in lower-left frame +.TP 0.2i +\(bu +package-tree\&.html: Class hierarchy for this package +.TP 0.2i +\(bu +package-use\&.html: Where this package is used +.TP 0.2i +\(bu +\fIdoc-files\fR: Image and example files directory +.TP 0.2i +\(bu +\fIclass-use\fR: Image and examples file location + +- Applet\&.html: Uses of the Applet class + +- AppletContext\&.html: Uses of the \f3AppletContext\fR interface + +- AppletStub\&.html: Uses of the \f3AppletStub\fR interface + +- AudioClip\&.html: Uses of the \f3AudioClip\fR interface +.RE + +.RE + +.TP 0.2i +\(bu +\fIsrc-html\fR: Source code directory +.RS +.TP 0.2i +\(bu +\fIjava\fR: Package directory +.RS +.TP 0.2i +\(bu +\fIapplet\fR: Subpackage directory + +- Applet\&.html: Applet source code + +- AppletContext\&.html: \f3AppletContext\fR source code + +- AppletStub\&.html: \f3AppletStub\fR source code + +- AudioClip\&.html: \f3AudioClip\fR source code +.RE + +.RE + +.SS GENERATED\ API\ DECLARATIONS +The \f3javadoc\fR command generates a declaration at the start of each class, interface, field, constructor, and method description for that API item\&. For example, the declaration for the \f3Boolean\fR class is: +.sp +.nf +\f3public final class Boolean\fP +.fi +.nf +\f3extends Object\fP +.fi +.nf +\f3implements Serializable\fP +.fi +.nf +\f3\fP +.fi +.sp +The declaration for the \f3Boolean\&.valueOf\fR method is: +.sp +.nf +\f3public static Boolean valueOf(String s)\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3javadoc\fR command can include the modifiers \f3public\fR, \f3protected\fR, \f3private\fR, \f3abstract\fR, \f3final\fR, \f3static\fR, \f3transient\fR, and \f3volatile\fR, but not \f3synchronized\fR or \f3native\fR\&. The \f3synchronized\fR and \f3native\fR modifiers are considered implementation detail and not part of the API specification\&. +.PP +Rather than relying on the keyword \f3synchronized\fR, APIs should document their concurrency semantics in the main description of the comment\&. For example, a description might be: A single enumeration cannot be used by multiple threads concurrently\&. The document should not describe how to achieve these semantics\&. As another example, while the \f3Hashtable\fR option should be thread-safe, there is no reason to specify that it is achieved by synchronizing all of its exported methods\&. It is better to reserve the right to synchronize internally at the bucket level for higher concurrency\&. +.SH DOCUMENTATION\ COMMENTS +This section describes source code comments and comment inheritance\&. +.SS SOURCE\ CODE\ COMMENTS +You can include documentation comments in the source code, ahead of declarations for any class, interface, method, constructor, or field\&. You can also create documentation comments for each package and another one for the overview, though their syntax is slightly different\&. A documentation comment consists of the characters between \f3/**\fR and \f3*/\fR that end it\&. Leading asterisks are allowed on each line and are described further in the following section\&. The text in a comment can continue onto multiple lines\&. +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * This is the typical format of a simple documentation comment\fP +.fi +.nf +\f3 * that spans two lines\&.\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp +To save space you can put a comment on one line: +.sp +.nf +\f3/** This comment takes up only one line\&. */\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Placement of Comments + +Documentation comments are recognized only when placed immediately before class, interface, constructor, method, or field declarations\&. Documentation comments placed in the body of a method are ignored\&. The \f3javadoc\fR command recognizes only one documentation comment per declaration statement\&. See Where Tags Can Be Used\&. +.PP +A common mistake is to put an \f3import\fR statement between the class comment and the class declaration\&. Do not put an \f3import\fR statement at this location because the \f3javadoc\fR command ignores the class comment\&. +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * This is the class comment for the class Whatever\&.\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3import com\&.example; // MISTAKE \- Important not to put import statement here\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3public class Whatever{ }\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Parts of Comments + +A documentation comment has a main description followed by a tag section\&. The main description begins after the starting delimiter \f3/**\fR and continues until the tag section\&. The tag section starts with the first block tag, which is defined by the first \f3@\fR character that begins a line (ignoring leading asterisks, white space, and leading separator \f3/**\fR)\&. It is possible to have a comment with only a tag section and no main description\&. The main description cannot continue after the tag section begins\&. The argument to a tag can span multiple lines\&. There can be any number of tags, and some types of tags can be repeated while others cannot\&. For example, this \f3@see\fR tag starts the tag section: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * This sentence holds the main description for this documentation comment\&.\fP +.fi +.nf +\f3 * @see java\&.lang\&.Object\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Block and inline Tags + +A tag is a special keyword within a documentation comment that the \f3javadoc\fR command processes\&. There are two kinds of tags: block tags, which appear as an \f3@tag\fR tag (also known as standalone tags), and inline tags, which appear within braces, as an \f3{@tag}\fR tag\&. To be interpreted, a block tag must appear at the beginning of a line, ignoring leading asterisks, white space, and the separator (\f3/**\fR)\&. This means you can use the \f3@\fR character elsewhere in the text and it will not be interpreted as the start of a tag\&. If you want to start a line with the \f3@\fR character and not have it be interpreted, then use the HTML entity \f3@\fR\&. Each block tag has associated text, which includes any text following the tag up to, but not including, either the next tag, or the end of the documentation comment\&. This associated text can span multiple lines\&. An inline tag is allowed and interpreted anywhere that text is allowed\&. The following example contains the \f3@deprecated\fR block tag and the \f3{@link}\fR inline tag\&. See Javadoc Tags\&. +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * @deprecated As of JDK 1\&.1, replaced by {@link #setBounds(int,int,int,int)}\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Write Comments in HTML + +The text must be written in HTML with HTML entities and HTML tags\&. You can use whichever version of HTML your browser supports\&. The standard doclet generates HTML 3\&.2-compliant code elsewhere (outside of the documentation comments) with the inclusion of cascading style sheets and frames\&. HTML 4\&.0 is preferred for generated files because of the frame sets\&. +.PP +For example, entities for the less than symbol (<) and the greater than symbol (>) should be written as \f3<\fR and \f3>\fR\&. Similarly, the ampersand (&) should be written as \f3&\fR\&. The bold HTML tag \f3<b>\fR is shown in the following example\&. +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * This is a <b>doc</b> comment\&.\fP +.fi +.nf +\f3 * @see java\&.lang\&.Object\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Leading Asterisks + +When the \f3javadoc\fR command parses a documentation comment, leading asterisks (*) on each line are discarded, and blanks and tabs that precede the initial asterisks (*) are also discarded\&. If you omit the leading asterisk on a line, then the leading white space is no longer removed so that you can paste code examples directly into a documentation comment inside a \f3<PRE>\fR tag with its indentation preserved\&. Spaces are interpreted by browsers more uniformly than tabs\&. Indentation is relative to the left margin (rather than the separator \f3/**\fR or \f3<PRE>\fR tag)\&. +.PP +First Sentence + +The first sentence of each documentation comment should be a summary sentence that contains a concise but complete description of the declared entity\&. This sentence ends at the first period that is followed by a blank, tab, or line terminator, or at the first block tag\&. The \f3javadoc\fR command copies this first sentence to the member summary at the top of the HTML page\&. +.PP +Multiple-Field Declarations + +The Java platform lets you declare multiple fields in a single statement, but this statement can have only one documentation comment that is copied for all fields\&. If you want individual documentation comments for each field, then declare each field in a separate statement\&. For example, the following documentation comment does not make sense written as a single declaration and would be better handled as two declarations: +.sp +.nf +\f3/** \fP +.fi +.nf +\f3 * The horizontal and vertical distances of point (x,y)\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3public int x, y; // Avoid this \fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3javadoc\fR command generates the following documentation from the previous code: +.sp +.nf +\f3public int x\fP +.fi +.nf +\f3\fP +.fi +.sp +The horizontal and vertical distances of point (x, y)\&. +.sp +.nf +\f3public int y\fP +.fi +.nf +\f3\fP +.fi +.sp +The horizontal and vertical distances of point (x, y)\&. +.PP +Use of Header Tags + +When writing documentation comments for members, it is best not to use HTML heading tags such as \f3<H1>\fR and \f3<H2>\fR, because the \f3javadoc\fR command creates an entire structured document, and these structural tags might interfere with the formatting of the generated document\&. However, you can use these headings in class and package comments to provide your own structure\&. +.SS METHOD\ COMMENT\ INHERITANCE +The \f3javadoc\fR command allows method comment inheritance in classes and interfaces to fill in missing text or to explicitly inherit method comments\&. Constructors, fields, and nested classes do not inherit documentation comments\&. +.PP +\fINote:\fR The source file for an inherited method must be on the path specified by the \f3-sourcepath\fR option for the documentation comment to be available to copy\&. Neither the class nor its package needs to be passed in on the command line\&. This contrasts with Release 1\&.3\&.\fIn\fR and earlier releases, where the class had to be a documented class\&. +.PP +Fill in Missing Text + +When a main description, or \f3@return\fR, \f3@param\fR, or \f3@throws\fR tag is missing from a method comment, the \f3javadoc\fR command copies the corresponding main description or tag comment from the method it overrides or implements (if any)\&. See Method Comment Inheritance\&. +.PP +When an \f3@param\fR tag for a particular parameter is missing, the comment for that parameter is copied from the method further up the inheritance hierarchy\&. When an \f3@throws\fR tag for a particular exception is missing, the \f3@throws\fR tag is copied only when that exception is declared\&. +.PP +This behavior contrasts with Release 1\&.3 and earlier, where the presence of any main description or tag would prevent all comments from being inherited\&. +.PP +See Javadoc Tags and Options\&. +.PP +Explicit Inheritance + +Insert the \f3{@inheritDoc}\fR inline tag in a method main description or \f3@return\fR, \f3@param\fR, or \f3@throws\fR tag comment\&. The corresponding inherited main description or tag comment is copied into that spot\&. +.SS CLASS\ AND\ INTERFACE\ INHERITANCE +Comment inheritance occurs in all possible cases of inheritance from classes and interfaces: +.TP 0.2i +\(bu +When a method in a class overrides a method in a superclass +.TP 0.2i +\(bu +When a method in an interface overrides a method in a superinterface +.TP 0.2i +\(bu +When a method in a class implements a method in an interface +.PP +In the first two cases, the \f3javadoc\fR command generates the subheading \fIOverrides\fR in the documentation for the overriding method\&. A link to the method being overridden is included, whether or not the comment is inherited\&. +.PP +In the third case, when a method in a specified class implements a method in an interface, the \f3javadoc\fR command generates the subheading \fISpecified by\fR in the documentation for the overriding method\&. A link to the method being implemented is included, whether or not the comment is inherited\&. +.SS METHOD\ COMMENTS\ ALGORITHM +If a method does not have a documentation comment, or has an \f3{@inheritDoc}\fR tag, then the \f3javadoc\fR command uses the following algorithm to search for an applicable comment\&. The algorithm is designed to find the most specific applicable documentation comment, and to give preference to interfaces over superclasses: +.TP 0.4i +1\&. +Look in each directly implemented (or extended) interface in the order they appear following the word \f3implements\fR (or \f3extends\fR) in the method declaration\&. Use the first documentation comment found for this method\&. +.TP 0.4i +2\&. +If Step 1 failed to find a documentation comment, then recursively apply this entire algorithm to each directly implemented (or extended) interface in the same order they were examined in Step 1\&. +.TP 0.4i +3\&. +When Step 2 fails to find a documentation comment and this is a class other than the \f3Object\fR class, but not an interface: +.RS +.TP 0.4i +1\&. +If the superclass has a documentation comment for this method, then use it\&. +.TP 0.4i +2\&. +If Step 3a failed to find a documentation comment, then recursively apply this entire algorithm to the superclass\&. +.RE + +.SH JAVADOC\ TAGS +The \f3javadoc\fR command parses special tags when they are embedded within a Java documentation comment\&. The \f3javadoc\fR tags let you autogenerate a complete, well-formatted API from your source code\&. The tags start with an at sign (\f3@\fR) and are case-sensitive\&. They must be typed with the uppercase and lowercase letters as shown\&. A tag must start at the beginning of a line (after any leading spaces and an optional asterisk), or it is treated as text\&. By convention, tags with the same name are grouped together\&. For example, put all \f3@see\fR tags together\&. For more information, see Where Tags Can Be Used\&. +.PP +Tags have the following types: +.TP 0.2i +\(bu +Bock tags: Place block tags only in the tag section that follows the description\&. Block tags have the form: \fI@tag\fR\&. +.TP 0.2i +\(bu +Inline tags: Place inline tags anywhere in the main description or in the comments for block tags\&. Inline tags are enclosed within braces: \fI{@tag}\fR\&. +.PP +For custom tags, see -tag tagname:Xaoptcmf:"taghead"\&. See also Where Tags Can Be Used\&. +.SS TAG\ DESCRIPTIONS +.TP +@author \fIname-text\fR +Introduced in JDK 1\&.0 + +Adds an Author entry with the specified name text to the generated documents when the \f3-author\fR option is used\&. A documentation comment can contain multiple \f3@author\fR tags\&. You can specify one name per \f3@author\fR tag or multiple names per tag\&. In the former case, the \f3javadoc\fR command inserts a comma (,) and space between names\&. In the latter case, the entire text is copied to the generated document without being parsed\&. Therefore, you can use multiple names per line if you want a localized name separator other than a comma\&. See @author in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@author +.TP +{@code \fItext\fR} +Introduced in JDK 1\&.5 + +Equivalent to \f3<code>{@literal}</code>\fR\&. + +Displays text in code font without interpreting the text as HTML markup or nested Javadoc tags\&. This enables you to use regular angle brackets (< and >) instead of the HTML entities (\f3<\fR and \f3>\fR) in documentation comments, such as in parameter types (\f3<Object>\fR), inequalities (\f33 < 4\fR), or arrows (\f3<-\fR)\&. For example, the documentation comment text \f3{@code A<B>C}\fR displayed in the generated HTML page unchanged as \f3A<B>C\fR\&. This means that the \f3<B>\fR is not interpreted as bold and is in code font\&. If you want the same functionality without the code font, then use the \f3{@literal}\fR tag\&. +.TP +@deprecated \fIdeprecated-text\fR +Introduced in JDK 1\&.0 + +Adds a comment indicating that this API should no longer be used (even though it may continue to work)\&. The \f3javadoc\fR command moves \f3deprecated-text\fRahead of the main description, placing it in italics and preceding it with a bold warning: Deprecated\&. This tag is valid in all documentation comments: overview, package, class, interface, constructor, method and field\&. + +The first sentence of deprecated text should tell the user when the API was deprecated and what to use as a replacement\&. The \f3javadoc\fR command copies the first sentence to the summary section and index\&. Subsequent sentences can also explain why it was deprecated\&. You should include an \f3{@link}\fR tag (for Javadoc 1\&.2 or later) that points to the replacement API\&. + +Use the \fI@deprecated annotation\fR tag to deprecate a program element\&. See How and When to Deprecate APIs at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation\&.html + +See also @deprecated in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@deprecated +.TP +{@docRoot} +Introduced in JDK 1\&.3 + +Represents the relative path to the generated document\&'s (destination) root directory from any generated page\&. This tag is useful when you want to include a file, such as a copyright page or company logo, that you want to reference from all generated pages\&. Linking to the copyright page from the bottom of each page is common\&. + +This \f3{@docRoot}\fR tag can be used both on the command line and in a documentation comment\&. This tag is valid in all documentation comments: overview, package, class, interface, constructor, method and field, and includes the text portion of any tag (such as the \f3@return\fR, \f3@param\fR and \f3@deprecated\fR tags)\&. +.RS +.TP 0.2i +\(bu +On the command line, where the header, footer, or bottom are defined: \f3javadoc -bottom \&'<a href="{@docRoot}/copyright\&.html">Copyright</a>\&'\fR\&. + +When you use the \f3{@docRoot}\fR tag this way in a make file, some \f3makefile\fR programs require a special way to escape for the brace \f3{}\fR characters\&. For example, the Inprise MAKE version 5\&.2 running on Windows requires double braces: \f3{{@docRoot}}\fR\&. It also requires double (rather than single) quotation marks to enclose arguments to options such as the \f3-bottom\fR option (with the quotation marks around the \f3href\fR argument omitted)\&. +.TP 0.2i +\(bu +In a documentation comment: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * See the <a href="{@docRoot}/copyright\&.html">Copyright</a>\&.\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp + + +This tag is needed because the generated documents are in hierarchical directories, as deep as the number of subpackages\&. The expression: \f3<a href="{@docRoot}/copyright\&.html">\fR resolves to \f3<a href="\&.\&./\&.\&./copyright\&.html">\fR for \f3java/lang/Object\&.java\fR and \f3<a href="\&.\&./\&.\&./\&.\&./copyright\&.html">\fR for \f3java/lang/ref/Reference\&.java\fR\&. +.RE + +.TP +@exception \fIclass-name description\fR +Introduced in JDK 1\&.0 + +Identical to the \f3@throws\fR tag\&. See @throws class-name description\&. +.TP +{@inheritDoc} +Introduced in JDK 1\&.4 + +Inherits (copies) documentation from the nearest inheritable class or implementable interface into the current documentation comment at this tag\&'s location\&. This enables you to write more general comments higher up the inheritance tree and to write around the copied text\&. + +This tag is valid only in these places in a documentation comment: +.RS +.TP 0.2i +\(bu +In the main description block of a method\&. In this case, the main description is copied from a class or interface up the hierarchy\&. +.TP 0.2i +\(bu +In the text arguments of the \f3@return\fR, \f3@param,\fR and \f3@throws\fR tags of a method\&. In this case, the tag text is copied from the corresponding tag up the hierarchy\&. +.RE + + +See Method Comment Inheritance for a description of how comments are found in the inheritance hierarchy\&. Note that if this tag is missing, then the comment is or is not automatically inherited according to rules described in that section\&. +.TP +{@link \fIpackage\&.class#member label\fR} +Introduced in JDK 1\&.2 + +Inserts an inline link with a visible text label that points to the documentation for the specified package, class, or member name of a referenced class\&. This tag is valid in all documentation comments: overview, package, class, interface, constructor, method and field, including the text portion of any tag, such as the \f3@return\fR, \f3@param\fR and \f3@deprecated\fR tags\&. See @link in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#{@link + +This tag is similar to the \f3@see\fR tag\&. Both tags require the same references and accept the same syntax for \f3package\&.class#member\fR and \f3label\fR\&. The main difference is that the \f3{@link}\fR tag generates an inline link rather than placing the link in the See Also section\&. The \f3{@link}\fR tag begins and ends with braces to separate it from the rest of the inline text\&. If you need to use the right brace (\f3}\fR) inside the label, then use the HTML entity notation \f3}\fR\&. + +There is no limit to the number of \f3{@link}\fR tags allowed in a sentence\&. You can use this tag in the main description part of any documentation comment or in the text portion of any tag, such as the \f3@deprecated\fR, \f3@return\fR or \f3@param\fR tags\&. + +For example, here is a comment that refers to the \f3getComponentAt(int, int)\fR method: +.sp +.nf +\f3Use the {@link #getComponentAt(int, int) getComponentAt} method\&.\fP +.fi +.nf +\f3\fP +.fi +.sp + + +From this code, the standard doclet generates the following HTML (assuming it refers to another class in the same package): +.sp +.nf +\f3Use the <a href="Component\&.html#getComponentAt(int, int)">getComponentAt</a> method\&.\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The previous line appears on the web page as: +.sp +.nf +\f3Use the getComponentAt method\&.\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +{@linkplain \fIpackage\&.class#member label\fR} +Introduced in JDK 1\&.4 + +Behaves the same as the \f3{@link}\fR tag, except the link label is displayed in plain text rather than code font\&. Useful when the label is plain text\&. For example, \f3Refer to {@linkplain add() the overridden method}\fR\&. displays as: Refer to the overridden method\&. +.TP +{@literal \fItext\fR} +Introduced in JDK 1\&.5 + +Displays text without interpreting the text as HTML markup or nested Javadoc tags\&. This enables you to use angle brackets (\f3< and >\fR) instead of the HTML entities (\f3<\fR and \f3>\fR) in documentation comments, such as in parameter types (\f3<Object>\fR), inequalities (\f33 < 4\fR), or arrows (<-)\&. For example, the documentation comment text \f3{@literal A<B>C}\fR displays unchanged in the generated HTML page in your browser, as \f3A<B>C\fR\&. The \f3<B>\fR is not interpreted as bold (and it is not in code font)\&. If you want the same functionality with the text in code font, then use the \f3{@code}\fR tag\&. +.TP +@param \fIparameter-name description\fR +Introduced in JDK 1\&.0 + +Adds a parameter with the specified \f3parameter-name\fR followed by the specified description to the Parameters section\&. When writing the documentation comment, you can continue the description onto multiple lines\&. This tag is valid only in a documentation comment for a method, constructor, or class\&. See @param in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@param + +The \f3parameter-name\fR can be the name of a parameter in a method or constructor, or the name of a type parameter of a class, method, or constructor\&. Use angle brackets around this parameter name to specify the use of a type parameter\&. + +Example of a type parameter of a class: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * @param <E> Type of element stored in a list\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3public interface List<E> extends Collection<E> {\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Example of a type parameter of a method: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * @param string the string to be converted\fP +.fi +.nf +\f3 * @param type the type to convert the string to\fP +.fi +.nf +\f3 * @param <T> the type of the element\fP +.fi +.nf +\f3 * @param <V> the value of the element\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3<T, V extends T> V convert(String string, Class<T> type) {\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +@return \fIdescription\fR +Introduced in JDK 1\&.0 + +Adds a Returns section with the description text\&. This text should describe the return type and permissible range of values\&. This tag is valid only in a documentation comment for a method\&. See @return in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@return +.TP +@see \fIreference\fR +Introduced in JDK 1\&.0 + +Adds a \fISee Also\fR heading with a link or text entry that points to a reference\&. A documentation comment can contain any number of \f3@see\fR tags, which are all grouped under the same heading\&. The \f3@see\fR tag has three variations\&. The form is the most common\&. This tag is valid in any documentation comment: overview, package, class, interface, constructor, method, or field\&. For inserting an inline link within a sentence to a package, class, or member, see \f3{@link}\fR\&. + +\fIForm 1\fR\&. The @see \f3string\fR tag form adds a text entry for \fIstring\fR\&. No link is generated\&. The string is a book or other reference to information not available by URL\&. The \f3javadoc\fR command distinguishes this from the previous cases by searching for a double quotation mark (") as the first character\&. For example, \f3@see "The Java Programming Language"\fR that generates the following text: + +\fISee Also\fR: + +"The Java Programming Language" + +\fIForm 2\fR\&. The \f3@see <a href="URL#value">label</a>\fR form adds a link as defined by \f3URL#value\fR\&. The \f3URL#value\fR parameter is a relative or absolute URL\&. The \f3javadoc\fR command distinguishes this from other cases by searching for a less-than symbol (\f3<\fR) as the first character\&. For example, \f3@see <a href="spec\&.html#section">Java Spec</a>\fR generates the following link: + +\fISee Also\fR: + +Java Spec + +\fIForm 3\fR\&. The \f3@see package\&.class#member label\fR form adds a link with a visible text label that points to the documentation for the specified name in the Java Language that is referenced\&. The label is optional\&. If the label is omitted, then the name appears instead as visible text, suitably shortened\&. Use the \f3-noqualifier\fR option to globally remove the package name from this visible text\&. Use the label when you want the visible text to be different from the autogenerated visible text\&. See How a Name Appears\&. + +In Java SE 1\&.2 only, the name but not the label automatically appears in \f3<code>\fR HTML tags\&. Starting with Java SE 1\&.2\&.2, the \f3<code>\fR tag is always included around the visible text, whether or not a label is used\&. +.RS +.TP 0.2i +\(bu +\f3package\&.class#member\fR is any valid program element name that is referenced, such as a package, class, interface, constructor, method or field name, except that the character ahead of the member name should be a number sign (\f3#\fR)\&. The class represents any top-level or nested class or interface\&. The member represents any constructor, method, or field (not a nested class or interface)\&. If this name is in the documented classes, then the \f3javadoc\fR command create a link to it\&. To create links to external referenced classes, use the \f3-link\fR option\&. Use either of the other two \f3@see\fR tag forms to refer to the documentation of a name that does not belong to a referenced class\&. See Specify a Name\&. + +\fINote:\fR External referenced classes are classes that are not passed into the \f3javadoc\fR command on the command line\&. Links in the generated documentation to external referenced classes are called external references or external links\&. For example, if you run the \f3javadoc\fR command on only the \f3java\&.awt package\fR, then any class in \f3java\&.lang\fR, such as \f3Object\fR, is an external referenced class\&. Use the \f3-link\fR and \f3-linkoffline\fR options to link to external referenced classes\&. The source comments of external referenced classes are not available to the \f3javadoc\fR command run\&. +.TP 0.2i +\(bu +\f3label\fR is optional text that is visible as the link label\&. The label can contain white space\&. If \f3label\fR is omitted, then \f3package\&.class\&.member\fR appears, suitably shortened relative to the current class and package\&. See How a Name Appears\&. +.TP 0.2i +\(bu +A space is the delimiter between \f3package\&.class#member\fR and \f3label\fR\&. A space inside parentheses does not indicate the start of a label, so spaces can be used between parameters in a method\&. +.RE + + +\fI\fRIn the following example, an \f3@see\fR tag (in the \f3Character\fR class) refers to the equals method in the \f3String\fR class\&. The tag includes both arguments: the name \f3String#equals(Object)\fR and the label \f3equals\fR\&. +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * @see String#equals(Object) equals\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The standard doclet produces HTML that is similar to: +.sp +.nf +\f3<dl>\fP +.fi +.nf +\f3<dt><b>See Also:</b>\fP +.fi +.nf +\f3<dd><a href="\&.\&./\&.\&./java/lang/String#equals(java\&.lang\&.Object)"><code>equals<code></a>\fP +.fi +.nf +\f3</dl>\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The previous code looks similar to the following in a browser, where the label is the visible link text: + +\fISee Also\fR: + +equals +.PP +Specify a Name + +\fI\fRThis \f3package\&.class#member\fR name can be either fully qualified, such as \f3java\&.lang\&.String#toUpperCase()\fR or not, such as \f3String#toUpperCase()\fR or \f3#toUpperCase()\fR\&. If the name is less than fully qualified, then the \f3javadoc\fR command uses the standard Java compiler search order to find it\&. See Search Order for the @see Tag\&. The name can contain white space within parentheses, such as between method arguments\&.The advantage to providing shorter, partially qualified names is that they are shorter to type and there is less clutter in the source code\&. The following listing shows the different forms of the name, where \f3Class\fR can be a class or interface; Type can be a class, interface, array, or primitive; and method can be a method or constructor\&. +.sp +.nf +\f3\fITypical forms for\fR\fI @see package\&.class#member\fR\fP +.fi +.nf +\f3\fIReferencing a member of the current class\fR\fP +.fi +.nf +\f3@see #field\fP +.fi +.nf +\f3@see #method(Type, Type,\&.\&.\&.)\fP +.fi +.nf +\f3@see #method(Type argname, Type argname,\&.\&.\&.)\fP +.fi +.nf +\f3@see #constructor(Type, Type,\&.\&.\&.)\fP +.fi +.nf +\f3@see #constructor(Type argname, Type argname,\&.\&.\&.) \fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\fIReferencing another class in the current or imported packages\fR\fP +.fi +.nf +\f3@see Class#field\fP +.fi +.nf +\f3@see Class#method(Type, Type,\&.\&.\&.)\fP +.fi +.nf +\f3@see Class#method(Type argname, Type argname,\&.\&.\&.)\fP +.fi +.nf +\f3@see Class#constructor(Type, Type,\&.\&.\&.)\fP +.fi +.nf +\f3@see Class#constructor(Type argname, Type argname,\&.\&.\&.)\fP +.fi +.nf +\f3@see Class\&.NestedClass\fP +.fi +.nf +\f3@see Class \fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\fIReferencing an element in another package (fully qualified)\fR\fP +.fi +.nf +\f3@see package\&.Class#field\fP +.fi +.nf +\f3@see package\&.Class#method(Type, Type,\&.\&.\&.)\fP +.fi +.nf +\f3@see package\&.Class#method(Type argname, Type argname,\&.\&.\&.)\fP +.fi +.nf +\f3@see package\&.Class#constructor(Type, Type,\&.\&.\&.)\fP +.fi +.nf +\f3@see package\&.Class#constructor(Type argname, Type argname,\&.\&.\&.)\fP +.fi +.nf +\f3@see package\&.Class\&.NestedClass\fP +.fi +.nf +\f3@see package\&.Class\fP +.fi +.nf +\f3@see package\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3\fRNotes about the previous listing: +.TP 0.2i +\(bu +The first set of forms with no class or package causes the \f3javadoc\fR command to search only through the current class hierarchy\&. It finds a member of the current class or interface, one of its superclasses or superinterfaces, or one of its enclosing classes or interfaces (search Items 1\(en3)\&. It does not search the rest of the current package or other packages (search Items 4\(en5)\&. See Search Order for the @see Tag\&. +.TP 0.2i +\(bu +If any method or constructor is entered as a name with no parentheses, such as \f3getValue\fR, and if there is no field with the same name, then the \f3javadoc\fR command still creates a link to the method\&. If this method is overloaded, then the \f3javadoc\fR command links to the first method its search encounters, which is unspecified\&. +.TP 0.2i +\(bu +Nested classes must be specified as \f3outer\&.inner\fR, not simply \f3inner\fR, for all forms\&. +.TP 0.2i +\(bu +As stated, the number sign (\f3#\fR), rather than a dot (\f3\&.\fR) separates a member from its class\&. This enables the \f3javadoc\fR command to resolve ambiguities, because the dot also separates classes, nested classes, packages, and subpackages\&. However, the \f3javadoc\fR command properly parses a dot when there is no ambiguity, but prints a warning to alert you\&. +.PP +Search Order for the @see Tag + +\fI\fRThe \f3javadoc\fR command processes an \f3@see\fR tag that appears in a source file, package file, or overview file\&. In the latter two files, you must fully qualify the name you supply with the \f3@see\fR tag\&. In a source file, you can specify a name that is fully qualified or partially qualified\&. +.PP +The following is the search order for the \f3@see\fR tag\&. +.TP 0.4i +1\&. +The current class or interface\&. +.TP 0.4i +2\&. +Any enclosing classes and interfaces searching the closest first\&. +.TP 0.4i +3\&. +Any superclasses and superinterfaces, searching the closest first\&. +.TP 0.4i +4\&. +The current package\&. +.TP 0.4i +5\&. +Any imported packages, classes, and interfaces, searching in the order of the \f3import\fR statement\&. +.PP +The \f3javadoc\fR command continues to search recursively through Items 1-3 for each class it encounters until it finds a match\&. That is, after it searches through the current class and its enclosing class E, it searches through the superclasses of E before the enclosing classes of E\&. In Items 4 and 5, the \f3javadoc\fR command does not search classes or interfaces within a package in any specified order (that order depends on the particular compiler)\&. In Item 5, the \f3javadoc\fR command searches in \fIjava\&.lang\fR because that is imported by all programs\&. +.PP +When the \f3javadoc\fR command encounters an \f3@see\fR tag in a source file that is not fully qualified, it searches for the specified name in the same order as the Java compiler would, except the \f3javadoc\fR command does not detect certain name space ambiguities because it assumes the source code is free of these errors\&. This search order is formally defined in the Java Language Specification\&. The \f3javadoc\fR command searches for that name through all related and imported classes and packages\&. In particular, it searches in this order: +.TP 0.4i +1\&. +The current class or interface\&. +.TP 0.4i +2\&. +Any enclosing classes and interfaces, searching the closest first\&. +.TP 0.4i +3\&. +Any superclasses and superinterfaces, searching the closest first\&. +.TP 0.4i +4\&. +The current package\&. +.TP 0.4i +5\&. +Any imported packages, classes, and interfaces, searching in the order of the \f3import\fR statements\&. +.PP +The \f3javadoc\fR command does not necessarily look in subclasses, nor will it look in other packages even when their documentation is being generated in the same run\&. For example, if the \f3@see\fR tag is in the \f3java\&.awt\&.event\&.KeyEvent\fR class and refers to a name in the \f3java\&.awt package\fR, then the \f3javadoc\fR command does not look in that package unless that class imports it\&. +.PP +How a Name Appears + +\fI\fRIf \f3label\fR is omitted, then \f3package\&.class\&.member\fR appears\&. In general, it is suitably shortened relative to the current class and package\&. Shortened means the \f3javadoc\fR command displays only the minimum name necessary\&. For example, if the \f3String\&.toUpperCase()\fR method contains references to a member of the same class and to a member of a different class, then the class name is displayed only in the latter case, as shown in the following listing\&. Use the \f3-noqualifier\fR option to globally remove the package names\&. +.PP +\fIType of reference\fR: The \f3@see\fR tag refers to a member of the same class, same package +.br +\fIExample in\fR: \f3@see String#toLowerCase()\fR +.br +\fIAppears as\fR: \f3toLowerCase()\fR - omits the package and class names +.br + +.PP +\fIType of reference\fR: The \f3@see\fR tag refers to a member of a different class, same package +.br +\fIExample in\fR: \f3@see Character#toLowerCase(char)\fR +.br +\fIAppears as\fR: \f3Character\&.toLowerCase(char)\fR - omits the package name, includes the class name +.br + +.PP +\fIType of reference\fR: The \f3@see\fR tag refers to a member of a different class, different package +.br +\fIExample in\fR: \f3@see java\&.io\&.File#exists()\fR +.br +\fIAppears as\fR: \f3java\&.io\&.File\&.exists()\fR - includes the package and class names +.br + +.PP +Examples of the @see Tag + +The comment to the right shows how the name appears when the \f3@see\fR tag is in a class in another package, such as \f3java\&.applet\&.Applet\fR\&. See @see in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@see +.sp +.nf +\f3 See also:\fP +.fi +.nf +\f3@see java\&.lang\&.String // String \fP +.fi +.nf +\f3@see java\&.lang\&.String The String class // The String class \fP +.fi +.nf +\f3@see String // String \fP +.fi +.nf +\f3@see String#equals(Object) // String\&.equals(Object) \fP +.fi +.nf +\f3@see String#equals // String\&.equals(java\&.lang\&.Object) \fP +.fi +.nf +\f3@see java\&.lang\&.Object#wait(long) // java\&.lang\&.Object\&.wait(long) \fP +.fi +.nf +\f3@see Character#MAX_RADIX // Character\&.MAX_RADIX \fP +.fi +.nf +\f3@see <a href="spec\&.html">Java Spec</a> // Java Spec \fP +.fi +.nf +\f3@see "The Java Programming Language" // "The Java Programming Language" \fP +.fi +.nf +\f3\fP +.fi +.sp +\fINote:\fR You can extend the \f3@se\fR\f3e\fR tag to link to classes not being documented with the \f3-link\fR option\&. +.TP +@serial \fIfield-description\fR | include | exclude +Introduced in JDK 1\&.2 + +Used in the documentation comment for a default serializable field\&. See Documenting Serializable Fields and Data for a Class at http://docs\&.oracle\&.com/javase/8/docs/platform/serialization/spec/serial-arch\&.html#5251 + +See also Oracle\(cqs Criteria for Including Classes in the Serialized Form Specification at http://www\&.oracle\&.com/technetwork/java/javase/documentation/serialized-criteria-137781\&.html + +An optional \f3field-description\fR should explain the meaning of the field and list the acceptable values\&. When needed, the description can span multiple lines\&. The standard doclet adds this information to the serialized form page\&. See Cross-Reference Pages\&. + +If a serializable field was added to a class after the class was made serializable, then a statement should be added to its main description to identify at which version it was added\&. + +The \f3include\fR and \f3exclude\fR arguments identify whether a class or package should be included or excluded from the serialized form page\&. They work as follows: +.RS +.TP 0.2i +\(bu +A public or protected class that implements \f3Serializable\fR is included unless that class (or its package) is marked with the \f3@serial exclude\fR tag\&. +.TP 0.2i +\(bu +A private or package-private class that implements \f3Serializable\fR is excluded unless that class (or its package) is marked with the \f3@serial include\fR tag\&. +.RE + + +For example, the \f3javax\&.swing\fR package is marked with the \f3@serial\fR\f3exclude\fR tag in package\&.html or package-info\&.java\&. The public class \f3java\&.security\&.BasicPermission\fR is marked with the \f3@serial exclude\fR tag\&. The package-private class \f3java\&.util\&.PropertyPermissionCollection\fR is marked with the \f3@serial include\fR tag\&. + +The \f3@serial\fR tag at the class level overrides the \f3@serial\fR tag at the package level\&. +.TP +@serialData \fIdata-description\fR +Introduced in JDK 1\&.2 + +Uses the data description value to document the types and order of data in the serialized form\&. This data includes the optional data written by the \f3writeObject\fR method and all data (including base classes) written by the \f3Externalizable\&.writeExternal\fR method\&. + +The \f3@serialData\fR tag can be used in the documentation comment for the \f3writeObject\fR, \f3readObject\fR, \f3writeExternal\fR, \f3readExternal\fR, \f3writeReplace\fR, and \f3readResolve\fR methods\&. +.TP +@serialField \fIfield-name\fR\fIfield-type\fR\fIfield-description\fR +Introduced in JDK 1\&.2 + +Documents an \f3ObjectStreamField\fR component of the \f3serialPersistentFields\fR member of a \f3Serializable\fR class\&. Use one \f3@serialField\fR tag for each \f3ObjectStreamField\fR component\&. +.TP +@since \fIsince-text\fR +Introduced in JDK 1\&.1 + +Adds a \fISince\fR heading with the specified \f3since-text\fR value to the generated documentation\&. The text has no special internal structure\&. This tag is valid in any documentation comment: overview, package, class, interface, constructor, method, or field\&. This tag means that this change or feature has existed since the software release specified by the \f3since-text\fR value, for example: \f3@since 1\&.5\fR\&. + +For Java platform source code, the \f3@since\fR tag indicates the version of the Java platform API specification, which is not necessarily when the source code was added to the reference implementation\&. Multiple \f3@since\fR tags are allowed and are treated like multiple \f3@author\fR tags\&. You could use multiple tags when the program element is used by more than one API\&. +.TP +@throws \fIclass-name\fR\fIdescription\fR +Introduced in JDK 1\&.2 + +Behaves the same as the \f3@exception\fR tag\&. See @throws in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@exception + +The \f3@throws\fR tag adds a \fIThrows\fR subheading to the generated documentation, with the \f3class-name\fR and \f3description\fR text\&. The \fIclass-name\fR is the name of the exception that might be thrown by the method\&. This tag is valid only in the documentation comment for a method or constructor\&. If this class is not fully specified, then the \f3javadoc\fR command uses the search order to look up this class\&. Multiple \f3@throws\fR tags can be used in a specified documentation comment for the same or different exceptions\&. See Search Order for the @see Tag\&. + +To ensure that all checked exceptions are documented, when an \f3@throws\fR tag does not exist for an exception in the throws clause, the \f3javadoc\fR command adds that exception to the HTML output (with no description) as though it were documented with the \f3@throws\fR tag\&. + +The \f3@throws\fR documentation is copied from an overridden method to a subclass only when the exception is explicitly declared in the overridden method\&. The same is true for copying from an interface method to an implementing method\&. You can use the \f3{@inheritDoc}\fR tag to force the \f3@throws\fR tag to inherit documentation\&. +.TP +{@value \fIpackage\&.class#field\fR} +Introduced in JDK 1\&.4 + +Displays constant values\&. When the \f3{@value}\fR tag is used without an argument in the documentation comment of a static field, it displays the value of that constant: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * The value of this constant is {@value}\&.\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3public static final String SCRIPT_START = "<script>"\fP +.fi +.nf +\f3\fP +.fi +.sp + + +When used with the argument \f3package\&.class#field\fR in any documentation comment, he \f3{@value}\fR tag displays the value of the specified constant: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * Evaluates the script starting with {@value #SCRIPT_START}\&.\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3public String evalScript(String script) {}\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The argument \f3package\&.class#field\fR takes a form similar to that of the \f3@see\fR tag argument, except that the member must be a static field\&. + +The values of these constants are also displayed in Constant Field Values at http://docs\&.oracle\&.com/javase/8/docs/api/constant-values\&.html +.TP +@version \fIversion-text\fR +Introduced in JDK 1\&.0 + +Adds a \fIVersion\fR subheading with the specified \f3version-text\fR value to the generated documents when the \f3-version\fR option is used\&. This tag is intended to hold the current release number of the software that this code is part of, as opposed to the\f3@since\fR tag, which holds the release number where this code was introduced\&. The \f3version-text\fR value has no special internal structure\&. See @version in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#@version + +A documentation comment can contain multiple \f3@version\fR tags\&. When it makes sense, you can specify one release number per \f3@version\fR tag or multiple release numbers per tag\&. In the former case, the \f3javadoc\fR command inserts a comma (,) and a space between the names\&. In the latter case, the entire text is copied to the generated document without being parsed\&. Therefore, you can use multiple names per line when you want a localized name separator other than a comma\&. +.SH WHERE\ TAGS\ CAN\ BE\ USED +The following sections describe where tags can be used\&. Note that the following tags can be used in all documentation comments: \f3@see\fR, \f3@since\fR, \f3@deprecated\fR, \f3{@link}\fR, \f3{@linkplain}\fR, and \f3{@docroot}\fR\&. +.SS OVERVIEW\ TAGS +Overview tags are tags that can appear in the documentation comment for the overview page (which resides in the source file typically named overview\&.html)\&. Similar to any other documentation comments, these tags must appear after the main description +.PP +\fINote:\fR The \f3{@link}\fR tag has a bug in overview documents in Java SE 1\&.2\&. The text appears correctly but has no link\&. The \f3{@docRoot}\fR tag does not currently work in overview documents\&. +.PP +The overview tags are the following: +.PP +@see reference || @since since-text || @serialField field-name field-type field-description || @author name-text || @version version-text || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.SS PACKAGE\ TAGS +Package tags are tags that can appear in the documentation comment for a package, that resides in the source file named package\&.html or package-info\&.java\&. The \f3@serial\fR tag can only be used here with the \f3include\fR or \f3exclude\fR argument\&. +.PP +The package tags are the following: +.PP +@see reference || @since since-text || @serial field-description | include | exclude || @author name-text || @version version-text || {@linkplain package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.SS CLASS\ AND\ INTERFACE\ TAGS +The following are tags that can appear in the documentation comment for a class or interface\&. The \f3@serial\fR tag can only be used within the documentation for a class or interface with an \f3include\fR or \f3exclude\fR argument\&. +.PP +@see reference || @since since-text || @deprecated deprecated-text || @serial field-description | include | exclude || @author name-text || @version version-text || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || +.PP +Class comment example: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * A class representing a window on the screen\&.\fP +.fi +.nf +\f3 * For example:\fP +.fi +.nf +\f3 * <pre>\fP +.fi +.nf +\f3 * Window win = new Window(parent);\fP +.fi +.nf +\f3 * win\&.show();\fP +.fi +.nf +\f3 * </pre>\fP +.fi +.nf +\f3 *\fP +.fi +.nf +\f3 * @author Sami Shaio\fP +.fi +.nf +\f3 * @version 1\&.13, 06/08/06\fP +.fi +.nf +\f3 * @see java\&.awt\&.BaseWindow\fP +.fi +.nf +\f3 * @see java\&.awt\&.Button\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3class Window extends BaseWindow {\fP +.fi +.nf +\f3 \&.\&.\&.\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS FIELD\ TAGS +These tags can appear in fields: +.PP +@see reference || @since since-text || @deprecated deprecated-text || @serial field-description | include | exclude || @serialField field-name field-type field-description || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@docRoot} || {@value package\&.class#field} +.PP +Field comment example: +.sp +.nf +\f3 /**\fP +.fi +.nf +\f3 * The X\-coordinate of the component\&.\fP +.fi +.nf +\f3 *\fP +.fi +.nf +\f3 * @see #getLocation()\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3 int x = 1263732;\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS CONSTRUCTOR\ AND\ METHOD\ TAGS +The following tags can appear in the documentation comment for a constructor or a method, except for the \f3@return\fR tag, which cannot appear in a constructor, and the \f3{@inheritDoc}\fR tag, which has restrictions\&. +.PP +@see reference || @since since-text || @deprecated deprecated-text || @param parameter-name description || @return description || @throws class-name description || @exception class-name description || @serialData data-description || {@link package\&.class#member label} || {@linkplain package\&.class#member label} || {@inheritDoc} || {@docRoot} +.PP +\fINote:\fR The \f3@serialData\fR tag can only be used in the documentation comment for the \f3writeObject\fR, \f3readObject\fR, \f3writeExternal\fR, \f3readExternal\fR, \f3writeReplace\fR, and \f3readResolve\fR methods\&. +.PP +Method comment example: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * Returns the character at the specified index\&. An index \fP +.fi +.nf +\f3 * ranges from <code>0</code> to <code>length() \- 1</code>\fP +.fi +.nf +\f3 *\fP +.fi +.nf +\f3 * @param index the index of the desired character\&.\fP +.fi +.nf +\f3 * @return the desired character\&.\fP +.fi +.nf +\f3 * @exception StringIndexOutOfRangeException \fP +.fi +.nf +\f3 * if the index is not in the range <code>0</code> \fP +.fi +.nf +\f3 * to <code>length()\-1</code>\fP +.fi +.nf +\f3 * @see java\&.lang\&.Character#charValue()\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3 public char charAt(int index) {\fP +.fi +.nf +\f3 \&.\&.\&.\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +The \f3javadoc\fR command uses doclets to determine its output\&. The \f3javadoc\fR command uses the default standard doclet unless a custom doclet is specified with the \f3-doclet\fR option\&. The \f3javadoc\fR command provides a set of command-line options that can be used with any doclet\&. These options are described in Javadoc Options\&. The standard doclet provides an additional set of command-line options that are described in Standard Doclet Options\&. All option names are not case-sensitive, but their arguments are case-sensitive\&. +.TP 0.2i +\(bu +See also Javadoc Options +.TP 0.2i +\(bu +See also Standard Doclet Options +.PP +The options are: +.PP +-1\&.1 || -author || -bootclasspath classpathlist || -bottom text || -breakiterator || -charset name || -classpath classpathlist || -d directory || -docencoding name || -docfilesubdirs || -doclet class || -docletpath classpathlist || -doctitle title || -encoding || -exclude packagename1:packagename2:\&.\&.\&. || -excludedocfilessubdir name1:name2 || -extdirs dirist || -footer footer || -group groupheading packagepattern:packagepattern || -header header || -help || -helpfile path\efilename || -Jflag || -javafx ||-keywords || -link extdocURL || -linkoffline extdocURL packagelistLoc || -linksource || -locale language_country_variant || -nocomment || -nodeprecated || -nodeprecatedlist || -nohelp || -noindex || -nonavbar || -noqualifier all | packagename1:packagename2\&.\&.\&. || -nosince || -notimestamp || -notree || -overview path/filename || -package || -private || -protected || -public || -quiet || -serialwarn || -source release || -sourcepath sourcepathlist || -sourcetab tablength || -splitindex || -stylesheet path/filename || -subpackages package1:package2:\&.\&.\&. || -tag tagname:Xaoptcmf:"taghead" || -taglet class || -tagletpath tagletpathlist || -title title || -top || -use || -verbose || -version || -windowtitle title +.PP +The following options are the core Javadoc options that are available to all doclets\&. The standard doclet provides the rest of the doclets: \f3-bootclasspath\fR, \f3-breakiterator\fR, \f3-classpath\fR, \f3-doclet\fR, \f3-docletpath\fR, \f3-encoding\fR, -\f3exclude\fR, \f3-extdirs\fR, \f3-help\fR, \f3-locale\fR, \f3-\fR\f3overview\fR, \f3-package\fR, \f3-private\fR, \f3-protected\fR, \f3-public\fR, \f3-quiet\fR, \f3-source\fR, \f3-sourcepath\fR, \f3-subpackages\fR, and \f3-verbose\fR\&. +.SS JAVADOC\ OPTIONS +.TP +-overview \fIpath/filename\fR +.br +Specifies that the \f3javadoc\fR command should retrieve the text for the overview documentation from the source file specified by the \fIpath/filename\fRand place it on the Overview page (overview-summary\&.html)\&. The \fIpath/filename\fRis relative to the current directory\&. + +While you can use any name you want for the \f3filename\fR value and place it anywhere you want for the path, it is typical to name it overview\&.html and place it in the source tree at the directory that contains the topmost package directories\&. In this location, no path is needed when documenting packages, because the \f3-sourcepath\fR option points to this file\&. + +For example, if the source tree for the \f3java\&.lang\fR package is /src/classes/java/lang/, then you could place the overview file at /src/classes/overview\&.html + +See Real-World Examples\&. + +For information about the file specified by \fIpath/filename,\fRsee Overview Comment Files\&. + +The overview page is created only when you pass two or more package names to the \f3javadoc\fR command\&. For a further explanation, see HTML Frames\&. The title on the overview page is set by \f3-doctitle\fR\&. +.TP +-Xdoclint:(all|none|[-]\fI<group>\fR) +.br +Reports warnings for bad references, lack of accessibility and missing Javadoc comments, and reports errors for invalid Javadoc syntax and missing HTML tags\&. + +This option enables the \f3javadoc\fR command to check for all documentation comments included in the generated output\&. As always, you can select which items to include in the generated output with the standard options \f3-public\fR, \f3-protected\fR, \f3-package\fR and \f3-private\fR\&. + +When the \f3-Xdoclint\fR is enabled, it reports issues with messages similar to the \f3javac\fR command\&. The \f3javadoc\fR command prints a message, a copy of the source line, and a caret pointing at the exact position where the error was detected\&. Messages may be either warnings or errors, depending on their severity and the likelihood to cause an error if the generated documentation were run through a validator\&. For example, bad references or missing Javadoc comments do not cause the \f3javadoc\fR command to generate invalid HTML, so these issues are reported as warnings\&. Syntax errors or missing HTML end tags cause the \f3javadoc\fR command to generate invalid output, so these issues are reported as errors\&. + +By default, the \f3-Xdoclint\fR option is enabled\&. Disable it with the option \f3-Xdoclint:none\fR\&. + +Change what the \f3-Xdoclint\fR option reports with the following options: +.RS +.TP 0.2i +\(bu +\f3-Xdoclint none\fR : disable the \f3-Xdoclint\fR option +.TP 0.2i +\(bu +\f3-Xdoclint\fR\fIgroup\fR : enable \fIgroup\fR checks +.TP 0.2i +\(bu +\f3-Xdoclint all\fR : enable all groups of checks +.TP 0.2i +\(bu +\f3-Xdoclint all,\fR\fI-group\fR : enable all except \fIgroup\fR checks +.RE + + +The variable \fIgroup\fR has one of the following values: +.RS +.TP 0.2i +\(bu +\f3accessibility\fR : Checks for the issues to be detected by an accessibility checker (for example, no caption or summary attributes specified in a \f3<table>\fR tag)\&. +.TP 0.2i +\(bu +\f3html\fR : Detects high-level HTML issues, like putting block elements inside inline elements, or not closing elements that require an end tag\&. The rules are derived from theHTML 4\&.01 Specification\&. This type of check enables the \f3javadoc\fR command to detect HTML issues that many browsers might accept\&. +.TP 0.2i +\(bu +\f3missing\fR : Checks for missing Javadoc comments or tags (for example, a missing comment or class, or a missing \f3@return\fR tag or similar tag on a method)\&. +.TP 0.2i +\(bu +\f3reference\fR : Checks for issues relating to the references to Java API elements from Javadoc tags (for example, item not found in \f3@see\fR , or a bad name after \f3@param)\fR\&. +.TP 0.2i +\(bu +\f3syntax\fR : Checks for low level issues like unescaped angle brackets (\f3<\fR and \f3>\fR) and ampersands (\f3&\fR) and invalid Javadoc tags\&. +.RE + + +You can specify the \f3-Xdoclint\fR option multiple times to enable the option to check errors and warnings in multiple categories\&. Alternatively, you can specify multiple error and warning categories by using the preceding options\&. For example, use either of the following commands to check for the HTML, syntax, and accessibility issues in the file \fIfilename\fR\&. +.sp +.nf +\f3javadoc \-Xdoclint:html \-Xdoclint:syntax \-Xdoclint:accessibility \fIfilename\fR\fP +.fi +.nf +\f3javadoc \-Xdoclint:html,syntax,accessibility \fIfilename\fR\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\fINote:\fR The \f3javadoc\fR command does not guarantee the completeness of these checks\&. In particular, it is not a full HTML compliance checker\&. The goal of the -\f3Xdoclint\fR option is to enable the \f3javadoc\fR command to report majority of common errors\&. + +The \f3javadoc\fR command does not attempt to fix invalid input, it just reports it\&. +.TP +-public +.br +Shows only public classes and members\&. +.TP +-protected +.br +Shows only protected and public classes and members\&. This is the default\&. +.TP +-package +.br +Shows only package, protected, and public classes and members\&. +.TP +-private +.br +Shows all classes and members\&. +.TP +-help +.br +Displays the online help, which lists all of the \f3javadoc\fR and \f3doclet\fR command-line options\&. +.TP +-doclet \fIclass\fR +.br +Specifies the class file that starts the doclet used in generating the documentation\&. Use the fully qualified name\&. This doclet defines the content and formats the output\&. If the \f3-doclet\fR option is not used, then the \f3javadoc\fR command uses the standard doclet for generating the default HTML format\&. This class must contain the \f3start(Root)\fR method\&. The path to this starting class is defined by the \f3-docletpath\fR option\&. See Doclet Overview at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html +.TP +-docletpath \fIclasspathlist\fR +.br +Specifies the path to the doclet starting class file (specified with the \f3-doclet\fR option) and any JAR files it depends on\&. If the starting class file is in a JAR file, then this option specifies the path to that JAR file\&. You can specify an absolute path or a path relative to the current directory\&. If \f3classpathlist\fR contains multiple paths or JAR files, then they should be separated with a colon (:) on Oracle Solaris and a semi-colon (;) on Windows\&. This option is not necessary when the doclet starting class is already in the search path\&. See Doclet Overview at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html +.TP +-1\&.1 +.br +Removed from Javadoc 1\&.4 with no replacement\&. This option created documentation with the appearance and functionality of documentation generated by Javadoc 1\&.1 (it never supported nested classes)\&. If you need this option, then use Javadoc 1\&.2 or 1\&.3 instead\&. +.TP +-source \fIrelease\fR +.br +Specifies the release of source code accepted\&. The following values for the \f3release\fR parameter are allowed\&. Use the value of \f3release\fR that corresponds to the value used when you compile code with the \f3javac\fR command\&. +.RS +.TP 0.2i +\(bu +\fIRelease Value: 1\&.5\fR\&. The \f3javadoc\fR command accepts code containing generics and other language features introduced in JDK 1\&.5\&. The compiler defaults to the 1\&.5 behavior when the \f3-source\fR option is not used\&. +.TP 0.2i +\(bu +\fIRelease Value: 1\&.4\fR\&. The \f3javadoc\fR command accepts code containing assertions, which were introduced in JDK 1\&.4\&. +.TP 0.2i +\(bu +\fIRelease Value: 1\&.3\fR\&. The \f3javadoc\fR command does not support assertions, generics, or other language features introduced after JDK 1\&.3\&. +.RE + +.TP +-sourcepath \fIsourcepathlist\fR +.br +Specifies the search paths for finding source files when passing package names or the \f3-subpackages\fR option into the \f3javadoc\fR command\&. Separate multiple paths with a colon (:)\&. The \f3javadoc\fR command searches all subdirectories of the specified paths\&. Note that this option is not only used to locate the source files being documented, but also to find source files that are not being documented, but whose comments are inherited by the source files being documented\&. + +You can use the \f3-sourcepath\fR option only when passing package names into the \f3javadoc\fR command\&. This will not locate source files passed into the \f3javadoc\fR command\&. To locate source files, \f3\fRchange to that directory or include the path ahead of each file, as shown at Document One or More Classes\&. If you omit \f3-sourcepath\fR, then the \f3javadoc\fR command uses the class path to find the source files (see \f3-classpath\fR)\&. The default \f3-sourcepath\fR is the value of class path\&. If \f3-classpath\fR is omitted and you pass package names into the \f3javadoc\fR command, then the \f3javadoc\fR command searches in the current directory and subdirectories for the source files\&. + +Set \f3sourcepathlist\fR to the root directory of the source tree for the package you are documenting\&. + +For example, suppose you want to document a package called \f3com\&.mypackage\fR, whose source files are located at:/home/user/src/com/mypackage/*\&.java\&. Specify the sourcepath to /home/user/src, the directory that contains com\emypackage, and then supply the package name, as follows: +.sp +.nf +\f3javadoc \-sourcepath /home/user/src/ com\&.mypackage\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Notice that if you concatenate the value of sourcepath and the package name together and change the dot to a slash (/), then you have the full path to the package: + +/home/user/src/com/mypackage + +To point to two source paths: +.sp +.nf +\f3javadoc \-sourcepath /home/user1/src:/home/user2/src com\&.mypackage\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-classpath \fIclasspathlist\fR +.br +Specifies the paths where the \f3javadoc\fR command searches for referenced classes These are the documented classes plus any classes referenced by those classes\&. Separate multiple paths with a colon (:)\&. The \f3javadoc\fR command searches all subdirectories of the specified paths\&. Follow the instructions in the class path documentation for specifying the \f3classpathlist\fR value\&. + +If you omit \f3-sourcepath\fR, then the \f3javadoc\fR command uses \f3-classpath\fR to find the source files and class files (for backward compatibility)\&. If you want to search for source and class files in separate paths, then use both \f3-sourcepath\fR and \f3-classpath\fR\&. + +For example, if you want to document \f3com\&.mypackage\fR, whose source files reside in the directory /home/user/src/com/mypackage, and if this package relies on a library in /home/user/lib, then you would use the following command: +.sp +.nf +\f3javadoc \-sourcepath /home/user/lib \-classpath /home/user/src com\&.mypackage\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Similar to other tools, if you do not specify \f3-classpath\fR, then the \f3javadoc\fR command uses the \f3CLASSPATH\fR environment variable when it is set\&. If both are not set, then the \f3javadoc\fR command searches for classes from the current directory\&. + +For an in-depth description of how the \f3javadoc\fR command uses \f3-classpath\fR to find user classes as it relates to extension classes and bootstrap classes, see How Classes Are Found at http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html + +A class path element that contains a base name of * is considered equivalent to specifying a list of all the files in the directory with the extension \f3\&.jar\fR or \f3\&.JAR\fR\&. + +For example, if directory \f3mydir\fR contains \f3a\&.jar\fR and \f3b\&.JA\fRR, then the class path element \f3foo/*\fR is expanded to a \f3A\&.jar:b\&.JAR\fR, except that the order of JAR files is unspecified\&. All JAR files in the specified directory including hidden files are included in the list\&. A class path entry that consists of * expands to a list of all the jar files in the current directory\&. The \f3CLASSPATH\fR environment variable is similarly expanded\&. Any class path wildcard expansion occurs before the Java Virtual Machine (JVM) starts\&. No Java program ever sees unexpanded wild cards except by querying the environment, for example, by calling System\&.getenv(\f3"CLASSPATH"\fR)\&. +.TP +-subpackages \fIpackage1:package2:\&.\&.\&.\fR +.br +Generates documentation from source files in the specified packages and recursively in their subpackages\&. This option is useful when adding new subpackages to the source code because they are automatically included\&. Each package argument is any top-level subpackage (such as \f3java\fR) or fully qualified package (such as \f3javax\&.swing\fR) that does not need to contain source files\&. Arguments are separated by colons on all operating systems\&. Wild cards are not allowed\&. Use \f3-sourcepath\fR to specify where to find the packages\&. This option does not process source files that are in the source tree but do not belong to the packages\&. See Process Source Files\&. + +For example, the following command generates documentation for packages named \f3java\fR and \f3javax\&.swing\fR and all of their subpackages\&. +.sp +.nf +\f3javadoc \-d docs \-sourcepath /home/user/src \-subpackages java:javax\&.swing \fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-exclude \fIpackagename1:packagename2:\&.\&.\&.\fR +.br +Unconditionally excludes the specified packages and their subpackages from the list formed by \f3-subpackages\fR\&. It excludes those packages even when they would otherwise be included by some earlier or later \f3-subpackages\fR option\&. + +The following example would include \f3java\&.io\fR, \f3java\&.util\fR, and \f3java\&.math\fR (among others), but would exclude packages rooted at \f3java\&.net\fR and \f3java\&.lang\fR\&. Notice that this example excludes \f3java\&.lang\&.ref\fR, which is a subpackage of \f3java\&.lang\fR\&. +.sp +.nf +\f3javadoc \-sourcepath /home/user/src \-subpackages java \-exclude \fP +.fi +.nf +\f3 java\&.net:java\&.lang\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-bootclasspath \fIclasspathlist\fR +.br +Specifies the paths where the boot classes reside\&. These are typically the Java platform classes\&. The \f3bootclasspath\fR is part of the search path the \f3javadoc\fR command uses to look up source and class files\&. For more information, see How Classes Are Found at http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html + +Separate directories in the \f3classpathlist\fR parameters with semicolons (;) for Windows and colons (:) for Oracle Solaris\&. +.TP +-extdirs \fIdirist\fR +.br +Specifies the directories where extension classes reside\&. These are any classes that use the Java Extension mechanism\&. The \f3extdirs\fR option is part of the search path the \f3javadoc\fR command uses to look up source and class files\&. See the \f3-classpath\fR option for more information\&. Separate directories in \f3dirlist\fR with semicolons (;) for Windows and colons (:) for Oracle Solaris\&. +.TP +-verbose +.br +Provides more detailed messages while the \f3javadoc\fR command runs\&. Without the \f3verbose\fR option, messages appear for loading the source files, generating the documentation (one message per source file), and sorting\&. The verbose option causes the printing of additional messages that specify the number of milliseconds to parse each Java source file\&. +.TP +-quiet +.br +Shuts off messages so that only the warnings and errors appear to make them easier to view\&. It also suppresses the \f3version\fR string\&. +.TP +-breakiterator +.br +Uses the internationalized sentence boundary of \f3java\&.text\&.BreakIterator\fR to determine the end of the first sentence in the main description of a package, class, or member for English\&. All other locales already use the \f3BreakIterator\fR class, rather than an English language, locale-specific algorithm\&. The first sentence is copied to the package, class, or member summary and to the alphabetic index\&. From JDK 1\&.2 and later, the \f3BreakIterator\fR class is used to determine the end of a sentence for all languages except for English\&. Therefore, the \f3-breakiterator\fR option has no effect except for English from 1\&.2 and later\&. English has its own default algorithm: +.RS +.TP 0.2i +\(bu +English default sentence-break algorithm\&. Stops at a period followed by a space or an HTML block tag, such as \f3<P>\fR\&. +.TP 0.2i +\(bu +Breakiterator sentence-break algorithm\&. Stops at a period, question mark, or exclamation point followed by a space when the next word starts with a capital letter\&. This is meant to handle most abbreviations (such as "The serial no\&. is valid", but will not handle "Mr\&. Smith")\&. The \f3-breakiterator\fR option does not stop at HTML tags or sentences that begin with numbers or symbols\&. The algorithm stops at the last period in \&.\&./filename, even when embedded in an HTML tag\&. +.RE + + +In Java SE 1\&.5 the \f3-breakiterator\fR option warning messages are removed, and the default sentence-break algorithm is unchanged\&. If you have not modified your source code to eliminate the \f3-breakiterator\fR option warnings in Java SE 1\&.4\&.x, then you do not have to do anything\&. The warnings go away starting with Java SE 1\&.5\&.0\&. +.TP +-locale \fIlanguage_country_variant\fR +.br +Specifies the locale that the \f3javadoc\fR command uses when it generates documentation\&. The argument is the name of the locale, as described in \f3j\fR\f3ava\&.util\&.Locale\fR documentation, such as \f3en_US\fR (English, United States) or \f3en_US_WIN\fR (Windows variant)\&. + +\fINote:\fR The \f3-locale\fR option must be placed ahead (to the left) of any options provided by the standard doclet or any other doclet\&. Otherwise, the navigation bars appear in English\&. This is the only command-line option that depends on order\&. See Standard Doclet Options\&. + +Specifying a locale causes the \f3javadoc\fR command to choose the resource files of that locale for messages such as strings in the navigation bar, headings for lists and tables, help file contents, comments in the stylesheet\&.css file, and so on\&. It also specifies the sorting order for lists sorted alphabetically, and the sentence separator to determine the end of the first sentence\&. The \f3-locale\fR option does not determine the locale of the documentation comment text specified in the source files of the documented classes\&. +.TP +-encoding +.br +Specifies the encoding name of the source files, such as \f3EUCJIS/SJIS\fR\&. If this option is not specified, then the platform default converter is used\&. See also the\f3-docencoding name\fR and \f3-charset name\fR options\&. +.TP +-J\fIflag\fR +.br +Passes \f3flag\fR directly to the Java Runtime Environment (JRE) that runs the \f3javadoc\fR command\&. For example, if you must ensure that the system sets aside 32 MB of memory in which to process the generated documentation, then you would call the \f3-Xmx\fR option as follows: \f3javadoc -J-Xmx32m -J-Xms32m com\&.mypackage\fR\&. Be aware that \f3-Xms\fR is optional because it only sets the size of initial memory, which is useful when you know the minimum amount of memory required\&. + +There is no space between the \f3J\fR and the \f3flag\fR\&. + +Use the \f3-version\fR option to find out what version of the \f3javadoc\fR command you are using\&. The version number of the standard doclet appears in its output stream\&. See Running the Javadoc Command\&. +.sp +.nf +\f3javadoc \-J\-version\fP +.fi +.nf +\f3java version "1\&.7\&.0_09"\fP +.fi +.nf +\f3Java(TM) SE Runtime Environment (build 1\&.7\&.0_09\-b05)\fP +.fi +.nf +\f3Java HotSpot(TM) 64\-Bit Server VM (build 23\&.5\-b02, mixed mode)\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-javafx +.br +Generates HTML documentation using the JavaFX extensions to the standard doclet\&. The generated documentation includes a Property Summary section in addition to the other summary sections generated by the standard Java doclet\&. The listed properties are linked to the sections for the getter and setter methods of each property\&. + +If there are no documentation comments written explicitly for getter and setter methods, the documentation comments from the property method are automatically copied to the generated documentation for these methods\&. This option also adds a new \f3@defaultValue\fR tag that allows documenting the default value for a property\&. + +Example: +.sp +.nf +\f3javadoc \-javafx MyClass\&.java \-d testdir\fP +.fi +.sp + +.SS STANDARD\ DOCLET\ OPTIONS +.TP +-d \fIdirectory\fR +.br +Specifies the destination directory where the \f3javadoc\fR command saves the generated HTML files\&. If you omit the \f3-d\fR option, then the files are saved to the current directory\&. The \f3directory\fR value can be absolute or relative to the current working directory\&. As of Java SE 1\&.4, the destination directory is automatically created when the \f3javadoc\fR command runs\&. + +For example, the following command generates the documentation for the package \f3com\&.mypackage\fR and saves the results in the /user/doc/ directory: \f3javadoc -d\fR\f3/user/doc/\fR\f3com\&.mypackage\fR\&. +.TP +-use +.br +Includes one Use page for each documented class and package\&. The page describes what packages, classes, methods, constructors and fields use any API of the specified class or package\&. Given class C, things that use class C would include subclasses of C, fields declared as C, methods that return C, and methods and constructors with parameters of type C\&. For example, you can look at the Use page for the \f3String\fR type\&. Because the \f3getName\fR method in the \f3java\&.awt\&.Font\fR class returns type \f3String\fR, the \f3getName\fR method uses \f3String\fR and so the \f3getName\fR method appears on the Use page for \f3String\fR\&.This documents only uses of the API, not the implementation\&. When a method uses \f3String\fR in its implementation, but does not take a string as an argument or return a string, that is not considered a use of \f3String\fR\&.To access the generated Use page, go to the class or package and click the \fIUse link\fR in the navigation bar\&. +.TP +-version +.br +Includes the @version text in the generated docs\&. This text is omitted by default\&. To find out what version of the \f3javadoc\fR command you are using, use the \f3-J-version\fR option\&. +.TP +-author +.br +Includes the \f3@author\fR text in the generated docs\&. +.TP +-splitindex +.br +Splits the index file into multiple files, alphabetically, one file per letter, plus a file for any index entries that start with non-alphabetical symbols\&. +.TP +-windowtitle \fItitle\fR +.br +Specifies the title to be placed in the HTML \f3<title>\fR tag\&. The text specified in the \f3title\fR tag appears in the window title and in any browser bookmarks (favorite places) that someone creates for this page\&. This title should not contain any HTML tags because the browser does not interpret them correctly\&. Use escape characters on any internal quotation marks within the \f3title\fR tag\&. If the \f3-windowtitle\fR option is omitted, then the \f3javadoc\fR command uses the value of the \f3-doctitle\fR option for the \f3-windowtitle\fR option\&. For example, \f3javadoc -windowtitle "Java SE Platform" com\&.mypackage\fR\&. +.TP +-doctitle \fItitle\fR +.br +Specifies the title to place near the top of the overview summary file\&. The text specified in the \f3title\fR tag is placed as a centered, level-one heading directly beneath the top navigation bar\&. The \f3title\fR tag can contain HTML tags and white space, but when it does, you must enclose the title in quotation marks\&. Internal quotation marks within the \f3title\fR tag must be escaped\&. For example, \f3javadoc -header "<b>Java Platform </b><br>v1\&.4" com\&.mypackage\&.\fR +.TP +-title \fItitle\fR +.br +No longer exists\&. It existed only in Beta releases of Javadoc 1\&.2\&. It was renamed to \f3-doctitle\fR\&. This option was renamed to make it clear that it defines the document title, rather than the window title\&. +.TP +-header \fIheader\fR +.br +Specifies the header text to be placed at the top of each output file\&. The header is placed to the right of the upper navigation bar\&. The \f3header\fR can contain HTML tags and white space, but when it does, the \f3header\fR must be enclosed in quotation marks\&. Use escape characters for internal quotation marks within a header\&. For example, \f3javadoc -header "<b>Java Platform </b><br>v1\&.4" com\&.mypackage\&.\fR +.TP +-footer \fIfooter\fR +.br +Specifies the footer text to be placed at the bottom of each output file\&. The \fIfooter\fR value is placed to the right of the lower navigation bar\&. The \f3footer\fR value can contain HTML tags and white space, but when it does, the \f3footer\fR value must be enclosed in quotation marks\&. Use escape characters for any internal quotation marks within a footer\&. +.TP +-top +.br +Specifies the text to be placed at the top of each output file\&. +.TP +-bottom \fItext\fR +.br +Specifies the text to be placed at the bottom of each output file\&. The text is placed at the bottom of the page, underneath the lower navigation bar\&. The text can contain HTML tags and white space, but when it does, the text must be enclosed in quotation marks\&. Use escape characters for any internal quotation marks within text\&. +.TP +-link \fIextdocURL\fR +.br +Creates links to existing Javadoc-generated documentation of externally referenced classes\&. The \fIextdocURL\fR argument is the absolute or relative URL of the directory that contains the external Javadoc-generated documentation you want to link to\&. You can specify multiple \f3-link\fR options in a specified \f3javadoc\fR command run to link to multiple documents\&. + +The package-list file must be found in this directory (otherwise, use the \f3-linkoffline\fR option)\&. The \f3javadoc\fR command reads the package names from the package-list file and links to those packages at that URL\&. When the \f3javadoc\fR command runs, the \f3extdocURL\fR value is copied into the \f3<A HREF>\fR links that are created\&. Therefore, \f3extdocURL\fR must be the URL to the directory, and not to a file\&. You can use an absolute link for \fIextdocURL\fR to enable your documents to link to a document on any web site, or you can use a relative link to link only to a relative location\&. If you use a relative link, then the value you pass in should be the relative path from the destination directory (specified with the \f3-d\fR option) to the directory containing the packages being linked to\&.When you specify an absolute link, you usually use an HTTP link\&. However, if you want to link to a file system that has no web server, then you can use a file link\&. Use a file link only when everyone who wants to access the generated documentation shares the same file system\&.In all cases, and on all operating systems, use a slash as the separator, whether the URL is absolute or relative, and \f3h\fR\f3ttp:\fR or \f3f\fR\f3ile:\fR as specified in the URL Memo: Uniform Resource Locators at http://www\&.ietf\&.org/rfc/rfc1738\&.txt +.sp +.nf +\f3\-link http://<host>/<directory>/<directory>/\&.\&.\&./<name>\fP +.fi +.nf +\f3\-link file://<host>/<directory>/<directory>/\&.\&.\&./<name>\fP +.fi +.nf +\f3\-link <directory>/<directory>/\&.\&.\&./<name>\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Differences between the -linkoffline and -link options + +Use the \f3-link\fR option in the following cases: +.TP 0.2i +\(bu +When you use a relative path to the external API document\&. +.TP 0.2i +\(bu +When you use an absolute URL to the external API document if your shell lets you open a connection to that URL for reading\&. +.PP +Use the \f3-linkoffline\fR option when you use an absolute URL to the external API document, if your shell does not allow a program to open a connection to that URL for reading\&. This can occur when you are behind a firewall and the document you want to link to is on the other side\&. +.PP +\f3Example 1 Absolute Link to External Documents\fR +.PP +Use the following command if you want to link to the \f3java\&.lang\fR, \f3java\&.io\fR and other Java platform packages, shown at http://docs\&.oracle\&.com/javase/8/docs/api/index\&.html +.sp +.nf +\f3javadoc \-link http://docs\&.oracle\&.com/javase/8/docs/api/ com\&.mypackage\fP +.fi +.nf +\f3\fP +.fi +.sp +The command generates documentation for the package \f3com\&.mypackage\fR with links to the Java SE packages\&. The generated documentation contains links to the \f3Object\fR class, for example, in the class \f3trees\fR\&. Other options, such as the \f3-sourcepath\fR and \f3-d\fR options, are not shown\&. +.PP +\f3Example 2 Relative Link to External Documents\fR +.PP +In this example, there are two packages with documents that are generated in different runs of the \f3javadoc\fR command, and those documents are separated by a relative path\&. The packages are \f3com\&.apipackage\fR, an API, and c\f3om\&.spipackage\fR, an Service Provide Interface (SPI)\&. You want the documentation to reside in docs/api/com/apipackage and docs/spi/com/spipackage\&. Assuming that the API package documentation is already generated, and that docs is the current directory, you document the SPI package with links to the API documentation by running: \f3javadoc -d \&./spi -link \&.\&./api com\&.spipackage\fR\&. +.PP +Notice the \f3-link\fR option is relative to the destination directory (docs/spi)\&. +.PP +Notes + +The \f3-link\fR option lets you link to classes referenced to by your code, but not documented in the current \f3javadoc\fR command run\&. For these links to go to valid pages, you must know where those HTML pages are located and specify that location with \f3extdocURL\fR\&. This allows third-party documentation to link to java\&.* documentation at http://docs\&.oracle\&.com\&.Omit the \f3-link\fR option when you want the \f3javadoc\fR command to create links only to APIs within the documentation it is generating in the current run\&. Without the \f3-link\fR option, the \f3javadoc\fR command does not create links to documentation for external references because it does not know whether or where that documentation exists\&.The \f3-link\fR option can create links in several places in the generated documentation\&. See Process Source Files\&. Another use is for cross-links between sets of packages: Execute the \f3javadoc\fR command on one set of packages, then run the \f3javadoc\fR command again on another set of packages, creating links both ways between both sets\&. +.PP +How to Reference a Class + +For a link to an externally referenced class to appear (and not just its text label), the class must be referenced in the following way\&. It is not sufficient for it to be referenced in the body of a method\&. It must be referenced in either an \f3import\fR statement or in a declaration\&. Here are examples of how the class \f3java\&.io\&.File\fR can be referenced: +.PP +\fI\fRIn any kind of import statement\&. By wildcard import, import explicitly by name, or automatically import for \f3java\&.lang\&.*\fR\&. +.PP +In Java SE 1\&.3\&.\fIn\fR and 1\&.2\&.\fIn\fR, only an explicit import by name works\&. A wildcard \f3import\fR statement does not work, nor does the automatic \f3import java\&.lang\&.*\fR\&. +.PP +\fI\fRIn a declaration: \f3void mymethod(File f) {}\fR +.PP +The reference can be in the return type or parameter type of a method, constructor, field, class, or interface, or in an implements, extends, or throws statement\&. +.PP +An important corollary is that when you use the \f3-link\fR option, there can be many links that unintentionally do not appear due to this constraint\&. The text would appear without being a link\&. You can detect these by the warnings they emit\&. The simplest way to properly reference a class and add the link would be to import that class\&. +.PP +Package List + +The \f3-link\fR option requires that a file named package-list, which is generated by the \f3javadoc\fR command, exists at the URL you specify with the \f3-link\fR option\&. The package-list file is a simple text file that lists the names of packages documented at that location\&. In the earlier example, the \f3javadoc\fR command searches for a file named package-list at the specified URL, reads in the package names, and links to those packages at that URL\&. +.PP +For example, the package list for the Java SE API is located at http://docs\&.oracle\&.com/javase/8/docs/api/package-list +.PP +The package list starts as follows: +.sp +.nf +\f3java\&.applet\fP +.fi +.nf +\f3java\&.awt\fP +.fi +.nf +\f3java\&.awt\&.color\fP +.fi +.nf +\f3java\&.awt\&.datatransfer\fP +.fi +.nf +\f3java\&.awt\&.dnd\fP +.fi +.nf +\f3java\&.awt\&.event\fP +.fi +.nf +\f3java\&.awt\&.font\fP +.fi +.nf +\f3and so on \&.\&.\&.\&.\fP +.fi +.nf +\f3\fP +.fi +.sp +When \f3javadoc\fR is run without the \f3-link\fR option and encounters a name that belongs to an externally referenced class, it prints the name with no link\&. However, when the \f3-link\fR option is used, the \f3javadoc\fR command searches the package-list file at the specified \fIextdocURL\fR location for that package name\&. When it finds the package name, it prefixes the name with \fIextdocURL\fR\&. +.PP +For there to be no broken links, all of the documentation for the external references must exist at the specified URLs\&. The \f3javadoc\fR command does not check that these pages exist, but only that the package-list exists\&. +.PP +Multiple Links + +You can supply multiple \f3-link\fR options to link to any number of externally generated documents\&. Javadoc 1\&.2 has a known bug that prevents you from supplying more than one \f3-link\fR options\&. This was fixed in Javadoc 1\&.2\&.2\&. Specify a different link option for each external document to link to \f3javadoc -link extdocURL1 -link extdocURL2 \&.\&.\&. -link extdocURLn com\&.mypackage\fR where \fIextdocURL1\fR, \fIextdocURL2\fR, \&.\f3\&.\&. extdocURLn\fR point respectively to the roots of external documents, each of which contains a file named package-list\&. +.PP +Cross Links + +Note that bootstrapping might be required when cross-linking two or more documents that were previously generated\&. If package-list does not exist for either document when you run the \f3javadoc\fR command on the first document, then the package-list does not yet exist for the second document\&. Therefore, to create the external links, you must regenerate the first document after you generate the second document\&. +.PP +In this case, the purpose of first generating a document is to create its package-list (or you can create it by hand if you are certain of the package names)\&. Then, generate the second document with its external links\&. The \f3javadoc\fR command prints a warning when a needed external package-list file does not exist\&. +.TP +-linkoffline \fIextdocURL packagelistLoc\fR +.br +This option is a variation of the \f3-link\fR option\&. They both create links to Javadoc-generated documentation for externally referenced classes\&. Use the \f3-link\fRo\f3ffline\fR option when linking to a document on the web when the \f3javadoc\fR command cannot access the document through a web connection\&. Use the \f3-linkoffline\fR option when package-list file of the external document is not accessible or does not exist at the \f3extdocURL\fR location, but does exist at a different location that can be specified by \f3packageListLoc\fR (typically local)\&. If \f3extdocURL\fR is accessible only on the World Wide Web, then the \f3-linkoffline\fR option removes the constraint that the \f3javadoc\fR command must have a web connection to generate documentation\&. Another use is as a work-around to update documents: After you have run the \f3javadoc\fR command on a full set of packages, you can run the \f3javadoc\fR command again on a smaller set of changed packages, so that the updated files can be inserted back into the original set\&. Examples follow\&. The \f3-linkoffline\fR option takes two arguments\&. The first is for the string to be embedded in the \f3<a href>\fR links, and the second tells the \f3-linkoffline\fR option where to find package-list: +.RS +.TP 0.2i +\(bu +The \f3extdocURL\fR value is the absolute or relative URL of the directory that contains the external Javadoc-generated documentation you want to link to\&. When relative, the value should be the relative path from the destination directory (specified with the \f3-d\fR option) to the root of the packages being linked to\&. For more information, see \fIextdocURL\fR in the \f3-link\fR option\&. +.TP 0.2i +\(bu +The \f3packagelistLoc\fR value is the path or URL to the directory that contains the package-list file for the external documentation\&. This can be a URL (http: or file:) or file path, and can be absolute or relative\&. When relative, make it relative to the current directory from where the \f3javadoc\fR command was run\&. Do not include the package-list file name\&. + +You can specify multiple \f3-linkoffline\fR options in a specified \f3javadoc\fR command run\&. Before Javadoc 1\&.2\&.2, the \f3-linkfile\fR options could be specified once\&. +.RE + +.PP +Absolute Links to External Documents + +You might have a situation where you want to link to the \f3java\&.lang\fR, \f3java\&.io\fR and other Java SE packages at http://docs\&.oracle\&.com/javase/8/docs/api/index\&.html +.PP +However, your shell does not have web access\&. In this case, do the following: +.TP 0.4i +1\&. +Open the package-list file in a browser at http://docs\&.oracle\&.com/javase/8/docs/api/package-list +.TP 0.4i +2\&. +Save the file to a local directory, and point to this local copy with the second argument, \f3packagelistLoc\fR\&. In this example, the package list file was saved to the current directory (\&.)\&. +.PP +The following command generates documentation for the package c\f3om\&.mypackage\fR with links to the Java SE packages\&. The generated documentation will contain links to the \f3Object\fR class, for example, in the class \f3trees\fR\&. Other necessary options, such as \f3-sourcepath\fR, are not shown\&. +.sp +.nf +\f3javadoc \-linkoffline http://docs\&.oracle\&.com/javase/8/docs/api/ \&. com\&.mypackage \fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Relative Links to External Documents + +It is not very common to use \f3-linkoffline\fR with relative paths, for the simple reason that the \f3-link\fR option is usually enough\&. When you use the \f3-linkoffline\fR option, the package-list file is usually local, and when you use relative links, the file you are linking to is also local, so it is usually unnecessary to give a different path for the two arguments to the \f3-linkoffline\fR option When the two arguments are identical, you can use the \f3-link\fR option\&. +.PP +Create a package-list File Manually + +If a package-list file does not exist yet, but you know what package names your document will link to, then you can manually create your own copy of this file and specify its path with \f3packagelistLoc\fR\&. An example would be the previous case where the package list for \f3com\&.spipackage\fR did not exist when \f3com\&.apipackage\fR was first generated\&. This technique is useful when you need to generate documentation that links to new external documentation whose package names you know, but which is not yet published\&. This is also a way of creating package-list files for packages generated with Javadoc 1\&.0 or 1\&.1, where package-list files were not generated\&. Similarly, two companies can share their unpublished package-list files so they can release their cross-linked documentation simultaneously\&. +.PP +Link to Multiple Documents + +You can include the \f3-linkoffline\fR option once for each generated document you want to refer to: +.sp +.nf +\f3javadoc \-linkoffline extdocURL1 packagelistLoc1 \-linkoffline extdocURL2\fP +.fi +.nf +\f3packagelistLoc2 \&.\&.\&.\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Update Documents + +You can also use the \f3-linkoffline\fR option when your project has dozens or hundreds of packages\&. If you have already run the \f3javadoc\fR command on the entire source tree, then you can quickly make small changes to documentation comments and rerun the \f3javadoc\fR command on a portion of the source tree\&. Be aware that the second run works properly only when your changes are to documentation comments and not to declarations\&. If you were to add, remove, or change any declarations from the source code, then broken links could show up in the index, package tree, inherited member lists, Use page, and other places\&. +.PP +First, create a new destination directory, such as update, for this new small run\&. In this example, the original destination directory is named html\&. In the simplest example, change directory to the parent of html\&. Set the first argument of the \f3-linkoffline\fR option to the current directory (\&.) and set the second argument to the relative path to html, where it can find package-list and pass in only the package names of the packages you want to update: +.sp +.nf +\f3javadoc \-d update \-linkoffline \&. html com\&.mypackage\fP +.fi +.nf +\f3\fP +.fi +.sp +When the \f3javadoc\fR command completes, copy these generated class pages in update/com/package (not the overview or index) to the original files in html/com/package\&. +.TP +-linksource +.br +Creates an HTML version of each source file (with line numbers) and adds links to them from the standard HTML documentation\&. Links are created for classes, interfaces, constructors, methods, and fields whose declarations are in a source file\&. Otherwise, links are not created, such as for default constructors and generated classes\&. + +This option exposes all private implementation details in the included source files, including private classes, private fields, and the bodies of private methods, regardless of the \f3-public\fR, \f3-package\fR, \f3-protected\fR, and \f3-private\fR options\&. Unless you also use the \f3-private\fR option, not all private classes or interfaces are accessible through links\&. + +Each link appears on the name of the identifier in its declaration\&. For example, the link to the source code of the \f3Button\fR class would be on the word \f3Button\fR: +.sp +.nf +\f3public class Button extends Component implements Accessible\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The link to the source code of the \f3getLabel\fR method in the \f3Button\fR class is on the word \f3getLabel\fR: +.sp +.nf +\f3public String getLabel()\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-group groupheading \fIpackagepattern:packagepattern\fR +.br +Separates packages on the overview page into whatever groups you specify, one group per table\&. You specify each group with a different \f3-group\fR option\&. The groups appear on the page in the order specified on the command line\&. Packages are alphabetized within a group\&. For a specified \f3-group\fR option, the packages matching the list of \f3packagepattern\fR expressions appear in a table with the heading \fIgroupheading\fR\&. +.RS +.TP 0.2i +\(bu +The \f3groupheading\fR can be any text and can include white space\&. This text is placed in the table heading for the group\&. +.TP 0.2i +\(bu +The \f3packagepattern\fR value can be any package name at the start of any package name followed by an asterisk (*)\&. The asterisk is the only wildcard allowed and means match any characters\&. Multiple patterns can be included in a group by separating them with colons (:)\&. If you use an asterisk in a pattern or pattern list, then the pattern list must be inside quotation marks, such as \f3"java\&.lang*:java\&.util"\fR\&. +.RE + + +When you do not supply a \f3-group\fR option, all packages are placed in one group with the heading \fIPackages\fR and appropriate subheadings\&. If the subheadings do not include all documented packages (all groups), then the remaining packages appear in a separate group with the subheading Other Packages\&. + +For example, the following \f3javadoc\fR command separates the three documented packages into \fICore\fR, \fIExtension\fR, and \fIOther Packages\fR\&. The trailing dot (\&.) does not appear in \f3java\&.lang*\fR\&. Including the dot, such as \f3java\&.lang\&.*\fR omits the\f3java\&.lang\fR package\&. +.sp +.nf +\f3javadoc \-group "Core Packages" "java\&.lang*:java\&.util"\fP +.fi +.nf +\f3 \-group "Extension Packages" "javax\&.*"\fP +.fi +.nf +\f3 java\&.lang java\&.lang\&.reflect java\&.util javax\&.servlet java\&.new\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\fICore Packages\fR + +\f3java\&.lang\fR + +\f3java\&.lang\&.reflect\fR + +\f3java\&.util\fR + +\fIExtension Packages\fR + +\f3javax\&.servlet\fR + +\fIOther Packages\fR + +\f3java\&.new\fR +.TP +-nodeprecated +.br +Prevents the generation of any deprecated API in the documentation\&. This does what the \f3-nodeprecatedlist\fR option does, and it does not generate any deprecated API throughout the rest of the documentation\&. This is useful when writing code when you do not want to be distracted by the deprecated code\&. +.TP +-nodeprecatedlist +.br +Prevents the generation of the file that contains the list of deprecated APIs (deprecated-list\&.html) and the link in the navigation bar to that page\&. The \f3javadoc\fR command continues to generate the deprecated API throughout the rest of the document\&. This is useful when your source code contains no deprecated APIs, and you want to make the navigation bar cleaner\&. +.TP +-nosince +.br +Omits from the generated documents the \f3Since\fR sections associated with the \f3@since\fR tags\&. +.TP +-notree +.br +Omits the class/interface hierarchy pages from the generated documents\&. These are the pages you reach using the Tree button in the navigation bar\&. The hierarchy is produced by default\&. +.TP +-noindex +.br +Omits the index from the generated documents\&. The index is produced by default\&. +.TP +-nohelp +.br +Omits the HELP link in the navigation bars at the top and bottom of each page of output\&. +.TP +-nonavbar +.br +Prevents the generation of the navigation bar, header, and footer, that are usually found at the top and bottom of the generated pages\&. The \f3-nonavbar\fR option has no affect on the \f3-bottom\fR option\&. The \f3-nonavbar\fR option is useful when you are interested only in the content and have no need for navigation, such as when you are converting the files to PostScript or PDF for printing only\&. +.TP +-helpfile \fIpath\efilename\fR +.br +Specifies the path of an alternate help file path\efilename that the HELP link in the top and bottom navigation bars link to\&. Without this option, the \f3javadoc\fR command creates a help file help-doc\&.html that is hard-coded in the \f3javadoc\fR command\&. This option lets you override the default\&. The file name can be any name and is not restricted to help-doc\&.html\&. The \f3javadoc\fR command adjusts the links in the navigation bar accordingly, for example: +.sp +.nf +\f3javadoc \-helpfile /home/user/myhelp\&.html java\&.awt\&.\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-stylesheet \fIpath/filename\fR +.br +Specifies the path of an alternate HTML stylesheet file\&. Without this option, the \f3javadoc\fR command automatically creates a stylesheet file stylesheet\&.css that is hard-coded in the \f3javadoc\fR command\&. This option lets you override the default\&. The file name can be any name and is not restricted to stylesheet\&.css, for example: +.sp +.nf +\f3javadoc \-stylesheet file /home/user/mystylesheet\&.css com\&.mypackage\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-serialwarn +.br +Generates compile-time warnings for missing \f3@serial\fR tags\&. By default, Javadoc 1\&.2\&.2 and later versions generate no serial warnings\&. This is a reversal from earlier releases\&. Use this option to display the serial warnings, which helps to properly document default serializable fields and \f3writeExternal\fR methods\&. +.TP +-charset \fIname\fR +.br +Specifies the HTML character set for this document\&. The name should be a preferred MIME name as specified in the IANA Registry, Character Sets at http://www\&.iana\&.org/assignments/character-sets + +For example, \f3javadoc -charset "iso-8859-1" mypackage\fR inserts the following line in the head of every generated page: +.sp +.nf +\f3<META http\-equiv="Content\-Type" content="text/html; charset=ISO\-8859\-1">\fP +.fi +.nf +\f3\fP +.fi +.sp + + +This \f3META\fR tag is described in the HTML standard (4197265 and 4137321), HTML Document Representation, at http://www\&.w3\&.org/TR/REC-html40/charset\&.html#h-5\&.2\&.2 + +See also the \f3-encoding\fR and \f3-docencoding name\fR options\&. +.TP +-docencoding \fIname\fR +.br +Specifies the encoding of the generated HTML files\&. The name should be a preferred MIME name as specified in the IANA Registry, Character Sets at http://www\&.iana\&.org/assignments/character-sets + +If you omit the \f3-docencoding\fR option but use the \f3-encoding\fR option, then the encoding of the generated HTML files is determined by the \f3-encoding\fR option, for example: \f3javadoc -docencoding "iso-8859-1" mypackage\fR\&. See also the \f3-encoding\fR and \f3-docencoding name\fR options\&. +.TP +-keywords +.br +Adds HTML keyword <META> tags to the generated file for each class\&. These tags can help search engines that look for <META> tags find the pages\&. Most search engines that search the entire Internet do not look at <META> tags, because pages can misuse them\&. Search engines offered by companies that confine their searches to their own website can benefit by looking at <META> tags\&. The <META> tags include the fully qualified name of the class and the unqualified names of the fields and methods\&. Constructors are not included because they are identical to the class name\&. For example, the class \f3String\fR starts with these keywords: +.sp +.nf +\f3<META NAME="keywords" CONTENT="java\&.lang\&.String class">\fP +.fi +.nf +\f3<META NAME="keywords" CONTENT="CASE_INSENSITIVE_ORDER">\fP +.fi +.nf +\f3<META NAME="keywords" CONTENT="length()">\fP +.fi +.nf +\f3<META NAME="keywords" CONTENT="charAt()">\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-tag \fItagname\fR:Xaoptcmf:"\fItaghead\fR" +.br +Enables the \f3javadoc\fR command to interpret a simple, one-argument \f3@tagname\fR custom block tag in documentation comments\&. For the \f3javadoc\fR command to spell-check tag names, it is important to include a \f3-tag\fR option for every custom tag that is present in the source code, disabling (with \f3X\fR) those that are not being output in the current run\&.The colon (:) is always the separator\&. The \f3-tag\fR option outputs the tag heading \fItaghead\fR in bold, followed on the next line by the text from its single argument\&. Similar to any block tag, the argument text can contain inline tags, which are also interpreted\&. The output is similar to standard one-argument tags, such as the \f3@return\fR and \f3@author\fR tags\&. Omitting a value for \fItaghead\fR causes \f3tagname\fR to be the heading\&. + +\fIPlacement of tags\fR: The \f3Xaoptcmf\fR arguments determine where in the source code the tag is allowed to be placed, and whether the tag can be disabled (using \f3X\fR)\&. You can supply either \f3a\fR, to allow the tag in all places, or any combination of the other letters: + +\f3X\fR (disable tag) + +\f3a\fR (all) + +\f3o\fR (overview) + +\f3p\fR (packages) + +\f3t\fR (types, that is classes and interfaces) + +\f3c\fR (constructors) + +\f3m\fR (methods) + +\f3f\fR (fields) + +\fIExamples of single tags\fR: An example of a tag option for a tag that can be used anywhere in the source code is: \f3-tag todo:a:"To Do:"\fR\&. + +If you want the \f3@todo\fR tag to be used only with constructors, methods, and fields, then you use: \f3-tag todo:cmf:"To Do:"\fR\&. + +Notice the last colon (:) is not a parameter separator, but is part of the heading text\&. You would use either tag option for source code that contains the \f3@todo\fR tag, such as: \f3@todo The documentation for this method needs work\fR\&. + +\fIColons in tag names\fR: Use a backslash to escape a colon that you want to use in a tag name\&. Use the \f3-tag ejb\e\e:bean:a:"EJB Bean:"\fR option for the following documentation comment: +.sp +.nf +\f3/**\fP +.fi +.nf +\f3 * @ejb:bean\fP +.fi +.nf +\f3 */\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\fISpell-checking tag names\fR: Some developers put custom tags in the source code that they do not always want to output\&. In these cases, it is important to list all tags that are in the source code, enabling the ones you want to output and disabling the ones you do not want to output\&. The presence of \f3X\fR disables the tag, while its absence enables the tag\&. This gives the \f3javadoc\fR command enough information to know whether a tag it encounters is unknown, which is probably the results of a typographical error or a misspelling\&. The \f3javadoc\fR command prints a warning in these cases\&. You can add \f3X\fR to the placement values already present, so that when you want to enable the tag, you can simply delete the \f3X\fR\&. For example, if the \f3@todo\fR tag is a tag that you want to suppress on output, then you would use: \f3-tag todo:Xcmf:"To Do:"\fR\&. If you would rather keep it simple, then use this: \f3-tag todo:X\fR\&. The syntax \f3-tag todo:X\fR works even when the \f3@todo\fR tag is defined by a taglet\&. + +\fIOrder of tags\fR: The order of the \f3-ta\fR\f3g\fR and \f3-taglet\fR options determines the order the tags are output\&. You can mix the custom tags with the standard tags to intersperse them\&. The tag options for standard tags are placeholders only for determining the order\&. They take only the standard tag\&'s name\&. Subheadings for standard tags cannot be altered\&. This is illustrated in the following example\&.If the \f3-tag\fR option is missing, then the position of the \f3-tagle\fR\f3t\fR option determines its order\&. If they are both present, then whichever appears last on the command line determines its order\&. This happens because the tags and taglets are processed in the order that they appear on the command line\&. For example, if the \f3-taglet\fR and \f3-tag\fR options have the name \f3todo\fR value, then the one that appears last on the command line determines the order\&. + +\fIExample of a complete set of tags\fR: This example inserts To Do after Parameters and before Throws in the output\&. By using \f3X\fR, it also specifies that the \f3@example\fR tag might be encountered in the source code that should not be output during this run\&. If you use the \f3@argfile\fR tag, then you can put the tags on separate lines in an argument file similar to this (no line continuation characters needed): +.sp +.nf +\f3\-tag param\fP +.fi +.nf +\f3\-tag return\fP +.fi +.nf +\f3\-tag todo:a:"To Do:"\fP +.fi +.nf +\f3\-tag throws\fP +.fi +.nf +\f3\-tag see\fP +.fi +.nf +\f3\-tag example:X\fP +.fi +.nf +\f3\fP +.fi +.sp + + +When the \f3javadoc\fR command parses the documentation comments, any tag encountered that is neither a standard tag nor passed in with the \f3-tag\fR or \f3-taglet\fR options is considered unknown, and a warning is thrown\&. + +The standard tags are initially stored internally in a list in their default order\&. Whenever the \f3-tag\fR options are used, those tags get appended to this list\&. Standard tags are moved from their default position\&. Therefore, if a \f3-tag\fR option is omitted for a standard tag, then it remains in its default position\&. + +\fIAvoiding conflicts\fR: If you want to create your own namespace, then you can use a dot-separated naming convention similar to that used for packages: \f3com\&.mycompany\&.todo\fR\&. Oracle will continue to create standard tags whose names do not contain dots\&. Any tag you create will override the behavior of a tag by the same name defined by Oracle\&. If you create a \f3@todo\fR tag or taglet, then it always has the same behavior you define, even when Oracle later creates a standard tag of the same name\&. + +\fIAnnotations vs\&. Javadoc tags\fR: In general, if the markup you want to add is intended to affect or produce documentation, then it should be a Javadoc tag\&. Otherwise, it should be an annotation\&. See Custom Tags and Annotations in How to Write Doc Comments for the Javadoc Tool at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html#annotations + +You can also create more complex block tags or custom inline tags with the \f3-taglet\fR option\&. +.TP +-taglet \fIclass\fR +.br +Specifies the class file that starts the taglet used in generating the documentation for that tag\&. Use the fully qualified name for the \f3class\fR value\&. This taglet also defines the number of text arguments that the custom tag has\&. The taglet accepts those arguments, processes them, and generates the output\&. For extensive documentation with example taglets, see: Taglet Overview at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/taglet/overview\&.html + +Taglets are useful for block or inline tags\&. They can have any number of arguments and implement custom behavior, such as making text bold, formatting bullets, writing out the text to a file, or starting other processes\&. Taglets can only determine where a tag should appear and in what form\&. All other decisions are made by the doclet\&. A taglet cannot do things such as remove a class name from the list of included classes\&. However, it can execute side effects, such as printing the tag\&'s text to a file or triggering another process\&. Use the \f3-tagletpath\fR option to specify the path to the taglet\&. The following example inserts the To Do taglet after Parameters and ahead of Throws in the generated pages\&. Alternately, you can use the \f3-taglet\fR option in place of its \f3-tag\fR option, but that might be difficult to read\&. +.sp +.nf +\f3\-taglet com\&.sun\&.tools\&.doclets\&.ToDoTaglet\fP +.fi +.nf +\f3\-tagletpath /home/taglets \fP +.fi +.nf +\f3\-tag return\fP +.fi +.nf +\f3\-tag param\fP +.fi +.nf +\f3\-tag todo\fP +.fi +.nf +\f3\-tag throws\fP +.fi +.nf +\f3\-tag see\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-tagletpath \fItagletpathlist\fR +.br +Specifies the search paths for finding taglet class files\&. The \f3tagletpathlist\fR can contain multiple paths by separating them with a colon (:)\&. The \f3javadoc\fR command searches all subdirectories of the specified paths\&. +.TP +-docfilesubdirs +.br +Enables deep copying of doc-files directories\&. Subdirectories and all contents are recursively copied to the destination\&. For example, the directory doc-files/example/images and all of its contents would be copied\&. There is also an option to exclude subdirectories\&. +.TP +-excludedocfilessubdir \fIname1:name2\fR +.br +Excludes any doc-files subdirectories with the specified names\&. This prevents the copying of SCCS and other source-code-control subdirectories\&. +.TP +-noqualifier all | \fIpackagename1\fR:\fIpackagename2\&.\&.\&.\fR +.br +Omits qualifying package names from class names in output\&. The argument to the \f3-noqualifier\fR option is either \f3all\fR (all package qualifiers are omitted) or a colon-separate list of packages, with wild cards, to be removed as qualifiers\&. The package name is removed from places where class or interface names appear\&. See Process Source Files\&. + +The following example omits all package qualifiers: \f3-noqualifier all\fR\&. + +The following example omits \f3java\&.lang\fR and \f3java\&.io\fR package qualifiers: \f3-noqualifier java\&.lang:java\&.io\fR\&. + +The following example omits package qualifiers starting with \f3java\fR, and \f3com\&.sun\fR subpackages, but not \f3javax\fR: \f3-noqualifier java\&.*:com\&.sun\&.*\fR\&. + +Where a package qualifier would appear due to the previous behavior, the name can be suitably shortened\&. See How a Name Appears\&. This rule is in effect whether or not the \f3-noqualifier\fR option is used\&. +.TP +-notimestamp +.br +Suppresses the time stamp, which is hidden in an HTML comment in the generated HTML near the top of each page\&. The \f3-notimestamp\fR option is useful when you want to run the \f3javadoc\fR command on two source bases and get the differences between \f3diff\fR them, because it prevents time stamps from causing a \f3diff\fR (which would otherwise be a \f3diff\fR on every page)\&. The time stamp includes the \f3javadoc\fR command release number, and currently appears similar to this: \f3<!-- Generated by javadoc (build 1\&.5\&.0_01) on Thu Apr 02 14:04:52 IST 2009 -->\fR\&. +.TP +-nocomment +.br +Suppresses the entire comment body, including the main description and all tags, and generate only declarations\&. This option lets you reuse source files that were originally intended for a different purpose so that you can produce skeleton HTML documentation at the early stages of a new project\&. +.TP +-sourcetab \fItablength\fR +.br +Specifies the number of spaces each tab uses in the source\&. +.SH COMMAND-LINE\ ARGUMENT\ FILES +To shorten or simplify the \f3javadoc\fR command, you can specify one or more files that contain arguments to the \f3javadoc\fR command (except \f3-J\fR options)\&. This enables you to create \f3javadoc\fR commands of any length on any operating system\&. +.PP +An argument file can include \f3javac\fR options and source file names in any combination\&. The arguments within a file can be space-separated or newline-separated\&. If a file name contains embedded spaces, then put the whole file name in double quotation marks\&. +.PP +File Names within an argument file are relative to the current directory, not the location of the argument file\&. Wild cards (\f3*\fR) are not allowed in these lists (such as for specifying *\&.java)\&. Using the at sign (@) to recursively interpret files is not supported\&. The \f3-J\fR options are not supported because they are passed to the launcher, which does not support argument files\&. +.PP +When you run the \f3javadoc\fR command, pass in the path and name of each argument file with the @ leading character\&. When the \f3javadoc\fR command encounters an argument beginning with the at sign (@), it expands the contents of that file into the argument list\&. +.PP +\f3Example 1 Single Argument File\fR +.PP +You could use a single argument file named \f3argfile\fR to hold all \f3javadoc\fR command arguments: \f3javadoc @argfile\fR\&. The argument file \f3\fRcontains the contents of both files, as shown in the next example\&. +.PP +\f3Example 2 Two Argument Files\fR +.PP +You can create two argument files: One for the \f3javadoc\fR command options and the other for the package names or source file names\&. Notice the following lists have no line-continuation characters\&. +.PP +Create a file named options that contains: +.sp +.nf +\f3\-d docs\-filelist \fP +.fi +.nf +\f3\-use \fP +.fi +.nf +\f3\-splitindex\fP +.fi +.nf +\f3\-windowtitle \&'Java SE 7 API Specification\&'\fP +.fi +.nf +\f3\-doctitle \&'Java SE 7 API Specification\&'\fP +.fi +.nf +\f3\-header \&'<b>Java\(tm SE 7</b>\&'\fP +.fi +.nf +\f3\-bottom \&'Copyright © 1993\-2011 Oracle and/or its affiliates\&. All rights reserved\&.\&'\fP +.fi +.nf +\f3\-group "Core Packages" "java\&.*"\fP +.fi +.nf +\f3\-overview /java/pubs/ws/1\&.7\&.0/src/share/classes/overview\-core\&.html\fP +.fi +.nf +\f3\-sourcepath /java/pubs/ws/1\&.7\&.0/src/share/classes\fP +.fi +.nf +\f3\fP +.fi +.sp +Create a file named packages that contains: +.sp +.nf +\f3com\&.mypackage1\fP +.fi +.nf +\f3com\&.mypackage2\fP +.fi +.nf +\f3com\&.mypackage3\fP +.fi +.nf +\f3\fP +.fi +.sp +Run the \f3javadoc\fR command as follows: +.sp +.nf +\f3javadoc @options @packages\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 3 Argument Files with Paths\fR +.PP +The argument files can have paths, but any file names inside the files are relative to the current working directory (not \f3path1\fR or \f3path2\fR): +.sp +.nf +\f3javadoc @path1/options @path2/packages\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 4 Option Arguments\fR +.PP +The following example saves an argument to a \f3javadoc\fR command option in an argument file\&. The \f3-bottom\fR option is used because it can have a lengthy argument\&. You could create a file named bottom to contain the text argument: +.sp +.nf +\f3<font size="\-1">\fP +.fi +.nf +\f3 <a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fP +.fi +.nf +\f3 Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&. <br/>\fP +.fi +.nf +\f3 Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fP +.fi +.nf +\f3 Other names may be trademarks of their respective owners\&.</font>\fP +.fi +.nf +\f3\fP +.fi +.sp +Run the \f3javadoc\fR command as follows:\f3javadoc -bottom @bottom @packages\fR\&. +.PP +You can also include the \f3-bottom\fR option at the start of the argument file and run the \f3javadoc\fR command as follows: \f3javadoc @bottom @packages\fR\&. +.SH RUNNING\ THE\ JAVADOC\ COMMAND +The release number of the \f3javadoc\fR command can be determined with the \f3javadoc -J-version\fR option\&. The release number of the standard doclet appears in the output stream\&. It can be turned off with the \f3-quiet\fR option\&. +.PP +Use the public programmatic interface to call the \f3javadoc\fR command from within programs written in the Java language\&. This interface is in \f3com\&.sun\&.tools\&.javadoc\&.Main\fR (and the \f3javadoc\fR command is reentrant)\&. For more information, see The Standard Doclet at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/standard-doclet\&.html#runningprogrammatically +.PP +The following instructions call the standard HTML doclet\&. To call a custom doclet, use the \f3-doclet\fR and \f3-docletpath\fR options\&. See Doclet Overview at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/doclet/overview\&.html +.SS SIMPLE\ EXAMPLES +You can run the \f3javadoc\fR command on entire packages or individual source files\&. Each package name has a corresponding directory name\&. +.PP +In the following examples, the source files are located at /home/src/java/awt/*\&.java\&. The destination directory is /home/html\&. +.PP +Document One or More Packages + +To document a package, the source files for that package must be located in a directory that has the same name as the package\&. +.PP +If a package name has several identifiers (separated by dots, such as \f3java\&.awt\&.color\fR), then each subsequent identifier must correspond to a deeper subdirectory (such as java/awt/color)\&. +.PP +You can split the source files for a single package among two such directory trees located at different places, as long as \f3-sourcepath\fR points to them both\&. For example, src1/java/awt/color and src2/java/awt/color\&. +.PP +You can run the \f3javadoc\fR command either by changing directories (with the \f3cd\fR command) or by using the \f3-sourcepath\fR option\&. The following examples illustrate both alternatives\&. +.PP +\f3Example 1 Recursive Run from One or More Packages\fR +.PP +This example uses \f3-sourcepath\fR so the \f3javadoc\fR command can be run from any directory and \f3-subpackages\fR (a new 1\&.4 option) for recursion\&. It traverses the subpackages of the java directory excluding packages rooted at \f3java\&.net\fR and \f3java\&.lang\fR\&. Notice this excludes \f3java\&.lang\&.ref\fR, a subpackage of \f3java\&.lang\fR\&. To also traverse down other package trees, append their names to the \f3-subpackages\fR argument, such as \f3java:javax:org\&.xml\&.sax\fR\&. +.sp +.nf +\f3javadoc \-d /home/html \-sourcepath /home/src \-subpackages java \-exclude\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 2 Change to Root and Run Explicit Packages\fR +.PP +Change to the parent directory of the fully qualified package\&. Then, run the \f3javadoc\fR command with the names of one or more packages that you want to document: +.sp +.nf +\f3cd /home/src/\fP +.fi +.nf +\f3javadoc \-d /home/html java\&.awt java\&.awt\&.event\fP +.fi +.nf +\f3\fP +.fi +.sp +To also traverse down other package trees, append their names to the \f3-subpackages\fR argument, such as j\f3ava:javax:org\&.xml\&.sax\fR\&. +.PP +\f3Example 3 Run from Any Directory on Explicit Packages in One Tree\fR +.PP +In this case, it does not matter what the current directory is\&. Run the \f3javadoc\fR command and use the \f3-sourcepath\fR option with the parent directory of the top-level package\&. Provide the names of one or more packages that you want to document: +.sp +.nf +\f3javadoc \-d /home/html \-sourcepath /home/src java\&.awt java\&.awt\&.event\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 4 Run from Any Directory on Explicit Packages in Multiple Trees\fR +.PP +Run the \f3javadoc\fR command and use the \f3-sourcepath\fR option with a colon-separated list of the paths to each tree\&'s root\&. Provide the names of one or more packages that you want to document\&. All source files for a specified package do not need to be located under a single root directory, but they must be found somewhere along the source path\&. +.sp +.nf +\f3javadoc \-d /home/html \-sourcepath /home/src1:/home/src2 java\&.awt java\&.awt\&.event\fP +.fi +.nf +\f3\fP +.fi +.sp +The result is that all cases generate HTML-formatted documentation for the \f3public\fR and \f3protected\fR classes and interfaces in packages j\f3ava\&.awt\fR and \f3java\&.awt\&.even\fRt and save the HTML files in the specified destination directory\&. Because two or more packages are being generated, the document has three HTML frames: one for the list of packages, another for the list of classes, and the third for the main class pages\&. +.PP +Document One or More Classes + +The second way to run the \f3javadoc\fR command is to pass one or more source files\&. You can run \f3javadoc\fR either of the following two ways: by changing directories (with the \f3cd\fR command) or by fully specifying the path to the source files\&. Relative paths are relative to the current directory\&. The \f3-sourcepath\fR option is ignored when passing source files\&. You can use command-line wild cards, such as an asterisk (*), to specify groups of classes\&. +.PP +\f3Example 1 Change to the Source Directory\fR +.PP +Change to the directory that holds the source files\&. Then run the \f3javadoc\fR command with the names of one or more source files you want to document\&. +.PP +This example generates HTML-formatted documentation for the classes \f3Button\fR, \f3Canvas,\fR and classes that begin with \f3Graphics\fR\&. Because source files rather than package names were passed in as arguments to the \f3javadoc\fR command, the document has two frames: one for the list of classes and the other for the main page\&. +.sp +.nf +\f3cd /home/src/java/awt\fP +.fi +.nf +\f3javadoc \-d /home/html Button\&.java Canvas\&.java Graphics*\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 2 Change to the Root Directory of the Package\fR +.PP +This is useful for documenting individual source files from different subpackages off of the same root\&. Change to the package root directory, and supply the source files with paths from the root\&. +.sp +.nf +\f3cd /home/src/\fP +.fi +.nf +\f3javadoc \-d /home/html java/awt/Button\&.java java/applet/Applet\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3Example 3 Document Files from Any Directory\fR +.PP +In this case, it does not matter what the current directory is\&. Run the \f3javadoc\fR command with the absolute path (or path relative to the current directory) to the source files you want to document\&. +.sp +.nf +\f3javadoc \-d /home/html /home/src/java/awt/Button\&.java\fP +.fi +.nf +\f3/home/src/java/awt/Graphics*\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Document Packages and Classes + +You can document entire packages and individual classes at the same time\&. Here is an example that mixes two of the previous examples\&. You can use the \f3-sourcepath\fR option for the path to the packages but not for the path to the individual classes\&. +.sp +.nf +\f3javadoc \-d /home/html \-sourcepath /home/src java\&.awt\fP +.fi +.nf +\f3/home/src/java/applet/Applet\&.java\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS REAL-WORLD\ EXAMPLES +The following command-line and \f3makefile\fR versions of the \f3javadoc\fR command run on the Java platform APIs\&. It uses 180 MB of memory to generate the documentation for the 1500 (approximately) public and protected classes in the Java SE 1\&.2\&. Both examples use absolute paths in the option arguments, so that the same \f3javadoc\fR command can be run from any directory\&. +.PP +Command-Line Example + +The following command might be too long for some shells\&. You can use a command-line argument file (or write a shell script) to overcome this limitation\&. +.PP +In the example, \f3packages\fR is the name of a file that contains the packages to process, such as \f3java\&.applet\fR\f3java\&.lang\fR\&. None of the options should contain any newline characters between the single quotation marks\&. For example, if you copy and paste this example, then delete the newline characters from the \f3-bottom\fR option\&. +.sp +.nf +\f3javadoc \-sourcepath /java/jdk/src/share/classes \e\fP +.fi +.nf +\f3\-overview /java/jdk/src/share/classes/overview\&.html \e\fP +.fi +.nf +\f3\-d /java/jdk/build/api \e\fP +.fi +.nf +\f3\-use \e\fP +.fi +.nf +\f3\-splitIndex \e\fP +.fi +.nf +\f3\-windowtitle \&'Java Platform, Standard Edition 7 API Specification\&' \e\fP +.fi +.nf +\f3\-doctitle \&'Java Platform, Standard Edition 7 API Specification\&' \e\fP +.fi +.nf +\f3\-header \&'<b>Java\(tm SE 7</b>\&' \e\fP +.fi +.nf +\f3\-bottom \&'<font size="\-1">\fP +.fi +.nf +\f3<a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fP +.fi +.nf +\f3Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&.<br/>\fP +.fi +.nf +\f3Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fP +.fi +.nf +\f3Other names may be trademarks of their respective owners\&.</font>\&' \e\fP +.fi +.nf +\f3\-group "Core Packages" "java\&.*:com\&.sun\&.java\&.*:org\&.omg\&.*" \e\fP +.fi +.nf +\f3\-group "Extension Packages" "javax\&.*" \e\fP +.fi +.nf +\f3\-J\-Xmx180m \e \fP +.fi +.nf +\f3@packages\fP +.fi +.nf +\f3\fP +.fi +.sp + +.PP +Programmatic Interface + +The Javadoc Access API enables the user to invoke the Javadoc tool directly from a Java application without executing a new process\&. +.PP +For example, the following statements are equivalent to the command \f3javadoc -d /home/html -sourcepath /home/src -subpackages java -exclude java\&.net:java\&.lang com\&.example\fR: +.sp +.nf +\f3import javax\&.tools\&.DocumentationTool;\fP +.fi +.nf +\f3import javax\&.tools\&.ToolProvider;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3public class JavaAccessSample{\fP +.fi +.nf +\f3 public static void main(String[] args){\fP +.fi +.nf +\f3 DocumentationTool javadoc = ToolProvider\&.getSystemDocumentationTool();\fP +.fi +.nf +\f3 int rc = javadoc\&.run( null, null, null,\fP +.fi +.nf +\f3 "\-d", "/home/html",\fP +.fi +.nf +\f3 "\-sourcepath", "home/src",\fP +.fi +.nf +\f3 "\-subpackages", "java",\fP +.fi +.nf +\f3 "\-exclude", "java\&.net:java\&.lang",\fP +.fi +.nf +\f3 "com\&.example");\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3\fP +.fi +.sp +The first three arguments of the \f3run\fR method specify input, standard output, and standard error streams\&. \f3Null\fR is the default value for \f3System\&.in\fR, \f3System\&.out\fR, and \f3System\&.err\fR, respectively\&. +.SS THE\ MAKEFILE\ EXAMPLE +This is an example of a GNU \f3makefile\fR\&. Single quotation marks surround \f3makefile\fR arguments\&. For an example of a Windows \f3makefile\fR, see the \f3makefiles\fR section of the Javadoc FAQ at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137483\&.html#makefiles +.sp +.nf +\f3javadoc \-sourcepath $(SRCDIR) \e /* Sets path for source files */\fP +.fi +.nf +\f3 \-overview $(SRCDIR)/overview\&.html \e /* Sets file for overview text */\fP +.fi +.nf +\f3 \-d /java/jdk/build/api \e /* Sets destination directory */\fP +.fi +.nf +\f3 \-use \e /* Adds "Use" files */\fP +.fi +.nf +\f3 \-splitIndex \e /* Splits index A\-Z */\fP +.fi +.nf +\f3 \-windowtitle $(WINDOWTITLE) \e /* Adds a window title */\fP +.fi +.nf +\f3 \-doctitle $(DOCTITLE) \e /* Adds a doc title */\fP +.fi +.nf +\f3 \-header $(HEADER) \e /* Adds running header text */\fP +.fi +.nf +\f3 \-bottom $(BOTTOM) \e /* Adds text at bottom */\fP +.fi +.nf +\f3 \-group $(GROUPCORE) \e /* 1st subhead on overview page */\fP +.fi +.nf +\f3 \-group $(GROUPEXT) \e /* 2nd subhead on overview page */\fP +.fi +.nf +\f3 \-J\-Xmx180m \e /* Sets memory to 180MB */\fP +.fi +.nf +\f3 java\&.lang java\&.lang\&.reflect \e /* Sets packages to document */\fP +.fi +.nf +\f3 java\&.util java\&.io java\&.net \e\fP +.fi +.nf +\f3 java\&.applet\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3WINDOWTITLE = \&'Java\(tm SE 7 API Specification\&'\fP +.fi +.nf +\f3DOCTITLE = \&'Java\(tm Platform Standard Edition 7 API Specification\&'\fP +.fi +.nf +\f3HEADER = \&'<b>Java\(tm SE 7</font>\&'\fP +.fi +.nf +\f3BOTTOM = \&'<font size="\-1">\fP +.fi +.nf +\f3 <a href="http://bugreport\&.sun\&.com/bugreport/">Submit a bug or feature</a><br/>\fP +.fi +.nf +\f3 Copyright © 1993, 2011, Oracle and/or its affiliates\&. All rights reserved\&.<br/>\fP +.fi +.nf +\f3 Oracle is a registered trademark of Oracle Corporation and/or its affiliates\&.\fP +.fi +.nf +\f3 Other names may be trademarks of their respective owners\&.</font>\&'\fP +.fi +.nf +\f3GROUPCORE = \&'"Core Packages" "java\&.*:com\&.sun\&.java\&.*:org\&.omg\&.*"\&'\fP +.fi +.nf +\f3GROUPEXT = \&'"Extension Packages" "javax\&.*"\&'\fP +.fi +.nf +\f3SRCDIR = \&'/java/jdk/1\&.7\&.0/src/share/classes\&'\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS NOTES +.TP 0.2i +\(bu +If you omit the \f3-windowtitle\fR option, then the \f3javadoc\fR command copies the document title to the window title\&. The \f3-windowtitle\fR option text is similar to the the \f3-doctitle\fR option, but without HTML tags to prevent those tags from appearing as raw text in the window title\&. +.TP 0.2i +\(bu +If you omit the \f3-footer\fR option, then the \f3javadoc\fR command copies the header text to the footer\&. +.TP 0.2i +\(bu +Other important options you might want to use, but were not needed in the previous example, are the \f3-classpath\fR and \f3-link\fR options\&. +.SH GENERAL\ TROUBLESHOOTING +.TP 0.2i +\(bu +The \f3javadoc\fR command reads only files that contain valid class names\&. If the \f3javadoc\fR command is not correctly reading the contents of a file, then verify that the class names are valid\&. See Process Source Files\&. +.TP 0.2i +\(bu +See the Javadoc FAQ for information about common bugs and for troubleshooting tips at http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137483\&.html +.SH ERRORS\ AND\ WARNINGS +Error and warning messages contain the file name and line number to the declaration line rather than to the particular line in the documentation comment\&. +.PP +For example, this message \f3error: cannot read: Class1\&.java\fR means that the \f3javadoc\fR command is trying to load \f3Class1\&.jav\fR\f3a\fR in the current directory\&. The class name is shown with its path (absolute or relative)\&. +.SH ENVIRONMENT +.TP +CLASSPATH +\f3CLASSPATH\fR is the environment variable that provides the path that the \f3javadoc\fR command uses to find user class files\&. This environment variable is overridden by the \f3-classpath\fR option\&. Separate directories with a semicolon for Windows or a colon for Oracle Solaris\&. + +\fIWindows example\fR: \f3\&.;C:\eclasses;C:\ehome\ejava\eclasses\fR + +\fIOracle Solaris example\fR: \f3\&.:/home/classes:/usr/local/java/classes\fR\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +javac(1) +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +jdb(1) +.TP 0.2i +\(bu +javah(1) +.TP 0.2i +\(bu +javap(1) +.SH RELATED\ DOCUMENTS +.TP 0.2i +\(bu +Javadoc Technology at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javadoc/index\&.html +.TP 0.2i +\(bu +How Classes Are Found http://docs\&.oracle\&.com/javase/8/docs/technotes/tools/findingclasses\&.html +.TP 0.2i +\(bu +How to Write Doc Comments for the Javadoc Tool http://www\&.oracle\&.com/technetwork/java/javase/documentation/index-137868\&.html +.TP 0.2i +\(bu +URL Memo, Uniform Resource Locators http://www\&.ietf\&.org/rfc/rfc1738\&.txt +.TP 0.2i +\(bu +HTML standard, HTML Document Representation (4197265 and 4137321) http://www\&.w3\&.org/TR/REC-html40/charset\&.html#h-5\&.2\&.2 +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javafxpackager.1 b/jdk-1.8.0.281/man/man1/javafxpackager.1 new file mode 100755 index 0000000..3e9bf8e --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javafxpackager.1 @@ -0,0 +1,1107 @@ +'\" t +.\" Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javafxpackager +.\" Language: English +.\" Date: 03 March 2015 +.\" SectDesc: Java Deployment Tools +.\" Software: JDK 8 +.\" Arch: Generic +.\" Part Number: E38209-04 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javafxpackager" "1" "03 March 2015" "JDK 8" "Java Deployment Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +javafxpackager \- \fBNote:\fR This tool has been renamed \fBjavapackager\fR\&. The \fBjavafxpackager\&.exe\fR file may be removed in a future release\&. Please update your scripts to use \fBjavapackager\fR\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager\fR \fIcommand\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommand\fR +.RS 4 +The task that should be performed\&. +.RE +.PP +options +.RS 4 +One or more options for the command separated by spaces\&. +.RE +.SH "COMMANDS" +.PP +You can specify one of the following commands\&. After the command, specify the options for it\&. +.PP +\-createbss +.RS 4 +Converts CSS files into binary form\&. +.RE +.PP +\-createjar +.RS 4 +Produces a JAR archive according to other parameters\&. +.RE +.PP +\-deploy +.RS 4 +Assembles the application package for redistribution\&. By default, the deploy task generates the base application package, but it can also generate a self\-contained application package if requested\&. +.RE +.PP +\-makeall +.RS 4 +Performs compilation, +\fBcreatejar\fR, and +\fBdeploy\fR +steps as one call, with most arguments predefined, and attempts to generate all applicable self\-contained application packages\&. The source files must be located in a folder called +\fBsrc\fR, and the resulting files (JAR, JNLP, HTML, and self\-contained application packages) are put in a folder called +\fBdist\fR\&. This command can only be configured in a minimal way and is as automated as possible\&. +.RE +.PP +\-signjar +.RS 4 +Signs JAR file(s) with a provided certificate\&. +.RE +.SH "OPTIONS FOR THE CREATEBSS COMMAND" +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to package\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.SH "OPTIONS FOR THE CREATEJAR COMMAND" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +Qualified name of the application class to be executed\&. +.RE +.PP +\-argument \fIarg\fR +.RS 4 +An unnamed argument to be inserted into the JNLP file as an +\fB<fx:argument>\fR +element\&. +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +List of dependent JAR file names\&. +.RE +.PP +\-manifestAttrs \fImanifest\-attributes\fR +.RS 4 +List of names and values for additional manifest attributes\&. Syntax: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1=value1,name2=value2,name3=value3"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-nocss2bin +.RS 4 +The packager will not convert CSS files to binary form before copying to JAR\&. +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +Name (without the extension) of the file that will be generated\&. +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +A properties file with default named application parameters\&. +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +Qualified name of the JavaFX preloader class to be executed\&. Use this option only for JavaFX applications\&. Do not use for Java applications, including headless applications\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to package\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.SH "OPTIONS FOR THE DEPLOY COMMAND" +.PP +\-allpermissions +.RS 4 +If present, the application will require all security permissions in the JNLP file\&. +.RE +.PP +\-appclass \fIapp\-class\fR +.RS 4 +Qualified name of the application class to be executed\&. +.RE +.PP +\-argument \fIarg\fR +.RS 4 +An unnamed argument to be inserted into an +\fB<fx:argument>\fR +element in the JNLP file\&. +.RE +.PP +\-B\fIbundler\-argument=value\fR +.RS 4 +Provides information to the bundler that is used to package a self\-contained application\&. See Arguments for Self\-Contained Application Bundlers for information on the arguments for each bundler\&. +.RE +.PP +\-callbacks +.RS 4 +Specifies user callback methods in generated HTML\&. The format is the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1:value1,name2:value2,\&.\&.\&."\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-description \fIdescription\fR +.RS 4 +Description of the application\&. +.RE +.PP +\-embedCertificates +.RS 4 +If present, the certificates will be embedded in the JNLP file\&. +.RE +.PP +\-embedjnlp +.RS 4 +If present, the JNLP file will be embedded in the HTML document\&. +.RE +.PP +\-height \fIheight\fR +.RS 4 +Height of the application\&. +.RE +.PP +\-htmlparamfile \fIfile\fR +.RS 4 +Properties file with parameters for the resulting application when it is run in the browser\&. +.RE +.PP +\-isExtension +.RS 4 +If present, the +\fBsrcfiles\fR +are treated as extensions\&. +.RE +.PP +\-name \fIname\fR +.RS 4 +Name of the application\&. +.RE +.PP +\-native \fItype\fR +.RS 4 +Generate self\-contained application bundles (if possible)\&. Use the +\fB\-B\fR +option to provide arguments to the bundlers being used\&. If +\fItype\fR +is specified, then only a bundle of this type is created\&. If no type is specified, +\fBall\fR +is used\&. +.sp +The following values are valid for +\fItype\fR: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBall\fR: Runs all of the installers for the platform on which it is running, and creates a disk image for the application\&. This value is used if +\fItype\fR +is not specified\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBinstaller\fR: Runs all of the installers for the platform on which it is running\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBimage\fR: Creates a disk image for the application\&. On OS X, the image is the +\fB\&.app\fR +file\&. On Linux, the image is the directory that gets installed\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdmg\fR: Generates a DMG file for OS X\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpkg\fR: Generates a +\fB\&.pkg\fR +package for OS X\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmac\&.appStore\fR: Generates a package for the Mac App Store\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBrpm\fR: Generates an RPM package for Linux\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdeb\fR: Generates a Debian package for Linux\&. +.RE +.RE +.PP +\-nosign +.RS 4 +If present, the bundle generated for self\-contained applications is not signed by the bundler\&. The default for bundlers that support signing is to sign the bundle if signing keys are properly configured\&. This attribute is ignored by bundlers that do not support signing\&. At the time of the 8u40 release of the JDK, only OS X bundlers support signing\&. +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +Name (without the extension) of the file that will be generated\&. +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +Properties file with default named application parameters\&. +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +Qualified name of the JavaFX preloader class to be executed\&. Use this option only for JavaFX applications\&. Do not use for Java applications, including headless applications\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to package\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.PP +\-templateId +.RS 4 +Application ID of the application for template processing\&. +.RE +.PP +\-templateInFilename +.RS 4 +Name of the HTML template file\&. Placeholders are in the following form: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#XXXX\&.YYYY(APPID)#\fR + +.fi +.if n \{\ +.RE +.\} +Where APPID is the identifier of an application and XXX is one of following: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.URL\fR +.sp +Location of dtjava\&.js in the Deployment Toolkit\&. By default, the location is +.sp +http://java\&.com/js/dtjava\&.js +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.CODE\fR +.sp +Script element to include dtjava\&.js of the Deployment Toolkit\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.DYNAMIC\fR +.sp +Code to embed the application into a given placeholder\&. It is expected that the code will be wrapped in the +\fBfunction()\fR +method\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.ONLOAD\fR +.sp +All the code needed to embed the application into a web page using the +\fBonload\fR +hook (except inclusion of dtjava\&.js)\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.LAUNCH\&.CODE\fR +.sp +Code needed to launch the application\&. It is expected that the code will be wrapped in the +\fBfunction()\fR +method\&. +.RE +.RE +.PP +\-templateOutFilename +.RS 4 +Name of the HTML file that will be generated from the template\&. +.RE +.PP +\-title \fItitle\fR +.RS 4 +Title of the application\&. +.RE +.PP +\-vendor \fIvendor\fR +.RS 4 +Vendor of the application\&. +.RE +.PP +\-width \fIwidth\fR +.RS 4 +Width of the application\&. +.RE +.PP +\-updatemode \fIupdate\-mode\fR +.RS 4 +Sets the update mode for the JNLP file\&. +.RE +.SH "OPTIONS FOR THE MAKEALL COMMAND" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +Qualified name of the application class to be executed\&. +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +List of dependent JAR file names\&. +.RE +.PP +\-height \fIheight\fR +.RS 4 +Height of the application\&. +.RE +.PP +\-name \fIname\fR +.RS 4 +Name of the application\&. +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +Qualified name of the JavaFX preloader class to be executed\&. Use this option only for JavaFX applications\&. Do not use for Java applications, including headless applications\&. +.RE +.PP +\-width \fIwidth\fR +.RS 4 +Width of the application\&. +.RE +.SH "OPTIONS FOR THE SIGNJAR COMMAND" +.PP +\-alias +.RS 4 +Alias for the key\&. +.RE +.PP +\-keyPass +.RS 4 +Password for recovering the key\&. +.RE +.PP +\-keyStore \fIfile\fR +.RS 4 +Keystore file name\&. +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to be signed\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.PP +\-storePass +.RS 4 +Password to check integrity of the keystore or unlock the keystore +.RE +.PP +\-storeType +.RS 4 +Keystore type\&. The default value is "jks"\&. +.RE +.SH "ARGUMENTS FOR SELF-CONTAINED APPLICATION BUNDLERS" +.PP +The +\fB\-B\fR +option for the +\fB\-deploy\fR +command is used to specify arguments for the bundler that is used to create self\-contained applications\&. Each type of bundler has its own set of arguments\&. +.SS "General Bundler Arguments" +.PP +appVersion=\fIversion\fR +.RS 4 +Version of the application package\&. Some bundlers restrict the format of the version string\&. +.RE +.PP +classPath=\fIpath\fR +.RS 4 +Class path relative to the assembled application directory\&. The path is typically extracted from the JAR file manifest, and does not need to be set if you are using the other +\fBjavapackager\fR +commands\&. +.RE +.PP +icon=\fIpath\fR +.RS 4 +Location of the default icon to be used for launchers and other assists\&. For OS X, the format must be +\fB\&.icns\fR\&. For Linux, the format must be +\fB\&.png\fR\&. +.RE +.PP +identifier=\fIvalue\fR +.RS 4 +Default value that is used for other platform\-specific values such as +\fBmac\&.CFBundleIdentifier\fR\&. Reverse DNS order is recommended, for example, +\fBcom\&.example\&.application\&.my\-application\fR\&. +.RE +.PP +jvmOptions=\fIoption\fR +.RS 4 +Option to be passed to the JVM when the application is run\&. Any option that is valid for the +\fBjava\fR +command can be used\&. To pass more than one option, use multiple instances of the +\fB\-B\fR +option, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmOptions=\-Xmx128m \-BjvmOptions=\-Xms128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +jvmProperties=\fIproperty\fR=\fIvalue\fR +.RS 4 +Java System Property to be passed to the VM when the application is run\&. Any property that is valid for the +\fB\-D\fR +option of the +\fBjava\fR +command can be used\&. Specify both the property name and the value for the property\&. To pass more than one property, use multiple instances of the +\fB\-B\fR +option, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmProperties=apiUserName=example \-BjvmProperties=apiKey=abcdef1234567890\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +mainJar=\fIfilename\fR +.RS 4 +Name of the JAR file that contains the main class for the application\&. The file name is typically extracted from the JAR file manifest, and does not need to be set if you are using the other +\fBjavapackager\fR +commands\&. +.RE +.PP +preferencesID=\fInode\fR +.RS 4 +Preferences node to examine to check for JVM options that the user can override\&. The node specified is passed to the application at run time as the option +\fB\-Dapp\&.preferences\&.id\fR\&. This argument is used with the +\fBuserJVMOptions\fR +argument\&. +.RE +.PP +runtime=\fIpath\fR +.RS 4 +Location of the JRE or JDK to include in the package bundle\&. Provide a file path to the root folder of the JDK or JRE\&. To use the system default JRE, do not provide a path, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Bruntime=\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +userJvmOptions=\fIoption\fR=\fIvalue\fR +.RS 4 +JVM options that users can override\&. Any option that is valid for the +\fBjava\fR +command can be used\&. Specify both the option name and the value for the option\&. To pass more than one option, use multiple instances of the +\fB\-B\fR +option, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BuserJvmOptions=\-Xmx=128m \-BuserJvmOptions=\-Xms=128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SS "OS X Application Bundler Arguments" +.PP +mac\&.category=\fIcategory\fR +.RS 4 +Category for the application\&. The category must be in the list of categories found on the Apple Developer website\&. +.RE +.PP +mac\&.CFBundleIdentifier=\fIvalue\fR +.RS 4 +Value stored in the info plist for +\fBCFBundleIdentifier\fR\&. This value must be globally unique and contain only letters, numbers, dots, and dashes\&. Reverse DNS order is recommended, for example, +\fBcom\&.example\&.application\&.my\-application\fR\&. +.RE +.PP +mac\&.CFBundleName=\fIname\fR +.RS 4 +Name of the application as it appears on the OS X Menu Bar\&. A name of less than 16 characters is recommended\&. The default is the name attribute\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.PP +mac\&.signing\-key\-developer\-id\-app=\fIkey\fR +.RS 4 +Name of the signing key used for Devleloper ID or Gatekeeper signing\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.bundle\-id\-signing\-prefix=\fIprefix\fR +.RS 4 +Prefix that is applied to the signed binary when binaries that lack plists or existing signatures are found inside the bundles\&. +.RE +.SS "OS X DMG (Disk Image) Bundler Arguments" +.PP +The OS X DMG installer shows the license file specified by +\fBlicenseFile\fR, if provided, before allowing the disk image to be mounted\&. +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +systemWide=\fIboolean\fR +.RS 4 +Flag that indicates which drag\-to\-install target to use\&. Set to +\fBtrue\fR +to show the Applications folder\&. Set to +\fBfalse\fR +to show the Desktop folder\&. The default is +\fBtrue\fR\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.PP +mac\&.dmg\&.simple=\fIboolean\fR +.RS 4 +Flag that indicates if DMG customization steps that depend on executing AppleScript code are skipped\&. Set to +\fBtrue\fR +to skip the steps\&. When set to +\fBtrue\fR, the disk window does not have a background image, and the icons are not moved into place\&. If the +\fBsystemWide\fR +argument is also set to +\fBtrue\fR, then a symbolic link to the root Applications folder is added to the DMG file\&. If the +\fBsystemWide\fR +argument is set to +\fBfalse\fR, then only the application is added to the DMG file, no link to the desktop is added\&. +.RE +.SS "OS X PKG Bundler Arguments" +.PP +The OS X PKG installer presents a wizard and shows the license file specified by +\fBlicenseFile\fR +as one of the pages in the wizard\&. The user must accept the terms before installing the application\&. +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +mac\&.signing\-key\-developer\-id\-installer=\fIkey\fR +.RS 4 +Name of the signing key used for Developer ID or Gatekeeper signing\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.SS "Mac App Store Bundler Arguments" +.PP +mac\&.app\-store\-entitlements=\fIpath\fR +.RS 4 +Location of the file that contains the entitlements that the application operates under\&. The file must be in the format specified by Apple\&. The path to the file can be specified in absolute terms, or relative to the invocation of +\fBjavapackager\fR\&. If no entitlements are specified, then the application operates in a sandbox that is stricter than the typical applet sandbox, and access to network sockets and all files is prevented\&. +.RE +.PP +mac\&.signing\-key\-app=\fIkey\fR +.RS 4 +Name of the application signing key for the Mac App Store\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.signing\-key\-pkg=\fIkey\fR +.RS 4 +Name of the installer signing key for the Mac App Store\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.SS "Linux Debian Bundler Arguments" +.PP +The license file specified by +\fBlicenseFile\fR +is not presented to the user in all cases, but the file is included in the application metadata\&. +.PP +category=\fIcategory\fR +.RS 4 +Category for the application\&. See http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.html for examples\&. +.RE +.PP +copyright=\fIstring\fR +.RS 4 +Copyright string for the application\&. This argument is used in the Debian metadata\&. +.RE +.PP +email=\fIaddress\fR +.RS 4 +Email address used in the Debian Maintainer field\&. +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +licenseType=\fItype\fR +.RS 4 +Short name of the license type, such as +\fB\-BlicenseType=Proprietary\fR, or +\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fR\&. +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +Corporation, organization, or individual providing the application\&. This argument is used in the Debian Maintainer field\&. +.RE +.SS "Linux RPM Bundler Arguments" +.PP +category=\fIcategory\fR +.RS 4 +Category for the application\&. See http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.html for examples\&. +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +licenseType=\fItype\fR +.RS 4 +Short name of the license type, such as +\fB\-BlicenseType=Proprietary\fR, or +\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fR\&. +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +Corporation, organization, or individual providing the application\&. +.RE +.SH "DEPRECATED OPTIONS" +.PP +The following options are no longer used by the packaging tool and are ignored if present\&. +.PP +\-runtimeversion \fIversion\fR +.RS 4 +Version of the required JavaFX Runtime\&. Deprecated\&. +.RE +.PP +\-noembedlauncher +.RS 4 +If present, the packager will not add the JavaFX launcher classes to the JAR file\&. Deprecated\&. +.RE +.SH "NOTES" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +A +\fB\-v \fRoption can be used with any task command to enable verbose output\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +When the +\fB\-srcdir\fR +option is allowed in a command, it can be used more than once\&. If the +\fB\-srcfiles\fR +option is specified, the files named in the argument will be looked for in the location specified in the preceding +\fBsrcdir\fR +option\&. If there is no +\fB\-srcdir\fR +preceding +\fB\-srcfiles\fR, the directory from which the +\fBjavapackager\fR +command is executed is used\&. +.RE +.SH "EXAMPLES" +.PP +\fBExample 1 \fRUsing the \-createjar Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-createjar \-appclass package\&.ClassName\fR +\fB \-srcdir classes \-outdir out \-outfile outjar \-v\fR + +.fi +.if n \{\ +.RE +.\} +Packages the contents of the +\fBclasses\fR +directory to +\fBoutjar\&.jar\fR, sets the application class to +\fBpackage\&.ClassName\fR\&. +.RE +.PP +\fBExample 2 \fRUsing the \-deploy Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fR +\fB \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fR + +.fi +.if n \{\ +.RE +.\} +Generates +\fBoutfile\&.jnlp\fR +and the corresponding +\fBoutfile\&.html\fR +files in +\fBoutdir\fR +for application +\fBAppName\fR, which is started by +\fBpackage\&.ClassName\fR +and has dimensions of 34 by 43 pixels\&. +.RE +.PP +\fBExample 3 \fRUsing the \-makeall Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fR +\fB\-height 600\fR + +.fi +.if n \{\ +.RE +.\} +Does all the packaging work including compilation, +\fBcreatejar\fR, and +\fBdeploy\fR\&. +.RE +.PP +\fBExample 4 \fRUsing the \-signjar Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fR +\fB\-alias duke \-keypass **** \-srcdir dist\fR + +.fi +.if n \{\ +.RE +.\} +Signs all of the JAR files in the +\fBdist\fR +directory, attaches a certificate with the specified alias, +\fBkeyStore\fR +and +\fBstorePass\fR, and puts the signed JAR files back into the +\fBdist\fR +directory\&. +.RE +.PP +\fBExample 5 \fRUsing the \-deploy Command with Bundler Arguments +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-native deb \-Bcategory=Education \-BjvmOptions=\-Xmx128m \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB \-BjvmOptions=\-Xms128m \-outdir packages \-outfile BrickBreaker \-srcdir dist \fR +\fB \-srcfiles BrickBreaker\&.jar \-appclass brickbreaker\&.Main \-name BrickBreaker \fR +\fB \-title "BrickBreaker demo"\fR + +.fi +.if n \{\ +.RE +.\} +Generates the native Linux Debian package for running the BrickBreaker application as a self\- contained application\&. +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javah.1 b/jdk-1.8.0.281/man/man1/javah.1 new file mode 100755 index 0000000..d0f9bfe --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javah.1 @@ -0,0 +1,138 @@ +'\" t +.\" Copyright (c) 1994, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Basic Tools +.\" Title: javah.1 +.\" +.if n .pl 99999 +.TH javah 1 "21 November 2013" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +javah \- Generates C header and source files from a Java class\&. +.SH SYNOPSIS +.sp +.nf + +\fBjavah\fR [ \fIoptions\fR ] f\fIully\-qualified\-class\-name \&.\&.\&.\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIfully-qualified-class-name\fR +The fully qualified location of the classes to be converted to C header and source files\&. +.SH DESCRIPTION +The \f3javah\fR command generates C header and source files that are needed to implement native methods\&. The generated header and source files are used by C programs to reference an object\&'s instance variables from native source code\&. The \f3\&.h\fR file contains a \f3struct\fR definition with a layout that parallels the layout of the corresponding class\&. The fields in the \f3struct\fR correspond to instance variables in the class\&. +.PP +The name of the header file and the structure declared within it are derived from the name of the class\&. When the class passed to the \f3javah\fR command is inside a package, the package name is added to the beginning of both the header file name and the structure name\&. Underscores (_) are used as name delimiters\&. +.PP +By default the \f3javah\fR command creates a header file for each class listed on the command line and puts the files in the current directory\&. Use the \f3-stubs\fR option to create source files\&. Use the \f3-o\fR option to concatenate the results for all listed classes into a single file\&. +.PP +The Java Native Interface (JNI) does not require header information or stub files\&. The \f3javah\fR command can still be used to generate native method function prototypes needed for JNI-style native methods\&. The \f3javah\fR command produces JNI-style output by default and places the result in the \f3\&.h\fR file\&. +.SH OPTIONS +.TP +-o \fIoutputfile\fR +.br +Concatenates the resulting header or source files for all the classes listed on the command line into an output file\&. Only one of \f3-o\fR or \f3-d\fR can be used\&. +.TP +-d \fIdirectory\fR +.br +Sets the directory where the \f3javah\fR command saves the header files or the stub files\&. Only one of \f3-d\fR or \f3-o\fR can be used\&. +.TP +-stubs +.br +Causes the \f3javah\fR command to generate C declarations from the Java object file\&. +.TP +-verbose +.br +Indicates verbose output and causes the \f3javah\fR command to print a message to \f3stdout\fR about the status of the generated files\&. +.TP +-help +.br +Prints a help message for \f3javah\fR usage\&. +.TP +-version +.br +Prints \f3javah\fR command release information\&. +.TP +-jni +.br +Causes the \f3javah\fR command to create an output file containing JNI-style native method function prototypes\&. This is the default output; use of \f3-jni\fR is optional\&. +.TP +-classpath \fIpath\fR +.br +Specifies the path the \f3javah\fR command uses to look up classes\&. Overrides the default or the \f3CLASSPATH\fR environment variable when it is set\&. Directories are separated by colons on Oracle Solaris and semicolons on Windows\&. The general format for path is: + +\fIOracle Solaris\fR: + +\&.:\fIyour-path\fR + +Example: \f3\&.:/home/avh/classes:/usr/local/java/classes\fR + +\fIWindows\fR: + +\&.;\fIyour-path\fR + +Example: \f3\&.;C:\eusers\edac\eclasses;C:\etools\ejava\eclasses\fR + +As a special convenience, a class path element that contains a base name of * is considered equivalent to specifying a list of all the files in the directory with the extension \f3\&.jar\fR or \f3\&.JAR\fR\&. + +For example, if directory \f3mydir\fR contains \f3a\&.jar\fR and \f3b\&.JAR\fR, then the class path element \f3mydir/*\fR is expanded to a \f3A\fR\f3\&.jar:b\&.JAR\fR, except that the order of jar files is unspecified\&. All JAR files in the specified directory, including hidden ones, are included in the list\&. A class path entry that consists of * expands to a list of all the JAR files in the current directory\&. The \f3CLASSPATH\fR environment variable, where defined, is similarly expanded\&. Any class path wild card expansion occurs before the Java Virtual Machine (JVM) is started\&. A Java program will never see unexpanded wild cards except by querying the environment\&. For example, by calling \f3System\&.getenv("CLASSPATH")\fR\&. +.TP +-bootclasspath \fIpath\fR +.br +Specifies the path from which to load bootstrap classes\&. By default, the bootstrap classes are the classes that implement the core Java platform located in \f3jre\elib\ert\&.jar\fR and several other JAR files\&. +.TP +-old +.br +Specifies that old JDK 1\&.0-style header files should be generated\&. +.TP +-force +.br +Specifies that output files should always be written\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +javah(1) +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +jdb(1) +.TP 0.2i +\(bu +javap(1) +.TP 0.2i +\(bu +javadoc(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javap.1 b/jdk-1.8.0.281/man/man1/javap.1 new file mode 100755 index 0000000..83698f3 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javap.1 @@ -0,0 +1,372 @@ +'\" t +.\" Copyright (c) 1994, 2014, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javap +.\" Language: English +.\" Date: 8 August 2014 +.\" SectDesc: Basic Tools +.\" Software: JDK 8 +.\" Arch: generic +.\" Part Number: E38209-03 +.\" +.if n .pl 99999 +.TH "javap" "1" "8 August 2014" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +javap \- Disassembles one or more class files\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavap\fR [\fIoptions\fR] \fIclassfile\fR\&.\&.\&. +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +The command\-line options\&. See Options\&. +.RE +.PP +\fIclassfile\fR +.RS 4 +One or more classes separated by spaces to be processed for annotations such as DocFooter\&.class\&. You can specify a class that can be found in the class path, by its file name or with a URL such as +\fBfile:///home/user/myproject/src/DocFooter\&.class\fR\&. +.RE +.SH "DESCRIPTION" +.PP +The +\fBjavap\fR +command disassembles one or more class files\&. The output depends on the options used\&. When no options are used, then the +\fBjavap\fR +command prints the package, protected and public fields, and methods of the classes passed to it\&. The +\fBjavap\fR +command prints its output to +\fBstdout\fR\&. +.SH "OPTIONS" +.PP +\-help +.br +\-\-help +.br +\-? +.RS 4 +Prints a help message for the +\fBjavap\fR +command\&. +.RE +.PP +\-version +.RS 4 +Prints release information\&. +.RE +.PP +\-l +.RS 4 +Prints line and local variable tables\&. +.RE +.PP +\-public +.RS 4 +Shows only public classes and members\&. +.RE +.PP +\-protected +.RS 4 +Shows only protected and public classes and members\&. +.RE +.PP +\-private +.br +\-p +.RS 4 +Shows all classes and members\&. +.RE +.PP +\-J\fIoption\fR +.RS 4 +Passes the specified option to the JVM\&. For example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavap \-J\-version\fR +\fBjavap \-J\-Djava\&.security\&.manager \-J\-Djava\&.security\&.policy=MyPolicy MyClassName\fR + +.fi +.if n \{\ +.RE +.\} +For more information about JVM options, see the command documentation\&. +.RE +.PP +\-s +.RS 4 +Prints internal type signatures\&. +.RE +.PP +\-sysinfo +.RS 4 +Shows system information (path, size, date, MD5 hash) of the class being processed\&. +.RE +.PP +\-constants +.RS 4 +Shows +\fBstatic final\fR +constants\&. +.RE +.PP +\-c +.RS 4 +Prints disassembled code, for example, the instructions that comprise the Java bytecodes, for each of the methods in the class\&. +.RE +.PP +\-verbose +.RS 4 +Prints stack size, number of locals and arguments for methods\&. +.RE +.PP +\-classpath \fIpath\fR +.RS 4 +Specifies the path the +\fBjavap\fR +command uses to look up classes\&. Overrides the default or the +\fBCLASSPATH\fR +environment variable when it is set\&. +.RE +.PP +\-bootclasspath \fIpath\fR +.RS 4 +Specifies the path from which to load bootstrap classes\&. By default, the bootstrap classes are the classes that implement the core Java platform located in +\fBjre/lib/rt\&.jar\fR +and several other JAR files\&. +.RE +.PP +\-extdir \fIdirs\fR +.RS 4 +Overrides the location at which installed extensions are searched for\&. The default location for extensions is the value of +\fBjava\&.ext\&.dirs\fR\&. +.RE +.SH "EXAMPLE" +.PP +Compile the following +\fBDocFooter\fR +class: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBimport java\&.awt\&.*;\fR +\fBimport java\&.applet\&.*;\fR +\fB \fR +\fBpublic class DocFooter extends Applet {\fR +\fB String date;\fR +\fB String email;\fR +\fB \fR +\fB public void init() {\fR +\fB resize(500,100);\fR +\fB date = getParameter("LAST_UPDATED");\fR +\fB email = getParameter("EMAIL");\fR +\fB }\fR +\fB \fR +\fB public void paint(Graphics g) {\fR +\fB g\&.drawString(date + " by ",100, 15);\fR +\fB g\&.drawString(email,290,15);\fR +\fB }\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The output from the +\fBjavap DocFooter\&.class\fR +command yields the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompiled from "DocFooter\&.java"\fR +\fBpublic class DocFooter extends java\&.applet\&.Applet {\fR +\fB java\&.lang\&.String date;\fR +\fB java\&.lang\&.String email;\fR +\fB public DocFooter();\fR +\fB public void init();\fR +\fB public void paint(java\&.awt\&.Graphics);\fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.PP +The output from +\fBjavap \-c DocFooter\&.class\fR +command yields the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBCompiled from "DocFooter\&.java"\fR +\fBpublic class DocFooter extends java\&.applet\&.Applet {\fR +\fB java\&.lang\&.String date;\fR +\fB java\&.lang\&.String email;\fR + +\fB public DocFooter();\fR +\fB Code:\fR +\fB 0: aload_0 \fR +\fB 1: invokespecial #1 // Method\fR +\fBjava/applet/Applet\&."<init>":()V\fR +\fB 4: return \fR + +\fB public void init();\fR +\fB Code:\fR +\fB 0: aload_0 \fR +\fB 1: sipush 500\fR +\fB 4: bipush 100\fR +\fB 6: invokevirtual #2 // Method resize:(II)V\fR +\fB 9: aload_0 \fR +\fB 10: aload_0 \fR +\fB 11: ldc #3 // String LAST_UPDATED\fR +\fB 13: invokevirtual #4 // Method\fR +\fB getParameter:(Ljava/lang/String;)Ljava/lang/String;\fR +\fB 16: putfield #5 // Field date:Ljava/lang/String;\fR +\fB 19: aload_0 \fR +\fB 20: aload_0 \fR +\fB 21: ldc #6 // String EMAIL\fR +\fB 23: invokevirtual #4 // Method\fR +\fB getParameter:(Ljava/lang/String;)Ljava/lang/String;\fR +\fB 26: putfield #7 // Field email:Ljava/lang/String;\fR +\fB 29: return \fR + +\fB public void paint(java\&.awt\&.Graphics);\fR +\fB Code:\fR +\fB 0: aload_1 \fR +\fB 1: new #8 // class java/lang/StringBuilder\fR +\fB 4: dup \fR +\fB 5: invokespecial #9 // Method\fR +\fB java/lang/StringBuilder\&."<init>":()V\fR +\fB 8: aload_0 \fR +\fB 9: getfield #5 // Field date:Ljava/lang/String;\fR +\fB 12: invokevirtual #10 // Method\fR +\fB java/lang/StringBuilder\&.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;\fR +\fB 15: ldc #11 // String by \fR +\fB 17: invokevirtual #10 // Method\fR +\fB java/lang/StringBuilder\&.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;\fR +\fB 20: invokevirtual #12 // Method\fR +\fB java/lang/StringBuilder\&.toString:()Ljava/lang/String;\fR +\fB 23: bipush 100\fR +\fB 25: bipush 15\fR +\fB 27: invokevirtual #13 // Method\fR +\fB java/awt/Graphics\&.drawString:(Ljava/lang/String;II)V\fR +\fB 30: aload_1 \fR +\fB 31: aload_0 \fR +\fB 32: getfield #7 // Field email:Ljava/lang/String;\fR +\fB 35: sipush 290\fR +\fB 38: bipush 15\fR +\fB 40: invokevirtual #13 // Method\fR +\fBjava/awt/Graphics\&.drawString:(Ljava/lang/String;II)V\fR +\fB 43: return \fR +\fB}\fR + +.fi +.if n \{\ +.RE +.\} +.SH "SEE ALSO" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javac(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javadoc(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +javah(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdb(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jdeps(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javapackager.1 b/jdk-1.8.0.281/man/man1/javapackager.1 new file mode 100755 index 0000000..a356d2a --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javapackager.1 @@ -0,0 +1,1107 @@ +'\" t +.\" Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: javapackager +.\" Language: English +.\" Date: 03 March 2015 +.\" SectDesc: Java Deployment Tools +.\" Software: JDK 8 +.\" Arch: Generic +.\" Part Number: E38209-04 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "javapackager" "1" "03 March 2015" "JDK 8" "Java Deployment Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +javapackager \- Performs tasks related to packaging and signing Java and JavaFX applications\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager\fR \fIcommand\fR [\fIoptions\fR] +.fi +.if n \{\ +.RE +.\} +.PP +\fIcommand\fR +.RS 4 +The task that should be performed\&. +.RE +.PP +options +.RS 4 +One or more options for the command separated by spaces\&. +.RE +.SH "COMMANDS" +.PP +You can specify one of the following commands\&. After the command, specify the options for it\&. +.PP +\-createbss +.RS 4 +Converts CSS files into binary form\&. +.RE +.PP +\-createjar +.RS 4 +Produces a JAR archive according to other parameters\&. +.RE +.PP +\-deploy +.RS 4 +Assembles the application package for redistribution\&. By default, the deploy task generates the base application package, but it can also generate a self\-contained application package if requested\&. +.RE +.PP +\-makeall +.RS 4 +Performs compilation, +\fBcreatejar\fR, and +\fBdeploy\fR +steps as one call, with most arguments predefined, and attempts to generate all applicable self\-contained application packages\&. The source files must be located in a folder called +\fBsrc\fR, and the resulting files (JAR, JNLP, HTML, and self\-contained application packages) are put in a folder called +\fBdist\fR\&. This command can only be configured in a minimal way and is as automated as possible\&. +.RE +.PP +\-signjar +.RS 4 +Signs JAR file(s) with a provided certificate\&. +.RE +.SH "OPTIONS FOR THE CREATEBSS COMMAND" +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to package\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.SH "OPTIONS FOR THE CREATEJAR COMMAND" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +Qualified name of the application class to be executed\&. +.RE +.PP +\-argument \fIarg\fR +.RS 4 +An unnamed argument to be inserted into the JNLP file as an +\fB<fx:argument>\fR +element\&. +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +List of dependent JAR file names\&. +.RE +.PP +\-manifestAttrs \fImanifest\-attributes\fR +.RS 4 +List of names and values for additional manifest attributes\&. Syntax: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1=value1,name2=value2,name3=value3"\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-nocss2bin +.RS 4 +The packager will not convert CSS files to binary form before copying to JAR\&. +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +Name (without the extension) of the file that will be generated\&. +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +A properties file with default named application parameters\&. +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +Qualified name of the JavaFX preloader class to be executed\&. Use this option only for JavaFX applications\&. Do not use for Java applications, including headless applications\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to package\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.SH "OPTIONS FOR THE DEPLOY COMMAND" +.PP +\-allpermissions +.RS 4 +If present, the application will require all security permissions in the JNLP file\&. +.RE +.PP +\-appclass \fIapp\-class\fR +.RS 4 +Qualified name of the application class to be executed\&. +.RE +.PP +\-argument \fIarg\fR +.RS 4 +An unnamed argument to be inserted into an +\fB<fx:argument>\fR +element in the JNLP file\&. +.RE +.PP +\-B\fIbundler\-argument=value\fR +.RS 4 +Provides information to the bundler that is used to package a self\-contained application\&. See Arguments for Self\-Contained Application Bundlers for information on the arguments for each bundler\&. +.RE +.PP +\-callbacks +.RS 4 +Specifies user callback methods in generated HTML\&. The format is the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB"name1:value1,name2:value2,\&.\&.\&."\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\-description \fIdescription\fR +.RS 4 +Description of the application\&. +.RE +.PP +\-embedCertificates +.RS 4 +If present, the certificates will be embedded in the JNLP file\&. +.RE +.PP +\-embedjnlp +.RS 4 +If present, the JNLP file will be embedded in the HTML document\&. +.RE +.PP +\-height \fIheight\fR +.RS 4 +Height of the application\&. +.RE +.PP +\-htmlparamfile \fIfile\fR +.RS 4 +Properties file with parameters for the resulting application when it is run in the browser\&. +.RE +.PP +\-isExtension +.RS 4 +If present, the +\fBsrcfiles\fR +are treated as extensions\&. +.RE +.PP +\-name \fIname\fR +.RS 4 +Name of the application\&. +.RE +.PP +\-native \fItype\fR +.RS 4 +Generate self\-contained application bundles (if possible)\&. Use the +\fB\-B\fR +option to provide arguments to the bundlers being used\&. If +\fItype\fR +is specified, then only a bundle of this type is created\&. If no type is specified, +\fBall\fR +is used\&. +.sp +The following values are valid for +\fItype\fR: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBall\fR: Runs all of the installers for the platform on which it is running, and creates a disk image for the application\&. This value is used if +\fItype\fR +is not specified\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBinstaller\fR: Runs all of the installers for the platform on which it is running\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBimage\fR: Creates a disk image for the application\&. On OS X, the image is the +\fB\&.app\fR +file\&. On Linux, the image is the directory that gets installed\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdmg\fR: Generates a DMG file for OS X\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBpkg\fR: Generates a +\fB\&.pkg\fR +package for OS X\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmac\&.appStore\fR: Generates a package for the Mac App Store\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBrpm\fR: Generates an RPM package for Linux\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBdeb\fR: Generates a Debian package for Linux\&. +.RE +.RE +.PP +\-nosign +.RS 4 +If present, the bundle generated for self\-contained applications is not signed by the bundler\&. The default for bundlers that support signing is to sign the bundle if signing keys are properly configured\&. This attribute is ignored by bundlers that do not support signing\&. At the time of the 8u40 release of the JDK, only OS X bundlers support signing\&. +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-outfile \fIfilename\fR +.RS 4 +Name (without the extension) of the file that will be generated\&. +.RE +.PP +\-paramfile \fIfile\fR +.RS 4 +Properties file with default named application parameters\&. +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +Qualified name of the JavaFX preloader class to be executed\&. Use this option only for JavaFX applications\&. Do not use for Java applications, including headless applications\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to package\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.PP +\-templateId +.RS 4 +Application ID of the application for template processing\&. +.RE +.PP +\-templateInFilename +.RS 4 +Name of the HTML template file\&. Placeholders are in the following form: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB#XXXX\&.YYYY(APPID)#\fR + +.fi +.if n \{\ +.RE +.\} +Where APPID is the identifier of an application and XXX is one of following: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.URL\fR +.sp +Location of dtjava\&.js in the Deployment Toolkit\&. By default, the location is +.sp +http://java\&.com/js/dtjava\&.js +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.SCRIPT\&.CODE\fR +.sp +Script element to include dtjava\&.js of the Deployment Toolkit\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.DYNAMIC\fR +.sp +Code to embed the application into a given placeholder\&. It is expected that the code will be wrapped in the +\fBfunction()\fR +method\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.EMBED\&.CODE\&.ONLOAD\fR +.sp +All the code needed to embed the application into a web page using the +\fBonload\fR +hook (except inclusion of dtjava\&.js)\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBDT\&.LAUNCH\&.CODE\fR +.sp +Code needed to launch the application\&. It is expected that the code will be wrapped in the +\fBfunction()\fR +method\&. +.RE +.RE +.PP +\-templateOutFilename +.RS 4 +Name of the HTML file that will be generated from the template\&. +.RE +.PP +\-title \fItitle\fR +.RS 4 +Title of the application\&. +.RE +.PP +\-vendor \fIvendor\fR +.RS 4 +Vendor of the application\&. +.RE +.PP +\-width \fIwidth\fR +.RS 4 +Width of the application\&. +.RE +.PP +\-updatemode \fIupdate\-mode\fR +.RS 4 +Sets the update mode for the JNLP file\&. +.RE +.SH "OPTIONS FOR THE MAKEALL COMMAND" +.PP +\-appclass \fIapp\-class\fR +.RS 4 +Qualified name of the application class to be executed\&. +.RE +.PP +\-classpath \fIfiles\fR +.RS 4 +List of dependent JAR file names\&. +.RE +.PP +\-height \fIheight\fR +.RS 4 +Height of the application\&. +.RE +.PP +\-name \fIname\fR +.RS 4 +Name of the application\&. +.RE +.PP +\-preloader \fIpreloader\-class\fR +.RS 4 +Qualified name of the JavaFX preloader class to be executed\&. Use this option only for JavaFX applications\&. Do not use for Java applications, including headless applications\&. +.RE +.PP +\-width \fIwidth\fR +.RS 4 +Width of the application\&. +.RE +.SH "OPTIONS FOR THE SIGNJAR COMMAND" +.PP +\-alias +.RS 4 +Alias for the key\&. +.RE +.PP +\-keyPass +.RS 4 +Password for recovering the key\&. +.RE +.PP +\-keyStore \fIfile\fR +.RS 4 +Keystore file name\&. +.RE +.PP +\-outdir \fIdir\fR +.RS 4 +Name of the directory that will receive generated output files\&. +.RE +.PP +\-srcdir \fIdir\fR +.RS 4 +Base directory of the files to be signed\&. +.RE +.PP +\-srcfiles \fIfiles\fR +.RS 4 +List of files in the directory specified by the +\fB\-srcdir\fR +option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&. +.RE +.PP +\-storePass +.RS 4 +Password to check integrity of the keystore or unlock the keystore +.RE +.PP +\-storeType +.RS 4 +Keystore type\&. The default value is "jks"\&. +.RE +.SH "ARGUMENTS FOR SELF-CONTAINED APPLICATION BUNDLERS" +.PP +The +\fB\-B\fR +option for the +\fB\-deploy\fR +command is used to specify arguments for the bundler that is used to create self\-contained applications\&. Each type of bundler has its own set of arguments\&. +.SS "General Bundler Arguments" +.PP +appVersion=\fIversion\fR +.RS 4 +Version of the application package\&. Some bundlers restrict the format of the version string\&. +.RE +.PP +classPath=\fIpath\fR +.RS 4 +Class path relative to the assembled application directory\&. The path is typically extracted from the JAR file manifest, and does not need to be set if you are using the other +\fBjavapackager\fR +commands\&. +.RE +.PP +icon=\fIpath\fR +.RS 4 +Location of the default icon to be used for launchers and other assists\&. For OS X, the format must be +\fB\&.icns\fR\&. For Linux, the format must be +\fB\&.png\fR\&. +.RE +.PP +identifier=\fIvalue\fR +.RS 4 +Default value that is used for other platform\-specific values such as +\fBmac\&.CFBundleIdentifier\fR\&. Reverse DNS order is recommended, for example, +\fBcom\&.example\&.application\&.my\-application\fR\&. +.RE +.PP +jvmOptions=\fIoption\fR +.RS 4 +Option to be passed to the JVM when the application is run\&. Any option that is valid for the +\fBjava\fR +command can be used\&. To pass more than one option, use multiple instances of the +\fB\-B\fR +option, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmOptions=\-Xmx128m \-BjvmOptions=\-Xms128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +jvmProperties=\fIproperty\fR=\fIvalue\fR +.RS 4 +Java System Property to be passed to the VM when the application is run\&. Any property that is valid for the +\fB\-D\fR +option of the +\fBjava\fR +command can be used\&. Specify both the property name and the value for the property\&. To pass more than one property, use multiple instances of the +\fB\-B\fR +option, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BjvmProperties=apiUserName=example \-BjvmProperties=apiKey=abcdef1234567890\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +mainJar=\fIfilename\fR +.RS 4 +Name of the JAR file that contains the main class for the application\&. The file name is typically extracted from the JAR file manifest, and does not need to be set if you are using the other +\fBjavapackager\fR +commands\&. +.RE +.PP +preferencesID=\fInode\fR +.RS 4 +Preferences node to examine to check for JVM options that the user can override\&. The node specified is passed to the application at run time as the option +\fB\-Dapp\&.preferences\&.id\fR\&. This argument is used with the +\fBuserJVMOptions\fR +argument\&. +.RE +.PP +runtime=\fIpath\fR +.RS 4 +Location of the JRE or JDK to include in the package bundle\&. Provide a file path to the root folder of the JDK or JRE\&. To use the system default JRE, do not provide a path, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-Bruntime=\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +userJvmOptions=\fIoption\fR=\fIvalue\fR +.RS 4 +JVM options that users can override\&. Any option that is valid for the +\fBjava\fR +command can be used\&. Specify both the option name and the value for the option\&. To pass more than one option, use multiple instances of the +\fB\-B\fR +option, as shown in the following example: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\-BuserJvmOptions=\-Xmx=128m \-BuserJvmOptions=\-Xms=128m\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SS "OS X Application Bundler Arguments" +.PP +mac\&.category=\fIcategory\fR +.RS 4 +Category for the application\&. The category must be in the list of categories found on the Apple Developer website\&. +.RE +.PP +mac\&.CFBundleIdentifier=\fIvalue\fR +.RS 4 +Value stored in the info plist for +\fBCFBundleIdentifier\fR\&. This value must be globally unique and contain only letters, numbers, dots, and dashes\&. Reverse DNS order is recommended, for example, +\fBcom\&.example\&.application\&.my\-application\fR\&. +.RE +.PP +mac\&.CFBundleName=\fIname\fR +.RS 4 +Name of the application as it appears on the OS X Menu Bar\&. A name of less than 16 characters is recommended\&. The default is the name attribute\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.PP +mac\&.signing\-key\-developer\-id\-app=\fIkey\fR +.RS 4 +Name of the signing key used for Devleloper ID or Gatekeeper signing\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.bundle\-id\-signing\-prefix=\fIprefix\fR +.RS 4 +Prefix that is applied to the signed binary when binaries that lack plists or existing signatures are found inside the bundles\&. +.RE +.SS "OS X DMG (Disk Image) Bundler Arguments" +.PP +The OS X DMG installer shows the license file specified by +\fBlicenseFile\fR, if provided, before allowing the disk image to be mounted\&. +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +systemWide=\fIboolean\fR +.RS 4 +Flag that indicates which drag\-to\-install target to use\&. Set to +\fBtrue\fR +to show the Applications folder\&. Set to +\fBfalse\fR +to show the Desktop folder\&. The default is +\fBtrue\fR\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.PP +mac\&.dmg\&.simple=\fIboolean\fR +.RS 4 +Flag that indicates if DMG customization steps that depend on executing AppleScript code are skipped\&. Set to +\fBtrue\fR +to skip the steps\&. When set to +\fBtrue\fR, the disk window does not have a background image, and the icons are not moved into place\&. If the +\fBsystemWide\fR +argument is also set to +\fBtrue\fR, then a symbolic link to the root Applications folder is added to the DMG file\&. If the +\fBsystemWide\fR +argument is set to +\fBfalse\fR, then only the application is added to the DMG file, no link to the desktop is added\&. +.RE +.SS "OS X PKG Bundler Arguments" +.PP +The OS X PKG installer presents a wizard and shows the license file specified by +\fBlicenseFile\fR +as one of the pages in the wizard\&. The user must accept the terms before installing the application\&. +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +mac\&.signing\-key\-developer\-id\-installer=\fIkey\fR +.RS 4 +Name of the signing key used for Developer ID or Gatekeeper signing\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. +.RE +.SS "Mac App Store Bundler Arguments" +.PP +mac\&.app\-store\-entitlements=\fIpath\fR +.RS 4 +Location of the file that contains the entitlements that the application operates under\&. The file must be in the format specified by Apple\&. The path to the file can be specified in absolute terms, or relative to the invocation of +\fBjavapackager\fR\&. If no entitlements are specified, then the application operates in a sandbox that is stricter than the typical applet sandbox, and access to network sockets and all files is prevented\&. +.RE +.PP +mac\&.signing\-key\-app=\fIkey\fR +.RS 4 +Name of the application signing key for the Mac App Store\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.signing\-key\-pkg=\fIkey\fR +.RS 4 +Name of the installer signing key for the Mac App Store\&. If you imported a standard key from the Apple Developer Website, then that key is used by default\&. If no key can be identified, then the application is not signed\&. +.RE +.PP +mac\&.CFBundleVersion=\fIvalue\fR +.RS 4 +Version number for the application, used internally\&. The value must be at least one integer and no more than three integers separated by periods (\&.) for example, 1\&.3 or 2\&.0\&.1\&. The value can be different than the value for the +\fBappVersion\fR +argument\&. If the +\fBappVersion\fR +argument is specified with a valid value and the +\fBmac\&.CFBundleVersion\fR +argument is not specified, then the +\fBappVersion\fR +value is used\&. If neither argument is specified, +\fB100\fR +is used as the version number\&. If this version is an upgrade for an existing application, the value must be greater than previous version number\&. +.RE +.SS "Linux Debian Bundler Arguments" +.PP +The license file specified by +\fBlicenseFile\fR +is not presented to the user in all cases, but the file is included in the application metadata\&. +.PP +category=\fIcategory\fR +.RS 4 +Category for the application\&. See http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.html for examples\&. +.RE +.PP +copyright=\fIstring\fR +.RS 4 +Copyright string for the application\&. This argument is used in the Debian metadata\&. +.RE +.PP +email=\fIaddress\fR +.RS 4 +Email address used in the Debian Maintainer field\&. +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +licenseType=\fItype\fR +.RS 4 +Short name of the license type, such as +\fB\-BlicenseType=Proprietary\fR, or +\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fR\&. +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +Corporation, organization, or individual providing the application\&. This argument is used in the Debian Maintainer field\&. +.RE +.SS "Linux RPM Bundler Arguments" +.PP +category=\fIcategory\fR +.RS 4 +Category for the application\&. See http://standards\&.freedesktop\&.org/menu\-spec/latest/apa\&.html for examples\&. +.RE +.PP +licenseFile=\fIpath\fR +.RS 4 +Location of the End User License Agreement (EULA) to be presented or recorded by the bundler\&. The path is relative to the packaged application resources, for example, +\fB\-BlicenseFile=COPYING\fR\&. +.RE +.PP +licenseType=\fItype\fR +.RS 4 +Short name of the license type, such as +\fB\-BlicenseType=Proprietary\fR, or +\fB"\-BlicenseType=GPL v2 + Classpath Exception"\fR\&. +.RE +.PP +vendor=\fIvalue\fR +.RS 4 +Corporation, organization, or individual providing the application\&. +.RE +.SH "DEPRECATED OPTIONS" +.PP +The following options are no longer used by the packaging tool and are ignored if present\&. +.PP +\-runtimeversion \fIversion\fR +.RS 4 +Version of the required JavaFX Runtime\&. Deprecated\&. +.RE +.PP +\-noembedlauncher +.RS 4 +If present, the packager will not add the JavaFX launcher classes to the JAR file\&. Deprecated\&. +.RE +.SH "NOTES" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +A +\fB\-v \fRoption can be used with any task command to enable verbose output\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +When the +\fB\-srcdir\fR +option is allowed in a command, it can be used more than once\&. If the +\fB\-srcfiles\fR +option is specified, the files named in the argument will be looked for in the location specified in the preceding +\fBsrcdir\fR +option\&. If there is no +\fB\-srcdir\fR +preceding +\fB\-srcfiles\fR, the directory from which the +\fBjavapackager\fR +command is executed is used\&. +.RE +.SH "EXAMPLES" +.PP +\fBExample 1 \fRUsing the \-createjar Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-createjar \-appclass package\&.ClassName\fR +\fB \-srcdir classes \-outdir out \-outfile outjar \-v\fR + +.fi +.if n \{\ +.RE +.\} +Packages the contents of the +\fBclasses\fR +directory to +\fBoutjar\&.jar\fR, sets the application class to +\fBpackage\&.ClassName\fR\&. +.RE +.PP +\fBExample 2 \fRUsing the \-deploy Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fR +\fB \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fR + +.fi +.if n \{\ +.RE +.\} +Generates +\fBoutfile\&.jnlp\fR +and the corresponding +\fBoutfile\&.html\fR +files in +\fBoutdir\fR +for application +\fBAppName\fR, which is started by +\fBpackage\&.ClassName\fR +and has dimensions of 34 by 43 pixels\&. +.RE +.PP +\fBExample 3 \fRUsing the \-makeall Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fR +\fB\-height 600\fR + +.fi +.if n \{\ +.RE +.\} +Does all the packaging work including compilation, +\fBcreatejar\fR, and +\fBdeploy\fR\&. +.RE +.PP +\fBExample 4 \fRUsing the \-signjar Command +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fR +\fB\-alias duke \-keypass **** \-srcdir dist\fR + +.fi +.if n \{\ +.RE +.\} +Signs all of the JAR files in the +\fBdist\fR +directory, attaches a certificate with the specified alias, +\fBkeyStore\fR +and +\fBstorePass\fR, and puts the signed JAR files back into the +\fBdist\fR +directory\&. +.RE +.PP +\fBExample 5 \fRUsing the \-deploy Command with Bundler Arguments +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjavapackager \-deploy \-native deb \-Bcategory=Education \-BjvmOptions=\-Xmx128m \fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB \-BjvmOptions=\-Xms128m \-outdir packages \-outfile BrickBreaker \-srcdir dist \fR +\fB \-srcfiles BrickBreaker\&.jar \-appclass brickbreaker\&.Main \-name BrickBreaker \fR +\fB \-title "BrickBreaker demo"\fR + +.fi +.if n \{\ +.RE +.\} +Generates the native Linux Debian package for running the BrickBreaker application as a self\- contained application\&. +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/javaws.1 b/jdk-1.8.0.281/man/man1/javaws.1 new file mode 100755 index 0000000..99f842b --- /dev/null +++ b/jdk-1.8.0.281/man/man1/javaws.1 @@ -0,0 +1,157 @@ +'\" t +.\" Copyright (c) 2003, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Web Start Tools +.\" Title: javaws.1 +.\" +.if n .pl 99999 +.TH javaws 1 "21 November 2013" "JDK 8" "Java Web Start Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +javaws \- Starts Java Web Start\&. +.SH SYNOPSIS +.sp +.nf + +\fBjavaws\fR [ \fIrun\-options\fR ] \fIjnlp\fR +.fi +.nf + +\fBjavaws\fR [ \fIcontrol\-options\fR ] +.fi +.sp +.TP +\fIrun-options\fR +Command-line \f3run-options\fR\&. The \f3run-options\fR can be in any order\&. See Run-Options\&. +.TP +\fIjnlp\fR +Either the path of or the Uniform Resource Locator (URL) of the Java Network Launching Protocol (JNLP) file\&. +.TP +\fIcontrol-options\fR +Command-line \f3control-options\fR\&. The \f3control-options\fR can be in any order\&. See Control-Options\&. +.SH DESCRIPTION +\fINote:\fR The \f3javaws\fR command is not available on Oracle Solaris\&. +.PP +The \f3javaws\fR command starts Java Web Start, which is the reference implementation of the JNLP\&. Java Web Start starts Java applications and applets hosted on a network\&. +.PP +If a JNLP file is specified, then the \f3javaws\fR command starts the Java application or applet specified in the JNLP file\&. +.PP +The \f3javaws\fR launcher has a set of options that are supported in the current release\&. However, the options may be removed in a future release\&. +.SH RUN-OPTIONS +.TP +-offline +.br +Runs Java Web Start in offline mode\&. +.TP +-Xnosplash +.br +Does not display the initial splash screen\&. +.TP +-open \fIarguments\fR +.br +When specified, this option replaces the arguments in the JNLP file with \f3-open\fR\f3arguments\fR\&. +.TP +-print \fIarguments\fR +.br +When specified, this option replaces the arguments in the JNLP file with \f3-print\fR\f3arguments\fR\&. +.TP +-online +.br +Uses online mode\&. This is the default behavior\&. +.TP +-wait +.br +The \f3javaws\fR process does not exit until the application exits\&. This option does not function as described on Windows platforms\&. +.TP +-verbose +.br +Displays additional output\&. +.TP +-J\fIoption\fR +.br +Passes option to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.TP +-system +.br +Runs the application from the system cache only\&. +.SH CONTROL-OPTIONS +.TP +-viewer +.br +Shows the cache viewer in the Java Control Panel\&. +.TP +-clearcache +.br +Removes all non-installed applications from the cache\&. +.TP +-userConfig \fIproperty-name\fR +.br +Clears the specified deployment property\&. +.TP +-userConfig \fIproperty-name property-value\fR +.br +Sets the specified deployment property to the specified value\&. +.TP +-uninstall +.br +Removes all applications from the cache\&. +.TP +-uninstall \fIjnlp\fR +.br +Removes the application from the cache\&. +.TP +-print \fIimport-options\fRjnlp +.br +Imports the application to the cache\&. +.SH IMPORT-OPTIONS +.TP +-silent +.br +Imports silently (with no user interface)\&. +.TP +-system +.br +Imports application to the system cache\&. +.TP +-codebase \fIurl\fR +.br +Retrieves resources from the specified codebase\&. +.TP +-shortcut +.br +Installs shortcuts if the user allows a prompt\&. This option has no effect unless the \f3-silent\fR option is also used\&. +.TP +-association +.br +Installs associations if the user allows a prompt\&. This option has no effect unless the \f3-silent\fR option is also used\&. +.SH FILES +For information about the user and system cache and deployment\&.properties files, see Deployment Configuration File and Properties at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/deployment/deployment-guide/properties\&.html +.SH SEE\ ALSO +.TP 0.2i +\(bu +Java Web Start at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javaws/index\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jcmd.1 b/jdk-1.8.0.281/man/man1/jcmd.1 new file mode 100755 index 0000000..f8f2908 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jcmd.1 @@ -0,0 +1,216 @@ +'\" t +.\" Copyright (c) 2012, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jcmd +.\" Language: English +.\" Date: 03 March 2015 +.\" SectDesc: Troubleshooting Tools +.\" Software: JDK 8 +.\" Arch: generic +.\" Part Number: E38209-04 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jcmd" "1" "03 March 2015" "JDK 8" "Troubleshooting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +jcmd \- Sends diagnostic command requests to a running Java Virtual Machine (JVM)\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR [\fB\-l\fR|\fB\-h\fR|\fB\-help\fR] +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fBPerfCounter\&.print\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fB\-f\fR \fIfilename\fR +.fi +.if n \{\ +.RE +.\} +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjcmd\fR \fIpid\fR|\fImain\-class\fR \fIcommand\fR[ \fIarguments\fR] +.fi +.if n \{\ +.RE +.\} +.SH "DESCRIPTION" +.PP +The +\fBjcmd\fR +utility is used to send diagnostic command requests to the JVM\&. It must be used on the same machine on which the JVM is running, and have the same effective user and group identifiers that were used to launch the JVM\&. +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +.PP +To invoke diagnostic commands from a remote machine or with different identifiers, you can use the +\fBcom\&.sun\&.management\&.DiagnosticCommandMBean\fR +interface\&. For more information about the +\fBDiagnosticCommandMBean\fR +interface, see the API documentation at http://docs\&.oracle\&.com/javase/8/docs/jre/api/management/extension/com/sun/management/DiagnosticCommandMBean\&.html +T} +.TE +.sp 1 +.sp .5v +.RE +.PP +If you run +\fBjcmd\fR +without arguments or with the +\fB\-l\fR +option, it prints the list of running Java process identifiers with the main class and command\-line arguments that were used to launch the process\&. Running +\fBjcmd\fR +with the +\fB\-h\fR +or +\fB\-help\fR +option prints the tool\(cqs help message\&. +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br +.TS +allbox tab(:); +l. +T{ +.PP +The +\fBjcmd\fR +utility can be used 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 http://docs\&.oracle\&.com/javacomponents/jmc\&.htm +T} +.TE +.sp 1 +.sp .5v +.RE +.PP +If you specify the processes identifier (\fIpid\fR) or the main class (\fImain\-class\fR) as the first argument, +\fBjcmd\fR +sends the diagnostic command request to the Java process with the specified identifier or to all Java processes with the specified name of the main class\&. You can also send the diagnostic command request to all available Java processes by specifying +\fB0\fR +as the process identifier\&. Use one of the following as the diagnostic command request: +.PP +Perfcounter\&.print +.RS 4 +Prints the performance counters available for the specified Java process\&. The list of performance counters might vary with the Java process\&. +.RE +.PP +\-f \fIfilename\fR +.RS 4 +The name of the file from which to read diagnostic commands and send them to the specified Java process\&. Used only with the +\fB\-f\fR +option\&. Each command in the file must be written on a single line\&. Lines starting with a number sign (\fB#\fR) are ignored\&. Processing of the file ends when all lines have been read or when a line containing the +\fBstop\fR +keyword is read\&. +.RE +.PP +\fIcommand\fR [\fIarguments\fR] +.RS 4 +The command to be sent to the specified Java process\&. The list of available diagnostic commands for a given process can be obtained by sending the +\fBhelp\fR +command to this process\&. Each diagnostic command has its own set of arguments\&. To see the description, syntax, and a list of available arguments for a command, use the name of the command as the argument for the +\fBhelp\fR +command\&. +.sp +\fBNote:\fR +If any arguments contain spaces, you must surround them with single or double quotation marks (\fB\*(Aq\fR +or +\fB"\fR)\&. In addition, you must escape single or double quotation marks with a backslash (\fB\e\fR) to prevent the operating system shell from processing quotation marks\&. Alternatively, you can surround these arguments with single quotation marks and then with double quotation marks (or with double quotation marks and then with single quotation marks)\&. +.RE +.SH "OPTIONS" +.PP +Options are mutually exclusive\&. +.PP +\-f \fIfilename\fR +.RS 4 +Reads commands from the specified file\&. This option can be used only if you specify the process identifier or the main class as the first argument\&. Each command in the file must be written on a single line\&. Lines starting with a number sign (\fB#\fR) are ignored\&. Processing of the file ends when all lines have been read or when a line containing the +\fBstop\fR +keyword is read\&. +.RE +.PP +\-h +.br +\-help +.RS 4 +Prints a help message\&. +.RE +.PP +\-l +.RS 4 +Prints the list of running Java processes identifiers with the main class and command\-line arguments\&. +.RE +.SH "SEE ALSO" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jconsole.1 b/jdk-1.8.0.281/man/man1/jconsole.1 new file mode 100755 index 0000000..ddd1f15 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jconsole.1 @@ -0,0 +1,92 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Troubleshooting, Profiling, Monitoring and Management Tools +.\" Title: jconsole.1 +.\" +.if n .pl 99999 +.TH jconsole 1 "21 November 2013" "JDK 8" "Java Troubleshooting, Profiling, Monitoring and Management Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jconsole \- Starts a graphical console that lets you monitor and manage Java applications\&. +.SH SYNOPSIS +.sp +.nf + +\fBjconsole\fR [ \fIoptions\fR ] [ connection \&.\&.\&. ] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +connection = \fIpid\fR | \fIhost\fR:\fIport\fR | \fIjmxURL\fR +The \f3pid\fR value is the process ID of a local Java Virtual Machine (JVM)\&. The JVM must be running with the same user ID as the user ID running the \f3jconsole\fR command\&.The \f3host:port\fR values are the name of the host system on which the JVM is running, and the port number specified by the system property \f3com\&.sun\&.management\&.jmxremote\&.port\fR when the JVM was started\&.The \f3jmxUrl\fR value is the address of the JMX agent to be connected to as described in JMXServiceURL\&. + +For more information about the \f3connection\fR parameter, see Monitoring and Management Using JMX Technology at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/agent\&.html + +See also the \f3JMXServiceURL\fR class description at http://docs\&.oracle\&.com/javase/8/docs/api/javax/management/remote/JMXServiceURL\&.html +.SH DESCRIPTION +The \f3jconsole\fR command starts a graphical console tool that lets you monitor and manage Java applications and virtual machines on a local or remote machine\&. +.PP +On Windows, the \f3jconsole\fR command does not associate with a console window\&. It does, however, display a dialog box with error information when the \f3jconsole\fR command fails\&. +.SH OPTIONS +.TP +-interval\fI=n\fR +.br +Sets the update interval to \fIn\fR seconds (default is 4 seconds)\&. +.TP +-notile +.br +Does not tile windows initially (for two or more connections)\&. +.TP +-pluginpath \fIplugins\fR +.br +Specifies a list of directories or JAR files to be searched for \f3JConsole\fR plug-ins\&. The \fIplugins\fR path should contain a provider-configuration file named \f3META-INF/services/com\&.sun\&.tools\&.jconsole\&.JConsolePlugin\fR that contains one line for each plug-in\&. The line specifies the fully qualified class name of the class implementing the \f3com\&.sun\&.tools\&.jconsole\&.JConsolePlugin\fR class\&. +.TP +-version +.br +Displays release information and exits\&. +.TP +-help +.br +Displays a help message\&. +.TP +-J\fIflag\fR +.br +Passes \f3flag\fR to the JVM on which the \f3jconsole\fR command is run\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +Using JConsole at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/jconsole\&.html +.TP 0.2i +\(bu +Monitoring and Management Using JMX Technology at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/management/agent\&.html +.TP 0.2i +\(bu +The \f3JMXServiceURL\fR class description at http://docs\&.oracle\&.com/javase/8/docs/api/javax/management/remote/JMXServiceURL\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jdb.1 b/jdk-1.8.0.281/man/man1/jdb.1 new file mode 100755 index 0000000..efa6be5 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jdb.1 @@ -0,0 +1,250 @@ +'\" t +.\" Copyright (c) 1995, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Basic Tools +.\" Title: jdb.1 +.\" +.if n .pl 99999 +.TH jdb 1 "21 November 2013" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jdb \- Finds and fixes bugs in Java platform programs\&. +.SH SYNOPSIS +.sp +.nf + +\fBjdb\fR [\fIoptions\fR] [\fIclassname\fR] [\fIarguments\fR] +.fi +.sp +.TP +\fIoptions\fR +Command-line options\&. See Options\&. +.TP +\fIclass\fRname +Name of the main class to debug\&. +.TP +\fIarguments\fR +Arguments passed to the \f3main()\fR method of the class\&. +.SH DESCRIPTION +The Java Debugger (JDB) is a simple command-line debugger for Java classes\&. The \f3jdb\fR command and its options call the JDB\&. The \f3jdb\fR command demonstrates the Java Platform Debugger Architecture (JDBA) and provides inspection and debugging of a local or remote Java Virtual Machine (JVM)\&. See Java Platform Debugger Architecture (JDBA) at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jpda/index\&.html +.SS START\ A\ JDB\ SESSION +There are many ways to start a JDB session\&. The most frequently used way is to have JDB launch a new JVM with the main class of the application to be debugged\&. Do this by substituting the \f3jdb\fR command for the \f3java\fR command in the command line\&. For example, if your application\&'s main class is \f3MyClass\fR, then use the following command to debug it under JDB: +.sp +.nf +\f3jdb MyClass\fP +.fi +.nf +\f3\fP +.fi +.sp +When started this way, the \f3jdb\fR command calls a second JVM with the specified parameters, loads the specified class, and stops the JVM before executing that class\&'s first instruction\&. +.PP +Another way to use the \f3jdb\fR command is by attaching it to a JVM that is already running\&. Syntax for starting a JVM to which the \f3jdb\fR command attaches when the JVM is running is as follows\&. This loads in-process debugging libraries and specifies the kind of connection to be made\&. +.sp +.nf +\f3java \-agentlib:jdwp=transport=dt_socket,server=y,suspend=n MyClass\fP +.fi +.nf +\f3\fP +.fi +.sp +You can then attach the \f3jdb\fR command to the JVM with the following command: +.sp +.nf +\f3jdb \-attach 8000\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3MyClass\fR argument is not specified in the \f3jdb\fR command line in this case because the \f3jdb\fR command is connecting to an existing JVM instead of launching a new JVM\&. +.PP +There are many other ways to connect the debugger to a JVM, and all of them are supported by the \f3jdb\fR command\&. The Java Platform Debugger Architecture has additional documentation on these connection options\&. +.SS BASIC\ JDB\ COMMANDS +The following is a list of the basic \f3jdb\fR commands\&. The JDB supports other commands that you can list with the \f3-help\fR option\&. +.TP +help or ? +The \f3help\fR or \f3?\fR commands display the list of recognized commands with a brief description\&. +.TP +run +After you start JDB and set breakpoints, you can use the \f3run\fR command to execute the debugged application\&. The \f3run\fR command is available only when the \f3jdb\fR command starts the debugged application as opposed to attaching to an existing JVM\&. +.TP +cont +Continues execution of the debugged application after a breakpoint, exception, or step\&. +.TP +print +Displays Java objects and primitive values\&. For variables or fields of primitive types, the actual value is printed\&. For objects, a short description is printed\&. See the dump command to find out how to get more information about an object\&. + +\fINote:\fR To display local variables, the containing class must have been compiled with the \f3javac -g\fR option\&. + +The \f3print\fR command supports many simple Java expressions including those with method invocations, for example: +.sp +.nf +\f3print MyClass\&.myStaticField\fP +.fi +.nf +\f3print myObj\&.myInstanceField\fP +.fi +.nf +\f3print i + j + k (i, j, k are primities and either fields or local variables)\fP +.fi +.nf +\f3print myObj\&.myMethod() (if myMethod returns a non\-null)\fP +.fi +.nf +\f3print new java\&.lang\&.String("Hello")\&.length()\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +dump +For primitive values, the \f3dump\fR command is identical to the \f3print\fR command\&. For objects, the \f3dump\fR command prints the current value of each field defined in the object\&. Static and instance fields are included\&. The \f3dump\fR command supports the same set of expressions as the \f3print\fR command\&. +.TP +threads +List the threads that are currently running\&. For each thread, its name and current status are printed and an index that can be used in other commands\&. In this example, the thread index is 4, the thread is an instance of \f3java\&.lang\&.Thread\fR, the thread name is \f3main\fR, and it is currently running\&. +.sp +.nf +\f34\&. (java\&.lang\&.Thread)0x1 main running\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +thread +Select a thread to be the current thread\&. Many \f3jdb\fR commands are based on the setting of the current thread\&. The thread is specified with the thread index described in the threads command\&. +.TP +where +The \f3where\fR command with no arguments dumps the stack of the current thread\&. The \f3where\fR\f3all\fR command dumps the stack of all threads in the current thread group\&. The \f3where\fR\f3threadindex\fR command dumps the stack of the specified thread\&. + +If the current thread is suspended either through an event such as a breakpoint or through the \f3suspend\fR command, then local variables and fields can be displayed with the \f3print\fR and \f3dump\fR commands\&. The \f3up\fR and \f3down\fR commands select which stack frame is the current stack frame\&. +.SS BREAKPOINTS +Breakpoints can be set in JDB at line numbers or at the first instruction of a method, for example: +.TP 0.2i +\(bu +The command \f3stop at MyClass:22\fR sets a breakpoint at the first instruction for line 22 of the source file containing \f3MyClass\fR\&. +.TP 0.2i +\(bu +The command \f3stop in java\&.lang\&.String\&.length\fR sets a breakpoint at the beginning of the method \f3java\&.lang\&.String\&.length\fR\&. +.TP 0.2i +\(bu +The command \f3stop in MyClass\&.<clinit>\fR uses \f3<clinit>\fR to identify the static initialization code for \f3MyClass\fR\&. +.PP +When a method is overloaded, you must also specify its argument types so that the proper method can be selected for a breakpoint\&. For example, \f3MyClass\&.myMethod(int,java\&.lang\&.String)\fR or \f3MyClass\&.myMethod()\fR\&. +.PP +The \f3clear\fR command removes breakpoints using the following syntax: \f3clear MyClass:45\fR\&. Using the \f3clear\fR or \f3stop\fR command with no argument displays a list of all breakpoints currently set\&. The \f3cont\fR command continues execution\&. +.SS STEPPING +The \f3step\fR command advances execution to the next line whether it is in the current stack frame or a called method\&. The \f3next\fR command advances execution to the next line in the current stack frame\&. +.SS EXCEPTIONS +When an exception occurs for which there is not a \f3catch\fR statement anywhere in the throwing thread\&'s call stack, the JVM typically prints an exception trace and exits\&. When running under JDB, however, control returns to JDB at the offending throw\&. You can then use the \f3jdb\fR command to diagnose the cause of the exception\&. +.PP +Use the \f3catch\fR command to cause the debugged application to stop at other thrown exceptions, for example: \f3catch java\&.io\&.FileNotFoundException\fR or \f3catch\fR\f3mypackage\&.BigTroubleException\fR\&. Any exception that is an instance of the specified class or subclass stops the application at the point where it is thrown\&. +.PP +The \f3ignore\fR command negates the effect of an earlier \f3catch\fR command\&. The \f3ignore\fR command does not cause the debugged JVM to ignore specific exceptions, but only to ignore the debugger\&. +.SH OPTIONS +When you use the \f3jdb\fR command instead of the \f3java\fR command on the command line, the \f3jdb\fR command accepts many of the same options as the \f3java\fR command, including \f3-D\fR, \f3-classpath\fR, and \f3-X\fR options\&. The following list contains additional options that are accepted by the \f3jdb\fR command\&. +.PP +Other options are supported to provide alternate mechanisms for connecting the debugger to the JVM it is to debug\&. For additional documentation about these connection alternatives, see Java Platform Debugger Architecture (JPDA) at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/jpda/index\&.html +.TP +-help +.br +Displays a help message\&. +.TP +-sourcepath \fIdir1:dir2: \&. \&. \&.\fR +.br +Uses the specified path to search for source files in the specified path\&. If this option is not specified, then use the default path of dot (\&.)\&. +.TP +-attach \fIaddress\fR +.br +Attaches the debugger to a running JVM with the default connection mechanism\&. +.TP +-listen \fIaddress\fR +.br +Waits for a running JVM to connect to the specified address with a standard connector\&. +.TP +-launch +.br +Starts the debugged application immediately upon startup of JDB\&. The \f3-launch\fR option removes the need for the \f3run\fR command\&. The debugged application is launched and then stopped just before the initial application class is loaded\&. At that point, you can set any necessary breakpoints and use the \f3cont\fR command to continue execution\&. +.TP +-listconnectors +.br +List the connectors available in this JVM\&. +.TP +-connect connector-name:\fIname1=value1\fR +.br +Connects to the target JVM with the named connector and listed argument values\&. +.TP +-dbgtrace [\fIflags\fR] +.br +Prints information for debugging the \f3jdb\fR command\&. +.TP +-tclient +.br +Runs the application in the Java HotSpot VM client\&. +.TP +-tserver +.br +Runs the application in the Java HotSpot VM server\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the JVM, where option is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH OPTIONS\ FORWARDED\ TO\ THE\ DEBUGGER\ PROCESS +.TP +-v -verbose[:\fIclass\fR|gc|jni] +.br +Turns on verbose mode\&. +.TP +-D\fIname\fR=\fIvalue\fR +.br +Sets a system property\&. +.TP +-classpath \fIdir\fR +.br +Lists directories separated by colons in which to look for classes\&. +.TP +-X\fIoption\fR +.br +Nonstandard target JVM option\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +javac(1) +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +javah(1) +.TP 0.2i +\(bu +javap(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jdeps.1 b/jdk-1.8.0.281/man/man1/jdeps.1 new file mode 100755 index 0000000..54ecb1e --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jdeps.1 @@ -0,0 +1,517 @@ +'\" t +.\" Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Basic Tools +.\" Title: jdeps.1 +.\" +.if n .pl 99999 +.TH jdeps 1 "21 November 2013" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jdeps \- Java class dependency analyzer\&. +.SH SYNOPSIS +.sp +.nf + +\fBjdeps\fR [\fIoptions\fR] \fIclasses\fR \&.\&.\&. +.fi +.sp +.TP +\fIoptions\fR +Command-line options\&. See Options\&. +.TP +\fIclasses\fR +Name of the classes to analyze\&. You can specify a class that can be found in the class path, by its file name, a directory, or a JAR file\&. +.SH DESCRIPTION +The \fI\fR\f3jdeps\fR command shows the package-level or class-level dependencies of Java class files\&. The input class can be a path name to a \f3\&.class\fR file, a directory, a JAR file, or it can be a fully qualified class name to analyze all class files\&. The options determine the output\&. By default, \f3jdeps\fR outputs the dependencies to the system output\&. It can generate the dependencies in DOT language (see the \f3-dotoutput\fR option)\&. +.SH OPTIONS +.TP +-dotoutput <\fIdir\fR> +.br +Destination directory for DOT file output\&. If specified, \f3jdeps\fR will generate one dot file per each analyzed archive named <\fIarchive-file-name\fR>\&.dot listing the dependencies, and also a summary file named summary\&.dot listing the dependencies among the archives\&. +.TP +-s, -summary +.br +Prints dependency summary only\&. +.TP +-v, -verbose +.br +Prints all class-level dependencies\&. +.TP +-verbose:package +.br +Prints package-level dependencies excluding dependencies within the same archive\&. +.TP +-verbose:class +.br +Prints class-level dependencies excluding dependencies within the same archive\&. +.TP +-cp <\fIpath\fR>, -classpath <\fIpath\fR> +.br +Specifies where to find class files\&. + +See also Setting the Class Path\&. +.TP +-p <\fIpkg name\fR>, -package <\fIpkg name\fR> +.br +Finds dependencies in the specified package\&. You can specify this option multiple times for different packages\&. The \f3-p\fR and \f3-e\fR options are mutually exclusive\&. +.TP +-e <\fIregex\fR>, -regex <\fIregex\fR> +.br +Finds dependencies in packages matching the specified regular expression pattern\&. The \f3-p\fR and \f3-e\fR options are mutually exclusive\&. +.TP +-include <\fIregex\fR> +.br +Restricts analysis to classes matching pattern\&. This option filters the list of classes to be analyzed\&. It can be used together with \f3-p\fR and \f3-e\fR which apply pattern to the dependencies\&. +.TP +-jdkinternals +.br +Finds class-level dependences in JDK internal APIs\&. By default, it analyzes all classes specified in the \f3-classpath\fR option and in input files unless you specified the \f3-include\fR option\&. You cannot use this option with the \f3-p\fR, \f3-e\fR, and \f3-s\fR options\&. + +\fIWarning\fR: JDK internal APIs may not be accessible in upcoming releases\&. +.TP +-P, -profile +.br +Shows profile or the file containing a package\&. +.TP +-apionly +.br +Restricts analysis to APIs, for example, dependences from the signature of \f3public\fR and \f3protected\fR members of public classes including field type, method parameter types, returned type, and checked exception types\&. +.TP +-R, -recursive +.br +Recursively traverses all dependencies\&. +.TP +-version +.br +Prints version information\&. +.TP +-h, -?, -help +.br +Prints help message for \f3jdeps\fR\&. +.SH EXAMPLES +Analyzing the dependencies of Notepad\&.jar\&. +.sp +.nf +\f3$ jdeps demo/jfc/Notepad/Notepad\&.jar\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3demo/jfc/Notepad/Notepad\&.jar \-> /usr/java/jre/lib/rt\&.jar\fP +.fi +.nf +\f3 <unnamed> (Notepad\&.jar)\fP +.fi +.nf +\f3 \-> java\&.awt \fP +.fi +.nf +\f3 \-> java\&.awt\&.event \fP +.fi +.nf +\f3 \-> java\&.beans \fP +.fi +.nf +\f3 \-> java\&.io \fP +.fi +.nf +\f3 \-> java\&.lang \fP +.fi +.nf +\f3 \-> java\&.net \fP +.fi +.nf +\f3 \-> java\&.util \fP +.fi +.nf +\f3 \-> java\&.util\&.logging \fP +.fi +.nf +\f3 \-> javax\&.swing \fP +.fi +.nf +\f3 \-> javax\&.swing\&.border \fP +.fi +.nf +\f3 \-> javax\&.swing\&.event \fP +.fi +.nf +\f3 \-> javax\&.swing\&.text \fP +.fi +.nf +\f3 \-> javax\&.swing\&.tree \fP +.fi +.nf +\f3 \-> javax\&.swing\&.undo \fP +.fi +.nf +\f3\fP +.fi +.sp +Use -P or -profile option to show on which profile that Notepad depends\&. +.sp +.nf +\f3$ jdeps \-profile demo/jfc/Notepad/Notepad\&.jar \fP +.fi +.nf +\f3demo/jfc/Notepad/Notepad\&.jar \-> /usr/java/jre/lib/rt\&.jar (Full JRE)\fP +.fi +.nf +\f3 <unnamed> (Notepad\&.jar)\fP +.fi +.nf +\f3 \-> java\&.awt Full JRE\fP +.fi +.nf +\f3 \-> java\&.awt\&.event Full JRE\fP +.fi +.nf +\f3 \-> java\&.beans Full JRE\fP +.fi +.nf +\f3 \-> java\&.io compact1\fP +.fi +.nf +\f3 \-> java\&.lang compact1\fP +.fi +.nf +\f3 \-> java\&.net compact1\fP +.fi +.nf +\f3 \-> java\&.util compact1\fP +.fi +.nf +\f3 \-> java\&.util\&.logging compact1\fP +.fi +.nf +\f3 \-> javax\&.swing Full JRE\fP +.fi +.nf +\f3 \-> javax\&.swing\&.border Full JRE\fP +.fi +.nf +\f3 \-> javax\&.swing\&.event Full JRE\fP +.fi +.nf +\f3 \-> javax\&.swing\&.text Full JRE\fP +.fi +.nf +\f3 \-> javax\&.swing\&.tree Full JRE\fP +.fi +.nf +\f3 \-> javax\&.swing\&.undo Full JRE\fP +.fi +.nf +\f3\fP +.fi +.sp +Analyzing the immediate dependencies of a specific class in a given classpath, for example the \f3com\&.sun\&.tools\&.jdeps\&.Main\fR class in the tools\&.jar file\&. +.sp +.nf +\f3$ jdeps \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fP +.fi +.nf +\f3lib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fP +.fi +.nf +\f3 com\&.sun\&.tools\&.jdeps (tools\&.jar)\fP +.fi +.nf +\f3 \-> java\&.io \fP +.fi +.nf +\f3 \-> java\&.lang \fP +.fi +.nf +\f3\fP +.fi +.sp +Use the \f3-verbose:class\fR option to find class-level dependencies or use the \f3-v\fR or \f3-verbose\fR option to include dependencies from the same JAR file\&. +.sp +.nf +\f3$ jdeps \-verbose:class \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3lib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fP +.fi +.nf +\f3 com\&.sun\&.tools\&.jdeps\&.Main (tools\&.jar)\fP +.fi +.nf +\f3 \-> java\&.io\&.PrintWriter \fP +.fi +.nf +\f3 \-> java\&.lang\&.Exception \fP +.fi +.nf +\f3 \-> java\&.lang\&.Object \fP +.fi +.nf +\f3 \-> java\&.lang\&.String \fP +.fi +.nf +\f3 \-> java\&.lang\&.System \fP +.fi +.nf +\f3\fP +.fi +.sp +Use the \f3-R\fR or \f3-recursive\fR option to analyze the transitive dependencies of the \f3com\&.sun\&.tools\&.jdeps\&.Main\fR class\&. +.sp +.nf +\f3$ jdeps \-R \-cp lib/tools\&.jar com\&.sun\&.tools\&.jdeps\&.Main\fP +.fi +.nf +\f3lib/tools\&.jar \-> /usr/java/jre/lib/rt\&.jar\fP +.fi +.nf +\f3 com\&.sun\&.tools\&.classfile (tools\&.jar)\fP +.fi +.nf +\f3 \-> java\&.io \fP +.fi +.nf +\f3 \-> java\&.lang \fP +.fi +.nf +\f3 \-> java\&.lang\&.reflect \fP +.fi +.nf +\f3 \-> java\&.nio\&.charset \fP +.fi +.nf +\f3 \-> java\&.nio\&.file \fP +.fi +.nf +\f3 \-> java\&.util \fP +.fi +.nf +\f3 \-> java\&.util\&.regex \fP +.fi +.nf +\f3 com\&.sun\&.tools\&.jdeps (tools\&.jar)\fP +.fi +.nf +\f3 \-> java\&.io \fP +.fi +.nf +\f3 \-> java\&.lang \fP +.fi +.nf +\f3 \-> java\&.nio\&.file \fP +.fi +.nf +\f3 \-> java\&.nio\&.file\&.attribute \fP +.fi +.nf +\f3 \-> java\&.text \fP +.fi +.nf +\f3 \-> java\&.util \fP +.fi +.nf +\f3 \-> java\&.util\&.jar \fP +.fi +.nf +\f3 \-> java\&.util\&.regex \fP +.fi +.nf +\f3 \-> java\&.util\&.zip \fP +.fi +.nf +\f3/usr/java/jre/lib/jce\&.jar \-> /usr/java/jre/lib/rt\&.jar\fP +.fi +.nf +\f3 javax\&.crypto (jce\&.jar)\fP +.fi +.nf +\f3 \-> java\&.io \fP +.fi +.nf +\f3 \-> java\&.lang \fP +.fi +.nf +\f3 \-> java\&.lang\&.reflect \fP +.fi +.nf +\f3 \-> java\&.net \fP +.fi +.nf +\f3 \-> java\&.nio \fP +.fi +.nf +\f3 \-> java\&.security \fP +.fi +.nf +\f3 \-> java\&.security\&.cert \fP +.fi +.nf +\f3 \-> java\&.security\&.spec \fP +.fi +.nf +\f3 \-> java\&.util \fP +.fi +.nf +\f3 \-> java\&.util\&.concurrent \fP +.fi +.nf +\f3 \-> java\&.util\&.jar \fP +.fi +.nf +\f3 \-> java\&.util\&.regex \fP +.fi +.nf +\f3 \-> java\&.util\&.zip \fP +.fi +.nf +\f3 \-> javax\&.security\&.auth \fP +.fi +.nf +\f3 \-> sun\&.security\&.jca JDK internal API (rt\&.jar)\fP +.fi +.nf +\f3 \-> sun\&.security\&.util JDK internal API (rt\&.jar)\fP +.fi +.nf +\f3 javax\&.crypto\&.spec (jce\&.jar)\fP +.fi +.nf +\f3 \-> java\&.lang \fP +.fi +.nf +\f3 \-> java\&.security\&.spec \fP +.fi +.nf +\f3 \-> java\&.util \fP +.fi +.nf +\f3/usr/java/jre/lib/rt\&.jar \-> /usr/java/jre/lib/jce\&.jar\fP +.fi +.nf +\f3 java\&.security (rt\&.jar)\fP +.fi +.nf +\f3 \-> javax\&.crypto\fP +.fi +.nf +\f3\fP +.fi +.sp +Generate dot files of the dependencies of Notepad demo\&. +.sp +.nf +\f3$ jdeps \-dotoutput dot demo/jfc/Notepad/Notepad\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp +\f3jdeps\fR will create one dot file for each given JAR file named <\fIfilename\fR>\&.dot in the dot directory specified in the \f3-dotoutput\fR option, and also a summary file named summary\&.dot that will list the dependencies among the JAR files +.sp +.nf +\f3$ cat dot/Notepad\&.jar\&.dot \fP +.fi +.nf +\f3digraph "Notepad\&.jar" {\fP +.fi +.nf +\f3 // Path: demo/jfc/Notepad/Notepad\&.jar\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.awt";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.awt\&.event";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.beans";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.io";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.lang";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.net";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.util";\fP +.fi +.nf +\f3 "<unnamed>" \-> "java\&.util\&.logging";\fP +.fi +.nf +\f3 "<unnamed>" \-> "javax\&.swing";\fP +.fi +.nf +\f3 "<unnamed>" \-> "javax\&.swing\&.border";\fP +.fi +.nf +\f3 "<unnamed>" \-> "javax\&.swing\&.event";\fP +.fi +.nf +\f3 "<unnamed>" \-> "javax\&.swing\&.text";\fP +.fi +.nf +\f3 "<unnamed>" \-> "javax\&.swing\&.tree";\fP +.fi +.nf +\f3 "<unnamed>" \-> "javax\&.swing\&.undo";\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3$ cat dot/summary\&.dot\fP +.fi +.nf +\f3digraph "summary" {\fP +.fi +.nf +\f3 "Notepad\&.jar" \-> "rt\&.jar";\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +javap(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jhat.1 b/jdk-1.8.0.281/man/man1/jhat.1 new file mode 100755 index 0000000..d8c09f5 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jhat.1 @@ -0,0 +1,116 @@ +'\" t +.\" Copyright (c) 2006, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Troubleshooting Tools +.\" Title: jhat.1 +.\" +.if n .pl 99999 +.TH jhat 1 "21 November 2013" "JDK 8" "Troubleshooting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jhat \- Analyzes the Java heap\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjhat\fR [ \fIoptions\fR ] \fIheap\-dump\-file\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIheap-dump-file\fR +Java binary heap dump file to be browsed\&. For a dump file that contains multiple heap dumps, you can specify which dump in the file by appending \f3#<number>\fR to the file name, for example, \f3myfile\&.hprof#3\fR\&. +.SH DESCRIPTION +The \f3jhat\fR command parses a Java heap dump file and starts a web server\&. The \f3jhat\fR command lets you to browse heap dumps with your favorite web browser\&. The \f3jhat\fR command supports predesigned queries such as show all instances of a known class \f3MyClass\fR, and Object Query Language (OQL)\&. OQL is similar to SQL, except for querying heap dumps\&. Help on OQL is available from the OQL help page shown by the \f3jhat\fR command\&. With the default port, OQL help is available at http://localhost:7000/oqlhelp/ +.PP +There are several ways to generate a Java heap dump: +.TP 0.2i +\(bu +Use the \f3jmap -dump\fR option to obtain a heap dump at runtime\&. See jmap(1)\&. +.TP 0.2i +\(bu +Use the \f3jconsole\fR option to obtain a heap dump through \f3HotSpotDiagnosticMXBean\fR at runtime\&. See jconsole(1) and the \f3HotSpotDiagnosticMXBean\fR interface description at http://docs\&.oracle\&.com/javase/8/docs/jre/api/management/extension/com/sun/management/HotSpotDiagnosticMXBean\&.html +.TP 0.2i +\(bu +Heap dump is generated when an \f3OutOfMemoryError\fR is thrown by specifying the \f3-XX:+HeapDumpOnOutOfMemoryError\fR Java Virtual Machine (JVM) option\&. +.TP 0.2i +\(bu +Use the \f3hprof\fR command\&. See the HPROF: A Heap/CPU Profiling Tool at http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/hprof\&.html +.SH OPTIONS +.TP +-stack false|true +.br +Turns off tracking object allocation call stack\&. If allocation site information is not available in the heap dump, then you have to set this flag to \f3false\fR\&. The default is \f3true\fR\&. +.TP +-refs false|true +.br +Turns off tracking of references to objects\&. Default is \f3true\fR\&. By default, back pointers, which are objects that point to a specified object such as referrers or incoming references, are calculated for all objects in the heap\&. +.TP +-port \fIport-number\fR +.br +Sets the port for the \f3jhat\fR HTTP server\&. Default is 7000\&. +.TP +-exclude \fIexclude-file\fR +.br +Specifies a file that lists data members that should be excluded from the reachable objects query\&. For example, if the file lists \f3java\&.lang\&.String\&.value\fR, then, then whenever the list of objects that are reachable from a specific object \f3o\fR are calculated, reference paths that involve \f3java\&.lang\&.String\&.value\fR field are not considered\&. +.TP +-baseline \fIexclude-file\fR +.br +Specifies a baseline heap dump\&. Objects in both heap dumps with the same object ID are marked as not being new\&. Other objects are marked as new\&. This is useful for comparing two different heap dumps\&. +.TP +-debug \fIint\fR +.br +Sets the debug level for this tool\&. A level of 0 means no debug output\&. Set higher values for more verbose modes\&. +.TP +-version +.br +Reports the release number and exits +.TP +-h +.br +Dsiplays a help message and exits\&. +.TP +-help +.br +Displays a help message and exits\&. +.TP +-J\fIflag\fR +.br +Passes \f3flag\fR to the Java Virtual Machine on which the \f3jhat\fR command is running\&. For example, \f3-J-Xmx512m\fR to use a maximum heap size of 512 MB\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jmap(1) +.TP 0.2i +\(bu +jconsole(1) +.TP 0.2i +\(bu +HPROF: A Heap/CPU Profiling Tool at http://docs\&.oracle\&.com/javase/8/docs/technotes/samples/hprof\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jinfo.1 b/jdk-1.8.0.281/man/man1/jinfo.1 new file mode 100755 index 0000000..98f2bf0 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jinfo.1 @@ -0,0 +1,112 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Troubleshooting Tools +.\" Title: jinfo.1 +.\" +.if n .pl 99999 +.TH jinfo 1 "21 November 2013" "JDK 8" "Troubleshooting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jinfo \- Generates configuration information\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjinfo\fR [ \fIoption\fR ] \fIpid\fR +.fi +.nf + +\fBjinfo\fR [ \fIoption \fR] \fIexecutable core\fR +.fi +.nf + +\fBjinfo\fR [ \fIoption \fR] \fI[ servier\-id ] remote\-hostname\-or\-IP\fR +.fi +.sp +.TP +\fIoption\fR +The command-line options\&. See Options\&. +.TP +\fIpid\fR +The process ID for which the configuration information is to be printed\&. The process must be a Java process\&. To get a list of Java processes running on a machine, use the jps(1) command\&. +.TP +\fIexecutable\fR +The Java executable from which the core dump was produced\&. +.TP +\fIcore\fR +The core file for which the configuration information is to be printed\&. +.TP +\fIremote-hostname-or-IP\fR +The remote debug server \f3hostname\fR or \f3IP\fR address\&. See jsadebugd(1)\&. +.TP +\fIserver-id\fR +An optional unique ID to use when multiple debug servers are running on the same remote host\&. +.SH DESCRIPTION +The \f3jinfo\fR command prints Java configuration information for a specified Java process or core file or a remote debug server\&. The configuration information includes Java system properties and Java Virtual Machine (JVM) command-line flags\&. If the specified process is running on a 64-bit JVM, then you might need to specify the \f3-J-d64\fR option, for example: \f3jinfo\fR\f3-J-d64 -sysprops pid\fR\&. +.PP +This utility is unsupported and might not be available in future releases of the JDK\&. In Windows Systems where \f3dbgeng\&.dll\fR is not present, Debugging Tools For Windows must be installed to have these tools working\&. The \f3PATH\fR environment variable should contain the location of the jvm\&.dll that is used by the target process or the location from which the crash dump file was produced\&. For example, \f3set PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR \&. +.SH OPTIONS +.TP +no-option +Prints both command-line flags and system property name-value pairs\&. +.TP +-flag \fIname\fR +.br +Prints the name and value of the specified command-line flag\&. +.TP +-flag \fI[+|-]name\fR +.br +enables or disables the specified Boolean command-line flag\&. +.TP +-flag \fIname=value\fR +.br +Sets the specified command-line flag to the specified value\&. +.TP +-flags +.br +Prints command-line flags passed to the JVM\&. +.TP +-sysprops +.br +Prints Java system properties as name-value pairs\&. +.TP +-h +.br +Prints a help message\&. +.TP +-help +.br +Prints a help message\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jps(1) +.TP 0.2i +\(bu +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jjs.1 b/jdk-1.8.0.281/man/man1/jjs.1 new file mode 100755 index 0000000..ea88ff9 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jjs.1 @@ -0,0 +1,228 @@ +'\" t +.\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jjs +.\" Language: English +.\" Date: 03 March 2015 +.\" SectDesc: Basic Tools +.\" Software: JDK 8 +.\" Arch: generic +.\" Part Number: E38209-04 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jjs" "1" "03 March 2015" "JDK 8" "Basic Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +jjs \- Invokes the Nashorn engine\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB\fBjjs\fR\fR\fB [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIscript\-files\fR\fR\fB] [\-\- \fR\fB\fIarguments\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.PP +\fIoptions\fR +.RS 4 +One or more options of the +\fBjjs\fR +command, separated by spaces\&. For more information, see Options\&. +.RE +.PP +\fIscript\-files\fR +.RS 4 +One or more script files which you want to interpret using Nashorn, separated by spaces\&. If no files are specified, an interactive shell is started\&. +.RE +.PP +\fIarguments\fR +.RS 4 +All values after the double hyphen marker (\fB\-\-\fR) are passed through to the script or the interactive shell as arguments\&. These values can be accessed by using the +\fBarguments\fR +property (see Example 3)\&. +.RE +.SH "DESCRIPTION" +.PP +The +\fBjjs\fR +command\-line tool is used to invoke the Nashorn engine\&. You can use it to interpret one or several script files, or to run an interactive shell\&. +.SH "OPTIONS" +.PP +The options of the +\fBjjs\fR +command control the conditions under which scripts are interpreted by Nashorn\&. +.PP +\-cp \fIpath\fR +.br +\-classpath \fIpath\fR +.RS 4 +Specifies the path to the supporting class files To set multiple paths, the option can be repeated, or you can separate each path with a colon (:)\&. +.RE +.PP +\-D\fIname\fR=\fIvalue\fR +.RS 4 +Sets a system property to be passed to the script by assigning a value to a property name\&. The following example shows how to invoke Nashorn in interactive mode and assign +\fBmyValue\fR +to the property named +\fBmyKey\fR: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-DmyKey=myValue\fR\fR +\fBjjs> \fR\fB\fBjava\&.lang\&.System\&.getProperty("myKey")\fR\fR +\fBmyValue\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +This option can be repeated to set multiple properties\&. +.RE +.PP +\-doe +.br +\-\-dump\-on\-error +.RS 4 +Provides a full stack trace when an error occurs\&. By default, only a brief error message is printed\&. +.RE +.PP +\-fv +.br +\-\-fullversion +.RS 4 +Prints the full Nashorn version string\&. +.RE +.PP +\-fx +.RS 4 +Launches the script as a JavaFX application\&. +.RE +.PP +\-h +.br +\-help +.RS 4 +Prints the list of options and their descriptions\&. +.RE +.PP +\-\-language=[es5] +.RS 4 +Specifies the ECMAScript language version\&. The default version is ES5\&. +.RE +.PP +\-ot +.br +\-\-optimistic\-types=[true|false] +.RS 4 +Enables or disables optimistic type assumptions with deoptimizing recompilation\&. Running with optimistic types will yield higher final speed, but may increase warmup time\&. +.RE +.PP +\-scripting +.RS 4 +Enables shell scripting features\&. +.RE +.PP +\-strict +.RS 4 +Enables strict mode, which enforces stronger adherence to the standard (ECMAScript Edition 5\&.1), making it easier to detect common coding errors\&. +.RE +.PP +\-t=\fIzone\fR +.br +\-timezone=\fIzone\fR +.RS 4 +Sets the specified time zone for script execution\&. It overrides the time zone set in the OS and used by the +\fBDate\fR +object\&. +.RE +.PP +\-v +.br +\-version +.RS 4 +Prints the Nashorn version string\&. +.RE +.SH "EXAMPLES" +.PP +\fBExample 1 \fRRunning a Script with Nashorn +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjjs script\&.js\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fBExample 2 \fRRunning Nashorn in Interactive Mode +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs\fR\fR +\fBjjs> \fR\fB\fBprintln("Hello, World!")\fR\fR +\fBHello, World!\fR +\fBjjs> \fR\fB\fBquit()\fR\fR +\fB>>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.PP +\fBExample 3 \fRPassing Arguments to Nashorn +.RS 4 +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB>> \fR\fB\fBjjs \-\- a b c\fR\fR +\fBjjs> \fR\fB\fBarguments\&.join(", ")\fR\fR +\fBa, b, c\fR +\fBjjs>\fR + +.fi +.if n \{\ +.RE +.\} +.RE +.SH "SEE ALSO" +.PP +\fBjrunscript\fR +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jmap.1 b/jdk-1.8.0.281/man/man1/jmap.1 new file mode 100755 index 0000000..f8c8f65 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jmap.1 @@ -0,0 +1,123 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Troubleshooting Tools +.\" Title: jmap.1 +.\" +.if n .pl 99999 +.TH jmap 1 "21 November 2013" "JDK 8" "Troubleshooting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jmap \- Prints shared object memory maps or heap memory details for a process, core file, or remote debug server\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjmap\fR [ \fIoptions\fR ] \fIpid\fR +.fi +.nf + +\fBjmap\fR [ \fIoptions\fR ] \fIexecutable\fR \fIcore\fR +.fi +.nf + +\fBjmap\fR [ \fIoptions\fR ] [ \fIpid\fR ] \fIserver\-id\fR@ ] \fIremote\-hostname\-or\-IP\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIpid\fR +The process ID for which the memory map is to be printed\&. The process must be a Java process\&. To get a list of Java processes running on a machine, use the jps(1) command\&. +.TP +\fIexecutable\fR +The Java executable from which the core dump was produced\&. +.TP +\fIcore\fR +The core file for which the memory map is to be printed\&. +.TP +\fIremote-hostname-or-IP\fR +The remote debug server \f3hostname\fR or \f3IP\fR address\&. See jsadebugd(1)\&. +.TP +\fIserver-id\fR +An optional unique ID to use when multiple debug servers are running on the same remote host\&. +.SH DESCRIPTION +The \f3jmap\fR command prints shared object memory maps or heap memory details of a specified process, core file, or remote debug server\&. If the specified process is running on a 64-bit Java Virtual Machine (JVM), then you might need to specify the \f3-J-d64\fR option, for example: \f3jmap\fR\f3-J-d64 -heap pid\fR\&. +.PP +\fINote:\fR This utility is unsupported and might not be available in future releases of the JDK\&. On Windows Systems where the \f3dbgeng\&.dll\fR file is not present, Debugging Tools For Windows must be installed to make these tools work\&. The \f3PATH\fR environment variable should contain the location of the \f3jvm\&.dll\fR file that is used by the target process or the location from which the crash dump file was produced, for example: \f3set PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR\&. +.SH OPTIONS +.TP +<no option> +When no option is used, the \f3jmap\fR command prints shared object mappings\&. For each shared object loaded in the target JVM, the start address, size of the mapping, and the full path of the shared object file are printed\&. This behavior is similar to the Oracle Solaris \f3pmap\fR utility\&. +.TP +-dump:[live,] format=b, file=\fIfilename\fR +.br +Dumps the Java heap in \f3hprof\fR binary format to \f3filename\fR\&. The \f3live\fR suboption is optional, but when specified, only the active objects in the heap are dumped\&. To browse the heap dump, you can use the jhat(1) command to read the generated file\&. +.TP +-finalizerinfo +.br +Prints information about objects that are awaiting finalization\&. +.TP +-heap +.br +Prints a heap summary of the garbage collection used, the head configuration, and generation-wise heap usage\&. In addition, the number and size of interned Strings are printed\&. +.TP +-histo[:live] +.br +Prints a histogram of the heap\&. For each Java class, the number of objects, memory size in bytes, and the fully qualified class names are printed\&. The JVM internal class names are printed with an asterisk (*) prefix\&. If the \f3live\fR suboption is specified, then only active objects are counted\&. +.TP +-clstats +.br +Prints class loader wise statistics of Java heap\&. For each class loader, its name, how active it is, address, parent class loader, and the number and size of classes it has loaded are printed\&. +.TP +-F +.br +Force\&. Use this option with the \f3jmap -dump\fR or \f3jmap -histo\fR option when the pid does not respond\&. The \f3live\fR suboption is not supported in this mode\&. +.TP +-h +.br +Prints a help message\&. +.TP +-help +.br +Prints a help message\&. +.TP +-J\fIflag\fR +.br +Passes \f3flag\fR to the Java Virtual Machine where the \f3jmap\fR command is running\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jhat(1) +.TP 0.2i +\(bu +jps(1) +.TP 0.2i +\(bu +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jps.1 b/jdk-1.8.0.281/man/man1/jps.1 new file mode 100755 index 0000000..c7026f7 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jps.1 @@ -0,0 +1,184 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Monitoring Tools +.\" Title: jps.1 +.\" +.if n .pl 99999 +.TH jps 1 "21 November 2013" "JDK 8" "Monitoring Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jps \- Lists the instrumented Java Virtual Machines (JVMs) on the target system\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjps\fR [ \fIoptions\fR ] [ \fIhostid\fR ] +.fi +.sp +.TP +\fIoptions\fR +Command-line options\&. See Options\&. +.TP +\fIhostid\fR +The identifier of the host for which the process report should be generated\&. The \f3hostid\fR can include optional components that indicate the communications protocol, port number, and other implementation specific data\&. See Host Identifier\&. +.SH DESCRIPTION +The \f3jps\fR command lists the instrumented Java HotSpot VMs on the target system\&. The command is limited to reporting information on JVMs for which it has the access permissions\&. +.PP +If the \f3jps\fR command is run without specifying a \f3hostid\fR, then it searches for instrumented JVMs on the local host\&. If started with a \f3hostid\fR, then it searches for JVMs on the indicated host, using the specified protocol and port\&. A \f3jstatd\fR process is assumed to be running on the target host\&. +.PP +The \f3jps\fR command reports the local JVM identifier, or \f3lvmid\fR, for each instrumented JVM found on the target system\&. The \f3lvmid\fR is typically, but not necessarily, the operating system\&'s process identifier for the JVM process\&. With no options, \f3jps\fR lists each Java application\&'s \f3lvmid\fR followed by the short form of the application\&'s class name or jar file name\&. The short form of the class name or JAR file name omits the class\&'s package information or the JAR files path information\&. +.PP +The \f3jps\fR command uses the Java launcher to find the class name and arguments passed to the main method\&. If the target JVM is started with a custom launcher, then the class or JAR file name and the arguments to the \f3main\fR method are not available\&. In this case, the \f3jps\fR command outputs the string \f3Unknown\fR for the class name or JAR file name and for the arguments to the \f3main\fR method\&. +.PP +The list of JVMs produced by the \f3jps\fR command can be limited by the permissions granted to the principal running the command\&. The command only lists the JVMs for which the principle has access rights as determined by operating system-specific access control mechanisms\&. +.SH OPTIONS +The \f3jps\fR command supports a number of options that modify the output of the command\&. These options are subject to change or removal in the future\&. +.TP +-q +.br +Suppresses the output of the class name, JAR file name, and arguments passed to the \f3main\fR method, producing only a list of local JVM identifiers\&. +.TP +-m +.br +Displays the arguments passed to the \f3main\fR method\&. The output may be \f3null\fR for embedded JVMs\&. +.TP +-l +.br +Displays the full package name for the application\&'s \f3main\fR class or the full path name to the application\&'s JAR file\&. +.TP +-v +.br +Displays the arguments passed to the JVM\&. +.TP +-V +.br +Suppresses the output of the class name, JAR file name, and arguments passed to the main method, producing only a list of local JVM identifiers\&. +.TP +-J\f3option\fR +.br +Passes \f3option\fR to the JVM, where option is one of the \f3options\fR described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH HOST\ IDENTIFIER +The host identifier, or \f3hostid\fR is a string that indicates the target system\&. The syntax of the \f3hostid\fR string corresponds to the syntax of a URI: +.sp +.nf +\f3[protocol:][[//]hostname][:port][/servername]\fP +.fi +.nf +\f3\fP +.fi +.sp +.TP +\fIprotocol\fR +The communications protocol\&. If the \f3protocol\fR is omitted and a \f3hostname\fR is not specified, then the default protocol is a platform-specific, optimized, local protocol\&. If the protocol is omitted and a host name is specified, then the default protocol is \f3rmi\fR\&. +.TP +hostname +A hostname or IP address that indicates the target host\&. If you omit the \f3hostname\fR parameter, then the target host is the local host\&. +.TP +port +The default port for communicating with the remote server\&. If the \f3hostname\fR parameter is omitted or the \f3protocol\fR parameter specifies an optimized, local protocol, then the \f3port\fR parameter is ignored\&. Otherwise, treatment of the \f3port\fR parameter is implementation specific\&. For the default \f3rmi\fR protocol, the \f3port\fR parameter indicates the port number for the rmiregistry on the remote host\&. If the \f3port\fR parameter is omitted, and the \f3protocol\fR parameter indicates \f3rmi\fR, then the default rmiregistry port (1099) is used\&. +.TP +servername +The treatment of this parameter depends on the implementation\&. For the optimized, local protocol, this field is ignored\&. For the \f3rmi\fR protocol, this parameter is a string that represents the name of the RMI remote object on the remote host\&. See the \f3jstatd\fR command \f3-n\fRoption for more information\&. +.SH OUTPUT\ FORMAT +The output of the \f3jps\fR command follows the following pattern: +.sp +.nf +\f3lvmid [ [ classname | JARfilename | "Unknown"] [ arg* ] [ jvmarg* ] ]\fP +.fi +.nf +\f3\fP +.fi +.sp +All output tokens are separated by white space\&. An \f3arg\fR value that includes embedded white space introduces ambiguity when attempting to map arguments to their actual positional parameters\&. +.PP +\fINote:\fR It is recommended that you do not write scripts to parse \f3jps\fR output because the format might change in future releases\&. If you write scripts that parse \f3jps\fR output, then expect to modify them for future releases of this tool\&. +.SH EXAMPLES +This section provides examples of the \f3jps\fR command\&. +.PP +List the instrumented JVMs on the local host: +.sp +.nf +\f3jps\fP +.fi +.nf +\f318027 Java2Demo\&.JAR\fP +.fi +.nf +\f318032 jps\fP +.fi +.nf +\f318005 jstat\fP +.fi +.nf +\f3\fP +.fi +.sp +The following example lists the instrumented JVMs on a remote host\&. This example assumes that the \f3jstat\fR server and either the its internal RMI registry or a separate external rmiregistry process are running on the remote host on the default port (port 1099)\&. It also assumes that the local host has appropriate permissions to access the remote host\&. This example also includes the \f3-l\fR option to output the long form of the class names or JAR file names\&. +.sp +.nf +\f3jps \-l remote\&.domain\fP +.fi +.nf +\f33002 /opt/jdk1\&.7\&.0/demo/jfc/Java2D/Java2Demo\&.JAR\fP +.fi +.nf +\f32857 sun\&.tools\&.jstatd\&.jstatd\fP +.fi +.nf +\f3\fP +.fi +.sp +The following example lists the instrumented JVMs on a remote host with a non-default port for the RMI registry\&. This example assumes that the \f3jstatd\fR server, with an internal RMI registry bound to port 2002, is running on the remote host\&. This example also uses the \f3-m\fR option to include the arguments passed to the \f3main\fR method of each of the listed Java applications\&. +.sp +.nf +\f3jps \-m remote\&.domain:2002\fP +.fi +.nf +\f33002 /opt/jdk1\&.7\&.0/demo/jfc/Java2D/Java2Demo\&.JAR\fP +.fi +.nf +\f33102 sun\&.tools\&.jstatd\&.jstatd \-p 2002\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +jstat(1) +.TP 0.2i +\(bu +jstatd(1) +.TP 0.2i +\(bu +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jrunscript.1 b/jdk-1.8.0.281/man/man1/jrunscript.1 new file mode 100755 index 0000000..7000f93 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jrunscript.1 @@ -0,0 +1,175 @@ +'\" t +.\" Copyright (c) 2006, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Scripting Tools +.\" Title: jrunscript.1 +.\" +.if n .pl 99999 +.TH jrunscript 1 "21 November 2013" "JDK 8" "Scripting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jrunscript \- Runs a command-line script shell that supports interactive and batch modes\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjrunscript\fR [\fIoptions\fR] [\fIarguments\fR] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIarguments\fR +Arguments, when used, follow immediately after options or the command name\&. See Arguments\&. +.SH DESCRIPTION +The \f3jrunscript\fR command is a language-independent command-line script shell\&. The \f3jrunscript\fR command supports both an interactive (read-eval-print) mode and a batch (\f3-f\fR option) mode of script execution\&. By default, JavaScript is the language used, but the \f3-l\fR option can be used to specify a different language\&. By using Java to scripting language communication, the \f3jrunscript\fR command supports an exploratory programming style\&. +.SH OPTIONS +.TP +-classpath \fIpath\fR +.br +Indicate where any class files are that the script needs to access\&. +.TP +-cp \fIpath\fR +.br +Same as \f3-classpath\fR\f3path\fR\&. +.TP +-D\fIname\fR=\fIvalue\fR +.br +Sets a Java system property\&. +.TP +-J\fIflag\fR +.br +Passes \f3flag\fR directly to the Java Virtual Machine where the \f3jrunscript\fR command is running\&. +.TP +-I \fIlanguage\fR +.br +Uses the specified scripting language\&. By default, JavaScript is used\&. To use other scripting languages, you must specify the corresponding script engine\&'s JAR file with the \f3-cp\fR or \f3-classpath\fR option\&. +.TP +-e \fIscript\fR +.br +Evaluates the specified script\&. This option can be used to run one-line scripts that are specified completely on the command line\&. +.TP +-encoding \fIencoding\fR +.br +Specifies the character encoding used to read script files\&. +.TP +-f \fIscript-file\fR +.br +Evaluates the specified script file (batch mode)\&. +.TP +-f - +.br +Reads and evaluates a script from standard input (interactive mode)\&. +.TP +-help +.br +Displays a help message and exits\&. +.TP +-? +.br +Displays a help message and exits\&. +.TP +-q +.br +Lists all script engines available and exits\&. +.SH ARGUMENTS +If arguments are present and if no \f3-e\fR or \f3-f\fR option is used, then the first argument is the script file and the rest of the arguments, if any, are passed to the script\&. If arguments and \f3-e\fR or the \f3-f\fR option are used, then all arguments are passed to the script\&. If arguments, \f3-e\fR and \f3-f\fR are missing, then interactive mode is used\&. Script arguments are available to a script in an engine variable named \f3arguments\fR of type \f3String\fR array\&. +.SH EXAMPLES +.SS EXECUTE\ INLINE\ SCRIPTS +.sp +.nf +\f3jrunscript \-e "print(\&'hello world\&')"\fP +.fi +.nf +\f3jrunscript \-e "cat(\&'http://www\&.example\&.com\&')"\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS USE\ SPECIFIED\ LANGUAGE\ AND\ EVALUATE\ THE\ SCRIPT\ FILE +.sp +.nf +\f3jrunscript \-l js \-f test\&.js\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS INTERACTIVE\ MODE +.sp +.nf +\f3jrunscript\fP +.fi +.nf +\f3js> print(\&'Hello World\en\&');\fP +.fi +.nf +\f3Hello World\fP +.fi +.nf +\f3js> 34 + 55\fP +.fi +.nf +\f389\&.0\fP +.fi +.nf +\f3js> t = new java\&.lang\&.Thread(function() { print(\&'Hello World\en\&'); })\fP +.fi +.nf +\f3Thread[Thread\-0,5,main]\fP +.fi +.nf +\f3js> t\&.start()\fP +.fi +.nf +\f3js> Hello World\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3js>\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS RUN\ SCRIPT\ FILE\ WITH\ SCRIPT\ ARGUMENTS +The test\&.js file is the script file\&. The \f3arg1\fR, \f3arg2\fR and \f3arg3\fR arguments are passed to the script\&. The script can access these arguments with an arguments array\&. +.sp +.nf +\f3jrunscript test\&.js arg1 arg2 arg3\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +If JavaScript is used, then before it evaluates a user defined script, the \f3jrunscript\fR command initializes certain built-in functions and objects\&. These JavaScript built-ins are documented in JsDoc-Toolkit at http://code\&.google\&.com/p/jsdoc-toolkit/ +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jsadebugd.1 b/jdk-1.8.0.281/man/man1/jsadebugd.1 new file mode 100755 index 0000000..f5168ba --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jsadebugd.1 @@ -0,0 +1,88 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Troubleshooting Tools +.\" Title: jsadebugd.1 +.\" +.if n .pl 99999 +.TH jsadebugd 1 "21 November 2013" "JDK 8" "Troubleshooting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jsadebugd \- Attaches to a Java process or core file and acts as a debug server\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjsadebugd\fR \fIpid\fR [ \fIserver\-id\fR ] +.fi +.nf + +\fBjsadebugd\fR \fIexecutable\fR \fIcore\fR [ \fIserver\-id\fR ] +.fi +.sp +.TP +\fIpid\fR +The process ID of the process to which the debug server attaches\&. The process must be a Java process\&. To get a list of Java processes running on a machine, use the jps(1) command\&. At most one instance of the debug server can be attached to a single process\&. +.TP +\fIexecutable\fR +The Java executable from which the core dump was produced\&. +.TP +\fIcore\fR +The core file to which the debug server should attach\&. +.TP +\fIserver-id\fR +An optional unique ID that is needed when multiple debug servers are started on the same machine\&. This ID must be used by remote clients to identify the particular debug server to which to attach\&. Within a single machine, this ID must be unique\&. +.SH DESCRIPTION +The \f3jsadebugd\fR command attaches to a Java process or core file and acts as a debug server\&. Remote clients such as \f3jstack\fR, \f3jmap\fR, and \f3jinfo\fR can attach to the server through Java Remote Method Invocation (RMI)\&. Before you start the \f3jsadebugd\fR command, start the RMI registry with the \f3rmiregistry\fR command as follows where \fI$JAVA_HOME\fR is the JDK installation directory: +.sp +.nf +\f3rmiregistry \-J\-Xbootclasspath/p:$JAVA_HOME/lib/sajdi\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp +If the RMI registry was not started, then the \f3jsadebugd\fR command starts an RMI registry in a standard (1099) port internally\&. The debug server can be stopped by sending a \f3SIGINT\fR to it\&. To send a SIGINT press \fICtrl+C\fR\&. +.PP +\fINote:\fR This utility is unsupported and may or may not be available in future releases of the JDK\&. In Windows Systems where \f3dbgeng\&.dll\fR is not present, Debugging Tools For Windows must be installed to have these tools working\&. The \f3PATH\fR environment variable should contain the location of jvm\&.dll used by the target process or the location from which the crash dump file was produced\&. For example, \f3s\fR\f3et PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jinfo(1) +.TP 0.2i +\(bu +jmap(1) +.TP 0.2i +\(bu +jps(1) +.TP 0.2i +\(bu +jstack(1) +.TP 0.2i +\(bu +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jstack.1 b/jdk-1.8.0.281/man/man1/jstack.1 new file mode 100755 index 0000000..e95a70d --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jstack.1 @@ -0,0 +1,117 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Troubleshooting Tools +.\" Title: jstack.1 +.\" +.if n .pl 99999 +.TH jstack 1 "21 November 2013" "JDK 8" "Troubleshooting Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jstack \- Prints Java thread stack traces for a Java process, core file, or remote debug server\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjstack\fR [ \fIoptions\fR ] \fIpid\fR +.fi +.nf + +\fBjstack\fR [ \fIoptions\fR ] \fIexecutable\fR \fIcore\fR +.fi +.nf + +\fBjstack\fR [ \fIoptions\fR ] [ \fIserver\-id\fR@ ] \fIremote\-hostname\-or\-IP\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIpid\fR +The process ID for which the stack trace is printed\&. The process must be a Java process\&. To get a list of Java processes running on a machine, use the jps(1) command\&. +.TP +\fIexecutable\fR +The Java executable from which the core dump was produced\&. +.TP +\fIcore\fR +The core file for which the stack trace is to be printed\&. +.TP +\fIremote-hostname-or-IP\fR +The remote debug server \f3hostname\fR or \f3IP\fR address\&. See jsadebugd(1)\&. +.TP +\fIserver-id\fR +An optional unique ID to use when multiple debug servers are running on the same remote host\&. +.SH DESCRIPTION +The \f3jstack\fR command prints Java stack traces of Java threads for a specified Java process, core file, or remote debug server\&. For each Java frame, the full class name, method name, byte code index (BCI), and line number, when available, are printed\&. With the \f3-m\fR option, the \f3jstack\fR command prints both Java and native frames of all threads with the program counter (PC)\&. For each native frame, the closest native symbol to PC, when available, is printed\&. C++ mangled names are not demangled\&. To demangle C++ names, the output of this command can be piped to \f3c++filt\fR\&. When the specified process is running on a 64-bit Java Virtual Machine, you might need to specify the \f3-J-d64\fR option, for example: \f3jstack -J-d64 -m pid\fR\&. +.PP +\fINote:\fR This utility is unsupported and might not be available in future release of the JDK\&. In Windows Systems where the dbgeng\&.dll file is not present, Debugging Tools For Windows must be installed so these tools work\&. The \f3PATH\fR environment variable needs to contain the location of the jvm\&.dll that is used by the target process, or the location from which the crash dump file was produced\&. For example: +.sp +.nf +\f3set PATH=<jdk>\ejre\ebin\eclient;%PATH%\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +.TP +-F +.br +Force a stack dump when \f3jstack\fR [\f3-l\fR] \f3pid\fR does not respond\&. +.TP +-l +.br +Long listing\&. Prints additional information about locks such as a list of owned \f3java\&.util\&.concurrent\fR ownable synchronizers\&. See the \f3AbstractOwnableSynchronizer\fR class description at http://docs\&.oracle\&.com/javase/8/docs/api/java/util/concurrent/locks/AbstractOwnableSynchronizer\&.html +.TP +-m +.br +Prints a mixed mode stack trace that has both Java and native C/C++ frames\&. +.TP +-h +.br +Prints a help message\&. +.TP +-help +.br +Prints a help message\&. +.SH KNOWN\ BUGS +In mixed mode stack trace, the \f3-m\fR option does not work with the remote debug server\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +pstack(1) +.TP 0.2i +\(bu +C++filt(1) +.TP 0.2i +\(bu +jps(1) +.TP 0.2i +\(bu +jsadebugd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jstat.1 b/jdk-1.8.0.281/man/man1/jstat.1 new file mode 100755 index 0000000..d8a4c33 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jstat.1 @@ -0,0 +1,758 @@ +'\" t +.\" Copyright (c) 2004, 2015, Oracle and/or its affiliates. All rights reserved. +.\" +.\" Title: jstat +.\" Language: English +.\" Date: 03 March 2015 +.\" SectDesc: Monitoring Tools +.\" Software: JDK 8 +.\" Arch: generic +.\" Part Number: E38209-04 +.\" Doc ID: JSSOR +.\" +.if n .pl 99999 +.TH "jstat" "1" "03 March 2015" "JDK 8" "Monitoring Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.SH "NAME" +jstat \- Monitors Java Virtual Machine (JVM) statistics\&. This command is experimental and unsupported\&. +.SH "SYNOPSIS" +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat\fR [ \fIgeneralOption\fR | \fIoutputOptions vmid\fR [ \fIinterval\fR[s|ms] [ \fIcount \fR] ] +.fi +.if n \{\ +.RE +.\} +.PP +\fIgeneralOption\fR +.RS 4 +A single general command\-line option +\fB\-help\fR +or +\fB\-options\fR\&. See General Options\&. +.RE +.PP +\fIoutputOptions\fR +.RS 4 +One or more output options that consist of a single +\fBstatOption\fR, plus any of the +\fB\-t\fR, +\fB\-h\fR, and +\fB\-J\fR +options\&. See Output Options\&. +.RE +.PP +\fIvmid\fR +.RS 4 +Virtual machine identifier, which is a string that indicates the target JVM\&. The general syntax is the following: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][//]lvmid[@hostname[:port]/servername]\fR + +.fi +.if n \{\ +.RE +.\} +The syntax of the +\fBvmid\fR +string corresponds to the syntax of a URI\&. The +\fBvmid\fR +string can vary from a simple integer that represents a local JVM to a more complex construction that specifies a communications protocol, port number, and other implementation\-specific values\&. See Virtual Machine Identifier\&. +.RE +.PP +\fIinterval\fR [s|ms] +.RS 4 +Sampling interval in the specified units, seconds (s) or milliseconds (ms)\&. Default units are milliseconds\&. Must be a positive integer\&. When specified, the +\fBjstat\fR +command produces its output at each interval\&. +.RE +.PP +\fIcount\fR +.RS 4 +Number of samples to display\&. The default value is infinity which causes the +\fBjstat\fR +command to display statistics until the target JVM terminates or the +\fBjstat\fR +command is terminated\&. This value must be a positive integer\&. +.RE +.SH "DESCRIPTION" +.PP +The +\fBjstat\fR +command displays performance statistics for an instrumented Java HotSpot VM\&. The target JVM is identified by its virtual machine identifier, or +\fBvmid\fR +option\&. +.SH "VIRTUAL MACHINE IDENTIFIER" +.PP +The syntax of the +\fBvmid\fR +string corresponds to the syntax of a URI: +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fB[protocol:][//]lvmid[@hostname[:port]/servername]\fR + +.fi +.if n \{\ +.RE +.\} +.PP +\fIprotocol\fR +.RS 4 +The communications protocol\&. If the +\fIprotocol\fR +value is omitted and a host name is not specified, then the default protocol is a platform\-specific optimized local protocol\&. If the +\fIprotocol\fR +value is omitted and a host name is specified, then the default protocol is +\fBrmi\fR\&. +.RE +.PP +\fIlvmid\fR +.RS 4 +The local virtual machine identifier for the target JVM\&. The +\fBlvmid\fR +is a platform\-specific value that uniquely identifies a JVM on a system\&. The +\fBlvmid\fR +is the only required component of a virtual machine identifier\&. The +\fBlvmid\fR +is typically, but not necessarily, the operating system\*(Aqs process identifier for the target JVM process\&. You can use the +\fBjps\fR +command to determine the +\fBlvmid\fR\&. Also, you can determine the +\fBlvmid\fR +on Solaris, Linux, and OS X platforms with the +\fBps\fR +command, and on Windows with the Windows Task Manager\&. +.RE +.PP +\fIhostname\fR +.RS 4 +A hostname or IP address that indicates the target host\&. If the +\fIhostname\fR +value is omitted, then the target host is the local host\&. +.RE +.PP +\fIport\fR +.RS 4 +The default port for communicating with the remote server\&. If the +\fIhostname\fR +value is omitted or the +\fIprotocol\fR +value specifies an optimized, local protocol, then the +\fIport\fR +value is ignored\&. Otherwise, treatment of the +\fBport\fR +parameter is implementation\-specific\&. For the default +\fBrmi\fR +protocol, the port value indicates the port number for the rmiregistry on the remote host\&. If the +\fIport\fR +value is omitted and the +\fIprotocol\fR +value indicates +\fBrmi\fR, then the default rmiregistry port (1099) is used\&. +.RE +.PP +\fIservername\fR +.RS 4 +The treatment of the +\fBservername\fR +parameter depends on implementation\&. For the optimized local protocol, this field is ignored\&. For the +\fBrmi\fR +protocol, it represents the name of the RMI remote object on the remote host\&. +.RE +.SH "OPTIONS" +.PP +The +\fBjstat\fR +command supports two types of options, general options and output options\&. General options cause the +\fBjstat\fR +command to display simple usage and version information\&. Output options determine the content and format of the statistical output\&. +.PP +All options and their functionality are subject to change or removal in future releases\&. +.SS "General Options" +.PP +If you specify one of the general options, then you cannot specify any other option or parameter\&. +.PP +\-help +.RS 4 +Displays a help message\&. +.RE +.PP +\-options +.RS 4 +Displays a list of static options\&. See Output Options\&. +.RE +.SS "Output Options" +.PP +If you do not specify a general option, then you can specify output options\&. Output options determine the content and format of the +\fBjstat\fR +command\*(Aqs output, and consist of a single +\fBstatOption\fR, plus any of the other output options (\fB\-h\fR, +\fB\-t\fR, and +\fB\-J\fR)\&. The +\fBstatOption\fR +must come first\&. +.PP +Output is formatted as a table, with columns that are separated by spaces\&. A header row with titles describes the columns\&. Use the +\fB\-h\fR +option to set the frequency at which the header is displayed\&. Column header names are consistent among the different options\&. In general, if two options provide a column with the same name, then the data source for the two columns is the same\&. +.PP +Use the +\fB\-t\fR +option to display a time stamp column, labeled Timestamp as the first column of output\&. The Timestamp column contains the elapsed time, in seconds, since the target JVM started\&. The resolution of the time stamp is dependent on various factors and is subject to variation due to delayed thread scheduling on heavily loaded systems\&. +.PP +Use the interval and count parameters to determine how frequently and how many times, respectively, the +\fBjstat\fR +command displays its output\&. +.PP +\fBNote:\fR +Do not to write scripts to parse the +\fBjstat\fR +command\*(Aqs output because the format might change in future releases\&. If you write scripts that parse +\fBjstat\fR +command output, then expect to modify them for future releases of this tool\&. +.PP +\-\fIstatOption\fR +.RS 4 +Determines the statistics information the +\fBjstat\fR +command displays\&. The following lists the available options\&. Use the +\fB\-options\fR +general option to display the list of options for a particular platform installation\&. See Stat Options and Output\&. +.sp +\fBclass\fR: Displays statistics about the behavior of the class loader\&. +.sp +\fBcompiler\fR: Displays statistics about the behavior of the Java HotSpot VM Just\-in\-Time compiler\&. +.sp +\fBgc\fR: Displays statistics about the behavior of the garbage collected heap\&. +.sp +\fBgccapacity\fR: Displays statistics about the capacities of the generations and their corresponding spaces\&. +.sp +\fBgccause\fR: Displays a summary about garbage collection statistics (same as +\fB\-gcutil\fR), with the cause of the last and current (when applicable) garbage collection events\&. +.sp +\fBgcnew\fR: Displays statistics of the behavior of the new generation\&. +.sp +\fBgcnewcapacity\fR: Displays statistics about the sizes of the new generations and its corresponding spaces\&. +.sp +\fBgcold\fR: Displays statistics about the behavior of the old generation and metaspace statistics\&. +.sp +\fBgcoldcapacity\fR: Displays statistics about the sizes of the old generation\&. +.sp +\fBgcmetacapacity\fR: Displays statistics about the sizes of the metaspace\&. +.sp +\fBgcutil\fR: Displays a summary about garbage collection statistics\&. +.sp +\fBprintcompilation\fR: Displays Java HotSpot VM compilation method statistics\&. +.RE +.PP +\-h \fIn\fR +.RS 4 +Displays a column header every +\fIn\fR +samples (output rows), where +\fIn\fR +is a positive integer\&. Default value is 0, which displays the column header the first row of data\&. +.RE +.PP +\-t +.RS 4 +Displays a timestamp column as the first column of output\&. The time stamp is the time since the start time of the target JVM\&. +.RE +.PP +\-J\fIjavaOption\fR +.RS 4 +Passes +\fBjavaOption\fR +to the Java application launcher\&. For example, +\fB\-J\-Xms48m\fR +sets the startup memory to 48 MB\&. For a complete list of options, see +java(1)\&. +.RE +.SS "Stat Options and Output" +.PP +The following information summarizes the columns that the +\fBjstat\fR +command outputs for each +\fIstatOption\fR\&. +.PP +\-class \fIoption\fR +.RS 4 +Class loader statistics\&. +.sp +\fBLoaded\fR: Number of classes loaded\&. +.sp +\fBBytes\fR: Number of kBs loaded\&. +.sp +\fBUnloaded\fR: Number of classes unloaded\&. +.sp +\fBBytes\fR: Number of Kbytes unloaded\&. +.sp +\fBTime\fR: Time spent performing class loading and unloading operations\&. +.RE +.PP +\-compiler \fIoption\fR +.RS 4 +Java HotSpot VM Just\-in\-Time compiler statistics\&. +.sp +\fBCompiled\fR: Number of compilation tasks performed\&. +.sp +\fBFailed\fR: Number of compilations tasks failed\&. +.sp +\fBInvalid\fR: Number of compilation tasks that were invalidated\&. +.sp +\fBTime\fR: Time spent performing compilation tasks\&. +.sp +\fBFailedType\fR: Compile type of the last failed compilation\&. +.sp +\fBFailedMethod\fR: Class name and method of the last failed compilation\&. +.RE +.PP +\-gc \fIoption\fR +.RS 4 +Garbage\-collected heap statistics\&. +.sp +\fBS0C\fR: Current survivor space 0 capacity (kB)\&. +.sp +\fBS1C\fR: Current survivor space 1 capacity (kB)\&. +.sp +\fBS0U\fR: Survivor space 0 utilization (kB)\&. +.sp +\fBS1U\fR: Survivor space 1 utilization (kB)\&. +.sp +\fBEC\fR: Current eden space capacity (kB)\&. +.sp +\fBEU\fR: Eden space utilization (kB)\&. +.sp +\fBOC\fR: Current old space capacity (kB)\&. +.sp +\fBOU\fR: Old space utilization (kB)\&. +.sp +\fBMC\fR: Metaspace capacity (kB)\&. +.sp +\fBMU\fR: Metacspace utilization (kB)\&. +.sp +\fBCCSC\fR: Compressed class space capacity (kB)\&. +.sp +\fBCCSU\fR: Compressed class space used (kB)\&. +.sp +\fBYGC\fR: Number of young generation garbage collection events\&. +.sp +\fBYGCT\fR: Young generation garbage collection time\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.sp +\fBFGCT\fR: Full garbage collection time\&. +.sp +\fBGCT\fR: Total garbage collection time\&. +.RE +.PP +\-gccapacity \fIoption\fR +.RS 4 +Memory pool generation and space capacities\&. +.sp +\fBNGCMN\fR: Minimum new generation capacity (kB)\&. +.sp +\fBNGCMX\fR: Maximum new generation capacity (kB)\&. +.sp +\fBNGC\fR: Current new generation capacity (kB)\&. +.sp +\fBS0C\fR: Current survivor space 0 capacity (kB)\&. +.sp +\fBS1C\fR: Current survivor space 1 capacity (kB)\&. +.sp +\fBEC\fR: Current eden space capacity (kB)\&. +.sp +\fBOGCMN\fR: Minimum old generation capacity (kB)\&. +.sp +\fBOGCMX\fR: Maximum old generation capacity (kB)\&. +.sp +\fBOGC\fR: Current old generation capacity (kB)\&. +.sp +\fBOC\fR: Current old space capacity (kB)\&. +.sp +\fBMCMN\fR: Minimum metaspace capacity (kB)\&. +.sp +\fBMCMX\fR: Maximum metaspace capacity (kB)\&. +.sp +\fBMC\fR: Metaspace capacity (kB)\&. +.sp +\fBCCSMN\fR: Compressed class space minimum capacity (kB)\&. +.sp +\fBCCSMX\fR: Compressed class space maximum capacity (kB)\&. +.sp +\fBCCSC\fR: Compressed class space capacity (kB)\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.RE +.PP +\-gccause \fIoption\fR +.RS 4 +This option displays the same summary of garbage collection statistics as the +\fB\-gcutil\fR +option, but includes the causes of the last garbage collection event and (when applicable) the current garbage collection event\&. In addition to the columns listed for +\fB\-gcutil\fR, this option adds the following columns\&. +.sp +\fBLGCC\fR: Cause of last garbage collection +.sp +\fBGCC\fR: Cause of current garbage collection +.RE +.PP +\-gcnew \fIoption\fR +.RS 4 +New generation statistics\&. +.sp +\fBS0C\fR: Current survivor space 0 capacity (kB)\&. +.sp +\fBS1C\fR: Current survivor space 1 capacity (kB)\&. +.sp +\fBS0U\fR: Survivor space 0 utilization (kB)\&. +.sp +\fBS1U\fR: Survivor space 1 utilization (kB)\&. +.sp +\fBTT\fR: Tenuring threshold\&. +.sp +\fBMTT\fR: Maximum tenuring threshold\&. +.sp +\fBDSS\fR: Desired survivor size (kB)\&. +.sp +\fBEC\fR: Current eden space capacity (kB)\&. +.sp +\fBEU\fR: Eden space utilization (kB)\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBYGCT\fR: Young generation garbage collection time\&. +.RE +.PP +\-gcnewcapacity \fIoption\fR +.RS 4 +New generation space size statistics\&. +.sp +\fBNGCMN\fR: Minimum new generation capacity (kB)\&. +.sp +\fBNGCMX\fR: Maximum new generation capacity (kB)\&. +.sp +\fBNGC\fR: Current new generation capacity (kB)\&. +.sp +\fBS0CMX\fR: Maximum survivor space 0 capacity (kB)\&. +.sp +\fBS0C\fR: Current survivor space 0 capacity (kB)\&. +.sp +\fBS1CMX\fR: Maximum survivor space 1 capacity (kB)\&. +.sp +\fBS1C\fR: Current survivor space 1 capacity (kB)\&. +.sp +\fBECMX\fR: Maximum eden space capacity (kB)\&. +.sp +\fBEC\fR: Current eden space capacity (kB)\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.RE +.PP +\-gcold \fIoption\fR +.RS 4 +Old generation and metaspace behavior statistics\&. +.sp +\fBMC\fR: Metaspace capacity (kB)\&. +.sp +\fBMU\fR: Metaspace utilization (kB)\&. +.sp +\fBCCSC\fR: Compressed class space capacity (kB)\&. +.sp +\fBCCSU\fR: Compressed class space used (kB)\&. +.sp +\fBOC\fR: Current old space capacity (kB)\&. +.sp +\fBOU\fR: Old space utilization (kB)\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.sp +\fBFGCT\fR: Full garbage collection time\&. +.sp +\fBGCT\fR: Total garbage collection time\&. +.RE +.PP +\-gcoldcapacity \fIoption\fR +.RS 4 +Old generation size statistics\&. +.sp +\fBOGCMN\fR: Minimum old generation capacity (kB)\&. +.sp +\fBOGCMX\fR: Maximum old generation capacity (kB)\&. +.sp +\fBOGC\fR: Current old generation capacity (kB)\&. +.sp +\fBOC\fR: Current old space capacity (kB)\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.sp +\fBFGCT\fR: Full garbage collection time\&. +.sp +\fBGCT\fR: Total garbage collection time\&. +.RE +.PP +\-gcmetacapacity \fIoption\fR +.RS 4 +Metaspace size statistics\&. +.sp +\fBMCMN\fR: Minimum metaspace capacity (kB)\&. +.sp +\fBMCMX\fR: Maximum metaspace capacity (kB)\&. +.sp +\fBMC\fR: Metaspace capacity (kB)\&. +.sp +\fBCCSMN\fR: Compressed class space minimum capacity (kB)\&. +.sp +\fBCCSMX\fR: Compressed class space maximum capacity (kB)\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.sp +\fBFGCT\fR: Full garbage collection time\&. +.sp +\fBGCT\fR: Total garbage collection time\&. +.RE +.PP +\-gcutil \fIoption\fR +.RS 4 +Summary of garbage collection statistics\&. +.sp +\fBS0\fR: Survivor space 0 utilization as a percentage of the space\*(Aqs current capacity\&. +.sp +\fBS1\fR: Survivor space 1 utilization as a percentage of the space\*(Aqs current capacity\&. +.sp +\fBE\fR: Eden space utilization as a percentage of the space\*(Aqs current capacity\&. +.sp +\fBO\fR: Old space utilization as a percentage of the space\*(Aqs current capacity\&. +.sp +\fBM\fR: Metaspace utilization as a percentage of the space\*(Aqs current capacity\&. +.sp +\fBCCS\fR: Compressed class space utilization as a percentage\&. +.sp +\fBYGC\fR: Number of young generation GC events\&. +.sp +\fBYGCT\fR: Young generation garbage collection time\&. +.sp +\fBFGC\fR: Number of full GC events\&. +.sp +\fBFGCT\fR: Full garbage collection time\&. +.sp +\fBGCT\fR: Total garbage collection time\&. +.RE +.PP +\-printcompilation \fIoption\fR +.RS 4 +Java HotSpot VM compiler method statistics\&. +.sp +\fBCompiled\fR: Number of compilation tasks performed by the most recently compiled method\&. +.sp +\fBSize\fR: Number of bytes of byte code of the most recently compiled method\&. +.sp +\fBType\fR: Compilation type of the most recently compiled method\&. +.sp +\fBMethod\fR: Class name and method name identifying the most recently compiled method\&. Class name uses slash (/) instead of dot (\&.) as a name space separator\&. Method name is the method within the specified class\&. The format for these two fields is consistent with the HotSpot +\fB\-XX:+PrintCompilation\fR +option\&. +.RE +.SH "EXAMPLES" +.PP +This section presents some examples of monitoring a local JVM with an +\fIlvmid\fR +of 21891\&. +.SS "The gcutil Option" +.PP +This example attaches to lvmid 21891 and takes 7 samples at 250 millisecond intervals and displays the output as specified by the \-\fBgcutil\fR +option\&. +.PP +The output of this example shows that a young generation collection occurred between the third and fourth sample\&. The collection took 0\&.078 seconds and promoted objects from the eden space (E) to the old space (O), resulting in an increase of old space utilization from 66\&.80% to 68\&.19%\&. Before the collection, the survivor space was 97\&.02% utilized, but after this collection it is 91\&.03% utilized\&. +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcutil 21891 250 7\fR +\fB S0 S1 E O M CCS YGC YGCT FGC FGCT GCT \fR +\fB 0\&.00 97\&.02 70\&.31 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 0\&.00 97\&.02 86\&.23 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 0\&.00 97\&.02 96\&.53 66\&.80 95\&.52 89\&.14 7 0\&.300 0 0\&.000 0\&.300\fR +\fB 91\&.03 0\&.00 1\&.98 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 15\&.82 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 17\&.80 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +\fB 91\&.03 0\&.00 17\&.80 68\&.19 95\&.89 91\&.24 8 0\&.378 0 0\&.000 0\&.378\fR +.fi +.if n \{\ +.RE +.\} +.SS "Repeat the Column Header String" +.PP +This example attaches to lvmid 21891 and takes samples at 250 millisecond intervals and displays the output as specified by +\fB\-gcnew\fR +option\&. In addition, it uses the +\fB\-h3\fR +option to output the column header after every 3 lines of data\&. +.PP +In addition to showing the repeating header string, this example shows that between the second and third samples, a young GC occurred\&. Its duration was 0\&.001 seconds\&. The collection found enough active data that the survivor space 0 utilization (S0U) would have exceeded the desired survivor Size (DSS)\&. As a result, objects were promoted to the old generation (not visible in this output), and the tenuring threshold (TT) was lowered from 31 to 2\&. +.PP +Another collection occurs between the fifth and sixth samples\&. This collection found very few survivors and returned the tenuring threshold to 31\&. +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcnew \-h3 21891 250\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 0\&.0 31\&.7 31 31 32\&.0 512\&.0 178\&.6 249 0\&.203\fR +\fB 64\&.0 64\&.0 0\&.0 31\&.7 31 31 32\&.0 512\&.0 355\&.5 249 0\&.203\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 21\&.9 250 0\&.204\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 245\&.9 250 0\&.204\fR +\fB 64\&.0 64\&.0 35\&.4 0\&.0 2 31 32\&.0 512\&.0 421\&.1 250 0\&.204\fR +\fB 64\&.0 64\&.0 0\&.0 19\&.0 31 31 32\&.0 512\&.0 84\&.4 251 0\&.204\fR +\fB S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT\fR +\fB 64\&.0 64\&.0 0\&.0 19\&.0 31 31 32\&.0 512\&.0 306\&.7 251 0\&.204\fR + +.fi +.if n \{\ +.RE +.\} +.SS "Include a Time Stamp for Each Sample" +.PP +This example attaches to lvmid 21891 and takes 3 samples at 250 millisecond intervals\&. The +\fB\-t\fR +option is used to generate a time stamp for each sample in the first column\&. +.PP +The Timestamp column reports the elapsed time in seconds since the start of the target JVM\&. In addition, the +\fB\-gcoldcapacity\fR +output shows the old generation capacity (OGC) and the old space capacity (OC) increasing as the heap expands to meet allocation or promotion demands\&. The old generation capacity (OGC) has grown from 11,696 kB to 13,820 kB after the eighty\-first full garbage collection (FGC)\&. The maximum capacity of the generation (and space) is 60,544 kB (OGCMX), so it still has room to expand\&. +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBTimestamp OGCMN OGCMX OGC OC YGC FGC FGCT GCT\fR +\fB 150\&.1 1408\&.0 60544\&.0 11696\&.0 11696\&.0 194 80 2\&.874 3\&.799\fR +\fB 150\&.4 1408\&.0 60544\&.0 13820\&.0 13820\&.0 194 81 2\&.938 3\&.863\fR +\fB 150\&.7 1408\&.0 60544\&.0 13820\&.0 13820\&.0 194 81 2\&.938 3\&.863\fR + +.fi +.if n \{\ +.RE +.\} +.SS "Monitor Instrumentation for a Remote JVM" +.PP +This example attaches to lvmid 40496 on the system named remote\&.domain using the +\fB\-gcutil\fR +option, with samples taken every second indefinitely\&. +.PP +The lvmid is combined with the name of the remote host to construct a +\fIvmid\fR +of +\fB40496@remote\&.domain\fR\&. This vmid results in the use of the +\fBrmi\fR +protocol to communicate to the default +\fBjstatd\fR +server on the remote host\&. The +\fBjstatd\fR +server is located using the +\fBrmiregistry\fR +command on +\fBremote\&.domain\fR +that is bound to the default port of the +\fBrmiregistry\fR +command (port 1099)\&. +.sp +.if n \{\ +.RS 4 +.\} +.nf +\fBjstat \-gcutil 40496@remote\&.domain 1000\fR +\fB\fI\&.\&.\&. output omitted\fR\fR + +.fi +.if n \{\ +.RE +.\} +.SH "SEE ALSO" +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +java(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jps(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +jstatd(1) +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jstatd.1 b/jdk-1.8.0.281/man/man1/jstatd.1 new file mode 100755 index 0000000..070a840 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jstatd.1 @@ -0,0 +1,189 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Monitoring Tools +.\" Title: jstatd.1 +.\" +.if n .pl 99999 +.TH jstatd 1 "21 November 2013" "JDK 8" "Monitoring Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jstatd \- Monitors Java Virtual Machines (JVMs) and enables remote monitoring tools to attach to JVMs\&. This command is experimental and unsupported\&. +.SH SYNOPSIS +.sp +.nf + +\fBjstatd\fR [ \fIoptions\fR ] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.SH DESCRIPTION +The \f3jstatd\fR command is an RMI server application that monitors for the creation and termination of instrumented Java HotSpot VMs and provides an interface to enable remote monitoring tools to attach to JVMs that are running on the local host\&. +.PP +The \f3jstatd\fR server requires an RMI registry on the local host\&. The \f3jstatd\fR server attempts to attach to the RMI registry on the default port, or on the port you specify with the \f3-p\fR\f3port\fR option\&. If an RMI registry is not found, then one is created within the \f3jstatd\fR application that is bound to the port that is indicated by the \f3-p\fR\f3port\fR option or to the default RMI registry port when the \f3-p\fR\f3port\fR option is omitted\&. You can stop the creation of an internal RMI registry by specifying the \f3-nr\fR option\&. +.SH OPTIONS +.TP +-nr +.br +Does not attempt to create an internal RMI registry within the \f3jstatd\fR process when an existing RMI registry is not found\&. +.TP +-p \fIport\fR +.br +The port number where the RMI registry is expected to be found, or when not found, created if the \f3-nr\fR option is not specified\&. +.TP +-n \fIrminame\fR +.br +Name to which the remote RMI object is bound in the RMI registry\&. The default name is \f3JStatRemoteHost\fR\&. If multiple \f3jstatd\fR servers are started on the same host, then the name of the exported RMI object for each server can be made unique by specifying this option\&. However, doing so requires that the unique server name be included in the monitoring client\&'s \f3hostid\fR and \f3vmid\fR strings\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the JVM, where option is one of the \f3options\fR described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH SECURITY +The \f3jstatd\fR server can only monitor JVMs for which it has the appropriate native access permissions\&. Therefore, the \f3jstatd\fR process must be running with the same user credentials as the target JVMs\&. Some user credentials, such as the root user in UNIX-based systems, have permission to access the instrumentation exported by any JVM on the system\&. A \f3jstatd\fR process running with such credentials can monitor any JVM on the system, but introduces additional security concerns\&. +.PP +The \f3jstatd\fR server does not provide any authentication of remote clients\&. Therefore, running a \f3jstatd\fR server process exposes the instrumentation export by all JVMs for which the \f3jstatd\fR process has access permissions to any user on the network\&. This exposure might be undesirable in your environment, and therefore, local security policies should be considered before you start the \f3jstatd\fR process, particularly in production environments or on networks that are not secure\&. +.PP +The \f3jstatd\fR server installs an instance of \f3RMISecurityPolicy\fR when no other security manager is installed, and therefore, requires a security policy file to be specified\&. The policy file must conform to Default Policy Implementation and Policy File Syntax at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html +.PP +The following policy file allows the \f3jstatd\fR server to run without any security exceptions\&. This policy is less liberal than granting all permissions to all code bases, but is more liberal than a policy that grants the minimal permissions to run the \f3jstatd\fR server\&. +.sp +.nf +\f3grant codebase "file:${java\&.home}/\&.\&./lib/tools\&.jar" { \fP +.fi +.nf +\f3 permission java\&.security\&.AllPermission;\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fP +.fi +.sp +To use this policy setting, copy the text into a file called \f3jstatd\&.all\&.policy\fR and run the \f3jstatd\fR server as follows: +.sp +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=jstatd\&.all\&.policy\fP +.fi +.nf +\f3\fP +.fi +.sp +For sites with more restrictive security practices, it is possible to use a custom policy file to limit access to specific trusted hosts or networks, though such techniques are subject to IP address spoofing attacks\&. If your security concerns cannot be addressed with a customized policy file, then the safest action is to not run the \f3jstatd\fR server and use the \f3jstat\fR and \f3jps\fR tools locally\&. +.SH REMOTE\ INTERFACE +The interface exported by the \f3jstatd\fR process is proprietary and guaranteed to change\&. Users and developers are discouraged from writing to this interface\&. +.SH EXAMPLES +The following are examples of the \f3jstatd\fR command\&. The \f3jstatd\fR scripts automatically start the server in the background +.SS INTERNAL\ RMI\ REGISTRY +This example shows hos to start a \f3jstatd\fR session with an internal RMI registry\&. This example assumes that no other server is bound to the default RMI registry port (port 1099)\&. +.sp +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=all\&.policy\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS EXTERNAL\ RMI\ REGISTRY +This example starts a \f3jstatd\fR session with a external RMI registry\&. +.sp +.nf +\f3rmiregistry&\fP +.fi +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=all\&.policy\fP +.fi +.nf +\f3\fP +.fi +.sp +This example starts a \f3jstatd\fR session with an external RMI registry server on port 2020\&. +.sp +.nf +\f3jrmiregistry 2020&\fP +.fi +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=all\&.policy \-p 2020\fP +.fi +.nf +\f3\fP +.fi +.sp +This example starts a \f3jstatd\fR session with an external RMI registry on port 2020 that is bound to \f3AlternateJstatdServerName\fR\&. +.sp +.nf +\f3rmiregistry 2020&\fP +.fi +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=all\&.policy \-p 2020\fP +.fi +.nf +\f3 \-n AlternateJstatdServerName\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS STOP\ THE\ CREATION\ OF\ AN\ IN-PROCESS\ RMI\ REGISTRY +This example starts a \f3jstatd\fR session that does not create an RMI registry when one is not found\&. This example assumes an RMI registry is already running\&. If an RMI registry is not running, then an error message is displayed\&. +.sp +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=all\&.policy \-nr\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS ENABLE\ RMI\ LOGGING +This example starts a \f3jstatd\fR session with RMI logging capabilities enabled\&. This technique is useful as a troubleshooting aid or for monitoring server activities\&. +.sp +.nf +\f3jstatd \-J\-Djava\&.security\&.policy=all\&.policy\fP +.fi +.nf +\f3 \-J\-Djava\&.rmi\&.server\&.logCalls=true\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +jps(1) +.TP 0.2i +\(bu +jstat(1) +.TP 0.2i +\(bu +rmiregistry(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/jvisualvm.1 b/jdk-1.8.0.281/man/man1/jvisualvm.1 new file mode 100755 index 0000000..59746d5 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/jvisualvm.1 @@ -0,0 +1,75 @@ +'\" t +.\" Copyright (c) 2008, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Troubleshooting, Profiling, Monitoring and Management Tools +.\" Title: jvisualvm.1 +.\" +.if n .pl 99999 +.TH jvisualvm 1 "21 November 2013" "JDK 8" "Java Troubleshooting, Profiling, Monitoring and Management Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +jvisualvm \- Visually monitors, troubleshoots, and profiles Java applications\&. +.SH SYNOPSIS +.sp +.nf + +\fBjvisualvm\fR [ \fIoptions\fR ] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.SH DESCRIPTION +Java VisualVM is an intuitive graphical user interface that provides detailed information about Java technology-based applications (Java applications) while they are running on a specified Java Virtual Machine (JVM)\&. The name Java VisualVM comes from the fact that Java VisualVM provides information about the JVM software visually\&. +.PP +Java VisualVM combines several monitoring, troubleshooting, and profiling utilities into a single tool\&. For example, most of the functionality offered by the standalone tools \f3jmap\fR, \f3jinfo\fR, \f3jstat,\fR and \f3jstack\fR were integrated into Java VisualVM\&. Other functionality, such as some that offered by the \f3jconsole\fR command, can be added as optional plug-ins\&. +.PP +Java VisualVM is useful to Java application developers to troubleshoot applications and to monitor and improve the applications\&' performance\&. Java VisualVM enables developers to generate and analyze heap dumps, track down memory leaks, perform and monitor garbage collection, and perform lightweight memory and CPU profiling\&. You can expand the Java VisualVM functionality with plug-ins\&. For example, most of the functionality of the \f3jconsole\fR command is available through the \fIMBeans\fR Tab and JConsole Plug-in Wrapper plug-ins\&. You can choose from a catalog of standard Java VisualVM plug-ins by selecting \fITools\fR and then \fIPlugins\fR in the Java VisualVM menus\&. +.PP +Start Java VisualVM with the following command: +.sp +.nf +\f3% jvisualvm <options>\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +The following option is available when you launch Java VisualVM +.TP +-J\fIjvm_option\fR +.br +Pass this \f3jvm_option\fR to the JVM software +.SH SEE\ ALSO +.TP 0.2i +\(bu +Java VisualVM developer\(cqs site http://visualvm\&.java\&.net/ +.TP 0.2i +\(bu +Java VisualVM in Java SE documentation http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/visualvm/index\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/keytool.1 b/jdk-1.8.0.281/man/man1/keytool.1 new file mode 100755 index 0000000..03f1fbd --- /dev/null +++ b/jdk-1.8.0.281/man/man1/keytool.1 @@ -0,0 +1,1593 @@ +'\" t +.\" Copyright (c) 1998, 2020, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 31 August 2020 +.\" SectDesc: Security Tools +.\" Title: keytool.1 +.\" +.if n .pl 99999 +.TH keytool 1 "31 August 2020" "JDK 8" "Security Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +keytool \- Manages a keystore (database) of cryptographic keys, X\&.509 certificate chains, and trusted certificates\&. +.SH SYNOPSIS +.sp +.nf + +\fBkeytool\fR [\fIcommands\fR] +.fi +.sp +.TP +\fIcommands\fR +See Commands\&. These commands are categorized by task as follows: +.RS +.TP 0.2i +\(bu +Create or Add Data to the Keystore +.RS +.TP 0.2i +\(bu +-gencert +.TP 0.2i +\(bu +-genkeypair +.TP 0.2i +\(bu +-genseckey +.TP 0.2i +\(bu +-importcert +.TP 0.2i +\(bu +-importpassword +.RE + +.TP 0.2i +\(bu +Import Contents From Another Keystore +.RS +.TP 0.2i +\(bu +-importkeystore +.RE + +.TP 0.2i +\(bu +Generate Certificate Request +.RS +.TP 0.2i +\(bu +-certreq +.RE + +.TP 0.2i +\(bu +Export Data +.RS +.TP 0.2i +\(bu +-exportcert +.RE + +.TP 0.2i +\(bu +Display Data +.RS +.TP 0.2i +\(bu +-list +.TP 0.2i +\(bu +-printcert +.TP 0.2i +\(bu +-printcertreq +.TP 0.2i +\(bu +-printcrl +.RE + +.TP 0.2i +\(bu +Manage the Keystore +.RS +.TP 0.2i +\(bu +-storepasswd +.TP 0.2i +\(bu +-keypasswd +.TP 0.2i +\(bu +-delete +.TP 0.2i +\(bu +-changealias +.RE + +.TP 0.2i +\(bu +Get Help +.RS +.TP 0.2i +\(bu +-help +.RE + +.RE + +.SH DESCRIPTION +The \f3keytool\fR command is a key and certificate management utility\&. It enables users to administer their own public/private key pairs and associated certificates for use in self-authentication (where the user authenticates himself or herself to other users and services) or data integrity and authentication services, using digital signatures\&. The \f3keytool\fR command also enables users to cache the public keys (in the form of certificates) of their communicating peers\&. +.PP +A certificate is a digitally signed statement from one entity (person, company, and so on\&.), that says that the public key (and some other information) of some other entity has a particular value\&. (See Certificate\&.) When data is digitally signed, the signature can be verified to check the data integrity and authenticity\&. Integrity means that the data has not been modified or tampered with, and authenticity means the data comes from whoever claims to have created and signed it\&. +.PP +The \f3keytool\fR command also enables users to administer secret keys and passphrases used in symmetric encryption and decryption (DES)\&. +.PP +The \f3keytool\fR command stores the keys and certificates in a keystore\&. See KeyStore aliases\&. +.SH COMMAND\ AND\ OPTION\ NOTES +See Commands for a listing and description of the various commands\&. +.TP 0.2i +\(bu +All command and option names are preceded by a minus sign (-)\&. +.TP 0.2i +\(bu +The options for each command can be provided in any order\&. +.TP 0.2i +\(bu +All items not italicized or in braces or brackets are required to appear as is\&. +.TP 0.2i +\(bu +Braces surrounding an option signify that a default value will be used when the option is not specified on the command line\&. See Option Defaults\&. Braces are also used around the \f3-v\fR, \f3-rfc\fR, and \f3-J\fR options, which only have meaning when they appear on the command line\&. They do not have any default values other than not existing\&. +.TP 0.2i +\(bu +Brackets surrounding an option signify that the user is prompted for the values when the option is not specified on the command line\&. For the \f3-keypass\fR option, if you do not specify the option on the command line, then the \f3keytool\fR command first attempts to use the keystore password to recover the private/secret key\&. If this attempt fails, then the \f3keytool\fR command prompts you for the private/secret key password\&. +.TP 0.2i +\(bu +Items in italics (option values) represent the actual values that must be supplied\&. For example, here is the format of the \f3-printcert\fR command: +.sp +.nf +\f3keytool \-printcert {\-file \fIcert_file\fR} {\-v}\fP +.fi +.sp + + + + +When you specify a \f3-printcert\fR command, replace \fIcert_file\fR with the actual file name, as follows: \f3keytool -printcert -file VScert\&.cer\fR +.TP 0.2i +\(bu +Option values must be put in quotation marks when they contain a blank (space)\&. +.TP 0.2i +\(bu +The \f3-help\fR option is the default\&. The \f3keytool\fR command is the same as \f3keytool -help\fR\&. +.SH OPTION\ DEFAULTS +The following examples show the defaults for various option values\&. +.sp +.nf +\f3\-alias "mykey"\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-keyalg\fP +.fi +.nf +\f3 "DSA" (when using \-genkeypair)\fP +.fi +.nf +\f3 "DES" (when using \-genseckey)\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-keysize\fP +.fi +.nf +\f3 2048 (when using \-genkeypair and \-keyalg is "RSA")\fP +.fi +.nf +\f3 1024 (when using \-genkeypair and \-keyalg is "DSA")\fP +.fi +.nf +\f3 256 (when using \-genkeypair and \-keyalg is "EC")\fP +.fi +.nf +\f3 56 (when using \-genseckey and \-keyalg is "DES")\fP +.fi +.nf +\f3 168 (when using \-genseckey and \-keyalg is "DESede")\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-validity 90\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-keystore <the file named \&.keystore in the user\&'s home directory>\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-storetype <the value of the "keystore\&.type" property in the\fP +.fi +.nf +\f3 security properties file, which is returned by the static\fP +.fi +.nf +\f3 getDefaultType method in java\&.security\&.KeyStore>\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-file\fP +.fi +.nf +\f3 stdin (if reading)\fP +.fi +.nf +\f3 stdout (if writing)\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-protected false\fP +.fi +.nf +\f3\fP +.fi +.sp +In generating a public/private key pair, the signature algorithm (\f3-sigalg\fR option) is derived from the algorithm of the underlying private key: +.TP 0.2i +\(bu +If the underlying private key is of type DSA, then the \f3-sigalg\fR option defaults to SHA256withDSA\&. +.TP 0.2i +\(bu +If the underlying private key is of type RSA, then the \f3-sigalg\fR option defaults to SHA256withRSA\&. +.TP 0.2i +\(bu +If the underlying private key is of type EC, then the \f3-sigalg\fR option defaults to SHA256withECDSA\&. +.PP +For a full list of \f3-keyalg\fR and \f3-sigalg\fR arguments, see Java Cryptography Architecture (JCA) Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html#AppA +.SH COMMON\ OPTIONS +The \f3-v\fR option can appear for all commands except \f3-help\fR\&. When the \f3-v\fR option appears, it signifies verbose mode, which means that more information is provided in the output\&. +.PP +There is also a \f3-Jjavaoption\fR argument that can appear for any command\&. When the \f3-Jjavaoption\fR appears, the specified \f3javaoption\fR string is passed directly to the Java interpreter\&. This option does not contain any spaces\&. It is useful for adjusting the execution environment or memory usage\&. For a list of possible interpreter options, type \f3java -h\fR or \f3java -X\fR at the command line\&. +.PP +These options can appear for all commands operating on a keystore: +.TP +-storetype \fIstoretype\fR +.br +This qualifier specifies the type of keystore to be instantiated\&. +.TP +-keystore \fIkeystore\fR +.br +The keystore location\&. + +If the JKS \f3storetype\fR is used and a keystore file does not yet exist, then certain \f3keytool\fR commands can result in a new keystore file being created\&. For example, if \f3keytool -genkeypair\fR is called and the \f3-keystore\fR option is not specified, the default keystore file named \f3\&.keystore\fR in the user\&'s home directory is created when it does not already exist\&. Similarly, if the \f3-keystore ks_file\fR option is specified but ks_file does not exist, then it is created\&. For more information on the JKS \f3storetype\fR, see the \fIKeyStore Implementation\fR section in KeyStore aliases\&. + +Note that the input stream from the \f3-keystore\fR option is passed to the \f3KeyStore\&.load\fR method\&. If \f3NONE\fR is specified as the URL, then a null stream is passed to the \f3KeyStore\&.load\fR method\&. \f3NONE\fR should be specified if the keystore is not file-based\&. For example, when it resides on a hardware token device\&. +.TP +-storepass[:\fIenv\fR| :\fIfile\fR] argument +.br +The password that is used to protect the integrity of the keystore\&. + +If the modifier \f3env\fR or \f3file\fR is not specified, then the password has the \f3value\fR argument, which must be at least 6 characters long\&. Otherwise, the password is retrieved as follows: +.RS +.TP 0.2i +\(bu +\f3env\fR: Retrieve the password from the environment variable named \f3argument\fR\&. +.TP 0.2i +\(bu +\f3file\fR: Retrieve the password from the file named argument\&. +.RE + + +\fINote:\fR All other options that require passwords, such as \f3-keypass\fR, \f3-srckeypass\fR, -\f3destkeypass\fR, \f3-srcstorepass\fR, and \f3-deststorepass\fR, accept the \fIenv\fR and \fIfile\fR modifiers\&. Remember to separate the password option and the modifier with a colon (:)\&. + +The password must be provided to all commands that access the keystore contents\&. For such commands, when the \f3-storepass\fR option is not provided at the command line, the user is prompted for it\&. + +When retrieving information from the keystore, the password is optional\&. If no password is specified, then the integrity of the retrieved information cannot be verified and a warning is displayed\&. +.TP +-providerName \fIprovider_name\fR +.br +Used to identify a cryptographic service provider\&'s name when listed in the security properties file\&. +.TP +-providerClass \fIprovider_class_name\fR +.br +Used to specify the name of a cryptographic service provider\&'s master class file when the service provider is not listed in the security properties file\&. +.TP +-providerArg \fIprovider_arg\fR +.br +Used with the \f3-providerClass\fR option to represent an optional string input argument for the constructor of \f3provider_class_name\fR\&. +.TP +-protected +.br +Either \f3true\fR or \f3false\fR\&. This value should be specified as \f3true\fR when a password must be specified by way of a protected authentication path such as a dedicated PIN reader\&.Because there are two keystores involved in the \f3-importkeystore\fR command, the following two options \f3-srcprotected\fR and -\f3destprotected\fR are provided for the source keystore and the destination keystore respectively\&. +.TP +-ext \fI{name{:critical} {=value}}\fR +.br +Denotes an X\&.509 certificate extension\&. The option can be used in \f3-genkeypair\fR and \f3-gencert\fR to embed extensions into the certificate generated, or in \f3-certreq\fR to show what extensions are requested in the certificate request\&. The option can appear multiple times\&. The \f3name\fR argument can be a supported extension name (see Named Extensions) or an arbitrary OID number\&. The \f3value\fR argument, when provided, denotes the argument for the extension\&. When \fIvalue\fR is omitted, that means that the default value of the extension or the extension requires no argument\&. The \f3:critical\fR modifier, when provided, means the extension\&'s \f3isCritical\fR attribute is \f3true\fR; otherwise, it is \f3false\fR\&. You can use \f3:c\fR in place of \f3:critical\fR\&. +.SH NAMED\ EXTENSIONS +The \f3keytool\fR command supports these named extensions\&. The names are not case-sensitive)\&. +.TP +BC or BasicContraints +\fIValues\fR: The full form is: \f3ca:{true|false}[,pathlen:<len>]\fR or \f3<len>\fR, which is short for \f3ca:true,pathlen:<len>\fR\&. When <\f3len\fR> is omitted, you have \f3ca:true\fR\&. +.TP +KU or KeyUsage +\fIValues\fR: \f3usage\fR(,\f3usage\fR)*, where \fIusage\fR can be one of \f3digitalSignature\fR, \f3nonRepudiation\fR (contentCommitment), \f3keyEncipherment\fR, \f3dataEncipherment\fR, \f3keyAgreement\fR, \f3keyCertSign\fR, \f3cRLSign\fR, \f3encipherOnly\fR, \f3decipherOnly\fR\&. The \fIusage\fR argument can be abbreviated with the first few letters (\f3dig\fR for \f3digitalSignature\fR) or in camel-case style (\f3dS\fR for \f3digitalSignature\fR or \f3cRLS\fR for \f3cRLSign\fR), as long as no ambiguity is found\&. The \f3usage\fR values are case-sensitive\&. +.TP +EKU or ExtendedKeyUsage +\fIValues\fR: \f3usage\fR(,\f3usage\fR)*, where \fIusage\fR can be one of \f3anyExtendedKeyUsage\fR, \f3serverAuth\fR, \f3clientAuth\fR, \f3codeSigning\fR, \f3emailProtection\fR, \f3timeStamping\fR, \f3OCSPSigning\fR, or any \fIOID string\fR\&. The \fIusage\fR argument can be abbreviated with the first few letters or in camel-case style, as long as no ambiguity is found\&. The \f3usage\fR values are case-sensitive\&. +.TP +SAN or SubjectAlternativeName +\fIValues\fR: \f3type\fR:\f3value\fR(,t\f3ype:value\fR)*, where \f3type\fR can be \f3EMAIL\fR, \f3URI\fR, \f3DNS\fR, \f3IP\fR, or \f3OID\fR\&. The \f3value\fR argument is the string format value for the \f3type\fR\&. +.TP +IAN or IssuerAlternativeName +\fIValues\fR: Same as \f3SubjectAlternativeName\fR\&. +.TP +SIA or SubjectInfoAccess +\fIValues\fR: \f3method\fR:\f3location-type\fR:\f3location-value\fR (,\f3method:location-type\fR:\f3location-value\fR)*, where \f3method\fR can be \f3timeStamping\fR, \f3caRepository\fR or any OID\&. The \f3location-type\fR and \f3location-value\fR arguments can be any \f3type\fR:\f3value\fR supported by the \f3SubjectAlternativeName\fR extension\&. +.TP +AIA or AuthorityInfoAccess +\fIValues\fR: Same as \f3SubjectInfoAccess\fR\&. The \f3method\fR argument can be \f3ocsp\fR,\f3caIssuers\fR, or any OID\&. +.PP +When \f3name\fR is OID, the value is the hexadecimal dumped DER encoding of the \f3extnValue\fR for the extension excluding the OCTET STRING type and length bytes\&. Any extra character other than standard hexadecimal numbers (0-9, a-f, A-F) are ignored in the HEX string\&. Therefore, both 01:02:03:04 and 01020304 are accepted as identical values\&. When there is no value, the extension has an empty value field\&. +.PP +A special name \f3honored\fR, used in \f3-gencert\fR only, denotes how the extensions included in the certificate request should be honored\&. The value for this name is a comma separated list of \f3all\fR (all requested extensions are honored), \f3name{:[critical|non-critical]}\fR (the named extension is honored, but using a different \f3isCritical\fR attribute) and \f3-name\fR (used with \f3all\fR, denotes an exception)\&. Requested extensions are not honored by default\&. +.PP +If, besides the\f3-ext honored\fR option, another named or OID \f3-ext\fR option is provided, this extension is added to those already honored\&. However, if this name (or OID) also appears in the honored value, then its value and criticality overrides the one in the request\&. +.PP +The \f3subjectKeyIdentifier\fR extension is always created\&. For non-self-signed certificates, the \f3authorityKeyIdentifier\fR is created\&. +.PP +\fINote:\fR Users should be aware that some combinations of extensions (and other certificate fields) may not conform to the Internet standard\&. See Certificate Conformance Warning\&. +.SH COMMANDS +.TP +-gencert +.sp +.nf +\f3{\-rfc} {\-infile \fIinfile\fR} {\-outfile \fIoutfile\fR} {\-alias \fIalias\fR} {\-sigalg \fIsigalg\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-dname \fIdname\fR} {\-startdate \fIstartdate\fR {\-ext \fIext\fR}* {\-validity \fIvalDays\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-keypass \fIkeypass\fR] {\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-storetype \fIstoretype\fR} {\-providername \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Generates a certificate as a response to a certificate request file (which can be created by the \f3keytool\fR\f3-certreq\fR command)\&. The command reads the request from \fIinfile\fR (if omitted, from the standard input), signs it using alias\&'s private key, and outputs the X\&.509 certificate into \fIoutfile\fR (if omitted, to the standard output)\&. When\f3-rfc\fR is specified, the output format is Base64-encoded PEM; otherwise, a binary DER is created\&. + +The \f3sigalg\fR value specifies the algorithm that should be used to sign the certificate\&. The \f3startdate\fR argument is the start time and date that the certificate is valid\&. The \f3valDays\fR argument tells the number of days for which the certificate should be considered valid\&. + +When \f3dname\fR is provided, it is used as the subject of the generated certificate\&. Otherwise, the one from the certificate request is used\&. + +The \f3ext\fR value shows what X\&.509 extensions will be embedded in the certificate\&. Read Common Options for the grammar of \f3-ext\fR\&. + +The \f3-gencert\fR option enables you to create certificate chains\&. The following example creates a certificate, \f3e1\fR, that contains three certificates in its certificate chain\&. + +The following commands creates four key pairs named \f3ca\fR, \f3ca1\fR, \f3ca2\fR, and \f3e1\fR: +.sp +.nf +\f3keytool \-alias ca \-dname CN=CA \-genkeypair\fP +.fi +.nf +\f3keytool \-alias ca1 \-dname CN=CA \-genkeypair\fP +.fi +.nf +\f3keytool \-alias ca2 \-dname CN=CA \-genkeypair\fP +.fi +.nf +\f3keytool \-alias e1 \-dname CN=E1 \-genkeypair\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following two commands create a chain of signed certificates; \f3ca\fR signs \f3ca1\fR and \f3ca1\fR signs \f3ca2\fR, all of which are self-issued: +.sp +.nf +\f3keytool \-alias ca1 \-certreq |\fP +.fi +.nf +\f3 keytool \-alias ca \-gencert \-ext san=dns:ca1 |\fP +.fi +.nf +\f3 keytool \-alias ca1 \-importcert\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3keytool \-alias ca2 \-certreq |\fP +.fi +.nf +\f3 $KT \-alias ca1 \-gencert \-ext san=dns:ca2 |\fP +.fi +.nf +\f3 $KT \-alias ca2 \-importcert\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following command creates the certificate \f3e1\fR and stores it in the file \f3e1\&.cert\fR, which is signed by \f3ca2\fR\&. As a result, \f3e1\fR should contain \f3ca\fR, \f3ca1\fR, and \f3ca2\fR in its certificate chain: +.sp +.nf +\f3keytool \-alias e1 \-certreq | keytool \-alias ca2 \-gencert > e1\&.cert\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-genkeypair +.sp +.nf +\f3{\-alias \fIalias\fR} {\-keyalg \fIkeyalg\fR} {\-keysize \fIkeysize\fR} {\-sigalg \fIsigalg\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-dname \fIdname\fR] [\-keypass \fIkeypass\fR] {\-startdate \fIvalue\fR} {\-ext \fIext\fR}*\fP +.fi +.sp +.sp +.nf +\f3{\-validity \fIvalDays\fR} {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Generates a key pair (a public key and associated private key)\&. Wraps the public key into an X\&.509 v3 self-signed certificate, which is stored as a single-element certificate chain\&. This certificate chain and the private key are stored in a new keystore entry identified by alias\&. + +The \f3keyalg\fR value specifies the algorithm to be used to generate the key pair, and the \f3keysize\fR value specifies the size of each key to be generated\&. The \f3sigalg\fR value specifies the algorithm that should be used to sign the self-signed certificate\&. This algorithm must be compatible with the \f3keyalg\fR value\&. + +The \f3dname\fR value specifies the X\&.500 Distinguished Name to be associated with the value of \f3alias\fR, and is used as the issuer and subject fields in the self-signed certificate\&. If no distinguished name is provided at the command line, then the user is prompted for one\&. + +The value of \f3keypass\fR is a password used to protect the private key of the generated key pair\&. If no password is provided, then the user is prompted for it\&. If you press \fIthe Return key\fR at the prompt, then the key password is set to the same password as the keystore password\&. The \f3keypass\fR value must be at least 6 characters\&. + +The value of \f3startdate\fR specifies the issue time of the certificate, also known as the "Not Before" value of the X\&.509 certificate\&'s Validity field\&. + +The option value can be set in one of these two forms: + +\f3([+-]nnn[ymdHMS])+\fR + +\f3[yyyy/mm/dd] [HH:MM:SS]\fR + +With the first form, the issue time is shifted by the specified value from the current time\&. The value is a concatenation of a sequence of subvalues\&. Inside each subvalue, the plus sign (+) means shift forward, and the minus sign (-) means shift backward\&. The time to be shifted is \f3nnn\fR units of years, months, days, hours, minutes, or seconds (denoted by a single character of \f3y\fR, \f3m\fR, \f3d\fR, \f3H\fR, \f3M\fR, or \f3S\fR respectively)\&. The exact value of the issue time is calculated using the \f3java\&.util\&.GregorianCalendar\&.add(int field, int amount)\fR method on each subvalue, from left to right\&. For example, by specifying, the issue time will be: +.sp +.nf +\f3Calendar c = new GregorianCalendar();\fP +.fi +.nf +\f3c\&.add(Calendar\&.YEAR, \-1);\fP +.fi +.nf +\f3c\&.add(Calendar\&.MONTH, 1);\fP +.fi +.nf +\f3c\&.add(Calendar\&.DATE, \-1);\fP +.fi +.nf +\f3return c\&.getTime()\fP +.fi +.nf +\f3\fP +.fi +.sp + + +With the second form, the user sets the exact issue time in two parts, year/month/day and hour:minute:second (using the local time zone)\&. The user can provide only one part, which means the other part is the same as the current date (or time)\&. The user must provide the exact number of digits as shown in the format definition (padding with 0 when shorter)\&. When both the date and time are provided, there is one (and only one) space character between the two parts\&. The hour should always be provided in 24 hour format\&. + +When the option is not provided, the start date is the current time\&. The option can be provided at most once\&. + +The value of \f3valDays\fR specifies the number of days (starting at the date specified by \f3-startdate\fR, or the current date when \f3-startdate\fR is not specified) for which the certificate should be considered valid\&. + +This command was named \f3-genkey\fR in earlier releases\&. The old name is still supported in this release\&. The new name, \f3-genkeypair\fR, is preferred going forward\&. +.TP +-genseckey +.sp +.nf +\f3{\-alias \fIalias\fR} {\-keyalg \fIkeyalg\fR} {\-keysize \fIkeysize\fR} [\-keypass \fIkeypass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}} {\-v}\fP +.fi +.sp +.sp +.nf +\f3{\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Generates a secret key and stores it in a new \f3KeyStore\&.SecretKeyEntry\fR identified by \f3alias\fR\&. + +The value of \f3keyalg\fR specifies the algorithm to be used to generate the secret key, and the value of \f3keysize\fR specifies the size of the key to be generated\&. The \f3keypass\fR value is a password that protects the secret key\&. If no password is provided, then the user is prompted for it\&. If you press the Return key at the prompt, then the key password is set to the same password that is used for the \f3keystore\fR\&. The \f3keypass\fR value must be at least 6 characters\&. +.TP +-importcert +.sp +.nf +\f3{\-alias \fIalias\fR} {\-file \fIcert_file\fR} [\-keypass \fIkeypass\fR] {\-noprompt} {\-trustcacerts}\fP +.fi +.sp +.sp +.nf +\f3{\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Reads the certificate or certificate chain (where the latter is supplied in a PKCS#7 formatted reply or a sequence of X\&.509 certificates) from the file \f3cert_file\fR, and stores it in the \f3keystore\fR entry identified by \f3alias\fR\&. If no file is specified, then the certificate or certificate chain is read from \f3stdin\fR\&. + +The \f3keytool\fR command can import X\&.509 v1, v2, and v3 certificates, and PKCS#7 formatted certificate chains consisting of certificates of that type\&. The data to be imported must be provided either in binary encoding format or in printable encoding format (also known as Base64 encoding) as defined by the Internet RFC 1421 standard\&. In the latter case, the encoding must be bounded at the beginning by a string that starts with \f3-\fR\f3----BEGIN\fR, and bounded at the end by a string that starts with \f3-----END\fR\&. + +You import a certificate for two reasons: To add it to the list of trusted certificates, and to import a certificate reply received from a certificate authority (CA) as the result of submitting a Certificate Signing Request to that CA (see the \f3-certreq\fR option in Commands)\&. + +Which type of import is intended is indicated by the value of the \f3-alias\fR option\&. If the alias does not point to a key entry, then the \f3keytool\fR command assumes you are adding a trusted certificate entry\&. In this case, the alias should not already exist in the keystore\&. If the alias does already exist, then the \f3keytool\fR command outputs an error because there is already a trusted certificate for that alias, and does not import the certificate\&. If the alias points to a key entry, then the \f3keytool\fR command assumes you are importing a certificate reply\&. +.TP +-importpassword +.sp +.nf +\f3{\-alias \fIalias\fR} [\-keypass \fIkeypass\fR] {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Imports a passphrase and stores it in a new \f3KeyStore\&.SecretKeyEntry\fR identified by \f3alias\fR\&. The passphrase may be supplied via the standard input stream; otherwise the user is prompted for it\&. \f3keypass\fR is a password used to protect the imported passphrase\&. If no password is provided, the user is prompted for it\&. If you press the Return key at the prompt, the key password is set to the same password as that used for the \f3keystore\fR\&. \f3keypass\fR must be at least 6 characters long\&. +.TP +-importkeystore +.sp +.nf +\f3{\-srcstoretype \fIsrcstoretype\fR} {\-deststoretype \fIdeststoretype\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-srcstorepass \fIsrcstorepass\fR] [\-deststorepass \fIdeststorepass\fR] {\-srcprotected}\fP +.fi +.sp +.sp +.nf +\f3{\-destprotected} \fP +.fi +.sp +.sp +.nf +\f3{\-srcalias \fIsrcalias\fR {\-destalias \fIdestalias\fR} [\-srckeypass \fIsrckeypass\fR]} \fP +.fi +.sp +.sp +.nf +\f3[\-destkeypass \fIdestkeypass\fR] {\-noprompt}\fP +.fi +.sp +.sp +.nf +\f3{\-srcProviderName \fIsrc_provider_name\fR} {\-destProviderName \fIdest_provider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}} {\-v}\fP +.fi +.sp +.sp +.nf +\f3{\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Imports a single entry or all entries from a source keystore to a destination keystore\&. + +When the \f3-srcalias\fR option is provided, the command imports the single entry identified by the alias to the destination keystore\&. If a destination alias is not provided with \f3destalias\fR, then \f3srcalias\fR is used as the destination alias\&. If the source entry is protected by a password, then \f3srckeypass\fR is used to recover the entry\&. If \fIsrckeypass\fR is not provided, then the \f3keytool\fR command attempts to use \f3srcstorepass\fR to recover the entry\&. If \f3srcstorepass\fR is either not provided or is incorrect, then the user is prompted for a password\&. The destination entry is protected with \f3destkeypass\fR\&. If \f3destkeypass\fR is not provided, then the destination entry is protected with the source entry password\&. For example, most third-party tools require \f3storepass\fR and \f3keypass\fR in a PKCS #12 keystore to be the same\&. In order to create a PKCS #12 keystore for these tools, always specify a \f3-destkeypass\fR to be the same as \f3-deststorepass\fR\&. + +If the \f3-srcalias\fR option is not provided, then all entries in the source keystore are imported into the destination keystore\&. Each destination entry is stored under the alias from the source entry\&. If the source entry is protected by a password, then \f3srcstorepass\fR is used to recover the entry\&. If \f3srcstorepass\fR is either not provided or is incorrect, then the user is prompted for a password\&. If a source keystore entry type is not supported in the destination keystore, or if an error occurs while storing an entry into the destination keystore, then the user is prompted whether to skip the entry and continue or to quit\&. The destination entry is protected with the source entry password\&. + +If the destination alias already exists in the destination keystore, then the user is prompted to either overwrite the entry or to create a new entry under a different alias name\&. + +If the \f3-noprompt\fR option is provided, then the user is not prompted for a new destination alias\&. Existing entries are overwritten with the destination alias name\&. Entries that cannot be imported are skipped and a warning is displayed\&. +.TP +-printcertreq +.sp +.nf +\f3{\-file \fIfile\fR}\fP +.fi +.sp + + +Prints the content of a PKCS #10 format certificate request, which can be generated by the \f3keytool\fR\f3-certreq\fR command\&. The command reads the request from file\&. If there is no file, then the request is read from the standard input\&. +.TP +-certreq +.sp +.nf +\f3{\-alias \fIalias\fR} {\-dname \fIdname\fR} {\-sigalg \fIsigalg\fR} {\-file \fIcertreq_file\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-keypass \fIkeypass\fR] {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-storepass \fIstorepass\fR] {\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Generates a Certificate Signing Request (CSR) using the PKCS #10 format\&. + +A CSR is intended to be sent to a certificate authority (CA)\&. The CA authenticates the certificate requestor (usually off-line) and will return a certificate or certificate chain, used to replace the existing certificate chain (which initially consists of a self-signed certificate) in the keystore\&. + +The private key associated with alias is used to create the PKCS #10 certificate request\&. To access the private key, the correct password must be provided\&. If \f3keypass\fR is not provided at the command line and is different from the password used to protect the integrity of the keystore, then the user is prompted for it\&. If \f3dname\fR is provided, then it is used as the subject in the CSR\&. Otherwise, the X\&.500 Distinguished Name associated with alias is used\&. + +The \f3sigalg\fR value specifies the algorithm that should be used to sign the CSR\&. + +The CSR is stored in the file certreq_file\&. If no file is specified, then the CSR is output to \f3stdout\fR\&. + +Use the \f3importcert\fR command to import the response from the CA\&. +.TP +-exportcert +.sp +.nf +\f3{\-alias \fIalias\fR} {\-file \fIcert_file\fR} {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-storepass \fIstorepass\fR] {\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-rfc} {\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Reads from the keystore the certificate associated with \fIalias\fR and stores it in the cert_file file\&. When no file is specified, the certificate is output to \f3stdout\fR\&. + +The certificate is by default output in binary encoding\&. If the \f3-rfc\fR option is specified, then the output in the printable encoding format defined by the Internet RFC 1421 Certificate Encoding Standard\&. + +If \f3alias\fR refers to a trusted certificate, then that certificate is output\&. Otherwise, \f3alias\fR refers to a key entry with an associated certificate chain\&. In that case, the first certificate in the chain is returned\&. This certificate authenticates the public key of the entity addressed by \f3alias\fR\&. + +This command was named \f3-export\fR in earlier releases\&. The old name is still supported in this release\&. The new name, \f3-exportcert\fR, is preferred going forward\&. +.TP +-list +.sp +.nf +\f3{\-alias \fIalias\fR} {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v | \-rfc} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Prints to \f3stdout\fR the contents of the keystore entry identified by \f3alias\fR\&. If no \f3alias\fR is specified, then the contents of the entire keystore are printed\&. + +This command by default prints the SHA256 fingerprint of a certificate\&. If the \f3-v\fR option is specified, then the certificate is printed in human-readable format, with additional information such as the owner, issuer, serial number, and any extensions\&. If the \f3-rfc\fR option is specified, then the certificate contents are printed using the printable encoding format, as defined by the Internet RFC 1421 Certificate Encoding Standard\&. + +You cannot specify both \f3-v\fR and \f3-rfc\fR\&. +.TP +-printcert +.sp +.nf +\f3{\-file \fIcert_file\fR | \-sslserver \fIhost\fR[:\fIport\fR]} {\-jarfile \fIJAR_file\fR {\-rfc} {\-v}\fP +.fi +.sp +.sp +.nf +\f3{\-Jjavaoption}\fP +.fi +.sp + + +Reads the certificate from the file cert_file, the SSL server located at host:port, or the signed JAR file \f3JAR_file\fR (with the \f3-jarfile\fR option and prints its contents in a human-readable format\&. When no port is specified, the standard HTTPS port 443 is assumed\&. Note that \f3-sslserver\fR and -file options cannot be provided at the same time\&. Otherwise, an error is reported\&. If neither option is specified, then the certificate is read from \f3stdin\fR\&. + +When\f3-rfc\fR is specified, the \f3keytool\fR command prints the certificate in PEM mode as defined by the Internet RFC 1421 Certificate Encoding standard\&. See Internet RFC 1421 Certificate Encoding Standard\&. + +If the certificate is read from a file or \f3stdin\fR, then it might be either binary encoded or in printable encoding format, as defined by the RFC 1421 Certificate Encoding standard\&. + +If the SSL server is behind a firewall, then the \f3-J-Dhttps\&.proxyHost=proxyhost\fR and \f3-J-Dhttps\&.proxyPort=proxyport\fR options can be specified on the command line for proxy tunneling\&. See Java Secure Socket Extension (JSSE) Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide\&.html + +\fINote:\fR This option can be used independently of a keystore\&. +.TP +-printcrl +.sp +.nf +\f3\-file \fIcrl_\fR {\-v}\fP +.fi +.sp + + +Reads the Certificate Revocation List (CRL) from the file \f3crl_\fR\&. A CRL is a list of digital certificates that were revoked by the CA that issued them\&. The CA generates the \f3crl_\fR file\&. + +\fINote:\fR This option can be used independently of a keystore\&. +.TP +-storepasswd +.sp +.nf +\f3[\-new \fInew_storepass\fR] {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR}\fP +.fi +.sp +.sp +.nf +\f3[\-storepass \fIstorepass\fR] {\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-Jjavaoption}\fP +.fi +.sp + + +Changes the password used to protect the integrity of the keystore contents\&. The new password is \f3new_storepass\fR, which must be at least 6 characters\&. +.TP +-keypasswd +.sp +.nf +\f3{\-alias \fIalias\fR} [\-keypass \fIold_keypass\fR] [\-new \fInew_keypass\fR] {\-storetype \fIstoretype\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR] {\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}} {\-v}\fP +.fi +.sp +.sp +.nf +\f3{\-Jjavaoption}\fP +.fi +.sp + + +Changes the password under which the private/secret key identified by \f3alias\fR is protected, from \f3old_keypass\fR to \f3new_keypass\fR, which must be at least 6 characters\&. + +If the \f3-keypass\fR option is not provided at the command line, and the key password is different from the keystore password, then the user is prompted for it\&. + +If the \f3-new\fR option is not provided at the command line, then the user is prompted for it +.TP +-delete +.sp +.nf +\f3[\-alias \fIalias\fR] {\-storetype \fIstoretype\fR} {\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR]\fP +.fi +.sp +.sp +.nf +\f3{\-providerName \fIprovider_name\fR} \fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}}\fP +.fi +.sp +.sp +.nf +\f3{\-v} {\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Deletes from the keystore the entry identified by \f3alias\fR\&. The user is prompted for the alias, when no alias is provided at the command line\&. +.TP +-changealias +.sp +.nf +\f3{\-alias \fIalias\fR} [\-destalias \fIdestalias\fR] [\-keypass \fIkeypass\fR] {\-storetype \fIstoretype\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-keystore \fIkeystore\fR} [\-storepass \fIstorepass\fR] {\-providerName \fIprovider_name\fR}\fP +.fi +.sp +.sp +.nf +\f3{\-providerClass \fIprovider_class_name\fR {\-providerArg \fIprovider_arg\fR}} {\-v}\fP +.fi +.sp +.sp +.nf +\f3{\-protected} {\-Jjavaoption}\fP +.fi +.sp + + +Move an existing keystore entry from the specified \f3alias\fR to a new alias, \f3destalias\fR\&. If no destination alias is provided, then the command prompts for one\&. If the original entry is protected with an entry password, then the password can be supplied with the \f3-keypass\fR option\&. If no key password is provided, then the \f3storepass\fR (if provided) is attempted first\&. If the attempt fails, then the user is prompted for a password\&. +.TP +-help +.br +Lists the basic commands and their options\&. + +For more information about a specific command, enter the following, where \f3command_name\fR is the name of the command: \f3keytool -command_name -help\fR\&. +.SH EXAMPLES +This example walks through the sequence of steps to create a keystore for managing public/private key pair and certificates from trusted entities\&. +.SS GENERATE\ THE\ KEY\ PAIR +First, create a keystore and generate the key pair\&. You can use a command such as the following typed as a single line: +.sp +.nf +\f3keytool \-genkeypair \-dname "cn=Mark Jones, ou=Java, o=Oracle, c=US"\fP +.fi +.nf +\f3 \-alias business \-keypass <new password for private key>\fP +.fi +.nf +\f3 \-keystore /working/mykeystore\fP +.fi +.nf +\f3 \-storepass <new password for keystore> \-validity 180\fP +.fi +.nf +\f3\fP +.fi +.sp +The command creates the keystore named \f3mykeystore\fR in the working directory (assuming it does not already exist), and assigns it the password specified by \f3<new password for keystore>\fR\&. It generates a public/private key pair for the entity whose distinguished name has a common name of Mark Jones, organizational unit of Java, organization of Oracle and two-letter country code of US\&. It uses the default DSA key generation algorithm to create the keys; both are 1024 bits\&. +.PP +The command uses the default SHA256withDSA signature algorithm to create a self-signed certificate that includes the public key and the distinguished name information\&. The certificate is valid for 180 days, and is associated with the private key in a keystore entry referred to by the alias \f3business\fR\&. The private key is assigned the password specified by \f3<new password for private key>\fR\&. +.PP +The command is significantly shorter when the option defaults are accepted\&. In this case, no options are required, and the defaults are used for unspecified options that have default values\&. You are prompted for any required values\&. You could have the following: +.sp +.nf +\f3keytool \-genkeypair\fP +.fi +.nf +\f3\fP +.fi +.sp +In this case, a keystore entry with the alias \f3mykey\fR is created, with a newly generated key pair and a certificate that is valid for 90 days\&. This entry is placed in the keystore named \f3\&.keystore\fR in your home directory\&. The keystore is created when it does not already exist\&. You are prompted for the distinguished name information, the keystore password, and the private key password\&. +.PP +The rest of the examples assume you executed the \f3-genkeypair\fR command without options specified, and that you responded to the prompts with values equal to those specified in the first \f3-genkeypair\fR command\&. For example, a distinguished name of \f3cn=Mark Jones\fR, \f3ou=Java\fR, \f3o=Oracle\fR, \f3c=US\fR)\&. +.SS REQUEST\ A\ SIGNED\ CERTIFICATE\ FROM\ A\ CA +Generating the key pair created a self-signed certificate\&. A certificate is more likely to be trusted by others when it is signed by a Certification Authority (CA)\&. To get a CA signature, first generate a Certificate Signing Request (CSR), as follows: +.sp +.nf +\f3keytool \-certreq \-file MarkJ\&.csr\fP +.fi +.nf +\f3\fP +.fi +.sp +This creates a CSR for the entity identified by the default alias \f3mykey\fR and puts the request in the file named MarkJ\&.csr\&. Submit this file to a CA, such as VeriSign\&. The CA authenticates you, the requestor (usually off-line), and returns a certificate, signed by them, authenticating your public key\&. In some cases, the CA returns a chain of certificates, each one authenticating the public key of the signer of the previous certificate in the chain\&. +.SS IMPORT\ A\ CERTIFICATE\ FOR\ THE\ CA +You now need to replace the self-signed certificate with a certificate chain, where each certificate in the chain authenticates the public key of the signer of the previous certificate in the chain, up to a root CA\&. +.PP +Before you import the certificate reply from a CA, you need one or more trusted certificates in your keystore or in the \f3cacerts\fR keystore file\&. See \f3-importcert\fR in Commands\&. +.TP 0.2i +\(bu +If the certificate reply is a certificate chain, then you need the top certificate of the chain\&. The root CA certificate that authenticates the public key of the CA\&. +.TP 0.2i +\(bu +If the certificate reply is a single certificate, then you need a certificate for the issuing CA (the one that signed it)\&. If that certificate is not self-signed, then you need a certificate for its signer, and so on, up to a self-signed root CA certificate\&. +.PP +The \f3cacerts\fR keystore file ships with several VeriSign root CA certificates, so you probably will not need to import a VeriSign certificate as a trusted certificate in your keystore\&. But if you request a signed certificate from a different CA, and a certificate authenticating that CA\&'s public key was not added to \f3cacerts\fR, then you must import a certificate from the CA as a trusted certificate\&. +.PP +A certificate from a CA is usually either self-signed or signed by another CA, in which case you need a certificate that authenticates that CA\&'s public key\&. Suppose company ABC, Inc\&., is a CA, and you obtain a file named A\f3BCCA\&.cer\fR that is supposed to be a self-signed certificate from ABC, that authenticates that CA\&'s public key\&. Be careful to ensure the certificate is valid before you import it as a trusted certificate\&. View it first with the \f3keytool -printcert\fR command or the \f3keytool -importcert\fR command without the \f3-noprompt\fR option, and make sure that the displayed certificate fingerprints match the expected ones\&. You can call the person who sent the certificate, and compare the fingerprints that you see with the ones that they show or that a secure public key repository shows\&. Only when the fingerprints are equal is it guaranteed that the certificate was not replaced in transit with somebody else\&'s (for example, an attacker\&'s) certificate\&. If such an attack takes place, and you did not check the certificate before you imported it, then you would be trusting anything the attacker has signed\&. +.PP +If you trust that the certificate is valid, then you can add it to your keystore with the following command: +.sp +.nf +\f3keytool \-importcert \-alias abc \-file ABCCA\&.cer\fP +.fi +.nf +\f3\fP +.fi +.sp +This command creates a trusted certificate entry in the keystore, with the data from the file ABCCA\&.cer, and assigns the alias \f3abc\fR to the entry\&. +.SS IMPORT\ THE\ CERTIFICATE\ REPLY\ FROM\ THE\ CA +After you import a certificate that authenticates the public key of the CA you submitted your certificate signing request to (or there is already such a certificate in the cacerts file), you can import the certificate reply and replace your self-signed certificate with a certificate chain\&. This chain is the one returned by the CA in response to your request (when the CA reply is a chain), or one constructed (when the CA reply is a single certificate) using the certificate reply and trusted certificates that are already available in the keystore where you import the reply or in the \f3cacerts\fR keystore file\&. +.PP +For example, if you sent your certificate signing request to VeriSign, then you can import the reply with the following, which assumes the returned certificate is named VSMarkJ\&.cer: +.sp +.nf +\f3keytool \-importcert \-trustcacerts \-file VSMarkJ\&.cer\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS EXPORT\ A\ CERTIFICATE\ THAT\ AUTHENTICATES\ THE\ PUBLIC\ KEY +If you used the \f3jarsigner\fR command to sign a Java Archive (JAR) file, then clients that want to use the file will want to authenticate your signature\&. One way the clients can authenticate you is by first importing your public key certificate into their keystore as a trusted entry\&. +.PP +You can export the certificate and supply it to your clients\&. As an example, you can copy your certificate to a file named MJ\&.cer with the following command that assumes the entry has an alias of \f3mykey\fR: +.sp +.nf +\f3keytool \-exportcert \-alias mykey \-file MJ\&.cer\fP +.fi +.nf +\f3\fP +.fi +.sp +With the certificate and the signed JAR file, a client can use the \f3jarsigner\fR command to authenticate your signature\&. +.SS IMPORT\ KEYSTORE +The command \f3importkeystore\fR is used to import an entire keystore into another keystore, which means all entries from the source keystore, including keys and certificates, are all imported to the destination keystore within a single command\&. You can use this command to import entries from a different type of keystore\&. During the import, all new entries in the destination keystore will have the same alias names and protection passwords (for secret keys and private keys)\&. If the \f3keytool\fR command cannot recover the private keys or secret keys from the source keystore, then it prompts you for a password\&. If it detects alias duplication, then it asks you for a new alias, and you can specify a new alias or simply allow the \f3keytool\fR command to overwrite the existing one\&. +.PP +For example, to import entries from a typical JKS type keystore key\&.jks into a PKCS #11 type hardware-based keystore, use the command: +.sp +.nf +\f3keytool \-importkeystore\fP +.fi +.nf +\f3 \-srckeystore key\&.jks \-destkeystore NONE\fP +.fi +.nf +\f3 \-srcstoretype JKS \-deststoretype PKCS11\fP +.fi +.nf +\f3 \-srcstorepass <src keystore password>\fP +.fi +.nf +\f3 \-deststorepass <destination keystore pwd>\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3importkeystore\fR command can also be used to import a single entry from a source keystore to a destination keystore\&. In this case, besides the options you see in the previous example, you need to specify the alias you want to import\&. With the \f3-srcalias\fR option specified, you can also specify the destination alias name in the command line, as well as protection password for a secret/private key and the destination protection password you want\&. The following command demonstrates this: +.sp +.nf +\f3keytool \-importkeystore\fP +.fi +.nf +\f3 \-srckeystore key\&.jks \-destkeystore NONE\fP +.fi +.nf +\f3 \-srcstoretype JKS \-deststoretype PKCS11\fP +.fi +.nf +\f3 \-srcstorepass <src keystore password>\fP +.fi +.nf +\f3 \-deststorepass <destination keystore pwd>\fP +.fi +.nf +\f3 \-srcalias myprivatekey \-destalias myoldprivatekey\fP +.fi +.nf +\f3 \-srckeypass <source entry password>\fP +.fi +.nf +\f3 \-destkeypass <destination entry password>\fP +.fi +.nf +\f3 \-noprompt\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS GENERATE\ CERTIFICATES\ FOR\ AN\ SSL\ SERVER +The following are \f3keytool\fR commands to generate key pairs and certificates for three entities: Root CA (\f3root\fR), Intermediate CA (\f3ca\fR), and SSL server (\f3server\fR)\&. Ensure that you store all the certificates in the same keystore\&. In these examples, RSA is the recommended the key algorithm\&. +.sp +.nf +\f3keytool \-genkeypair \-keystore root\&.jks \-alias root \-ext bc:c\fP +.fi +.nf +\f3keytool \-genkeypair \-keystore ca\&.jks \-alias ca \-ext bc:c\fP +.fi +.nf +\f3keytool \-genkeypair \-keystore server\&.jks \-alias server\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3keytool \-keystore root\&.jks \-alias root \-exportcert \-rfc > root\&.pem\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3keytool \-storepass <storepass> \-keystore ca\&.jks \-certreq \-alias ca |\fP +.fi +.nf +\f3 keytool \-storepass <storepass> \-keystore root\&.jks\fP +.fi +.nf +\f3 \-gencert \-alias root \-ext BC=0 \-rfc > ca\&.pem\fP +.fi +.nf +\f3keytool \-keystore ca\&.jks \-importcert \-alias ca \-file ca\&.pem\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3keytool \-storepass <storepass> \-keystore server\&.jks \-certreq \-alias server |\fP +.fi +.nf +\f3 keytool \-storepass <storepass> \-keystore ca\&.jks \-gencert \-alias ca\fP +.fi +.nf +\f3 \-ext ku:c=dig,kE \-rfc > server\&.pem\fP +.fi +.nf +\f3cat root\&.pem ca\&.pem server\&.pem |\fP +.fi +.nf +\f3 keytool \-keystore server\&.jks \-importcert \-alias server\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH TERMS +.TP +Keystore +A keystore is a storage facility for cryptographic keys and certificates\&. +.TP +Keystore entries +Keystores can have different types of entries\&. The two most applicable entry types for the \f3keytool\fR command include the following: + +\fIKey entries\fR: Each entry holds very sensitive cryptographic key information, which is stored in a protected format to prevent unauthorized access\&. Typically, a key stored in this type of entry is a secret key, or a private key accompanied by the certificate chain for the corresponding public key\&. See Certificate Chains\&. The \f3keytool\fR command can handle both types of entries, while the \f3jarsigner\fR tool only handles the latter type of entry, that is private keys and their associated certificate chains\&. + +\fITrusted certificate entries\fR: Each entry contains a single public key certificate that belongs to another party\&. The entry is called a trusted certificate because the keystore owner trusts that the public key in the certificate belongs to the identity identified by the subject (owner) of the certificate\&. The issuer of the certificate vouches for this, by signing the certificate\&. +.TP +KeyStore aliases +All keystore entries (key and trusted certificate entries) are accessed by way of unique aliases\&. + +An alias is specified when you add an entity to the keystore with the \f3-genseckey\fR command to generate a secret key, the \f3-genkeypair\fR command to generate a key pair (public and private key), or the \f3-importcert\fR command to add a certificate or certificate chain to the list of trusted certificates\&. Subsequent \f3keytool\fR commands must use this same alias to refer to the entity\&. + +For example, you can use the alias \f3duke\fR to generate a new public/private key pair and wrap the public key into a self-signed certificate with the following command\&. See Certificate Chains\&. +.sp +.nf +\f3keytool \-genkeypair \-alias duke \-keypass dukekeypasswd\fP +.fi +.nf +\f3\fP +.fi +.sp + + +This example specifies an initial password of \f3dukekeypasswd\fR required by subsequent commands to access the private key associated with the alias \f3duke\fR\&. If you later want to change Duke\&'s private key password, use a command such as the following: +.sp +.nf +\f3keytool \-keypasswd \-alias duke \-keypass dukekeypasswd \-new newpass\fP +.fi +.nf +\f3\fP +.fi +.sp + + +This changes the password from \f3dukekeypasswd\fR to \f3newpass\fR\&. A password should not be specified on a command line or in a script unless it is for testing purposes, or you are on a secure system\&. If you do not specify a required password option on a command line, then you are prompted for it\&. +.TP +KeyStore implementation +The \f3KeyStore\fR class provided in the \f3java\&.security\fR package supplies well-defined interfaces to access and modify the information in a keystore\&. It is possible for there to be multiple different concrete implementations, where each implementation is that for a particular type of keystore\&. + +Currently, two command-line tools (\f3keytool\fR and \f3jarsigner\fR) and a GUI-based tool named Policy Tool make use of keystore implementations\&. Because the \f3KeyStore\fR class is \f3public\fR, users can write additional security applications that use it\&. + +There is a built-in default implementation, provided by Oracle\&. It implements the keystore as a file with a proprietary keystore type (format) named JKS\&. It protects each private key with its individual password, and also protects the integrity of the entire keystore with a (possibly different) password\&. + +Keystore implementations are provider-based\&. More specifically, the application interfaces supplied by \f3KeyStore\fR are implemented in terms of a Service Provider Interface (SPI)\&. That is, there is a corresponding abstract \f3KeystoreSpi\fR class, also in the \f3java\&.security package\fR, which defines the Service Provider Interface methods that providers must implement\&. The term \fIprovider\fR refers to a package or a set of packages that supply a concrete implementation of a subset of services that can be accessed by the Java Security API\&. To provide a keystore implementation, clients must implement a provider and supply a \f3KeystoreSpi\fR subclass implementation, as described in How to Implement a Provider in the Java Cryptography Architecture at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/HowToImplAProvider\&.html + +Applications can choose different types of keystore implementations from different providers, using the \f3getInstance\fR factory method supplied in the \f3KeyStore\fR class\&. A keystore type defines the storage and data format of the keystore information, and the algorithms used to protect private/secret keys in the keystore and the integrity of the keystore\&. Keystore implementations of different types are not compatible\&. + +The \f3keytool\fR command works on any file-based keystore implementation\&. It treats the keystore location that is passed to it at the command line as a file name and converts it to a \f3FileInputStream\fR, from which it loads the keystore information\&.)The \f3jarsigner\fR and \f3policytool\fR commands can read a keystore from any location that can be specified with a URL\&. + +For \f3keytool\fR and \f3jarsigner\fR, you can specify a keystore type at the command line, with the \f3-storetype\fR option\&. For Policy Tool, you can specify a keystore type with the \fIKeystore\fR menu\&. + +If you do not explicitly specify a keystore type, then the tools choose a keystore implementation based on the value of the \f3keystore\&.type\fR property specified in the security properties file\&. The security properties file is called \f3java\&.security\fR, and resides in the security properties directory, \f3java\&.home\elib\esecurity\fR on Windows and \f3java\&.home/lib/security\fR on Oracle Solaris, where \f3java\&.home\fR is the runtime environment directory\&. The \f3jre\fR directory in the SDK or the top-level directory of the Java Runtime Environment (JRE)\&. + +Each tool gets the \f3keystore\&.type\fR value and then examines all the currently installed providers until it finds one that implements a keystores of that type\&. It then uses the keystore implementation from that provider\&.The \f3KeyStore\fR class defines a static method named \f3getDefaultType\fR that lets applications and applets retrieve the value of the \f3keystore\&.type\fR property\&. The following line of code creates an instance of the default keystore type as specified in the \f3keystore\&.type\fR property: +.sp +.nf +\f3KeyStore keyStore = KeyStore\&.getInstance(KeyStore\&.getDefaultType());\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The default keystore type is \f3jks\fR, which is the proprietary type of the keystore implementation provided by Oracle\&. This is specified by the following line in the security properties file: +.sp +.nf +\f3keystore\&.type=jks\fP +.fi +.nf +\f3\fP +.fi +.sp + + +To have the tools utilize a keystore implementation other than the default, you can change that line to specify a different keystore type\&. For example, if you have a provider package that supplies a keystore implementation for a keystore type called \f3pkcs12\fR, then change the line to the following: +.sp +.nf +\f3keystore\&.type=pkcs12\fP +.fi +.nf +\f3\fP +.fi +.sp + + +\fINote:\fR Case does not matter in keystore type designations\&. For example, JKS would be considered the same as jks\&. +.TP +Certificate +A certificate (or public-key certificate) is a digitally signed statement from one entity (the issuer), saying that the public key and some other information of another entity (the subject) has some specific value\&. The following terms are related to certificates: + +\fIPublic Keys\fR: These are numbers associated with a particular entity, and are intended to be known to everyone who needs to have trusted interactions with that entity\&. Public keys are used to verify signatures\&. + +\fIDigitally Signed\fR: If some data is digitally signed, then it is stored with the identity of an entity and a signature that proves that entity knows about the data\&. The data is rendered unforgeable by signing with the entity\&'s private key\&. + +\fIIdentity\fR: A known way of addressing an entity\&. In some systems, the identity is the public key, and in others it can be anything from an Oracle Solaris UID to an email address to an X\&.509 distinguished name\&. + +\fISignature\fR: A signature is computed over some data using the private key of an entity\&. The signer, which in the case of a certificate is also known as the issuer\&. + +\fIPrivate Keys\fR: These are numbers, each of which is supposed to be known only to the particular entity whose private key it is (that is, it is supposed to be kept secret)\&. Private and public keys exist in pairs in all public key cryptography systems (also referred to as public key crypto systems)\&. In a typical public key crypto system, such as DSA, a private key corresponds to exactly one public key\&. Private keys are used to compute signatures\&. + +\fIEntity\fR: An entity is a person, organization, program, computer, business, bank, or something else you are trusting to some degree\&. + +Public key cryptography requires access to users\&' public keys\&. In a large-scale networked environment, it is impossible to guarantee that prior relationships between communicating entities were established or that a trusted repository exists with all used public keys\&. Certificates were invented as a solution to this public key distribution problem\&. Now a Certification Authority (CA) can act as a trusted third party\&. CAs are entities such as businesses that are trusted to sign (issue) certificates for other entities\&. It is assumed that CAs only create valid and reliable certificates because they are bound by legal agreements\&. There are many public Certification Authorities, such as VeriSign, Thawte, Entrust, and so on\&. + +You can also run your own Certification Authority using products such as Microsoft Certificate Server or the Entrust CA product for your organization\&. With the \f3keytool\fR command, it is possible to display, import, and export certificates\&. It is also possible to generate self-signed certificates\&. + +The \f3keytool\fR command currently handles X\&.509 certificates\&. +.TP +X\&.509 Certificates +The X\&.509 standard defines what information can go into a certificate and describes how to write it down (the data format)\&. All the data in a certificate is encoded with two related standards called ASN\&.1/DER\&. Abstract Syntax Notation 1 describes data\&. The Definite Encoding Rules describe a single way to store and transfer that data\&. + +All X\&.509 certificates have the following data, in addition to the signature: + +\fIVersion\fR: This identifies which version of the X\&.509 standard applies to this certificate, which affects what information can be specified in it\&. Thus far, three versions are defined\&. The \f3keytool\fR command can import and export v1, v2, and v3 certificates\&. It generates v3 certificates\&. + +X\&.509 Version 1 has been available since 1988, is widely deployed, and is the most generic\&. + +X\&.509 Version 2 introduced the concept of subject and issuer unique identifiers to handle the possibility of reuse of subject or issuer names over time\&. Most certificate profile documents strongly recommend that names not be reused and that certificates should not make use of unique identifiers\&. Version 2 certificates are not widely used\&. + +X\&.509 Version 3 is the most recent (1996) and supports the notion of extensions where anyone can define an extension and include it in the certificate\&. Some common extensions are: KeyUsage (limits the use of the keys to particular purposes such as \f3signing-only\fR) and AlternativeNames (allows other identities to also be associated with this public key, for example\&. DNS names, email addresses, IP addresses)\&. Extensions can be marked critical to indicate that the extension should be checked and enforced or used\&. For example, if a certificate has the KeyUsage extension marked critical and set to \f3keyCertSign\fR, then when this certificate is presented during SSL communication, it should be rejected because the certificate extension indicates that the associated private key should only be used for signing certificates and not for SSL use\&. + +\fISerial number\fR: The entity that created the certificate is responsible for assigning it a serial number to distinguish it from other certificates it issues\&. This information is used in numerous ways\&. For example, when a certificate is revoked its serial number is placed in a Certificate Revocation List (CRL)\&. + +\fISignature algorithm identifier\fR: This identifies the algorithm used by the CA to sign the certificate\&. + +\fIIssuer name\fR: The X\&.500 Distinguished Name of the entity that signed the certificate\&. See X\&.500 Distinguished Names\&. This is typically a CA\&. Using this certificate implies trusting the entity that signed this certificate\&. In some cases, such as root or top-level CA certificates, the issuer signs its own certificate\&. + +\fIValidity period\fR: Each certificate is valid only for a limited amount of time\&. This period is described by a start date and time and an end date and time, and can be as short as a few seconds or almost as long as a century\&. The validity period chosen depends on a number of factors, such as the strength of the private key used to sign the certificate, or the amount one is willing to pay for a certificate\&. This is the expected period that entities can rely on the public value, when the associated private key has not been compromised\&. + +\fISubject name\fR: The name of the entity whose public key the certificate identifies\&. This name uses the X\&.500 standard, so it is intended to be unique across the Internet\&. This is the X\&.500 Distinguished Name (DN) of the entity\&. See X\&.500 Distinguished Names\&. For example, +.sp +.nf +\f3CN=Java Duke, OU=Java Software Division, O=Oracle Corporation, C=US\fP +.fi +.nf +\f3\fP +.fi +.sp + + +These refer to the subject\&'s common name (CN), organizational unit (OU), organization (O), and country (C)\&. + +\fISubject public key information\fR: This is the public key of the entity being named with an algorithm identifier that specifies which public key crypto system this key belongs to and any associated key parameters\&. +.TP +Certificate Chains +The \f3keytool\fR command can create and manage keystore key entries that each contain a private key and an associated certificate chain\&. The first certificate in the chain contains the public key that corresponds to the private key\&. + +When keys are first generated, the chain starts off containing a single element, a self-signed certificate\&. See \f3-genkeypair\fR in Commands\&. A self-signed certificate is one for which the issuer (signer) is the same as the subject\&. The subject is the entity whose public key is being authenticated by the certificate\&. Whenever the \f3-genkeypair\fR command is called to generate a new public/private key pair, it also wraps the public key into a self-signed certificate\&. + +Later, after a Certificate Signing Request (CSR) was generated with the \f3-certreq\fR command and sent to a Certification Authority (CA), the response from the CA is imported with \f3-importcert\fR, and the self-signed certificate is replaced by a chain of certificates\&. See the \f3-certreq\fR and \f3-importcert\fR options in Commands\&. At the bottom of the chain is the certificate (reply) issued by the CA authenticating the subject\&'s public key\&. The next certificate in the chain is one that authenticates the CA\&'s public key\&. + +In many cases, this is a self-signed certificate, which is a certificate from the CA authenticating its own public key, and the last certificate in the chain\&. In other cases, the CA might return a chain of certificates\&. In this case, the bottom certificate in the chain is the same (a certificate signed by the CA, authenticating the public key of the key entry), but the second certificate in the chain is a certificate signed by a different CA that authenticates the public key of the CA you sent the CSR to\&. The next certificate in the chain is a certificate that authenticates the second CA\&'s key, and so on, until a self-signed root certificate is reached\&. Each certificate in the chain (after the first) authenticates the public key of the signer of the previous certificate in the chain\&. + +Many CAs only return the issued certificate, with no supporting chain, especially when there is a flat hierarchy (no intermediates CAs)\&. In this case, the certificate chain must be established from trusted certificate information already stored in the keystore\&. + +A different reply format (defined by the PKCS #7 standard) includes the supporting certificate chain in addition to the issued certificate\&. Both reply formats can be handled by the \f3keytool\fR command\&. + +The top-level (root) CA certificate is self-signed\&. However, the trust into the root\&'s public key does not come from the root certificate itself, but from other sources such as a newspaper\&. This is because anybody could generate a self-signed certificate with the distinguished name of, for example, the VeriSign root CA\&. The root CA public key is widely known\&. The only reason it is stored in a certificate is because this is the format understood by most tools, so the certificate in this case is only used as a vehicle to transport the root CA\&'s public key\&. Before you add the root CA certificate to your keystore, you should view it with the \f3-printcert\fR option and compare the displayed fingerprint with the well-known fingerprint obtained from a newspaper, the root CA\&'s Web page, and so on\&. +.TP +The cacerts Certificates File +A certificates file named \f3cacerts\fR resides in the security properties directory, \f3java\&.home\elib\esecurity\fR on Windows and \f3java\&.home/lib/security\fR on Oracle Solaris, where \f3java\&.home\fR is the runtime environment\&'s directory, which would be the \f3jre\fR directory in the SDK or the top-level directory of the JRE\&. + +The \f3cacerts\fR file represents a system-wide keystore with CA certificates\&. System administrators can configure and manage that file with the \f3keytool\fR command by specifying \f3jks\fR as the keystore type\&. The \f3cacerts\fR keystore file ships with a default set of root CA certificates\&. You can list the default certificates with the following command: +.sp +.nf +\f3keytool \-list \-keystore java\&.home/lib/security/cacerts\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The initial password of the \f3cacerts\fR keystore file is \f3changeit\fR\&. System administrators should change that password and the default access permission of that file upon installing the SDK\&. + +\fINote:\fR It is important to verify your \f3cacerts\fR file\&. Because you trust the CAs in the \f3cacerts\fR file as entities for signing and issuing certificates to other entities, you must manage the \f3cacerts\fR file carefully\&. The \f3cacerts\fR file should contain only certificates of the CAs you trust\&. It is your responsibility to verify the trusted root CA certificates bundled in the \f3cacerts\fR file and make your own trust decisions\&. + +To remove an untrusted CA certificate from the \f3cacerts\fR file, use the \f3delete\fR option of the \f3keytool\fR command\&. You can find the \f3cacerts\fR file in the JRE installation directory\&. Contact your system administrator if you do not have permission to edit this file +.TP +Internet RFC 1421 Certificate Encoding Standard +Certificates are often stored using the printable encoding format defined by the Internet RFC 1421 standard, instead of their binary encoding\&. This certificate format, also known as Base64 encoding, makes it easy to export certificates to other applications by email or through some other mechanism\&. + +Certificates read by the \f3-importcert\fR and \f3-printcert\fR commands can be in either this format or binary encoded\&. The \f3-exportcert\fR command by default outputs a certificate in binary encoding, but will instead output a certificate in the printable encoding format, when the \f3-rfc\fR option is specified\&. + +The \f3-list\fR command by default prints the SHA256 fingerprint of a certificate\&. If the \f3-v\fR option is specified, then the certificate is printed in human-readable format\&. If the \f3-rfc\fR option is specified, then the certificate is output in the printable encoding format\&. + +In its printable encoding format, the encoded certificate is bounded at the beginning and end by the following text: +.sp +.nf +\f3\-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\-\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3encoded certificate goes here\&. \fP +.fi +.nf +\f3\fP +.fi +.nf +\f3\-\-\-\-\-END CERTIFICATE\-\-\-\-\-\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +X\&.500 Distinguished Names +X\&.500 Distinguished Names are used to identify entities, such as those that are named by the \f3subject\fR and \f3issuer\fR (signer) fields of X\&.509 certificates\&. The \f3keytool\fR command supports the following subparts: + +\fIcommonName\fR: The common name of a person such as Susan Jones\&. + +\fIorganizationUnit\fR: The small organization (such as department or division) name\&. For example, Purchasing\&. + +\fIlocalityName\fR: The locality (city) name, for example, Palo Alto\&. + +\fIstateName\fR: State or province name, for example, California\&. + +\fIcountry\fR: Two-letter country code, for example, CH\&. + +When you supply a distinguished name string as the value of a \f3-dname\fR option, such as for the \f3-genkeypair\fR command, the string must be in the following format: +.sp +.nf +\f3CN=cName, OU=orgUnit, O=org, L=city, S=state, C=countryCode\fP +.fi +.nf +\f3\fP +.fi +.sp + + +All the italicized items represent actual values and the previous keywords are abbreviations for the following: +.sp +.nf +\f3CN=commonName\fP +.fi +.nf +\f3OU=organizationUnit\fP +.fi +.nf +\f3O=organizationName\fP +.fi +.nf +\f3L=localityName\fP +.fi +.nf +\f3S=stateName\fP +.fi +.nf +\f3C=country\fP +.fi +.nf +\f3\fP +.fi +.sp + + +A sample distinguished name string is: +.sp +.nf +\f3CN=Mark Smith, OU=Java, O=Oracle, L=Cupertino, S=California, C=US\fP +.fi +.nf +\f3\fP +.fi +.sp + + +A sample command using such a string is: +.sp +.nf +\f3keytool \-genkeypair \-dname "CN=Mark Smith, OU=Java, O=Oracle, L=Cupertino,\fP +.fi +.nf +\f3S=California, C=US" \-alias mark\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Case does not matter for the keyword abbreviations\&. For example, CN, cn, and Cn are all treated the same\&. + +Order matters; each subcomponent must appear in the designated order\&. However, it is not necessary to have all the subcomponents\&. You can use a subset, for example: +.sp +.nf +\f3CN=Steve Meier, OU=Java, O=Oracle, C=US\fP +.fi +.nf +\f3\fP +.fi +.sp + + +If a distinguished name string value contains a comma, then the comma must be escaped by a backslash (\e) character when you specify the string on a command line, as in: +.sp +.nf +\f3cn=Peter Schuster, ou=Java\e, Product Development, o=Oracle, c=US\fP +.fi +.nf +\f3\fP +.fi +.sp + + +It is never necessary to specify a distinguished name string on a command line\&. When the distinguished name is needed for a command, but not supplied on the command line, the user is prompted for each of the subcomponents\&. In this case, a comma does not need to be escaped by a backslash (\e)\&. +.SH WARNINGS +.SS IMPORTING\ TRUSTED\ CERTIFICATES\ WARNING +\fIImportant\fR: Be sure to check a certificate very carefully before importing it as a trusted certificate\&. +.PP +Windows Example: + +View the certificate first with the \f3-printcert\fR command or the \f3-importcert\fR command without the \f3-noprompt\fR option\&. Ensure that the displayed certificate fingerprints match the expected ones\&. For example, suppose sends or emails you a certificate that you put it in a file named \f3\etmp\ecert\fR\&. Before you consider adding the certificate to your list of trusted certificates, you can execute a \f3-printcert\fR command to view its fingerprints, as follows: +.sp +.nf +\f3 keytool \-printcert \-file \etmp\ecert\fP +.fi +.nf +\f3 Owner: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fP +.fi +.nf +\f3 Issuer: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fP +.fi +.nf +\f3 Serial Number: 59092b34\fP +.fi +.nf +\f3 Valid from: Thu Sep 25 18:01:13 PDT 1997 until: Wed Dec 24 17:01:13 PST 1997\fP +.fi +.nf +\f3 Certificate Fingerprints:\fP +.fi +.nf +\f3 SHA1: 20:B6:17:FA:EF:E5:55:8A:D0:71:1F:E8:D6:9D:C0:37:13:0E:5E:FE\fP +.fi +.nf +\f3 SHA256: 90:7B:70:0A:EA:DC:16:79:92:99:41:FF:8A:FE:EB:90:\fP +.fi +.nf +\f3 17:75:E0:90:B2:24:4D:3A:2A:16:A6:E4:11:0F:67:A4\fP +.fi +.sp + +.PP +Oracle Solaris Example: + +View the certificate first with the \f3-printcert\fR command or the \f3-importcert\fR command without the \f3-noprompt\fR option\&. Ensure that the displayed certificate fingerprints match the expected ones\&. For example, suppose someone sends or emails you a certificate that you put it in a file named \f3/tmp/cert\fR\&. Before you consider adding the certificate to your list of trusted certificates, you can execute a \f3-printcert\fR command to view its fingerprints, as follows: +.sp +.nf +\f3 keytool \-printcert \-file /tmp/cert\fP +.fi +.nf +\f3 Owner: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fP +.fi +.nf +\f3 Issuer: CN=ll, OU=ll, O=ll, L=ll, S=ll, C=ll\fP +.fi +.nf +\f3 Serial Number: 59092b34\fP +.fi +.nf +\f3 Valid from: Thu Sep 25 18:01:13 PDT 1997 until: Wed Dec 24 17:01:13 PST 1997\fP +.fi +.nf +\f3 Certificate Fingerprints:\fP +.fi +.nf +\f3 SHA1: 20:B6:17:FA:EF:E5:55:8A:D0:71:1F:E8:D6:9D:C0:37:13:0E:5E:FE\fP +.fi +.nf +\f3 SHA256: 90:7B:70:0A:EA:DC:16:79:92:99:41:FF:8A:FE:EB:90:\fP +.fi +.nf +\f3 17:75:E0:90:B2:24:4D:3A:2A:16:A6:E4:11:0F:67:A4\fP +.fi +.nf +\f3\fP +.fi +.sp +Then call or otherwise contact the person who sent the certificate and compare the fingerprints that you see with the ones that they show\&. Only when the fingerprints are equal is it guaranteed that the certificate was not replaced in transit with somebody else\&'s certificate such as an attacker\&'s certificate\&. If such an attack took place, and you did not check the certificate before you imported it, then you would be trusting anything the attacker signed, for example, a JAR file with malicious class files inside\&. +.PP +\fINote:\fR It is not required that you execute a \f3-printcert\fR command before importing a certificate\&. This is because before you add a certificate to the list of trusted certificates in the keystore, the \f3-importcert\fR command prints out the certificate information and prompts you to verify it\&. You can then stop the import operation\&. However, you can do this only when you call the \f3-importcert\fR command without the \f3-noprompt\fR option\&. If the \f3-noprompt\fR option is specified, then there is no interaction with the user\&. +.SS PASSWORDS\ WARNING +Most commands that operate on a keystore require the store password\&. Some commands require a private/secret key password\&. Passwords can be specified on the command line in the \f3-storepass\fR and \f3-keypass\fR options\&. However, a password should not be specified on a command line or in a script unless it is for testing, or you are on a secure system\&. When you do not specify a required password option on a command line, you are prompted for it\&. +.SS CERTIFICATE\ CONFORMANCE\ WARNING +The Internet standard RFC 5280 has defined a profile on conforming X\&.509 certificates, which includes what values and value combinations are valid for certificate fields and extensions\&. See the standard at http://tools\&.ietf\&.org/rfc/rfc5280\&.txt +.PP +The \f3keytool\fR command does not enforce all of these rules so it can generate certificates that do not conform to the standard\&. Certificates that do not conform to the standard might be rejected by JRE or other applications\&. Users should ensure that they provide the correct options for \f3-dname\fR, \f3-ext\fR, and so on\&. +.SH NOTES +.SS IMPORT\ A\ NEW\ TRUSTED\ CERTIFICATE +Before you add the certificate to the keystore, the \f3keytool\fR command verifies it by attempting to construct a chain of trust from that certificate to a self-signed certificate (belonging to a root CA), using trusted certificates that are already available in the keystore\&. +.PP +If the \f3-trustcacerts\fR option was specified, then additional certificates are considered for the chain of trust, namely the certificates in a file named \f3cacerts\fR\&. +.PP +If the \f3keytool\fR command fails to establish a trust path from the certificate to be imported up to a self-signed certificate (either from the keystore or the \f3cacerts\fR file), then the certificate information is printed, and the user is prompted to verify it by comparing the displayed certificate fingerprints with the fingerprints obtained from some other (trusted) source of information, which might be the certificate owner\&. Be very careful to ensure the certificate is valid before importing it as a trusted certificate\&. See Importing Trusted Certificates Warning\&. The user then has the option of stopping the import operation\&. If the \f3-noprompt\fR option is specified, then there is no interaction with the user\&. +.SS IMPORT\ A\ CERTIFICATE\ REPLY +When you import a certificate reply, the certificate reply is validated with trusted certificates from the keystore, and optionally, the certificates configured in the \f3cacerts\fR keystore file when the \f3-trustcacert\fR\f3s\fR option is specified\&. See The cacerts Certificates File\&. +.PP +The methods of determining whether the certificate reply is trusted are as follows: +.TP 0.2i +\(bu +If the reply is a single X\&.509 certificate, then the \f3keytool\fR command attempts to establish a trust chain, starting at the certificate reply and ending at a self-signed certificate (belonging to a root CA)\&. The certificate reply and the hierarchy of certificates is used to authenticate the certificate reply from the new certificate chain of aliases\&. If a trust chain cannot be established, then the certificate reply is not imported\&. In this case, the \f3keytool\fR command does not print the certificate and prompt the user to verify it, because it is very difficult for a user to determine the authenticity of the certificate reply\&. +.TP 0.2i +\(bu +If the reply is a PKCS #7 formatted certificate chain or a sequence of X\&.509 certificates, then the chain is ordered with the user certificate first followed by zero or more CA certificates\&. If the chain ends with a self-signed root CA certificate and the\f3-trustcacerts\fR option was specified, the \f3keytool\fR command attempts to match it with any of the trusted certificates in the keystore or the \f3cacerts\fR keystore file\&. If the chain does not end with a self-signed root CA certificate and the \f3-trustcacerts\fR option was specified, the \f3keytool\fR command tries to find one from the trusted certificates in the keystore or the \f3cacerts\fR keystore file and add it to the end of the chain\&. If the certificate is not found and the \f3-noprompt\fR option is not specified, the information of the last certificate in the chain is printed, and the user is prompted to verify it\&. +.PP +If the public key in the certificate reply matches the user\&'s public key already stored with \f3alias\fR, then the old certificate chain is replaced with the new certificate chain in the reply\&. The old chain can only be replaced with a valid \f3keypass\fR, and so the password used to protect the private key of the entry is supplied\&. If no password is provided, and the private key password is different from the keystore password, the user is prompted for it\&. +.PP +This command was named \f3-import\fR in earlier releases\&. This old name is still supported in this release\&. The new name, \f3-importcert\fR, is preferred going forward\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +jar(1) +.TP 0.2i +\(bu +jarsigner(1) +.TP 0.2i +\(bu +Trail: Security Features in Java SE at http://docs\&.oracle\&.com/javase/tutorial/security/index\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/native2ascii.1 b/jdk-1.8.0.281/man/man1/native2ascii.1 new file mode 100755 index 0000000..c6ebca1 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/native2ascii.1 @@ -0,0 +1,66 @@ +'\" t +.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Internationalization Tools +.\" Title: native2ascii.1 +.\" +.if n .pl 99999 +.TH native2ascii 1 "21 November 2013" "JDK 8" "Internationalization Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +native2ascii \- Creates localizable applications by converting a file with characters in any supported character encoding to one with ASCII and/or Unicode escapes or vice versa\&. +.SH SYNOPSIS +.sp +.nf + +\fBnative2ascii\fR [ \fIinputfile\fR ] [ \fIoutputfile\fR ] +.fi +.sp +.TP +\fIinputfile\fR +The encoded file to be converted to ASCII\&. +.TP +\fIoutputfile\fR +The converted ASCII file\&. +.SH DESCRIPTION +The \f3native2ascii\fR command converts encoded files supported by the Java Runtime Environment (JRE) to files encoded in ASCII, using Unicode escapes (\f3\eu\fR\fIxxxx\fR) notation for all characters that are not part of the ASCII character set\&. This process is required for properties files that contain characters not in ISO-8859-1 character sets\&. The tool can also perform the reverse conversion\&. +.PP +If the \f3outputfile\fR value is omitted, then standard output is used for output\&. If, in addition, the \f3inputfile\fR value is omitted, then standard input is used for input\&. +.SH OPTIONS +.TP +-reverse +.br +Perform the reverse operation: Converts a file encoded in ISO-8859-1 with Unicode escapes to a file in any character encoding supported by the JRE\&. +.TP +-encoding \fIencoding_name\fR +.br +Specifies the name of the character encoding to be used by the conversion procedure\&. If this option is not present, then the default character encoding (as determined by the \f3java\&.nio\&.charset\&.Charset\&.defaultCharset\fR method) is used\&. The \f3encoding_name\fR string must be the name of a character encoding that is supported by the JRE\&. See Supported Encodings at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/intl/encoding\&.doc\&.html +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine (JVM), where option is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/orbd.1 b/jdk-1.8.0.281/man/man1/orbd.1 new file mode 100755 index 0000000..a585e57 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/orbd.1 @@ -0,0 +1,193 @@ +'\" t +.\" Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java IDL and RMI-IIOP Tools +.\" Title: orbd.1 +.\" +.if n .pl 99999 +.TH orbd 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +orbd \- Enables clients to locate and call persistent objects on servers in the CORBA environment\&. +.SH SYNOPSIS +.sp +.nf + +\fBorbd\fR [ \fIoptions\fR ] +.fi +.sp +.TP +\fIoptions\fR +Command-line options\&. See Options\&. +.SH DESCRIPTION +The \f3orbd\fR command enables clients to transparently locate and call persistent objects on servers in the CORBA environment\&. The Server Manager included with the orbd tool is used to enable clients to transparently locate and call persistent objects on servers in the CORBA environment\&. The persistent servers, while publishing the persistent object references in the naming service, include the port number of the ORBD in the object reference instead of the port number of the server\&. The inclusion of an ORBD port number in the object reference for persistent object references has the following advantages: +.TP 0.2i +\(bu +The object reference in the naming service remains independent of the server life cycle\&. For example, the object reference could be published by the server in the Naming Service when it is first installed, and then, independent of how many times the server is started or shut down, the ORBD returns the correct object reference to the calling client\&. +.TP 0.2i +\(bu +The client needs to look up the object reference in the naming service only once, and can keep reusing this reference independent of the changes introduced due to server life cycle\&. +.PP +To access the ORBD Server Manager, the server must be started using \f3servertool\fR, which is a command-line interface for application programmers to register, unregister, start up, and shut down a persistent server\&. For more information on the Server Manager, see Server Manager\&. +.PP +When \f3orbd\fR starts, it also starts a naming service\&. For more information about the naming service\&. See Start and Stop the Naming Service\&. +.SH OPTIONS +.TP +-ORBInitialPort \fInameserverport\fR +.br +Required\&. Specifies the port on which the name server should be started\&. After it is started, \f3orbd\fR listens for incoming requests on this port\&. On Oracle Solaris software, you must become the root user to start a process on a port below 1024\&. For this reason, Oracle recommends that you use a port number above or equal to 1024\&. +.SS NONREQUIRED\ OPTIONS +.TP +-port \fIport\fR +.br +Specifies the activation port where ORBD should be started, and where ORBD will be accepting requests for persistent objects\&. The default value for this port is 1049\&. This port number is added to the port field of the persistent Interoperable Object References (IOR)\&. +.TP +-defaultdb \fIdirectory\fR +.br +Specifies the base where the ORBD persistent storage directory, \f3orb\&.db\fR, is created\&. If this option is not specified, then the default value is \f3\&./orb\&.db\fR\&. +.TP +-serverPollingTime \fImilliseconds\fR +.br +Specifies how often ORBD checks for the health of persistent servers registered through \f3servertool\fR\&. The default value is 1000 ms\&. The value specified for \f3milliseconds\fR must be a valid positive integer\&. +.TP +-serverStartupDelay milliseconds +.br +Specifies how long ORBD waits before sending a location forward exception after a persistent server that is registered through \f3servertool\fR is restarted\&. The default value is 1000 ms\&. The value specified for \f3milliseconds\fR must be a valid positive integer\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SS START\ AND\ STOP\ THE\ NAMING\ SERVICE +A naming service is a CORBA service that allows CORBA objects to be named by means of binding a name to an object reference\&. The name binding can be stored in the naming service, and a client can supply the name to obtain the desired object reference\&. +.PP +Before running a client or a server, you will start ORBD\&. ORBD includes a persistent naming service and a transient naming service, both of which are an implementation of the COS Naming Service\&. +.PP +The Persistent Naming Service provides persistence for naming contexts\&. This means that this information is persistent across service shutdowns and startups, and is recoverable in the event of a service failure\&. If ORBD is restarted, then the Persistent Naming Service restores the naming context graph, so that the binding of all clients\&' and servers\&' names remains intact (persistent)\&. +.PP +For backward compatibility, \f3tnameserv\fR, a Transient Naming Service that shipped with earlier releases of the JDK, is also included in this release of Java SE\&. A transient naming service retains naming contexts as long as it is running\&. If there is a service interruption, then the naming context graph is lost\&. +.PP +The \f3-ORBInitialPort\fR argument is a required command-line argument for \f3orbd\fR, and is used to set the port number on which the naming service runs\&. The following instructions assume you can use port 1050 for the Java IDL Object Request Broker Daemon\&. When using Oracle Solaris software, you must become a root user to start a process on a port lower than 1024\&. For this reason, it is recommended that you use a port number above or equal to 1024\&. You can substitute a different port when necessary\&. +.PP +To start \f3orbd\fR from a UNIX command shell, enter: +.sp +.nf +\f3orbd \-ORBInitialPort 1050&\fP +.fi +.nf +\f3\fP +.fi +.sp +From an MS-DOS system prompt (Windows), enter: +.sp +.nf +\f3start orbd \-ORBInitialPort 1050\fP +.fi +.nf +\f3\fP +.fi +.sp +Now that ORBD is running, you can run your server and client applications\&. When running the client and server applications, they must be made aware of the port number (and machine name, when applicable) where the Naming Service is running\&. One way to do this is to add the following code to your application: +.sp +.nf +\f3Properties props = new Properties();\fP +.fi +.nf +\f3props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP +.fi +.nf +\f3props\&.put("org\&.omg\&.CORBA\&.ORBInitialHost", "MyHost");\fP +.fi +.nf +\f3ORB orb = ORB\&.init(args, props);\fP +.fi +.nf +\f3\fP +.fi +.sp +In this example, the naming service is running on port 1050 on host \f3MyHost\fR\&. Another way is to specify the port number and/or machine name when running the server or client application from the command line\&. For example, you would start your \f3HelloApplication\fR with the following command line: +.sp +.nf +\f3java HelloApplication \-ORBInitialPort 1050 \-ORBInitialHost MyHost\fP +.fi +.nf +\f3\fP +.fi +.sp +To stop the naming service, use the relevant operating system command, such as \f3pkill\fR\f3orbd\fR on Oracle Solaris, or \fICtrl+C\fR in the DOS window in which \f3orbd\fR is running\&. Note that names registered with the naming service can disappear when the service is terminated because of a transient naming service\&. The Java IDL naming service will run until it is explicitly stopped\&. +.PP +For more information about the naming service included with ORBD, see Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html +.SH SERVER\ MANAGER +To access the ORBD Server Manager and run a persistent server, the server must be started with \f3servertool\fR, which is a command-line interface for application programmers to register, unregister, start up, and shut down a persistent server\&. When a server is started using \f3servertool\fR, it must be started on the same host and port on which \f3orbd\fR is executing\&. If the server is run on a different port, then the information stored in the database for local contexts will be invalid and the service will not work properly\&. +.PP +See Java IDL: The "Hello World" Example at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlExample\&.html +.PP +In this example, you run the \f3idlj\fR compiler and \f3javac\fR compiler as shown in the tutorial\&. To run the ORBD Server Manager, follow these steps for running the application: +.PP +Start \f3orbd\fR\&. +.PP +UNIX command shell, enter: \f3orbd -ORBInitialPort 1050\fR\&. +.PP +MS-DOS system prompt (Windows), enter: \f3s\fR\f3tart orbd -ORBInitialPort 105\fR\f30\fR\&. +.PP +Port 1050 is the port on which you want the name server to run\&. The \f3-ORBInitialPort\fR option is a required command-line argument\&. When using Oracle Solaris software, you must become a root user to start a process on a port below 1024\&. For this reason, it is recommended that you use a port number above or equal to 1024\&. +.PP +Start the \f3servertool\fR: \f3servertool -ORBInitialPort 1050\fR\&. +.PP +Make sure the name server (\f3orbd\fR) port is the same as in the previous step, for example, \f3-ORBInitialPort 1050\&.\fR The \f3servertool\fR must be started on the same port as the name server\&. +.PP +In the \f3servertool\fR command line interface, start the \f3Hello\fR server from the \f3servertool\fR prompt: +.sp +.nf +\f3servertool > register \-server HelloServer \-classpath \&. \-applicationName\fP +.fi +.nf +\f3 HelloServerApName\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3servertool\fR registers the server, assigns it the name \f3HelloServerApName\fR, and displays its server ID with a listing of all registered servers\&.Run the client application from another terminal window or prompt: +.sp +.nf +\f3java HelloClient \-ORBInitialPort 1050 \-ORBInitialHost localhost\fP +.fi +.nf +\f3\fP +.fi +.sp +For this example, you can omit \f3-ORBInitialHost localhost\fR because the name server is running on the same host as the \f3Hello\fR client\&. If the name server is running on a different host, then use the -\f3ORBInitialHost nameserverhost\fR option to specify the host on which the IDL name server is running\&.Specify the name server (\f3orbd\fR) port as done in the previous step, for example, \f3-ORBInitialPort 1050\fR\&. When you finish experimenting with the ORBD Server Manager, be sure to shut down or terminate the name server (\f3orbd\fR) and \f3servertool\fR\&. To shut down \f3orbd\fR from am MS-DOS prompt, select the window that is running the server and enter \fICtrl+C\fR to shut it down\&. +.PP +To shut down \f3orbd\fR from an Oracle Solaris shell, find the process, and terminate with the \f3kill\fR command\&. The server continues to wait for invocations until it is explicitly stopped\&. To shut down the \f3servertool\fR, type \fIquit\fR and press the \fIEnter\fR key\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +servertool(1) +.TP 0.2i +\(bu +Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/pack200.1 b/jdk-1.8.0.281/man/man1/pack200.1 new file mode 100755 index 0000000..7298c13 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/pack200.1 @@ -0,0 +1,270 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Deployment Tools +.\" Title: pack200.1 +.\" +.if n .pl 99999 +.TH pack200 1 "21 November 2013" "JDK 8" "Java Deployment Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +pack200 \- Packages a JAR file into a compressed pack200 file for web deployment\&. +.SH SYNOPSIS +.sp +.nf + +\fBpack200\fR [\fIoptions\fR] \fIoutput\-file\fR \fIJAR\-file\fR +.fi +.sp +Options can be in any order\&. The last option on the command line or in a properties file supersedes all previously specified options\&. +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIoutput-file\fR +Name of the output file\&. +.TP +\fIJAR-file\fR +Name of the input file\&. +.SH DESCRIPTION +The \f3pack200\fR command is a Java application that transforms a JAR file into a compressed pack200 file with the Java gzip compressor\&. The pack200 files are highly compressed files that can be directly deployed to save bandwidth and reduce download time\&. +.PP +The \f3pack200\fR command has several options to fine-tune and set the compression engine\&. The typical usage is shown in the following example, where \f3myarchive\&.pack\&.gz\fR is produced with the default \f3pack200\fR command settings: +.sp +.nf +\f3pack200 myarchive\&.pack\&.gz myarchive\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +.TP +-r, --repack +.br +Produces a JAR file by packing and unpacking a JAR file\&. The resulting file can be used as an input to the \f3jarsigner\fR(1) tool\&. The following example packs and unpacks the myarchive\&.jar file: +.sp +.nf +\f3pack200 \-\-repack myarchive\-packer\&.jar myarchive\&.jar\fP +.fi +.nf +\f3pack200 \-\-repack myarchive\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The following example preserves the order of files in the input file\&. +.TP +-g, --no-gzip +.br +Produces a \f3pack200\fR file\&. With this option, a suitable compressor must be used, and the target system must use a corresponding decompresser\&. +.sp +.nf +\f3pack200 \-\-no\-gzip myarchive\&.pack myarchive\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-G, --strip-debug +.br +Strips debugging attributes from the output\&. These include \f3SourceFile\fR, \f3LineNumberTable\fR, \f3LocalVariableTable\fR and \f3LocalVariableTypeTable\fR\&. Removing these attributes reduces the size of both downloads and installations, but reduces the usefulness of debuggers\&. +.TP +--keep-file-order +.br +Preserve the order of files in the input file\&. This is the default behavior\&. +.TP +-O, --no-keep-file-order +.br +The packer reorders and transmits all elements\&. The packer can also remove JAR directory names to reduce the download size\&. However, certain JAR file optimizations, such as indexing, might not work correctly\&. +.TP +-S\fIvalue\fR , --segment-limit=\fIvalue\fR +.br +The value is the estimated target size \fIN\fR (in bytes) of each archive segment\&. If a single input file requires more than \fIN\fR bytes, then its own archive segment is provided\&. As a special case, a value of \f3-1\fR produces a single large segment with all input files, while a value of 0 produces one segment for each class\&. Larger archive segments result in less fragmentation and better compression, but processing them requires more memory\&. + +The size of each segment is estimated by counting the size of each input file to be transmitted in the segment with the size of its name and other transmitted properties\&. + +The default is -1, which means that the packer creates a single segment output file\&. In cases where extremely large output files are generated, users are strongly encouraged to use segmenting or break up the input file into smaller JARs\&. + +A 10 MB JAR packed without this limit typically packs about 10 percent smaller, but the packer might require a larger Java heap (about 10 times the segment limit)\&. +.TP +-E\fIvalue\fR , --effort=\fIvalue\fR +.br +If the value is set to a single decimal digit, then the packer uses the indicated amount of effort in compressing the archive\&. Level 1 might produce somewhat larger size and faster compression speed, while level 9 takes much longer, but can produce better compression\&. The special value 0 instructs the \f3pack200\fR command to copy through the original JAR file directly with no compression\&. The JSR 200 standard requires any unpacker to understand this special case as a pass-through of the entire archive\&. + +The default is 5, to invest a modest amount of time to produce reasonable compression\&. +.TP +-H\fIvalue\fR , --deflate-hint=\fIvalue\fR +.br +Overrides the default, which preserves the input information, but can cause the transmitted archive to be larger\&. The possible values are: \f3true\fR, \f3false\fR, or \f3keep\fR\&. + +If the \f3value\fR is \f3true\fR or false, then the \f3packer200\fR command sets the deflation hint accordingly in the output archive and does not transmit the individual deflation hints of archive elements\&. + +The \f3keep\fR value preserves deflation hints observed in the input JAR\&. This is the default\&. +.TP +-m\fIvalue\fR , --modification-time=\fIvalue\fR +.br +The possible values are \f3latest\fR and \f3keep\fR\&. + +If the value is latest, then the packer attempts to determine the latest modification time, among all the available entries in the original archive, or the latest modification time of all the available entries in that segment\&. This single value is transmitted as part of the segment and applied to all the entries in each segment\&. This can marginally decrease the transmitted size of the archive at the expense of setting all installed files to a single date\&. + +If the value is \f3keep\fR, then modification times observed in the input JAR are preserved\&. This is the default\&. +.TP +-P\fIfile\fR , --pass-file=\fIfile\fR +.br +Indicates that a file should be passed through bytewise with no compression\&. By repeating the option, multiple files can be specified\&. There is no pathname transformation, except that the system file separator is replaced by the JAR file separator forward slash (/)\&. The resulting file names must match exactly as strings with their occurrences in the JAR file\&. If \f3file\fR is a directory name, then all files under that directory are passed\&. +.TP +-U\fIaction\fR , --unknown-attribute=\fIaction\fR +.br +Overrides the default behavior, which means that the class file that contains the unknown attribute is passed through with the specified \f3action\fR\&. The possible values for actions are \f3error\fR, \f3strip\fR, or \f3pass\fR\&. + +If the value is \f3error\fR, then the entire \f3pack200\fR command operation fails with a suitable explanation\&. + +If the value is \f3strip\fR, then the attribute is dropped\&. Removing the required Java Virtual Machine (JVM) attributes can cause class loader failures\&. + +If the value is \f3pass\fR, then the entire class is transmitted as though it is a resource\&. +.TP +.nf +-C\fIattribute-name\fR=\fIlayout\fR , --class-attribute=\fIattribute-name\fR=\fIaction\fR +.br +.fi +See next option\&. +.TP +.nf +-F\fIattribute-name\fR=\fIlayout\fR , --field-attribute=\fIattribute-name\fR=\fIaction\fR +.br +.fi +See next option\&. +.TP +.nf +-M\fIattribute-name\fR=\fIlayout\fR , --method-attribute=\fIattribute-name\fR=\fIaction\fR +.br +.fi +See next option\&. +.TP +.nf +-D\fIattribute-name\fR=\fIlayout\fR , --code-attribute=\fIattribute-name\fR=\fIaction\fR +.br +.fi +With the previous four options, the attribute layout can be specified for a class entity, such as \f3class-attribute\fR, \f3field-attribute\fR, \f3method-attribute\fR, and \f3code-attribute\fR\&. The \fIattribute-name\fR is the name of the attribute for which the layout or action is being defined\&. The possible values for \fIaction\fR are \f3some-layout-string\fR, \f3error\fR, \f3strip\fR, \f3pass\fR\&. + +\f3some-layout-string\fR: The layout language is defined in the JSR 200 specification, for example: \f3--class-attribute=SourceFile=RUH\fR\&. + +If the value is \f3error\fR, then the \f3pack200\fR operation fails with an explanation\&. + +If the value is \f3strip\fR, then the attribute is removed from the output\&. Removing JVM-required attributes can cause class loader failures\&. For example, \f3--class-attribute=CompilationID=pass\fR causes the class file that contains this attribute to be passed through without further action by the packer\&. + +If the value is \f3pass\fR, then the entire class is transmitted as though it is a resource\&. +.TP +-f \fIpack\&.properties\fR , --config-file=\fIpack\&.properties\fR +.br +A configuration file, containing Java properties to initialize the packer, can be specified on the command line\&. +.sp +.nf +\f3pack200 \-f pack\&.properties myarchive\&.pack\&.gz myarchive\&.jar\fP +.fi +.nf +\f3more pack\&.properties\fP +.fi +.nf +\f3# Generic properties for the packer\&.\fP +.fi +.nf +\f3modification\&.time=latest\fP +.fi +.nf +\f3deflate\&.hint=false\fP +.fi +.nf +\f3keep\&.file\&.order=false\fP +.fi +.nf +\f3# This option will cause the files bearing new attributes to\fP +.fi +.nf +\f3# be reported as an error rather than passed uncompressed\&.\fP +.fi +.nf +\f3unknown\&.attribute=error\fP +.fi +.nf +\f3# Change the segment limit to be unlimited\&.\fP +.fi +.nf +\f3segment\&.limit=\-1\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-v, --verbose +.br +Outputs minimal messages\&. Multiple specification of this option will create more verbose messages\&. +.TP +-q, --quiet +.br +Specifies quiet operation with no messages\&. +.TP +-l\fIfilename\fR , --log-file=\fIfilename\fR +.br +Specifies a log file to output messages\&. +.TP +-?, -h, --help +.br +Prints help information about this command\&. +.TP +-V, --version +.br +Prints version information about this command\&. +.TP +-J\fIoption\fR +.br +Passes the specified option to the Java Virtual Machine\&. For more information, see the reference page for the java(1) command\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. +.SH EXIT\ STATUS +The following exit values are returned: 0 for successful completion and a number greater than 0 when an error occurs\&. +.SH NOTES +This command should not be confused with \f3pack\fR(1)\&. The \f3pack\fR and \f3pack200\fR commands are separate products\&. +.PP +The Java SE API Specification provided with the JDK is the superseding authority, when there are discrepancies\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +unpack200(1) +.TP 0.2i +\(bu +jar(1) +.TP 0.2i +\(bu +jarsigner(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/policytool.1 b/jdk-1.8.0.281/man/man1/policytool.1 new file mode 100755 index 0000000..263c0e8 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/policytool.1 @@ -0,0 +1,94 @@ +'\" t +.\" Copyright (c) 2001, 2015, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 03 March 2015 +.\" SectDesc: Security Tools +.\" Title: policytool.1 +.\" +.if n .pl 99999 +.TH policytool 1 "03 March 2015" "JDK 8" "Security Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +policytool \- Reads and writes a plain text policy file based on user input through the utility GUI\&. +.SH SYNOPSIS +.sp +.nf + +\fBpolicytool\fR [ \fB\-file\fR ] [ \fIfilename\fR ] +.fi +.sp +.TP +-file +.br +Directs the \f3policytool\fR command to load a policy file\&. +.TP +\fIfilename\fR +The name of the file to be loaded\&. +.PP +\fIExamples\fR: +.PP +Run the policy tool administrator utility: +.sp +.nf +\f3policytool\fP +.fi +.nf +\f3\fP +.fi +.sp +Run the \f3policytool\fR command and load the specified file: +.sp +.nf +\f3policytool \-file \fImypolicyfile\fR\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH DESCRIPTION +The \f3policytool\fR command calls an administrator\&'s GUI that enables system administrators to manage the contents of local policy files\&. A policy file is a plain-text file with a \f3\&.policy\fR extension, that maps remote requestors by domain, to permission objects\&. For details, see Default Policy Implementation and Policy File Syntax at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html +.SH OPTIONS +.TP +-file +.br +Directs the \f3policytool\fR command to load a policy file\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +Default Policy Implementation and Policy File Syntax at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html +.TP 0.2i +\(bu +Policy File Creation and Management at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyGuide\&.html +.TP 0.2i +\(bu +Permissions in Java SE Development Kit (JDK) at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/permissions\&.html +.TP 0.2i +\(bu +Java Security Overview at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/overview/jsoverview\&.html +.TP 0.2i +\(bu +Java Cryptography Architecture (JCA) Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/rmic.1 b/jdk-1.8.0.281/man/man1/rmic.1 new file mode 100755 index 0000000..a916852 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/rmic.1 @@ -0,0 +1,203 @@ +'\" t +.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Remote Method Invocation (RMI) Tools +.\" Title: rmic.1 +.\" +.if n .pl 99999 +.TH rmic 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +rmic \- Generates stub, skeleton, and tie classes for remote objects that use the Java Remote Method Protocol (JRMP) or Internet Inter-Orb protocol (IIOP)\&. Also generates Object Management Group (OMG) Interface Definition Language (IDL) +.SH SYNOPSIS +.sp +.nf + +\fBrmic\fR [ \fIoptions\fR ] \fIpackage\-qualified\-class\-names\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line \f3options\fR\&. See Options\&. +.TP +\fIpackage-qualified-class-names\fR +Class names that include their packages, for example, \f3java\&.awt\&.Color\fR\&. +.SH DESCRIPTION +\fIDeprecation Note:\fR Support for static generation of Java Remote Method Protocol (JRMP) stubs and skeletons has been deprecated\&. Oracle recommends that you use dynamically generated JRMP stubs instead, eliminating the need to use this tool for JRMP-based applications\&. See the \f3java\&.rmi\&.server\&.UnicastRemoteObject\fR specification at http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/server/UnicastRemoteObject\&.html for further information\&. +.PP +The \f3rmic\fR compiler generates stub and skeleton class files using the Java Remote Method Protocol (JRMP) and stub and tie class files (IIOP protocol) for remote objects\&. These class files are generated from compiled Java programming language classes that are remote object implementation classes\&. A remote implementation class is a class that implements the interface \f3java\&.rmi\&.Remote\fR\&. The class names in the \f3rmic\fR command must be for classes that were compiled successfully with the \f3javac\fR command and must be fully package qualified\&. For example, running the \f3rmic\fR command on the class file name \f3HelloImpl\fR as shown here creates the \f3HelloImpl_Stub\&.class\fRfile in the hello subdirectory (named for the class\&'s package): +.sp +.nf +\f3rmic hello\&.HelloImpl\fP +.fi +.nf +\f3\fP +.fi +.sp +A skeleton for a remote object is a JRMP protocol server-side entity that has a method that dispatches calls to the remote object implementation\&. +.PP +A tie for a remote object is a server-side entity similar to a skeleton, but communicates with the client with the IIOP protocol\&. +.PP +A stub is a client-side proxy for a remote object that is responsible for communicating method invocations on remote objects to the server where the actual remote object implementation resides\&. A client\&'s reference to a remote object, therefore, is actually a reference to a local stub\&. +.PP +By default, the \f3rmic\fR command generates stub classes that use the 1\&.2 JRMP stub protocol version only, as though the \f3-v1\&.2\fR option was specified\&. The \f3-vcompat\fR option was the default in releases before 5\&.0\&. Use the \f3-iiop\fR option to generate stub and tie classes for the IIOP protocol\&. See Options\&. +.PP +A stub implements only the remote interfaces, and not any local interfaces that the remote object also implements\&. Because a JRMP stub implements the same set of remote interfaces as the remote object, a client can use the Java programming language built-in operators for casting and type checking\&. For IIOP, the \f3PortableRemoteObject\&.narrow\fR method must be used\&. +.SH OPTIONS +.TP +-bootclasspath \fIpath\fR +.br +Overrides the location of bootstrap class files\&. +.TP +-classpath path +.br +Specifies the path the \f3rmic\fR command uses to look up classes\&. This option overrides the default or the \f3CLASSPATH\fR environment variable when it is set\&. Directories are separated by colons\&. The general format for path is: \f3\&.:<your_path>\fR, for example: \f3\&.:/usr/local/java/classes\fR\&. +.TP +-d \fIdirectory\fR +.br +Specifies the root destination directory for the generated class hierarchy\&. You can use this option to specify a destination directory for the stub, skeleton, and tie files\&. For example, the following command places the stub and skeleton classes derived from MyClass into the directory /java/classes/exampleclass\&. +.sp +.nf +\f3rmic \-d /java/classes exampleclass\&.MyClass\fP +.fi +.nf +\f3\fP +.fi +.sp + + +If the \f3-d\fR option is not specified, then the default behavior is as if \f3-d \&.\fR was specified\&. The package hierarchy of the target class is created in the current directory, and stub/tie/skeleton files are placed within it\&. In some earlier releases of the \f3rmic\fR command, if the \f3-d\fR option was not specified, then the package hierarchy was not created, and all of the output files were placed directly in the current directory\&. +.TP +-extdirs \fIpath\fR +.br +Overrides the location of installed extensions\&. +.TP +-g +.br +Enables the generation of all debugging information, including local variables\&. By default, only line number information is generated\&. +.TP +-idl +.br +Causes the \f3rmic\fR command to generate OMG IDL for the classes specified and any classes referenced\&. IDL provides a purely declarative, programming language-independent way to specify an API for an object\&. The IDL is used as a specification for methods and data that can be written in and called from any language that provides CORBA bindings\&. This includes Java and C++ among others\&. See Java IDL: IDL to Java Language Mapping at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.html + +When the \f3-idl\fR option is used, other options also include: +.RS +.TP 0.2i +\(bu +The \f3-always\fR or \f3-alwaysgenerate\fR options force regeneration even when existing stubs/ties/IDL are newer than the input class\&. +.TP 0.2i +\(bu +The \f3-factory\fR option uses the \f3factory\fR keyword in generated IDL\&. +.TP 0.2i +\(bu +The \f3-idlModule\fR from J\f3avaPackage[\&.class]\fR\f3toIDLModule\fR specifies \f3IDLEntity\fR package mapping, for example: \f3-idlModule\fR\f3my\&.module my::real::idlmod\fR\&. +.TP 0.2i +\(bu +\f3-idlFile\fR\f3fromJavaPackage[\&.class] toIDLFile\fR specifies \f3IDLEntity\fR file mapping, for example: \f3-idlFile test\&.pkg\&.X TEST16\&.idl\fR\&. +.RE + +.TP +-iiop +.br +Causes the \f3rmic\fR command to generate IIOP stub and tie classes, rather than JRMP stub and skeleton classes\&. A stub class is a local proxy for a remote object and is used by clients to send calls to a server\&. Each remote interface requires a stub class, which implements that remote interface\&. A client reference to a remote object is a reference to a stub\&. Tie classes are used on the server side to process incoming calls, and dispatch the calls to the proper implementation class\&. Each implementation class requires a tie class\&. + +If you call the \f3rmic\fR command with the \f3-iiop\fR, then it generates stubs and ties that conform to this naming convention: +.sp +.nf +\f3_<implementationName>_stub\&.class\fP +.fi +.nf +\f3_<interfaceName>_tie\&.class\fP +.fi +.nf +\f3\fP +.fi +.sp +.RS +.TP 0.2i +\(bu +When you use the \f3-iiop\fR option, other options also include: +.TP 0.2i +\(bu +The \f3-always\fR or \f3-alwaysgenerate\fR options force regeneration even when existing stubs/ties/IDL are newer than the input class\&. +.TP 0.2i +\(bu +The \f3-nolocalstubs\fR option means do not create stubs optimized for same-process clients and servers\&. +.TP 0.2i +\(bu +The \f3-noValueMethods\fR option must be used with the \f3-idl\fR option\&. The \f3-noValueMethods\fR option prevents the addition of \f3valuetype\fR methods and initializers to emitted IDL\&. These methods and initializers are optional for valuetypes, and are generated unless the \f3-noValueMethods\fR option is specified with the \f3-idl\fR option\&. +.TP 0.2i +\(bu +The \f3-poa\fR option changes the inheritance from \f3org\&.omg\&.CORBA_2_3\&.portable\&.ObjectImpl\fR to \f3org\&.omg\&.PortableServer\&.Servant\fR\&. The \f3PortableServer\fR module for the Portable Object Adapter (POA) defines the native \f3Servant\fR type\&. In the Java programming language, the \f3Servant\fR type is mapped to the \f3Java org\&.omg\&.PortableServer\&.Servant\fR class\&. It serves as the base class for all POA servant implementations and provides a number of methods that can be called by the application programmer, and methods that are called by the POA and that can be overridden by the user to control aspects of servant behavior\&. Based on the OMG IDL to Java Language Mapping Specification, CORBA V 2\&.3\&.1 ptc/00-01-08\&.pdf\&..RE + +.TP +-J +.br +Used with any Java command, the \f3-J\fR option passes the argument that follows the \f3-J\fR (no spaces between the \f3-J\fRand the argument) to the Java interpreter +.TP +-keep or -keepgenerated +.br +Retains the generated \f3\&.java\fR source files for the stub, skeleton, and tie classes and writes them to the same directory as the\f3\&.class\fR files\&. +.TP +-nowarn +.br +Turns off warnings\&. When the \f3-nowarn\fR options is used\&. The compiler does not print out any warnings\&. +.TP +-nowrite +.br +Does not write compiled classes to the file system\&. +.TP +-vcompat (deprecated) +.br +Generates stub and skeleton classes that are compatible with both the 1\&.1 and 1\&.2 JRMP stub protocol versions\&. This option was the default in releases before 5\&.0\&. The generated stub classes use the 1\&.1 stub protocol version when loaded in a JDK 1\&.1 virtual machine and use the 1\&.2 stub protocol version when loaded into a 1\&.2 (or later) virtual machine\&. The generated skeleton classes support both 1\&.1 and 1\&.2 stub protocol versions\&. The generated classes are relatively large to support both modes of operation\&. Note: This option has been deprecated\&. See Description\&. +.TP +-verbose +.br +Causes the compiler and linker to print out messages about what classes are being compiled and what class files are being loaded\&. +.TP +-v1\&.1 (deprecated) +.br +Generates stub and skeleton classes for the 1\&.1 JRMP stub protocol version only\&. The \f3-v1\&.1\fR option is only useful for generating stub classes that are serialization-compatible with preexisting, statically deployed stub classes that were generated by the \f3rmic\fR command from JDK 1\&.1 and that cannot be upgraded (and dynamic class loading is not being used)\&. Note: This option has been deprecated\&. See Description\&. +.TP +-v1\&.2 (deprecated) +.br +(Default) Generates stub classes for the 1\&.2 JRMP stub protocol version only\&. No skeleton classes are generated because skeleton classes are not used with the 1\&.2 stub protocol version\&. The generated stub classes do not work when they are loaded into a JDK 1\&.1 virtual machine\&. Note: This option has been deprecated\&. See Description\&. +.SH ENVIRONMENT\ VARIABLES +.TP +CLASSPATH +Used to provide the system a path to user-defined classes\&. Directories are separated by colons, for example: \f3\&.:/usr/local/java/classes\fR\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +javac(1) +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +Setting the Class Path +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/rmid.1 b/jdk-1.8.0.281/man/man1/rmid.1 new file mode 100755 index 0000000..923724a --- /dev/null +++ b/jdk-1.8.0.281/man/man1/rmid.1 @@ -0,0 +1,294 @@ +'\" t +.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Remote Method Invocation (RMI) Tools +.\" Title: rmid.1 +.\" +.if n .pl 99999 +.TH rmid 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +rmid \- Starts the activation system daemon that enables objects to be registered and activated in a Java Virtual Machine (JVM)\&. +.SH SYNOPSIS +.sp +.nf + +\fBrmid\fR [\fIoptions\fR] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.SH DESCRIPTION +The \f3rmid\fR command starts the activation system daemon\&. The activation system daemon must be started before activatable objects can be either registered with the activation system or activated in a JVM\&. For details on how to write programs that use activatable objects, the \fIUsing Activation\fR tutorial at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi/activation/overview\&.html +.PP +Start the daemon by executing the \f3rmid\fR command and specifying a security policy file, as follows: +.sp +.nf +\f3rmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fP +.fi +.nf +\f3\fP +.fi +.sp +When you run Oracle\(cqs implementation of the \f3rmid\fR command, by default you must specify a security policy file so that the \f3rmid\fR command can verify whether or not the information in each \f3ActivationGroupDesc\fR is allowed to be used to start a JVM for an activation group\&. Specifically, the command and options specified by the \f3CommandEnvironment\fR and any properties passed to an \f3ActivationGroupDesc\fR constructor must now be explicitly allowed in the security policy file for the \f3rmid\fR command\&. The value of the \f3sun\&.rmi\&.activation\&.execPolicy\fR property dictates the policy that the \f3rmid\fR command uses to determine whether or not the information in an \f3ActivationGroupDesc\fR can be used to start a JVM for an activation group\&. For more information see the description of the -J-Dsun\&.rmi\&.activation\&.execPolicy=policy option\&. +.PP +Executing the \f3rmid\fR command starts the Activator and an internal registry on the default port1098 and binds an \f3ActivationSystem\fR to the name \f3java\&.rmi\&.activation\&.ActivationSystem\fR in this internal registry\&. +.PP +To specify an alternate port for the registry, you must specify the \f3-port\fR option when you execute the \f3rmid\fR command\&. For example, the following command starts the activation system daemon and a registry on the registry\&'s default port, 1099\&. +.sp +.nf +\f3rmid \-J\-Djava\&.security\&.policy=rmid\&.policy \-port 1099\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH START\ RMID\ ON\ DEMAND +An alternative to starting \f3rmid\fR from the command line is to configure \f3inetd\fR (Oracle Solaris) or \f3xinetd\fR (Linux) to start \f3rmid\fR on demand\&. +.PP +When RMID starts, it attempts to obtain an inherited channel (inherited from \f3inetd\fR/\f3xinetd\fR) by calling the \f3System\&.inheritedChannel\fR method\&. If the inherited channel is null or not an instance of \f3java\&.nio\&.channels\&.ServerSocketChannel\fR, then RMID assumes that it was not started by \f3inetd\fR/\f3xinetd\fR, and it starts as previously described\&. +.PP +If the inherited channel is a \f3ServerSocketChannel\fR instance, then RMID uses the \f3java\&.net\&.ServerSocket\fR obtained from the \f3ServerSocketChannel\fR as the server socket that accepts requests for the remote objects it exports: The registry in which the \f3java\&.rmi\&.activation\&.ActivationSystem\fR is bound and the \f3java\&.rmi\&.activation\&.Activator\fR remote object\&. In this mode, RMID behaves the same as when it is started from the command line, except in the following cases: +.TP 0.2i +\(bu +Output printed to \f3System\&.err\fR is redirected to a file\&. This file is located in the directory specified by the \f3java\&.io\&.tmpdir\fR system property (typically \f3/var/tmp\fR or \f3/tmp\fR) with the prefix \f3rmid-err\fR and the suffix \f3tmp\fR\&. +.TP 0.2i +\(bu +The \f3-port\fR option is not allowed\&. If this option is specified, then RMID exits with an error message\&. +.TP 0.2i +\(bu +The \f3-log\fR option is required\&. If this option is not specified, then RMID exits with an error message +.PP +See the man pages for \f3inetd\fR (Oracle Solaris) or \f3xinetd\fR (Linux) for details on how to configure services to be started on demand\&. +.SH OPTIONS +.TP +-C\fIoption\fR +.br +Specifies an option that is passed as a command-line argument to each child process (activation group) of the \f3rmid\fR command when that process is created\&. For example, you could pass a property to each virtual machine spawned by the activation system daemon: +.sp +.nf +\f3rmid \-C\-Dsome\&.property=value\fP +.fi +.nf +\f3\fP +.fi +.sp + + +This ability to pass command-line arguments to child processes can be useful for debugging\&. For example, the following command enables server-call logging in all child JVMs\&. +.sp +.nf +\f3rmid \-C\-Djava\&.rmi\&.server\&.logCalls=true\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-J\fIoption\fR +.br +Specifies an option that is passed to the Java interpreter running RMID\&. For example, to specify that the \f3rmid\fR command use a policy file named \f3rmid\&.policy\fR, the \f3-J\fR option can be used to define the \f3java\&.security\&.policy\fR property on the \f3rmid\fR command line, for example: +.sp +.nf +\f3rmid \-J\-Djava\&.security\&.policy\-rmid\&.policy\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-J-Dsun\&.rmi\&.activation\&.execPolicy=\fIpolicy\fR +.br +Specifies the policy that RMID employs to check commands and command-line options used to start the JVM in which an activation group runs\&. Please note that this option exists only in Oracle\&'s implementation of the Java RMI activation daemon\&. If this property is not specified on the command line, then the result is the same as though \f3-J-Dsun\&.rmi\&.activation\&.execPolicy=default\fR were specified\&. The possible values of \f3policy\fR can be \f3default\fR, \f3policyClassName\fR, or \f3none\fR\&. +.RS +.TP 0.2i +\(bu +default + +The \f3default\fR or unspecified value \f3execPolicy\fR allows the \f3rmid\fR command to execute commands with specific command-line options only when the \f3rmid\fR command was granted permission to execute those commands and options in the security policy file that the \f3rmid\fR command uses\&. Only the default activation group implementation can be used with the default execution policy\&. + +The \f3rmid\fR command starts a JVM for an activation group with the information in the group\&'s registered activation group descriptor, an \f3ActivationGroupDesc\fR\&. The group descriptor specifies an optional \f3ActivationGroupDesc\&.CommandEnvironment\fR that includes the command to execute to start the activation group and any command-line options to be added to the command line\&. By default, the \f3rmid\fR command uses the \f3java\fR command found in \f3java\&.home\fR\&. The group descriptor also contains properties overrides that are added to the command line as options defined as: \f3-D<property>=<value>\fR\&.The \f3com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR permission grants the \f3rmid\fR command permission to execute a command that is specified in the group descriptor\&'s \f3CommandEnvironment\fR to start an activation group\&. The \f3com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR permission enables the \f3rmid\fR command to use command-line options, specified as properties overrides in the group descriptor or as options in the \f3CommandEnvironment\fR when starting the activation group\&.When granting the \f3rmid\fR command permission to execute various commands and options, the permissions \f3ExecPermission\fR and \f3ExecOptionPermission\fR must be granted to all code sources\&. + +\fIExecPermission\fR + +The \f3ExecPermission\fR class represents permission for the \f3rmid\fR command to execute a specific command to start an activation group\&. + +\fISyntax\fR: The name of an \f3ExecPermission\fR is the path name of a command to grant the \f3rmid\fR command permission to execute\&. A path name that ends in a slash (/) and an asterisk (*) indicates that all of the files contained in that directory where slash is the file-separator character, \f3File\&.separatorChar\fR\&. A path name that ends in a slash (/) and a minus sign (-) indicates all files and subdirectories contained in that directory (recursively)\&. A path name that consists of the special token \f3<<ALL FILES>>\fR matches any file\&. + +A path name that consists of an asterisk (*) indicates all the files in the current directory\&. A path name that consists of a minus sign (-) indicates all the files in the current directory and (recursively) all files and subdirectories contained in the current directory\&. + +\fIExecOptionPermission\fR + +The \f3ExecOptionPermission\fR class represents permission for the \f3rmid\fR command to use a specific command-line option when starting an activation group\&. The name of an \f3ExecOptionPermission\fR is the value of a command-line option\&. + +\fISyntax\fR: Options support a limited wild card scheme\&. An asterisk signifies a wild card match, and it can appear as the option name itself (matches any option), or an asterisk (*) can appear at the end of the option name only when the asterisk (*) follows a dot (\&.) or an equals sign (=)\&. + +For example: \f3*\fR or \f3-Dmydir\&.*\fR or \f3-Da\&.b\&.c=*\fR is valid, but \f3*mydir\fR or \f3-Da*b\fR or \f3ab*\fR is not\&. + +\fIPolicy file for rmid\fR + +When you grant the \f3rmid\fR command permission to execute various commands and options, the permissions \f3ExecPermission\fR and \f3ExecOptionPermission\fR must be granted to all code sources (universally)\&. It is safe to grant these permissions universally because only the \f3rmid\fR command checks these permissions\&. + +An example policy file that grants various execute permissions to the \f3rmid\fR command is: +.sp +.nf +\f3grant {\fP +.fi +.nf +\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fP +.fi +.nf +\f3 "/files/apps/java/jdk1\&.7\&.0/solaris/bin/java";\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fP +.fi +.nf +\f3 "/files/apps/rmidcmds/*";\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP +.fi +.nf +\f3 "\-Djava\&.security\&.policy=/files/policies/group\&.policy";\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP +.fi +.nf +\f3 "\-Djava\&.security\&.debug=*";\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP +.fi +.nf +\f3 "\-Dsun\&.rmi\&.*";\fP +.fi +.nf +\f3};\fP +.fi +.nf +\f3\fP +.fi +.sp + + +The first permission granted allows the \f3rmid\fR tcommand o execute the 1\&.7\&.0 release of the \f3java\fR command, specified by its explicit path name\&. By default, the version of the \f3java\fR command found in \f3java\&.home\fR is used (the same one that the \f3rmid\fR command uses), and does not need to be specified in the policy file\&. The second permission allows the \f3rmid\fR command to execute any command in the directory \f3/files/apps/rmidcmds\fR\&. + +The third permission granted, an \f3ExecOptionPermission\fR, allows the \f3rmid\fR command to start an activation group that defines the security policy file to be \f3/files/policies/group\&.policy\fR\&. The next permission allows the \f3java\&.security\&.debug property\fR to be used by an activation group\&. The last permission allows any property in the \f3sun\&.rmi property\fR name hierarchy to be used by activation groups\&. + +To start the \f3rmid\fR command with a policy file, the \f3java\&.security\&.policy\fR property needs to be specified on the \f3rmid\fR command line, for example: + +\f3rmid -J-Djava\&.security\&.policy=rmid\&.policy\fR\&. +.TP 0.2i +\(bu +<policyClassName> + +If the default behavior is not flexible enough, then an administrator can provide, when starting the \f3rmid\fR command, the name of a class whose \f3checkExecCommand\fR method is executed to check commands to be executed by the \f3rmid\fR command\&. + +The \f3policyClassName\fR specifies a public class with a public, no-argument constructor and an implementation of the following \f3checkExecCommand\fR method: +.sp +.nf +\f3 public void checkExecCommand(ActivationGroupDesc desc, String[] command)\fP +.fi +.nf +\f3 throws SecurityException;\fP +.fi +.nf +\f3\fP +.fi +.sp + + +Before starting an activation group, the \f3rmid\fR command calls the policy\&'s \f3checkExecCommand\fR method and passes to it the activation group descriptor and an array that contains the complete command to start the activation group\&. If the \f3checkExecCommand\fR throws a \f3SecurityException\fR, then the \f3rmid\fR command does not start the activation group and an \f3ActivationException\fR is thrown to the caller attempting to activate the object\&. +.TP 0.2i +\(bu +none + +If the \f3sun\&.rmi\&.activation\&.execPolicy\fR property value is \f3none\fR, then the \f3rmid\fR command does not perform any validation of commands to start activation groups\&. +.RE + +.TP +-log \fIdir\fR +.br +Specifies the name of the directory the activation system daemon uses to write its database and associated information\&. The log directory defaults to creating a log, in the directory in which the \f3rmid\fR command was executed\&. +.TP +-port \fIport\fR +.br +Specifies the port the registry uses\&. The activation system daemon binds the \f3ActivationSystem\fR, with the name \f3java\&.rmi\&.activation\&.ActivationSystem\fR, in this registry\&. The \f3ActivationSystem\fR on the local machine can be obtained using the following \f3Naming\&.lookup\fR method call: +.sp +.nf +\f3import java\&.rmi\&.*; \fP +.fi +.nf +\f3 import java\&.rmi\&.activation\&.*;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 ActivationSystem system; system = (ActivationSystem)\fP +.fi +.nf +\f3 Naming\&.lookup("//:port/java\&.rmi\&.activation\&.ActivationSystem");\fP +.fi +.nf +\f3\fP +.fi +.sp + +.TP +-stop +.br +Stops the current invocation of the \f3rmid\fR command for a port specified by the \f3-port\fR option\&. If no port is specified, then this option stops the \f3rmid\fR invocation running on port 1098\&. +.SH ENVIRONMENT\ VARIABLES +.TP +CLASSPATH +Used to provide the system a path to user-defined classes\&. Directories are separated by colons, for example: \f3\&.:/usr/local/java/classes\fR\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +Setting the Class Path +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/rmiregistry.1 b/jdk-1.8.0.281/man/man1/rmiregistry.1 new file mode 100755 index 0000000..7caad57 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/rmiregistry.1 @@ -0,0 +1,78 @@ +'\" t +.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Remote Method Invocation (RMI) Tools +.\" Title: rmiregistry.1 +.\" +.if n .pl 99999 +.TH rmiregistry 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +rmiregistry \- Starts a remote object registry on the specified port on the current host\&. +.SH SYNOPSIS +.sp +.nf + +\fBrmiregistry\fR [ \fIport\fR ] +.fi +.sp +.TP +\fIport\fR +The number of a \f3port\fR on the current host at which to start the remote object registry\&. +.SH DESCRIPTION +The \f3rmiregistry\fR command creates and starts a remote object registry on the specified port on the current host\&. If the port is omitted, then the registry is started on port 1099\&. The \f3rmiregistry\fR command produces no output and is typically run in the background, for example: +.sp +.nf +\f3rmiregistry &\fP +.fi +.nf +\f3\fP +.fi +.sp +A remote object registry is a bootstrap naming service that is used by RMI servers on the same host to bind remote objects to names\&. Clients on local and remote hosts can then look up remote objects and make remote method invocations\&. +.PP +The registry is typically used to locate the first remote object on which an application needs to call methods\&. That object then provides application-specific support for finding other objects\&. +.PP +The methods of the \f3java\&.rmi\&.registry\&.LocateRegistry\fR class are used to get a registry operating on the local host or local host and port\&. +.PP +The URL-based methods of the \f3java\&.rmi\&.Naming\fR class operate on a registry and can be used to look up a remote object on any host and on the local host\&. Bind a simple name (string) to a remote object, rebind a new name to a remote object (overriding the old binding), unbind a remote object, and list the URL bound in the registry\&. +.SH OPTIONS +.TP +-J +.br +Used with any Java option to pass the option following the \f3-J\fR (no spaces between the \f3-J\fR and the option) to the Java interpreter\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +java(1) +.TP 0.2i +\(bu +\f3java\&.rmi\&.registry\&.LocateRegistry\fR class description at http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/registry/LocateRegistry\&.html +.TP 0.2i +\(bu +\f3java\&.rmi\&.Naming class description\fR at http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/Naming\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/schemagen.1 b/jdk-1.8.0.281/man/man1/schemagen.1 new file mode 100755 index 0000000..5f06cd1 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/schemagen.1 @@ -0,0 +1,101 @@ +'\" t +.\" Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Web Services Tools +.\" Title: schemagen.1 +.\" +.if n .pl 99999 +.TH schemagen 1 "21 November 2013" "JDK 8" "Java Web Services Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +schemagen \- Generates a schema for every name space that is referenced in your Java classes\&. +.SH SYNOPSIS +.sp +.nf + +\fBschemagen\fR [ \fIoptions\fR ] \fIjava\-files\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIjava-files\fR +The Java class files to be processed\&. +.SH DESCRIPTION +The schema generator creates a schema file for each name space referenced in your Java classes\&. Currently, you cannot control the name of the generated schema files\&. To control the schema file names, see Using SchemaGen with Ant at http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/schemagenTask\&.html +.PP +Start the schema generator with the appropriate \f3schemagen\fR shell script in the bin directory for your platform\&. The current schema generator can process either Java source files or class files\&. +.sp +.nf +\f3schemagen\&.sh Foo\&.java Bar\&.java \&.\&.\&.\fP +.fi +.nf +\f3Note: Writing schema1\&.xsd\fP +.fi +.nf +\f3\fP +.fi +.sp +If your java files reference other classes, then those classes must be accessible on your system \f3CLASSPATH\fR environment variable, or they need to be specified in the \f3schemagen\fR command line with the class path options\&. See Options\&. If the referenced files are not accessible or specified, then you get errors when you generate the schema\&. +.SH OPTIONS +.TP +-d \fIpath\fR +.br +The location where the \f3schemagen\fR command places processor-generated and \f3javac\fR-generated class files\&. +.TP +-cp \fIpath\fR +.br +The location where the \f3schemagen\fR command places user-specified files\&. +.TP +-classpath \fIpath\fR +.br +The location where the \f3schemagen\fR command places user-specified files\&. +.TP +-encoding \fIencoding\fR +.br +Specifies the encoding to use for \f3apt\fR or \f3javac\fR command invocations\&. +.TP +-episode \fIfile\fR +.br +Generates an episode file for separate compilation\&. +.TP +-version +.br +Displays release information\&. +.TP +-help +.br +Displays a help message\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +Using SchemaGen with Ant at http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/schemagenTask\&.html +.TP 0.2i +\(bu +Java Architecture for XML Binding (JAXB) at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/xml/jaxb/index\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/serialver.1 b/jdk-1.8.0.281/man/man1/serialver.1 new file mode 100755 index 0000000..6ebeca8 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/serialver.1 @@ -0,0 +1,90 @@ +'\" t +.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Remote Method Invocation (RMI) Tools +.\" Title: serialver.1 +.\" +.if n .pl 99999 +.TH serialver 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +serialver \- Returns the serial version UID for specified classes\&. +.SH SYNOPSIS +.sp +.nf + +\fBserialver\fR [ \fIoptions\fR ] [ \fIclassnames\fR ] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIclassnames\fR +The classes for which the \f3serialVersionUID\fR is to be returned\&. +.SH DESCRIPTION +The \f3serialver\fR command returns the \f3serialVersionUID\fR for one or more classes in a form suitable for copying into an evolving class\&. When called with no arguments, the \f3serialver\fR command prints a usage line\&. +.SH OPTIONS +.TP +-classpath \fIpath-files\fR +.br +Sets the search path for application classes and resources\&. Separate classes and resources with a colon (:)\&. +.TP +-show +.br +Displays a simple user interface\&. Enter the full class name and press either the \fIEnter\fR key or the \fIShow\fR button to display the \f3serialVersionUID\fR\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine, where option is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH NOTES +The \f3serialver\fR command loads and initializes the specified classes in its virtual machine, and by default, it does not set a security manager\&. If the \f3serialver\fR command is to be run with untrusted classes, then a security manager can be set with the following option: +.sp +.nf +\f3\-J\-Djava\&.security\&.manager\fP +.fi +.nf +\f3\fP +.fi +.sp +When necessary, a security policy can be specified with the following option: +.sp +.nf +\f3\-J\-Djava\&.security\&.policy=<policy file>\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +policytool(1) +.TP 0.2i +\(bu +The \f3java\&.io\&.ObjectStream\fR class description at http://docs\&.oracle\&.com/javase/8/docs/api/java/io/ObjectStreamClass\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/servertool.1 b/jdk-1.8.0.281/man/man1/servertool.1 new file mode 100755 index 0000000..ce22404 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/servertool.1 @@ -0,0 +1,117 @@ +'\" t +.\" Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java IDL and RMI-IIOP Tools +.\" Title: servertool.1 +.\" +.if n .pl 99999 +.TH servertool 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +servertool \- Provides an easy-to-use interface for developers to register, unregister, start up, and shut down a persistent server\&. +.SH SYNOPSIS +.sp +.nf + +\fBservertool\fR \-ORBInitialPort \fInameserverport\fR [ \fIoptions\fR ] [ \fIcommands \fR] +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +commands +The command-line commands\&. See Commands\&. +.SH DESCRIPTION +The \f3servertool\fR command provides the command-line interface for developers to register, unregister, start up, and shut down a persistent server\&. Command-line commands let you obtain various statistical information about the server\&. See Commands\&. +.SH OPTIONS +.TP +-ORBInitialHost \fInameserverhost\fR +.br +This options is required\&. It specifies the host machine on which the name server runs and listens for incoming requests\&. The \f3nameserverhost\fR value must specify the port on which the \f3orb\fR is running and listening for requests\&. The value defaults to \f3localhost\fR when this option is not specified\&. If \f3orbd\fR and \f3servertool\fR are running on different machines, then you must specify the name or IP address of the host on which \f3orbd\fR is running\&. + +\fINote:\fR On Oracle Solaris, you must become a root user to start a process on a port below 1024\&. Oracle recommends that you use a port number above or equal to 1024 for the \f3nameserverport\fR value\&. +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH COMMANDS +You can start the \f3servertool\fR command with or without a command-line command\&. +.TP 0.2i +\(bu +If you did not specify a command when you started \f3servertool\fR, then the command-line tool displays the \f3servertool\fR prompt where you can enter commands: \f3servertool >\fR\&. +.TP 0.2i +\(bu +If you specify a command when you start \f3servertool\fR, then the Java IDL Server Tool starts, executes the command, and exits\&. +.TP +.ll 180 +register -server \fIserver-class-name\fR -classpath \fIclasspath-to-server\fR [ -applicationName \fIapplication-name\fR -args \fIargs-to-server\fR -vmargs \fIflags-for-JVM\fR ] +Registers a new persistent server with the Object Request Broker Daemon (ORBD)\&. If the server is not already registered, then it is registered and activated\&. This command causes an installation method to be called in the \f3main\fR class of the server identified by the \f3-server\fR option\&. The installation method must be \f3public static void install(org\&.omg\&.CORBA\&.ORB)\fR\&. The install method is optional and lets developers provide their own server installation behavior, such as creating a database schema\&. +.TP +.ll 180 +unregister -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR +Unregisters a server from the ORBD with either its server ID or its application name\&. This command causes an uninstallation method to be called in the \f3main\fR class of the server identified by the \f3-server\fR option\&. The \f3uninstall\fR method must be \f3public static void uninstall(org\&.omg\&.CORBA\&.ORB)\fR\&. The \f3uninstall\fR method is optional and lets developers provide their own server uninstallation behavior, such as undoing the behavior of the \f3install\fR method\&. +.TP +getserverid -applicationName \fIapplication-name\fR +Returns the server ID that corresponds to the \f3application-name\fR value\&. +.TP +list +Lists information about all persistent servers registered with the ORBD\&. +.TP +listappnames +Lists the application names for all servers currently registered with the ORBD\&. +.TP +listactive +Lists information about all persistent servers that were started by the ORBD and are currently running\&. +.TP +.ll 180 +locate -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR [ -endpointType \fIendpointType\fR ] +Locates the endpoints (ports) of a specific type for all ORBs created by a registered server\&. If a server is not already running, then it is activated\&. If an \f3endpointType\fR value is not specified, then the plain/non-protected endpoint associated with each ORB in a server is returned\&. +.TP +.ll 180 +locateperorb -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR [ -orbid \fIORB-name\fR ] +Locates all the endpoints (ports) registered by a specific Object Request Broker (ORB) of registered server\&. If a server is not already running, then it is activated\&. If an \f3orbid\fR is not specified, then the default value of \f3""\fR is assigned to the \f3orbid\fR\&. If any ORBs are created with an \f3orbid\fR of empty string, then all ports registered by it are returned\&. +.TP +orblist -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR +Lists the \f3ORBId\fR of the ORBs defined on a server\&. An \f3ORBId\fR is the string name for the ORB created by the server\&. If the server is not already running, then it is activated\&. +.TP +shutdown -serverid \fIserver-id\fR | -applicationName application-name +Shut down an active server that is registered with ORBD\&. During execution of this command, the \f3shutdown\fR method defined in the class specified by either the \f3-serverid\fR or \f3-applicationName\fR parameter is also called to shut down the server process\&. +.TP +startup -serverid \fIserver-id\fR | -applicationName application-name +Starts up or activate a server that is registered with ORBD\&. If the server is not running, then this command starts the server\&. If the server is already running, then an error message is displayed\&. +.TP +help +Lists all the commands available to the server through the \f3servertool\fR command\&. +.TP +quit +Exits the \f3servertool\fR command\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +orbd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/tnameserv.1 b/jdk-1.8.0.281/man/man1/tnameserv.1 new file mode 100755 index 0000000..c53ce9e --- /dev/null +++ b/jdk-1.8.0.281/man/man1/tnameserv.1 @@ -0,0 +1,468 @@ +'\" t +.\" Copyright (c) 1999, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java IDL and RMI-IIOP Tools +.\" Title: tnameserv.1 +.\" +.if n .pl 99999 +.TH tnameserv 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +tnameserv \- Interface Definition Language (IDL)\&. +.SH SYNOPSIS +.sp +.nf + +\fBtnameserve\fR \fB\-ORBInitialPort\fR [ \fInameserverport\fR ] +.fi +.sp +.TP +-ORBInitialPort \fInameserverport\fR +.br +The initial port where the naming service listens for the bootstrap protocol used to implement the ORB \f3resolve_initial_references\fR and \f3list_initial_references\fR methods\&. +.SH DESCRIPTION +Java IDL includes the Object Request Broker Daemon (ORBD)\&. ORBD is a daemon process that contains a Bootstrap Service, a Transient Naming Service, a Persistent Naming Service, and a Server Manager\&. The Java IDL tutorials all use ORBD, but you can substitute the \f3tnameserv\fR command for the \f3orbd\fR command in any of the examples that use a Transient Naming Service\&. +.PP +See orbd(1) or Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html +.PP +The CORBA Common Object Services (COS) Naming Service provides a tree-structure directory for object references similar to a file system that provides a directory structure for files\&. The Transient Naming Service provided with Java IDL, \f3tnameserv\fR, is a simple implementation of the COS Naming Service specification\&. +.PP +Object references are stored in the name space by name and each object reference-name pair is called a name binding\&. Name bindings can be organized under naming contexts\&. Naming contexts are name bindings and serve the same organizational function as a file system subdirectory\&. All bindings are stored under the initial naming context\&. The initial naming context is the only persistent binding in the name space\&. The rest of the name space is lost when the Java IDL naming service process stops and restarts\&. +.PP +For an applet or application to use COS naming, its ORB must know the port of a host running a naming service or have access to an initial naming context string for that naming service\&. The naming service can either be the Java IDL naming service or another COS-compliant naming service\&. +.SS START\ THE\ NAMING\ SERVICE +You must start the Java IDL naming service before an application or applet that uses its naming service\&. Installation of the Java IDL product creates a script (Oracle Solaris: \f3tnameserv\fR) or executable file (Windows: \f3tnameserv\&.exe\fR) that starts the Java IDL naming service\&. Start the naming service so it runs in the background\&. +.PP +If you do not specify otherwise, then the Java IDL naming service listens on port 900 for the bootstrap protocol used to implement the ORB \f3resolve_initial_references\fR and \f3list_initial_references methods\fR, as follows: +.sp +.nf +\f3tnameserv \-ORBInitialPort nameserverport&\fP +.fi +.nf +\f3\fP +.fi +.sp +If you do not specify the name server port, then port 900 is used by default\&. When running Oracle Solaris software, you must become the root user to start a process on a port below 1024\&. For this reason, it is recommended that you use a port number greater than or equal to 1024\&. To specify a different port, for example, 1050, and to run the naming service in the background, from a UNIX command shell, enter: +.sp +.nf +\f3tnameserv \-ORBInitialPort 1050&\fP +.fi +.nf +\f3\fP +.fi +.sp +From an MS-DOS system prompt (Windows), enter: +.sp +.nf +\f3start tnameserv \-ORBInitialPort 1050\fP +.fi +.nf +\f3\fP +.fi +.sp +Clients of the name server must be made aware of the new port number\&. Do this by setting the \f3org\&.omg\&.CORBA\&.ORBInitialPort\fR property to the new port number when you create the ORB object\&. +.SS RUN\ THE\ SERVER\ AND\ CLIENT\ ON\ DIFFERENT\ HOSTS +In most of the Java IDL and RMI-IIOP tutorials, the naming service, server, and client are all running on the development machine\&. In real-world deployment, the client and server probably run on different host machines from the Naming Service\&. +.PP +For the client and server to find the Naming Service, they must be made aware of the port number and host on which the naming service is running\&. Do this by setting the \f3org\&.omg\&.CORBA\&.ORBInitialPort\fR and \f3org\&.omg\&.CORBA\&.ORBInitialHost\fR properties in the client and server files to the machine name and port number on which the Naming Service is running\&. An example of this is shown in Getting Started Using RMI-IIOP at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi-iiop/rmiiiopexample\&.html +.PP +You could also use the command-line options \f3-ORBInitialPort nameserverport#\fR and \f3-ORBInitialHost nameserverhostname\fR to tell the client and server where to find the naming service\&. For one example of doing this using the command-line option, see Java IDL: The Hello World Example on Two Machines at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/tutorial/jidl2machines\&.html +.PP +For example, suppose the Transient Naming Service, \f3tnameserv\fR is running on port 1050 on host \f3nameserverhost\fR\&. The client is running on host \f3clienthost,\fR and the server is running on host \f3serverhost\fR\&. +.PP +Start \f3tnameserv\fR on the host \f3nameserverhost\fR: +.sp +.nf +\f3tnameserv \-ORBInitialPort 1050\fP +.fi +.nf +\f3\fP +.fi +.sp +Start the server on the \f3serverhost\fR: +.sp +.nf +\f3java Server \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fP +.fi +.nf +\f3\fP +.fi +.sp +Start the client on the \f3clienthost\fR: +.sp +.nf +\f3java Client \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS STOP\ THE\ NAMING\ SERVICE +To stop the Java IDL naming service, use the relevant operating system command, such as \f3kill\fR for a Unix process or \f3Ctrl+C\fR for a Windows process\&. The naming service continues to wait for invocations until it is explicitly shut down\&. Note that names registered with the Java IDL naming service disappear when the service is terminated\&. +.SH OPTIONS +.TP +-J\fIoption\fR +.br +Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH EXAMPLES +.SS ADD\ OBJECTS\ TO\ THE\ NAME\ SPACE +The following example shows how to add names to the name space\&. It is a self-contained Transient Naming Service client that creates the following simple tree\&. +.sp +.nf +\f3Initial Naming Context\fP +.fi +.nf +\f3 plans\fP +.fi +.nf +\f3 Personal\fP +.fi +.nf +\f3 calendar\fP +.fi +.nf +\f3 schedule\fP +.fi +.nf +\f3\fP +.fi +.sp +In this example, \f3plans\fR is an object reference and \f3Personal\fR is a naming context that contains two object references: \f3calendar\fR and \f3schedule\fR\&. +.sp +.nf +\f3import java\&.util\&.Properties;\fP +.fi +.nf +\f3import org\&.omg\&.CORBA\&.*;\fP +.fi +.nf +\f3import org\&.omg\&.CosNaming\&.*;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3public class NameClient {\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 public static void main(String args[]) {\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 try {\fP +.fi +.nf +\f3\fP +.fi +.sp +In Start the Naming Service, the \f3nameserver\fR was started on port 1050\&. The following code ensures that the client program is aware of this port number\&. +.sp +.nf +\f3 Properties props = new Properties();\fP +.fi +.nf +\f3 props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP +.fi +.nf +\f3 ORB orb = ORB\&.init(args, props);\fP +.fi +.nf +\f3\fP +.fi +.sp +This code obtains the initial naming context and assigns it to \f3ctx\fR\&. The second line copies \f3ctx\fR into a dummy object reference \f3objref\fR that is attached to various names and added into the name space\&. +.sp +.nf +\f3 NamingContext ctx =\fP +.fi +.nf +\f3 NamingContextHelper\&.narrow(\fP +.fi +.nf +\f3 orb\&.resolve_initial_references("NameService"));\fP +.fi +.nf +\f3 NamingContext objref = ctx;\fP +.fi +.nf +\f3\fP +.fi +.sp +This code creates a name \f3plans\fR of type \f3text\fR and binds it to the dummy object reference\&. \f3plans\fR is then added under the initial naming context using the \f3rebind\fR method\&. The \f3rebind\fR method enables you to run this program over and over again without getting the exceptions from using the \f3bind\fR method\&. +.sp +.nf +\f3 NameComponent nc1 = new NameComponent("plans", "text");\fP +.fi +.nf +\f3 NameComponent[] name1 = {nc1};\fP +.fi +.nf +\f3 ctx\&.rebind(name1, objref);\fP +.fi +.nf +\f3 System\&.out\&.println("plans rebind successful!");\fP +.fi +.nf +\f3\fP +.fi +.sp +This code creates a naming context called \f3Personal\fR of type \f3directory\fR\&. The resulting object reference, \f3ctx2\fR, is bound to the \f3name\fR and added under the initial naming context\&. +.sp +.nf +\f3 NameComponent nc2 = new NameComponent("Personal", "directory");\fP +.fi +.nf +\f3 NameComponent[] name2 = {nc2};\fP +.fi +.nf +\f3 NamingContext ctx2 = ctx\&.bind_new_context(name2);\fP +.fi +.nf +\f3 System\&.out\&.println("new naming context added\&.\&.");\fP +.fi +.nf +\f3\fP +.fi +.sp +The remainder of the code binds the dummy object reference using the names \f3schedule\fR and \f3calendar\fR under the \f3Personal\fR naming context (\f3ctx2\fR)\&. +.sp +.nf +\f3 NameComponent nc3 = new NameComponent("schedule", "text");\fP +.fi +.nf +\f3 NameComponent[] name3 = {nc3};\fP +.fi +.nf +\f3 ctx2\&.rebind(name3, objref);\fP +.fi +.nf +\f3 System\&.out\&.println("schedule rebind successful!");\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 NameComponent nc4 = new NameComponent("calender", "text");\fP +.fi +.nf +\f3 NameComponent[] name4 = {nc4};\fP +.fi +.nf +\f3 ctx2\&.rebind(name4, objref);\fP +.fi +.nf +\f3 System\&.out\&.println("calender rebind successful!");\fP +.fi +.nf +\f3 } catch (Exception e) {\fP +.fi +.nf +\f3 e\&.printStackTrace(System\&.err);\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp +.SS BROWSING\ THE\ NAME\ SPACE +The following sample program shoes how to browse the name space\&. +.sp +.nf +\f3import java\&.util\&.Properties;\fP +.fi +.nf +\f3import org\&.omg\&.CORBA\&.*;\fP +.fi +.nf +\f3import org\&.omg\&.CosNaming\&.*;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3public class NameClientList {\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 public static void main(String args[]) {\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 try {\fP +.fi +.nf +\f3\fP +.fi +.sp +In Start the Naming Service, the \f3nameserver\fR was started on port 1050\&. The following code ensures that the client program is aware of this port number\&. +.sp +.nf +\f3 Properties props = new Properties();\fP +.fi +.nf +\f3 props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP +.fi +.nf +\f3 ORB orb = ORB\&.init(args, props);\fP +.fi +.nf +\f3\fP +.fi +.sp +The following code obtains the initial naming context\&. +.sp +.nf +\f3 NamingContext nc =\fP +.fi +.nf +\f3 NamingContextHelper\&.narrow(\fP +.fi +.nf +\f3 orb\&.resolve_initial_references("NameService"));\fP +.fi +.nf +\f3\fP +.fi +.sp +The \f3list\fR method lists the bindings in the naming context\&. In this case, up to 1000 bindings from the initial naming context will be returned in the \f3BindingListHolder\fR; any remaining bindings are returned in the \f3BindingIteratorHolder\fR\&. +.sp +.nf +\f3 BindingListHolder bl = new BindingListHolder();\fP +.fi +.nf +\f3 BindingIteratorHolder blIt= new BindingIteratorHolder();\fP +.fi +.nf +\f3 nc\&.list(1000, bl, blIt);\fP +.fi +.nf +\f3\fP +.fi +.sp +This code gets the array of bindings out of the returned \f3BindingListHolder\fR\&. If there are no bindings, then the program ends\&. +.sp +.nf +\f3 Binding bindings[] = bl\&.value;\fP +.fi +.nf +\f3 if (bindings\&.length == 0) return;\fP +.fi +.nf +\f3\fP +.fi +.sp +The remainder of the code loops through the bindings and prints outs the names\&. +.sp +.nf +\f3 for (int i=0; i < bindings\&.length; i++) {\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 // get the object reference for each binding\fP +.fi +.nf +\f3 org\&.omg\&.CORBA\&.Object obj = nc\&.resolve(bindings[i]\&.binding_name);\fP +.fi +.nf +\f3 String objStr = orb\&.object_to_string(obj);\fP +.fi +.nf +\f3 int lastIx = bindings[i]\&.binding_name\&.length\-1;\fP +.fi +.nf +\f3\fP +.fi +.nf +\f3 // check to see if this is a naming context\fP +.fi +.nf +\f3 if (bindings[i]\&.binding_type == BindingType\&.ncontext) {\fP +.fi +.nf +\f3 System\&.out\&.println("Context: " +\fP +.fi +.nf +\f3 bindings[i]\&.binding_name[lastIx]\&.id);\fP +.fi +.nf +\f3 } else {\fP +.fi +.nf +\f3 System\&.out\&.println("Object: " +\fP +.fi +.nf +\f3 bindings[i]\&.binding_name[lastIx]\&.id);\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 } catch (Exception e) {\fP +.fi +.nf +\f3 e\&.printStackTrace(System\&.err)\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3 }\fP +.fi +.nf +\f3}\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +orbd(1) +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/unpack200.1 b/jdk-1.8.0.281/man/man1/unpack200.1 new file mode 100755 index 0000000..e45cb1a --- /dev/null +++ b/jdk-1.8.0.281/man/man1/unpack200.1 @@ -0,0 +1,117 @@ +'\" t +.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Deployment Tools +.\" Title: unpack200.1 +.\" +.if n .pl 99999 +.TH unpack200 1 "21 November 2013" "JDK 8" "Java Deployment Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +unpack200 \- Transforms a packed file produced by pack200(1) into a JAR file for web deployment\&. +.SH SYNOPSIS +.sp +.nf + +\fBunpack200\fR [ \fIoptions\fR ] input\-file \fIJAR\-file\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIinput-file\fR +Name of the input file, which can be a pack200 gzip file or a pack200 file\&. The input can also be JAR file produced by \f3pack200\fR(1) with an effort of \f30\fR, in which case the contents of the input file are copied to the output JAR file with the Pack200 marker\&. +.TP +\fIJAR-file\fR +Name of the output JAR file\&. +.SH DESCRIPTION +The \f3unpack200\fR command is a native implementation that transforms a packed file produced by \f3pack200\fR\f3(1)\fR into a JAR file\&. A typical usage follows\&. In the following example, the \f3myarchive\&.jar\fR file is produced from \f3myarchive\&.pack\&.gz\fR with the default \f3unpack200\fR command settings\&. +.sp +.nf +\f3unpack200 myarchive\&.pack\&.gz myarchive\&.jar\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +.TP +-Hvalue --deflate-hint=\fIvalue\fR +.br +Sets the deflation to be \f3true\fR, \f3false\fR, or \f3keep\fR on all entries within a JAR file\&. The default mode is \f3keep\fR\&. If the value is \f3true\fR or \f3false\fR, then the \f3--deflate=hint\fR option overrides the default behavior and sets the deflation mode on all entries within the output JAR file\&. +.TP +-r --remove-pack-file +.br +Removes the input pack file\&. +.TP +-v --verbose +.br +Displays minimal messages\&. Multiple specifications of this option displays more verbose messages\&. +.TP +-q --quiet +.br +Specifies quiet operation with no messages\&. +.TP +-lfilename --log-file=\fIfilename\fR +.br +Specifies a log file where output messages are logged\&. +.TP +-? -h --help +.br +Prints help information about the \f3unpack200\fR command\&. +.TP +-V --version +.br +Prints version information about the \f3unpack200\fR command\&. +.TP +-J\fIoption\fR +.br +Passes option to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&. +.SH NOTES +This command should not be confused with the \f3unpack\fR command\&. They are distinctly separate products\&. +.PP +The Java SE API Specification provided with the JDK is the superseding authority in case of discrepancies\&. +.SH EXIT\ STATUS +The following exit values are returned: 0 for successful completion, and a value that is greater than 0 when an error occurred\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +pack200(1) +.TP 0.2i +\(bu +jar(1) +.TP 0.2i +\(bu +jarsigner(1) +.TP 0.2i +\(bu +Pack200 and Compression at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/deployment/deployment-guide/pack200\&.html +.TP 0.2i +\(bu +The Java SE Technical Documentation page at http://docs\&.oracle\&.com/javase/ +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/wsgen.1 b/jdk-1.8.0.281/man/man1/wsgen.1 new file mode 100755 index 0000000..cc98e98 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/wsgen.1 @@ -0,0 +1,155 @@ +'\" t +.\" Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Web Services Tools +.\" Title: wsgen.1 +.\" +.if n .pl 99999 +.TH wsgen 1 "21 November 2013" "JDK 8" "Java Web Services Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +wsgen \- Reads a web service endpoint implementation (SEI) class and generates all of the required artifacts for web service deployment, and invocation\&. +.SH SYNOPSIS +.sp +.nf + +\fBwsgen\fR [ \fIoptions\fR ] \fISEI\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fISEI\fR +The web service endpoint implementation class (SEI) to be read\&. +.SH DESCRIPTION +The \f3wsgen\fR command generates JAX-WS portable artifacts used in JAX-WS web services\&. The tool reads a web service endpoint class and generates all the required artifacts for web service deployment and invocation\&. JAXWS 2\&.1\&.1 RI also provides a \f3wsgen\fR Ant task, see the \fITools\fR tab of the JAX-WS (wsgen) page at http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsgenant\&.html +.PP +To start the \f3wsgen\fR command, do the following: +.sp +.nf +\f3export JAXWS_HOME=/pathto/jaxws\-ri\fP +.fi +.nf +\f3$JAXWS_HOME/bin/wsgen\&.sh \-help\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +.TP +-classpath \fIpath\fR +.br +The location of the input class files\&. +.TP +-cp \fIpath\fR +.br +The location of the input class files\&. +.TP +-d \fIdirectory\fR +.br +The location for where to place generated output files\&. +.TP +-extension +.br +Allow vendor extensions\&. Use of extensions can result in applications that are not portable or that do not work with other implementations\&. +.TP +-help +.br +Displays a help message about the \f3wsgen\fR command\&. +.TP +-keep +.br +Keeps the generated files\&. +.TP +-r \fIdirectory\fR +.br +Uses this option with the \f3-wsdl\fR option to specify where to place generated resource files such as WSDLs\&. +.TP +-s \fIdirectory\fR +.br +The location for where to place generated source files\&. +.TP +-verbose +.br +Displays compiler messages\&. +.TP +-version +.br +Prints release information\&. +.TP +-wsdl [ :protocol ] \fI\fR +.br +An optional command that generates a WSDL file to review before endpoint deployment\&. The WSDL files contains a machine-readable description of how the service can be called, what parameters it expects, and what data structures it returns\&. + +By default the \f3wsgen\fR command does not generate a WSDL file\&. The \f3protocol\fR value is optional and is used to specify what protocol should be used for the WSDL binding (\f3wsdl:binding\fR)\&. Valid protocols are \f3soap1\&.1\fR and \f3Xsoap1\&.2\fR\&. The default is \f3soap1\&.1\fR\&. The \f3Xsoap1\&.2\fR protocol is not standard and can only be used with the \f3-extension\fR option\&. +.TP +-servicename \fIname\fR +.br +Used only with the \f3-wsdl\fR option to specify a particular WSDL service (\f3wsdl:service\fR) name to be generated in the WSDL, for example: \f3-servicename "{http://mynamespace/}MyService"\fR\&. +.TP +-portname \fIname\fR +.br +Used only with the \f3-wsdl\fR option to specify a particular WSDL port (\f3wsdl:port\fR) name to be generated in the WSDL, for example: \f3-portname "{http://mynamespace/}MyPort"\fR\&. +.SH EXAMPLES +The following example generates the wrapper classes for \f3StockService\fR with \f3@WebService\fR annotations inside stock directory\&. +.sp +.nf +\f3wsgen \-d stock \-cp myclasspath stock\&.StockService\fP +.fi +.nf +\f3\fP +.fi +.sp +The following example generates a SOAP 1\&.1 WSDL and schema for the \f3stock\&.StockService\fR class with \f3@WebService\fR annotations\&. +.sp +.nf +\f3wsgen \-wsdl \-d stock \-cp myclasspath stock\&.StockService\fP +.fi +.nf +\f3\fP +.fi +.sp +The following example generates a SOAP 1\&.2 WSDL\&. +.sp +.nf +\f3wsgen \-wsdl:Xsoap1\&.2 \-d stock \-cp myclasspath stock\&.StockService \fP +.fi +.nf +\f3\fP +.fi +.sp +\fINote:\fR You do not have to generate WSDL at development time because the JAXWS run time environment generates a WSDL for you when you deploy your service\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +wsimport(1) +.TP 0.2i +\(bu +\fIThe Tools\fR tab of the JAX-WS (wsgen) page http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsgenant\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/wsimport.1 b/jdk-1.8.0.281/man/man1/wsimport.1 new file mode 100755 index 0000000..ecdd293 --- /dev/null +++ b/jdk-1.8.0.281/man/man1/wsimport.1 @@ -0,0 +1,196 @@ +'\" t +.\" Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Web Services Tools +.\" Title: wsimport.1 +.\" +.if n .pl 99999 +.TH wsimport 1 "21 November 2013" "JDK 8" "Java Web Services Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +wsimport \- Generates JAX-WS portable artifacts that can be packaged in a web application archive (WAR) file and provides an Ant task\&. +.SH SYNOPSIS +.sp +.nf + +\fBwsimport\fR [ \fIoptions\fR ] \fIwsdl\fR +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +\fIwsdl\fR +The file that contains the machine-readable description of how the web service can be called, what parameters it expects, and what data structures it returns\&. +.SH DESCRIPTION +The \f3wsimport\fR command generates the following JAX-WS portable artifacts\&. These artifacts can be packaged in a WAR file with the WSDL and schema documents and the endpoint implementation to be deployed\&. The \f3wsimport\fR command also provides a \f3wsimport\fR Ant task, see the Tools tab of the Wsimport Ant Task page at http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.html +.TP 0.2i +\(bu +Service Endpoint Interface (SEI) +.TP 0.2i +\(bu +Service +.TP 0.2i +\(bu +Exception class is mapped from \f3wsdl:fault\fR (if any) +.TP 0.2i +\(bu +Async Response Bean is derived from response \f3wsdl:message\fR (if any) +.TP 0.2i +\(bu +JAXB generated value types (mapped java classes from schema types) +.PP +To start the \f3wsgen\fR command, do the following: +.PP +\fIOracle Solaris/Linux\fR: +.sp +.nf +\f3/bin/wsimport\&.sh \-help\fP +.fi +.nf +\f3\fP +.fi +.sp +\fIWindows\fR: +.sp +.nf +\f3\ebin\ewsimport\&.bat \-help\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH OPTIONS +.TP +-d \fIdirectory\fR +.br +Specifies where to place generated output files\&. +.TP +-b \fIpath\fR +.br +Specifies external JAX-WS or JAXB binding files\&. Multiple JAX-WS and JAXB binding files can be specified with the \f3-b\fR option\&. You can use these files to customize package names, bean names, and so on\&. For more information about JAX-WS and JAXB binding files, see the \fIUsers Guide\fR tab of WSDL Customization at http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.html +.TP +-B \fIjaxbOption\fR +.br +Passes the \f3jaxbOption\fR option to the JAXB schema compiler\&. +.TP +-catalog +.br +Specifies a catalog file to resolve external entity references\&. The \f3-catalog\fR option supports the TR9401, XCatalog, and OASIS XML Catalog formats\&. See the \fIUsers Guide\fR tab of the Catalog Support page at http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/catalog-support\&.html +.TP +-extension +.br +Allows vendor extensions\&. Use of extensions can result in applications that are not portable or that do not work with other implementations\&. +.TP +-help +.br +Displays a help message for the \f3wsimport\fR command\&. +.TP +-httpproxy: \fIhost\fR:\fIport\fR +.br +Specifies an HTTP proxy server\&. The default is 8080\&. +.TP +-keep +.br +Keeps generated files\&. +.TP +-p \fIname\fR +.br +Specifies a target package \fIname\fR to override the WSDL and schema binding customizations, and the default algorithm defined in the specification\&. +.TP +-s \fIdirectory\fR +.br +Specifies where to place generated source files\&. +.TP +-verbose +.br +Displays compiler messages\&. +.TP +-version +.br +Prints release information\&. +.TP +-wsdllocation \fIlocation\fR +.br +Specifies the \f3@WebServiceClient\&.wsdlLocation\fR value\&. +.TP +-target +.br +Generates code according to the specified JAX-WS specification version\&. Version 2\&.0 generates compliant code for the JAX-WS 2\&.0 specification\&. +.TP +-quiet +.br +Suppresses the \f3wsimport\fR command output\&. +.PP +Multiple \f3JAX-WS\fR and \f3JAXB\fR binding files can be specified using the \f3-b\fR option, and they can be used to customize various things such as package names and bean names\&. More information about \f3JAX-WS\fR and \f3JAXB\fR binding files can be found in the customization documentation at https://jax-ws\&.dev\&.java\&.net/nonav/2\&.1\&.1/docs/customizations\&.html +.SH NONSTANDARD\ OPTIONS +.TP +-XadditionalHeaders +.br +Maps headers not bound to a request or response message to Java method parameters\&. +.TP +-Xauthfile \fIfile\fR +.br +The WSDL URI that specifies the file that contains authorization information\&. This URI is in the following format: + +http://\fIuser-name\fR:\f3password\fR@\fIhost-name\fR/\fIweb-service-name\fR>?wsdl\&. +.TP +-Xdebug +.br +Prints debugging information\&. +.TP +-Xno-addressing-databinding +.br +Enables binding of W3C EndpointReferenceType to Java\&. +.TP +-Xnocompile +.br +Does not compile the generated Java files\&. +.SH EXAMPLE +The following example generates the Java artifacts and compiles the artifacts by importing \f3http://stockquote\&.example\&.com/quote?wsdl\fR +.sp +.nf +\f3wsimport \-p stockquote http://stockquote\&.example\&.com/quote?wsdl\fP +.fi +.nf +\f3\fP +.fi +.sp +.SH SEE\ ALSO +.TP 0.2i +\(bu +wsgen(1) +.TP 0.2i +\(bu +The Tools tab of Wsimport Ant Task page http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.html +.TP 0.2i +\(bu +The \fIUsers Guide\fR tab of Catalog Support page http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/catalog-support\&.html +.TP 0.2i +\(bu +The \fIUsers Guide\fR tab of WSDL Customization page http://jax-ws\&.java\&.net/nonav/2\&.1\&.1/docs/wsimportant\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/man/man1/xjc.1 b/jdk-1.8.0.281/man/man1/xjc.1 new file mode 100755 index 0000000..3ae5d6e --- /dev/null +++ b/jdk-1.8.0.281/man/man1/xjc.1 @@ -0,0 +1,212 @@ +'\" t +.\" Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. +.\" Arch: generic +.\" Software: JDK 8 +.\" Date: 21 November 2013 +.\" SectDesc: Java Web Services Tools +.\" Title: xjc.1 +.\" +.if n .pl 99999 +.TH xjc 1 "21 November 2013" "JDK 8" "Java Web Services Tools" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- + +.SH NAME +xjc \- Compiles an XML schema file into fully annotated Java classes\&. +.SH SYNOPSIS +.sp +.nf + +\fBxjc\fR [ \fIoptions\fR ] \fBschema\fR \fIfile/URL/dir/jar\fR \&.\&.\&. [\fB\-b\fR \fIbindinfo\fR ] \&.\&.\&. +.fi +.sp +.TP +\fIoptions\fR +The command-line options\&. See Options\&. +.TP +schema \fIfile/URL/dir/jar \&.\&.\&.\fR +The location of the XML schema file\&. If \f3dir\fR is specified, then all schema files in it are compiled\&. If \f3jar\fR is specified, then the \f3/META-INF/sun-jaxb\&.episode\fR binding file is compiled\&. +.TP +-b \fIbindinfo\fR +.br +The location of the bindings files\&. +.SH DESCRIPTION +Start the binding compiler with the appropriate \f3xjc\fR shell script in the bin directory for your platform\&. There is also an Ant task to run the binding complier\&. See Using the XJC with Ant at http://jaxb\&.java\&.net/nonav/2\&.1\&.3/docs/xjcTask\&.html +.SH OPTIONS +.TP 0.2i +\(bu +See also Nonstandard Options +.TP 0.2i +\(bu +See also Deprecated and Removed Options +.TP +-nv +.br +By default, the XJC binding compiler performs strict validation of the source schema before processing it\&. Use this option to disable strict schema validation\&. This does not mean that the binding compiler will not perform any validation, but means that it will perform a less-strict validation\&. +.TP +-extension +.br +By default, the XJC binding compiler strictly enforces the rules outlined in the Compatibility chapter of the JAXB Specification\&. Appendix E\&.2 defines a set of W3C XML Schema features that are not completely supported by JAXB v1\&.0\&. In some cases, you may be allowed to use them in the \f3-extension\fR mode enabled by this switch\&. In the default (strict) mode, you are also limited to using only the binding customization defined in the specification\&. By using the \f3-extension\fR switch, you will be allowed to use the JAXB Vendor Extensions\&. +.TP +-b \fIfile\fR +.br +Specifies one or more external binding files to process\&. Each binding file must have its own \f3-b\fR switch\&. The syntax of the external binding files is flexible\&. You can have a single binding file that contains customization for multiple schemas or you can break the customization into multiple bindings files: \f3xjc schema1\&.xsd schema2\&.xsd schema3\&.xsd -b bindings123\&.xjb\fR\f3xjc schema1\&.xsd schema2\&.xsd schema3\&.xsd -b bindings1\&.xjb -b bindings2\&.xjb -b bindings3\&.xjb\fR\&. In addition, the ordering of the schema files and binding files on the command line does not matter\&. +.TP +-d \fIdir\fR +.br +By default, the XJC binding compiler generates the Java content classes in the current directory\&. Use this option to specify an alternate output directory\&. The output directory must already exist\&. The XJC binding compiler does not create it for you\&. +.TP +-p \fIpkg\fR +.br +When you specify a target package with this command-line option, it overrides any binding customization for the package name and the default package name algorithm defined in the specification\&. +.TP +-httpproxy \fIproxy\fR +.br +Specifies the HTTP or HTTPS proxy in the format \fI[user[:password]@]proxyHost[:proxyPort]\fR\&. The old \f3-host\fR and \f3-port\fR options are still supported by the RI for backward compatibility, but they were deprecated\&. The password specified with this option is an argument that is visible to other users who use the top command\&. For greater security, use the \f3-httpproxyfile\fR option\&. +.TP +-httpproxyfile file +.br +Specifies the HTTP or HTTPS proxy with a file\&. The same format as the \f3-httpproxy\fR option, but the password specified in the file is not visible to other users\&. +.TP +-classpath arg +.br +Specifies where to find client application class files used by the \fIjxb:javaType\fR and xjc:\fIsuperClass\fR customization\&. +.TP +-catalog file +.br +Specifies catalog files to resolve external entity references\&. Supports the TR9401, XCatalog, and OASIS XML Catalog formats\&. See XML Entity and URI Resolvers at http://xerces\&.apache\&.org/xml-commons/components/resolver/resolver-article\&.html +.TP +-readOnly +.br +By default, the XJC binding compiler does not write-protect the Java source files it generates\&. Use this option to force the XJC binding compiler to mark the generated Java sources as read-only\&. +.TP +-npa +.br +Suppresses the generation of package level annotations into \f3**/package-info\&.java\fR\&. Using this switch causes the generated code to internalize those annotations into the other generated classes\&. +.TP +-no-header +.br +Suppresses the generation of a file header comment that includes some note and time stamp\&. Using this makes the generated code more compatible with the \f3diff\fR command\&. +.TP +-target 2\&.0 +.br +Avoids generating code that relies on any JAXB 2\&.1 features\&. This will allow the generated code to run with JAXB 2\&.0 runtime environment (such as Java SE 6)\&. +.TP +-xmlschema +.br +Treats input schemas as W3C XML Schema (default)\&. If you do not specify this switch, then your input schemas are treated as though they are W3C XML Schemas\&. +.TP +-relaxing +.br +Treats input schemas as RELAX NG (experimental and unsupported)\&. Support for RELAX NG schemas is provided as a JAXB Vendor Extension\&. +.TP +-relaxing-compact +.br +Treat input schemas as RELAX NG compact syntax (experimental and unsupported)\&. Support for RELAX NG schemas is provided as a JAXB Vendor Extension\&. +.TP +-dtd +.br +Treats input schemas as XML DTD (experimental and unsupported)\&. Support for RELAX NG schemas is provided as a JAXB Vendor Extension\&. +.TP +-wsdl +.br +Treats input as WSDL and compiles schemas inside it (experimental and unsupported)\&. +.TP +-quiet +.br +Suppress compiler output, such as progress information and warnings\&. +.TP +-verbose +.br +Be extra verbose, such as printing informational messages or displaying stack traces upon some errors\&. +.TP +-help +.br +Displays a brief summary of the compiler switches\&. +.TP +-version +.br +Displays the compiler version information\&. +.TP +\fIschema file/URL/dir\fR +Specifies one or more schema files to compile\&. If you specify a directory, then the \f3xjc\fR command scans it for all schema files and compiles them\&. +.SS NONSTANDARD\ OPTIONS +.TP +-XLocator +.br +Causes the generated code to expose SAX Locator information about the source XML in the Java bean instances after unmarshalling\&. +.TP +-Xsync-methods +.br +Causes all of the generated method signatures to include the \f3synchronized\fR keyword\&. +.TP +-mark-generated +.br +Marks the generated code with the annotation \f3@javax\&.annotation\&.Generated\fR\&. +.TP +-episode file +.br +Generates the specified episode file for separate compilation\&. +.SS DEPRECATED\ AND\ REMOVED\ OPTIONS +.TP +-host & -port +.br +These options are replaced with the \f3-httpproxy\fR option\&. For backward compatibility, these options are supported, but will not be documented and might be removed from future releases\&. +.TP +-use-runtime +.br +Because the JAXB 2\&.0 specification has defined a portable runtime environment, it is no longer necessary for the JAXB RI to generate \f3**/impl/runtime\fRpackages\&. Therefore, this switch is obsolete and was removed\&. +.TP +-source +.br +The \f3-source\fR compatibility switch was introduced in the first JAXB 2\&.0 Early Access release\&. This switch is removed from future releases of JAXB 2\&.0\&. If you need to generate 1\&.0\&.x code, then use an installation of the 1\&.0\&.x code base\&. +.SH COMPILER\ RESTRICTIONS +In general, it is safest to compile all related schemas as a single unit with the same binding compiler switches\&. Keep the following list of restrictions in mind when running the \f3xjc\fR command\&. Most of these issues only apply when you compile multiple schemas with multiple invocations of the \f3xjc\fR command\&. +.PP +To compile multiple schemas at the same time, keep the following precedence rules for the target Java package name in mind: +.TP 0.4i +1\&. +The \f3-p\fR option has the highest precedence\&. +.TP 0.4i +2\&. +\fIjaxb:package\fR customization\&. +.TP 0.4i +3\&. +If \f3targetNamespace\fR is declared, then apply the \f3t\fR\f3argetNamespace\fR to the Java package name algorithm defined in the specification\&. +.TP 0.4i +4\&. +If no \f3targetNamespace\fR is declared, then use a hard coded package named \f3generated\fR\&. +.PP +You cannot have more than one \fIjaxb:schemaBindings\fR per name space, so it is impossible to have two schemas in the same target name space compiled into different Java packages\&. +.PP +All schemas being compiled into the same Java package must be submitted to the XJC binding compiler at the same time\&. They cannot be compiled independently and work as expected\&. +.PP +Element substitution groups that are spread across multiple schema files must be compiled at the same time\&. +.SH SEE\ ALSO +.TP 0.2i +\(bu +Binding Compiler (xjc) at http://jaxb\&.java\&.net/nonav/2\&.2\&.3u1/docs/xjc\&.html +.TP 0.2i +\(bu +Java Architecture for XML Binding (JAXB) at http://www\&.oracle\&.com/technetwork/articles/javase/index-140168\&.html +.RE +.br +'pl 8.5i +'bp diff --git a/jdk-1.8.0.281/release b/jdk-1.8.0.281/release new file mode 100755 index 0000000..40329a3 --- /dev/null +++ b/jdk-1.8.0.281/release @@ -0,0 +1,6 @@ +JAVA_VERSION="1.8.0_281" +OS_NAME="Linux" +OS_VERSION="2.6" +OS_ARCH="amd64" +SOURCE=" .:a7625bac5c36 corba:5bc269c62ea0 deploy:e06652fcd2a9 hotspot:aebc8f1b0e9f hotspot/make/closed:f45ffcf8727d hotspot/src/closed:765dc620b71c install:871eca5f8aa2 jaxp:f8d94f5b6cf7 jaxws:748857f45772 jdk:9bd8cd71da43 jdk/make/closed:c4cafc6aa07f jdk/src/closed:2e7a0628823d langtools:683e5cf02538 nashorn:b26197e30e55" +BUILD_TYPE="commercial" diff --git a/packaging/jdk.manifest b/packaging/jdk.manifest new file mode 100755 index 0000000..75b0fa5 --- /dev/null +++ b/packaging/jdk.manifest @@ -0,0 +1,5 @@ +<manifest> + <request> + <domain name="_"/> + </request> +</manifest> diff --git a/packaging/jdk.spec b/packaging/jdk.spec new file mode 100755 index 0000000..77e5a65 --- /dev/null +++ b/packaging/jdk.spec @@ -0,0 +1,59 @@ +Name: jdk +Summary: Oracle JDK for Tizen Application Build +Version: 1.8.0.281 +Release: 1 +Group: Development/Tools +License: Oracle Technology Network License +Source0: %{name}-%{version}.tar.gz +AutoReqProv: no +BuildRequires: elfutils +BuildRequires: patchelf + +%description +%{summary} + +%prep +%setup -q + +%build +%ifarch %{arm} aarch64 riscv64 +LD_INTERPRETER=$(patchelf --print-interpreter /emul/usr/bin/gcc) +LD_RPATH="$(patchelf --print-rpath /emul/usr/bin/gcc):/usr/jdk-%{version}/lib/amd64/jli" +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/java +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/java +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/javac +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/javac +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/javah +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/javah +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/jar +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/jar +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/jre/lib/amd64/server/libjvm.so +%endif + +%ifarch x86_64 +LD_INTERPRETER=$(patchelf --print-interpreter /usr/bin/gcc) +LD_RPATH="$(patchelf --print-rpath /usr/bin/gcc):/usr/jdk-%{version}/lib/amd64/jli" +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/java +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/java +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/javac +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/javac +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/javah +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/javah +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/bin/jar +patchelf --set-interpreter ${LD_INTERPRETER} ./jdk-%{version}/bin/jar +patchelf --set-rpath ${LD_RPATH} ./jdk-%{version}/jre/lib/amd64/server/libjvm.so +%endif + + +%install +install -d %{buildroot}/%{_bindir} +/bin/cp -rvf jdk-%{version} %{buildroot}/usr/ +/bin/ln -sf /usr/jdk-%{version}/bin/java %{buildroot}/%{_bindir} + +%clean +rm -rf %{buildroot} + +%files +%attr(755,root,root) +/usr/jdk-%{version} +%{_bindir}/java