1 |
On Tue, 2005-11-29 at 13:50 +0200, Petteri Räty wrote: |
2 |
> Greg Tassone wrote: |
3 |
> > |
4 |
> > FYI: There is nothing "unstable" about JDK 1.5 (or Java 5). |
5 |
... |
6 |
> It has simply |
7 |
> > been package-masked here at Gentoo because there have been some |
8 |
> > lingering ebuilds that didn't compile cleanly with it. Hopefully it is |
9 |
> > going to be unmasked VERY soon. |
10 |
> > |
11 |
> |
12 |
> It also by default produces class files that are not compatible with |
13 |
> earlier versions etc. |
14 |
... |
15 |
> You can safely make 1.5 the user vm using java-config -s. But just be |
16 |
> sure you don't ever set it as the system vm. |
17 |
|
18 |
Very true. Just to clear up any confusion for others on the list, this |
19 |
means that if you are trying to run a 1.5 JDK as the primary on your |
20 |
system at the same time you have a 1.4 JDK running, the 1.4 JDK will be |
21 |
unable to use most of the code compiled from the 1.5 JDK (by default). |
22 |
|
23 |
Since most packages on the Gentoo distro compile themselves from source |
24 |
(Java included), having a 1.5 JDK as your *system VM* means that your |
25 |
Java applications would be compiled so that ONLY Java 5 (and higher) |
26 |
runtimes could use the applications. This is a show-stopper for those |
27 |
still running a 1.4 JDK (at least for non-developers, who should know |
28 |
how to deal with this stuff anyway): |
29 |
|
30 |
Choices: |
31 |
|
32 |
* Run only 1.5 or higher on your system (with no intention of ever |
33 |
going back down). Note that as of a while ago certain packages |
34 |
in the Portage tree still required 1.4, so this approach may |
35 |
preclude installing those packages from Portage. |
36 |
--OR-- |
37 |
* Take Petteri's advice and leave 1.4 as the system VM, and set |
38 |
your "user" VM to 1.5 (or higher) if desired. |
39 |
|
40 |
HTH to clarify... |
41 |
|
42 |
Greg |