🚀 go-pugleaf

Rob:

Here it is again... <g>  (It stands a chance of becoming a FAQ after
everyone comes back from BorCon)...

-Rich
........
Unfortunately JavaSoft changed quite a few things in JDK1.2beta4 that
had been consistent with every other JDK from 1.02 on.  As a result,
JBuilder cannot correctly determine the name of the JDK or the
classpath.  The former is a cosmetic problem, the latter just requires
manual intervention.

Configure the JDK as you would normally, creating a new JDK and
specifying a path to JAVA.EXE.  Ignore the unusual name for now.
Manually edit the CLASSPATH for the new JDK so that it reads
"c:\jdk1.2beta4\jre\lib\rt.jar" adjusted for your installation
directory.  Press OK and wait for the dependancy files to be built.

You can use this JDK without any difficulty, but you do get an unusual
name listed.  If you want to correct this, you can exit JBuilder and
manually edit the file c:\JBuilder2\bin\LIBRARY.INI by hand.  Replace
line with the offending name with the following:

[JDK_java version "1.2beta4"]
That should be enough to let you work with the beta.  We will have an
interim release of JBuilder available to address the problem for real
in the not too distant future.




Rob Williams wrote:
> 
> I was following the advice in the servlet example about adding 1.2 as the
> JDK and it just doesn't work.  Far as I can tell, it's because the names of
> some of the files (i.e. classes.zip) have changed.  What is the solution?  I
> need to get doing Servlets.
> 
> Thanks,
> --
> Rob Williams
> RobCo Incorporated

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=