NOTE: I'm filing this against 1.5.0_01 only because I don't see an
entry for 1.5.0 for 'Release'.
I noticed a problem when installing the FCS version of JDK 1.5.0 after
uninstalling JDK 1.5.0 beta3 (build55).
The basic problem was that:
- in beta3, JDK 1.5.0 created a /usr/jdk/jdk1.5.0 directory (it wasn't
a symlink like it is in FCS)
- For beta3, I had installed:
SUNWj5rt SUNWj5dev SUNWj5cfg SUNWj5man SUNWj5dmo *and* SUNWj5jmp
but when I decided to upgrade to JDK 1.5.0 FCS I uninstalled JDK 1.5.0
beta by pkgrm'ing everything *but* SUNWj5jmp. I was following the
instructions at:
http://java.sun.com/j2se/1.5.0/install-solaris.html#install-pkg
This leaves the /usr/jdk/jdk1.5.0 directory intact. the instructions
above did not say to pkgrm SUNWj5jmp prior to pkgadd'ing the main
JDK 1.5.0 FCS pkgs.
So now, when I install JDK 1.5.0 FCS, via
% pkgadd -d . SUNWj5rt SUNWj5dev SUNWj5cfg SUNWj5man SUNWj5dmo
/usr/jdk looks like:
% ls -l
total 4
drwxr-xr-x 3 root bin 512 Oct 5 15:13 instances/
drwxr-xr-x 3 root bin 512 Oct 5 15:13 jdk1.5.0/
/usr/jdk/jdk1.5.0 looks like:
% ls -l
total 4
lrwxrwxrwx 1 root other 18 Oct 5 15:13 jdk1.5.0 -> instances/jdk1.5.0
drwxr-xr-x 5 root bin 512 Oct 5 15:12 man/
I'm guessing some install script is attempting to do the following
in /usr/jdk:
ln -s instances/jdk1.5.0 jdk1.5.0
but since jdk1.5.0 exists and is a directory, it creates the "jdk1.5.0"
symlink inside the /usr/jdk/jdk1.5.0 direcotry.
This causes the JDK to be installed incorrectly. Most importantly, the
path /usr/jdk/jdk1.5.0/bin/java does not exist.
I am not sure if this is a problem with the SUNWj5* packages or whether the
instructions at http://java.sun.com/j2se/1.5.0/install-solaris.html#install-pkg
need to be updated or both, but at the very least, shouldn't the script that
creates the link check first if /usr/jdk/jdk1.5.0 exists ?
There might be other scenarios where bits are installed under /usr/jdk/jdk1.5.0
and pkgrm'ing just the beta3 SUNWj5* pkgs would leave /usr/jdk/jdk1.5.0
intact.
###@###.### 10/5/04 22:48 GMT
###@###.### 10/5/04 23:05 GMT
entry for 1.5.0 for 'Release'.
I noticed a problem when installing the FCS version of JDK 1.5.0 after
uninstalling JDK 1.5.0 beta3 (build55).
The basic problem was that:
- in beta3, JDK 1.5.0 created a /usr/jdk/jdk1.5.0 directory (it wasn't
a symlink like it is in FCS)
- For beta3, I had installed:
SUNWj5rt SUNWj5dev SUNWj5cfg SUNWj5man SUNWj5dmo *and* SUNWj5jmp
but when I decided to upgrade to JDK 1.5.0 FCS I uninstalled JDK 1.5.0
beta by pkgrm'ing everything *but* SUNWj5jmp. I was following the
instructions at:
http://java.sun.com/j2se/1.5.0/install-solaris.html#install-pkg
This leaves the /usr/jdk/jdk1.5.0 directory intact. the instructions
above did not say to pkgrm SUNWj5jmp prior to pkgadd'ing the main
JDK 1.5.0 FCS pkgs.
So now, when I install JDK 1.5.0 FCS, via
% pkgadd -d . SUNWj5rt SUNWj5dev SUNWj5cfg SUNWj5man SUNWj5dmo
/usr/jdk looks like:
% ls -l
total 4
drwxr-xr-x 3 root bin 512 Oct 5 15:13 instances/
drwxr-xr-x 3 root bin 512 Oct 5 15:13 jdk1.5.0/
/usr/jdk/jdk1.5.0 looks like:
% ls -l
total 4
lrwxrwxrwx 1 root other 18 Oct 5 15:13 jdk1.5.0 -> instances/jdk1.5.0
drwxr-xr-x 5 root bin 512 Oct 5 15:12 man/
I'm guessing some install script is attempting to do the following
in /usr/jdk:
ln -s instances/jdk1.5.0 jdk1.5.0
but since jdk1.5.0 exists and is a directory, it creates the "jdk1.5.0"
symlink inside the /usr/jdk/jdk1.5.0 direcotry.
This causes the JDK to be installed incorrectly. Most importantly, the
path /usr/jdk/jdk1.5.0/bin/java does not exist.
I am not sure if this is a problem with the SUNWj5* packages or whether the
instructions at http://java.sun.com/j2se/1.5.0/install-solaris.html#install-pkg
need to be updated or both, but at the very least, shouldn't the script that
creates the link check first if /usr/jdk/jdk1.5.0 exists ?
There might be other scenarios where bits are installed under /usr/jdk/jdk1.5.0
and pkgrm'ing just the beta3 SUNWj5* pkgs would leave /usr/jdk/jdk1.5.0
intact.
###@###.### 10/5/04 22:48 GMT
###@###.### 10/5/04 23:05 GMT