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

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.33

  ViewVC Help
Powered by ViewVC 1.1.20