Re: Build errors
Hi Eric, You have to add the build/gensrc folder to your Eclipse build path. That folder is created when running ant. HTH, Vincent Eric Douglas wrote: What am I missing now on this Java build? Running the ant script shows me a Build Successful message, though the Problems tab in the Eclipse IDE shows missing classes for all the font references, on the CodePointMapping and the Courier, Helvetica, etc. These classes have no source in the IDE. They have class files in the jar. I try to call the jar methods and I get errors. A call to PDFRenderer.setupFontInfo(new FontInfo()) gives me a compilation error message on the invalid class reference. A call to setFontBaseURL(Fonts\) gives me an invalid path error (trying to find syntax to point to custom font files I put in a Fonts folder in another jar on the classpath). I take those out to see if it just works with no reference to my custom fonts, if it can just automatically find them in the classpath, and my program just hangs on the FopFactory.newFop(FOUserAgent) statement. -Original Message- From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Sent: Thursday, August 12, 2010 8:35 AM To: fop-dev@xmlgraphics.apache.org Subject: Re: Build errors linkmap.xml? I don't think we have a file with that name in FOP. Could that be coming from Apache Forrest somehow, maybe due to a buggy XML parser maybe? Maybe putting a current Xerces and Xalan in the JRE's lib/endorsed directory may change something. Otherwise, please provide a snippet from the output log. On 10.08.2010 17:27:00 Eric Douglas wrote: When I download the source for fop 1.0, the ant build shows successful, but if I try a regular build just to check for errors before running the ant build I get a bunch of error messages such as the content of element type li must match... (on linkmap.xml). Is this normal or am I missing something? Jeremias Maerki
RE: Build errors
There is a file linkmap.xml but not in the source download. Maybe this is my problem. I downloaded both and unzipped fop-1.0-bin.zip, then unzipped fop-1.0-src.zip to the same root path, telling it to replace any duplicate file names. I'll try wiping out the files and unzipping just the src again. It would seem they might just conflict each other. -Original Message- From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Sent: Thursday, August 12, 2010 8:35 AM To: fop-dev@xmlgraphics.apache.org Subject: Re: Build errors linkmap.xml? I don't think we have a file with that name in FOP. Could that be coming from Apache Forrest somehow, maybe due to a buggy XML parser maybe? Maybe putting a current Xerces and Xalan in the JRE's lib/endorsed directory may change something. Otherwise, please provide a snippet from the output log. On 10.08.2010 17:27:00 Eric Douglas wrote: When I download the source for fop 1.0, the ant build shows successful, but if I try a regular build just to check for errors before running the ant build I get a bunch of error messages such as the content of element type li must match... (on linkmap.xml). Is this normal or am I missing something? Jeremias Maerki
RE: Build errors
It appears that was the case. I was confused because my setup has a build folder under every project source folder, or at least it creates it there after the first compile, so I thought the src.zip could be extracted right over the bin.zip since the bin.zip has a build folder and the src.zip doesn't. I deleted my project, removed the files on disk, and extracted just the src.zip to recreate the project. Then I compiled and got some errors in the Eclipse Problems tab, though none such as what I was getting previously. There is an error that it can't find javax.crypto because the package added the Java libraries as some sort of specific reference to rt.jar. I deleted that from the build path and added a reference to the JRE System Library and that error went away. All other errors in the Eclipse Problems tab appear to be expected errors, font related, from classes with no source which are created from the ant build such as org.apache.fop.fonts.CodePointMapping. -Original Message- From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Sent: Thursday, August 12, 2010 8:35 AM To: fop-dev@xmlgraphics.apache.org Subject: Re: Build errors linkmap.xml? I don't think we have a file with that name in FOP. Could that be coming from Apache Forrest somehow, maybe due to a buggy XML parser maybe? Maybe putting a current Xerces and Xalan in the JRE's lib/endorsed directory may change something. Otherwise, please provide a snippet from the output log. On 10.08.2010 17:27:00 Eric Douglas wrote: When I download the source for fop 1.0, the ant build shows successful, but if I try a regular build just to check for errors before running the ant build I get a bunch of error messages such as the content of element type li must match... (on linkmap.xml). Is this normal or am I missing something? Jeremias Maerki
RE: Build errors
What am I missing now on this Java build? Running the ant script shows me a Build Successful message, though the Problems tab in the Eclipse IDE shows missing classes for all the font references, on the CodePointMapping and the Courier, Helvetica, etc. These classes have no source in the IDE. They have class files in the jar. I try to call the jar methods and I get errors. A call to PDFRenderer.setupFontInfo(new FontInfo()) gives me a compilation error message on the invalid class reference. A call to setFontBaseURL(Fonts\) gives me an invalid path error (trying to find syntax to point to custom font files I put in a Fonts folder in another jar on the classpath). I take those out to see if it just works with no reference to my custom fonts, if it can just automatically find them in the classpath, and my program just hangs on the FopFactory.newFop(FOUserAgent) statement. -Original Message- From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Sent: Thursday, August 12, 2010 8:35 AM To: fop-dev@xmlgraphics.apache.org Subject: Re: Build errors linkmap.xml? I don't think we have a file with that name in FOP. Could that be coming from Apache Forrest somehow, maybe due to a buggy XML parser maybe? Maybe putting a current Xerces and Xalan in the JRE's lib/endorsed directory may change something. Otherwise, please provide a snippet from the output log. On 10.08.2010 17:27:00 Eric Douglas wrote: When I download the source for fop 1.0, the ant build shows successful, but if I try a regular build just to check for errors before running the ant build I get a bunch of error messages such as the content of element type li must match... (on linkmap.xml). Is this normal or am I missing something? Jeremias Maerki
Re: Build errors
linkmap.xml? I don't think we have a file with that name in FOP. Could that be coming from Apache Forrest somehow, maybe due to a buggy XML parser maybe? Maybe putting a current Xerces and Xalan in the JRE's lib/endorsed directory may change something. Otherwise, please provide a snippet from the output log. On 10.08.2010 17:27:00 Eric Douglas wrote: When I download the source for fop 1.0, the ant build shows successful, but if I try a regular build just to check for errors before running the ant build I get a bunch of error messages such as the content of element type li must match... (on linkmap.xml). Is this normal or am I missing something? Jeremias Maerki
