RE: 'Available' in java cent builds..

Nicola wrote:

	The distro should ship built with the api usage of the lowest possible
	JDK. Actual builds are done with the highest JDK that is compatible.
	This practically means use JDK1.3 for builds that don't need DB stuff
	and ship double-versions of the releases if using DB stuff (1.4 is
	incompatible :-( )

The problem I have is that I 'need' JDK1.4 at built time (or a smart build)
so I can use (say) java.util.logging, but then at runtime if the underlying
JDK classes are not there I fallback ok. Building a JDK1.4 gives class
format 48.0 or something, unless one can set switches (I guess), which (from
my experience) JDK1.3 and such do not like.

I guess I can move the jdk14 stuff into yet another project (if I can figure
out how to make centipede build the extra ones, right now I can't, any
pointers?) If I have a jdk14 project then perhaps it can be built w/JDK1.4
and everything else be built with JDK1.3 (or JDK1.2, whatever).

In making a second (optional) package (with dependencies) I wonder if I've
been a bit mean on the user. They now have two JARs to have to add to their
classpath, right?

This will (probably) work for me, but I am still interested in working with
somebody on an 'available' (class and/or version) sensitive javac cent.
Anybody game?

regards,

Adam



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com