simplification of what I'm currently using:
<target name="pdf">
<path id="fop.classpath">
<pathelement location="${avalon-framework.jar}"/>
<pathelement location="${batik.jar}"/>
<pathelement location="${fop.jar}"/>
<pathelement location="${jimi.jar}"/>
</path>
<taskdef name="fop"
classname="org.apache.fop.tools.anttasks.Fop"
classpathref="fop.classpath"/>
<fop fofile="${fop.file}"
outfile="${pdf.file}"
format="application/pdf">
</fop>
</target>
You can also use a fileset for input files, AFAICT, any some other not so obvious stuff that I didn't understand from looking at the code.
BTW, the <fop> Task is *extremely* noisy with debugging/warning/error output (as is the commandline), and I haven't figured out a good way to turn the volume down with the Ant task.
Jerome Paul wrote:
Would it be possible to have examply code showing how to access the fop task sent to the list.cheers Jerome -----Original Message----- From: Joerg Pietschmann [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 7 January 2003 5:23 AM To: Ant Users List; Stefan Bodewig Subject: Re: Fop Task On Monday 06 January 2003 09:37, Stefan Bodewig wrote:Should we point to it from our external tasks section? I almost think it shouldn't be necessary as people who want a FOP task will have the FOP distribution already and will know about the task from FOP's docs.Ahem: it's completely undocumented and well hidden. Someone ought to do something about this. Well, I guess this someone will be me...Does it get compiled by the nightly Gump runs?I'd say yes, but I wouldn't back this if asked officially. J.Pietschmann
-- Christopher Lenz /=/ cmlenz at gmx.de -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
