🚀 go-pugleaf

My understanding is that JBuilder cannot easily (at all?) be used with
more recent JDK's, because it (like other IDE's) is built on a modified
JDK itself.

What are Borland's plans to fix this? From the point of view of anyone
whose application is being built for, say, six months down the line, not
using the very latest JDK features is suicidal - the app will be
obsolete on release without, for instance, a Swing and Java 2D look and
feel.

Specificly, will the next version of JBuilder allow easy JDK upgrades by
the user? And if so, when will it be out? I'd rather not have to put
JBuilder aside as a pretty toy, and work from the command line; but if
it can't do 1.2 at this point, there's no other choice for a responsible
developer. Since Java will keep advancing, this will always be an issue.

 \/\/ I-I I T 
 Blauvelt
 whit@transpect.com