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

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

  ViewVC Help
Powered by ViewVC 1.1.20