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

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

  ViewVC Help
Powered by ViewVC 1.1.20