I got lucky!!!!!! I didn't really work on this just now but I activated one of my other FOP working copy and had the error Phil reported:
C:\Dev\FOP\main\xml-fop-temp\build.xml:353: java.io.IOException: java.io.FileNotFoundException: file:\C:\Dev\FOP\main\xml-fop-temp\build\gensrc\org\apache\fop\events\event-model.xml (The filename, directory name, or volume label syntax is incorrect) I added some test code in EventModel and look what I got: resourcegen: [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml [eventResourceGenerator] Apache Xalan: Xalan Java 2.4.1 [eventResourceGenerator] org.apache.xalan.processor.TransformerFactoryImpl So my code is actually passing in the right file URL but Xalan messes it up internally somewhere. Please note that I reproduced this with Sun Java 1.4.2_16, not 6.0.something. Once I put the XML libraries from FOP's lib directory in the JDK's jre/lib/endorsed directory, Xalan showed version 2.7.0 and the build ran through. I wonder why I didn't run into this sooner. I always build FOP with FOP 1.4.2_16 with no endorsed directory. Weird stuff. And I'm absolutely clueless why this bug was triggered in Phil's environment as he uses Java 6 which uses a newer Xalan. Anyway, I've just committed a work-around that avoids passing the XSLT processor the target file URL and instead works with OutputStreams I manage myself. http://svn.apache.org/viewvc?rev=677404&view=rev Phil, please do another "svn up" and retry. I hope this is it this time. On 16.07.2008 20:41:12 Bones wrote: > > Well, I am too. My advise is to put this issue on the the back burner and see > if anyone can duplicate the problem. > > thoughts? > > Andreas Delmelle-2 wrote: > > > > On Jul 16, 2008, at 13:00, Bones wrote: > > > > Hi Phil > > > >> > >> My parser/transform environment is the standard which comes with FOP, > >> however when I use FOP for development I also use SAXON for > >> transformation > >> and sometimes pure Sax2 for parsing. It depends. > > > > I haven't yet encountered such issues when /running/ FOP, only when > > building. > > If you only use FOP, this shouldn't really pose a problem. Seen that > > you're eager to start developing, it is a rather unfortunate one... :-/ > > > > BTW: Remember also that, when running FOP, unless you explicitly > > force the JVM to use the Xerces and Xalan versions in the > > distribution, then it will use whatever XML parser and XSLT processor > > come first in the classpath (most JVMs come bundled with a fallback > > parser; some, like GNU Classpath, do not have an XSLT processor, > > which causes mayhem in some environments because Xalan does not work > > in combination with the GNU XML parser...) > > > >> "In the end, I got it working by making sure that the build process > >> was using the exact same XML parser and XSLT processor that were > >> distributed with FOP. " - How do I do that with in ant? > >> > > > > > > Basically the same as for every other java application, it comes down > > to either: > > > > * copying all necessary JARs to JAVA_HOME/lib/endorsed > > * prepending those JARs to the bootclasspath (as in: "java - > > Xbootclasspath/p:...") > > * specifying the exact implementations to use by passing Java system > > properties (pattern: -Dinterface=implementation, as in: "java - > > Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryI > > mpl ...") > > > > The latter two options, for Ant, work by setting the ANT_OPTS > > environment variable (see: http://ant.apache.org/manual/ > > running.html#envvars) > > > > The first I already hinted at earlier, and you said you had tried it, > > to no avail, so I'm quite clueless at the moment. :-S > > > > > > Cheers > > > > Andreas > > > > > > > > -- > View this message in context: > http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18493995.html > Sent from the FOP - Dev mailing list archive at Nabble.com. Jeremias Maerki
