/[gentoo]/xml/htdocs/doc/en/java.xml
Gentoo

Diff of /xml/htdocs/doc/en/java.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.22 Revision 1.29
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/java.xml,v 1.22 2006/03/06 17:46:45 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/java.xml,v 1.29 2006/08/09 20:44:33 rane Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/java.xml"> 5<guide link="/doc/en/java.xml">
6<title>Gentoo Java Guide</title> 6<title>Gentoo Java Guide</title>
7 7
8<author title="Author and Editor"> 8<author title="Author">
9 <mail link="nichoj@gentoo.org">Joshua Nichols</mail>
10</author>
11<author title="Author">
9 <mail link="karltk@gentoo.org">Karl Trygve Kalleberg</mail> 12 <mail link="karltk@gentoo.org">Karl Trygve Kalleberg</mail>
10</author> 13</author>
11<author title="Editor"> 14<author title="Editor">
12 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 15 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
13</author> 16</author>
14<author title="Editor">
15 <mail link="vanquirius@gentoo.org">Marcelo Góes</mail>
16</author>
17 17
18<abstract> 18<abstract>
19This guide will introduce users and developers to Java and explain how to use 19This guide will introduce you to Java and explain how to use Java with Gentoo
20Java with Gentoo Linux. 20Linux.
21</abstract> 21</abstract>
22 22
23<!-- The content of this document is licensed under the CC-BY-SA license -->
24<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
23<license/> 25<license/>
24 26
25<version>0.3</version> 27<version>0.7</version>
26<date>2005-12-12</date> 28<date>2006-08-08</date>
27 29
28<chapter> 30<chapter>
29<title>What is Java?</title> 31<title>What is Java?</title>
30<section> 32<section>
31<title>Overview</title> 33<title>Overview</title>
32<body> 34<body>
33 35
34<p> 36<p>
35Java is a programming language developed by engineers of Sun Microsystems. 37Java is a programming language developed by engineers of Sun Microsystems. The
36The language is object-oriented and designed to run on multiple platforms 38language is object-oriented and designed to run on multiple platforms without
37without the need of recompiling code for each platform. Although Java can 39the need of recompiling code for each platform. Although Java can be compiled
38be compiled as a native program, much of Java's popularity can be attributed 40as a native program, much of Java's popularity can be attributed to its
39to its portability, along with other features such as garbage collection. 41portability, along with other features such as garbage collection. To make
40The ability to compile once and run in various platforms is achieved through 42platform independence possible the Java compiler compiles the Java code to an
41the use of just-in-time compilers (JIT), which compile Java bytecodes into 43intermediate representation called "Java bytecode" that runs on a JRE (Java
42native code when a given program is run. 44Runtime Environment) and not directly on the operating system.
43</p>
44
45<p> 45</p>
46
47<p>
46In order to run Java bytecodes, one needs to have a JRE (Java Runtime Environment) 48In order to run Java bytecode, one needs to have a JRE (Java Runtime
47installed. A JRE provides core libraries, a platform dependent Java Virtual Machine, 49Environment) installed. A JRE provides core libraries, a platform dependent
48plug-ins for browsers, among other things. A JDK (Java Development Kit) adds 50Java Virtual Machine, plug-ins for browsers, among other things. A JDK (Java
49programming tools, such as a bytecode compiler and a debugger. 51Development Kit) adds programming tools, such as a bytecode compiler and a
52debugger.
50</p> 53</p>
51 54
52</body> 55</body>
53</section> 56</section>
54</chapter>
55
56<chapter> 57</chapter>
57<title>Installing a JRE/JDK</title> 58
59<chapter>
60<title>New Java System</title>
61<section>
62<body>
63
64<p>
65The way Java is handled on Gentoo has recently seen many changes and
66improvements. This has only happened very recently, and as a result, all the
67packages related to it are marked with testing keywords, ie ~x86. This
68document assumes you are using the new system.
69</p>
70
71</body>
72</section>
73<section>
74<title>Keywords</title>
75<body>
76
77<p>
78If you are using the stable tree, i.e. x86, ppc, or amd64 as opposed to ~x86,
79~ppc, or ~amd64, you will need to add some entries to your
80<path>/etc/portage/package.keywords</path>:
81</p>
82
83<pre caption="package.keywords">
84# Core Gentoo/Java Packages
85dev-java/ant-core
86dev-java/ant-tasks
87dev-java/ant
88dev-java/java-config
89dev-java/java-config-wrapper
90dev-java/javatoolkit
91dev-java/sun-jce-bin
92# JDKs
93=dev-java/sun-jdk-1.4*
94=dev-java/sun-jdk-1.5*
95=dev-java/ibm-jdk-bin-1.4*
96=dev-java/ibm-jdk-bin-1.5*
97=dev-java/jrockit-jdk-bin-1.4*
98=dev-java/jrockit-jdk-bin-1.5*
99=dev-java/blackdown-jdk-1.4*
100dev-java/kaffe
101# JREs
102=dev-java/sun-jre-bin-1.4*
103=dev-java/sun-jre-bin-1.5*
104=dev-java/ibm-jre-bin-1.4*
105=dev-java/blackdown-jre-1.4*
106# Virtuals
107virtual/jdk
108virtual/jre
109# Compilers
110dev-java/eclipse-ecj
111dev-java/jikes
112# Documentation
113dev-java/java-sdk-docs
114# Misc packages that have been updated to generation-2,
115# where the generation-1 won't build and/or run properly
116dev-java/lucene
117# These have optional Java support, but need ~arch to function properly
118# with generation-2
119dev-util/subversion
120sys-libs/db
121</pre>
122
123<impo>
124It is crucial that you keyword ALL packages related to the new Java system,
125otherwise you will have problems in the later steps of this guide.
126</impo>
127
128<impo>
129It can't be emphasized enough that you have to have ALL the packages related
130to the new Java system keyworded for it to function properly.
131</impo>
132
133</body>
134</section>
135<section>
136<title>Existing installs</title>
137<body>
138
139<p>
140For existing installs, regardless of if you have installed anything Java
141before, make sure you have followed the <uri
142link="/proj/en/java/java-upgrade.xml">Java Upgrade Guide</uri>.
143</p>
144
145</body>
146</section>
147<section>
148<title>New installs</title>
149<body>
150
151<p>
152New installs should require no further preparation.
153</p>
154
155</body>
156</section>
157</chapter>
158
159<chapter>
160<title>Installing a Virtual Machine</title>
58<section> 161<section>
59<title>The choices</title> 162<title>The choices</title>
60<body> 163<body>
61 164
62<p> 165<p>
63Gentoo provides numerous JREs and JDKs. Among the current alternatives, we have: 166Gentoo provides numerous Runtime Environments (JREs) and Development Kits
64</p> 167(JDKs). Among the current choices, we have:
65
66<ul>
67 <li>blackdown-jre and blackdown-jdk, the Blackdown Java Kit</li>
68 <li>sun-jre-bin and sun-jdk, Sun's Java Kit </li>
69 <li>ibm-jre-bin and ibm-jdk-bin, the IBM Java Kit</li>
70 <li>compaq-jre and compaq-jdk, the Compaq Java Kit for Alpha/Linux/GNU</li>
71 <li>jrockit-jdk-bin, BEA WebLogic's J2SE Development Kit</li>
72</ul>
73
74<p> 168</p>
75The default is the Blackdown JRE/JDK 169
76pair, as it is freely ("free as in beer") available without any registration 170<table>
77fuss. 171<tr>
172 <th>Vendor</th>
173 <th>JDK</th>
174 <th>JRE</th>
175</tr>
176<tr>
177 <ti>The Blackdown Java Kit</ti>
178 <ti>dev-java/blackdown-jdk</ti>
179 <ti>dev-java/blackdown-jre</ti>
180</tr>
181<tr>
182 <ti>Sun's Java Kit</ti>
183 <ti>dev-java/sun-jdk</ti>
184 <ti>dev-java/sun-jre-bin</ti>
185</tr>
186<tr>
187 <ti>The IBM Java Kit</ti>
188 <ti>dev-java/ibm-jdk-bin</ti>
189 <ti>dev-java/ibm-jre-bin</ti>
190</tr>
191<tr>
192 <ti>The Compaq Java Kit for Alpha/Linux/GNU</ti>
193 <ti>dev-java/compaq-jdk</ti>
194 <ti>dev-java/compaq-jre</ti>
195</tr>
196<tr>
197 <ti>BEA WebLogic's J2SE Development Kit</ti>
198 <ti>dev-java/jrockit-jdk-bin</ti>
199</tr>
200</table>
201
202<!--
203TODO: list free implementations?
204note about not drop-in replacements
205kaffe/sablevm/gcj/jamvm
206-->
207
78</p> 208<p>
79 209The default is Blackdown for both the JRE and the JDK, as it is freely ("free
210as in beer") available without any registration fuss.
80<p> 211</p>
81Both the Sun JRE/JDK and the IBM JRE/JDK are generally faster, but getting them 212
213<p>
214The default for Java 1.4 is the Blackdown JRE/JDK pair, as it is freely
215("free as in beer") available without any registration fuss.
216</p>
217
218<p>
219JREs and JDKs from Sun, IBM, and BEA are generally faster, but getting them
82is a bit more work, as you are required to read and accept their license before 220is a bit more work, as you are required to read and accept their license before
83downloading (IBM additionally requires you to register). 221downloading (IBM additionally requires you to register).
84</p> 222</p>
85 223
86<p>
87Our ebuilds for the Sun and IBM JRE/JDKs will notify you of where to go to
88download them.
89</p>
90
91</body> 224</body>
92</section>
93<section> 225</section>
226<section>
94<title>Installing the Sun/IBM JRE/JDKs</title> 227<title>Installing a JRE/JDKs</title>
95<body> 228<body>
96 229
230<p>
231To install your profile's default JDK, you can run <c>emerge virtual/jdk</c>.
232Or to install your profile's default JRE, you can <c>emerge virtual/jre</c>.
97<p> 233</p>
98If you run <c>emerge =sun-jdk-1.4.2.06</c> or <c>=ibm-jdk-bin-1.4.2</c>, you will 234
99be notified that you are required to download the actual tarballs yourself. This 235<p>
100has to do with license restrictions for the Sun JRE/JDK (online click-wrap 236In recent events, Sun has relicensed their JDK and JRE under a more Linux
101license) and registration issues with the IBM JRE/JDK. 237distro friendly license. As a result, Sun releases Java 1.5 and onwards are
238freely downloadable, without any further hassle.
102</p> 239</p>
103 240
104<note> 241<note>
105ibm-jdk-bin is currently masked, you may have to unmask it to use it. 242A JDK also includes a JRE, so if you install a JDK you shouldn't have to also
243have to install a JRE.
106</note> 244</note>
107 245
246</body>
247</section>
248<section>
249<title>Installing fetch-restricted virtual machines</title>
250<body>
251
252<p>
253As already mentioned, some of the JDKs and JREs require you to jump through a
254few hoops before installing. Simply emerge the packages as you normally would.
255The ebuilds will then instruct you where to go and what to download.
256</p>
257
108<p> 258<p>
109You should download the indicated file(s) into 259You should download the indicated file(s) into
110<path>/usr/portage/distfiles</path>. Once that is done, you can rerun the emerge 260<path>/usr/portage/distfiles</path>. Once there, you can rerun the emerge
111command, then the JRE/JDK will be installed properly into <path>/opt</path>. 261command, at which point the JRE/JDK will be begin to install.
112</p> 262</p>
113 263
114</body> 264</body>
115</section> 265</section>
116</chapter>
117
118<chapter> 266</chapter>
119<title>Configuring your JRE/JDK</title> 267
268<chapter>
269<title>Configuring your virtual machine</title>
120<section> 270<section>
121<title>Overview</title> 271<title>Overview</title>
122<body> 272<body>
123 273
124<p> 274<p>
125Gentoo has the ability to have multiple JDKs and JREs installed without them 275Gentoo has the ability to have multiple JDKs and JREs installed without causing
126conflicting. 276conflicts.
127</p>
128
129<p> 277</p>
278
279<p>
130Using the <c>java-config</c> tool, you can set the system-wide default if you 280Using the <c>java-config</c> tool, you can set the system-wide default
131have root access. Users can also use <c>java-config</c> to set up their own 281(provided you have root access). Users can also use <c>java-config</c> to set
132personal default, that is different from the system-wide default. 282up their own personal default.
133</p> 283</p>
134 284
135</body> 285<note>
136</section> 286You can also use <e>eselect</e> to change the system and user vm. See
287<c>eselect java-vm help</c>.
288</note>
137 289
290</body>
138<section> 291</section>
292<section>
139<title>Setting a default JRE/JDK</title> 293<title>Setting a default virtual machine</title>
140<body> 294<body>
141 295
142<p> 296<p>
143Running the command <c>java-config --list-available-vms</c> will give you a list 297Running the command <c>java-config --list-available-vms</c> will give you a
144of all available JREs and JDKs on your system. Here is an example of output: 298list of all JREs and JDKs installed on your system. Here is an example of
299output:
145</p> 300</p>
146 301
147<pre caption="Listing available VMs"> 302<pre caption="Listing available VMs">
148# <i>java-config --list-available-vms</i> 303# <i>java-config --list-available-vms</i>
149[blackdown-jdk-1.3.1] Blackdown JDK 1.3.1 (/etc/env.d/java/20blackdown-jdk-1.3.1) 3041) Blackdown JDK 1.3.1 [blackdown-jdk-1.3] (/etc/env.d/java/20blackdown-jdk-1.3)
150[blackdown-jre-1.3.1] Blackdown JRE 1.3.1 (/etc/env.d/java/20blackdown-jre-1.3.1) 3052) Blackdown JDK 1.4.2.02 [blackdown-jdk-1.4] (/etc/env.d/java/20blackdown-jdk-1.4)
151[ibm-jdk-1.3.0] IBM JDK 1.3.0 (/etc/env.d/java/20ibm-jdk-1.3.0) 3063) Blackdown JRE 1.4.2.02 [blackdown-jre-1.4] (/etc/env.d/java/20blackdown-jre-1.4)
152[ibm-jdk-1.3.1] IBM JDK 1.3.1 (/etc/env.d/java/20ibm-jdk-1.3.1) 3074) IBM JDK 1.4.2 [ibm-jdk-bin-1.4] (/etc/env.d/java/20ibm-jdk-bin-1.4)
153[ibm-jre-1.3.1] IBM JRE 1.3.1 (/etc/env.d/java/20ibm-jre-1.3.1) 3085) IBM JRE 1.4.2 [ibm-jre-bin-1.4] (/etc/env.d/java/20ibm-jre-bin-1.4)
154[sun-jdk-1.4.0] Sun JDK 1.4.0 (/etc/env.d/java/20sun-jdk-1.4.0) 3096) WebLogic JRockit 1.4.2.05 [jrockit-jdk-bin-1.4] (/etc/env.d/java/20jrockit-jdk-bin-1.4)
3107) WebLogic JRockit 1.5.0.03 [jrockit-jdk-bin-1.5] (/etc/env.d/java/20jrockit-jdk-bin-1.5)
3118) Sun JDK 1.3.1.13 [sun-jdk-1.3] (/etc/env.d/java/20sun-jdk-1.3)
3129) Sun JDK 1.4.2.09 [sun-jdk-1.4] (/etc/env.d/java/20sun-jdk-1.4)
313*) Sun JDK 1.5.0.04 [sun-jdk-1.5] (/etc/env.d/java/20sun-jdk-1.5)
31411) Sun JRE 1.4.2.09 [sun-jre-bin-1.4] (/etc/env.d/java/20sun-jre-bin-1.4)
31512) Sun JRE 1.5.0.04 [sun-jre-bin-1.5] (/etc/env.d/java/20sun-jre-bin-1.5)
155</pre> 316</pre>
156 317
157<p> 318<p>
319The <e>*</e> indicates this is the current active vm (system-vm or user-vm when
158The name in the brackets <path>"[]"</path> is the handle or ID for that 320set). The name in the brackets (<e>[]</e>) is the handle or ID for that
159particular VM. You use pass that ID to <c>java-config --set-system-vm</c>. Here is 321particular VM. You use the handle or the number to <c>java-config
160an example of how to set the system VM. 322--set-system-vm</c>. Here is an example of how to set the system VM.
161</p> 323</p>
162 324
163<pre caption="Setting the System VM"> 325<pre caption="Setting the System VM">
326<comment>(By handle (preferred))</comment>
164# <i>java-config --set-system-vm ibm-jdk-1.3.1</i> 327# <i>java-config --set-system-vm blackdown-jdk-1.4</i>
165Now using IBM JDK 1.3.1 (/etc/env.d/java/20ibm-jdk-1.3.1) 328<comment>(By number)</comment>
329# <i>java-config --set-system-vm 2</i>
330</pre>
331
332<p>
333As a regular user, you can use <c>java-config --set-user-vm</c>.
166</pre> 334</p>
167 335
168<note> 336<note>
169You will have to be root to run --set-system-vm. 337You no longer have to <c>source</c> the profile for updates to the user/system
338VM take place.
170</note> 339</note>
171 340
172<p> 341</body>
173Once you have issued <c>java-config --set-system-vm</c> with a particular VM 342</section>
174ID, you will need to regenerate your <path>/etc/profile.env</path>. You can do 343<section id="preferred-vm">
175it like this: 344<title>Preferred VM</title>
345<body>
346
176</p> 347<p>
177 348While merging Java packages, the VM can and will be switched as necessary.
178<pre caption="Regenerating /etc/profile.env" >
179# <i>env-update</i>
180</pre>
181
182<p> 349</p>
183After this, you will either want to relogin, or resource 350
184<path>/etc/profile</path> into your environment.
185</p> 351<p>
186 352Because of the wide variety of available VMs, we do not have the resources to
353test and verify every package works on all of them. So to ensure that every
354packages merges smoothly, we have defined a list of <e>default/supported
355VMs</e> per arch. You can find them in
356<path>/usr/share/java-config/config/jdk-defaults.conf</path>. When you are
357merging a Java package, and it detects one of the VM in that file is installed,
358it will automatically use that VM, instead of the system-vm.
187<p> 359</p>
188As a regular user, you can use <c>java-config --set-user-vm</c>, which will 360
189create <path>~/.gentoo/java-env</path> with all required env vars. You would
190normally source this from your shell's startup script (generally
191<path>~/.bashrc</path>).
192</p> 361<p>
362The merge time VM switching is also needed when, for example, your system-vm is
363set a 1.4 VM and the package you are merging requires a 1.5 VM. While merging
364it will use the preferred 1.5 VM, leaving your system-vm choice intact.
365</p>
366
367<p>
368Of course, Gentoo is all about choice, so you can override these defaults in
369<path>/etc/java-config-2/build/jdk.conf</path> and have complete control over
370which VM will get used. Some examples:
371</p>
372
373<pre caption="Example /etc/java-config-2/build/jdk.conf">
374<comment>(I always want it to use a sun-jdk, ie sun-jdk-1.4 for 1.4, sun-jdk-1.5 for 1.5, etc)</comment>
375*=sun-jdk
376</pre>
377
378<pre caption="Example /etc/java-config-2/build/jdk.conf">
379<comment>(Always use sun-jdk-1.5 wherever possible, except for when a 1.4 or 1.3 VM is explicitly required)</comment>
380*=sun-jdk-1.5
381</pre>
382
383<pre caption="Example /etc/java-config-2/build/jdk.conf">
384<comment># For 1.3 I prefer sun-jdk 1.4 but when it is not available, use ibm-jdk-bin,
385# For 1.4, use blackdown-jdk, and for 1.5, use sun-jdk </comment>
3861.3=sun-jdk-1.4 ibm-jdk-bin
3871.4=blackdown-jdk
3881.5=sun-jdk
389</pre>
390
391<warn>
392You do not have to edit this file. If you change these options to use a
393unsupported VM, things could possibly break. Bugs reported with a unsupported
394VM won't be prioritized as much as bugs present within supported VMs.
395</warn>
396
397</body>
398</section>
399</chapter>
400
401<chapter>
402<title>Compilers</title>
403<section>
404<body>
405
406<p>
407The standard Java compiler used for building is javac, which comes with each
408JDK. In addition to configuring the VM used at build time, it is also possible
409configure which compiler is used. Essentially, you define a list your
410preference for which compiler to use in
411<path>/etc/java-config-2/build/compilers.conf</path>.
412</p>
413
414<pre caption="/etc/java-config-2/build/compilers.conf">
415# If the ebuild supports it
416# it will check the COMPILERS var front to back and
417# use the first compiler that is installed
418
419COMPILERS="ecj-3.1 jikes javac"
420</pre>
421
422<p>
423Some compilers don't support all possible -target and -source arguments.
424Therefore, each compiler in the list is checked to see if it can support the
425desired -source/-target. javac will work in all cases, so if no other suitable
426compiler is found, it will be used instead.
427</p>
428
429<p>
430More details about each compiler are provided below:
431</p>
432
433<table>
434<tr>
435 <th>Name</th>
436 <th>Handle</th>
437 <th>Package</th>
438 <th>Description</th>
439</tr>
440<tr>
441 <ti>javac</ti>
442 <ti>javac</ti>
443 <ti>N/A</ti>
444 <ti>
445 This is the default compiler that will be used, and comes with each JDK.
446 </ti>
447</tr>
448<tr>
449 <ti>jikes</ti>
450 <ti>jikes</ti>
451 <ti>dev-java/jikes</ti>
452 <ti>
453 Jikes was originally developed by IBM. Anecdotally, it is generally quicker
454 than javac. Note however, that it is more pedantic, and will fail under a
455 few circumstances where javac has no issue. It also does not support Java
456 1.5 syntax yet.
457 </ti>
458</tr>
459<tr>
460 <ti>Eclipse Compiler for Java</ti>
461 <ti>ecj-3.1</ti>
462 <ti>=dev-java/eclipse-ecj-3.1*</ti>
463 <ti>
464 ECJ is the compiler used by the Eclipse software development kit. It is
465 very full featured, and is pretty fast. It does support Java 1.5 syntax.
466 </ti>
467</tr>
468</table>
469
470</body>
471</section>
472</chapter>
473
474<chapter>
475<title>Setting a default CLASSPATH</title>
476<section>
477<body>
478
479<warn>
480The options explained in this section should be considered deprecated and will
481most likely be removed in the future. We strongly recommend against using
482these, because your Java projects or application should ideally manage their
483own classpaths. If you choose to specify a default CLASSPATH, some applications
484may behave unexpectedly, because classes they weren't expecting would be on the
485classpath.
486</warn>
487
488<p>
489<c>java-config</c> can also be used to set a system-wide default CLASSPATH, as
490well a user-specific default CLASSPATH.
491</p>
492
493<p>
494First, you will want to list available Java libraries installed on your system
495that might want to be put in your CLASSPATH. Here is an example of output:
496</p>
497
498<pre caption="Listing classes">
499# <i>java-config --list-available-packages</i>
500[xerces-2] The next generation of high performance, fully compliant XML parsers in the Apache Xerces family (/usr/share/xerces-2/package.env)
501[junit] Simple framework to write repeatable tests (/usr/share/junit/package.env)
502[bsh] BeanShell: A small embeddable Java source interpreter (/usr/share/bsh/package.env)
503[bcel] The Byte Code Engineering Library: analyze, create, manipulate Java class files (/usr/share/bcel/package.env)
504[log4j] A low-overhead robust logging package for Java (/usr/share/log4j/package.env)
505...
506</pre>
507
508<p>
509Again, the names in brackets (<e>[]</e>) are the IDs that you have to pass to
510<c>java-config --set-system-classpath</c>. Here is an example:
511</p>
512
513<pre caption="Setting classpaths">
514# <i>java-config --set-system-classpath log4j,xerces-2</i>
515</pre>
516
517<note>
518The current directory (<path>.</path>) will not be part of the system
519classpath, as that should be added in your system's login profile.
520</note>
521
522<p>
523You will have to update your environment by logging out, then in again or
524sourcing <path>/etc/profile</path>.
525</p>
526
527<p>
528For users, <c>java-config --set-user-classpath</c> will create
529<path>~/.gentoo/java-env-classpath</path>, which you should then source from
530your shell's profile.
531</p>
532
533<pre caption="Sourcing user specific classpath">
534<i>if [[ -f "${HOME}/.gentoo/java-env-classpath" ]]; then
535 source ${HOME}/.gentoo/java-env-classpath
536fi</i>
537</pre>
538
539<p>
540If you really want a system wide or user default classpath you can add
541something like the following to your shell's profile. But we would advise
542against it.
543</p>
544
545<pre caption="Setting classpath">
546# <i>export CLASSPATH="${CLASSPATH}:$(java-config --classpath log4j,xerces-2)"</i>
547</pre>
193 548
194</body> 549</body>
195</section> 550</section>
196</chapter> 551</chapter>
197 552
212<section> 567<section>
213<title>The flags</title> 568<title>The flags</title>
214<body> 569<body>
215 570
216<ul> 571<ul>
217 <li>The <b>java</b> flag adds support for Java in a variety of programs.</li> 572 <li>The <b>java</b> flag adds support for Java in a variety of programs</li>
573 <li>
574 The <b>nsplugin</b> flag adds support for Mozilla-like browsers (including
575 Firefox).You will need this for viewing Java applets in your Mozilla-like
576 browser.
218 <li> 577 </li>
219 The <b>nsplugin</b> flag adds a symlink to the javaplugin for 578 <li>
220 Mozilla-like browsers (including Firefox) if you are using, for example, 579 The <b>doc</b> flag will typically install API documentation, as generated
221 Blackdown's Java kit, IBM Java Kit or Sun's Java Kit. You will need this 580 by javadoc.
222 for viewing Java applets in your Mozilla-like browser. 581 </li>
582 <li>
583 The <b>source</b> flag will install a zip of the package's source code.
584 This is typically used to provide your IDE with the source code for the
585 package.
586 </li>
587 <li>
588 The <b>source</b> flag installs a zip of the source code of a package.
589 This is traditionally used for for IDEs to 'attach' source to the libraries
590 you are using.
591 </li>
592 <li>
593 For Java packages, the <b>doc</b> flag will build API documentation using
594 javadoc.
223 </li> 595 </li>
224</ul> 596</ul>
225 597
226</body> 598</body>
227</section> 599</section>
234<body> 606<body>
235 607
236<ul> 608<ul>
237 <li>java-config man page</li> 609 <li>java-config man page</li>
238 <li><c>java-config --help</c></li> 610 <li><c>java-config --help</c></li>
239 <li>The <path>/usr/bin/java-config</path> script itself</li>
240</ul> 611</ul>
241 612
242</body> 613</body>
243</section> 614</section>
244<section> 615<section>
245<title>Online resources</title> 616<title>Online resources</title>
246<body> 617<body>
247 618
248<ul> 619<ul>
249 <li>The <uri link="/proj/en/java/">Gentoo Java Project Page</uri></li> 620 <li>
621 The <uri link="http://www.gentoo.org/proj/en/java/">Java Project
622 Page</uri>
623 </li>
250 <li> 624 <li>
251 The <uri 625 The <uri
252 link="http://news.gmane.org/gmane.linux.gentoo.devel">gentoo-dev</uri>,
253 <uri link="http://news.gmane.org/gmane.linux.gentoo.user">gentoo-user
254 </uri> and <uri
255 link="http://news.gmane.org/gmane.linux.gentoo.java">gentoo-java</uri> 626 link="http://news.gmane.org/gmane.linux.gentoo.java">gentoo-java</uri>,
627 <uri
628 link="http://news.gmane.org/gmane.linux.gentoo.user">gentoo-user</uri>, and
629 <uri
630 link="http://news.gmane.org/gmane.linux.gentoo.devel">gentoo-dev</uri>
256 mailing list archives 631 mailing list archives
257 </li> 632 </li>
258 <li>#gentoo and #gentoo-java on irc.freenode.net</li> 633 <li>#gentoo and #gentoo-java on irc.freenode.net</li>
259 <li> 634 <li>
260 <uri 635 <uri

Legend:
Removed from v.1.22  
changed lines
  Added in v.1.29

  ViewVC Help
Powered by ViewVC 1.1.20