-
Bug
-
Resolution: Fixed
-
P4
-
1.3.0
-
None
-
beta
-
sparc
-
solaris_2.5.1
Currently all classes are built into
build/<platform>/classes
and then a scripts are run (jreimage.sh, jdkimage.sh and Release.gmk)
to package a jre-image-<platform> and a jdk-image-<platform>.
This is very broken. We should build the product the same way
as we ship it. The release engineering step should be no more
complicated than taking the contents of a classes/ directory
and packaging it into a .jar file. The reason that we have the
post-processing scripts is that there was no time to implement the
cleaner solution in 1.2. 1.3 is a good timeframe to clean this up.
This is what I have in mind:
build/solaris/jre/java/jvm/GNUmakefile
build/solaris/jre/bin/java
etc. and:
build/solaris/tools/javac/GNUmakefile
build/solaris/tools/bin/javac
etc.
This would be a good project for someone in release engineering
who would like to get intimate with the JDK makefiles.
I'd be happy to review the changes.
anand.palaniswamy@Eng 1999-05-25
build/<platform>/classes
and then a scripts are run (jreimage.sh, jdkimage.sh and Release.gmk)
to package a jre-image-<platform> and a jdk-image-<platform>.
This is very broken. We should build the product the same way
as we ship it. The release engineering step should be no more
complicated than taking the contents of a classes/ directory
and packaging it into a .jar file. The reason that we have the
post-processing scripts is that there was no time to implement the
cleaner solution in 1.2. 1.3 is a good timeframe to clean this up.
This is what I have in mind:
build/solaris/jre/java/jvm/GNUmakefile
build/solaris/jre/bin/java
etc. and:
build/solaris/tools/javac/GNUmakefile
build/solaris/tools/bin/javac
etc.
This would be a good project for someone in release engineering
who would like to get intimate with the JDK makefiles.
I'd be happy to review the changes.
anand.palaniswamy@Eng 1999-05-25