On 9/18/01 4:01 AM, "Sengupta, Avik" <[EMAIL PROTECTED]>
wrote:
> 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?
I just tried the latest logkit, 1.0b5, and all is well
I think I know what this is - there was a small bit of trouble a long while
ago, so 1.1 would have the problem. 1.2 doesn't seem to, and it would be
mighty appreciated if you would try the 1.2 nightly as is. The 1.2 nightly
is very solid (release imminent), so there is little or no risk to your
project.
I am updating the jar and build.xml to use a version-numbered jar for this,
as it makes things clearer for all.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
If you look up, there are no limits - Japanese Proverb
