IOException during build
Hi, I am getting an IOException while building the latest trunk version. It occurs on the first fixcrlf (line 430) for the EventFormatter.xml. The EventFormatter.xml is writable; I can delete it manually, so there should be no IOException. Is the build process somehow locking it? Anu clues?
Re: IOException during build
Works for me. Does this IOException have an error message associated with it? An IOException can be anything. On 16.04.2008 16:24:37 Raphael Parree wrote: Hi, I am getting an IOException while building the latest trunk version. It occurs on the first fixcrlf (line 430) for the EventFormatter.xml. The EventFormatter.xml is writable; I can delete it manually, so there should be no IOException. Is the build process somehow locking it? Anu clues? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IOException during build
Jeremias, I guess it has to do with the TransformerImpl implementation in the JVM. In JDK jdk1.5.0_11 (Sun) (the one I was using) the internal _osstream is not closed; in java 6 it is closed (hence it works with Java 6) (see line 726 in the JDK 1.6 b4) com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl). The transform is used in the EventProducerCollectorTask, it leaves the stream open and the next ant task tries to delete the file and fails. So it works with Java 6 update 4 not with JDK 1.5 b11 (both from SUN). -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED] Sent: 16 April 2008 18:05 To: fop-users@xmlgraphics.apache.org Subject: Re: IOException during build Works for me. Does this IOException have an error message associated with it? An IOException can be anything. On 16.04.2008 16:24:37 Raphael Parree wrote: Hi, I am getting an IOException while building the latest trunk version. It occurs on the first fixcrlf (line 430) for the EventFormatter.xml. The EventFormatter.xml is writable; I can delete it manually, so there should be no IOException. Is the build process somehow locking it? Anu clues? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IOException during build
Jeremias, I also tried JJDK1.5 Update 15 and it has the same problem. Using another Transformer implementation does the trick for me: set ANT_OPTS=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor .TransformerFactoryImpl (adding lib\xalan-2.7.0.jar;lib\serializer-2.7.0.jar to the classpath when running Ant.) -Original Message- From: Raphael Parree [mailto:[EMAIL PROTECTED] Sent: 16 April 2008 18:19 To: 'fop-users@xmlgraphics.apache.org' Subject: RE: IOException during build Jeremias, I guess it has to do with the TransformerImpl implementation in the JVM. In JDK jdk1.5.0_11 (Sun) (the one I was using) the internal _osstream is not closed; in java 6 it is closed (hence it works with Java 6) (see line 726 in the JDK 1.6 b4) com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl). The transform is used in the EventProducerCollectorTask, it leaves the stream open and the next ant task tries to delete the file and fails. So it works with Java 6 update 4 not with JDK 1.5 b11 (both from SUN). -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED] Sent: 16 April 2008 18:05 To: fop-users@xmlgraphics.apache.org Subject: Re: IOException during build Works for me. Does this IOException have an error message associated with it? An IOException can be anything. On 16.04.2008 16:24:37 Raphael Parree wrote: Hi, I am getting an IOException while building the latest trunk version. It occurs on the first fixcrlf (line 430) for the EventFormatter.xml. The EventFormatter.xml is writable; I can delete it manually, so there should be no IOException. Is the build process somehow locking it? Anu clues? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
