🚀 go-pugleaf

Noah Clements wrote:

> However, this seems to bring up an interesting problem.  How do we
> control which JVM (or even version of JDK 1.1) our clients are using?
> If I distribute an application which works well on JBuilder's JVM and
> JDK 1.1.3, and my client has JDK 1.1.5 installed (or vice versa), and
> implementation details require some workarounds, how can we make sure
> that our application still works?
>
> We certainly can't require that one version of the JDK is used over
> another as there may be other applications the client is using which
> require the other version.  Is the solution to include a classes.zip
> with all applications and reset classpaths with a batch file/script
> like the one you guys include with JBuilder?

Well, like Rich posted, you can package it with a JRE, and use
batch files to set environment variables and do the launching.

That works for applications fine and dandy.  But what about
applets?

Could be iffy.  But with any Java app, you can pull some of
the properties from java.lang.System's getProperty call, like
java.version, java.vendor, java.class.version, etc.  Then,
based on these, throw warnings that said app hasn't been
tested on this platform, and anomalies may result.



Andrew
--
  Andrew Bennett            ->  abennett@borland.com
  JBuilder info             ->  http://www.borland.com/jbuilder/
  JBuilder newsgroups info  ->  http://www.borland.com/newsgroups/
**** Please don't post a reply AND send email.  Do one.  I'll see it. ****