Jeremias Maerki wrote:

1. Provide a big fop-complete.jar which contains among the fop classes all
the utility packages with an Apache home (Commons, Avalon stuff). That's
for easy use and involves repackaging of the utility jars during build.

2. Provide the same fop.jar as before but we'll have some more jars in
out lib directory over time. This obviously means that the classpath
will get some longer.

IMO both has to be done, especially to service those who don't like a
lot of jars in their classpath.
Sounds reasonable. +1

Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to