Re: build failure with J2SDK1.4
Cyril Rognon wrote: Hi Fopers I have checked out the 0.20.3 with a -r fop-0_20_3 version tag (think that's the right thing to do to get the 0.20.3 release) Yes, but if you want the current maintenance branch source use -r fop-0_20_2-maintain when I try to build FOP, I get an error after 14 seconds. If anyone has some ideas, I take it ! I just tried it with win2k and jsdk1.4 and it worked from a dos box but I got the same error as you using cygwin. Are you using cygwin ? If yes, I just committed a patch to the maintenance branch which should fix this. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: build failure with J2SDK1.4
This is either a problem with the xml+xsl files we are using or a problem with the parser, I'm not usre which. Note that jdk1.4 comes with an xml parser which could be interfering with the xml parser in the lib directory. Sorry I can't be of more help. On 2002.04.19 11:55 Cyril Rognon wrote: Hi Fopers I have checked out the 0.20.3 with a -r fop-0_20_3 version tag (think that's the right thing to do to get the 0.20.3 release) Then I have uncommented the new method in src/org/apache/fop/svg/PDFGraphics2D.java when I try to build FOP, I get an error after 14 seconds. If anyone has some ideas, I take it ! The classpath set for the build : Fop Build System Building with classpath C:\bin\jsdk1.4.0\lib\tools.jar;C:\bin\jsdk1.4.0\lib\classes.zip;lib\ant.jar;lib\ant-1.3-optional.jar;lib\batik.jar;lib\buildtools.jar;lib\xerces-1.2.3.jar;lib\xalan-2.0.0.jar;lib\xalanj1compat.jar;lib\bsf.jar;lib\jimi-1.0.jar;lib\logkit-1.0.jar;lib\avalon-framework-4.0.jar Here is the trace of the build failure : [style] Transforming into E:\cvs\fop\maintain\xml-fop\build\src\org\apache\fop\render\pdf [style] Loading stylesheet E:\cvs\fop\maintain\xml-fop\.\build\src\codegen\code-point-mapping.xsl [style] Processing E:\cvs\fop\maintain\xml-fop\build\src\codegen\encodings.xml to E:\cvs\fop\maintain\xml-fop\build\src\org\apache\fop\render\pdf\CodePointMapping.java [style] Failed to process E:\cvs\fop\maintain\xml-fop\build\src\codegen\encodings.xml BUILD FAILED E:\cvs\fop\maintain\xml-fop\build.xml:472: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: File file:///E:/cvs/fop/maintain/xml-fop/E:/cvs/fop/maintain/xml-fop/build/src/codegen/encodings.xml not found. --- Nested Exception --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: build failure with J2SDK1.4
Thanks Keiron, I think you may be right. I have successfully done the build by processing the codegen target with a JDK1.3 JVM and the package target with the new JSDK1.4.0. It worked out well. It appears the XML parser that comes with this last JVM is interfering. Maybe further distro will have to watch out for this problem. thx Cyril At 09:26 23/04/2002 +0200, you wrote: This is either a problem with the xml+xsl files we are using or a problem with the parser, I'm not usre which. Note that jdk1.4 comes with an xml parser which could be interfering with the xml parser in the lib directory. Sorry I can't be of more help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: build failure with J2SDK1.4
Keiron Liddle wrote: On 2002.04.19 11:55 Cyril Rognon wrote: Hi Fopers I have checked out the 0.20.3 with a -r fop-0_20_3 version tag (think that's the right thing to do to get the 0.20.3 release) Then I have uncommented the new method in src/org/apache/fop/svg/PDFGraphics2D.java when I try to build FOP, I get an error after 14 seconds. If anyone has some ideas, I take it ! The classpath set for the build : Fop Build System Building with classpath C:\bin\jsdk1.4.0\lib\tools.jar;C:\bin\jsdk1.4.0\lib\classes.zip;lib\ant.jar;lib\ant-1.3-optional.jar;lib\batik.jar;lib\buildtools.jar;lib\xerces-1.2.3.jar;lib\xalan-2.0.0.jar;lib\xalanj1compat.jar;lib\bsf.jar;lib\jimi-1.0.jar;lib\logkit-1.0.jar;lib\avalon-framework-4.0.jar Here is the trace of the build failure : [style] Transforming into E:\cvs\fop\maintain\xml-fop\build\src\org\apache\fop\render\pdf [style] Loading stylesheet E:\cvs\fop\maintain\xml-fop\.\build\src\codegen\code-point-mapping.xsl [style] Processing E:\cvs\fop\maintain\xml-fop\build\src\codegen\encodings.xml to E:\cvs\fop\maintain\xml-fop\build\src\org\apache\fop\render\pdf\CodePointMapping.java [style] Failed to process E:\cvs\fop\maintain\xml-fop\build\src\codegen\encodings.xml BUILD FAILED E:\cvs\fop\maintain\xml-fop\build.xml:472: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: File file:///E:/cvs/fop/maintain/xml-fop/E:/cvs/fop/maintain/xml-fop/build/src/codegen/encodings.xml not found. --- Nested Exception --- Cyril, Keiron, Could there be some bizarre bug which is converting a filespec like E:\cvs\fop\maintain\xml-fop\.\build\src\codegen\code-point-mapping.xsl into E:\cvs\fop\maintain\xml-fop\E:\cvs\fop\maintain\xml-fop\build\src\codegen\code-point-mapping.xsl in certain circumstances? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
