🚀 go-pugleaf

Randall Fairman wrote:
> I sort of solved the problem, though there is something mysterious about it 
> all.
> 
> I noticed that a directory jb.install.vm had been created in my home 
> directory. I copied its contents to JBuilder2005/jdk1.4 and it worked.
> 
> I ought to be able to use other JVMs if I want to though, right?
> 
> Randall
> 

In general, JBuilder is supported only on the JDK with which it was 
released.

That being said... it is also only supported on the platforms on which 
it has been tested.  I don't believe that Fedora Core 4 is one of them.

So what does that mean?  If you are running on an unsupported platform 
anyway, you can twiddle whatever you want, just don't expect get 
"official" support when things go wrong.  And in case you wondered, this 
newsgroup would be classified as "un-official" support. ;-)

Back to the topic at hand... Other JVM's.  Sticking to the same 
major/minor release (for JB2005, JDK 1.4.2) is pretty safe, while 
switching to a different release (1.4.1 or 1.5) is pretty unsafe.  My 
personal preference on Linux (and Solaris) for switching the JDK is to 
make use of soft links.  Just rename the original JDK directory that 
JBuilder is using, and then replace it with a soft link that points to 
the JDK you want to use.  Much easier than mucking about in the 
configuration files.

-- 

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
     http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
     http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
     http://www.visi.com/~gyles19/fom-serve/cache/1.html