Some experiences i thought i would share:
I am trying to use velocity and FOP in the same servlet application. I get a
clash in versions of logkit used. I use the latest FOP sources from CVS,
which uses logkit1.0b4. Using velocity 1.1, i cannot figure out which
version of logkit is being used. the dist contains a log.jar. Using the
logkit1.0b4 jar, the avalon logging system in velocity cant find a setFormat
method in FileOutputLogTarget. In the reverse, using only the velocity jars,
FOP complains about some other method!
For a while, i debated writing my own custom class loaders :). I got the
whole thing to work by writing my own (almost dummy) LogSystem (not a happy
situation, certainly). I did not want to use Log4j in velocity, since FOP in
any case uses logkit.
Any ideas on how to make this easier? Should widely used components be more
circumspect on API changes, and go thru a much longer deprecation process?
