Re: Build problems... please help/advise...
Hi, I'm new to FOP, just joined the mailing list and I'm not sure what exactly is going on so I'd *really* appreciate it if someone could explain how to build FOP from the latest src (if it is even possible). I've been unable to build FOP from the src archive as of 3/11. A couple of the error messages I get are: I just did a build and it seems fine. The problem appears to be the version of batik that you have in the classpath. The batik javadocs you are refering to below are from june and are probably outdated. Make sure you are using the version of batik from cvs and there is no other batik in the classpath. [javac] /Users/bkylberg/Projects/xml-fop/src/java/org/apache/fop/image/ analyser/SVGReader.java:204: Method createSVGDocument(java.lang.String, java.io.InputStream) not found in class org.apache.batik.dom.svg.SAXSVGDocumentFactory [javac] SVGDocument doc = (SVGDocument) factory.createSVGDocument(uri, fis); [javac] /Users/bkylberg/Projects/xml-fop/src/java/org/apache/fop/render/ps/ PSTextPainter.java:93: class org.apache.fop.render.ps.PSTextPainter must be declared abstract. It does not define java.awt.geom.Rectangle2D getBounds(org.apache.batik.gvt.TextNode) from interface org.apache.batik.gvt.TextPainter. and so on until the build fails... The first error can be corrected by calling createDocument instead of createSVGDocument. createSVGDocument is an undefined API on SAXSVGDocumentFactory so I'm not sure how anyone has been able to compile this (ref: http://xml.apache.org/batik/javadoc/org/apache/batik/dom/svg/ SAXSVGDocumentFactory.html ). The second error is due to the fact that PSTextPainter claims to implement TextPainter (ref: http://xml.apache.org/batik/javadoc/org/apache/batik/gvt/ TextPainter.html ) but is in fact missing API implementations, among which getBounds is one. In fact I believe the implementation of PSTextPainter.getOutline(TextNode node) is altogether wrong insofar as PROXY_PAINTER isa StrokingTextPainter whose getOutline method takes a TextNode *and* a boolean (ref: http://xml.apache.org/batik/javadoc/org/apache/batik/gvt/renderer/ StrokingTextPainter.html ). According to the mailing list archives PSTextPainter was recently submitted and added to the repository (ref: http://marc.theaimsgroup.com/?l=fop-devm=104737262930539w=2 and http://marc.theaimsgroup.com/?l=fop-devm=104735385419249w=2 ). Perhaps everyone is using a different version of Java than I am ;-) but if not, then I'm wondering how anyone is able to build FOP given these defects? Am I the only one whose tried to build FOP from scratch in the past 2 days? Any advice would be greatly appreciated. -- Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Build problems... please help/advise...
Keiron,
Great! Thanks for the recommendation... indeed I had an older version of Batik sneaking into the build; tricky jars :-) In case anyone has this trouble in the future, I was able to figure out which jar was being loaded by editing the build.xml file line 401 from:
javac destdir=${build.dest} debug=${debug} deprecation=${deprecation} optimize=${optimize}>
to be:
javac verbose=true destdir=${build.dest} debug=${debug} deprecation=${deprecation} optimize=${optimize}>
Now, the compile is going through but I'm hanging on SerializeHyphPattern (here's the dump...):
compile-src:
[echo] Compiling the sources
[javac] Compiling 7 source files to /Users/bkylberg/Projects/xml-fop/build/classes
compile-jimi:
compile-jai:
compile-jce:
compile:
hyphenation:
BUILD FAILED
file:/Users/bkylberg/Projects/xml-fop/build.xml:446: taskdef class org.apache.fop.tools.anttasks.SerializeHyphPattern cannot be found
I noticed that Sam Ruby had a similar problem and Jeremias apparently corrected it; but I'm not sure how. Any recommendations?
-- Bob
On Thursday, March 13, 2003, at 06:40 PM, Keiron Liddle wrote:
Hi,
I'm new to FOP, just joined the mailing list and I'm not sure what
exactly is going on so I'd *really* appreciate it if someone could
explain how to build FOP from the latest src (if it is even possible).
I've been unable to build FOP from the src archive as of 3/11. A couple
of the error messages I get are:
I just did a build and it seems fine.
The problem appears to be the version of batik that you have in the classpath.
The batik javadocs you are refering to below are from june and are probably
outdated.
Make sure you are using the version of batik from cvs and there is no other batik
in the classpath.
Re: Build problems... please help/advise...
(Comments inline)
On 14.03.2003 07:05:08 Robert Kylberg wrote:
Keiron,
Great! Thanks for the recommendation... indeed I had an older version
of Batik sneaking into the build; tricky jars :-) In case anyone has
this trouble in the future, I was able to figure out which jar was
being loaded by editing the build.xml file line 401 from:
javac destdir=${build.dest} debug=${debug}
deprecation=${deprecation} optimize=${optimize}
to be:
javac verbose=true destdir=${build.dest} debug=${debug}
deprecation=${deprecation} optimize=${optimize}
You can get that easier by specifying build -verbose on the command
line. No modification of the build.xml necessary.
Now, the compile is going through but I'm hanging on
SerializeHyphPattern (here's the dump...):
compile-src:
[echo] Compiling the sources
[javac] Compiling 7 source files to
/Users/bkylberg/Projects/xml-fop/build/classes
compile-jimi:
compile-jai:
compile-jce:
compile:
hyphenation:
BUILD FAILED
file:/Users/bkylberg/Projects/xml-fop/build.xml:446: taskdef class
org.apache.fop.tools.anttasks.SerializeHyphPattern cannot be found
I noticed that Sam Ruby had a similar problem and Jeremias apparently
corrected it; but I'm not sure how. Any recommendations?
:-) I wasn't really Sam Ruby who had a problem, it was Gump
(http://jakarta.apache.org/gump) that had problems and it was Gump that
sent a nag mail to the mailing list notifying us of a build problem. The
problem is probably unrelated to what you're experiencing.
Are you using Ant 1.4 or older? Maybe it's because of that. Anyway, if
you don't have anything in your CLASSPATH environment variable (which is
usually a bad idea) and are using the build.bat script we supply you
shouldn't have any problems building FOP.
If you have problems building it's usually a good idea to try build
clean followed by build to force a full rebuild. The above seems to
be a partial build.
Good luck.
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
