-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
7-pool
-
None
-
generic
-
linux
BACKGROUND
JRockit includes a few patches of the JDK. In order to simplify the JRockit JDK updating process, we want to move as many as possible of these to the Java SE JDK.
PROBLEM
JRockit has always had a lot of customers in Asia, running on Asianux. For fonts to be displayed properly, we need fontconfig files for Asianux
In JRockit, the files we add are (in jre/lib):
* fontconfig.Asianux.bfc
* fontconfig.Asianux.1.0.bfc
* fontconfig.Asianux.1.0.properties.src
* fontconfig.Asianux.2.0.bfc
* fontconfig.Asianux.2.0.properties.src
* fontconfig.Asianux.properties.src
The way we do this is that we simply copy the RedHat files:
* fontconfig.RedHat.3.* => fontconfig.Asianux.1.0.*
* fontconfig.RedHat.4.* => fontconfig.Asianux.2.0.*
* fontconfig.RedHat.* => fontconfig.Asianux.*
Is this something we could do in the Java SE JDK as well? Doing this would:
a) Simplify the JRockit JDK update process by removing one step of the patching
b) Allow the Asianux users to go over to the merged JVM in the future
If this would be possible, I will create sub SRs for 1.4.2, 1.5.0 and 1.6.0
JRockit includes a few patches of the JDK. In order to simplify the JRockit JDK updating process, we want to move as many as possible of these to the Java SE JDK.
PROBLEM
JRockit has always had a lot of customers in Asia, running on Asianux. For fonts to be displayed properly, we need fontconfig files for Asianux
In JRockit, the files we add are (in jre/lib):
* fontconfig.Asianux.bfc
* fontconfig.Asianux.1.0.bfc
* fontconfig.Asianux.1.0.properties.src
* fontconfig.Asianux.2.0.bfc
* fontconfig.Asianux.2.0.properties.src
* fontconfig.Asianux.properties.src
The way we do this is that we simply copy the RedHat files:
* fontconfig.RedHat.3.* => fontconfig.Asianux.1.0.*
* fontconfig.RedHat.4.* => fontconfig.Asianux.2.0.*
* fontconfig.RedHat.* => fontconfig.Asianux.*
Is this something we could do in the Java SE JDK as well? Doing this would:
a) Simplify the JRockit JDK update process by removing one step of the patching
b) Allow the Asianux users to go over to the merged JVM in the future
If this would be possible, I will create sub SRs for 1.4.2, 1.5.0 and 1.6.0