BasicConfigurator does not call activeOptions() on
added appenders, therefore RollingFileAppender does
not work as expected with regard to pre-existing log
files. When configured from a config file,
DomConfigurator does call activeOptions() and
RollingFileAppender works as expected (that is,
initializes itself by scanning the hard drive for files
matching the log naming filespec within the defined
number range for backup versions). If one calls
activeOptions() in code after adding the appender in
code, it also works as expected.
Shouldn't BasicConfigurator call activeOptions() on its
added appenders? Or is this by design?
Thanks for considering this.