🚀 go-pugleaf

J.R.:

Actually, it's 1.2.0 and JBuilder went to manufacturing about a week
before 1.2.0 was available to the public.  We've always been very close
on the hosted JDK.

I shudder to think what'll happen to you if you hear about JDK 1.3 if
1.2.2 is killing you <g>.

You might be confusing some of Javasofts' code comments with the JDK
version, however.  There are "sub projects" at Javasoft and their
version numbers have no bearing on the JDK version.  JFC is one of those
sub projects, for example.

-Rich

"J. R. Antley" wrote:
> 
> Hi Raj,
> 
> It appears to me that "versionitis" is one of the biggest problems faced in
> Java.  The source which ships with JBuilder3 is about 8 months behind Sun's
> 1.2.2, although they are both called 1.2.2.  It's killing me!
> 
> Sigh,
> JR
> 
> Raj Kumar <Raj.Kumar@qwest.com> wrote in message
> news:7r6io9$m6r3@forums.borland.com...
> > Hi,
> >
> >   What JDK and swing version Ship with JBUILDER3.0
> >
> >   After buying jbuilder 3.0 , can i switch to latest release of JDK
> >
> > Thanks
> >
> > Raj
> >
> >

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Quality Assurance Manager
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=