/[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.22 Revision 1.44
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/java.xml,v 1.22 2006/03/06 17:46:45 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/java.xml,v 1.44 2009/10/07 18:14:31 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/java.xml"> 5<guide link="/doc/en/java.xml">
6<title>Gentoo Java Guide</title> 6<title>Gentoo Java Guide</title>
7 7
8<author title="Author and Editor"> 8<author title="Author">
9 <mail link="nichoj@gentoo.org">Joshua Nichols</mail>
10</author>
11<author title="Author">
9 <mail link="karltk@gentoo.org">Karl Trygve Kalleberg</mail> 12 <mail link="karltk@gentoo.org">Karl Trygve Kalleberg</mail>
10</author> 13</author>
11<author title="Editor"> 14<author title="Editor">
12 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 15 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
13</author> 16</author>
14<author title="Editor">
15 <mail link="vanquirius@gentoo.org">Marcelo Góes</mail>
16</author>
17 17
18<abstract> 18<abstract>
19This guide will introduce users and developers to Java and explain how to use 19This guide will introduce you to Java and explain how to use Java with Gentoo
20Java with Gentoo Linux. 20Linux.
21</abstract> 21</abstract>
22 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 -->
23<license/> 25<license/>
24 26
25<version>0.3</version> 27<version>0.19</version>
26<date>2005-12-12</date> 28<date>2009-10-07</date>
27 29
28<chapter> 30<chapter>
29<title>What is Java?</title> 31<title>What is Java?</title>
30<section> 32<section>
31<title>Overview</title> 33<title>Overview</title>
32<body> 34<body>
33 35
34<p> 36<p>
35Java is a programming language developed by engineers of Sun Microsystems. 37Java is a programming language developed by engineers of Sun Microsystems. The
36The language is object-oriented and designed to run on multiple platforms 38language is object-oriented and designed to run on multiple platforms without
37without the need of recompiling code for each platform. Although Java can 39the need of recompiling code for each platform. Although Java can be compiled
38be compiled as a native program, much of Java's popularity can be attributed 40as a native program, much of Java's popularity can be attributed to its
39to its portability, along with other features such as garbage collection. 41portability, along with other features such as garbage collection. To make
40The ability to compile once and run in various platforms is achieved through 42platform independence possible the Java compiler compiles the Java code to an
41the use of just-in-time compilers (JIT), which compile Java bytecodes into 43intermediate representation called "Java bytecode" that runs on a JRE (Java
42native code when a given program is run. 44Runtime Environment) and not directly on the operating system.
43</p>
44
45<p> 45</p>
46
47<p>
46In order to run Java bytecodes, one needs to have a JRE (Java Runtime Environment) 48In order to run Java bytecode, one needs to have a JRE (Java Runtime
47installed. A JRE provides core libraries, a platform dependent Java Virtual Machine, 49Environment) installed. A JRE provides core libraries, a platform dependent
48plug-ins for browsers, among other things. A JDK (Java Development Kit) adds 50Java Virtual Machine, plugins for browsers, among other things. A JDK (Java
49programming tools, such as a bytecode compiler and a debugger. 51Development Kit) adds programming tools, such as a bytecode compiler and a
52debugger.
50</p> 53</p>
51 54
52</body> 55</body>
53</section> 56</section>
54</chapter>
55
56<chapter> 57</chapter>
57<title>Installing a JRE/JDK</title> 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
71</body>
72</section>
73<section>
74<title>New installs</title>
75<body>
76
77<p>
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>
58<section> 87<section>
59<title>The choices</title> 88<title>The choices</title>
60<body> 89<body>
61 90
62<p> 91<p>
63Gentoo provides numerous JREs and JDKs. Among the current alternatives, we have: 92Gentoo provides numerous Runtime Environments (JREs) and Development Kits
64</p> 93(JDKs). Among the current choices, we have:
65
66<ul>
67 <li>blackdown-jre and blackdown-jdk, the Blackdown Java Kit</li>
68 <li>sun-jre-bin and sun-jdk, Sun's Java Kit </li>
69 <li>ibm-jre-bin and ibm-jdk-bin, the IBM Java Kit</li>
70 <li>compaq-jre and compaq-jdk, the Compaq Java Kit for Alpha/Linux/GNU</li>
71 <li>jrockit-jdk-bin, BEA WebLogic's J2SE Development Kit</li>
72</ul>
73
74<p> 94</p>
75The default is the Blackdown JRE/JDK 95
76pair, as it is freely ("free as in beer") available without any registration 96<table>
77fuss. 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-->
78</p> 128<p>
79 129The default for Java 1.6 is the Sun JRE/JDK pair.
80<p> 130</p>
81Both the Sun JRE/JDK and the IBM JRE/JDK are generally faster, but getting them
82is a bit more work, as you are required to read and accept their license before
83downloading (IBM additionally requires you to register).
84</p>
85 131
86<p>
87Our ebuilds for the Sun and IBM JRE/JDKs will notify you of where to go to
88download them.
89</p>
90
91</body> 132</body>
92</section>
93<section> 133</section>
134<section>
94<title>Installing the Sun/IBM JRE/JDKs</title> 135<title>Installing a JRE/JDKs</title>
95<body> 136<body>
96 137
138<p>
139To install your profile's default JDK, you can run <c>emerge virtual/jdk</c>.
140Or to install your profile's default JRE, you can <c>emerge virtual/jre</c>.
97<p> 141</p>
98If you run <c>emerge =sun-jdk-1.4.2.06</c> or <c>=ibm-jdk-bin-1.4.2</c>, you will 142
99be notified that you are required to download the actual tarballs yourself. This 143<p>
100has to do with license restrictions for the Sun JRE/JDK (online click-wrap 144In recent events, Sun has relicensed their JDK and JRE under a more Linux
101license) and registration issues with the IBM JRE/JDK. 145distro friendly license. As a result, Sun releases Java 1.5 and onwards are
146freely downloadable, without any further hassle.
102</p> 147</p>
103 148
104<note> 149<note>
105ibm-jdk-bin is currently masked, you may have to unmask it to use it. 150A JDK also includes a JRE, so if you install a JDK you shouldn't have to also
151have to install a JRE.
106</note> 152</note>
107 153
154</body>
155</section>
156<section>
157<title>Installing fetch-restricted virtual machines</title>
158<body>
159
160<p>
161Some of the JDKs and JREs require you to jump through a few hoops before
162installing. Simply emerge the packages as you normally would. The ebuilds will
163then instruct you where to go and what to download.
164</p>
165
108<p> 166<p>
109You should download the indicated file(s) into 167You should download the indicated file(s) into
110<path>/usr/portage/distfiles</path>. Once that is done, you can rerun the emerge 168<path>/usr/portage/distfiles</path>. Once there, you can rerun the emerge
111command, then the JRE/JDK will be installed properly into <path>/opt</path>. 169command, at which point the JRE/JDK will be begin to install.
112</p> 170</p>
113 171
114</body> 172</body>
115</section> 173</section>
116</chapter>
117
118<chapter> 174</chapter>
119<title>Configuring your JRE/JDK</title> 175
176<chapter>
177<title>Configuring your virtual machine</title>
120<section> 178<section>
121<title>Overview</title> 179<title>Overview</title>
122<body> 180<body>
123 181
124<p> 182<p>
125Gentoo has the ability to have multiple JDKs and JREs installed without them 183Gentoo has the ability to have multiple JDKs and JREs installed without causing
126conflicting. 184conflicts.
127</p>
128
129<p> 185</p>
186
187<p>
130Using the <c>java-config</c> tool, you can set the system-wide default if you 188Using the <c>java-config</c> tool, you can set the system-wide default
131have root access. Users can also use <c>java-config</c> to set up their own 189(provided you have root access). Users can also use <c>java-config</c> to set
132personal default, that is different from the system-wide default. 190up their own personal default.
133</p> 191</p>
134 192
135</body> 193<note>
136</section> 194You can also use <e>eselect</e> to change the system and user vm. See
195<c>eselect java-vm help</c>.
196</note>
137 197
198</body>
138<section> 199</section>
200<section>
139<title>Setting a default JRE/JDK</title> 201<title>Setting a default virtual machine</title>
140<body> 202<body>
141 203
142<p> 204<p>
143Running the command <c>java-config --list-available-vms</c> will give you a list 205Running the command <c>java-config --list-available-vms</c> will give you a
144of all available JREs and JDKs on your system. Here is an example of output: 206list of all JREs and JDKs installed on your system. Here is an example of
207output:
145</p> 208</p>
146 209
147<pre caption="Listing available VMs"> 210<pre caption="Listing available VMs">
148# <i>java-config --list-available-vms</i> 211# <i>java-config --list-available-vms</i>
149[blackdown-jdk-1.3.1] Blackdown JDK 1.3.1 (/etc/env.d/java/20blackdown-jdk-1.3.1) 212The following VMs are available for generation-2:
150[blackdown-jre-1.3.1] Blackdown JRE 1.3.1 (/etc/env.d/java/20blackdown-jre-1.3.1) 2131) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] <comment>(Build Only)</comment>
151[ibm-jdk-1.3.0] IBM JDK 1.3.0 (/etc/env.d/java/20ibm-jdk-1.3.0) 2142) Blackdown JRE 1.4.2.03 [blackdown-jre-1.4.2] <comment>(Build Only)</comment>
152[ibm-jdk-1.3.1] IBM JDK 1.3.1 (/etc/env.d/java/20ibm-jdk-1.3.1) 2153) IcedTea6-bin 1.4.1 [icedtea6-bin]
153[ibm-jre-1.3.1] IBM JRE 1.3.1 (/etc/env.d/java/20ibm-jre-1.3.1) 2164) Sun JDK 1.5.0.20 [sun-jdk-1.5] <comment>(Build Only)</comment>
154[sun-jdk-1.4.0] Sun JDK 1.4.0 (/etc/env.d/java/20sun-jdk-1.4.0) 217*) Sun JDK 1.6.0.16 [sun-jdk-1.6]
155</pre> 218</pre>
156 219
220<note>
221VMs marked as Build Only may contain security vulnerabilities and/or be EOL.
222Gentoo recommends not setting these VMs as either your system or user VM.
223Please see <uri link="java.xml#build-only">Build Only VM</uri> for more
224information.
225</note>
226
157<p> 227<p>
228The <e>*</e> indicates this is the current active vm (system-vm or user-vm when
158The name in the brackets <path>"[]"</path> is the handle or ID for that 229set). The name in the brackets (<e>[]</e>) is the handle or ID for that
159particular VM. You use pass that ID to <c>java-config --set-system-vm</c>. Here is 230particular VM. You use the handle or the number to <c>java-config
160an example of how to set the system VM. 231--set-system-vm</c>. Here is an example of how to set the system VM.
161</p> 232</p>
162 233
163<pre caption="Setting the System VM"> 234<pre caption="Setting the System VM">
235<comment>(By handle (preferred))</comment>
164# <i>java-config --set-system-vm ibm-jdk-1.3.1</i> 236# <i>java-config --set-system-vm blackdown-jdk-1.4</i>
165Now using IBM JDK 1.3.1 (/etc/env.d/java/20ibm-jdk-1.3.1) 237Now using blackdown-jdk-1.4 as your generation-2 system JVM
238WARNING: blackdown-jdk-1.4 is marked as a build-only JVM. Using this vm is not recommended.
239<comment>(By number)</comment>
240# <i>java-config --set-system-vm 5</i>
241Now using sun-jdk-1.6 as your generation-2 system JVM
242</pre>
243
244<p>
245As a regular user, you can use <c>java-config --set-user-vm</c>.
166</pre> 246</p>
167 247
168<note> 248<note>
169You will have to be root to run --set-system-vm. 249You no longer have to <c>source</c> the profile for updates to the user/system
250VM take place.
170</note> 251</note>
171 252
172<p> 253</body>
173Once you have issued <c>java-config --set-system-vm</c> with a particular VM 254</section>
174ID, you will need to regenerate your <path>/etc/profile.env</path>. You can do 255<section id="build-only">
175it like this: 256<title>Build Only VM</title>
257<body>
258
176</p> 259<p>
177 260Some virtual machines are flagged as build-only due to being EOL and/or
178<pre caption="Regenerating /etc/profile.env" > 261containing security vulnerabilities. These virtual machines will not
179# <i>env-update</i> 262automatically be used by Gentoo for the running of applications using Gentoo
180</pre> 263launchers but will still be available for use by Gentoo's build environment as
181 264some packages may require them for building. The setting of these virtual
265machines as either your system or user VM is strongly discouraged as these VMs
266will then be used when running the <path>/usr/bin/{java,javac,..}</path>
267executables and will also be used by any packages not using Gentoo's launcher
268scripts.
182<p> 269</p>
183After this, you will either want to relogin, or resource 270
184<path>/etc/profile</path> into your environment. 271</body>
272</section>
273<section id="preferred-vm">
274<title>Preferred VM</title>
275<body>
276
185</p> 277<p>
186 278While merging Java packages, the VM can and will be switched as necessary.
187<p> 279</p>
188As a regular user, you can use <c>java-config --set-user-vm</c>, which will 280
189create <path>~/.gentoo/java-env</path> with all required env vars. You would
190normally source this from your shell's startup script (generally
191<path>~/.bashrc</path>).
192</p> 281<p>
282Because of the wide variety of available VMs, we do not have the resources to
283test and verify every package works on all of them. So to ensure that every
284packages merges smoothly, we have defined a list of <e>default/supported
285VMs</e> per arch. You can find them in
286<path>/usr/share/java-config-2/config/jdk-defaults.conf</path>. When you are
287merging a Java package, and it detects one of the VM in that file is installed,
288it will automatically use that VM, instead of the system-vm.
289</p>
290
291<p>
292The merge time VM switching is also needed when, for example, your system-vm is
293set a 1.4 VM and the package you are merging requires a 1.5 VM. While merging
294it will use the preferred 1.5 VM, leaving your system-vm choice intact.
295</p>
296
297<p>
298Of course, Gentoo is all about choice, so you can override these defaults in
299<path>/etc/java-config-2/build/jdk.conf</path> and have complete control over
300which VM will get used. 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.4, use blackdown-jdk, and for 1.5, use sun-jdk </comment>
3161.3=sun-jdk-1.4 ibm-jdk-bin
3171.4=blackdown-jdk
3181.5=sun-jdk
319</pre>
320
321<warn>
322You do not have to edit this file. If you change these options to use a
323unsupported VM, things could possibly break. Bugs reported with a unsupported
324VM won't be prioritized as much as bugs present within supported VMs.
325</warn>
326
327</body>
328</section>
329</chapter>
330
331<chapter>
332<title>Compilers</title>
333<section>
334<body>
335
336<p>
337The standard Java compiler used for building is javac, which comes with each
338JDK. In addition to configuring the VM used at build time, it is also possible
339configure which compiler is used. Essentially, you define a list your
340preference for which compiler to use in
341<path>/etc/java-config-2/build/compilers.conf</path>.
342</p>
343
344<pre caption="/etc/java-config-2/build/compilers.conf">
345# If the ebuild supports it
346# it will check the COMPILERS var front to back and
347# use the first compiler that is installed
348
349COMPILERS="ecj-3.1 jikes javac"
350</pre>
351
352<p>
353Some compilers don't support all possible -target and -source arguments.
354Therefore, each compiler in the list is checked to see if it can support the
355desired -source/-target. javac will work in all cases, so if no other suitable
356compiler is found, it will be used instead.
357</p>
358
359<p>
360More details about each compiler are provided below:
361</p>
362
363<table>
364<tr>
365 <th>Name</th>
366 <th>Handle</th>
367 <th>Package</th>
368 <th>Description</th>
369</tr>
370<tr>
371 <ti>javac</ti>
372 <ti>javac</ti>
373 <ti>N/A</ti>
374 <ti>
375 This is the default compiler that will be used, and comes with each JDK.
376 </ti>
377</tr>
378<tr>
379 <ti>jikes</ti>
380 <ti>jikes</ti>
381 <ti>dev-java/jikes</ti>
382 <ti>
383 Jikes was originally developed by IBM. Anecdotally, it is generally quicker
384 than javac. Note however, that it is more pedantic, and will fail under a
385 few circumstances where javac has no issue. It also does not support Java
386 1.5 syntax yet.
387 </ti>
388</tr>
389<tr>
390 <ti>Eclipse Compiler for Java</ti>
391 <ti>ecj-3.1</ti>
392 <ti>=dev-java/eclipse-ecj-3.1*</ti>
393 <ti>
394 ECJ is the compiler used by the Eclipse software development kit. It is
395 very full featured, and is pretty fast. It does support Java 1.5 syntax.
396 </ti>
397</tr>
398</table>
399
400</body>
401</section>
402</chapter>
403
404<chapter>
405<title>Setting a default CLASSPATH</title>
406<section>
407<body>
408
409<warn>
410The options explained in this section should be considered deprecated and will
411most likely be removed in the future. We strongly recommend against using
412these, because your Java projects or application should ideally manage their
413own classpaths. If you choose to specify a default CLASSPATH, some applications
414may behave unexpectedly, because classes they weren't expecting would be on the
415classpath.
416</warn>
417
418<p>
419<c>java-config</c> can also be used to set a system-wide default CLASSPATH, as
420well a user-specific default CLASSPATH.
421</p>
422
423<p>
424First, you will want to list available Java libraries installed on your system
425that might want to be put in your CLASSPATH. Here is an example of output:
426</p>
427
428<pre caption="Listing classes">
429# <i>java-config --list-available-packages</i>
430[xerces-2] The next generation of high performance, fully compliant XML parsers in the Apache Xerces family (/usr/share/xerces-2/package.env)
431[junit] Simple framework to write repeatable tests (/usr/share/junit/package.env)
432[bsh] BeanShell: A small embeddable Java source interpreter (/usr/share/bsh/package.env)
433[bcel] The Byte Code Engineering Library: analyze, create, manipulate Java class files (/usr/share/bcel/package.env)
434[log4j] A low-overhead robust logging package for Java (/usr/share/log4j/package.env)
435...
436</pre>
437
438<p>
439Again, the names in brackets (<e>[]</e>) are the IDs that you have to pass to
440<c>java-config --set-system-classpath</c>. Here is an example:
441</p>
442
443<pre caption="Setting classpaths">
444# <i>java-config --set-system-classpath log4j,xerces-2</i>
445</pre>
446
447<note>
448The current directory (<path>.</path>) will not be part of the system
449classpath, as that should be added in your system's login profile.
450</note>
451
452<p>
453You will have to update your environment by logging out, then in again or
454sourcing <path>/etc/profile</path>.
455</p>
456
457<p>
458For users, <c>java-config --set-user-classpath</c> will create
459<path>~/.gentoo/java-env-classpath</path>, which you should then source from
460your shell's profile.
461</p>
462
463<pre caption="Sourcing user specific classpath">
464<i>if [[ -f "${HOME}/.gentoo/java-env-classpath" ]]; then
465 source ${HOME}/.gentoo/java-env-classpath
466fi</i>
467</pre>
468
469<p>
470If you really want a system wide or user default classpath you can add
471something like the following to your shell's profile. But we would advise
472against it.
473</p>
474
475<pre caption="Setting classpath">
476# <i>export CLASSPATH="${CLASSPATH}:$(java-config --classpath log4j,xerces-2)"</i>
477</pre>
478
479</body>
480</section>
481</chapter>
482
483<chapter>
484<title>Java Browser Plugins</title>
485<section>
486<title>Installing a plugin</title>
487<body>
488
489<p>
490You can install a Java plugin for your web browser by emerging a Java VM with
491the <c>nsplugin</c> USE flag set.
492</p>
493
494<note>
495<c>nsplugin</c> is not available for all architectures. Check for available
496plugins on your arch before trying to install a VM by running <c>emerge -pv
497&lt;java-vm&gt;</c>.
498</note>
499
500<p>
501Portage will allow you to install multiple versions of Java plugins, though
502only one will be used by your browser. You can check the list of available
503plugins by running:
504</p>
505
506<pre caption="Viewing available plugins">
507# <i>eselect java-nsplugin list</i>
508 [1] sun-jre-bin-1.6
509 [2] icedtea6-bin
510</pre>
511
512<p>
513In this example, <c>sun-jre-bin</c> is selected for the browser plugin.
514</p>
515
516<pre caption="Selecting a plugin">
517# <i>eselect java-nsplugin set sun-jre-bin-1.6</i>
518</pre>
519
520<p>
521Verify that the correct plugin was selected:
522</p>
523
524<pre caption="Verifying the correct plugin">
525# <i>eselect java-nsplugin list</i>
526 [1] sun-jre-bin-1.6 current
527 [2] icedtea6-bin
528</pre>
529
530<p>
531Java.com also provides a link to <uri
532link="http://java.com/en/download/installed.jsp">verify your installed
533plugin</uri>. Additionally, if you are using a Mozilla-based browser, you can
534verify your Java plugin by typing <c>about:plugins</c> into the address bar.
535</p>
536
537</body>
538</section>
539<section>
540<title>Plugins on multilib systems</title>
541<body>
542
543<p>
544If you are running a mixed 64-bit and 32-bit multilib system (for example, on
545AMD64), you can use 64-bit and 32-bit Java plugins. Unless you have a pressing
546need to run 32-bit Java applications, we recommend using native 64-bit plugins
547on 64-bit web browsers.
548</p>
549
550<p>
551There are several native 64-bit browser plugins available. The default JDK/JRE
552pair, <c>sun-jdk</c> and <c>sun-jre-bin</c>, both include browser plugins. Just
553emerge one of them with the <c>nsplugin</c> USE flag enabled.
554</p>
555
556<pre caption="Installing a 64-bit plugin">
557# <i>echo "dev-java/sun-jre-bin nsplugin" >> /etc/portage/package.use</i>
558# <i>emerge sun-jre-bin</i>
559</pre>
560
561<p>
562To use a 32-bit plugin on a 32-bit browser, you will need to emerge
563<c>emul-linux-x86-java</c> with the <c>nsplugin</c> USE flag enabled.
564</p>
565
566<pre caption="Installing a 32-bit plugin">
567# <i>echo "app-emulation/emul-linux-x86-java nsplugin" >> /etc/portage/package.use</i>
568# <i>emerge emul-linux-x86-java</i>
569</pre>
570
571<p>
572Next, check which plugins are available:
573</p>
574
575<pre caption="Viewing available plugins">
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
580Available 64-bit Java browser plugins
581 [1] icedtea6-bin
582 [2] sun-jre-bin-1.6
583</pre>
584
585<p>
586Now select the right plugin for your browsers:
587</p>
588
589<pre caption="Selecting plugins">
590<comment>(Choose the plugins for 32-bit and 64-bit browsers)</comment>
591# <i>eselect java-nsplugin set 32bit emul-linux-x86-java-1.6</i>
592# <i>eselect java-nsplugin set 64bit sun-jre-bin-1.6</i>
593</pre>
594
595<p>
596Verify the correct plugin was selected:
597</p>
598
599<pre caption="Verifying the correct plugin">
600# <i>eselect java-nsplugin list</i>
601Available 32-bit Java browser plugins
602 [1] emul-linux-x86-java-1.5
603 [2] emul-linux-x86-java-1.6 current
604Available 64-bit Java browser plugins
605 [1] icedtea6-bin
606 [2] sun-jre-bin-1.6 current
607</pre>
193 608
194</body> 609</body>
195</section> 610</section>
196</chapter> 611</chapter>
197 612
212<section> 627<section>
213<title>The flags</title> 628<title>The flags</title>
214<body> 629<body>
215 630
216<ul> 631<ul>
217 <li>The <b>java</b> flag adds support for Java in a variety of programs.</li> 632 <li>The <b>java</b> flag adds support for Java in a variety of programs</li>
218 <li> 633 <li>
219 The <b>nsplugin</b> flag adds a symlink to the javaplugin for 634 The <b>nsplugin</b> flag adds support for Mozilla-like browsers (including
220 Mozilla-like browsers (including Firefox) if you are using, for example, 635 Firefox). You will need this for viewing Java applets in your Mozilla-like
221 Blackdown's Java kit, IBM Java Kit or Sun's Java Kit. You will need this 636 browser.
222 for viewing Java applets in your Mozilla-like browser. 637 </li>
638 <li>
639 The <b>source</b> flag installs a zip of the source code of a package.
640 This is traditionally used for IDEs to 'attach' source to the libraries you
641 are using.
642 </li>
643 <li>The <b>jce</b> flag adds support for the Java Cryptography Engine</li>
644 <li>
645 For Java packages, the <b>doc</b> flag will build API documentation using
646 javadoc.
223 </li> 647 </li>
224</ul> 648</ul>
225 649
226</body> 650</body>
227</section> 651</section>
234<body> 658<body>
235 659
236<ul> 660<ul>
237 <li>java-config man page</li> 661 <li>java-config man page</li>
238 <li><c>java-config --help</c></li> 662 <li><c>java-config --help</c></li>
239 <li>The <path>/usr/bin/java-config</path> script itself</li>
240</ul> 663</ul>
241 664
242</body> 665</body>
243</section> 666</section>
244<section> 667<section>
245<title>Online resources</title> 668<title>Online resources</title>
246<body> 669<body>
247 670
248<ul> 671<ul>
249 <li>The <uri link="/proj/en/java/">Gentoo Java Project Page</uri></li> 672 <li>
673 The <uri link="http://www.gentoo.org/proj/en/java/">Java Project
674 Page</uri>
675 </li>
250 <li> 676 <li>
251 The <uri 677 The <uri
252 link="http://news.gmane.org/gmane.linux.gentoo.devel">gentoo-dev</uri>,
253 <uri link="http://news.gmane.org/gmane.linux.gentoo.user">gentoo-user
254 </uri> and <uri
255 link="http://news.gmane.org/gmane.linux.gentoo.java">gentoo-java</uri> 678 link="http://news.gmane.org/gmane.linux.gentoo.java">gentoo-java</uri>,
679 <uri
680 link="http://news.gmane.org/gmane.linux.gentoo.user">gentoo-user</uri>, and
681 <uri
682 link="http://news.gmane.org/gmane.linux.gentoo.devel">gentoo-dev</uri>
256 mailing list archives 683 mailing list archives
257 </li> 684 </li>
258 <li>#gentoo and #gentoo-java on irc.freenode.net</li> 685 <li>
686 <uri link="irc://irc.gentoo.org/gentoo">#gentoo</uri> and <uri
687 link="irc://irc.gentoo.org/gentoo-java">#gentoo-java</uri> on IRC
688 </li>
259 <li> 689 <li>
260 <uri 690 <uri
261 link="http://en.wikipedia.org/wiki/Java_programming_language">Wikipedia's 691 link="http://en.wikipedia.org/wiki/Java_programming_language">Wikipedia's
262 entry for Java</uri> 692 entry for Java</uri>
263 </li> 693 </li>
694 <li>
695 If you have suggestions or questions regarding this document, please email
696 the Gentoo Java team: <mail>java@gentoo.org</mail>
697 </li>
264</ul> 698</ul>
265 699
266</body> 700</body>
267</section> 701</section>
268</chapter> 702</chapter>

Legend:
Removed from v.1.22  
changed lines
  Added in v.1.44

  ViewVC Help
Powered by ViewVC 1.1.20