I'm reviewing the developer branch code and believe that although
CommandLineOptions parses the -c option and caches a userConfigFile,
the config file is not processed. FOP 0.20.5rc2 has an
org.apache.fop.configuration package for handling the -c option. Hence
it appears the -c option is not
Thanks Keiron for the feedback!
I found and reviewed the discussion regarding the move to Avalon (ref:
http://marc.theaimsgroup.com/?l=fop-devm=10226606705w=2 ).
I also appreciate your point that some aspects of configuration have
already been 're-enabled'; as exemplified in
Here's some sample code I use for configuring the PDFRenderer for the
moment:
import org.apache.avalon.framework.ExceptionUtil;
import org.apache.avalon.framework.configuration.Configurable;
import org.apache.avalon.framework.configuration.Configuration;
import
