🚀 go-pugleaf

I agree with comments.  When I purchased JBuilder 2, the box indicated that
it works with JDK1.2.  To then pay more for JBuilder 2.01 and find that
support for JDK1.2 is incomplete is intolerable.

I am seriously considering reporting inprise to UK trading standards.


Wray Johnson wrote in message <76c7gv$qln1@forums.borland.com>...
>INPRISE Please help one of your most loyal advocates!!!!
>
>!I just received my JBuilder 2.01 C/S upgrade CD.  I uninstalled and
>reinstalled everything.  I installed JDK 1.2.
>
>1.  When I added java version "1.2" to the Target JDK version in the
Project
>Properties or Default Project Properties dialog box I received the error
>that it could not build the dependency files after it attempted to scan the
>JDK.  FYI: I installed the JDK 1.2 in the "C:\JDK1.2" directory.
>
>2.  I cannot debug with JDK 1.2 - what gives?  NEW YORK -- December 9, 1998
>"Inprise Corporation Announces Immediate Support For The Java� 2 Platform"
>What good is it if debugging is not supported?  When can I expect to be
able
>to debug with JDK 1.2?  I love JBuilder C/S but this leaves a sour taste in
>my mouth!
>
>3. An to top it off when I attempt to run without debug mode I get the
>following:
>
>Warning: JIT compiler "javacomp" not found.  Will use interpreter.
>Exception in thread "main" java.lang.VerifyError: (class:
>COM/ure/orm/Application1, method: main signature: ([Ljava/lang/String;)V)
>Incompatible argument to function
>
>
>