CVS update by michaels packages/xemacs-packages/jde/lisp,
ChangeLog.upstream, efc-xemacs.el, jde-checkstyle.el,
jde-complete.el, jde-ejb.el, jde-import.el,
jde-java-grammar.el, jde-javadoc.el, jde-open-source.el,
jde-plugins.el, jde-which-method.el, jde-xemacs.el ...
xemacs-cvs at xemacs.org
xemacs-cvs at xemacs.org
Mon Nov 26 10:17:01 EST 2007
User: michaels
Date: 07/11/26 16:17:00
Modified: packages/xemacs-packages/jde/lisp ChangeLog
ChangeLog.upstream ReleaseNotes.txt beanshell.el
efc-xemacs.el efc.el jde-ant.el jde-bug.el
jde-checkstyle.el jde-compat.el jde-compile.el
jde-complete.el jde-db.el jde-dbo.el jde-dbs.el
jde-ejb.el jde-gen.el jde-help.el jde-imenu.el
jde-import.el jde-java-font-lock.el
jde-java-grammar.el jde-javadoc-gen.el
jde-javadoc.el jde-jdb.el jde-make.el
jde-open-source.el jde-parse-class.el jde-parse.el
jde-plugins.el jde-run.el jde-util.el
jde-which-method.el jde-widgets.el jde-wiz.el
jde-xemacs.el jde-xref.el jde.el jtags makefile
Added: packages/xemacs-packages/jde/doc .nosearch
packages/xemacs-packages/jde/doc/html/jde-ug/images
build_fcn_cust_buff.gif completion_menu1.gif
completion_menu2.gif completion_menu3.gif
packages/xemacs-packages/jde/doc/src/jde-ug/images
build_fcn_cust_buff.gif completion_menu1.gif
completion_menu2.gif completion_menu3.gif
packages/xemacs-packages/jde/java .nosearch
packages/xemacs-packages/jde/java/lib junit.jar
packages/xemacs-packages/jde/lisp ChangeLog.ours
efc.el.upstream jde-annotations.el jde-autoload.el
jde-custom.el jde-junit.el jde-project-file.el
jde-sregex.el jde-tree-widget.el
jde-util.el.upstream jde-widgets.el.upstream
jde-xemacs.el.upstream regress.el
Removed: packages/xemacs-packages/jde/lisp jde-setnu.el
tree-widget.el
Log:
Update jde to author version 2.3.5.1.
Revision Changes Path
1.58 +4 -0 XEmacs/packages/xemacs-packages/jde/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/jde/ChangeLog,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -p -r1.57 -r1.58
--- ChangeLog 2006/03/14 08:48:00 1.57
+++ ChangeLog 2007/11/26 15:16:16 1.58
@@ -1,3 +1,7 @@
+2007-11-18 Mike Sperber <mike at xemacs.org>
+
+ * Makefile (AUTHOR_VERSION): Update to upstream version 2.3.5.1.
+
2006-03-14 Norbert Koch <viteno at xemacs.org>
* Makefile (VERSION): XEmacs package 1.51 released.
1.78 +10 -5 XEmacs/packages/xemacs-packages/jde/Makefile
Index: Makefile
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/jde/Makefile,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -p -r1.77 -r1.78
--- Makefile 2006/03/14 08:48:00 1.77
+++ Makefile 2007/11/26 15:16:17 1.78
@@ -18,14 +18,14 @@
# Boston, MA 02111-1307, USA.
VERSION = 1.51
-AUTHOR_VERSION = 2.3.3
-MAINTAINER = Andy Piper <andy at xemacs.org>
+AUTHOR_VERSION = 2.3.5.1
+MAINTAINER = XEmacs Development Team <xemacs-beta at xemacs.org>
AUTHOR = Paul Kinnucan <paulk at mathworks.com>
PACKAGE = jde
PKG_TYPE = regular
REQUIRES = jde cc-mode semantic debug speedbar \
edit-utils eterm mail-lib xemacs-base xemacs-devel \
- eieio elib sh-script fsf-compat
+ cedet-common eieio elib sh-script fsf-compat os-utils
CATEGORY = standard
# WARNING order is really important here so that dependencies are
@@ -67,7 +67,6 @@ ELCS = $(EARLY_ELCS) \
lisp/jde-plugins.elc \
lisp/jde-parse-class.elc \
lisp/jde-run.elc \
- lisp/jde-setnu.elc \
lisp/jde-stat.elc \
lisp/jde-util.elc \
lisp/jde-which-method.elc \
@@ -75,8 +74,14 @@ ELCS = $(EARLY_ELCS) \
lisp/jde-wiz.elc \
lisp/jde-ejb.elc \
lisp/jde-xemacs.elc \
+ lisp/jde-annotations.elc \
+ lisp/jde-custom.el \
+ lisp/jde-junit.elc \
lisp/jde-xref.elc \
- lisp/tree-widget.elc \
+ lisp/jde-project-file.elc \
+ lisp/jde-sregex.elc \
+ lisp/jde-tree-widget.elc \
+ lisp/regress.elc \
$(LATE_ELCS)
EXTRA_SOURCES = lisp/ChangeLog.upstream
1.6 +1 -1 XEmacs/packages/xemacs-packages/jde/package-info.in
Index: package-info.in
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/jde/package-info.in,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- package-info.in 2006/03/03 20:40:25 1.5
+++ package-info.in 2007/11/26 15:16:17 1.6
@@ -13,7 +13,7 @@
filename FILENAME
md5sum MD5SUM
size SIZE
- provides (beanshell efc efc-xemacs jde-ant jde-bug jde-checkstyle jde-class jde-compat jde-compile jde-complete jde-db jde-dbo jde-dbs jde-ejb jde-gen jde-help jde-imenu jde-import jde-java-font-lock jde-java-grammar jde-javadoc-gen jde-javadoc jde-jdb jde-make jde-open-source jde-package jde-parse-class jde-parse jde-plugins jde-run jde-setnu jde-stat jde-util jde-which-method jde-widgets jde-wiz jde-xemacs jde-xref jde tree-widget)
+ provides (beanshell efc efc-xemacs jde-parse jde-db jde-dbo jde-dbs jde-ant jde-bug jde-checkstyle jde-class jde-compile jde-complete jde-gen jde-help jde-imenu jde-import jde-java-font-lock jde-java-grammar jde-javadoc-gen jde-javadoc jde-jdb jde-make jde-open-source jde-package jde-plugins jde-parse-class jde-run jde-stat jde-util jde-which-method jde-widgets jde-wiz jde-ejb jde-xemacs jde-annotations jde-custom.el jde-junit jde-xref jde-project-file jde-sregex jde-tree-widget regress jde)
requires (REQUIRES)
type regular
))
1.1 XEmacs/packages/xemacs-packages/jde/doc/.nosearch
Index: .nosearch
===================================================================
;; Exclude this directory from the Emacs load-path.
1.2 +1 -1 XEmacs/packages/xemacs-packages/jde/doc/html/jdb-ug/jdb-ug-toc.html
Index: jdb-ug-toc.html
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/jde/doc/html/jdb-ug/jdb-ug-toc.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- jdb-ug-toc.html 2006/03/03 20:40:33 1.1
+++ jdb-ug-toc.html 2007/11/26 15:16:21 1.2
@@ -1,6 +1,6 @@
<html>
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="StyleSheet" href="../css/jde_style.css" TYPE="text/css">
</head>
1.2 +156 -155 XEmacs/packages/xemacs-packages/jde/doc/html/jdb-ug/jdb-ug.html
Index: jdb-ug.html
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/jde/doc/html/jdb-ug/jdb-ug.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- jdb-ug.html 2006/03/03 20:40:33 1.1
+++ jdb-ug.html 2007/11/26 15:16:21 1.2
@@ -1,46 +1,46 @@
<html><link rel="StyleSheet" href="../css/jde_style.css" TYPE="text/css"><head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
- <title>Debugging with jdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.49"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><h1 class="title"><a name="d0e2"></a>Debugging with jdb</h1></div><div><p class="releaseinfo">
- <i>
- Revised for JDEE 2.3.3
- </i>
- </p></div><div><p class="copyright">Copyright © 1997, 1998, 1999, 2000, 2001, 2002, 2003 Paul Kinnucan</p></div><hr></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e31"></a><a name="Intro"></a>Debugger Setup</h2></div></div><p>You should perform the following steps before attempting to use jdb.</p><div class="itemizedlist"><ul type="disc"><li><p>Set the configuration variable
- <tt>jde-debugger</tt> to <tt>jdb</tt> if
+ <title>Debugging with jdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.67.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="d51e2"></a>Debugging with jdb</h1></div><div><p class="releaseinfo">
+ <em><span class="remark">
+ Revised for JDEE <span class="productnumber">2.3.3</span>
+ </span></em>
+ </p></div><div><p class="copyright">Copyright © 1997-2003 Paul Kinnucan</p></div></div><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e31"></a><a name="Intro"></a>Debugger Setup</h2></div></div></div><p>You should perform the following steps before attempting to use jdb.</p><div class="itemizedlist"><ul type="disc"><li><p>Set the configuration variable
+ <code class="varname">jde-debugger</code> to <code class="option">jdb</code> if
you are using version 1.3 (or later) of the Windows or
Solaris versions of the JDK or version 1.2.2 (or later) of
the Linux version of the JDK. Set
- <tt>jde-debugger</tt> to <tt>oldjdb</tt>
+ <code class="varname">jde-debugger</code> to <code class="option">oldjdb</code>
if you are using older versions of the JDK.</p></li><li><p>
- Use <tt>jde-sourcepath</tt> to specify the paths
+ Use <code class="varname">jde-sourcepath</code> to specify the paths
of any source code that you expect to visit while
debugging your application (see <a href="#SettingSourcePath">
Setting the Source Path</a>). If you suspect that a
problem is occurring in the Java API, you should include
the API source files in your source path.
</p></li><li><p>
- Set <tt>jde-compile-option-debug</tt> on
+ Set <code class="varname">jde-compile-option-debug</code> on
(see
<a href="../jde-ug/jde-ug-content.html#CompilingJavaPrograms">Compiling
Java Programs</a>). This causes the compiler to insert
information needed by the debugger into your
application's class files.
</p></li><li><p>Specify the app's main class either by setting the
- <tt>jde-run-application-class</tt> variable or by starting the
+ <code class="varname">jde-run-application-class</code> variable or by starting the
debugger from the buffer that contains the source file for
the main class.
- </p></li></ul></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e77"></a><a name="RunningDebugger"></a>Running the Debugger</h2></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e81"></a><a name="StartingDebugger"></a>Starting the Debugger</h4></div></div><p>To debug a program with <tt>jdb</tt>,
+ </p></li></ul></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e77"></a><a name="RunningDebugger"></a>Running the Debugger</h2></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e81"></a><a name="StartingDebugger"></a>Starting the Debugger</h4></div></div></div><p>To debug a program with <code class="filename">jdb</code>,
first select a buffer containing the source of the program you
want to debug (or a source buffer containing the program's
main class if you have not set
- <tt>jde-run-application-class</tt>). Then execute
- the JDEE's <b>jde-debug</b> command. You can execute
+ <code class="varname">jde-run-application-class</code>). Then execute
+ the JDEE's <code class="command">jde-debug</code> command. You can execute
this command by:
</p><div class="itemizedlist"><ul type="disc"><li><p>Selecting
- JDE->Debug App
+ <span><strong class="guimenu">JDE</strong></span>-><span><strong class="guimenuitem">Debug App</strong></span>
</p></li><li><p>
Entering the key combination
- <b>C</b>-<b>c</b> <b>C</b>-<b>v</b> <b>C</b>-<b>d</b>
- </p></li><li><p>Entering <b>M</b>-<b>x</b> <b>jde-debug</b></p></li></ul></div><p>The JDEE launches jdb, passing to it the name of the main
+ <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">c</strong></span> <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">v</strong></span> <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">d</strong></span>
+ </p></li><li><p>Entering <span><strong class="keycap">M</strong></span>-<span><strong class="keycap">x</strong></span> <code class="command">jde-debug</code></p></li></ul></div><p>The JDEE launches jdb, passing to it the name of the main
class of the program in the current source buffer and any
debug options that you have specified via the JDEE's debugger
option variables (see <a href="#SettingDebugOptions">Setting Debug Options</a>.
@@ -50,55 +50,55 @@
source window into two windows.
</p><div class="screenshot"><div class="mediaobject"><img src="images/debug1.gif"></div></div><p>
The upper window shows the source buffer. The menu bar
- of the source buffer displays a menu (Jdb)
+ of the source buffer displays a menu (<span><strong class="guimenu">Jdb</strong></span>)
of debug commands. The lower window shows the debugger
interaction buffer.
</p><p>At this point, you can set breakpoints, run to a breakpoint that
you set before you started the debugger, or step into the main method
- of your program.</p><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e154"></a><a name="SettingDebugOptions"></a>Setting Debug Options</h5></div></div><p>The <b>jde-jdb</b> command (selected by
- JDE->Debug App when jdb
+ of your program.</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e154"></a><a name="SettingDebugOptions"></a>Setting Debug Options</h5></div></div></div><p>The <code class="command">jde-jdb</code> command (selected by
+ <span><strong class="guimenu">JDE</strong></span>-><span><strong class="guimenuitem">Debug App</strong></span> when jdb
is the debugger for the current project) can optionally pass
command-line arguments that specify various debug options to
jdb when starting jdb. The JDEE provides two ways to specify
these options: via customization variables or in the
- minibuffer when you run the <b>jde-jdb</b>
- command.</p><p>The <b>jde-jdb</b> command passes any
+ minibuffer when you run the <code class="command">jde-jdb</code>
+ command.</p><p>The <code class="command">jde-jdb</code> command passes any
options that you specify via customization variables to jdb.
In addition, if you set the customization variable
- <tt>jde-db-read-vm-args</tt> to a non-nil value,
- the <b>jde-jdb</b> command prompts you to enter
+ <code class="varname">jde-db-read-vm-args</code> to a non-nil value,
+ the <code class="command">jde-jdb</code> command prompts you to enter
debugger options in the minibuffer. It appends the options
that you enter to the options specified via customization
variables. The JDEE saves the arguments that you enter in a
minibuffer history list. You can recall previously entered
options by pressing the up or down arrows on your keyboard.
- </p></div><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e183"></a><a name="SettingAppArguments"></a>Setting App Arguments</h5></div></div><p>You can use the customization variable
- <tt>jde-db-option-application-args</tt> to specify
+ </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e183"></a><a name="SettingAppArguments"></a>Setting App Arguments</h5></div></div></div><p>You can use the customization variable
+ <code class="varname">jde-db-option-application-args</code> to specify
arguments to be passed to the application launched by jdb.
- The <b>jde-jdb</b> command inserts the specified
+ The <code class="command">jde-jdb</code> command inserts the specified
arguments on the command-line that it constructs to run
jdb.</p><p>In addition, if you set the customization variable
- <tt>jde-db-read-app-args</tt> to a
- non-<tt>nil</tt> value, the
- <b>jde-jdb</b> command prompts you to enter the
+ <code class="varname">jde-db-read-app-args</code> to a
+ non-<code class="option">nil</code> value, the
+ <code class="command">jde-jdb</code> command prompts you to enter the
application arguments in the minibuffer. It appends the
options that you enter to the arguments specified via
- <tt>jde-db-option-application-args</tt>. The JDEE
+ <code class="varname">jde-db-option-application-args</code>. The JDEE
saves the arguments that you enter in a minibuffer history
list. You can recall previously entered options by pressing
- the up or down arrows on your keyboard. </p></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e209"></a><a name="EnteringCommands"></a>Entering Debug Commands</h4></div></div><p>The JDE lets you enter commands from either the current source
+ the up or down arrows on your keyboard. </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e209"></a><a name="EnteringCommands"></a>Entering Debug Commands</h4></div></div></div><p>The JDE lets you enter commands from either the current source
buffer or from the debugger command-line interaction buffer.
You can enter all debugger commands from the debugger
buffer. You can enter only a subset of debugger commands
from the current source buffer. </p><p> To enter a debugger command
from the current source buffer, select the command from the
- jdb menu or type the shortcut key for the command. The Jdb
+ jdb menu or type the shortcut key for the command. The <span><strong class="guimenu">Jdb</strong></span>
menu lists the shortcut keys
for debugger commands. </p><p>To enter a command in the debugger interaction window, type the
- command at the debugger prompt and press the <b>Enter</b>
+ command at the debugger prompt and press the <span><strong class="keycap">Enter</strong></span>
key. To see a list of debugger commands, enter the command
- <b>help</b>.
- </p></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e228"></a><a name="SteppingProgram"></a>Stepping Through a Program</h4></div></div><p>
+ <code class="command">help</code>.
+ </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e228"></a><a name="SteppingProgram"></a>Stepping Through a Program</h4></div></div></div><p>
Jdb provides a set of command-line commands that advance a
program to the next line or the next breakpoint. The JDEE's
jdb interface provides Emacs commands that invoke the jdb's
@@ -106,15 +106,15 @@
the next line to be executed in the source buffer. If you
prefer, you can enter jdb's step commands directly in the jdb
buffer.
- </p><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e234"></a><a name="StepCommands"></a>Step Commands</h5></div></div><p> The following table lists the jdb step commands
+ </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e234"></a><a name="StepCommands"></a>Step Commands</h5></div></div></div><p> The following table lists the jdb step commands
supported by the JDEE.
- </p><div class="table"><p><b>Table 1. Step Commands</b></p><table summary="Step Commands" border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th>Jdb Menu Item</th><th>Emacs Command</th><th>jdb Command</th><th>Description</th></tr></thead><tbody><tr><td>Step Over</td><td>jde-bug-step-over</td><td>next</td><td><p>Advance to the next line in the current
+ </p><div class="table"><a name="d51e240"></a><p class="title"><b>Table 1. Step Commands</b></p><table summary="Step Commands" border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th>Jdb Menu Item</th><th>Emacs Command</th><th>jdb Command</th><th>Description</th></tr></thead><tbody><tr><td>Step Over</td><td>jde-bug-step-over</td><td>next</td><td><p>Advance to the next line in the current
method, stepping over any lines that invoke other
methods.</p></td></tr><tr><td>Step Into</td><td>jde-debug-step-into</td><td>step</td><td><p>Advance to the next line in the
program.</p></td></tr><tr><td>Step Out</td><td>jde-debug-step-out</td><td>step up</td><td><p>Advance to the next line in the method
that invoked the current method.</p></td></tr><tr><td>Continue</td><td>jde-debug-cont</td><td>cont</td><td><p>Advance to the next breakpoint or to the
end of the program, whichever comes
- first.</p></td></tr></tbody></table></div></div><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e295"></a><a name="DebugCursor"></a>Debug Cursor</h5></div></div><p>The JDEE uses an arrow, called the debug cursor, to
+ first.</p></td></tr></tbody></table></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e295"></a><a name="DebugCursor"></a>Debug Cursor</h5></div></div></div><p>The JDEE uses an arrow, called the debug cursor, to
indicate the next line to be executed as the result of a
step or continue command. The debug cursor appears in the
left gutter of the source window containing the next line to
@@ -128,10 +128,10 @@
You should check your source path setting (see <a href="#SettingSourcePath">Setting the Source
Path</a>) to ensure that it includes all source
files in the execution path of your program.
- </p></div></div></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e313"></a><a name="SettingBreakpoints"></a>Setting Breakpoints</h2></div></div><p>To set a breakpoint on any executable line in the current
- source buffer, click on the line and select Jdb->Set Breakpoint
- (<b>C</b>-<b>c</b><b>C</b>-<b>a</b>
- <b>C</b>-<b>b</b>). The JDEE highlights the
+ </p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e313"></a><a name="SettingBreakpoints"></a>Setting Breakpoints</h2></div></div></div><p>To set a breakpoint on any executable line in the current
+ source buffer, click on the line and select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Set Breakpoint</strong></span>
+ (<span><strong class="keycap">C</strong></span>-<span><strong class="keycap">c</strong></span><span><strong class="keycap">C</strong></span>-<span><strong class="keycap">a</strong></span>
+ <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">b</strong></span>). The JDEE highlights the
current line to indicate that a breakpoint is to be set at that
line. </p><div class="screenshot"><div class="mediaobject"><img src="images/breakpoint.gif"></div></div><p>
If the debugger is
@@ -144,98 +144,98 @@
the debugger puts it on a list of pending breakpoints. If the
class is subsequently loades, the debugger sets the breakpoint
in the class.
- </p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e348"></a><a name="BreakpointColors"></a>Breakpoint Colors</h4></div></div><p>
+ </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e348"></a><a name="BreakpointColors"></a>Breakpoint Colors</h4></div></div></div><p>
The color of a breakpoint highlight indicates the status of the breakpoint
as follows.
- </p><div class="table"><p><b>Table 1. Breakpoint Colors</b></p><table summary="Breakpoint Colors" border="1"><colgroup><col><col></colgroup><thead><tr><th>Color</th><th>Description</th></tr></thead><tbody><tr><td>Green</td><td>The JDEE has not yet issued a command to the
+ </p><div class="table"><a name="d51e354"></a><p class="title"><b>Table 1. Breakpoint Colors</b></p><table summary="Breakpoint Colors" border="1"><colgroup><col><col></colgroup><thead><tr><th>Color</th><th>Description</th></tr></thead><tbody><tr><td>Green</td><td>The JDEE has not yet issued a command to the
debugger to set the breakpoint.</td></tr><tr><td>Yellow</td><td>The breakpoint is pending loading of the class in which it
- is to be set.</td></tr><tr><td>Red</td><td>The breakpoint has been set.</td></tr></tbody></table></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e380"></a><a name="ClearingBreakpoints"></a>Clearing
- Breakpoints</h4></div></div><p>
+ is to be set.</td></tr><tr><td>Red</td><td>The breakpoint has been set.</td></tr></tbody></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e380"></a><a name="ClearingBreakpoints"></a>Clearing
+ Breakpoints</h4></div></div></div><p>
To clear a breakpoint from a line in the current buffer, click
- on the line and select Jdb->Toggle Breakpoint
- (<b>C</b>-<b>c</b>
- <b>C</b>-<b>a</b>
- <b>C</b>-<b>b</b>).
+ on the line and select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Toggle Breakpoint</strong></span>
+ (<span><strong class="keycap">C</strong></span>-<span><strong class="keycap">c</strong></span>
+ <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">a</strong></span>
+ <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">b</strong></span>).
</p><p>To clear all breakpoints set in the current session,
- select Jdb->Clear
- Breakpoints.
+ select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Clear
+ Breakpoints</strong></span>.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You can also set and clear breakpoints by entering jdb
breakpoint commands in the jdb interaction buffer. See the
jdb documentation for information on using the jdb
- breakpoint commands.</p></div></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e421"></a><a name="SettingSourcePath"></a>Setting the Source Path</h2></div></div><p>The <tt>jde-sourcepath</tt> variable specifies the
+ breakpoint commands.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e421"></a><a name="SettingSourcePath"></a>Setting the Source Path</h2></div></div></div><p>The <code class="varname">jde-sourcepath</code> variable specifies the
directories the JDEE should search for source for classes
visited by the debugger as you step through your program.
- </p><p>To set this variable, enter <b>M-x customize-variable jde-sourcepath</b>.
+ </p><p>To set this variable, enter <code class="command">M-x customize-variable jde-sourcepath</code>.
The customization buffer for jde-sourcepath appears. The buffer shows the current
- source path as a list of paths.</p><div class="screenshot"><div class="mediaobject"><img src="images/debug2.gif"></div></div><p>To add a path, click the INS button
+ source path as a list of paths.</p><div class="screenshot"><div class="mediaobject"><img src="images/debug2.gif"></div></div><p>To add a path, click the <span class="guibutton">INS</span> button
corresponding to the position in the list and enter the path in
- the resulting edit field. To delete a path, click the DEL button
+ the resulting edit field. To delete a path, click the <span class="guibutton">DEL</span> button
corresponding to the path. You can use environment variables in paths and
use dot notation to specify paths relative to the project file for the
project to which this sourcepath applies. When you are done editing the buffer,
- press the State button to set the
+ press the <span class="guibutton">State</span> button to set the
variable.</p><p>To avoid having to specify the sourcepath every time you
start a session, save the setting of
- <tt>jde-db-sourcepath</tt> in your
- <tt>prj.el</tt> file (see <a href="../jde-ug/jde-ug-content.html#SavingProjSettings">Saving
+ <code class="varname">jde-db-sourcepath</code> in your
+ <code class="filename">prj.el</code> file (see <a href="../jde-ug/jde-ug-content.html#SavingProjSettings">Saving
Project Settings</a>) To save the setting in your project
file, select
- JDE->Project->Project File->Save (<b>C</b>-<b>c</b>
- <b>C</b>-<b>v</b>
- <b>C</b>-<b>p</b>
+ <span><strong class="guimenu">JDE</strong></span>-><span><strong class="guimenuitem">Project</strong></span>-><span><strong class="guimenuitem">Project File</strong></span>-><span><strong class="guimenuitem">Save</strong></span> (<span><strong class="keycap">C</strong></span>-<span><strong class="keycap">c</strong></span>
+ <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">v</strong></span>
+ <span><strong class="keycap">C</strong></span>-<span><strong class="keycap">p</strong></span>
). </p><p>
You must specify the paths of the top-level directories of any
source code that you might visit while debugging your
application. The source code directory structure must mirror
your application's package structure. For example, suppose that your
application includes a set of classes packaged in the
- <tt>myapp</tt> directory. Then, the source for those classes
- must be reside in a directory named <tt>myapp</tt> and you must
- specify the path of <tt>myapp</tt>'s parent directory.
+ <code class="filename">myapp</code> directory. Then, the source for those classes
+ must be reside in a directory named <code class="filename">myapp</code> and you must
+ specify the path of <code class="filename">myapp</code>'s parent directory.
</p><p>If you want to step through the JDK source code,
select the source code install option when you install the JDK
- and set the <tt>jde-sourcepath</tt> variable
+ and set the <code class="varname">jde-sourcepath</code> variable
to the top-level directory containing the source code.
The JDE will use the JDK's package structure to find the
- source code in the subdirectories. </p></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e505"></a><a name="DisplayingVariables"></a>Displaying Variables</h2></div></div><p>This section shows you how to display the values of variables
- (or expressions).</p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e511"></a><a name="DisplayingExpressions"></a>Displaying
- Expressions</h4></div></div><p>When the debuggee program is stopped, the debugger lets
+ source code in the subdirectories. </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e505"></a><a name="DisplayingVariables"></a>Displaying Variables</h2></div></div></div><p>This section shows you how to display the values of variables
+ (or expressions).</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e511"></a><a name="DisplayingExpressions"></a>Displaying
+ Expressions</h4></div></div></div><p>When the debuggee program is stopped, the debugger lets
you display the value of any valid Java expression composed of
variables currently in scope. For example, to display the
value of a local, in-scope variable whose source is displayed
in a Java source buffer, put the point on the variable and
select
- Jdb->Display->Expression. The JDEE prompts you to enter an expression to be
+ <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Display</strong></span>-><span><strong class="guimenuitem">Expression</strong></span>. The JDEE prompts you to enter an expression to be
evaluated and displayed in the minibuffer.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_var1.gif"></div></div><p> The default expression is the variable at point in the
source buffer. Edit the displayed expression and press
- <b>Enter</b>. The JDEE issues a command to the
- debugger to display the variable in the jdb buffer.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_var2.gif"></div></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e538"></a><a name="DisplayingObjects"></a>Displaying
- Objects</h4></div></div><p>To display the values of the fields of an object
+ <span><strong class="keycap">Enter</strong></span>. The JDEE issues a command to the
+ debugger to display the variable in the jdb buffer.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_var2.gif"></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e538"></a><a name="DisplayingObjects"></a>Displaying
+ Objects</h4></div></div></div><p>To display the values of the fields of an object
referenced by an in-scope variable in the current source
buffer, and select
- Jdb->Display->Object. The JDEE prompts you to enter the name of the
+ <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Display</strong></span>-><span><strong class="guimenuitem">Object</strong></span>. The JDEE prompts you to enter the name of the
variable in the minibuffer. The default is the variable at
- point in the source buffer. Press <b>Enter</b>. The
- JDEE issues a <b>dump</b> command to the debugger
+ point in the source buffer. Press <span><strong class="keycap">Enter</strong></span>. The
+ JDEE issues a <code class="command">dump</code> command to the debugger
to display the field values of the object referenced by the
- variable you entered.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_obj.gif"></div></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e562"></a><a name="DisplayingLocals"></a>Displaying Locals
- </h4></div></div><p>To display the values of all in-scope local variables,
+ variable you entered.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_obj.gif"></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e562"></a><a name="DisplayingLocals"></a>Displaying Locals
+ </h4></div></div></div><p>To display the values of all in-scope local variables,
including the values of the arguments of the method in which
the program is halted, select
- Jdb->Display->Locals. The JDEE issues a <b>locals</b>
+ <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Display</strong></span>-><span><strong class="guimenuitem">Locals</strong></span>. The JDEE issues a <code class="command">locals</code>
command to the debugger to display the local variable
- values.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_locals.gif"></div></div></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e583"></a><a name="SettingVariables"></a>Setting Variables</h2></div></div><p>Jdb allows you to change the values of variables that are
+ values.</p><div class="screenshot"><div class="mediaobject"><img src="images/display_locals.gif"></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e583"></a><a name="SettingVariables"></a>Setting Variables</h2></div></div></div><p>Jdb allows you to change the values of variables that are
in scope. To change the value of a variable via the JDEE's jdb
- interface:</p><div class="orderedlist"><ol type="1"><li><p>Position point on the variable you want to change.</p></li><li><p>Select Jdb->Set Variable.
+ interface:</p><div class="orderedlist"><ol type="1"><li><p>Position point on the variable you want to change.</p></li><li><p>Select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">Set Variable</strong></span>.
</p><p>The JDEE prompts you to enter a left expression that
represents the variable whose value you want to change. The
default is the variable at point in the source buffer.
</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var1.gif"></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Edit the expression if necessary. For example, to set
the value of an array element at point, edit the
- expression to include the index of the element.</p></div></li><li><p>Press <b>Enter</b>.</p><p>The JDEE prompts you to enter the new value of the
- variable.</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var2.gif"></div></div></li><li><p>Enter the new value at the prompt in the minibuffer.</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var3.gif"></div></div></li><li><p>Press <b>Enter</b>.</p><p>The JDEE issues a <b>set</b> command to the
+ expression to include the index of the element.</p></div></li><li><p>Press <span><strong class="keycap">Enter</strong></span>.</p><p>The JDEE prompts you to enter the new value of the
+ variable.</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var2.gif"></div></div></li><li><p>Enter the new value at the prompt in the minibuffer.</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var3.gif"></div></div></li><li><p>Press <span><strong class="keycap">Enter</strong></span>.</p><p>The JDEE issues a <code class="command">set</code> command to the
debugger to set the specified variable to the new
- value.</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var4.gif"></div></div></li></ol></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e645"></a><a name="DebugExternalProcesses"></a>Debugging External Processes</h2></div></div><p>Normally jdb launches the application that it debugs.
+ value.</p><div class="screenshot"><div class="mediaobject"><img src="images/set_var4.gif"></div></div></li></ol></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e645"></a><a name="DebugExternalProcesses"></a>Debugging External Processes</h2></div></div></div><p>Normally jdb launches the application that it debugs.
However, you can use jdb to debug processes that are not
launched by jdb itself. This is useful, for example, if you need
to debug a process running on a remote computer or a Java
@@ -248,146 +248,147 @@
anytime after it has started. Listen mode allows you to debug
the startup of a Java process launched by a nonJava process.</p><p>
The following sections explain how to use the JDEE's jdb
- interface to run jdb in attach and listen mode.</p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e655"></a><a name="AttachingProcesses"></a>Attaching Processes</h4></div></div><p>To attach jdb to an external process, you must ensure that the
+ interface to run jdb in attach and listen mode.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e655"></a><a name="AttachingProcesses"></a>Attaching Processes</h4></div></div></div><p>To attach jdb to an external process, you must ensure that the
external process is started in debug server mode. You must then
- start jdb in attach mode.</p><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e661"></a><a name="DebugServerMode"></a>Starting the External
- Process in Debug Server Mode</h5></div></div><p>To start an external process in debug server mode, you
+ start jdb in attach mode.</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e661"></a><a name="DebugServerMode"></a>Starting the External
+ Process in Debug Server Mode</h5></div></div></div><p>To start an external process in debug server mode, you
must start the vm that runs the process with the following
- command-line options:</p><div class="itemizedlist"><ul type="disc"><li><p><tt>-Xdebug</tt></p></li><li><p>
- <tt>-Xrunjdwp:transport=<b>TRANSPORT</b>,address=<b>ADDRESS</b>,server=y,suspend=<b>SUSPEND</b></tt>
- </p><p>where</p><div class="itemizedlist"><ul type="round"><li><p><tt><b>TRANSPORT</b></tt> is
+ command-line options:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">-Xdebug</code></p></li><li><p>
+ <code class="literal">-Xrunjdwp:transport=<span><strong class="keycap">TRANSPORT</strong></span>,address=<span><strong class="keycap">ADDRESS</strong></span>,server=y,suspend=<span><strong class="keycap">SUSPEND</strong></span></code>
+ </p><p>where</p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal"><span><strong class="keycap">TRANSPORT</strong></span></code> is
the type of communications channel between jdb and
the debuggee process, either
- <tt>dt_socket</tt> (socket) or
- <tt>dt_shmem</tt> (shared memory, valid
- only for Windows systems)</p></li><li><p><tt><b>ADDRESS</b></tt> is
+ <code class="literal">dt_socket</code> (socket) or
+ <code class="literal">dt_shmem</code> (shared memory, valid
+ only for Windows systems)</p></li><li><p><code class="literal"><span><strong class="keycap">ADDRESS</strong></span></code> is
the address of the socket port or shared memory area
used by the debuggee process to listen for a jdb
- connection.</p></li><li><p><tt><b>SUSPEND</b></tt> is
- either <tt>y</tt> (suspend the debuggee
+ connection.</p></li><li><p><code class="literal"><span><strong class="keycap">SUSPEND</strong></span></code> is
+ either <code class="literal">y</code> (suspend the debuggee
process at startup, i.e., to wait for jdb to start,
a useful option when you need to debug an
- application's startup code) or <tt>n</tt>
- (do not suspend the debuggee process)</p></li></ul></div></li></ul></div><div class="example"><p><b>Example 1. Specifying Socket Transport</b></p><p><tt>-Xdebug
- -Xrunjdwp:transport=dt_socket,address=4444,server=y,suspend=n</tt></p></div><div class="example"><p><b>Example 2. Specifying Shared Memory Transport (MS Windows only)</b></p><p><tt>-Xdebug
- -Xrunjdwp:transport=dt_shmem,address=javadebug,server=y,suspend=n</tt></p></div><p>The JDEE customization variable, <tt>jde-run-option-debug</tt>, causes
+ application's startup code) or <code class="literal">n</code>
+ (do not suspend the debuggee process)</p></li></ul></div></li></ul></div><div class="example"><a name="d51e719"></a><p class="title"><b>Example 1. Specifying Socket Transport</b></p><p><code class="literal">-Xdebug
+ -Xrunjdwp:transport=dt_socket,address=4444,server=y,suspend=n</code></p></div><div class="example"><a name="d51e725"></a><p class="title"><b>Example 2. Specifying Shared Memory Transport (MS Windows only)</b></p><p><code class="literal">-Xdebug
+ -Xrunjdwp:transport=dt_shmem,address=javadebug,server=y,suspend=n</code></p></div><p>The JDEE customization variable, <code class="varname">jde-run-option-debug</code>, causes
the JDEE to generate these arguments automatically when launching a vm to run a Java
application. Thus, if you plan to launch the debuggee process from the JDEE, you
- should set this variable to the desired options.</p></div><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e736"></a><a name="AttachMode"></a>Starting jdb in Attach
- Mode</h5></div></div><p>To attach jdb to an existing process via a socket,
- select Jdb->External Process->Attach Via Socket from the Emacs menu bar. By default,
+ should set this variable to the desired options.</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e736"></a><a name="AttachMode"></a>Starting jdb in Attach
+ Mode</h5></div></div></div><p>To attach jdb to an existing process via a socket,
+ select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">External Process</strong></span>-><span><strong class="guimenuitem">Attach Via Socket</strong></span> from the Emacs menu bar. By default,
the JDEE uses the socket address specified by
- the customization variable <tt>jde-db-option-connect-socket</tt>.
+ the customization variable <code class="varname">jde-db-option-connect-socket</code>.
If you set this variable to Prompt (nil), the JDEE
prompts you to enter a socket address in the minibuffer.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The default socket address specified by
- <tt>jde-db-option-connect-socket</tt>
+ <code class="varname">jde-db-option-connect-socket</code>
is the same as the default socket address specified
- by <tt>jde-run-option-debug</tt>. Thus, if you
+ by <code class="varname">jde-run-option-debug</code>. Thus, if you
want to attach jdb to a process started by the JDEE, the
only variable you have to set is
- <tt>jde-run-option-debug</tt> (to run
+ <code class="varname">jde-run-option-debug</code> (to run
the debuggee process in socket attach mode).</p></div><p>To attach jdb to an existing process via a shared memory
connection (Windows platforms only),
- select Jdb->External Process->Attach Via Shared Memory from the Emacs menu bar. By default,
+ select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">External Process</strong></span>-><span><strong class="guimenuitem">Attach Via Shared Memory</strong></span> from the Emacs menu bar. By default,
the JDEE uses the shared memory transport name specified by
the customization variable
- <tt>jde-db-option-connect-shared-memory-name</tt>.
+ <code class="varname">jde-db-option-connect-shared-memory-name</code>.
If you set this variable to Prompt (nil), the JDEE
prompts you to enter a shared-memory name in the minibuffer.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The default shared memory name specified by
- <tt>jde-db-option-connect-shared-memory-name</tt>
+ <code class="varname">jde-db-option-connect-shared-memory-name</code>
is the same as the default shared memory name specified
- by <tt>jde-run-option-debug</tt>. Thus, if you
+ by <code class="varname">jde-run-option-debug</code>. Thus, if you
want to attach jdb to a process started by the JDEE, the
only variable you have to set is
- <tt>jde-run-option-debug</tt> (to run
- the debuggee process in shared memory attach mode).</p></div></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e790"></a><a name="ListeningForProcesses"></a>Listening for Processes</h4></div></div><p>To connect an external process to a jdb instance running in listener
+ <code class="varname">jde-run-option-debug</code> (to run
+ the debuggee process in shared memory attach mode).</p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e790"></a><a name="ListeningForProcesses"></a>Listening for Processes</h4></div></div></div><p>To connect an external process to a jdb instance running in listener
mode:</p><div class="orderedlist"><ol type="1"><li><p>Start jdb in listener mode (see <a href="#ListenMode">Starting
jdb in Listen Mode</a>)</p></li><li><p>Start the debuggee process in debug client
mode(see <a href="#DebugClientMode">Starting
- the External Process in Debug Client Mode</a>)</p></li></ol></div><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e809"></a><a name="ListenMode"></a>Starting jdb in Listen Mode</h5></div></div><p>To start jdb in listen mode, select Jdb->External Process->Listen For from the Emacs menu bar. By default, the
+ the External Process in Debug Client Mode</a>)</p></li></ol></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e809"></a><a name="ListenMode"></a>Starting jdb in Listen Mode</h5></div></div></div><p>To start jdb in listen mode, select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">External Process</strong></span>-><span><strong class="guimenuitem">Listen For</strong></span> from the Emacs menu bar. By default, the
JDEE prompts you to enter the address of the process to
be debugged in the minibuffer. The JDEE customization variable
jde-db-option-listen-address allows you to specify a default
debuggee address. If you set this variable, the JDEE does not
prompt you to enter an address.
</p><p>To start jdb listening for existing process via a socket,
- select Jdb->External Process->Listen Via Socket from the Emacs menu bar. By default,
+ select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">External Process</strong></span>-><span><strong class="guimenuitem">Listen Via Socket</strong></span> from the Emacs menu bar. By default,
the JDEE uses the socket address specified by
- the customization variable <tt>jde-db-option-connect-socket</tt>.
+ the customization variable <code class="varname">jde-db-option-connect-socket</code>.
If you set this variable to Prompt (nil), the JDEE
prompts you to enter a socket address in the minibuffer.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The default socket address specified by
- <tt>jde-db-option-connect-socket</tt>
+ <code class="varname">jde-db-option-connect-socket</code>
is the same as the default socket address specified
- by <tt>jde-run-option-debug</tt>. Thus, if you
+ by <code class="varname">jde-run-option-debug</code>. Thus, if you
want jdb to listen for a process started by the JDEE, the
only variable you have to set is
- <tt>jde-run-option-debug</tt>, i.e., to run
+ <code class="varname">jde-run-option-debug</code>, i.e., to run
the debuggee process in socket listen (client) mode.</p></div><p>To start jdb listening for a process via a shared memory
connection (Windows platforms only),
- select Jdb->External Process->Listen Via Shared Memory from the Emacs menu bar. By default,
+ select <span><strong class="guimenu">Jdb</strong></span>-><span><strong class="guimenuitem">External Process</strong></span>-><span><strong class="guimenuitem">Listen Via Shared Memory</strong></span> from the Emacs menu bar. By default,
the JDEE uses the shared memory transport name specified by
the customization variable
- <tt>jde-db-option-connect-shared-memory-name</tt>.
+ <code class="varname">jde-db-option-connect-shared-memory-name</code>.
If you set this variable to Prompt (nil), the JDEE
prompts you to enter a shared-memory name in the minibuffer.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The default shared memory name specified by
- <tt>jde-db-option-connect-shared-memory-name</tt>
+ <code class="varname">jde-db-option-connect-shared-memory-name</code>
is the same as the default shared memory name specified
- by <tt>jde-run-option-debug</tt>. Thus, if you
+ by <code class="varname">jde-run-option-debug</code>. Thus, if you
want jdb to listen for a process started by the JDEE, the
only variable you have to set is
- <tt>jde-run-option-debug</tt>, i.e., to run
- the debuggee process in shared memory listen (client) mode.</p></div></div><div class="sect4"><div class="titlepage"><div><h5 class="title"><a name="d0e873"></a><a name="DebugClientMode"></a>Starting the External
- Process in Debug Client Mode</h5></div></div><p>To start an external process in debug client mode, you
+ <code class="varname">jde-run-option-debug</code>, i.e., to run
+ the debuggee process in shared memory listen (client) mode.</p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="d51e873"></a><a name="DebugClientMode"></a>Starting the External
+ Process in Debug Client Mode</h5></div></div></div><p>To start an external process in debug client mode, you
must start the vm that runs the process with the following
- command-line options:</p><div class="itemizedlist"><ul type="disc"><li><p><tt>-Xdebug</tt></p></li><li><p>
- <tt>-Xrunjdwp:transport=<b>TRANSPORT</b>,address=<b>ADDRESS</b>,server=n,suspend=<b>SUSPEND</b></tt>
- </p><p>where</p><div class="itemizedlist"><ul type="round"><li><p><tt><b>TRANSPORT</b></tt> is
+ command-line options:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">-Xdebug</code></p></li><li><p>
+ <code class="literal">-Xrunjdwp:transport=<span><strong class="keycap">TRANSPORT</strong></span>,address=<span><strong class="keycap">ADDRESS</strong></span>,server=n,suspend=<span><strong class="keycap">SUSPEND</strong></span></code>
+ </p><p>where</p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal"><span><strong class="keycap">TRANSPORT</strong></span></code> is
the type of communications channel between jdb and
the debuggee process, either
- <tt>dt_socket</tt> (socket) or
- <tt>dt_shmem</tt> (shared memory, valid
- only for Windows systems)</p></li><li><p><tt><b>ADDRESS</b></tt> is
+ <code class="literal">dt_socket</code> (socket) or
+ <code class="literal">dt_shmem</code> (shared memory, valid
+ only for Windows systems)</p></li><li><p><code class="literal"><span><strong class="keycap">ADDRESS</strong></span></code> is
the address of the socket port or shared memory area
used by jdb to listen for a debuggee process
- connection.</p></li><li><p><tt><b>SUSPEND</b></tt> is
- either <tt>y</tt> (suspend the debuggee
+ connection.</p></li><li><p><code class="literal"><span><strong class="keycap">SUSPEND</strong></span></code> is
+ either <code class="literal">y</code> (suspend the debuggee
process when the connection occurs,
a useful option when you need to debug an
- application's startup code) or <tt>n</tt>
- (do not suspend the debuggee process)</p></li></ul></div></li></ul></div><div class="example"><p><b>Example 3. Specifying Socket Transport</b></p><p><tt>-Xdebug
- -Xrunjdwp:transport=dt_socket,address=4444,server=n,suspend=n</tt></p></div><div class="example"><p><b>Example 4. Specifying Shared Memory Transport (MS Windows only)</b></p><p><tt>-Xdebug
- -Xrunjdwp:transport=dt_shmem,address=javadebug,server=n,suspend=n</tt></p></div><p>The JDEE customization variable, <tt>jde-run-option-debug</tt>, causes
+ application's startup code) or <code class="literal">n</code>
+ (do not suspend the debuggee process)</p></li></ul></div></li></ul></div><div class="example"><a name="d51e931"></a><p class="title"><b>Example 3. Specifying Socket Transport</b></p><p><code class="literal">-Xdebug
+ -Xrunjdwp:transport=dt_socket,address=4444,server=n,suspend=n</code></p></div><div class="example"><a name="d51e937"></a><p class="title"><b>Example 4. Specifying Shared Memory Transport (MS Windows only)</b></p><p><code class="literal">-Xdebug
+ -Xrunjdwp:transport=dt_shmem,address=javadebug,server=n,suspend=n</code></p></div><p>The JDEE customization variable, <code class="varname">jde-run-option-debug</code>, causes
the JDEE to generate these arguments automatically when launching a vm to run a Java
application. Thus, if you plan to launch the debuggee process from the JDEE, you
- should set this variable to the desired options.</p></div></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e948"></a><a name="DebugOptions"></a>Debug Options</h2></div></div><p>The JDEE allows you to specify debug options by setting JDEE
+ should set this variable to the desired options.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e948"></a><a name="DebugOptions"></a>Debug Options</h2></div></div></div><p>The JDEE allows you to specify debug options by setting JDEE
configuration variables. You can use the Emacs customization
feature to set debug variables interactively. To use the
- customization feature, select Project->Options->Debug from the
- JDE menu. (See <a href="../jde-ug/jde-ug-content.html#ConfiguringJDE">Configuring
+ customization feature, select <span><strong class="guimenu">Project</strong></span>-><span><strong class="guimenuitem">Options</strong></span>-><span><strong class="guimenuitem">Debug</strong></span> from the
+ <span><strong class="guimenu">JDE</strong></span> menu. (See <a href="../jde-ug/jde-ug-content.html#ConfiguringJDE">Configuring
the JDEE</a> for more information on using the
customization feature). To save the compilation settings in the
project file (see <a href="../jde-ug/jde-ug-content.html#UsingProjectFiles">Using
Project Files</a> for the current source buffer, select
- Project->Project File->Save from the
- JDE menu.</p><p>The following table lists the jdb customization variables.</p><div class="table"><p><b>Table 1. Jdb Customization Variables</b></p><table summary="Jdb Customization Variables" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Variable</th><th>Group</th><th>Usage</th></tr></thead><tbody><tr><td valign="top"><tt>jde-debugger</tt></td><td valign="top">Project</td><td valign="top">Specify which debugger to use to debug the current project.</td></tr><tr><td valign="top"><tt>jde-sourcepath</tt></td><td valign="top">Project</td><td valign="top">Specify location(s) of source files that
- can be visited while stepping through a program.</td></tr><tr><td valign="top"><tt>jde-db-mode-hook</tt></td><td valign="top">Project</td><td valign="top">Customization hook for jde-db inferior
- mode.</td></tr><tr><td valign="top"><tt>jde-global-classpath</tt></td><td valign="top">Project</td><td valign="top">Specify class paths for compile, run,
- and debug commands.</td></tr><tr><td valign="top"><tt>jde-db-read-vm-args</tt></td><td valign="top">Project</td><td>Specifies whether to read debugger VM arguments from
- the minibuffer.</td></tr><tr><td valign="top"><tt>jde-db-read-app-args</tt></td><td valign="top">Project</td><td>Specifies whether to read command-line application
- arguments from the minibuffer.</td></tr><tr><td valign="top"><tt>jde-db-option-classpath</tt></td><td valign="top">Debug</td><td valign="top">Specifies the classpath for the
+ <span><strong class="guimenu">Project</strong></span>-><span><strong class="guimenuitem">Project File</strong></span>-><span><strong class="guimenuitem">Save</strong></span> from the
+ <span><strong class="guimenu">JDE</strong></span> menu.</p><p>The following table lists the jdb customization variables.</p><div class="table"><a name="d51e984"></a><p class="title"><b>Table 1. Jdb Customization Variables</b></p><table summary="Jdb Customization Variables" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Variable</th><th>Group</th><th>Usage</th></tr></thead><tbody><tr><td valign="top"><code class="varname">jde-debugger</code></td><td valign="top">Project</td><td valign="top">Specify which debugger to use to debug the current project.</td></tr><tr><td valign="top"><code class="varname">jde-sourcepath</code></td><td valign="top">Project</td><td valign="top">Specify location(s) of source files that
+ can be visited while stepping through a program.</td></tr><tr><td valign="top"><code class="varname">jde-db-mode-hook</code></td><td valign="top">Project</td><td valign="top">Customization hook for jde-db inferior
+ mode.</td></tr><tr><td valign="top"><code class="varname">jde-global-classpath</code></td><td valign="top">Project</td><td valign="top">Specify class paths for compile, run,
+ and debug commands.</td></tr><tr><td valign="top"><code class="varname">jde-db-read-vm-args</code></td><td valign="top">Project</td><td>Specifies whether to read debugger VM arguments from
+ the minibuffer.</td></tr><tr><td valign="top"><code class="varname">jde-db-read-app-args</code></td><td valign="top">Project</td><td>Specifies whether to read command-line application
+ arguments from the minibuffer.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-classpath</code></td><td valign="top">Debug</td><td valign="top">Specifies the classpath for the
Java interpreter. This option overrides the
- jde-global-classpath option.</td></tr><tr><td valign="top"><tt>jde-db-option-verbose</tt></td><td valign="top">Debug</td><td valign="top">Print messages about the running
- process.</td></tr><tr><td valign="top"><tt>jde-db-option-properties</tt></td><td valign="top">Debug</td><td valign="top">Specify property values.</td></tr><tr><td valign="top"><tt>jde-db-option-heap-size</tt></td><td valign="top">Debug</td><td valign="top">Specify the initial and maximum size of
- the interpreter heap.</td></tr><tr><td valign="top"><tt>jde-db-option-stack-size</tt></td><td valign="top">Debug</td><td valign="top">Specify size of the C and Java stacks.</td></tr><tr><td valign="top"><tt>jde-db-option-garbage-</tt><tt>collection</tt></td><td valign="top">Debug</td><td valign="top">Specify garbage collection
- options.</td></tr><tr><td valign="top"><tt>jde-db-option-java-profile</tt></td><td valign="top">Debug</td><td valign="top">Enable Java profiling.</td></tr><tr><td valign="top"><tt>jde-db-option-heap-profile</tt></td><td valign="top">Debug</td><td valign="top">Output heap profiling data.</td></tr><tr><td valign="top"><tt>jde-db-option-verify</tt></td><td valign="top">Debug</td><td valign="top">Verify classes.</td></tr><tr><td valign="top"><tt>jde-db-option-vm-args</tt></td><td valign="top">Debug</td><td valign="top">Specify command-line arguments to be
- passed to the Java VM.</td></tr><tr><td valign="top"><tt>jde-db-option-application-args</tt></td><td valign="top">Debug</td><td valign="top">Specify command-line arguments to pass
- to the application.</td></tr><tr><td valign="top"><tt>jde-db-option-connect-socket</tt></td><td valign="top">Debug</td><td valign="top">Specify socket address of a running process
+ jde-global-classpath option.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-verbose</code></td><td valign="top">Debug</td><td valign="top">Print messages about the running
+ process.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-properties</code></td><td valign="top">Debug</td><td valign="top">Specify property values.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-heap-size</code></td><td valign="top">Debug</td><td valign="top">Specify the initial and maximum size of
+ the interpreter heap.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-stack-size</code></td><td valign="top">Debug</td><td valign="top">Specify size of the C and Java stacks.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-garbage-</code>
+ <code class="varname">collection</code></td><td valign="top">Debug</td><td valign="top">Specify garbage collection
+ options.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-java-profile</code></td><td valign="top">Debug</td><td valign="top">Enable Java profiling.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-heap-profile</code></td><td valign="top">Debug</td><td valign="top">Output heap profiling data.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-verify</code></td><td valign="top">Debug</td><td valign="top">Verify classes.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-vm-args</code></td><td valign="top">Debug</td><td valign="top">Specify command-line arguments to be
+ passed to the Java VM.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-application-args</code></td><td valign="top">Debug</td><td valign="top">Specify command-line arguments to pass
+ to the application.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-connect-socket</code></td><td valign="top">Debug</td><td valign="top">Specify socket address of a running process
to which you want to connect the debugger, using a
- debugger attach or listen command.</td></tr><tr><td valign="top"><tt>jde-db-option-connect-shared-memory-name</tt></td><td valign="top">Debug</td><td valign="top">Specify shared memory name used by the debugger
- to attach or listen for debuggee processes to debug.</td></tr><tr><td valign="top"><tt>jde-db-option-host</tt></td><td valign="top">Debug</td><td valign="top">Host of a remote process to which you
+ debugger attach or listen command.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-connect-shared-memory-name</code></td><td valign="top">Debug</td><td valign="top">Specify shared memory name used by the debugger
+ to attach or listen for debuggee processes to debug.</td></tr><tr><td valign="top"><code class="varname">jde-db-option-host</code></td><td valign="top">Debug</td><td valign="top">Host of a remote process to which you
wish to attach the debugger. This option is invalid for JDK verions
greater than JDK 1.1.x.</td></tr></tbody></table></div></div></div></body></html>
1.6 +1102 -892 XEmacs/packages/xemacs-packages/jde/doc/html/jde-ug/jde-ug-content.html
Index: jde-ug-content.html
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/jde/doc/html/jde-ug/jde-ug-content.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- jde-ug-content.html 2006/03/03 20:40:42 1.5
+++ jde-ug-content.html 2007/11/26 15:16:22 1.6
@@ -1,15 +1,18 @@
<html><link rel="StyleSheet" href="../css/jde_style.css" TYPE="text/css"><head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
- <title>JDEE User's Guide</title><meta name="generator" content="DocBook XSL Stylesheets V1.49"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><h1 class="title"><a name="d0e3"></a>JDEE User's Guide</h1></div><div><p class="releaseinfo">
- <i>
- Revised for JDEE 2.3.3
- </i>
- </p></div><div><p class="copyright">Copyright © 1997, 1998, 1999, 2000, 2001, 2002, 2003 Paul Kinnucan</p></div><hr></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e32"></a><a name="Intro"></a>Introduction</h2></div></div><p>Welcome to the <span class="emphasis"><i>JDEE User's Guide</i></span>. This
+ <title>JDEE User's Guide</title><meta name="generator" content="DocBook XSL Stylesheets V1.67.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="d51e3"></a>JDEE User's Guide</h1></div><div><p class="releaseinfo">
+ <em><span class="remark">
+ Revised for JDEE <span class="productnumber">2.3.6</span>
+ </span></em>
+ </p></div><div><p class="copyright">Copyright © 1997-2005 Paul Kinnucan</p></div></div><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e36"></a><a name="Intro"></a>Introduction</h2></div></div></div><p>Welcome to the <span class="emphasis"><em>JDEE User's Guide</em></span>. This
guide explains how to use the JDEE to develop Java applications and
applets. The guide assumes that you are familiar with Emacs, the
- Java programming language, and the Java development tools provided
- with the Java Development Kit (JDK) from Sun Microsystems,
- Inc. and compatible tools provided by other vendors.</p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e41"></a><a name="AboutJDE"></a>About the JDEE</h4></div></div><p>The Java Development Environment for Emacs (JDEE) is an
+ Java programming language, and Java development tools provided
+ by Sun Microsystems, Inc.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+ This guide and the JDEE user interface use the term "JDK" to
+ refer to Sun's Java 2 Software Development Kit (SDK) and its
+ predecessors.
+ </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e48"></a><a name="AboutJDE"></a>About the JDEE</h4></div></div></div><p>The Java Development Environment for Emacs (JDEE) is an
Emacs Lisp package that interfaces Emacs to third-party Java
application development tools, such as those provided by Sun
Microsystems as part of its JDK. The result is an integrated
@@ -39,7 +42,7 @@
easily and infinitely customizable
</p></li><li><p>
works with FSF Emacs and XEmacs
- </p></li></ul></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e84"></a><a name="JDERequirements"></a>JDE Requirements</h4></div></div><p>The JDE requires the following software: </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://www.gnu.org/">FSF Emacs</a> or
+ </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e91"></a><a name="JDERequirements"></a>JDE Requirements</h4></div></div></div><p>The JDE requires the following software: </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://www.gnu.org/">FSF Emacs</a> or
<a href="http://www.xemacs.org/">XEmacs</a> on Unix
platforms; the 20.6.1 version (or later) of
<a href="ftp://ftp.gnu.org/gnu/windows/emacs/latest">NT/Emacs</a> on
@@ -53,88 +56,88 @@
Web browser (e.g., Netscape or Internet Explorer) for
viewing documentation.
</p></li><li><p>
- latest versions of Eric Ludlam's speedbar,
- semantic, and
- eieio packages available for download from
+ latest versions of Eric Ludlam's <span class="symbol">speedbar</span>,
+ <span class="symbol">semantic</span>, and
+ <span class="symbol">eieio</span> packages available for download from
<a href="http://cedet.sourceforge.net">the CDET home page</a>
</p></li><li><p>
The elib package available from the
<a href="http://jdee.sunsite.dk">JDE web site</a>
</p></li><li><p>
- <b>bash</b> or another Unix-style shell highly
+ <code class="command">bash</code> or another Unix-style shell highly
recommended for Windows95/NT environments. The <a href="http://sources.redhat.com/cygwin">cygwin</a>
Unix emulation package for Windows from Red Hat includes
- <b>bash</b>.
- </p></li></ul></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e144"></a><a name="JDEComponents"></a>JDEE Components</h4></div></div><p>
+ <code class="command">bash</code>.
+ </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e151"></a><a name="JDEComponents"></a>JDEE Components</h4></div></div></div><p>
The JDEE distribution includes the following files:
</p><div class="itemizedlist"><ul type="disc"><li><p>
- <a href="../../../lisp/jde.el"><tt>jde.el</tt></a>.
+ <a href="../../../lisp/jde.el"><code class="filename">jde.el</code></a>.
Defines jde-mode, a major Emacs mode for developing Java code.
</p></li><li><p>
- <a href="../../../lisp/jde-run.el"><tt>jde-run.el</tt></a>.
+ <a href="../../../lisp/jde-run.el"><code class="filename">jde-run.el</code></a>.
Runs Java applications and applets
</p></li><li><p>
- <a href="../../../lisp/jde-db.el"><tt>jde-db.el</tt></a>.
- Interfaces Emacs to <b>jdb</b>, the command-line debugger that
+ <a href="../../../lisp/jde-db.el"><code class="filename">jde-db.el</code></a>.
+ Interfaces Emacs to <code class="command">jdb</code>, the command-line debugger that
comes with the JDK.
</p></li><li><p>
- <a href="../../../lisp/jde-gen.el"><tt>jde-gen.el</tt></a>.
+ <a href="../../../lisp/jde-gen.el"><code class="filename">jde-gen.el</code></a>.
Contains code generation templates.
</p></li><li><p>
- <tt>bsh.jar</tt>. Compiled files for the
+ <code class="filename">bsh.jar</code>. Compiled files for the
<a href="http://www.beanshell.org/">BeanShell</a>,
a Java source code interpreter developed by Pat Neimeyer.
</p></li><li><p>
- <a href="../../../lisp/beanshell.el"><tt>beanshell.el</tt></a>.
+ <a href="../../../lisp/beanshell.el"><code class="filename">beanshell.el</code></a>.
Provides an Emacs interface to the BeanShell interpreter.
</p></li><li><p>
- <a href="../../../lisp/jde-wiz.el"><tt>jde-wiz.el</tt></a>.
+ <a href="../../../lisp/jde-wiz.el"><code class="filename">jde-wiz.el</code></a>.
Provides "wizards" that generate skeleton
implementations of interfaces and skeleton overrides of
methods declared by superclasses.
</p></li><li><p>
- <a href="../../../lisp/jde-complete.el"><tt>jde-complete.el</tt></a>.
+ <a href="../../../lisp/jde-complete.el"><code class="filename">jde-complete.el</code></a>.
Automatic field and method completion package.
</p></li><li><p>
- <a href="../../../lisp/jde-parse.el"><tt>jde-parse.el</tt></a>.
+ <a href="../../../lisp/jde-parse.el"><code class="filename">jde-parse.el</code></a>.
Java parser package.</p></li><li><p>
- <a href="../../../lisp/java.bnf"><tt>java.bnf</tt></a>.
+ <a href="../../../lisp/java.bnf"><code class="filename">java.bnf</code></a>.
Java grammar used to generate the JDE's lisp-based Java parser.
</p></li><li><p>
- <a href="../../../lisp/jde-bug.el"><tt>jde-bug.el
- </tt></a>.
+ <a href="../../../lisp/jde-bug.el"><code class="filename">jde-bug.el
+ </code></a>.
JDEbug user interface package.
</p></li><li><p>
- <a href="../../../lisp/jde-dbs.el"><tt>jde-dbs.el</tt></a>.
+ <a href="../../../lisp/jde-dbs.el"><code class="filename">jde-dbs.el</code></a>.
JDEbug low-level command interface package.
</p></li><li><p>
- <a href="../../../lisp/jde-dbo.el"><tt>jde-dbo.el</tt></a>.
+ <a href="../../../lisp/jde-dbo.el"><code class="filename">jde-dbo.el</code></a>.
JDEbug output processing functions.
</p></li><li><p>
source code, jar files, and documentation for the <a href="../../java/">Java components</a> of the
- JDE.</p></li><li><p><a href="../../../lisp/jtags"><tt>jtags</tt></a>
+ JDE.</p></li><li><p><a href="../../../lisp/jtags"><code class="filename">jtags</code></a>
is a bash shell script that tags Java source hierarchies.
</p></li><li><p>
- <a href="../../../lisp/jtags.csh"><tt>jtags.csh</tt></a>
+ <a href="../../../lisp/jtags.csh"><code class="filename">jtags.csh</code></a>
is a c shell script that tags Java source heierarchies.
- </p></li></ul></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e266"></a><a name="LatestVersion"></a>Latest Version</h4></div></div><p>See <a href="http://jdee.sunsite.dk/rootpage.html#Downloading">
+ </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e273"></a><a name="LatestVersion"></a>Latest Version</h4></div></div></div><p>See <a href="http://jdee.sunsite.dk/rootpage.html#Downloading">
Downloading the JDE</a> on the JDE website for instructions on
downloading the most recent version of the JDE.
- </p></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e275"></a><a name="InstallingJDE"></a>Installing the JDE</h4></div></div><p>See the <a href="http://jdee.sunsite.dk/install.html">
+ </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e282"></a><a name="InstallingJDE"></a>Installing the JDE</h4></div></div></div><p>See the <a href="http://jdee.sunsite.dk/install.html">
JDE Installation Guide</a> on the JDE website for information
- on installing the JDE on your system.</p></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e284"></a><a name="ContactingAuthor"></a>Contacting the Author</h4></div></div><p>Please send bug reports and enhancement suggestions to
- <a href="mailto:pkinnucan at attbi.com">Paul Kinnucan</a>.
- </p></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e293"></a><a name="RegisterSelectJDK"></a>Registering and Selecting a JDK</h2></div></div><p>The JDEE relies on command-line Java development tools, such
- as those supplied by Sun Microsystems as part of its Java
+ on installing the JDE on your system.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e291"></a><a name="ContactingAuthor"></a>Contacting the Author</h4></div></div></div><p>Please send bug reports and enhancement suggestions to
+ <a href="mailto:pkinnucan at comcast.net">Paul Kinnucan</a>.
+ </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e300"></a><a name="RegisterSelectJDK"></a>Registering and Selecting a JDK</h2></div></div></div><p>The JDEE relies on command-line Java development tools, such
+ as those supplied by Sun Microsystems as part of its Java 2
Software Development Kit (SDK) also known as a Java Development
Kit (JDK). Before you can use the JDEE to compile, debug, or run
an application, you must tell it where the Java compiler,
debugger, and virtual machine are located on your system. The
JDEE assumes that the compiler, debugger, and vm are named
- <tt>javac</tt>, <tt>jdb</tt>, and
- <tt>java</tt>, respectively, and that they are
+ <code class="filename">javac</code>, <code class="filename">jdb</code>, and
+ <code class="filename">java</code>, respectively, and that they are
located on your system's command path. If these tools are not
located on the system command path or have different names, you
must tell the JDEE where they are located. The JDEE provides
@@ -150,248 +153,251 @@
to change JDKs by changing a single customization variable. The
following sections explain how to register and select
JDKs.
- </p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e310"></a><a name="RegisterJDK"></a>Registering a JDK</h4></div></div><p>To register a version of the JDK with the JDEE:</p><div class="orderedlist"><ol type="1"><li><p>Start Emacs.</p></li><li><p>Type <b>M-x customize-variable</b> and
- press <b>Enter</b></p><p>Emacs prompts you to enter the name of a variable
- to customize.</p></li><li><p>Enter <tt>jde-jdk-registry</tt> and
- press <b>Enter</b>.</p><p>The <tt>jde-jdk-registry</tt> customization
- buffer appears.</p><div class="screenshot"><div class="mediaobject"><img src="images/regjdk1.gif"></div></div></li><li><p>Click the <b>INS</b> button.</p><p>The entry for the JDK appears.</p><div class="screenshot"><div class="mediaobject"><img src="images/regjdk2.gif"></div></div></li><li><p>Enter the version number of the JDK and the path of the directory
+ </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e317"></a><a name="RegisterJDK"></a>Registering a JDK</h4></div></div></div><p>To register a version of the JDK with the JDEE:</p><div class="orderedlist"><ol type="1"><li><p>Start Emacs.</p></li><li><p>Type <code class="command">M-x customize-variable</code> and
+ press <code class="command">Enter</code></p><p>Emacs prompts you to enter the name of a variable
+ to customize.</p></li><li><p>Enter <code class="varname">jde-jdk-registry</code> and
+ press <code class="command">Enter</code>.</p><p>The <code class="varname">jde-jdk-registry</code> customization
+ buffer appears.</p><div class="screenshot"><div class="mediaobject"><img src="images/regjdk1.gif"></div></div></li><li><p>Click the <code class="command">INS</code> button.</p><p>The entry for the JDK appears.</p><div class="screenshot"><div class="mediaobject"><img src="images/regjdk2.gif"></div></div></li><li><p>Enter the version number of the JDK and the path of the directory
in which the JDK is installed.</p></li><li><p>Repeat the preceding steps until you have entered the versions and
- paths of all versions of the JDK that you wish to use with the JDEE.</p><div class="screenshot"><div class="mediaobject"><img src="images/regjdk3.gif"></div></div></li><li><p>Click the <b>State</b> button.</p><p>The <b>State</b> menu appears.</p></li><li><p>Select <b>Save for Future Sessions</b> from
- the <b>State</b> menu.</p></li><li><p>Click the <b>Finish</b> button to dismiss
- the customization buffer.</p></li></ol></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e396"></a><a name="SelectingJDK"></a>Selecting a JDK</h4></div></div><p>To select a JDK:</p><div class="orderedlist"><ol type="1"><li><p>Type <b>M-x customize-variable</b> and
- press <b>Enter</b></p><p>Emacs prompts you to enter the name of a variable
- to customize.</p></li><li><p>Enter <tt>jde-jdk</tt> and
- press <b>Enter</b>.</p><p>The <tt>jde-jdk</tt> customization
+ paths of all versions of the JDK that you wish to use with the JDEE.</p><div class="screenshot"><div class="mediaobject"><img src="images/regjdk3.gif"></div></div></li><li><p>Click the <code class="command">State</code> button.</p><p>The <code class="command">State</code> menu appears.</p></li><li><p>Select <code class="command">Save for Future Sessions</code> from
+ the <code class="command">State</code> menu.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This saves the setting of <code class="varname">jde-jdk-registry</code>
+ in your <code class="filename">.emacs</code> file.</p></div></li><li><p>Click the <code class="command">Finish</code> button to dismiss
+ the customization buffer.</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e412"></a><a name="SelectingJDK"></a>Selecting a JDK</h4></div></div></div><p>To select a JDK:</p><div class="orderedlist"><ol type="1"><li><p>Type <code class="command">M-x customize-variable</code> and
+ press <code class="command">Enter</code></p><p>Emacs prompts you to enter the name of a variable
+ to customize.</p></li><li><p>Enter <code class="varname">jde-jdk</code> and
+ press <code class="command">Enter</code>.</p><p>The <code class="varname">jde-jdk</code> customization
buffer appears.</p><div class="screenshot"><div class="mediaobject"><img src="images/seljdk1.gif"></div></div><p>The buffer lists the JDKs that you have previously registered
(see <a href="#RegisterJDK">Registering a JDK</a>).</p></li><li><p>Click the radio button next to the version of the JDK you
- want to use.</p></li><li><p>Click the <b>State</b> button.</p><p>The <b>State</b> menu appears.</p></li><li><p>Select <b>Save for Future Sessions</b> from
- the <b>State</b> menu.</p></li><li><p>Click the <b>Finish</b> button to dismiss
+ want to use.</p></li><li><p>Click the <code class="command">State</code> button.</p><p>The <code class="command">State</code> menu appears.</p></li><li><p>Select <code class="command">Save for Future Sessions</code> from
+ the <code class="command">State</code> menu.</p></li><li><p>Click the <code class="command">Finish</code> button to dismiss
the customization buffer.</p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This procedure saves your JDK selection in your
- <tt>.emacs</tt> file so that it applies to all
+ <code class="filename">.emacs</code> file so that it applies to all
projects. You can configure the JDEE to use different JDKs
for different projects by saving your customization in a
project file. See <a href="#UsingProjectFiles">Using
- Project Files</a> or more information.</p></div></div></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e474"></a><a name="EditingJavaSourceFiles"></a>Editing Java Source Files</h2></div></div><p>
+ Project Files</a> or more information.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e490"></a><a name="EditingJavaSourceFiles"></a>Editing Java Source Files</h2></div></div></div><p>
To edit an existing Java source file, load it into an Emacs
- buffer by executing <b>C-x C-f</b>. Loading a Java source file
- into a buffer causes the buffer to enter into <tt>jde-mode</tt>,
- a variant of <tt>java-mode</tt>, which is in turn a variant of
- the standard Emacs <tt>cc-mode</tt> for editing source files
- written in C and related languages. <tt>jde-mode</tt> offers all the
- specialized source file editing commands of <tt>cc-mode</tt> plus
+ buffer by executing <code class="command">C-x C-f</code>. Loading a Java source file
+ into a buffer causes the buffer to enter into <code class="function">jde-mode</code>,
+ a variant of <code class="function">java-mode</code>, which is in turn a variant of
+ the standard Emacs <code class="function">cc-mode</code> for editing source files
+ written in C and related languages. <code class="function">jde-mode</code> offers all the
+ specialized source file editing commands of <code class="function">cc-mode</code> plus
functions for creating, compiling, building, running, and debugging Java source files.
- You can invoke the commands by selecting them from the JDE
- menu that <tt>jde-mode</tt> displays on the Emacs menu bar or by
+ You can invoke the commands by selecting them from the <span><strong class="guimenu">JDE</strong></span>
+ menu that <code class="function">jde-mode</code> displays on the Emacs menu bar or by
typing the commands in the Emacs minibuffer.
</p><p>
- </p><div class="screenshot"><div class="mediaobject"><img src="images/jdemenu.gif" height="350" width="544" alt="Screenshot showing the JDE menu."></div></div><p>
- </p></div><div class="chapter"><div class="titlepage"><div><h2 class="title"><a name="d0e514"></a><a name="DocumentingCode"></a>Documenting Code</h2></div></div><p>
+ </p><div class="screenshot"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="544"><tr style="height: 350px"><td><img src="images/jdemenu.gif" height="350" alt="Screenshot showing the JDE menu."></td></tr></table></div></div><p>
+ </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d51e530"></a><a name="DocumentingCode"></a>Documenting Code</h2></div></div></div><p>
The JDE provides complete support for generating HTML
documentation for Java classes from comments inserted into the
source code for those classes.
</p><p>See also</p><p><a href="#DisplayingDoc">Displaying Java
- Documentation</a></p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e525"></a><a name="InsertingComments"></a>Inserting Javadoc
- Comments</h4></div></div><p>
+ Documentation</a></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e541"></a><a name="InsertingComments"></a>Inserting Javadoc
+ Comments</h4></div></div></div><p>
To insert a skeleton javadoc comment for a class or method,
position point in the first line of the method or class and
- select JDE->Document from the
- Emacs menubar or type <b>C-c C-v j</b>.
+ select <span><strong class="guimenuitem">JDE->Document</strong></span> from the
+ Emacs menubar or type <code class="command">C-c C-v j</code>.
</p><p>
To customize the javadoc skeletons, select
- JDE->Options->Project->Javadoc
+ <span><strong class="guimenuitem">JDE->Options->Project->Javadoc</strong></span>
from the Emacs menubar.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Thanks...</h3><p>
to <a href="mailto:david at dponce.com">David Ponce</a>
for developing the JDE's javadoc comment generation
facility.
- </p></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="d0e550"></a><a name="GeneratingJavadoc"></a>Generating the
- Documentation</h4></div></div><p>
+ </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d51e566"></a><a name="GeneratingJavadoc"></a>Generating the
+ Documentation</h4></div></div></div><p>
To generate documentation for the current project, open any
- source file in the project and select Make
- Doc from the JDE menu or
- enter <b>M-x jde-javadoc-make</b>.
+ source file in the project and select <span><strong class="guimenuitem">Make
+ Doc</strong></span> from the <span><strong class="guimenu">JDE</strong></span> menu or
+ enter <code class="command">M-x jde-javadoc-make</code>.
</p><p>
- The <b>jde-javadoc-make</b> command runs the JDK's
+ The <code class="command">jde-javadoc-make</code> command runs the JDK's
javadoc program to generate the documentation. The
- <b>javadoc</b> command must be on your system's
+ <code class="command">javadoc</code> command must be on your s