Re: [gentoo-java] Question about Sun-Jdk 1.4.2.10

[Greg Tassone <greg@tassone.net>]

[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]

On Wed, 2005-11-30 at 22:39 +0000, Peter B. West wrote:
> Joshua Nichols wrote:
> >>So who wants to run a 1.4 JDK?  And what, exactly, prevents anything
> >>from being compiled under 1.5?  The only thing I can think of is the
> >>user of the newly reserved word 'enum'.  Big deal.  How long has 1.5
> >>been around now?
> > 
> > Have you actually tried using a 1.5 JDK to emerge your system? I'm
> > guessing not, because xerces, xalan, and dom4j won't compile with 1.5,
> > and they are pretty critical XML libraries that lots of things use.
> > 
> 
> See my response to the "ant won't compile" message.  Same story, at 
> least partially.
> 
> Download sources for Xerces-J. Read README, which tells me I need the 
> tools.  Download the tools.  Extract "in the same directory."  What does 
> that mean? Read build.sh. Ah, tools is in the Xerces directory. Do that. 
>   Run sh build.sh jars. Result:
> 
> BUILD SUCCESSFUL
> Total time: 13 seconds
> 
> Do I really have to do this with Xalan as well?  Java 5 ships with 
> xerces as its parser, in place of crimson. That's in the incompatibility 
> notes. It ships with xalan, and defaults to using xsltc. Also in the 
> incompatibility notes.  (And xalan 2.7.0 has one reported bug that I 
> know of that causes problems with netbeans 5.0).
> 
> The simple fact is that I can pick up any of the binaries and they will 
> almost certainly run without problems.  There are a handful of obscure 
> binary-level incompatibilities, but the only problem I have encountered 
> is the netbeans bug I mentioned; not an incompatibility.
> 
> Peter


I think you're missing one of the main points here... he did NOT say
that they would not compile at all -- he said they would not compile on
the current Gentoo ebuild base (e.g., "... using a 1.5 JDK to emerge
your system").

Then, did you see the rest of his message, the part talking about the
1.5 overlay that is being worked on?  The main point of the overlay is
to get these "incompatibilities" resolved.  Then the "fixed" ebuilds
from the overlay can become mainstream in Portage.

This stuff takes time, especially when system-level stability issues
stand in the balance.

Greg


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]