>>>>> "rchase" == rchase <[EMAIL PROTECTED]> writes:
rchase> I haven't had to work with both JDKs yet but I may have to
rchase> soon. I was thinking that I would be able to switch easily
rchase> between JDK 1.1.x and JDK 1.2 by defining all the necessary
rchase> settings and saving them in a project file. Wouldn't this
rchase> provide an easy way to switch JDKs? Of course, that's
rchase> assuming that you're not using both JDKs for the same
rchase> project. (Would anyone actually want to do that?)
An applet project.
What ever people say if you want to write code which
works on all browsers you still write in 1.0 code (let alone 1.1).
However there is no reason to write the server side in 1.0. Hence my
first project was 1.1/1.0. Some classes were used both sides, some
server only, some client only. The packages didnt work out as either
1.1, or 1.0 when I wrote this, hence I didnt find "projects" that
helpful. What I ended up doing was writing a 1.1 prj.el, and a 1.0
prj.el and then loading them from a menu which I gave the rather twee
name of "JDE+". This way I switched JDK when I wanted rather then when
JDE noted a changed project.
rchase> With regards to your hopes that JDK 1.1.x will just go away,
rchase> well, I'm a little skeptical. Many Java developers (such as
rchase> myself) live in a world where things like multi-platform
rchase> browser support is a prime concern, and I'm not convinced
rchase> that multi-platform browser support for JDK 1.2 is that
rchase> close.
This is fairly irrelevant though. Developers have a choice
over what tools they use. Most people coding java will have a 1.2 JDK
on their machine. Theres nothing to stop you using 1.2 with the
changed command line tools, to compile 1.1, or 1.0 code. In fact all
you need to do to "switch" JDK's is alter the (boot)classpath to point
to the older classes. At least this is more or less what I used to do
with 1.0/1.1. I image it will still work with 1.1/1.2.
Phil
