tag:blogger.com,1999:blog-741750605858169835.post1099832344351816818..comments2024-01-24T14:53:02.919+00:00Comments on Stephen Colebourne's blog: Compiling for older JDKsStephen Colebournehttp://www.blogger.com/profile/01454237967846880639noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-741750605858169835.post-38824587219082874382005-07-01T00:55:56.000+01:002005-07-01T00:55:56.000+01:00Yup, -bootclasspath is what you want. There have b...Yup, -bootclasspath is what you want. There have been various bugs fixed in javac over the versions. I had a situation in which an old javac was creating illegal byte code just as my system went live. Generally it is safest to use the latest JDK with -source, -target and -bootclasspath.Tom Hawtinhttp://jroller.com/page/tackline/noreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-7745814799382010082005-06-27T05:30:27.000+01:002005-06-27T05:30:27.000+01:00I have a similar situation at work. The programs I...I have a similar situation at work. The programs I write need to work on Personal Java, which is basically a subset of the JDK 1.1 API (with a smidgen of JDK 1.2 APIs, just to spice things up). Unfortunately, my code sometimes runs afoul of a compiler bug that wasn't fixed until JDK 1.4, so compiling with the JDK 1.1 compiler is out of the question. The solution of course is to set *both* the -source and -target compiler switches to 1.1 and provide the JDK 1.1 classes.zip in the -bootclasspath switch. Doing all three things means there are no compatibility problems.Kevinnoreply@blogger.com