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

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

  ViewVC Help
Powered by ViewVC 1.1.20