🚀 go-pugleaf

Noah:

The control you seek is in the use of the JRE to distribute your
application.  Deploy your application with the version of the JRE that
matches the JDK you have tested/developed against.  It won't stop
someone from trying to use an earlier or later one if they want, but
you  have done everything you can from your side by giving them the one
that works.

If it's an applet, you are SOL -- none of the browsers support the
latest JDK so coding against it doesn't make all that much sense unless
you are about 8 months from completion and don't plan to take another
JDK.

-Rich

Noah Clements wrote:
> 
> On Mon, 08 Dec 1997 10:44:32 -0800, Andrew Bennett
> <abennett@borland.com> wrote:
> 
> >
> >
> >Derek Cribbs wrote:
> >
> >> I was wondering if anyone knows how borland is handling patches to fix
> >> bugs and also how to update JDK in Jbuilder. It ships with JDK 1.1.3 and
> >> JDK 1.1.5 is out now. How are they addressing these issues?
> >
> >We haven't announced anything yet.  When something is available, I'll
> >post it in jbuilder.announce.  So, you may want to watch that group.
> >
> >JDK 1.1.4 and 1.1.5 are just bug fixes above what we have.  As a result,
> >integrating a new JDK would take a significant amount of QA effort to
> >ensure that all the Java code we are using still works.  And if problems
> >are found, research into those problems and the creation of a work
> >around just lengthens the cycle.  Repeat until finished.
> >
> >As such, the code you create in JBuilder should run in 1.1.5 already,
> >assuming 1.1.5 has no new bugs in it that break your code.
> >
> Andrew,
> 
> I downloaded JDK1.1.5 and installed it on my machine and found that
> since they fixed some of their bugs (for me, notable the Print ones on
> win32), running applications in this environment broke some of my
> workarounds (using the same example, placement workarounds for drawing
> graphics on the print context).  So I can definitely see your point in
> making sure that you test a new JDK thoroughly before updating.
> 
> 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?
> 
> Thanks,
> 
> Noah