🚀 go-pugleaf

According to Borland they solved the problem in JBuilder 3.  What they said was
when JBuilder 2 came out the made it on the Sun spec and then Sun changed the
spec and that is why the thing with JBuilder 2 does work that well.  I read it a
while ago on one of the news groups.

Kobus

Ronen wrote:

> I am using JBuilder 2 and I have the same problem as mentioned below.
> Is there anyway to solve this?
>
> Ronen,
>
> Kobus du Toit <battlezone@iname.com> wrote in message
> news:37CA4EB7.78C9BB31@iname.com...
> > Are you using JBuilder 2 or 3, because I know JBuilder 2 gave that problem
> and I
> > think Borland also talked about that a long time ago.
> >
> > Kobus
> >
> > zaf wrote:
> >
> > > Ok with putting rt.jar in the path. Now some new problems:
> > >
> > > 1. jbuilder reports not finding the JIT compiler, and that it will
> interpret
> > > instead
> > > 2. jbuilder reports not finding a debug version, so debugging is not
> > > possible with jdk1.2.2
> > >
> > > Tor Iver Wilhelmsen <tor.wilhelmsen@sds.no> wrote in message
> > > news:uk8qhxxpy.fsf@sds.no...
> > > > "zaf" <zaf@hol.gr> writes:
> > > >
> > > > > In project properties, a user can define a new JDK. The Java 2
> package
> > > from
> > > > > SUN does not include a classes.zip file (as stated in the
> installation
> > > > > instructions page it is not required any more), so the classes field
> in
> > > the
> > > > > JDK definition form cannot be filled.
> > > >
> > > > No, they're in \lib\rt.jar now. Put the path to that JAR into the
> > > > classes field.
> >