By removing the code that allowed an external file to be passed in, this break exiting usage of the LogbackValve. We we're relying on the setFilename method to take in a file that would be externally configured.

We are using spring boot, and expecting the config file to be stored in the JAR/WAR file does not make sense in a real production environment. That would imply that we have to have different builds with different config files based on the environment the JAR/WAR is deployed to.

If we could re-open this ticket and fix this, that would be great.

Thanks,

Jeff Stano