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 eddiehsu <ed...@shinewave.com.tw> on 2001/03/12 04:53:47 UTC
Can't build the FOP with newest build.xml
I met the problem when I tried to build the FOP.And I tried different version of Ant to build it.It still cause the problem.Can anyone told me hold to slove it? ( I think someone change the build.xml,because it looked different with the old one)
================
build
Fop Build System
----------------
Out of environment space
Building with classpath
Starting Ant...
Buildfile: build.xml
BUILD FAILED
build.xml:117: Unexpected element "fileset"
Total time: 0 seconds
=================
Re: Can't build the FOP with newest build.xml
Posted by Kelly Campbell <ca...@merlot.channelpoint.com>.
On Tue, Mar 13, 2001 at 11:06:34AM +0800, eddiehsu wrote:
> I tried it,but it still cause the same problem.I think it's the "fileset" tag problem.
>
> Did anyone tell me what's the probelm is
You should use the build.sh or build.bat included with the fop source to
run the build. This sets up a correct classpath which includes ant 1.3,
xerces, and xalan.
The build process is described at
http://xml.apache.org/fop/compiling.html, except this is out of date as
far as setting up the classpath goes. The current CVS code doesn't require
setting up any classpath unless you want to add JAI, or otherwise change
what FOP compiles with.
-Kelly
--
Kelly A. Campbell Software Engineer
<ca...@merlotxml.org> ChannelPoint, Inc.
<ca...@channelpoint.com> Colorado Springs, Co.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Can't build the FOP with newest build.xml
Posted by eddiehsu <ed...@shinewave.com.tw>.
I tried it,but it still cause the same problem.I think it's the "fileset" tag problem.
Did anyone tell me what's the probelm is
>
>================
>build
>Fop Build System
>----------------
>Building with classpath
>Starting Ant...
>Buildfile: build.xml
>
>BUILD FAILED
>
>build.xml:117: Unexpected element "fileset"
>
>Total time: 0 seconds
>=================
Hi, Eddie
Assuming that you are using the latest Ant, your immediate problem is of
course the "Out of environment space", which is going to cause problems no
matter what. What it is causing here is that you have NO classpath at all,
which means it is not finding an Ant JAR, among others. The way to handle
this (or try to handle this...ultimately the DOS prompt on Windows is a
pretty feeble thing) is to add a line like
shell=c:\command.com /e:1024 /p
to your config.sys, and reboot. This increases space available for your
environment variables (classpath, path, etc). You can crank the '1024' up to
something else like 2048 or 4096 (and I've been known to use 8192).
Hope this fixes the situation.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Can't build the FOP with newest build.xml
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 11:53 AM 3/12/01 +0800, eddiehsu wrote:
>I met the problem when I tried to build the FOP.And I tried different
version of Ant to build it.It still cause the problem.Can anyone told me
hold to slove it? ( I think someone change the build.xml,because it looked
different with the old one)
>
>================
>build
>Fop Build System
>----------------
>Out of environment space
>Building with classpath
>Starting Ant...
>Buildfile: build.xml
>
>BUILD FAILED
>
>build.xml:117: Unexpected element "fileset"
>
>Total time: 0 seconds
>=================
Hi, Eddie
Assuming that you are using the latest Ant, your immediate problem is of
course the "Out of environment space", which is going to cause problems no
matter what. What it is causing here is that you have NO classpath at all,
which means it is not finding an Ant JAR, among others. The way to handle
this (or try to handle this...ultimately the DOS prompt on Windows is a
pretty feeble thing) is to add a line like
shell=c:\command.com /e:1024 /p
to your config.sys, and reboot. This increases space available for your
environment variables (classpath, path, etc). You can crank the '1024' up to
something else like 2048 or 4096 (and I've been known to use 8192).
Hope this fixes the situation.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org