SUGGESTED FIX
I verified that IPS is procesing the Java DB files as expected.
From Dag, Wanvik
did a quick status check, results were as expected:
In all cases the bundles had Java DB 10.6.2.1 in the db directory. The
build containing the push we did yesterday of 10.8.1.2 will hopefully
appear soon.
/hudsonws/jdk7/bundles/linux-i586/b142-2011-05-10_241/jdk-7-ea-linux-i586.rpm
- OK, only db + demo/db directories as expected
/hudsonws/jdk7/bundles/solaris-i586/b142-2011-05-10_241/jdk-7-ea-solaris-i586.tar.Z
- not yet OK, has both db directory from SUNWj7dev + demo/db
from SUNWj7dmo (correct), as well as separate SUNWjavadb-*
packages (should go away)
/hudsonws/jdk7/bundles/windows-i586/b142-2011-05-10_241/jdk-7-ea-windows-i586.exe
- OK, <jdk>/db subdirectory present. I could not see an extra
Sun/JavaDB directory being installed any longer. Optional demo
install seen.
PS! An "anomaly" I noticed: the installer asked for the
directory to use for *JRE*, but not for the JDK. Both appeared
in Program Files, though, the JRE twice, once inside the JDK and
once under Program Files. I suppose this is as it should be(?).
|
EVALUATION
The JavaDB team provides files to RE that contain JavaDB implementation. These files are put into the SUNW SVR4 java packages, not the javadb SVR4 packages. The IPS build process treats the Java DB files as any other artifact and places the files in the correct locations based on the package they are in, jdk or demos and samples.
|
Java