Well, using the CLASSPATH env variable begs for trouble. I consider it a mistake of Java 1.0 that has been carried on until today. Good thing you found the problem.
BTW, Peter, are you aware that the Folio website reports an error? On 18.01.2009 10:37:40 Peter B. West wrote: > Jeremias Maerki wrote: > > I have no idea what's going wrong. It seems to work for everyone else. > > In my log output with Ant 1.7 and the "-d" option I get different log > > output. For example, Ant includes the full classpath for the "javac" > > task in the "resourcegen" target which doesn't seem to happen on your > > end. But unfortunately, Ant doesn't log the effective classpath for the > > taskdef task at all, not even the setup of the "libs-build-classpath" > > and "libs-build-tools-classpath" early in build.xml which are used by > > the taskdef. > > > > What does "ant init" spit out? Have you checked for permission problems > > on the JAR files in the lib directory? > > > > Shrug. > > The problem was an older version of fop.jar on the CLASSPATH. That is, > the build is, at some point, dependent on the CLASSPATH, which doesn't > seem to be a good idea. > > Peter Jeremias Maerki
