Stefan Bodewig wrote: > > I think I know what's going on, but I don't have all pieces together > to test it (yet) - does it work if you move the <taskdef> for FOP's > manifest task out of the target and make it a sibling of target?
Yes. If I move the taskdefs to the top of the build.xml, I get one message: Trying to override old definition of task manifest Then everything proceeds fine - apparently the xml-fop version of the task is used. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
