I just tried to plug in fop .20.3 to an existing app that uses .20.2. I included the new avalon jar in my classpath, but I still get a logging error. From an end user persepective, I would just like to suggest that when you add a new component between non-version build changes that breaks the old build or throws an error, please just point me to what I need to do to fix the problem (url?) right there in the error message. I know I'm lazy, but if there's any way this can be done it would make my life a lot easier.
thx, Matt Savino > -----Original Message----- > From: Alistair Hopkins [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 27, 2002 7:53 AM > To: [EMAIL PROTECTED] > Subject: RE: Using Avalon/Logkit > > > Could the Avalon jar shipped with Fop include > org.apache.avalon.framework.logger.Log4JLogger and > org.apache.avalon.framework.logger.Logger so it's easy for us > to use log4j? > > It's only a few kb extra and it means that we don't have to > have lots of > avalon jars in the classpath, or have repackaged/custom versions of > Log4JLogger to get out of sync. > > Alistair > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
