|
71 | 71 | <section id="gs-requirements"> |
72 | 72 | <title>System Requirements</title> |
73 | 73 | <para>DrJava requires Java version 5 or later. Note that you will need to have the JDK (not the JRE) installed if you wish to use the debugger or create Javadoc within DrJava.</para> |
74 | | - <para>We recommend downloading and using Sun's JDK 6 (from <ulink url="http://java.sun.com">http://java.sun.com</ulink>) for Solaris, Linux, and Windows. Other users should use the Java virtual machine that comes with their operating system (including Mac OS X).</para> |
| 74 | + <para>We recommend downloading and using Oracle's JDK 6 (from <ulink url="http://www.oracle.com/technetwork/java/javase/downloads/index.html">http://www.oracle.com/technetwork/java/javase/downloads/index.html</ulink>) for Solaris, Linux, and Windows. Other users should use the Java virtual machine that comes with their operating system (including Mac OS X).</para> |
| 75 | + <para>Mac OS X 10.7 "Lion" does not include a default Java runtime anymore. Therefore, the operating system may prompt you to install Java if you have not installed it before. You can also download <ulink url="http://support.apple.com/kb/DL1421">Java for OS X Lion</ulink> from Apple's website, or <ulink url="http://support.apple.com/kb/index?page=search&fac=Downloads&q=java%20for%20os%20x&src=support_site.kbase.search.advanced">search for Java downloads for Mac OS X</ulink>.</para> |
75 | 76 | <para>DrJava uses two Java Virtual Machines (one for the main program, and one for the Interactions Pane) that use Java's Remote Method Invocation (RMI) to communicate with each other. RMI uses TCP/IP as the default transport mechanism, so you must have those drivers installed. Without TCP/IP, DrJava will not start properly.</para> |
76 | 77 | <para>Note that there is an incompatibility between Java's Swing |
77 | 78 | GUI library and the Compiz window manager on Linux. We, the developers |
78 | 79 | of DrJava, cannot do anything to fix this problem. We hope that future |
79 | 80 | versions of Java and Compiz will address the incompatibility. In the |
80 | 81 | meantime, we recommend that you disable Compiz if you experience |
81 | 82 | problems. We also suggest that you use the latest versions of Compiz |
82 | | -and Java, so you can benefit from possible bug fixes made by Sun and |
| 83 | +and Java, so you can benefit from possible bug fixes made by Oracle and |
83 | 84 | the Compiz developers. For more information, see <ulink url="http://drjava.org/compiz/">http://drjava.org/compiz/</ulink>.</para> |
84 | 85 | </section> |
85 | 86 |
|
@@ -957,9 +958,9 @@ can be compiled by the regular Java compiler.</para> |
957 | 958 | <!-- Chapter: Javadoc Integration --> |
958 | 959 | <chapter id="javadoc"> |
959 | 960 | <title>Documentation with Javadoc</title> |
960 | | - <para>Documenting your code is crucial to help others understand it, and even to remind yourself how your own older programs work. Unfortunately, it is easy for most external documentation to become out of date as a program changes. For this reason, it is useful to write documentation as comments in the code itself, where they can be easily updated with other changes. Javadoc is a documentation tool which defines a standard format for such comments, and which can generate HTML files to view the documentation from a web broswer. (As an example, see Sun's Javadoc documentation for the Java libraries at <ulink url="http://java.sun.com/j2se/1.4/docs/api/index.html">http://java.sun.com/j2se/1.4/docs/api/index.html</ulink>.)</para> |
| 961 | + <para>Documenting your code is crucial to help others understand it, and even to remind yourself how your own older programs work. Unfortunately, it is easy for most external documentation to become out of date as a program changes. For this reason, it is useful to write documentation as comments in the code itself, where they can be easily updated with other changes. Javadoc is a documentation tool which defines a standard format for such comments, and which can generate HTML files to view the documentation from a web broswer. (As an example, see Oracle's Javadoc documentation for the Java libraries at <ulink url="http://download.oracle.com/javase/6/docs/api/">http://download.oracle.com/javase/6/docs/api/</ulink>.)</para> |
961 | 962 |
|
962 | | - <para>You can easily run Javadoc over your programs from within DrJava, using the "Javadoc All Documents" and "Preview Javadoc for Current Document" commands in the Tools menu. These commands will generate Javadoc HTML files from the comments you have written and display them in a browser. This chapter gives a brief overview of these commands and how to write Javadoc comments. More detailed information on writing Javadoc comments can be found online at <ulink url="http://java.sun.com/j2se/javadoc/writingdoccomments/">http://java.sun.com/j2se/javadoc/writingdoccomments/</ulink>.</para> |
| 963 | + <para>You can easily run Javadoc over your programs from within DrJava, using the "Javadoc All Documents" and "Preview Javadoc for Current Document" commands in the Tools menu. These commands will generate Javadoc HTML files from the comments you have written and display them in a browser. This chapter gives a brief overview of these commands and how to write Javadoc comments. More detailed information on writing Javadoc comments can be found online at <ulink url="http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html">http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html</ulink>.</para> |
963 | 964 |
|
964 | 965 |
|
965 | 966 | <section id="javadoc-writing"> |
@@ -1034,7 +1035,7 @@ public class Student { |
1034 | 1035 |
|
1035 | 1036 | <formalpara> |
1036 | 1037 | <title>Configuring Javadoc</title> |
1037 | | - <para>You can configure many aspects of how Javadoc files are generated. Most prominent is the ability to hide fields and methods below a particular access level (eg. <literal>public</literal> or <literal>protected</literal>). By default, no private fields or methods are shown. Other options include specifying a URL to link to the Java library API (which defaults to Sun's own website), specifying a default destination directory for all Javadoc files, and specifying any custom parameters to pass to the Javadoc tool itself. Finally, for programs with many nested packages (folders), DrJava provides an option to always generate Javadoc for all packages in the program, rather than just the sub-packages of the open documents.</para> |
| 1038 | + <para>You can configure many aspects of how Javadoc files are generated. Most prominent is the ability to hide fields and methods below a particular access level (eg. <literal>public</literal> or <literal>protected</literal>). By default, no private fields or methods are shown. Other options include specifying a URL to link to the Java library API (which defaults to Oracle's own website), specifying a default destination directory for all Javadoc files, and specifying any custom parameters to pass to the Javadoc tool itself. Finally, for programs with many nested packages (folders), DrJava provides an option to always generate Javadoc for all packages in the program, rather than just the sub-packages of the open documents.</para> |
1038 | 1039 | </formalpara> |
1039 | 1040 |
|
1040 | 1041 | </section> |
@@ -1168,13 +1169,13 @@ pane (see <link linkend="configuration">Configuring DrJava</link>).</para> |
1168 | 1169 | <section id="other-dialogs-compiz"> |
1169 | 1170 | <title>Compiz Detected</title> |
1170 | 1171 | <para>DrJava suffers from an incompatibility between the Linux |
1171 | | -window manager Compiz and Sun's Swing Java GUI library. We, the |
| 1172 | +window manager Compiz and Oracle's Swing Java GUI library. We, the |
1172 | 1173 | developers of DrJava, cannot do anything to fix this problem. We hope |
1173 | 1174 | that future versions of Java and Compiz will address the |
1174 | 1175 | incompatibility. In the meantime, we recommend that you disable Compiz |
1175 | 1176 | if you experience problems. We also suggest that you use the latest |
1176 | 1177 | versions of Compiz and Java, so you can benefit from possible bug |
1177 | | -fixes made by Sun and the Compiz developers. For more information, see |
| 1178 | +fixes made by Oracle and the Compiz developers. For more information, see |
1178 | 1179 | <ulink |
1179 | 1180 | url="http://drjava.org/compiz/">http://drjava.org/compiz/</ulink>.</para> |
1180 | 1181 | <para>When DrJava detects that you are using Compiz, it will |
@@ -2105,13 +2106,13 @@ to.</para> |
2105 | 2106 | <listitem> |
2106 | 2107 | <para>Whether DrJava should warn the user if Compiz is |
2107 | 2108 | detected (see <link linkend="other-dialogs-compiz">Compiz Detected</link> dialog). DrJava suffers from an incompatibility between the Linux |
2108 | | -window manager Compiz and Sun's Swing Java GUI library. We, the |
| 2109 | +window manager Compiz and Oracle's Swing Java GUI library. We, the |
2109 | 2110 | developers of DrJava, cannot do anything to fix this problem. We hope |
2110 | 2111 | that future versions of Java and Compiz will address the |
2111 | 2112 | incompatibility. In the meantime, we recommend that you disable Compiz |
2112 | 2113 | if you experience problems. We also suggest that you use the latest |
2113 | 2114 | versions of Compiz and Java, so you can benefit from possible bug |
2114 | | -fixes made by Sun and the Compiz developers. For more information, see |
| 2115 | +fixes made by Oracle and the Compiz developers. For more information, see |
2115 | 2116 | <ulink |
2116 | 2117 | url="http://drjava.org/compiz/">http://drjava.org/compiz/</ulink>.</para> |
2117 | 2118 | </listitem> |
|
0 commit comments