1 |
On Wed, 2005-11-30 at 22:39 +0000, Peter B. West wrote: |
2 |
> Joshua Nichols wrote: |
3 |
> >>So who wants to run a 1.4 JDK? And what, exactly, prevents anything |
4 |
> >>from being compiled under 1.5? The only thing I can think of is the |
5 |
> >>user of the newly reserved word 'enum'. Big deal. How long has 1.5 |
6 |
> >>been around now? |
7 |
> > |
8 |
> > Have you actually tried using a 1.5 JDK to emerge your system? I'm |
9 |
> > guessing not, because xerces, xalan, and dom4j won't compile with 1.5, |
10 |
> > and they are pretty critical XML libraries that lots of things use. |
11 |
> > |
12 |
> |
13 |
> See my response to the "ant won't compile" message. Same story, at |
14 |
> least partially. |
15 |
> |
16 |
> Download sources for Xerces-J. Read README, which tells me I need the |
17 |
> tools. Download the tools. Extract "in the same directory." What does |
18 |
> that mean? Read build.sh. Ah, tools is in the Xerces directory. Do that. |
19 |
> Run sh build.sh jars. Result: |
20 |
> |
21 |
> BUILD SUCCESSFUL |
22 |
> Total time: 13 seconds |
23 |
> |
24 |
> Do I really have to do this with Xalan as well? Java 5 ships with |
25 |
> xerces as its parser, in place of crimson. That's in the incompatibility |
26 |
> notes. It ships with xalan, and defaults to using xsltc. Also in the |
27 |
> incompatibility notes. (And xalan 2.7.0 has one reported bug that I |
28 |
> know of that causes problems with netbeans 5.0). |
29 |
> |
30 |
> The simple fact is that I can pick up any of the binaries and they will |
31 |
> almost certainly run without problems. There are a handful of obscure |
32 |
> binary-level incompatibilities, but the only problem I have encountered |
33 |
> is the netbeans bug I mentioned; not an incompatibility. |
34 |
> |
35 |
> Peter |
36 |
|
37 |
|
38 |
I think you're missing one of the main points here... he did NOT say |
39 |
that they would not compile at all -- he said they would not compile on |
40 |
the current Gentoo ebuild base (e.g., "... using a 1.5 JDK to emerge |
41 |
your system"). |
42 |
|
43 |
Then, did you see the rest of his message, the part talking about the |
44 |
1.5 overlay that is being worked on? The main point of the overlay is |
45 |
to get these "incompatibilities" resolved. Then the "fixed" ebuilds |
46 |
from the overlay can become mainstream in Portage. |
47 |
|
48 |
This stuff takes time, especially when system-level stability issues |
49 |
stand in the balance. |
50 |
|
51 |
Greg |