You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see this noted in the test README, but it is affecting my tests as well. Running in jruby incurs a higher startup cost so I'd rather not have to create a new jruby instance for every test which initializes log4r.
Is there any strategy others have adopted for re-configuring log4r during runtime? I mean a full recreate of the loggers and outputters.
The text was updated successfully, but these errors were encountered:
Just to clarify: do you want to have the object instances to be fully recreated? Are you trying to recreating the objects using a new instance of the classes?
I want to be able to reconfigure log4r when the yml config file is changed. log4j has a feature like this and if you use PropertyConfigurator.configureAndWatch it works nicely, and I'd like it in Ruby too.
When I looked in to the code it wasn't obvious to me that it could be reconfigured. I'll try to hack on that and submit a pull request.
I see this noted in the test README, but it is affecting my tests as well. Running in jruby incurs a higher startup cost so I'd rather not have to create a new jruby instance for every test which initializes log4r.
Is there any strategy others have adopted for re-configuring log4r during runtime? I mean a full recreate of the loggers and outputters.
The text was updated successfully, but these errors were encountered: