Hi all,
This is Kris Mok. I was building the master branch of MRP (
http://mrp.codehaus.org/) the other day, and hit a few problems involving an
older milestone of Harmony. It wasn't hard to solve this particular issue;
my question is how should we maintain older milestones generally, so that
they can still be built a few years later?
I chose to use Harmony as the class library provider for the MRP build (as
opposed to GNU Classpath). The build process would automatically pull
Harmony 5.0M10p0 (rev 782693) from svn, and try to build Harmony first.
During the build, a few dependencies have been found to be no longer
available. I had to tweak things a little bit just to get the build go on.
sa...@sajia-laptop:~/build/mrp/components/harmony/5.0M10p0/harmony$ svn st
? depends/jars/xerces_2.10.0
M modules/archive/src/main/native/archive/unix/exports.txt
M make/depends.xml
M make/depends.properties
sa...@sajia-laptop:~/build/mrp/components/harmony/5.0M10p0/harmony$ svn di
Index: modules/archive/src/main/native/archive/unix/exports.txt
===================================================================
--- modules/archive/src/main/native/archive/unix/exports.txt (revision
782693)
+++ modules/archive/src/main/native/archive/unix/exports.txt (working
copy)
@@ -33,3 +33,4 @@
Java_java_util_zip_ZipFile_openZipImpl
JNI_OnLoad
JNI_OnUnload
+zipCachePool_new
Index: make/depends.xml
===================================================================
--- make/depends.xml (revision 782693)
+++ make/depends.xml (working copy)
@@ -84,7 +84,7 @@
<target name="-extract-xerces" unless="xerces.uptodate">
<unzip src="${xerces.zip}" dest="${xerces.dir}.tmp" />
<copy todir="${xerces.dir}" flatten="yes">
- <fileset dir="${xerces.dir}.tmp/xerces-2_9_1">
+ <fileset dir="${xerces.dir}.tmp/xerces-2_10_0">
<include name="resolver.jar" />
<include name="xercesImpl.jar" />
<include name="xml-apis.jar" />
Index: make/depends.properties
===================================================================
--- make/depends.properties (revision 782693)
+++ make/depends.properties (working copy)
@@ -24,10 +24,10 @@
xalan.url=${maven2.base}/xalan/xalan/2.7.0/xalan-2.7.0.jar
xalan.md5=a018d032c21a873225e702b36b171a10
-xerces.dir=${depends.jars}/xerces_2.9.1
+xerces.dir=${depends.jars}/xerces_2.10.0
xerces.zip=${xerces.dir}/xerces.zip
-xerces.url=http://www.apache.org/dist/xml/xerces-j/Xerces-J-bin.2.9.1.zip
-xerces.md5=a0e07ede1c3bd5231fe15eae24032b2e
+xerces.url=http://www.apache.org/dist/xerces/j/Xerces-J-bin.2.10.0.zip
+xerces.md5=8da14a7b2848eff131b7cc10668887e8
junit.dir=${depends.jars}/junit_4.4
junit.jar=${junit.dir}/junit.jar
As shown above, Xerces 2.9.1 just isn't there anymore. The only version I
can find on the Apache site now is 2.10.0. I knew I should modify
depends.properties, but missed the version number in a path in depends.xml.
It wasn't hard, but rather just tedious to get everything going.
Should I submit a patch for this, or are there any existing mechanisms that
keep older milestones build-able as time move on? There might be projects
out there that depends on these older milestones.
Regards,
Kris Mok
