Message-ID: <OF08BEF99B.91055741-ONCA2569BB.001CF027@accenture.com> From: paul.c.leopardi@accenture.com Date: Wed, 20 Dec 2000 15:19:15 +1000 Subject: Problems configuring Java 1.2 using IBM Java 2 Hi, Here is a copy of the KDE bug report for bug #17398 at http://bugs.kde.org//db/17/17398.html It is more a deficiency in packaging and documentation than a KDE bug as such. Best regards Package: kjava Version: KDE 2.1 beta 1 Severity: normal Installed from: SuSE 7.0 RPMs on ftp.kde.org Out of the box, konqueror can't find Java 1.2. Java 1.2 does not install automatically in the SuSE 7.0 installation and it is not included in the SuSE 7.0 RPMs for KDE 2.1. After learning this, I then installed the IBM Java 2 JDK and JRE from the SuSE 7.0 CDs. Packages ibmjava2 ( http://www.suse.de/en/produkte/susesoft/linux/Pakete_prof/paket_ibmjava2.htm... ) and ibmjre2 ( http://www.suse.de/en/produkte/susesoft/linux/Pakete_prof/paket_ibmjre2.html ) Also, I had links in /usr/lib which were appropriate for my recent VisualAge Java installation which had used JDK 1.1.7 and JRE 1.1.7 and I needed to sort these out and update them to 1.3. The konqueror documentation for KDE 2.1 pointed me at the configuration screen for Java/JavaScript for konqueror. After some guessing, trial and error, I changed this to point Java to /usr/lib/jdk1.3/jre (and not /usr/lib/jdk1.3 or /usr/lib/jre1.3 ) I needed to guess because there is no documentation to say which is the appropriate directory, what the directory structure should be or what within the directory structure konqueror is looking for. This works except that the Java console launches even though I have not checked the box on the configuration screen. I will try again using package java2 ( http://www.suse.de/en/produkte/susesoft/linux/Pakete_prof/paket_java2.html ) and will then report all details to feedback@suse.de The most likely results of this bug report are: (1) A change in the documentation to make it easier to configure Java 1.2 (2) A change in packaging on some distributions, especially those which will use KDE 2 as the default window manager, to make KDE 2 installation optionally work with Java "out of the box" without the user having to guess how to configure it. Also, the documentation at http://developer.kde.org/kde2arch/khtml/index.html seems to be out of date, in that it does not refer to the konqueror configuration screen but instead refers to CLASSPATH. Richard Moore:"Not installing a JVM is not a bug, it's a feature. Not all users want Java, and the JVMs are only available for a subset of the platforms supported by KDE. Add to this the huge size of a complete Java 2 run time and various licensing issues, and you can see why we leave it to the distribution. " See http://dot.kde.org/977039397/977182504/977185373/ <p>This message is intended solely for the designated recipient, may contain privileged or confidential information and may be subject to confidentiality agreement(s). Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please notify the sender immediately by reply e-mail and destroy the original communication.