Re: Fw: [GUMP] Build Failure - xml-fop
This doesn't appear to be Batik's fault--they're just
recoding their classes, and their GraphicsNode
interface has two more functions in it, one of which
needs implementing in FOP's PDFJpegNode class.
If Gump links to Batik's latest and greatest when
building FOP, then FOP will need to update whenever
Batik changes. Could/should that be changed so Gump
will only link to the Batik library that we get on a
cvs checkout?
Thankfully, it appears that if this is added to FOP's
PDFJpegNode it will at least compile against both
versions--library Batik and latest-and-greatest Batik:
public Rectangle2D getSensitiveBounds() {
return getGeometryBounds();
}
(code from
http://cvs.apache.org/viewcvs.cgi/xml-batik/sources/org/apache/batik/gvt/TextNode.java?rev=1.27sortby=datecontent-type=text/vnd.viewcvs-markup
-- a Batik class that needed changing itself as a
result to the new functions in GraphicsNode)
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
Hi Batik-Devs,
the latest changes in Batik broke both the
maintenance branch and HEAD
of FOP:
__
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: Fw: [GUMP] Build Failure - xml-fop
This doesn't appear to be Batik's fault--they're just
recoding their classes, and their GraphicsNode
interface has two more functions in it, one of which
needs implementing in FOP's PDFJpegNode class.
If Gump links to Batik's latest and greatest when
building FOP, then FOP will need to update whenever
Batik changes. Could/should that be changed so Gump
will only link to the Batik library that we get on a
cvs checkout?
Thankfully, it appears that if this is added to FOP's
PDFJpegNode it will at least compile against both
versions--library Batik and latest-and-greatest Batik:
public Rectangle2D getSensitiveBounds() {
return getGeometryBounds();
}
(code from
http://cvs.apache.org/viewcvs.cgi/xml-batik/sources/org/apache/batik/gvt/TextNode.java?rev=1.27sortby=datecontent-type=text/vnd.viewcvs-markup
-- a Batik class that needed changing itself as a
result to the new functions in GraphicsNode)
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
Hi Batik-Devs,
the latest changes in Batik broke both the
maintenance branch and HEAD
of FOP:
__
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop
Of course, we could simply add the method and hope nothing breaks in the
process. The whole Gump thing is about getting the projects to talk to
each other. We got barked at in the past because we changed our API
without thinking about third-party dependencies. Now I'm informing the
Batik guys about the consequences of their latest changes.
You see, your code below could simply be added to Batik's
AbstractGraphicsNode, I think, and everything would be in order again
(without us having to change anything).
It may very well be that FOP 0.20.5rc3 will not work with the current
CVS version of Batik because it lacks the getSensitiveBounds() method.
If something in the Batik code calls that method, boom,
NoSuchMethodError. But I haven't tested it, yet, so I can't tell for
sure.
Both projects, Batik and FOP, have changed their APIs in their past.
That is allowed but the projects should care about their customers and
avoid generating unnecessary problems. So, before I change anything in
our code I want to see if there are other possibilities.
On 30.05.2003 17:38:50 Glen Mazza wrote:
This doesn't appear to be Batik's fault--they're just
recoding their classes, and their GraphicsNode
interface has two more functions in it, one of which
needs implementing in FOP's PDFJpegNode class.
If Gump links to Batik's latest and greatest when
building FOP, then FOP will need to update whenever
Batik changes. Could/should that be changed so Gump
will only link to the Batik library that we get on a
cvs checkout?
Thankfully, it appears that if this is added to FOP's
PDFJpegNode it will at least compile against both
versions--library Batik and latest-and-greatest Batik:
public Rectangle2D getSensitiveBounds() {
return getGeometryBounds();
}
(code from
http://cvs.apache.org/viewcvs.cgi/xml-batik/sources/org/apache/batik/gvt/TextNode.java?rev=1.27sortby=datecontent-type=text/vnd.viewcvs-markup
-- a Batik class that needed changing itself as a
result to the new functions in GraphicsNode)
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
Hi Batik-Devs,
the latest changes in Batik broke both the
maintenance branch and HEAD
of FOP:
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop
--- Jeremias Maerki [EMAIL PROTECTED] wrote: You see, your code below could simply be added to Batik's AbstractGraphicsNode, I think, and everything would be in order again (without us having to change anything). They did that for one of the two functions that were added to the GraphicsNode interface, but that other function is too subclass-dependent. I looked at the subclasses--one explicitly returns NULL, some do more advanced calculations, etc., for that function. (I'm not even sure if what I copied is best for the FOP subclass--but it is probably sufficient.) With what it knows about its subclasses, the best AGN could probably do is return NULL. That would have allowed FOP's code to quietly compile, but would probably have caused severe logical errors later while running. So they possibly did us a favor by not implementing it in AGN. Both projects, Batik and FOP, have changed their APIs in their past. That is allowed but the projects should care about their customers and avoid generating unnecessary problems. I agree--I'm angry about this irresponsible treatment from the Batik team too! Let's get revenge on them and remove FOP's TRAX/XSLTInputHandler!!! ;) Glen __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Team page
Glen Mazza wrote: Yes, you may wish to wait a bit until more bios are updated on the page. I see no reason for being hasty in publishing. Well, there is no haste to publish the team page, but since the whole web site gets published together, and we have about 2 weeks of accumulated changes to publish, it currently is a bottleneck. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Team page
On 5/30/2003 10:14 AM, Victor Mote wrote: Well, there is no haste to publish the team page, but since the whole web site gets published together, and we have about 2 weeks of accumulated changes to publish, it currently is a bottleneck. If you publish it, they will come... ;-p (i.e., people will come 'a runnin' to fix things with their name next to it...) -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Team page
My email was meant as a joke--please publish it, especially as I would like to see the other pages (in particular the examples page) updated for this weekend. Most/All the other Apache sites with bios are 100% filled--so I don't see this as anything but a momentary concern. Glen --- Victor Mote [EMAIL PROTECTED] wrote: Glen Mazza wrote: Yes, you may wish to wait a bit until more bios are updated on the page. I see no reason for being hasty in publishing. Well, there is no haste to publish the team page, but since the whole web site gets published together, and we have about 2 weeks of accumulated changes to publish, it currently is a bottleneck. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Team page
Glen Mazza wrote: My email was meant as a joke--please publish it, especially as I would like to see the other pages (in particular the examples page) updated for this weekend. Sorry -- the joke went right over my head. I went ahead published the site a few minutes ago -- it should be live in about a half-hour, IIRC. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop-maintenance
Sam Ruby wrote: BUILD FAILED I've already sent a message to Batik because of this. Unfortunately, I'm on vacation next week. Anybody beside Keiron who is subscribed to batik-dev and who can watch how this unfolds? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop-maintenance
Ha, I was first! :-) Didn't you see my message? I'm subscribed and will watch over the issue. Enjoy your vacation! On 30.05.2003 21:10:33 J.Pietschmann wrote: Sam Ruby wrote: BUILD FAILED I've already sent a message to Batik because of this. Unfortunately, I'm on vacation next week. Anybody beside Keiron who is subscribed to batik-dev and who can watch how this unfolds? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop-maintenance
Jeremias Maerki wrote: Ha, I was first! :-) Didn't you see my message? No: the crossposted message was filed into the FOP folder. Any idea how Moz could file crossposted messages correctly, one into the A and the other into the B folder...they just end up both in the A folder if the filter for A has higher precedence than B...another example of a simple solution not quite living up to user expectations... :-/ I'm subscribed and will watch over the issue. Enjoy your vacation! Thanks! J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop-maintenance
I don't use Moz (which is my personal short for Mozzarella BTW) but I use the list-post or List-Post header to separate crossposts. On 30.05.2003 21:52:41 J.Pietschmann wrote: Jeremias Maerki wrote: Ha, I was first! :-) Didn't you see my message? No: the crossposted message was filed into the FOP folder. Any idea how Moz could file crossposted messages correctly, one into the A and the other into the B folder...they just end up both in the A folder if the filter for A has higher precedence than B...another example of a simple solution not quite living up to user expectations... :-/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - xml-fop-maintenance
Jeremias Maerki wrote: I don't use Moz (which is my personal short for Mozzarella BTW) but I use the list-post or List-Post header to separate crossposts. Clever, works perfectly! I always thought of a general tool chest wiki page, with how to set up eclipse for apache committers (including templates) and all kinds of other clues. If I ever get around to do this, the trick above will definitely be included in the mail clients section. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - xml-fop
This email is autogenerated from the output from: http://cvs.apache.org/builds/gump/2003-05-31/xml-fop.html Buildfile: build.xml init-avail: [echo] Jimi Support NOT Present [echo] JAI Support NOT Present [echo] JCE Support PRESENT init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 1.0dev [1999-2003] [echo] See build.properties and build-local.properties for additional build settings [filter] Reading filters from /home/rubys/jakarta/xml-fop/build/src/codegen/filter prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/gensrc [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14 [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph codegen: [echo] Resetting codegen directory [copy] Copying 33 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties/fo_ignore_this.dummy [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties/foenums_ignore_this.dummy [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/encodings.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/Courier.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/CourierOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/CourierOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/CourierBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/CourierBoldOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/Helvetica.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/HelveticaBold.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/HelveticaBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/HelveticaOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/HelveticaOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/HelveticaBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/HelveticaBoldOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/TimesRoman.xml to
[GUMP] Build Failure - xml-fop-maintenance
This email is autogenerated from the output from: http://cvs.apache.org/builds/gump/2003-05-31/xml-fop-maintenance.html Buildfile: build.xml init-avail: init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 0.20.5rc3a [1999-2003] [filter] Reading filters from /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/filter prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop-maintenance/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop-maintenance/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop-maintenance/build/classes/conf [copy] Replacing: @version@ - 0.20.5rc3a codegen: [echo] Resetting codegen directory [copy] Copying 37 files to /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/fo_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/foenums_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/extproperties.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/fo/properties/ExtensionPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/encodings.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/code-point-mapping.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/Courier.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/Courier-Oblique.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/Courier-Bold.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/Courier-BoldOblique.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop-maintenance/build/src/codegen/Helvetica-Bold.xml to /home/rubys/jakarta/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java
