From: Ted K. <te...@op...> - 2005-04-06 01:07:08
|
I upgraded xalan231.jar to xalan-j2-2.6.0.jar(jpackage version). Build went fine and everything appears to be playing well. Attached are the two jars manifests. Just edited the build.xml, testing on FC3. Going to tackle these one at a time, my long term goal is to get us to running with all newer libs and tomcat versions. Right off the bat I noticed that jpackage has a seperate rpm for tomcat4-jasper, which conflicts with the tomcat4-4.1.18-full.1jpp.noarch.rpm. Would it be possible to get a branch setup for this? Ted |