/[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.12 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.12 2003/11/22 10:01:56 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 17
15<abstract> 18<abstract>
16Users' and Developers' Guide to Java in Gentoo 19This guide will introduce you to Java and explain how to use Java with Gentoo
20Linux.
17</abstract> 21</abstract>
18 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 -->
19<license/> 25<license/>
20 26
21<version>0.1.4</version> 27<version>0.7</version>
22<date>November 21, 2003</date> 28<date>2006-08-08</date>
23 29
24<chapter> 30<chapter>
25<title>Installing a JDK/JRE</title> 31<title>What is Java?</title>
26<section> 32<section>
27<title>Overview</title> 33<title>Overview</title>
28<body> 34<body>
29 35
30<p> 36<p>
31Gentoo provides numerous JDKs and JREs. The default is the Blackdown JDK/JRE 37Java is a programming language developed by engineers of Sun Microsystems. The
32pair, as it is freely (beer) available without any registration fuss. 38language is object-oriented and designed to run on multiple platforms without
33</p> 39the need of recompiling code for each platform. Although Java can be compiled
34 40as a native program, much of Java's popularity can be attributed to its
35<note> 41portability, along with other features such as garbage collection. To make
36As kaffe becomes a JRE/JDK drop-in replacement, that will most likely become our 42platform independence possible the Java compiler compiles the Java code to an
37default. 43intermediate representation called "Java bytecode" that runs on a JRE (Java
38</note> 44Runtime Environment) and not directly on the operating system.
39
40<p> 45</p>
41Both the Sun JDK/JRE and the IBM JDK/JRE are generally faster, but getting them 46
47<p>
48In order to run Java bytecode, one needs to have a JRE (Java Runtime
49Environment) installed. A JRE provides core libraries, a platform dependent
50Java Virtual Machine, plug-ins for browsers, among other things. A JDK (Java
51Development Kit) adds programming tools, such as a bytecode compiler and a
52debugger.
53</p>
54
55</body>
56</section>
57</chapter>
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>
161<section>
162<title>The choices</title>
163<body>
164
165<p>
166Gentoo provides numerous Runtime Environments (JREs) and Development Kits
167(JDKs). Among the current choices, we have:
168</p>
169
170<table>
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
208<p>
209The default is Blackdown for both the JRE and the JDK, as it is freely ("free
210as in beer") available without any registration fuss.
211</p>
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
42is 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
43downloading (IBM additionally requires you to register). 221downloading (IBM additionally requires you to register).
44</p> 222</p>
45 223
46<p>
47Our ebuilds for the Sun and IBM JDK/JREs will notify you of where to go to
48download them.
49</p>
50
51</body> 224</body>
52</section>
53
54<section> 225</section>
226<section>
55<title>Installing the Sun/IBM JDK/JREs</title> 227<title>Installing a JRE/JDKs</title>
56<body> 228<body>
57 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>.
58<p> 233</p>
59If you run <c>emerge sun-jdk-1.3.1</c> or <c>emerge ibm-jdk-1.3.1</c>, you will 234
60be notified that you are required to download the actual tarballs yourself. This 235<p>
61has to do with license restrictions for the Sun JDK/JRE (online click-wrap 236In recent events, Sun has relicensed their JDK and JRE under a more Linux
62license) and registration issues with the IBM JDK/JRE. 237distro friendly license. As a result, Sun releases Java 1.5 and onwards are
238freely downloadable, without any further hassle.
63</p> 239</p>
64 240
65<note> 241<note>
66There is also a sun-jdk-1.4.0, but not all packages work nicely with Java 1.4, 242A JDK also includes a JRE, so if you install a JDK you shouldn't have to also
67so you're on your own if you use the 1.4.0 JDK. 243have to install a JRE.
68</note> 244</note>
69 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
70<p> 258<p>
71You should download the indicated file(s) into 259You should download the indicated file(s) into
72<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
73command, then the JDK/JRE will be installed properly into <path>/opt</path>. 261command, at which point the JRE/JDK will be begin to install.
74</p> 262</p>
75 263
76</body> 264</body>
77</section> 265</section>
78</chapter>
79
80<chapter> 266</chapter>
81<title>Configuring your JDK/JRE</title> 267
268<chapter>
269<title>Configuring your virtual machine</title>
82<section> 270<section>
83<title>Overview</title> 271<title>Overview</title>
84<body> 272<body>
85 273
86<p> 274<p>
87Gentoo 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
88conflicting. 276conflicts.
89</p>
90
91<p> 277</p>
278
279<p>
92Using 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
93have 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
94personal default, that is different from the system-wide default. 282up their own personal default.
95</p> 283</p>
96 284
97</body> 285<note>
98</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>
99 289
290</body>
100<section> 291</section>
292<section>
101<title>Setting a default JDK/JRE</title> 293<title>Setting a default virtual machine</title>
102<body> 294<body>
103 295
104<p> 296<p>
105Running 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
106of all available JREs and JDKs on your system, thus: 298list of all JREs and JDKs installed on your system. Here is an example of
299output:
107</p> 300</p>
108 301
109<pre caption="Listing available VMs"> 302<pre caption="Listing available VMs">
110# <i>java-config --list-available-vms</i> 303# <i>java-config --list-available-vms</i>
111[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)
112[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)
113[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)
114[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)
115[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)
116[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)
117</pre> 316</pre>
118 317
119<p> 318<p>
319The <e>*</e> indicates this is the current active vm (system-vm or user-vm when
120The 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
121particular VM. You use pass that ID to <c>java-config --set-system-vm</c>, thus: 321particular VM. You use the handle or the number to <c>java-config
322--set-system-vm</c>. Here is an example of how to set the system VM.
122</p> 323</p>
123 324
124<pre caption="Setting the System VM"> 325<pre caption="Setting the System VM">
326<comment>(By handle (preferred))</comment>
125# <i>java-config --set-system-vm=ibm-jdk-1.3.1</i> 327# <i>java-config --set-system-vm blackdown-jdk-1.4</i>
126Now 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>.
127</pre> 334</p>
128 335
129<note> 336<note>
130You 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.
131</note> 339</note>
132 340
133<p>
134Once you have issued <c>java-config --set-system-vm</c> with a particular VM ID,
135you will need to regenerate your /etc/profile.env, thus:
136</p>
137
138<pre caption="Regenerating /etc/profile.env" >
139# <i>env-update</i>
140</pre>
141
142<p>
143After this, you will either want to relogin, or resource
144<path>/etc/profile</path> into your environment.
145</p>
146
147<p>
148As a regular user, you can use <c>java-config --set-user-vm</c>, which will
149create <path>$HOME/.gentoo/java-env</path> with all required env vars. You would
150normally source this from your shell's startup script
151(<path>$HOME/.zshenv</path> in my case).
152</p>
153
154</body> 341</body>
155</section>
156
157<section> 342</section>
343<section id="preferred-vm">
344<title>Preferred VM</title>
345<body>
346
347<p>
348While merging Java packages, the VM can and will be switched as necessary.
349</p>
350
351<p>
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.
359</p>
360
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>
158<title>Setting a default CLASSPATH</title> 475<title>Setting a default CLASSPATH</title>
476<section>
159<body> 477<body>
160 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
161<p> 488<p>
162<c>java-config</c> can also be used to set a system-wide default CLASSPATH, and 489<c>java-config</c> can also be used to set a system-wide default CLASSPATH, as
163of course a user-specific default CLASSPATH. 490well a user-specific default CLASSPATH.
164</p>
165
166<p> 491</p>
167First you want to list available java libraries that might be interesting to put 492
168in your CLASSPATH, thus: 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:
169</p> 496</p>
170 497
171<pre caption="Listing classes"> 498<pre caption="Listing classes">
172# <i>java-config --list-available-packages</i> 499# <i>java-config --list-available-packages</i>
173[ant] No description (/usr/share/ant/classpath.env) 500[xerces-2] The next generation of high performance, fully compliant XML parsers in the Apache Xerces family (/usr/share/xerces-2/package.env)
174[java-gnome] No description (/usr/share/java-gnome/classpath.env) 501[junit] Simple framework to write repeatable tests (/usr/share/junit/package.env)
175[java-gtk] No description (/usr/share/java-gtk/classpath.env) 502[bsh] BeanShell: A small embeddable Java source interpreter (/usr/share/bsh/package.env)
176[log4j] "" (/usr/share/log4j/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>
177</pre> 515</pre>
178 516
179<note> 517<note>
180None of these packages have a proper description. That is something that will be 518The current directory (<path>.</path>) will not be part of the system
181implemented in the not-so-distant future. 519classpath, as that should be added in your system's login profile.
182</note> 520</note>
183 521
184<p> 522<p>
185Again, the name in brackets <path>"[]"</path> are the IDs that you have to pass 523You will have to update your environment by logging out, then in again or
186to <c>java-config --set-system-classpath</c>, thus:
187</p>
188
189<pre caption="Setting classpaths">
190# <i>java-config --set-system-classpath=log4j,java-gtk,java-gnome</i>
191</pre>
192
193<note>
194The current directory (.) will not be part of the system classpath, as that
195should be added in root's login profile.
196</note>
197
198<p>
199Again, you will want to run <c>env-update</c> to update your system's
200environment, and you might also want to relogin or resource the
201<path>/etc/profile</path>. 524sourcing <path>/etc/profile</path>.
202</p> 525</p>
203 526
204<p> 527<p>
205For users, <c>java-config --set-user-classpath</c> will create 528For users, <c>java-config --set-user-classpath</c> will create
206<path>$HOME/.gentoo/java-env-classpath</path>, which is automatically included 529<path>~/.gentoo/java-env-classpath</path>, which you should then source from
207by <path>$HOME/.gentoo/java-env</path>. 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
208</p> 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>
548
549</body>
550</section>
551</chapter>
552
553<chapter>
554<title>USE flags for use with Java</title>
555<section>
556<title>Setting USE flags</title>
557<body>
558
559<p>
560For more information regarding USE flags, refer to the <uri
561link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">USE flags</uri>
562chapter from the Gentoo Handbook.
563</p>
564
565</body>
566</section>
567<section>
568<title>The flags</title>
569<body>
570
571<ul>
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.
577 </li>
578 <li>
579 The <b>doc</b> flag will typically install API documentation, as generated
580 by javadoc.
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.
595 </li>
596</ul>
209 597
210</body> 598</body>
211</section> 599</section>
212</chapter> 600</chapter>
213 601
216<section> 604<section>
217<title>Off-line resources</title> 605<title>Off-line resources</title>
218<body> 606<body>
219 607
220<ul> 608<ul>
221<li>java-config man page</li> 609 <li>java-config man page</li>
222<li><c>java-config --help</c></li> 610 <li><c>java-config --help</c></li>
223<li>The <path>/usr/bin/java-config</path> script itself</li>
224</ul> 611</ul>
225 612
226</body> 613</body>
227</section> 614</section>
228
229<section> 615<section>
230<title>Online resources</title> 616<title>Online resources</title>
231<body> 617<body>
232 618
233<ul> 619<ul>
620 <li>
621 The <uri link="http://www.gentoo.org/proj/en/java/">Java Project
622 Page</uri>
623 </li>
624 <li>
625 The <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
234<li>The <uri link="http://news.gmane.org/gmane.linux.gentoo.devel" 630 link="http://news.gmane.org/gmane.linux.gentoo.devel">gentoo-dev</uri>
235>gentoo-dev</uri>, <uri link="http://news.gmane.org/gmane.linux.gentoo.user" 631 mailing list archives
236>gentoo-user </uri> mailing list archives</li> 632 </li>
237<li>#gentoo and #gentoo-java on irc.freenode.net</li> 633 <li>#gentoo and #gentoo-java on irc.freenode.net</li>
634 <li>
635 <uri
636 link="http://en.wikipedia.org/wiki/Java_programming_language">Wikipedia's
637 entry for Java</uri>
638 </li>
238</ul> 639</ul>
239 640
240</body> 641</body>
241</section> 642</section>
242</chapter> 643</chapter>

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

  ViewVC Help
Powered by ViewVC 1.1.20