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
Spam detection software, running on the system poa.cs.unibo.it, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system
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
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
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
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:
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,
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
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?
echobasedir ${basedir}
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
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
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:
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:
Peter,
Which file is this?
echobasedir ${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
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
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
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
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
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.
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
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
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
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
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
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,
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
That's the exception I worked around in
http://svn.apache.org/viewvc?rev=676307view=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
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
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
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,
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-Any---BUILD-FAILED
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]
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
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?
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
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
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.
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
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
39 matches
Mail list logo
