changeset 11002:a46063b10ea6

Merge
author asaha
date Wed, 01 Jul 2015 22:03:05 -0700
parents c374fd55cf34 c4b37246b927
children f0cc2c118718
files .hgtags src/share/classes/sun/security/pkcs11/P11Key.java test/java/util/stream/boottest/java/util/stream/UnorderedTest.java test/javax/xml/ws/8046817/GenerateEnumSchema.java test/javax/xml/ws/8046817/TestClassType.java test/javax/xml/ws/8046817/TestEnumType.java test/sun/security/pkcs11/sslecc/ClientJSSEServerJSSE.java
diffstat 328 files changed, 37846 insertions(+), 37108 deletions(-) [+]
line wrap: on
line diff
--- a/.hgtags	Wed Jun 24 11:10:35 2015 -0700
+++ b/.hgtags	Wed Jul 01 22:03:05 2015 -0700
@@ -445,3 +445,4 @@
 b2c55ff77112321472ec97c3a6931a999837d183 jdk8u60-b19
 cc6c74b164dfd0636d9dba8f9865baa18a6f2338 jdk8u60-b20
 63c9cedeeb9d0de656969f3deed7ddafae11754a jdk8u60-b21
+e9f82302d5fdef8a0976640e09363895e9dcde3c jdk8u60-b22
--- a/THIRD_PARTY_README	Wed Jun 24 11:10:35 2015 -0700
+++ b/THIRD_PARTY_README	Wed Jul 01 22:03:05 2015 -0700
@@ -1140,37 +1140,6 @@
 
 --------------------------------------------------------------------------------
 
-%% This notice is provided with respect to JSON, which may be included 
-with JRE 8 & JDK 8.
-
---- begin of LICENSE ---
-
-Copyright (c) 2002 JSON.org
-
-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 shall be used for Good, not Evil.
-
-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.
-
---- end of LICENSE ---
-
--------------------------------------------------------------------------------
-
 %% This notice is provided with respect to Kerberos functionality, which 
 which may be included with JRE 8, JDK 8, and OpenJDK 8.
 
@@ -1250,7 +1219,7 @@
 
 -------------------------------------------------------------------------------
 
-%% This notice is provided with respect to libpng 1.6.16, which may be
+%% This notice is provided with respect to libpng 1.6.16, which may be 
 included with JRE 8, JDK 8, and OpenJDK 8.
 
 --- begin of LICENSE ---
@@ -1370,7 +1339,7 @@
 
 -------------------------------------------------------------------------------
 
-%% This notice is provided with respect to libungif 4.1.3, which may be 
+%% This notice is provided with respect to GIFLIB 5.1.1 & libungif 4.1.3, which may be 
 included with JRE 8, JDK 8, and OpenJDK 8.
 
 --- begin of LICENSE ---
@@ -1399,13 +1368,13 @@
 
 -------------------------------------------------------------------------------
 
-%% This notice is provided with respect to Little CMS 2.5, which may be 
+%% This notice is provided with respect to Little CMS 2.7, which may be 
 included with JRE 8, JDK 8, and OpenJDK 8.
 
 --- begin of LICENSE ---
 
 Little CMS
-Copyright (c) 1998-2011 Marti Maria Saguer
+Copyright (c) 1998-2015 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
--- a/make/CreateJars.gmk	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/CreateJars.gmk	Wed Jul 01 22:03:05 2015 -0700
@@ -283,15 +283,15 @@
 	    -e '/_the\.*' -e '^_the\.*' -e '\\_the\.*' -e 'javac_state' \
 	    $(IMAGES_OUTPUTDIR)/lib$(PROFILE)/_the.jars.contents > $@.tmp
         ifneq ($(PROFILE), )
+	  # Strip out all META-INF/services/ entries
+	  $(GREP) -v -e 'META-INF/services/' $@.tmp > $@.tmp2
           ifneq ($(strip $(PROFILE_INCLUDE_METAINF_SERVICES)), )
-            # Strip out all META-INF/services/ entries
-	    $(GREP) -v -e 'META-INF/services/' $@.tmp > $@.tmp2
 	    # Add back the required services
 	    for service in $(PROFILE_INCLUDE_METAINF_SERVICES) ; do \
 	      $(ECHO) $$service >> $@.tmp2; \
 	    done
-	    $(MV) $@.tmp2 $@.tmp
           endif
+	  $(MV) $@.tmp2 $@.tmp
         endif
 	$(MV) $@.tmp $@
 
--- a/make/data/tzdata/VERSION	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/data/tzdata/VERSION	Wed Jul 01 22:03:05 2015 -0700
@@ -21,4 +21,4 @@
 # or visit www.oracle.com if you need additional information or have any
 # questions.
 #
-tzdata2015d
+tzdata2015e
--- a/make/data/tzdata/africa	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/data/tzdata/africa	Wed Jul 01 22:03:05 2015 -0700
@@ -361,9 +361,10 @@
 # time this summer, and carry out studies on the possibility of canceling the
 # practice altogether in future years."
 #
-# From Paul Eggert (2015-04-20):
-# For now, assume DST will be canceled.  Any resumption would likely
-# use different rules anyway.
+# From Paul Eggert (2015-04-24):
+# Yesterday the office of Egyptian President El-Sisi announced his
+# decision to abandon DST permanently.  See Ahram Online 2015-04-24.
+# http://english.ahram.org.eg/NewsContent/1/64/128509/Egypt/Politics-/Sisi-cancels-daylight-saving-time-in-Egypt.aspx
 
 Rule	Egypt	2008	only	-	Aug	lastThu	24:00	0	-
 Rule	Egypt	2009	only	-	Aug	20	24:00	0	-
@@ -810,20 +811,41 @@
 # will resume again at 02:00 on Saturday, August 2, 2014....
 # http://www.mmsp.gov.ma/fr/actualites.aspx?id=586
 
-# From Paul Eggert (2014-06-05):
-# For now, guess that later spring and fall transitions will use 2014's rules,
+# From Milamber (2015-06-08):
+# (Google Translation) The hour will thus be delayed 60 minutes
+# Sunday, June 14 at 3:00, the ministry said in a statement, adding
+# that the time will be advanced again 60 minutes Sunday, July 19,
+# 2015 at 2:00.  The move comes under 2.12.126 Decree of 26 Jumada I
+# 1433 (18 April 2012) and the decision of the Head of Government of
+# 16 N. 3-29-15 Chaaban 1435 (4 June 2015).
+# Source (french):
+# http://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/
+#
+# From Milamber (2015-06-09):
+# http://www.mmsp.gov.ma/fr/actualites.aspx?id=863
+#
+# From Michael Deckers (2015-06-09):
+# [The gov.ma announcement] would (probably) make the switch on 2015-07-19 go
+# from 03:00 to 04:00 rather than from 02:00 to 03:00, as in the patch....
+# I think the patch is correct and the quoted text is wrong; the text in
+# <http://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/> agrees
+# with the patch.
+
+# From Paul Eggert (2015-06-08):
+# For now, guess that later spring and fall transitions will use 2015's rules,
 # and guess that Morocco will switch to standard time at 03:00 the last
-# Saturday before Ramadan, and back to DST at 02:00 the first Saturday after
-# Ramadan.  To implement this, transition dates for 2015 through 2037 were
+# Sunday before Ramadan, and back to DST at 02:00 the first Sunday after
+# Ramadan.  To implement this, transition dates for 2016 through 2037 were
 # determined by running the following program under GNU Emacs 24.3, with the
 # results integrated by hand into the table below.
-# (let ((islamic-year 1436))
+# (let ((islamic-year 1437))
+#   (require 'cal-islam)
 #   (while (< islamic-year 1460)
 #     (let ((a (calendar-islamic-to-absolute (list 9 1 islamic-year)))
 #           (b (calendar-islamic-to-absolute (list 10 1 islamic-year)))
-#           (saturday 6))
-#       (while (/= saturday (mod (setq a (1- a)) 7)))
-#       (while (/= saturday (mod b 7))
+#           (sunday 0))
+#       (while (/= sunday (mod (setq a (1- a)) 7)))
+#       (while (/= sunday (mod b 7))
 #         (setq b (1+ b)))
 #       (setq a (calendar-gregorian-from-absolute a))
 #       (setq b (calendar-gregorian-from-absolute b))
@@ -867,32 +889,30 @@
 Rule	Morocco	2013	only	-	Jul	 7	 3:00	0	-
 Rule	Morocco	2013	only	-	Aug	10	 2:00	1:00	S
 Rule	Morocco	2013	max	-	Oct	lastSun	 3:00	0	-
-Rule	Morocco	2014	2022	-	Mar	lastSun	 2:00	1:00	S
+Rule	Morocco	2014	2021	-	Mar	lastSun	 2:00	1:00	S
 Rule	Morocco	2014	only	-	Jun	28	 3:00	0	-
 Rule	Morocco	2014	only	-	Aug	 2	 2:00	1:00	S
-Rule	Morocco	2015	only	-	Jun	13	 3:00	0	-
-Rule	Morocco	2015	only	-	Jul	18	 2:00	1:00	S
-Rule	Morocco	2016	only	-	Jun	 4	 3:00	0	-
-Rule	Morocco	2016	only	-	Jul	 9	 2:00	1:00	S
-Rule	Morocco	2017	only	-	May	20	 3:00	0	-
-Rule	Morocco	2017	only	-	Jul	 1	 2:00	1:00	S
-Rule	Morocco	2018	only	-	May	12	 3:00	0	-
-Rule	Morocco	2018	only	-	Jun	16	 2:00	1:00	S
-Rule	Morocco	2019	only	-	May	 4	 3:00	0	-
-Rule	Morocco	2019	only	-	Jun	 8	 2:00	1:00	S
-Rule	Morocco	2020	only	-	Apr	18	 3:00	0	-
-Rule	Morocco	2020	only	-	May	30	 2:00	1:00	S
-Rule	Morocco	2021	only	-	Apr	10	 3:00	0	-
-Rule	Morocco	2021	only	-	May	15	 2:00	1:00	S
-Rule	Morocco	2022	only	-	Apr	 2	 3:00	0	-
-Rule	Morocco	2022	only	-	May	 7	 2:00	1:00	S
-Rule	Morocco	2023	only	-	Apr	22	 2:00	1:00	S
-Rule	Morocco	2024	only	-	Apr	13	 2:00	1:00	S
-Rule	Morocco	2025	only	-	Apr	 5	 2:00	1:00	S
+Rule	Morocco	2015	only	-	Jun	14	 3:00	0	-
+Rule	Morocco	2015	only	-	Jul	19	 2:00	1:00	S
+Rule	Morocco	2016	only	-	Jun	 5	 3:00	0	-
+Rule	Morocco	2016	only	-	Jul	10	 2:00	1:00	S
+Rule	Morocco	2017	only	-	May	21	 3:00	0	-
+Rule	Morocco	2017	only	-	Jul	 2	 2:00	1:00	S
+Rule	Morocco	2018	only	-	May	13	 3:00	0	-
+Rule	Morocco	2018	only	-	Jun	17	 2:00	1:00	S
+Rule	Morocco	2019	only	-	May	 5	 3:00	0	-
+Rule	Morocco	2019	only	-	Jun	 9	 2:00	1:00	S
+Rule	Morocco	2020	only	-	Apr	19	 3:00	0	-
+Rule	Morocco	2020	only	-	May	24	 2:00	1:00	S
+Rule	Morocco	2021	only	-	Apr	11	 3:00	0	-
+Rule	Morocco	2021	only	-	May	16	 2:00	1:00	S
+Rule	Morocco	2022	only	-	May	 8	 2:00	1:00	S
+Rule	Morocco	2023	only	-	Apr	23	 2:00	1:00	S
+Rule	Morocco	2024	only	-	Apr	14	 2:00	1:00	S
+Rule	Morocco	2025	only	-	Apr	 6	 2:00	1:00	S
 Rule	Morocco	2026	max	-	Mar	lastSun	 2:00	1:00	S
-Rule	Morocco	2035	only	-	Oct	27	 3:00	0	-
-Rule	Morocco	2036	only	-	Oct	18	 3:00	0	-
-Rule	Morocco	2037	only	-	Oct	10	 3:00	0	-
+Rule	Morocco	2036	only	-	Oct	19	 3:00	0	-
+Rule	Morocco	2037	only	-	Oct	 4	 3:00	0	-
 
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
 Zone Africa/Casablanca	-0:30:20 -	LMT	1913 Oct 26
--- a/make/data/tzdata/iso3166.tab	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/data/tzdata/iso3166.tab	Wed Jul 01 22:03:05 2015 -0700
@@ -26,11 +26,10 @@
 # This file is in the public domain, so clarified as of
 # 2009-05-17 by Arthur David Olson.
 #
-# From Paul Eggert (2014-07-18):
+# From Paul Eggert (2015-05-02):
 # This file contains a table of two-letter country codes.  Columns are
 # separated by a single tab.  Lines beginning with '#' are comments.
-# Although all text currently uses ASCII encoding, this is planned to
-# change to UTF-8 soon.  The columns of the table are as follows:
+# All text uses UTF-8 encoding.  The columns of the table are as follows:
 #
 # 1.  ISO 3166-1 alpha-2 country code, current as of
 #     ISO 3166-1 Newsletter VI-16 (2013-07-11).  See: Updates on ISO 3166
@@ -61,7 +60,7 @@
 AT	Austria
 AU	Australia
 AW	Aruba
-AX	Aaland Islands
+AX	Åland Islands
 AZ	Azerbaijan
 BA	Bosnia & Herzegovina
 BB	Barbados
@@ -90,7 +89,7 @@
 CF	Central African Rep.
 CG	Congo (Rep.)
 CH	Switzerland
-CI	Cote d'Ivoire
+CI	Côte d'Ivoire
 CK	Cook Islands
 CL	Chile
 CM	Cameroon
@@ -234,7 +233,7 @@
 PW	Palau
 PY	Paraguay
 QA	Qatar
-RE	Reunion
+RE	Réunion
 RO	Romania
 RS	Serbia
 RU	Russia
--- a/make/data/tzdata/northamerica	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/data/tzdata/northamerica	Wed Jul 01 22:03:05 2015 -0700
@@ -2684,7 +2684,17 @@
 			-4:00	US	A%sT
 
 # Cayman Is
-# See America/Panama.
+
+# From Paul Eggert (2015-05-15):
+# The Cayman government has decided to introduce DST in 2016, the idea being
+# to keep in sync with New York.  The legislation hasn't passed but the change
+# seems quite likely.  See: Meade B. Cayman 27.
+# http://www.cayman27.com.ky/2015/05/15/clock-ticks-toward-daylight-saving-time-in-cayman
+
+Zone	America/Cayman	-5:25:32 -	LMT	1890     # Georgetown
+			-5:07:11 -	KMT	1912 Feb # Kingston Mean Time
+			-5:00	-	EST	2016
+			-5:00	US	E%sT
 
 # Costa Rica
 
@@ -3207,7 +3217,6 @@
 Zone	America/Panama	-5:18:08 -	LMT	1890
 			-5:19:36 -	CMT	1908 Apr 22 # Colón Mean Time
 			-5:00	-	EST
-Link America/Panama America/Cayman
 
 # Puerto Rico
 # There are too many San Juans elsewhere, so we'll use 'Puerto_Rico'.
--- a/make/data/tzdata/southamerica	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/data/tzdata/southamerica	Wed Jul 01 22:03:05 2015 -0700
@@ -53,7 +53,7 @@
 #	I suggest the use of _Summer time_ instead of the more cumbersome
 #	_daylight-saving time_.  _Summer time_ seems to be in general use
 #	in Europe and South America.
-#	-- E O Cutler, _New York Times_ (1937-02-14), quoted in
+#	-- E O Cutler, _New York Times_ (1937-02-14), quoted in
 #	H L Mencken, _The American Language: Supplement I_ (1960), p 466
 #
 # Earlier editions of these tables also used the North American style
--- a/make/lib/CoreLibraries.gmk	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/lib/CoreLibraries.gmk	Wed Jul 01 22:03:05 2015 -0700
@@ -207,7 +207,7 @@
     LDFLAGS_SUFFIX_windows := -export:winFileHandleOpen -export:handleLseek \
         jvm.lib $(BUILD_LIBFDLIBM) $(WIN_VERIFY_LIB) \
         shell32.lib delayimp.lib -DELAYLOAD:shell32.dll \
-        advapi32.lib, \
+        advapi32.lib version.lib, \
     VERSIONINFO_RESOURCE := $(JDK_TOPDIR)/src/windows/resource/version.rc, \
     RC_FLAGS := $(RC_FLAGS) \
         -D "JDK_FNAME=java.dll" \
--- a/make/mapfiles/libjava/mapfile-vers	Wed Jun 24 11:10:35 2015 -0700
+++ b/make/mapfiles/libjava/mapfile-vers	Wed Jul 01 22:03:05 2015 -0700
@@ -1,5 +1,5 @@
 #
-# Copyright (c) 1997, 2014, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 1997, 2015, Oracle and/or its affiliates. All rights reserved.
 # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 #
 # This code is free software; you can redistribute it and/or modify it
@@ -128,12 +128,12 @@
 		Java_java_lang_ClassLoader_defineClass0;
 		Java_java_lang_ClassLoader_defineClass1;
 		Java_java_lang_ClassLoader_defineClass2;
+		Java_java_lang_ClassLoader_findBuiltinLib;
 		Java_java_lang_ClassLoader_findLoadedClass0;
 		Java_java_lang_ClassLoader_resolveClass0;
 		Java_java_lang_ClassLoader_00024NativeLibrary_find;
 		Java_java_lang_ClassLoader_00024NativeLibrary_load;
 		Java_java_lang_ClassLoader_00024NativeLibrary_unload;
-		Java_java_lang_ClassLoader_00024NativeLibrary_findBuiltinLib;
 		Java_java_lang_ClassLoader_registerNatives;
 		Java_java_lang_Compiler_registerNatives;
 		Java_java_lang_Double_longBitsToDouble;
--- a/src/bsd/doc/man/appletviewer.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/appletviewer.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 1995, 2013, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 1995, 2013, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,42 +47,42 @@
 .\" -----------------------------------------------------------------
 .\" * 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
+
+.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
--- a/src/bsd/doc/man/extcheck.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/extcheck.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,43 +47,43 @@
 .\" -----------------------------------------------------------------
 .\" * 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)
+
+.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
--- a/src/bsd/doc/man/idlj.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/idlj.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,520 +47,520 @@
 .\" -----------------------------------------------------------------
 .\" * 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\&.
+
+.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
--- a/src/bsd/doc/man/jar.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/jar.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,437 +47,437 @@
 .\" -----------------------------------------------------------------
 .\" * 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
+
+.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
--- a/src/bsd/doc/man/jarsigner.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/jarsigner.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,761 +47,761 @@
 .\" -----------------------------------------------------------------
 .\" * 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
+
+.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
--- a/src/bsd/doc/man/java.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/java.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
 '\" t
 .\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved.
-.\"
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
--- a/src/bsd/doc/man/javac.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/javac.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,1322 +47,1322 @@
 .\" -----------------------------------------------------------------
 .\" * 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)
+
+.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
--- a/src/bsd/doc/man/javadoc.1	Wed Jun 24 11:10:35 2015 -0700
+++ b/src/bsd/doc/man/javadoc.1	Wed Jul 01 22:03:05 2015 -0700
@@ -1,6 +1,5 @@
-'\" t
-.\"  Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved.
-.\"
+'\" t
+.\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved.
 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 .\"
 .\" This code is free software; you can redistribute it and/or modify it
@@ -21,14 +20,14 @@
 .\" or visit www.oracle.com if you need additional information or have any
 .\" questions.
 .\"
-.\"     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"
+.\"     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
 .\" -----------------------------------------------------------------
@@ -48,2957 +47,2957 @@
 .\" -----------------------------------------------------------------
 .\" * 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&#064;\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&lt;\fR and \f3&gt;\fR\&. Similarly, the ampersand (&) should be written as \f3&amp;\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&lt;\fR and \f3&gt;\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&#125;\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&lt;\fR and \f3&gt;\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 t