I did some testing today and was able to get opt-fop and friendbook-fop running fine with just replacing fop.jar, batik.jar and the avalon-framework jar with the versions shipping with fop-0.20.5rc3a. I didn't have to modify any opt-fop source code at all. Logging was working and pdf's were coming out fine.
Eelco, why did you need to patch the files? Were you seeing errors? Assuming I'm not special and simply swapping out the jars works for everyone, I'm not sure if we need a new release now (especially since the opt-fop source files don't seem to need any changes). I'd probably just rather wait until the final version of fop-0.20.5 is released--then we can do a new release with the new jars if people feel it's necessary. --jim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > zz-Schnitzer, Jeff > Sent: Monday, June 09, 2003 6:29 PM > To: [EMAIL PROTECTED] > Subject: RE: [Mav-user] maverick-opt-fop with fop-0.20.5rc3a > > > +1 > > I'm all for pressing forward. > > Jeff > > > -----Original Message----- > > From: jim moore [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 09, 2003 9:59 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [Mav-user] maverick-opt-fop with fop-0.20.5rc3a > > > > Is there any compelling reason to remain backwards compatible? It > seems > > lame > > that we have to give up configurably logging to work with both > versions. > > Maybe we should just patch it completely (i.e. with logging) for the > most > > recent version and do a new release. > > > > People that want the older version can use the previous version of > opt-fop > > but I feel that the release version should be targeted to work with > the > > most > > recent version of fop. > > > > --jim > > > > ----- Original Message ----- > > From: "Eelco Hillenius" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, June 09, 2003 12:46 PM > > Subject: [Mav-user] maverick-opt-fop with fop-0.20.5rc3a > > > > > > > Hi all, > > > > > > When using the latest version of FOP (which is the only > version that > > behaves > > > really well with my system) I came across some API changes that > breaks > > > FopTransform from maverick-opt-fop. > > > > > > 1. Options are now only supported for command line operations; 2. > > > The Avalon logger now must be set with 'driver.setLogger(log)' > > instead > > of > > > 'MessageHandler.setScreenLogger(log)'. > > > > > > I do not think 'options' is supported in any other way > now; I could > not > > find > > > any docs about it (though I didn't search the mailing list. As it > not > > really > > > encouraged anyway, imho it's best to just discard it. > > > > > > I've included a path that works with both the older (4) and the > 5rc3a > > > versions of FOP. I do not set a logger though (but have the 5rc3a > > version > > as > > > a comment), as one of the methods breaks one of the > versions. If not > > set, > > > the default (screen-) logger will be used. > > > > > > Eelco > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Etnus, makers of TotalView, The > best > > thread debugger on the planet. Designed with thread > debugging features > > you've never dreamed of, try TotalView 6 free at www.etnus.com. > > [INVALID FOOTER] > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of > TotalView, The best thread debugger on the planet. Designed > with thread debugging features you've never dreamed of, try > TotalView 6 free at www.etnus.com. [INVALID FOOTER] > ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 [INVALID FOOTER]
