Uhm, my bad. I seem to have forgotten to upload the necessary change. Have done it now: http://svn.apache.org/viewvc/gump/metadata/project/xml-fop-maintenance.xml?view=markup
BTW, we could even think about switching off the Gump run for the maintenance branch. We won't really do anything there anymore and not referencing Batik directly sort of defeats the purpose of. Cocoon is the only project referencing the maintenance branch (AFAIK) but they switched to Maven which does not work with Gump, yet. WDYT? On 16.08.2006 12:16:41 Chris Bowditch wrote: > [EMAIL PROTECTED] wrote: > > >> [javac] /x1/gump/public/workspace/xml-fop- > >>maintenance/build/src/org/apache/fop/svg/PDFTranscoder.java:233: > >> > > > > getViewTransform(java.lang.String,org.w3c.dom.Element,float,float,org.apache. > > > >>batik.bridge.BridgeContext) in org.apache.batik.bridge.ViewBox cannot be > > > > > >>applied to (java.lang.String,org.w3c.dom.svg.SVGSVGElement,float,float) > >> [javac] Px = ViewBox.getViewTransform(ref, root, width, > > > > height); > > > >> [javac] ^ > > > > > > What do we want to do about this? > > In trunk this method now takes the BridgeContext (which I'm sure the > > maintenance code has available) so it can report line numbers in errors. > > The code will work fine if the BridgeContext is null (just no line > > numbers). > > > > Is there an expectation that fop-maintenance should work with trunk > > Batik? > > No. fop-maintenance only works with an old snapshot of Batik, why is it > trying to use Batik trunk? > > Chris > Jeremias Maerki
