You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bonekrusher <dj...@yahoo.com> on 2008/07/09 13:42:15 UTC
Building FOP Trunk with Ant - BUILD FAILED
Hi,
I am trying to build the FOP trunk (checked out with svn) with Ant and get
the following error:
va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
[javac] urls.add(libFiles[i].toURL());
[javac] ^
[javac] 26 warnings
[mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
[javac] Compiling 11 source files to
C:\fop_trunk\trunk\build\sandbox-classe
s
resourcegen:
[mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
[javac] Compiling 3 source files to
C:\fop_trunk\trunk\build\codegen-classes
[copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
BUILD FAILED
C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
java.io.FileNotFoundExcep
tion:
file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
l (The filename, directory name, or volume label syntax is incorrect)
Total time: 33 seconds
***************************
The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.
Any thoughts:?
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18359419.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Ant - BUILD FAILED
Posted by Leeloo5E-FOP <le...@yahoo.de>.
Hi,
got the same problem when trying to build FOP from Trunk with the
pre-installed version 1.6.5 of ant on a linux maschine. Using version 1.7.0
instead, the build runs fine. I do not try the newest version 1.7.1 of ant
yet (I comes out on june 28th). For building FOP from Trunk I used the
pre-installed jre 1.4.2 or 1.5.0 from SUN on my linux maschines.
Thats my suggestions.
Best Regards,
Lee
bonekrusher wrote:
>
> Hi,
>
> I am trying to build the FOP trunk (checked out with svn) with Ant and get
> the following error:
>
> va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
> [javac] urls.add(libFiles[i].toURL());
> [javac] ^
> [javac] 26 warnings
> [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
> [javac] Compiling 11 source files to
> C:\fop_trunk\trunk\build\sandbox-classe
> s
>
> resourcegen:
> [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
> [javac] Compiling 3 source files to
> C:\fop_trunk\trunk\build\codegen-classes
>
> [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>
> BUILD FAILED
> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
> java.io.FileNotFoundExcep
> tion:
> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
> l (The filename, directory name, or volume label syntax is incorrect)
>
> Total time: 33 seconds
>
> ***************************
>
> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.
>
> Any thoughts:?
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18400009.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 13, 2008, at 13:23, bonekrusher wrote:
>
> Ok, I wanted to test this at home to see if this was a machine issue.
Just out of curiosity, can you try to copy the following files under %
FOP%/lib :
serializer-2.7.0.jar
xalan-2.7.0.jar
xercesImpl-2.7.1.jar
xml-apis-1.3.04.jar
to the lib/endorsed directory in the Java home dir (create if it does
not exist).
Then try to run the clean build again.
It's a long shot, but maybe if the Xerces/Xalan implementations are
forced to be the same ones that FOP ships with...
HTH!
Cheers
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 13, 2008, at 14:44, bonekrusher wrote:
>
> Ok, when I added JAVACMD environment variable, I can not use ant. I
> set the
> variable to:
>
> C:\Program Files\Java\jdk1.6.0_04\bin
If any exists, the variable should contain the /full/ path to the
java executable, so:
C:\Program Files\Java\jdk1.6.0_04\bin\java.exe
would be more correct.
Anyway, if none exists, there is also no way in which this could
interfere with the build-process, so it's not necessary to create
one. It's only so that Ant, if it finds a JAVACMD variable, uses that
java.exe, rather than the one under %JAVA_HOME%/bin, while the build
script will still display the version corresponding to the latter...
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
YAHOO!!!!
Message:
BUILD SUCCESSFUL
Total time: 1 minute 7 seconds
Man, I thought it was just me. You guys are the best. Thanks for all the
work.
Whats funny is, I didn't even dive in the FOP source code to work on the
table-continued markers. I almost gave up!
Thanks.
Andreas Delmelle-2 wrote:
>
> On Jul 16, 2008, at 22:21, Jeremias Maerki wrote:
>
>> 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:
>>
>> <snip />
>> 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.
>
> Since the error is restricted to Windows, let's blame Microsoft. ;-P
>
> (I guess there's even a possibility that Xalan does not actually do
> anything wrong, but also calls File.toURL() somewhere, and the JVM's
> native implementation makes use of some Windows API function, which
> is responsible for the invalid URL...)
>
>> 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
>
> Yay!! Was I missing the obvious? Indeed, why even convert the File to
> a URL, if StreamSource() accepts, well, an InputStream, which
> bypasses this strangeness altogether...
>
> :-)
>
>
> Cheers
>
> Andreas
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18506988.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 16, 2008, at 22:21, Jeremias Maerki wrote:
> 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:
>
> <snip />
> 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.
Since the error is restricted to Windows, let's blame Microsoft. ;-P
(I guess there's even a possibility that Xalan does not actually do
anything wrong, but also calls File.toURL() somewhere, and the JVM's
native implementation makes use of some Windows API function, which
is responsible for the invalid URL...)
> 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
Yay!! Was I missing the obvious? Indeed, why even convert the File to
a URL, if StreamSource() accepts, well, an InputStream, which
bypasses this strangeness altogether...
:-)
Cheers
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
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
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 16, 2008, at 20:41, 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?
Always... :-)
If all else fails, I guess we could always send you the pre-generated
files, see if that gets you up and running (?)
It just seems that somewhere, /some/ component decides on using
"file.separator" instead of a simple forward slash, which mucks up
the URL.
Run 'ant -diagnostics resourcegen' and post (or mail me) the results.
Maybe that gives us a clue.
Thanks,
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Bones <Ph...@us.army.mil>.
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.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
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
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Bones <Ph...@us.army.mil>.
Hi Andreas,
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.
Phil
Peter B. West wrote:
>
> Andreas Delmelle wrote:
>> On Jul 15, 2008, at 14:55, Chris Bowditch wrote:
>>
>>> bonekrusher wrote:
>>>
>>> Hi,
>>>
>>>> Thanks Peter.
>>>> C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
>>>> This file is missing.
>>>
>>> That file is created by the build process. I think Peter was talking
>>> about how the build process references the file internally.
>>
>> Yeah, but after so many builds, one would assume that the file would
>> have been generated in the meantime.
>>
>
> Yes, that's what I'm thinking.
>
>> I had similar issues after the introduction of the event-module (but
>> those were NPEs, because the above mentioned file was not correctly
>> generated).
>> 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.
>
> The transformation process probably needs to be made more robust.
>
> Phil, what's your parser/transform environment?
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18485037.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
Peter B. West wrote:
> Bones wrote:
>> "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?
>>
>
> You're doing it. It's controlled by the classpath set up by ant, which
> looks pretty straightforward. All the jars in lib and lib/build + the
> codegen classes. So something very odd is going on.
>
D'uh
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
Bones wrote:
> "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?
>
You're doing it. It's controlled by the classpath set up by ant, which
looks pretty straightforward. All the jars in lib and lib/build + the
codegen classes. So something very odd is going on.
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Bones <Ph...@us.army.mil>.
"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?
Peter B. West wrote:
>
> Andreas Delmelle wrote:
>> On Jul 15, 2008, at 14:55, Chris Bowditch wrote:
>>
>>> bonekrusher wrote:
>>>
>>> Hi,
>>>
>>>> Thanks Peter.
>>>> C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
>>>> This file is missing.
>>>
>>> That file is created by the build process. I think Peter was talking
>>> about how the build process references the file internally.
>>
>> Yeah, but after so many builds, one would assume that the file would
>> have been generated in the meantime.
>>
>
> Yes, that's what I'm thinking.
>
>> I had similar issues after the introduction of the event-module (but
>> those were NPEs, because the above mentioned file was not correctly
>> generated).
>> 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.
>
> The transformation process probably needs to be made more robust.
>
> Phil, what's your parser/transform environment?
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18485057.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
Andreas Delmelle wrote:
> On Jul 15, 2008, at 14:55, Chris Bowditch wrote:
>
>> bonekrusher wrote:
>>
>> Hi,
>>
>>> Thanks Peter.
>>> C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
>>> This file is missing.
>>
>> That file is created by the build process. I think Peter was talking
>> about how the build process references the file internally.
>
> Yeah, but after so many builds, one would assume that the file would
> have been generated in the meantime.
>
Yes, that's what I'm thinking.
> I had similar issues after the introduction of the event-module (but
> those were NPEs, because the above mentioned file was not correctly
> generated).
> 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.
The transformation process probably needs to be made more robust.
Phil, what's your parser/transform environment?
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 15, 2008, at 14:55, Chris Bowditch wrote:
> bonekrusher wrote:
>
> Hi,
>
>> Thanks Peter. C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events
>> \event-model.xml This file is missing.
>
> That file is created by the build process. I think Peter was
> talking about how the build process references the file internally.
Yeah, but after so many builds, one would assume that the file would
have been generated in the meantime.
I had similar issues after the introduction of the event-module (but
those were NPEs, because the above mentioned file was not correctly
generated).
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.
Cheers
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Chris Bowditch <bo...@hotmail.com>.
bonekrusher wrote:
Hi,
> Thanks Peter.
>
> C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
>
> This file is missing.
That file is created by the build process. I think Peter was talking
about how the build process references the file internally.
<snip/>
Chris
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Thanks Peter.
C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
This file is missing.
Peter B. West wrote:
>
> It looks suspiciously like this guy:
> C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
> (Line 353 btw)
>
> It would be nice to see what is actually being passed into the
> eventResourceGenerator task.
>
> bonekrusher wrote:
>> Peter,
>>
>> Which file is this?
>>
>> <echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
>> immediately in front of line 352 to verify. It could be a mixed forward
>> and backslashed path.
>>
>>
>> Phil
>>
>>
>> Peter B. West wrote:
>>> bonekrusher wrote:
>>>> I will test this out later today on my home PC. I get a different set
>>>> of
>>>> errors on different machines.
>>>>
>>>> In the mean time I ran a new svn check out (as you suggested) on my
>>>> work
>>>> PC
>>>> and got the same original error message e.g.
>>>>
>>>> BUILD FAILED
>>>> C:\foptrunk2\trunk\build.xml:353: java.io.IOException:
>>>> java.io.FileNotFoundExcep
>>>> tion:
>>>> file:\C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xm
>>>> l (The filename, directory name, or volume label syntax is incorrect)
>>>>
>>>> So its seems I have two different problems. I thought I might be doing
>>>> something fundamentally wrong, but I was able to build FOP 0.94.
>>>>
>>>> As Jeremias suggested, I will try to download the trunk again from my
>>>> home
>>>> PC. I don't want to confuse the error reports from one machine to
>>>> another
>>>> as they appear to be different.
>>> Well, it's incorrect URL syntax. Presumably
>>> ${build.gensrc.dir}/org/apache/fop/events/event-model.xml
>>> (see line 353) is being passed in as a file path, not a URL.
>>>
>>> Put
>>> <echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
>>> immediately in front of line 352 to verify. It could be a mixed forward
>>> and backslashed path.
>>>
>>> In any case, it seems to be getting converted into a badly formed file:
>>> URL within the ant task.
>>> --
>>> Peter B. West <http://cv.pbw.id.au/>
>>> Folio <http://defoe.sourceforge.net/folio/>
>>>
>>>
>>
>
>
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18462574.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
It looks suspiciously like this guy:
C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml
(Line 353 btw)
It would be nice to see what is actually being passed into the
eventResourceGenerator task.
bonekrusher wrote:
> Peter,
>
> Which file is this?
>
> <echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
> immediately in front of line 352 to verify. It could be a mixed forward
> and backslashed path.
>
>
> Phil
>
>
> Peter B. West wrote:
>> bonekrusher wrote:
>>> I will test this out later today on my home PC. I get a different set of
>>> errors on different machines.
>>>
>>> In the mean time I ran a new svn check out (as you suggested) on my work
>>> PC
>>> and got the same original error message e.g.
>>>
>>> BUILD FAILED
>>> C:\foptrunk2\trunk\build.xml:353: java.io.IOException:
>>> java.io.FileNotFoundExcep
>>> tion:
>>> file:\C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xm
>>> l (The filename, directory name, or volume label syntax is incorrect)
>>>
>>> So its seems I have two different problems. I thought I might be doing
>>> something fundamentally wrong, but I was able to build FOP 0.94.
>>>
>>> As Jeremias suggested, I will try to download the trunk again from my
>>> home
>>> PC. I don't want to confuse the error reports from one machine to
>>> another
>>> as they appear to be different.
>> Well, it's incorrect URL syntax. Presumably
>> ${build.gensrc.dir}/org/apache/fop/events/event-model.xml
>> (see line 353) is being passed in as a file path, not a URL.
>>
>> Put
>> <echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
>> immediately in front of line 352 to verify. It could be a mixed forward
>> and backslashed path.
>>
>> In any case, it seems to be getting converted into a badly formed file:
>> URL within the ant task.
>> --
>> Peter B. West <http://cv.pbw.id.au/>
>> Folio <http://defoe.sourceforge.net/folio/>
>>
>>
>
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Peter,
Which file is this?
<echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
immediately in front of line 352 to verify. It could be a mixed forward
and backslashed path.
Phil
Peter B. West wrote:
>
> bonekrusher wrote:
>> I will test this out later today on my home PC. I get a different set of
>> errors on different machines.
>>
>> In the mean time I ran a new svn check out (as you suggested) on my work
>> PC
>> and got the same original error message e.g.
>>
>> BUILD FAILED
>> C:\foptrunk2\trunk\build.xml:353: java.io.IOException:
>> java.io.FileNotFoundExcep
>> tion:
>> file:\C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xm
>> l (The filename, directory name, or volume label syntax is incorrect)
>>
>> So its seems I have two different problems. I thought I might be doing
>> something fundamentally wrong, but I was able to build FOP 0.94.
>>
>> As Jeremias suggested, I will try to download the trunk again from my
>> home
>> PC. I don't want to confuse the error reports from one machine to
>> another
>> as they appear to be different.
>
> Well, it's incorrect URL syntax. Presumably
> ${build.gensrc.dir}/org/apache/fop/events/event-model.xml
> (see line 353) is being passed in as a file path, not a URL.
>
> Put
> <echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
> immediately in front of line 352 to verify. It could be a mixed forward
> and backslashed path.
>
> In any case, it seems to be getting converted into a badly formed file:
> URL within the ant task.
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18448657.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
bonekrusher wrote:
> I will test this out later today on my home PC. I get a different set of
> errors on different machines.
>
> In the mean time I ran a new svn check out (as you suggested) on my work PC
> and got the same original error message e.g.
>
> BUILD FAILED
> C:\foptrunk2\trunk\build.xml:353: java.io.IOException:
> java.io.FileNotFoundExcep
> tion:
> file:\C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xm
> l (The filename, directory name, or volume label syntax is incorrect)
>
> So its seems I have two different problems. I thought I might be doing
> something fundamentally wrong, but I was able to build FOP 0.94.
>
> As Jeremias suggested, I will try to download the trunk again from my home
> PC. I don't want to confuse the error reports from one machine to another
> as they appear to be different.
Well, it's incorrect URL syntax. Presumably
${build.gensrc.dir}/org/apache/fop/events/event-model.xml
(see line 353) is being passed in as a file path, not a URL.
Put
<echo>basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}</echo>
immediately in front of line 352 to verify. It could be a mixed forward
and backslashed path.
In any case, it seems to be getting converted into a badly formed file:
URL within the ant task.
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
I will test this out later today on my home PC. I get a different set of
errors on different machines.
In the mean time I ran a new svn check out (as you suggested) on my work PC
and got the same original error message e.g.
BUILD FAILED
C:\foptrunk2\trunk\build.xml:353: java.io.IOException:
java.io.FileNotFoundExcep
tion:
file:\C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xm
l (The filename, directory name, or volume label syntax is incorrect)
So its seems I have two different problems. I thought I might be doing
something fundamentally wrong, but I was able to build FOP 0.94.
As Jeremias suggested, I will try to download the trunk again from my home
PC. I don't want to confuse the error reports from one machine to another
as they appear to be different.
Regards,
Phil
Jeremias Maerki-2 wrote:
>
> That's the exception I worked around in
> http://svn.apache.org/viewvc?rev=676307&view=rev
> It shouldn't occur anymore in the latest FOP Trunk when Saxon is active.
>
> Did you only update EventProducerCollectorTask.java? Please update all
> of your working copy and please make sure it's a proper SVN checkout
> like I mentioned in one of my latest off-list mails.
>
> What happens if you do a new checkout and run that (starting from a
> green field)?
> - svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/
> - ant
>
> (Just for everyone's information: Phil sent me some log files and in one
> there was XHTML code in a Java file that contained the string "viewvc"
> so I told him I suspect that he's not working off a proper SVN working
> copy.)
>
> On 14.07.2008 00:59:05 bonekrusher wrote:
>>
>> Sure call me Phil :)
>>
>> I ran the svn update on the EventProducerCollectorTask.java file.
>>
>> Here is the stack after running ant:
>>
>> BUILD FAILED
>> java.lang.NullPointerException
>> at
>> net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingConte
>> ntHandler.java:404)
>> at
>> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingCont
>> entHandler.java:277)
>> at
>> org.apache.fop.events.model.EventModel.toSAX(EventModel.java:96)
>> at
>> org.apache.fop.events.model.EventModel.writeXMLizable(EventModel.java
>> :116)
>> at
>> org.apache.fop.events.model.EventModel.saveToXML(EventModel.java:133)
>>
>> at
>> org.apache.fop.tools.EventProducerCollector.saveModelToXML(EventProdu
>> cerCollector.java:202)
>> at
>> org.apache.fop.tools.EventProducerCollectorTask.execute(EventProducer
>> CollectorTask.java:70)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
>> a:106)
>> at org.apache.tools.ant.Task.perform(Task.java:348)
>> at org.apache.tools.ant.Target.execute(Target.java:357)
>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
>> cutor.java:41)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
>> at org.apache.tools.ant.Main.runBuild(Main.java:758)
>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>>
>> Andreas Delmelle-2 wrote:
>> >
>> > On Jul 13, 2008, at 19:34, bonekrusher wrote:
>> >
>> > Hi Bones (or can we just call you Phil ;-))
>> >
>> >> No spaces. Both trunk and Ant are as follows:
>> >>
>> >> c:\ant
>> >> c:\fop_trunk
>> >
>> > I've just committed a small change to EventProducerCollectorTask.java
>> > that /might/ help... (?)
>> >
>> > Can you try to update your sandbox, run a clean build and report back
>> > on whether that changed anything?
>> >
>> >
>> > Thanks
>> >
>> > Andreas
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18434967.html
>> Sent from the FOP - Dev mailing list archive at Nabble.com.
>
>
>
>
> Jeremias Maerki
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18442235.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
That's the exception I worked around in
http://svn.apache.org/viewvc?rev=676307&view=rev
It shouldn't occur anymore in the latest FOP Trunk when Saxon is active.
Did you only update EventProducerCollectorTask.java? Please update all
of your working copy and please make sure it's a proper SVN checkout
like I mentioned in one of my latest off-list mails.
What happens if you do a new checkout and run that (starting from a
green field)?
- svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/
- ant
(Just for everyone's information: Phil sent me some log files and in one
there was XHTML code in a Java file that contained the string "viewvc"
so I told him I suspect that he's not working off a proper SVN working
copy.)
On 14.07.2008 00:59:05 bonekrusher wrote:
>
> Sure call me Phil :)
>
> I ran the svn update on the EventProducerCollectorTask.java file.
>
> Here is the stack after running ant:
>
> BUILD FAILED
> java.lang.NullPointerException
> at
> net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingConte
> ntHandler.java:404)
> at
> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingCont
> entHandler.java:277)
> at org.apache.fop.events.model.EventModel.toSAX(EventModel.java:96)
> at
> org.apache.fop.events.model.EventModel.writeXMLizable(EventModel.java
> :116)
> at
> org.apache.fop.events.model.EventModel.saveToXML(EventModel.java:133)
>
> at
> org.apache.fop.tools.EventProducerCollector.saveModelToXML(EventProdu
> cerCollector.java:202)
> at
> org.apache.fop.tools.EventProducerCollectorTask.execute(EventProducer
> CollectorTask.java:70)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
> a:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
> cutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> at org.apache.tools.ant.Main.runBuild(Main.java:758)
> at org.apache.tools.ant.Main.startAnt(Main.java:217)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
> Andreas Delmelle-2 wrote:
> >
> > On Jul 13, 2008, at 19:34, bonekrusher wrote:
> >
> > Hi Bones (or can we just call you Phil ;-))
> >
> >> No spaces. Both trunk and Ant are as follows:
> >>
> >> c:\ant
> >> c:\fop_trunk
> >
> > I've just committed a small change to EventProducerCollectorTask.java
> > that /might/ help... (?)
> >
> > Can you try to update your sandbox, run a clean build and report back
> > on whether that changed anything?
> >
> >
> > Thanks
> >
> > Andreas
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18434967.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.
Jeremias Maerki
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Sure call me Phil :)
I ran the svn update on the EventProducerCollectorTask.java file.
Here is the stack after running ant:
BUILD FAILED
java.lang.NullPointerException
at
net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingConte
ntHandler.java:404)
at
net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingCont
entHandler.java:277)
at org.apache.fop.events.model.EventModel.toSAX(EventModel.java:96)
at
org.apache.fop.events.model.EventModel.writeXMLizable(EventModel.java
:116)
at
org.apache.fop.events.model.EventModel.saveToXML(EventModel.java:133)
at
org.apache.fop.tools.EventProducerCollector.saveModelToXML(EventProdu
cerCollector.java:202)
at
org.apache.fop.tools.EventProducerCollectorTask.execute(EventProducer
CollectorTask.java:70)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
cutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Andreas Delmelle-2 wrote:
>
> On Jul 13, 2008, at 19:34, bonekrusher wrote:
>
> Hi Bones (or can we just call you Phil ;-))
>
>> No spaces. Both trunk and Ant are as follows:
>>
>> c:\ant
>> c:\fop_trunk
>
> I've just committed a small change to EventProducerCollectorTask.java
> that /might/ help... (?)
>
> Can you try to update your sandbox, run a clean build and report back
> on whether that changed anything?
>
>
> Thanks
>
> Andreas
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18434967.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 13, 2008, at 19:34, bonekrusher wrote:
Hi Bones (or can we just call you Phil ;-))
> No spaces. Both trunk and Ant are as follows:
>
> c:\ant
> c:\fop_trunk
I've just committed a small change to EventProducerCollectorTask.java
that /might/ help... (?)
Can you try to update your sandbox, run a clean build and report back
on whether that changed anything?
Thanks
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
No spaces. Both trunk and Ant are as follows:
c:\ant
c:\fop_trunk
Max Berger wrote:
>
> Bones,
>
> just a quick check: Is there a space in the path to your checkout
> (e.g. C:\Documents and Settings) If so, please try moving the checkout
> to a dir without spaces. (e.g. C:\temp) and see if that helps.
>
> Max
>
>
> Am 13.07.2008 um 18:24 schrieb Peter B. West:
>
>> bonekrusher wrote:
>>> Ok I ran the build under three versions of ant:
>>> Apache Ant version 1.6.5 compiled on June 2 2005
>>> Apache Ant version 1.7.0 compiled on December 13 2006
>>> Apache Ant version 1.7.1 compiled on June 27 2008
>>> All failed. To rule out ant, I downloaded FOP 0.94 src and ran a
>>> successfully build.
>>> This would leave me to believe that the problem lies in the trunk
>>> version.
>>> Bones.
>>
>> You've found a real head-scratcher. I've just done an update on fop,
>> and run a clean, followed by package. I don't generally run the
>> tests. The build was OK. Hmmmm
>>
>> Can you look at the lib differences between 0.94 and trunk?
>>
>> --
>> Peter B. West <http://cv.pbw.id.au/>
>> Folio <http://defoe.sourceforge.net/folio/>
>
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18431648.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Max Berger <ma...@berger.name>.
Bones,
just a quick check: Is there a space in the path to your checkout
(e.g. C:\Documents and Settings) If so, please try moving the checkout
to a dir without spaces. (e.g. C:\temp) and see if that helps.
Max
Am 13.07.2008 um 18:24 schrieb Peter B. West:
> bonekrusher wrote:
>> Ok I ran the build under three versions of ant:
>> Apache Ant version 1.6.5 compiled on June 2 2005
>> Apache Ant version 1.7.0 compiled on December 13 2006
>> Apache Ant version 1.7.1 compiled on June 27 2008
>> All failed. To rule out ant, I downloaded FOP 0.94 src and ran a
>> successfully build.
>> This would leave me to believe that the problem lies in the trunk
>> version.
>> Bones.
>
> You've found a real head-scratcher. I've just done an update on fop,
> and run a clean, followed by package. I don't generally run the
> tests. The build was OK. Hmmmm
>
> Can you look at the lib differences between 0.94 and trunk?
>
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
bonekrusher wrote:
> Ok I ran the build under three versions of ant:
>
> Apache Ant version 1.6.5 compiled on June 2 2005
> Apache Ant version 1.7.0 compiled on December 13 2006
> Apache Ant version 1.7.1 compiled on June 27 2008
>
> All failed.
>
> To rule out ant, I downloaded FOP 0.94 src and ran a successfully build.
> This would leave me to believe that the problem lies in the trunk version.
>
> Bones.
You've found a real head-scratcher. I've just done an update on fop, and
run a clean, followed by package. I don't generally run the tests. The
build was OK. Hmmmm
Can you look at the lib differences between 0.94 and trunk?
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Ok I ran the build under three versions of ant:
Apache Ant version 1.6.5 compiled on June 2 2005
Apache Ant version 1.7.0 compiled on December 13 2006
Apache Ant version 1.7.1 compiled on June 27 2008
All failed.
To rule out ant, I downloaded FOP 0.94 src and ran a successfully build.
This would leave me to believe that the problem lies in the trunk version.
Bones.
Peter B. West wrote:
>
> NetBeans includes an ant distro.
>
> The script should sort itself out. Just try
> <wherever nb is>\java2\ant\bin\ant.bat -version
>
> Mine reports
> > $NB_HOME/java2/ant/bin/ant -version
> Apache Ant version 1.7.0 compiled on December 13 2006
>
> If you get a 1.7.0, try running the build.
>
> bonekrusher wrote:
>> Ok, when I added JAVACMD environment variable, I can not use ant. I set
>> the
>> variable to:
>>
>> C:\Program Files\Java\jdk1.6.0_04\bin
>>
>>
>>
>> bonekrusher wrote:
>>> Ok,
>>>
>>> My java home is: C:\Program Files\Java\jdk1.6.0_04
>>>
>>> I copied the jar files to: C:\Program
>>> Files\Java\jdk1.6.0_04\lib\endorsed
>>> [still didnt work]
>>>
>>> Ant Version: Apache Ant version 1.7.1 compiled on June 27 2008
>>>
>>> I did not have a JAVACMD environment variable - I added it and will
>>> reboot.
>>>
>>> Check back in a few minutes.
>>>
>>> Bones
>>>
>>>
>>>
>>>
>>> Andreas Delmelle-2 wrote:
>>>> On Jul 13, 2008, at 14:04, Peter B. West wrote:
>>>>
>>>>> bonekrusher wrote:
>>>>>> Ok, I wanted to test this at home to see if this was a machine issue.
>>>>>> Tested on:
>>>>>> Windows XP sp2
>>>>>> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
>>>>>> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>>>>>> I am still unable to build with ant. I get another set of errors.
>>>>>> I will email Jeremias the out.txt file.
>>>>>> I also tried the the version
>>>>>> (src/java/org/apache/fop/events/model/EventModel.java) posted, but
>>>>>> got a
>>>>>> bunch of errors. I will send that report to.
>>>>>> Bones
>>>>> What does
>>>>> ant -version
>>>>> tell you?
>>>>>
>>>>> How do you find out which command is being executed in Windows? In
>>>>> linux, you execute
>>>>> which ant
>>>> Come to think of it, also check whether there is a JAVACMD
>>>> environment variable that points to a java executable in a location
>>>> other than JAVA_HOME/bin.
>>>> In that case, the Java home echoed by the build script may throw one
>>>> off course in determining the version of Java that is actually used.
>>>>
>>>>
>>>> Cheers
>>>>
>>>> Andreas
>>>>
>>>>
>>>>
>>>
>>
>
>
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18430423.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
NetBeans includes an ant distro.
The script should sort itself out. Just try
<wherever nb is>\java2\ant\bin\ant.bat -version
Mine reports
> $NB_HOME/java2/ant/bin/ant -version
Apache Ant version 1.7.0 compiled on December 13 2006
If you get a 1.7.0, try running the build.
bonekrusher wrote:
> Ok, when I added JAVACMD environment variable, I can not use ant. I set the
> variable to:
>
> C:\Program Files\Java\jdk1.6.0_04\bin
>
>
>
> bonekrusher wrote:
>> Ok,
>>
>> My java home is: C:\Program Files\Java\jdk1.6.0_04
>>
>> I copied the jar files to: C:\Program Files\Java\jdk1.6.0_04\lib\endorsed
>> [still didnt work]
>>
>> Ant Version: Apache Ant version 1.7.1 compiled on June 27 2008
>>
>> I did not have a JAVACMD environment variable - I added it and will
>> reboot.
>>
>> Check back in a few minutes.
>>
>> Bones
>>
>>
>>
>>
>> Andreas Delmelle-2 wrote:
>>> On Jul 13, 2008, at 14:04, Peter B. West wrote:
>>>
>>>> bonekrusher wrote:
>>>>> Ok, I wanted to test this at home to see if this was a machine issue.
>>>>> Tested on:
>>>>> Windows XP sp2
>>>>> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
>>>>> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>>>>> I am still unable to build with ant. I get another set of errors.
>>>>> I will email Jeremias the out.txt file.
>>>>> I also tried the the version
>>>>> (src/java/org/apache/fop/events/model/EventModel.java) posted, but
>>>>> got a
>>>>> bunch of errors. I will send that report to.
>>>>> Bones
>>>> What does
>>>> ant -version
>>>> tell you?
>>>>
>>>> How do you find out which command is being executed in Windows? In
>>>> linux, you execute
>>>> which ant
>>> Come to think of it, also check whether there is a JAVACMD
>>> environment variable that points to a java executable in a location
>>> other than JAVA_HOME/bin.
>>> In that case, the Java home echoed by the build script may throw one
>>> off course in determining the version of Java that is actually used.
>>>
>>>
>>> Cheers
>>>
>>> Andreas
>>>
>>>
>>>
>>
>
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Ok, when I added JAVACMD environment variable, I can not use ant. I set the
variable to:
C:\Program Files\Java\jdk1.6.0_04\bin
bonekrusher wrote:
>
> Ok,
>
> My java home is: C:\Program Files\Java\jdk1.6.0_04
>
> I copied the jar files to: C:\Program Files\Java\jdk1.6.0_04\lib\endorsed
> [still didnt work]
>
> Ant Version: Apache Ant version 1.7.1 compiled on June 27 2008
>
> I did not have a JAVACMD environment variable - I added it and will
> reboot.
>
> Check back in a few minutes.
>
> Bones
>
>
>
>
> Andreas Delmelle-2 wrote:
>>
>> On Jul 13, 2008, at 14:04, Peter B. West wrote:
>>
>>> bonekrusher wrote:
>>>> Ok, I wanted to test this at home to see if this was a machine issue.
>>>> Tested on:
>>>> Windows XP sp2
>>>> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
>>>> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>>>> I am still unable to build with ant. I get another set of errors.
>>>> I will email Jeremias the out.txt file.
>>>> I also tried the the version
>>>> (src/java/org/apache/fop/events/model/EventModel.java) posted, but
>>>> got a
>>>> bunch of errors. I will send that report to.
>>>> Bones
>>>
>>> What does
>>> ant -version
>>> tell you?
>>>
>>> How do you find out which command is being executed in Windows? In
>>> linux, you execute
>>> which ant
>>
>> Come to think of it, also check whether there is a JAVACMD
>> environment variable that points to a java executable in a location
>> other than JAVA_HOME/bin.
>> In that case, the Java home echoed by the build script may throw one
>> off course in determining the version of Java that is actually used.
>>
>>
>> Cheers
>>
>> Andreas
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18429023.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Ok,
My java home is: C:\Program Files\Java\jdk1.6.0_04
I copied the jar files to: C:\Program Files\Java\jdk1.6.0_04\lib\endorsed
[still didnt work]
Ant Version: Apache Ant version 1.7.1 compiled on June 27 2008
I did not have a JAVACMD environment variable - I added it and will reboot.
Check back in a few minutes.
Bones
Andreas Delmelle-2 wrote:
>
> On Jul 13, 2008, at 14:04, Peter B. West wrote:
>
>> bonekrusher wrote:
>>> Ok, I wanted to test this at home to see if this was a machine issue.
>>> Tested on:
>>> Windows XP sp2
>>> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
>>> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>>> I am still unable to build with ant. I get another set of errors.
>>> I will email Jeremias the out.txt file.
>>> I also tried the the version
>>> (src/java/org/apache/fop/events/model/EventModel.java) posted, but
>>> got a
>>> bunch of errors. I will send that report to.
>>> Bones
>>
>> What does
>> ant -version
>> tell you?
>>
>> How do you find out which command is being executed in Windows? In
>> linux, you execute
>> which ant
>
> Come to think of it, also check whether there is a JAVACMD
> environment variable that points to a java executable in a location
> other than JAVA_HOME/bin.
> In that case, the Java home echoed by the build script may throw one
> off course in determining the version of Java that is actually used.
>
>
> Cheers
>
> Andreas
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18428888.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 13, 2008, at 14:04, Peter B. West wrote:
> bonekrusher wrote:
>> Ok, I wanted to test this at home to see if this was a machine issue.
>> Tested on:
>> Windows XP sp2
>> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
>> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>> I am still unable to build with ant. I get another set of errors.
>> I will email Jeremias the out.txt file.
>> I also tried the the version
>> (src/java/org/apache/fop/events/model/EventModel.java) posted, but
>> got a
>> bunch of errors. I will send that report to.
>> Bones
>
> What does
> ant -version
> tell you?
>
> How do you find out which command is being executed in Windows? In
> linux, you execute
> which ant
Come to think of it, also check whether there is a JAVACMD
environment variable that points to a java executable in a location
other than JAVA_HOME/bin.
In that case, the Java home echoed by the build script may throw one
off course in determining the version of Java that is actually used.
Cheers
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
bonekrusher wrote:
> Ok, I wanted to test this at home to see if this was a machine issue.
>
> Tested on:
>
> Windows XP sp2
> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>
> I am still unable to build with ant. I get another set of errors.
>
> I will email Jeremias the out.txt file.
>
> I also tried the the version
> (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a
> bunch of errors. I will send that report to.
>
> Bones
>
What does
ant -version
tell you?
How do you find out which command is being executed in Windows? In
linux, you execute
which ant
or
type ant
Can you do the equivalent on your system.
Can you list the files and file sizes of lib and lib/build?
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Ok, I wanted to test this at home to see if this was a machine issue.
Tested on:
Windows XP sp2
Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
I am still unable to build with ant. I get another set of errors.
I will email Jeremias the out.txt file.
I also tried the the version
(src/java/org/apache/fop/events/model/EventModel.java) posted, but got a
bunch of errors. I will send that report to.
Bones
Jeremias Maerki-2 wrote:
>
> On 12.07.2008 11:56:23 Andreas Delmelle wrote:
>> On Jul 11, 2008, at 13:22, Jeremias Maerki wrote:
>>
>> > Bonekrusher and I had an exchange off-list. He did a few tests for me
>> > and my recent change didn't help either.
>> >
>> > Basically, we established the following:
>> > - He's also running WinXP
>> > - He's running the same JDK as I do.
>>
>> The /exact/ same one (identical build)?
>
> Yes, Sun 1.6.0_04
>
>>
>> Just asking, since I remember running across some issues/
>> inconsistencies in the way the java.net.URL and java.net.URI
>> translate themselves to a String.
>> Maybe that's what's playing here... Is the warning about the
>> deprecated File.toURL() maybe related and a hint?
>
> If it is in fact the file URL that's the problem, I'm pretty sure the
> problem happens within Xalan as I'm passing in a StreamResult(File).
>
>> As of Java 6, the recommended way is to use File.toURI().toURL().
>> According to the API docs, File.toURL() "does not automatically
>> escape characters that are illegal in URLs. It is recommended that
>> new code convert an abstract pathname into a URL by first converting
>> it into a URI, via the toURI method, and then converting the URI into
>> a URL via the URI.toURL method."
>
> I guess it makes sense to change all occurences now that we're on Java
> 1.4. I've changed the StreamSource(File) to
> StreamSource(File.toURI().toURL().toExternalForm()) as a first
> experiment. Bonekrusher can then retry on his machine.
> http://svn.apache.org/viewvc?rev=676161&view=rev
>
> On my machine the following:
> System.out.println(outputFile.toURI().toASCIIString());
> System.out.println(outputFile.toURI().toString());
> System.out.println(outputFile.toURI().toURL().toExternalForm());
> System.out.println(outputFile.toURL().toExternalForm());
> yielded the following results:
> [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]
> file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
>
> Just for reference, Bonekrusher got
> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml
> on his machine (see his first post).
>
>> Makes you wonder why the implementation of toURL() then does not
>> simply do that already... I assume this is for reasons of backward-
>> compatibility, so as to not break any existing code that relies on
>> that behavior (?)
>
> Probably.
>
>>
>>
>> Cheers
>>
>> Andreas
>
>
>
>
> Jeremias Maerki
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18428400.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 12.07.2008 11:56:23 Andreas Delmelle wrote:
> On Jul 11, 2008, at 13:22, Jeremias Maerki wrote:
>
> > Bonekrusher and I had an exchange off-list. He did a few tests for me
> > and my recent change didn't help either.
> >
> > Basically, we established the following:
> > - He's also running WinXP
> > - He's running the same JDK as I do.
>
> The /exact/ same one (identical build)?
Yes, Sun 1.6.0_04
>
> Just asking, since I remember running across some issues/
> inconsistencies in the way the java.net.URL and java.net.URI
> translate themselves to a String.
> Maybe that's what's playing here... Is the warning about the
> deprecated File.toURL() maybe related and a hint?
If it is in fact the file URL that's the problem, I'm pretty sure the
problem happens within Xalan as I'm passing in a StreamResult(File).
> As of Java 6, the recommended way is to use File.toURI().toURL().
> According to the API docs, File.toURL() "does not automatically
> escape characters that are illegal in URLs. It is recommended that
> new code convert an abstract pathname into a URL by first converting
> it into a URI, via the toURI method, and then converting the URI into
> a URL via the URI.toURL method."
I guess it makes sense to change all occurences now that we're on Java
1.4. I've changed the StreamSource(File) to
StreamSource(File.toURI().toURL().toExternalForm()) as a first
experiment. Bonekrusher can then retry on his machine.
http://svn.apache.org/viewvc?rev=676161&view=rev
On my machine the following:
System.out.println(outputFile.toURI().toASCIIString());
System.out.println(outputFile.toURI().toString());
System.out.println(outputFile.toURI().toURL().toExternalForm());
System.out.println(outputFile.toURL().toExternalForm());
yielded the following results:
[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] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
Just for reference, Bonekrusher got
file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml
on his machine (see his first post).
> Makes you wonder why the implementation of toURL() then does not
> simply do that already... I assume this is for reasons of backward-
> compatibility, so as to not break any existing code that relies on
> that behavior (?)
Probably.
>
>
> Cheers
>
> Andreas
Jeremias Maerki
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Andreas Delmelle <an...@telenet.be>.
On Jul 11, 2008, at 13:22, Jeremias Maerki wrote:
> Bonekrusher and I had an exchange off-list. He did a few tests for me
> and my recent change didn't help either.
>
> Basically, we established the following:
> - He's also running WinXP
> - He's running the same JDK as I do.
The /exact/ same one (identical build)?
Just asking, since I remember running across some issues/
inconsistencies in the way the java.net.URL and java.net.URI
translate themselves to a String.
Maybe that's what's playing here... Is the warning about the
deprecated File.toURL() maybe related and a hint?
As of Java 6, the recommended way is to use File.toURI().toURL().
According to the API docs, File.toURL() "does not automatically
escape characters that are illegal in URLs. It is recommended that
new code convert an abstract pathname into a URL by first converting
it into a URI, via the toURI method, and then converting the URI into
a URL via the URI.toURL method."
Makes you wonder why the implementation of toURL() then does not
simply do that already... I assume this is for reasons of backward-
compatibility, so as to not break any existing code that relies on
that behavior (?)
Cheers
Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Bonekrusher and I had an exchange off-list. He did a few tests for me
and my recent change didn't help either.
Basically, we established the following:
- He's also running WinXP
- He's running the same JDK as I do.
- The XSLT processor used in the context of the error is a normal Apache
Xalan, just like on my machine.
I think Adrian's comment (about the file URL) could be a good hint at
what's wrong but I have no idea where this is coming from. Short of
debugging the code on Bonekrusher's machine I have no idea how to fix
this problem.
On 09.07.2008 19:58:20 bonekrusher wrote:
>
> Hi Jeremias - I set you an email. Let me know if you received it. thx
>
>
> Jeremias Maerki-2 wrote:
> >
> > Not really. Please do "ant clean package >out.txt" and send me the
> > "out.txt" file (off-list).
> >
> > On 09.07.2008 16:45:48 bonekrusher wrote:
> >>
> >> I spoke to soon. I am getting the same error after the clean.
> >>
> >> I am using Java 1.6
> >>
> >> Any ideas?
> >>
> >> thx
> >>
> >>
> >> Jeremias Maerki-2 wrote:
> >> >
> >> > Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> >> > wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> >> > unexpected side-effects.
> >> >
> >> > On 09.07.2008 16:15:54 bonekrusher wrote:
> >> >>
> >> >> I downloaded the latest Trunk this morning, which should be the
> >> latest.
> >> >> Correct?
> >> > <snip/>
> >> >
> >> >
> >> >
> >> > Jeremias Maerki
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
> >> Sent from the FOP - Dev mailing list archive at Nabble.com.
> >
> >
> >
> >
> > Jeremias Maerki
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18367327.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.
Jeremias Maerki
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Hi Jeremias - I set you an email. Let me know if you received it. thx
Jeremias Maerki-2 wrote:
>
> Not really. Please do "ant clean package >out.txt" and send me the
> "out.txt" file (off-list).
>
> On 09.07.2008 16:45:48 bonekrusher wrote:
>>
>> I spoke to soon. I am getting the same error after the clean.
>>
>> I am using Java 1.6
>>
>> Any ideas?
>>
>> thx
>>
>>
>> Jeremias Maerki-2 wrote:
>> >
>> > Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
>> > wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
>> > unexpected side-effects.
>> >
>> > On 09.07.2008 16:15:54 bonekrusher wrote:
>> >>
>> >> I downloaded the latest Trunk this morning, which should be the
>> latest.
>> >> Correct?
>> > <snip/>
>> >
>> >
>> >
>> > Jeremias Maerki
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
>> Sent from the FOP - Dev mailing list archive at Nabble.com.
>
>
>
>
> Jeremias Maerki
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18367327.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Not really. Please do "ant clean package >out.txt" and send me the
"out.txt" file (off-list).
On 09.07.2008 16:45:48 bonekrusher wrote:
>
> I spoke to soon. I am getting the same error after the clean.
>
> I am using Java 1.6
>
> Any ideas?
>
> thx
>
>
> Jeremias Maerki-2 wrote:
> >
> > Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> > wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> > unexpected side-effects.
> >
> > On 09.07.2008 16:15:54 bonekrusher wrote:
> >>
> >> I downloaded the latest Trunk this morning, which should be the latest.
> >> Correct?
> > <snip/>
> >
> >
> >
> > Jeremias Maerki
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.
Jeremias Maerki
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
I spoke to soon. I am getting the same error after the clean.
I am using Java 1.6
Any ideas?
thx
Jeremias Maerki-2 wrote:
>
> Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> unexpected side-effects.
>
> On 09.07.2008 16:15:54 bonekrusher wrote:
>>
>> I downloaded the latest Trunk this morning, which should be the latest.
>> Correct?
> <snip/>
>
>
>
> Jeremias Maerki
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
Jeremias - thanks, that did the trick.
Now I am on to see if I can fix the table-continued implementation. Wish me
luck :)
Regards,
Jeremias Maerki-2 wrote:
>
> Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> unexpected side-effects.
>
> On 09.07.2008 16:15:54 bonekrusher wrote:
>>
>> I downloaded the latest Trunk this morning, which should be the latest.
>> Correct?
> <snip/>
>
>
>
> Jeremias Maerki
>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18362967.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
unexpected side-effects.
On 09.07.2008 16:15:54 bonekrusher wrote:
>
> I downloaded the latest Trunk this morning, which should be the latest.
> Correct?
<snip/>
Jeremias Maerki
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by Adrian Cumiskey <ad...@gmail.com>.
Looks like your generated file URL has been somehow escaped incorrectly, not sure that would work....
"file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml"
Which version of Java are you using and on which Windows platform?
Adrian.
bonekrusher wrote:
> I downloaded the latest Trunk this morning, which should be the latest.
> Correct?
>
>
> Peter B. West wrote:
>> bonekrusher wrote:
>>> Hi,
>>>
>>> I am trying to build the FOP trunk (checked out with svn) with Ant and
>>> get
>>> the following error:
>>>
>>> va:231: warning: [deprecation] toURL() in java.io.File has been
>>> deprecated
>>> [javac] urls.add(libFiles[i].toURL());
>>> [javac] ^
>>> [javac] 26 warnings
>>> [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
>>> [javac] Compiling 11 source files to
>>> C:\fop_trunk\trunk\build\sandbox-classe
>>> s
>>>
>>> resourcegen:
>>> [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
>>> [javac] Compiling 3 source files to
>>> C:\fop_trunk\trunk\build\codegen-classes
>>>
>>> [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>>>
>>> BUILD FAILED
>>> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
>>> java.io.FileNotFoundExcep
>>> tion:
>>> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
>>> l (The filename, directory name, or volume label syntax is incorrect)
>>>
>>> Total time: 33 seconds
>>>
>>> ***************************
>>>
>>> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is
>>> empty.
>>>
>>> Any thoughts:?
>> What have you got in lib/build? Have you done an update recently? Fop's
>> build environment - which has always been challenging - just gets
>> weirder and weirder.
>>
>>
>> --
>> Peter B. West <http://cv.pbw.id.au/>
>> Folio <http://defoe.sourceforge.net/folio/>
>>
>>
>
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by bonekrusher <dj...@yahoo.com>.
I downloaded the latest Trunk this morning, which should be the latest.
Correct?
Peter B. West wrote:
>
> bonekrusher wrote:
>> Hi,
>>
>> I am trying to build the FOP trunk (checked out with svn) with Ant and
>> get
>> the following error:
>>
>> va:231: warning: [deprecation] toURL() in java.io.File has been
>> deprecated
>> [javac] urls.add(libFiles[i].toURL());
>> [javac] ^
>> [javac] 26 warnings
>> [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
>> [javac] Compiling 11 source files to
>> C:\fop_trunk\trunk\build\sandbox-classe
>> s
>>
>> resourcegen:
>> [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
>> [javac] Compiling 3 source files to
>> C:\fop_trunk\trunk\build\codegen-classes
>>
>> [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>>
>> BUILD FAILED
>> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
>> java.io.FileNotFoundExcep
>> tion:
>> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
>> l (The filename, directory name, or volume label syntax is incorrect)
>>
>> Total time: 33 seconds
>>
>> ***************************
>>
>> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is
>> empty.
>>
>> Any thoughts:?
>
> What have you got in lib/build? Have you done an update recently? Fop's
> build environment - which has always been challenging - just gets
> weirder and weirder.
>
>
> --
> Peter B. West <http://cv.pbw.id.au/>
> Folio <http://defoe.sourceforge.net/folio/>
>
>
--
View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18362623.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Posted by "Peter B. West" <li...@pbw.id.au>.
bonekrusher wrote:
> Hi,
>
> I am trying to build the FOP trunk (checked out with svn) with Ant and get
> the following error:
>
> va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
> [javac] urls.add(libFiles[i].toURL());
> [javac] ^
> [javac] 26 warnings
> [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
> [javac] Compiling 11 source files to
> C:\fop_trunk\trunk\build\sandbox-classe
> s
>
> resourcegen:
> [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
> [javac] Compiling 3 source files to
> C:\fop_trunk\trunk\build\codegen-classes
>
> [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>
> BUILD FAILED
> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
> java.io.FileNotFoundExcep
> tion:
> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
> l (The filename, directory name, or volume label syntax is incorrect)
>
> Total time: 33 seconds
>
> ***************************
>
> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.
>
> Any thoughts:?
What have you got in lib/build? Have you done an update recently? Fop's
build environment - which has always been challenging - just gets
weirder and weirder.
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>