Re: Upgrading Batik
Brian M Dube wrote: On Sat, Jan 08, 2011 at 12:44:13PM +1100, David Crossley wrote: Brian M Dube wrote: The Jing discussion reminded me of upgrading Batik. We currently package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did Cocoon or Forrest build a custom jar out of the modules that Batik ships? Forrest would have obtained that as-is from Cocoon at the time of an etc/cocoon_upgrade process. The svn log over in the Cocoon branch shows that it was Antonio (2005-05-23) who commited it there. This gave me some search clues and so found this around our 0.6 release: http://s.apache.org/qx8 Subject: Re: REsizing batik to a minimum for us. Date: May 27, 2004 -David I see. Thanks. Creating a batik-all-1.7.jar and copying it to forrest/lib/core in place of 1.6 causes problems which I'm having trouble diagnosing. I've also tried rebuilding the cocoon-batik-block against Batik 1.7, and it didn't help. I'll try a few more things, but this update may not make it into the release. Help is welcome. See issue https://issues.apache.org/jira/browse/FOR-1221 and our packaged Batik was upgraded as part of upgrading our Cocoon https://issues.apache.org/jira/browse/FOR-1240 -David
Re: Upgrading Batik
On Sat, Jan 08, 2011 at 12:44:13PM +1100, David Crossley wrote: Brian M Dube wrote: The Jing discussion reminded me of upgrading Batik. We currently package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did Cocoon or Forrest build a custom jar out of the modules that Batik ships? Forrest would have obtained that as-is from Cocoon at the time of an etc/cocoon_upgrade process. The svn log over in the Cocoon branch shows that it was Antonio (2005-05-23) who commited it there. This gave me some search clues and so found this around our 0.6 release: http://s.apache.org/qx8 Subject: Re: REsizing batik to a minimum for us. Date: May 27, 2004 -David I see. Thanks. Creating a batik-all-1.7.jar and copying it to forrest/lib/core in place of 1.6 causes problems which I'm having trouble diagnosing. I've also tried rebuilding the cocoon-batik-block against Batik 1.7, and it didn't help. I'll try a few more things, but this update may not make it into the release. Help is welcome. -Brian
Upgrading Batik
The Jing discussion reminded me of upgrading Batik. We currently package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did Cocoon or Forrest build a custom jar out of the modules that Batik ships? -Brian
Re: Upgrading Batik
Brian M Dube wrote: The Jing discussion reminded me of upgrading Batik. We currently package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did Cocoon or Forrest build a custom jar out of the modules that Batik ships? Forrest would have obtained that as-is from Cocoon at the time of an etc/cocoon_upgrade process. The svn log over in the Cocoon branch shows that it was Antonio (2005-05-23) who commited it there. This gave me some search clues and so found this around our 0.6 release: http://s.apache.org/qx8 Subject: Re: REsizing batik to a minimum for us. Date: May 27, 2004 -David
