/[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.35
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.35 2006/10/15 22:03:16 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.11</version>
14<date>June 25, 2002</date> 28<date>2006-10-15</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>Before You Begin</title>
61<section>
62<title>Existing installs</title>
63<body>
64
65<p>
66For existing installs, regardless of if you have installed anything Java
67before, make sure you have followed the <uri
68link="/proj/en/java/java-upgrade.xml">Java Upgrade Guide</uri>.
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>New installs</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 78New installs should require no further preparation.
79</p>
80
81</body>
82</section>
83</chapter>
84
85<chapter>
86<title>Installing a Virtual Machine</title>
87<section>
88<title>The choices</title>
89<body>
90
91<p>
92Gentoo provides numerous Runtime Environments (JREs) and Development Kits
93(JDKs). Among the current choices, we have:
94</p>
95
96<table>
97<tr>
98 <th>Vendor</th>
99 <th>JDK</th>
100 <th>JRE</th>
101</tr>
102<tr>
103 <ti>The Blackdown Java Kit</ti>
104 <ti>dev-java/blackdown-jdk</ti>
105 <ti>dev-java/blackdown-jre</ti>
106</tr>
107<tr>
108 <ti>Sun's Java Kit</ti>
109 <ti>dev-java/sun-jdk</ti>
110 <ti>dev-java/sun-jre-bin</ti>
111</tr>
112<tr>
113 <ti>The IBM Java Kit</ti>
114 <ti>dev-java/ibm-jdk-bin</ti>
115 <ti>dev-java/ibm-jre-bin</ti>
116</tr>
117<tr>
118 <ti>The Compaq Java Kit for Alpha/Linux/GNU</ti>
119 <ti>dev-java/compaq-jdk</ti>
120 <ti>dev-java/compaq-jre</ti>
121</tr>
122<tr>
123 <ti>BEA WebLogic's J2SE Development Kit</ti>
124 <ti>dev-java/jrockit-jdk-bin</ti>
125</tr>
126</table>
127
128<!--
129TODO: list free implementations?
130note about not drop-in replacements
131kaffe/sablevm/gcj/jamvm
132-->
133<p>
134The default for Java 1.4 is the Blackdown JRE/JDK pair, as it is freely
135("free as in beer") available without any registration fuss.
136</p>
137
138<p>
139JREs and JDKs from Sun, IBM, and BEA are generally faster, but getting them
140is a bit more work, as you are required to read and accept their license before
141downloading (IBM additionally requires you to register).
142</p>
143
144</body>
145</section>
146<section>
147<title>Installing a JRE/JDKs</title>
148<body>
149
150<p>
151To install your profile's default JDK, you can run <c>emerge virtual/jdk</c>.
152Or to install your profile's default JRE, you can <c>emerge virtual/jre</c>.
153</p>
154
155<p>
156In recent events, Sun has relicensed their JDK and JRE under a more Linux
157distro friendly license. As a result, Sun releases Java 1.5 and onwards are
158freely downloadable, without any further hassle.
159</p>
160
161<note>
162A JDK also includes a JRE, so if you install a JDK you shouldn't have to also
163have to install a JRE.
50JDK.</note> 164</note>
51 165
166</body>
167</section>
168<section>
169<title>Installing fetch-restricted virtual machines</title>
170<body>
171
172<p>
173As already mentioned, some of the JDKs and JREs require you to jump through a
174few hoops before installing. Simply emerge the packages as you normally would.
175The ebuilds will then instruct you where to go and what to download.
176</p>
177
178<p>
52<p>You should download the indicated file(s) into 179You should download the indicated file(s) into
53<path>/usr/portage/distfiles</path>. Once that is done, you can rerun 180<path>/usr/portage/distfiles</path>. Once there, you can rerun the emerge
54the emerge command, then the JDK/JRE will be installed properly into 181command, at which point the JRE/JDK will be begin to install.
55<path>/opt</path>.</p> 182</p>
56</body>
57</section>
58</chapter>
59 183
184</body>
185</section>
60<chapter> 186</chapter>
61<title>Configuring your JDK/JRE</title> 187
188<chapter>
189<title>Configuring your virtual machine</title>
62<section> 190<section>
63<title>Overview</title> 191<title>Overview</title>
64<body> 192<body>
193
194<p>
65<p>Gentoo has the ability to have multiple JDKs and JREs installed 195Gentoo has the ability to have multiple JDKs and JREs installed without causing
66without them conflicting. There are a few caveats to this, as noted 196conflicts.
67below.</p> 197</p>
68 198
199<p>
69<p>Using the <c>java-config</c> tool, you can set the system-wide 200Using 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> 201(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 202up their own personal default.
72system-wide default.</p> 203</p>
73</body>
74</section>
75 204
205<note>
206You can also use <e>eselect</e> to change the system and user vm. See
207<c>eselect java-vm help</c>.
208</note>
209
210</body>
76<section> 211</section>
212<section>
77<title>Setting a default JDK/JRE</title> 213<title>Setting a default virtual machine</title>
78<body> 214<body>
215
216<p>
79<p>Running the command <c>java-config --list-available-vms</c> will 217Running 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> 218list of all JREs and JDKs installed on your system. Here is an example of
219output:
220</p>
221
222<pre caption="Listing available VMs">
223# <i>java-config --list-available-vms</i>
224The following VMs are available for generation-2:
2251) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2]
2262) Blackdown JRE 1.4.2.03 [blackdown-jre-1.4.2]
2273) Blackdown 32bit JRE 1.4.2.03 [emul-linux-x86-java-1.4.2]
2284) Sun 32bit JRE 1.5.0.08 [emul-linux-x86-java-1.5]
2295) Kaffe 1.1.7 [kaffe]
230*) Sun JDK 1.5.0.08 [sun-jdk-1.5]
81<pre> 231</pre>
82[%1 ~] java-config --list-available-vms 232
83[blackdown-jdk-1.3.1] Blackdown JDK 1.3.1 (/etc/env.d/java/20blackdown-jdk-1.3.1) 233<p>
84[blackdown-jre-1.3.1] Blackdown JRE 1.3.1 (/etc/env.d/java/20blackdown-jre-1.3.1) 234The <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 235set). 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 236particular VM. You use the handle or the number to <c>java-config
92--set-system-vm</c>, thus:</p> 237--set-system-vm</c>. Here is an example of how to set the system VM.
238</p>
239
240<pre caption="Setting the System VM">
241<comment>(By handle (preferred))</comment>
242# <i>java-config --set-system-vm blackdown-jdk-1.4</i>
243Now using blackdown-jdk-1.4 as your generation-2 system JVM
244<comment>(By number)</comment>
245# <i>java-config --set-system-vm 6</i>
246Now using sun-jdk-1.5 as your generation-2 system JVM
93<pre> 247</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 248
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> 249<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>, 250As a regular user, you can use <c>java-config --set-user-vm</c>.
111which will create <path>$HOME/.gentoo/java-env</path> with all 251</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 252
253<note>
254You no longer have to <c>source</c> the profile for updates to the user/system
255VM take place.
256</note>
257
258</body>
117<section> 259</section>
260<section id="preferred-vm">
261<title>Preferred VM</title>
262<body>
263
264<p>
265While merging Java packages, the VM can and will be switched as necessary.
266</p>
267
268<p>
269Because of the wide variety of available VMs, we do not have the resources to
270test and verify every package works on all of them. So to ensure that every
271packages merges smoothly, we have defined a list of <e>default/supported
272VMs</e> per arch. You can find them in
273<path>/usr/share/java-config/config/jdk-defaults.conf</path>. When you are
274merging a Java package, and it detects one of the VM in that file is installed,
275it will automatically use that VM, instead of the system-vm.
276</p>
277
278<p>
279The merge time VM switching is also needed when, for example, your system-vm is
280set a 1.4 VM and the package you are merging requires a 1.5 VM. While merging
281it will use the preferred 1.5 VM, leaving your system-vm choice intact.
282</p>
283
284<p>
285Of course, Gentoo is all about choice, so you can override these defaults in
286<path>/etc/java-config-2/build/jdk.conf</path> and have complete control over
287which VM will get used. Some examples:
288</p>
289
290<pre caption="Example /etc/java-config-2/build/jdk.conf">
291<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>
292*=sun-jdk
293</pre>
294
295<pre caption="Example /etc/java-config-2/build/jdk.conf">
296<comment>(Always use sun-jdk-1.5 wherever possible, except for when a 1.4 or 1.3 VM is explicitly required)</comment>
297*=sun-jdk-1.5
298</pre>
299
300<pre caption="Example /etc/java-config-2/build/jdk.conf">
301<comment># For 1.3 I prefer sun-jdk 1.4 but when it is not available, use ibm-jdk-bin,
302# For 1.4, use blackdown-jdk, and for 1.5, use sun-jdk </comment>
3031.3=sun-jdk-1.4 ibm-jdk-bin
3041.4=blackdown-jdk
3051.5=sun-jdk
306</pre>
307
308<warn>
309You do not have to edit this file. If you change these options to use a
310unsupported VM, things could possibly break. Bugs reported with a unsupported
311VM won't be prioritized as much as bugs present within supported VMs.
312</warn>
313
314</body>
315</section>
316</chapter>
317
318<chapter>
319<title>Compilers</title>
320<section>
321<body>
322
323<p>
324The standard Java compiler used for building is javac, which comes with each
325JDK. In addition to configuring the VM used at build time, it is also possible
326configure which compiler is used. Essentially, you define a list your
327preference for which compiler to use in
328<path>/etc/java-config-2/build/compilers.conf</path>.
329</p>
330
331<pre caption="/etc/java-config-2/build/compilers.conf">
332# If the ebuild supports it
333# it will check the COMPILERS var front to back and
334# use the first compiler that is installed
335
336COMPILERS="ecj-3.1 jikes javac"
337</pre>
338
339<p>
340Some compilers don't support all possible -target and -source arguments.
341Therefore, each compiler in the list is checked to see if it can support the
342desired -source/-target. javac will work in all cases, so if no other suitable
343compiler is found, it will be used instead.
344</p>
345
346<p>
347More details about each compiler are provided below:
348</p>
349
350<table>
351<tr>
352 <th>Name</th>
353 <th>Handle</th>
354 <th>Package</th>
355 <th>Description</th>
356</tr>
357<tr>
358 <ti>javac</ti>
359 <ti>javac</ti>
360 <ti>N/A</ti>
361 <ti>
362 This is the default compiler that will be used, and comes with each JDK.
363 </ti>
364</tr>
365<tr>
366 <ti>jikes</ti>
367 <ti>jikes</ti>
368 <ti>dev-java/jikes</ti>
369 <ti>
370 Jikes was originally developed by IBM. Anecdotally, it is generally quicker
371 than javac. Note however, that it is more pedantic, and will fail under a
372 few circumstances where javac has no issue. It also does not support Java
373 1.5 syntax yet.
374 </ti>
375</tr>
376<tr>
377 <ti>Eclipse Compiler for Java</ti>
378 <ti>ecj-3.1</ti>
379 <ti>=dev-java/eclipse-ecj-3.1*</ti>
380 <ti>
381 ECJ is the compiler used by the Eclipse software development kit. It is
382 very full featured, and is pretty fast. It does support Java 1.5 syntax.
383 </ti>
384</tr>
385</table>
386
387</body>
388</section>
389</chapter>
390
391<chapter>
118<title>Setting a default CLASSPATH</title> 392<title>Setting a default CLASSPATH</title>
393<section>
119<body> 394<body>
395
396<warn>
397The options explained in this section should be considered deprecated and will
398most likely be removed in the future. We strongly recommend against using
399these, because your Java projects or application should ideally manage their
400own classpaths. If you choose to specify a default CLASSPATH, some applications
401may behave unexpectedly, because classes they weren't expecting would be on the
402classpath.
403</warn>
404
405<p>
120<p><c>java-config</c> can also be used to set a system-wide default 406<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> 407well a user-specific default CLASSPATH.
408</p>
122 409
123<p>First you want to list available java libraries that might be 410<p>
124interesting to put in your CLASSPATH, thus:</p> 411First, you will want to list available Java libraries installed on your system
412that might want to be put in your CLASSPATH. Here is an example of output:
413</p>
414
415<pre caption="Listing classes">
416# <i>java-config --list-available-packages</i>
417[xerces-2] The next generation of high performance, fully compliant XML parsers in the Apache Xerces family (/usr/share/xerces-2/package.env)
418[junit] Simple framework to write repeatable tests (/usr/share/junit/package.env)
419[bsh] BeanShell: A small embeddable Java source interpreter (/usr/share/bsh/package.env)
420[bcel] The Byte Code Engineering Library: analyze, create, manipulate Java class files (/usr/share/bcel/package.env)
421[log4j] A low-overhead robust logging package for Java (/usr/share/log4j/package.env)
422...
125<pre> 423</pre>
126[%1 ~] java-config --list-available-packages 424
127[ant] No description (/usr/share/ant/classpath.env) 425<p>
128[java-gnome] No description (/usr/share/java-gnome/classpath.env) 426Again, 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) 427<c>java-config --set-system-classpath</c>. Here is an example:
130[log4j] "" (/usr/share/log4j/package.env)
131</pre> 428</p>
132 429
133<note>None of these packages have a proper description. That is 430<pre caption="Setting classpaths">
134something that will be implemented in the not-so-distant 431# <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> 432</pre>
140java-config --set-system-classpath=log4j,java-gtk,java-gnome 433
434<note>
435The current directory (<path>.</path>) will not be part of the system
436classpath, as that should be added in your system's login profile.
437</note>
438
439<p>
440You will have to update your environment by logging out, then in again or
441sourcing <path>/etc/profile</path>.
141</pre> 442</p>
142<note>The current directory (.) will not be part of the system classpath, 443
143as that should be added in root's login profile.</note> 444<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 445For users, <c>java-config --set-user-classpath</c> will create
148<path>$HOME/.gentoo/java-env-classpath</path>, which is automatically 446<path>~/.gentoo/java-env-classpath</path>, which you should then source from
149included by <path>$HOME/.gentoo/java-env</path>.</p> 447your shell's profile.
448</p>
449
450<pre caption="Sourcing user specific classpath">
451<i>if [[ -f "${HOME}/.gentoo/java-env-classpath" ]]; then
452 source ${HOME}/.gentoo/java-env-classpath
453fi</i>
454</pre>
455
456<p>
457If you really want a system wide or user default classpath you can add
458something like the following to your shell's profile. But we would advise
459against it.
460</p>
461
462<pre caption="Setting classpath">
463# <i>export CLASSPATH="${CLASSPATH}:$(java-config --classpath log4j,xerces-2)"</i>
464</pre>
465
466</body>
467</section>
468</chapter>
469
470<chapter>
471<title>Java Browser Plug-ins</title>
472<section>
473<title>Installing a plug-in</title>
474<body>
475
476<p>
477You can install a Java plug-in for your web browser by emerging a Java VM with
478the <c>nsplugin</c> USE flag set.
479</p>
480
481<note>
482<c>nsplugin</c> is not available for all architectures. Check for available
483plug-ins on your arch before trying to install a VM by running <c>emerge -pv
484&lt;java-vm&gt;</c>.
485</note>
486
487<p>
488Portage will allow you to install multiple versions of Java plug-ins, though
489only one will be used by your browser. You can check the list of available
490plug-ins by running:
491</p>
492
493<pre caption="Viewing available plug-ins">
494# <i>eselect java-nsplugin list</i>
495 [1] sun-jre-bin-1.5
496 [2] blackdown-jre-1.4.2
497</pre>
498
499<p>
500In this example, <c>sun-jre-bin</c> is selected for the browser plug-in.
501</p>
502
503<pre caption="Selecting a plug-in">
504# <i>eselect java-nsplugin sun-jre-bin-1.5</i>
505</pre>
506
507<p>
508Verify that the correct plug-in was selected:
509</p>
510
511<pre caption="Verifying the correct plug-in">
512# <i>eselect java-nsplugin list</i>
513 [1] sun-jre-bin-1.5 current
514 [2] blackdown-jre-1.4.2
515</pre>
516
517<p>
518Java.com also provides a link to <uri
519link="http://java.com/en/download/installed.jsp">verify your installed
520plug-in</uri>. Additionally, if you are using a Mozilla-based browser, you can
521verify your Java plug-in by typing <c>about:plugins</c> into the address bar.
522</p>
523
524</body>
525</section>
526<section>
527<title>Plug-ins on multilib systems</title>
528<body>
529
530<p>
531If you are running a mixed 64-bit and 32-bit multilib system (for example, on AMD64),
532you can have both 64-bit and a 32-bit Java plug-ins installed.
533</p>
534
535<p>
536First, check which plug-ins are available:
537</p>
538
539<pre caption="Viewing available plug-ins">
540# <i>eselect java-nsplugin list</i>
541Available 32-bit Java browser plugins
542 [1] emul-linux-x86-java-1.4.2
543 [2] emul-linux-x86-java-1.5
544Available 64-bit Java browser plugins
545 [1] blackdown-jdk-1.4.2
546 [2] blackdown-jre-1.4.2
547</pre>
548
549<p>
550You can select a 32-bit plug-in for a 32-bit browser (for example,
551<c>firefox-bin</c>), and you can select a 64-bit plug-in for your 64-bit
552browser (for example, <c>konqueror</c>).
553</p>
554
555<pre caption="Selecting plug-ins">
556# <i>eselect java-nsplugin set 32bit emul-linux-x86-java-1.4.2</i>
557# <i>eselect java-nsplugin set 64bit blackdown-jdk-1.4.2</i>
558</pre>
559
560<p>
561Verify the correct plug-ins were selected:
562</p>
563
564<pre caption="Verifying the correct plug-ins">
565# <i>eselect java-nsplugin list</i>
566Available 32-bit Java browser plugins
567 [1] emul-linux-x86-java-1.4.2 current
568 [2] emul-linux-x86-java-1.5
569Available 64-bit Java browser plugins
570 [1] blackdown-jdk-1.4.2 current
571 [2] blackdown-jre-1.4.2
572</pre>
573
574</body>
575</section>
576</chapter>
577
578<chapter>
579<title>USE flags for use with Java</title>
580<section>
581<title>Setting USE flags</title>
582<body>
583
584<p>
585For more information regarding USE flags, refer to the <uri
586link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">USE flags</uri>
587chapter from the Gentoo Handbook.
588</p>
589
590</body>
591</section>
592<section>
593<title>The flags</title>
594<body>
595
596<ul>
597 <li>The <b>java</b> flag adds support for Java in a variety of programs</li>
598 <li>
599 The <b>nsplugin</b> flag adds support for Mozilla-like browsers (including
600 Firefox). You will need this for viewing Java applets in your Mozilla-like
601 browser.
602 </li>
603 <li>
604 The <b>source</b> flag installs a zip of the source code of a package.
605 This is traditionally used for IDEs to 'attach' source to the libraries you
606 are using.
607 </li>
608 <li>
609 For Java packages, the <b>doc</b> flag will build API documentation using
610 javadoc.
611 </li>
612</ul>
613
150</body> 614</body>
151</section> 615</section>
152</chapter> 616</chapter>
153 617
154<chapter> 618<chapter>
155<title>Additional resources</title> 619<title>Additional resources</title>
156<section> 620<section>
157<title>Off-line resources</title> 621<title>Off-line resources</title>
158<body> 622<body>
623
159<ul> 624<ul>
160<li>java-config man page</li> 625 <li>java-config man page</li>
161<li><c>java-config --help</c></li> 626 <li><c>java-config --help</c></li>
162<li>The <path>/usr/bin/java-config</path> script itself</li>
163</ul> 627</ul>
628
164</body> 629</body>
165</section> 630</section>
166<section> 631<section>
167<title>Online resources</title> 632<title>Online resources</title>
168<body> 633<body>
634
169<ul> 635<ul>
170<li>The <uri link="http://lists.gentoo.org/pipermail/gentoo-dev/"> 636 <li>
171gentoo-dev </uri>, 637 The <uri link="http://www.gentoo.org/proj/en/java/">Java Project
172<uri link="http://lists.gentoo.org/pipermail/gentoo-user/"> gentoo-user 638 Page</uri>
639 </li>
640 <li>
641 The <uri
642 link="http://news.gmane.org/gmane.linux.gentoo.java">gentoo-java</uri>,
643 <uri
644 link="http://news.gmane.org/gmane.linux.gentoo.user">gentoo-user</uri>, and
645 <uri
646 link="http://news.gmane.org/gmane.linux.gentoo.devel">gentoo-dev</uri>
173</uri> mailing list archives</li> 647 mailing list archives
174<li>#gentoo on irc.openprojects.net</li> 648 </li>
649 <li>#gentoo and #gentoo-java on irc.freenode.net</li>
650 <li>
651 <uri
652 link="http://en.wikipedia.org/wiki/Java_programming_language">Wikipedia's
653 entry for Java</uri>
654 </li>
175</ul> 655</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 656
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> 657</body>
198</section> 658</section>
199</chapter> 659</chapter>
200</guide> 660</guide>

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

  ViewVC Help
Powered by ViewVC 1.1.20