affects 1 projects,
and has been outstanding for 7 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml
,
and has been outstanding for 61 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
,
and has been outstanding for 61 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org
affects 1 projects,
and has been outstanding for 17 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
Done: https://issues.apache.org/jira/browse/GUMP-165
Thanks again,
Vincent
On 16/08/11 18:36, Simon Pepping wrote:
You can raise an issue in JIRA for project GUMP:
https://issues.apache.org/jira/browse/GUMP. Simon
On Tue, Aug 16, 2011 at 11:40:33AM +0100, Vincent Hennebert wrote:
Now I’m
On 12/08/11 20:38, Simon Pepping wrote:
On Wed, Aug 10, 2011 at 02:33:05PM +0100, Vincent Hennebert wrote:
On 10/08/11 12:56, Jeremias Maerki wrote:
junit-compile-java:
[mkdir] Created dir:
/srv/gump/public/workspace/xml-fop/build/test-classes
[mkdir] Created dir:
affects 1 projects,
and has been outstanding for 15 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
You can raise an issue in JIRA for project GUMP:
https://issues.apache.org/jira/browse/GUMP. Simon
On Tue, Aug 16, 2011 at 11:40:33AM +0100, Vincent Hennebert wrote:
Now I’m not too sure how to get JUnit upgraded. Should I send a mail to
general at gump.apache.org, or builds at apache.org, or
affects 1 projects,
and has been outstanding for 13 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
affects 1 projects,
and has been outstanding for 11 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
affects 1 projects,
and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 7 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
On Wed, Aug 10, 2011 at 02:33:05PM +0100, Vincent Hennebert wrote:
On 10/08/11 12:56, Jeremias Maerki wrote:
junit-compile-java:
[mkdir] Created dir:
/srv/gump/public/workspace/xml-fop/build/test-classes
[mkdir] Created dir:
/srv/gump/public/workspace/xml-fop/build/test-gensrc
affects 1 projects,
and has been outstanding for 5 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
On 10/08/11 12:56, Jeremias Maerki wrote:
junit-compile-java:
[mkdir] Created dir: /srv/gump/public/workspace/xml-fop/build/test-classes
[mkdir] Created dir: /srv/gump/public/workspace/xml-fop/build/test-gensrc
[mkdir] Created dir:
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml
affects 1 projects,
and has been outstanding for 14 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
-fop-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 14 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO
affects 1 projects,
and has been outstanding for 12 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
affects 1 projects,
and has been outstanding for 10 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
affects 1 projects,
and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 4 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 17 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml
affects 1 projects,
and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
,
and/or contact the folk at gene...@gump.apache.org.
Project xml-fop-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml
On 27 Mar 2011, at 15:30, Jeremias Maerki wrote:
To whom it may engage...
[junit] Testcase:
bookmarks_1.xml(org.apache.fop.intermediate.IntermediateFormatTestSuite$1):
Caused an ERROR
[junit] cvc-complex-type.2.4.b: The content of element 'nav:bookmark' is
not complete.
Hi,
While running the java code in unix,it is giving me following error
org.apache.fop.apps.FOPException: Failed to resolve font with embed-url
'/fonts/HEL.ttf'
any suggestion for tackling this exception
Thanks Regards,
Amit Lodha| Amdocs DDS| Tech Mahindra
Phase 3,Hinjewadi, Pune, INDIA
/org.apache.fop.apps.FOPException: Failed to resolve font with
embed-url '/fonts/HEL.ttf'/
any suggestion for tackling thisexception
Yes, the embed-url attributes expects a URL not a file reference. Try
changing /fonts/HEL.ttf to file:///fonts/HEL.ttf
Thanks,
Chris
***Thanks Regards
On 09.03.2011 17:05:19 Vincent Hennebert wrote:
On 09/03/11 07:51, Jeremias Maerki wrote:
On 08.03.2011 20:31:54 Vincent Hennebert wrote:
On 05/03/11 12:06, Jeremias Maerki wrote:
On 04.03.2011 16:06:30 Vincent Hennebert wrote:
On 03/03/11 12:44, Jeremias Maerki wrote:
Finally, after
On 05/03/11 12:06, Jeremias Maerki wrote:
On 04.03.2011 16:06:30 Vincent Hennebert wrote:
On 03/03/11 12:44, Jeremias Maerki wrote:
Finally, after over a week changing things and waiting a day for the
next build, the full test suite (minus hyphenation)
Just curious: why no hyphenation?
On 08.03.2011 20:31:54 Vincent Hennebert wrote:
On 05/03/11 12:06, Jeremias Maerki wrote:
On 04.03.2011 16:06:30 Vincent Hennebert wrote:
On 03/03/11 12:44, Jeremias Maerki wrote:
Finally, after over a week changing things and waiting a day for the
next build, the full test suite (minus
On 04.03.2011 16:06:30 Vincent Hennebert wrote:
On 03/03/11 12:44, Jeremias Maerki wrote:
Finally, after over a week changing things and waiting a day for the
next build, the full test suite (minus hyphenation)
Just curious: why no hyphenation?
Mostly because that requires the OFFO
On 03/03/11 12:44, Jeremias Maerki wrote:
Finally, after over a week changing things and waiting a day for the
next build, the full test suite (minus hyphenation)
Just curious: why no hyphenation?
is running in Gump
and passes under OpenJDK. It also uncovered a headless exception in
Batik
,
and/or contact the folk at gene...@gump.apache.org.
Project xml-fop-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only
affects 1 projects,
and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 7 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 5 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml
affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- org.apache.xmlgraphics.fop : XSL-FO (Formatting Objects) processor
- xml-fop : XSL-FO (Formatting Objects) processor
- xml-fop
affects 2 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- org.apache.xmlgraphics.fop : XSL-FO (Formatting Objects) processor
- xml-fop : XSL-FO (Formatting Objects) processor
Full details
http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xml-fop has an issue affecting its community integration.
This issue affects 2 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
Jeremias Maerki jerem...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
Summary: [PATCH] PS Renderer failed to process images using
CMYK color space
Product: Fop
Version: all
Platform: PC
OS/Version: Windows Vista
Status: NEW
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
Venkat Reddy vanukuri.ven...@googlemail.com changed:
What|Removed |Added
CC|
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
--- Comment #1 from Venkat Reddy vanukuri.ven...@googlemail.com 2009-11-23
07:44:10 UTC ---
Created an attachment (id=24591)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=24591)
Input FO file
--
Configure bugmail:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
--- Comment #2 from Venkat Reddy vanukuri.ven...@googlemail.com 2009-11-23
07:45:02 UTC ---
Created an attachment (id=24592)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=24592)
CMYK JPG image
--
Configure bugmail:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
--- Comment #3 from Venkat Reddy vanukuri.ven...@googlemail.com 2009-11-23
07:45:48 UTC ---
Created an attachment (id=24594)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=24594)
CMYK Tiff Image
--
Configure bugmail:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
--- Comment #4 from Venkat Reddy vanukuri.ven...@googlemail.com 2009-11-23
07:52:27 UTC ---
Please find that the code changes are in XMLGraphicsCommons project, the patch
should be applied to XMLGraphicsCommons and the
https://issues.apache.org/bugzilla/show_bug.cgi?id=48264
--- Comment #5 from Venkat Reddy vanukuri.ven...@googlemail.com 2009-11-23
08:01:26 UTC ---
Created an attachment (id=24595)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=24595)
Postscript output file after the changes
Please
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
affects 1 projects,
and has been outstanding for 37 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http
affects 1 projects,
and has been outstanding for 23 runs.
The current state of this project is 'Failed', with reason 'Configuration
Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http
projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop
projects,
and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http
...
:-)
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.
points, 4.0 required)
pts rule name description
-- --
0.7 SPF_FAIL SPF: sender does not match SPF record (fail)
[SPF failed: Please see
http://www.openspf.org/why.html?sender=fop-dev-return-35246
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
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
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
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
. 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
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
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
-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18428400.html
Sent from the FOP - Dev mailing list archive at Nabble.com.
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
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
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
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
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
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
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
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
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
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
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
\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
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
301 - 400 of 618 matches
Mail list logo
