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

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

  ViewVC Help
Powered by ViewVC 1.1.20