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
-- where, by default, logConfig is the current project directory plus "src/main/resources/logback.xml". However, the property never gets cleared after the task runs.
The result is that if you also have a logback-test.xml, which Logback is supposed to use preferentially, it'll be ignored and you'll waste some time wondering why it keeps insisting on using your production logging settings in a development environment. My workaround has been to add a hook to the compile task (compile andFinally { System.clearProperty("logback.configurationFile"); }), and I guess I could also calculate the absolute path to my logback-test.xml file and set scalateLoggingConfig to that, but I don't think either should be necessary -- the task is just not behaving well here.
The text was updated successfully, but these errors were encountered:
In ScalatePlugin.generateScalateSource, you're doing this--
-- where, by default, logConfig is the current project directory plus "src/main/resources/logback.xml". However, the property never gets cleared after the task runs.
The result is that if you also have a
logback-test.xml
, which Logback is supposed to use preferentially, it'll be ignored and you'll waste some time wondering why it keeps insisting on using your production logging settings in a development environment. My workaround has been to add a hook to the compile task (compile andFinally { System.clearProperty("logback.configurationFile"); }
), and I guess I could also calculate the absolute path to mylogback-test.xml
file and setscalateLoggingConfig
to that, but I don't think either should be necessary -- the task is just not behaving well here.The text was updated successfully, but these errors were encountered: