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!
We only use the relased version, and put the mimimum we need to ensure that
a basic Velocity jar has file-based logging 'out of the box' which I think
is a nice convenience for new users. This is the first time we have run
into this, and I think there is a nice fix to make everyone happy.
> 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?
Yes - what I think we can do is two-fold :
1) Look into why 1.0b4 doesn't work with Velocity and fix that.
2) Make a build target so you can build a velocity jar w/o logkit included.
That way it's simple and easy for both the new user so they don't have to go
hunt things down and setup the classpath (as well as the lazy user like
myself), and the more advanced user who runs into conflicts like this.
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
