Ticket #1161 (closed: fixed)
Logging service shouldn't get started until it's fully read in the config files
Reported by: | Russell Taylor | Owned by: | Russell Taylor |
---|---|---|---|
Priority: | minor | Milestone: | Iteration 22 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
At the moment, the logging starts up after the Mantid.properties file is read in, and before the Mantid.user.properties file has been read in.
This can lead to things like:
- Spurious messages about directories not existing, when in fact their about to be correctly set in the Mantid.user.properties.
- A file and/or directory for the log being created in the default place specified in the Mantid.properties file even though the Mantid.user.properties will override it.
Change History
Note: See
TracTickets for help on using
tickets.
(In [4160]) Downgrade some of the logging messages in the ConfigService - they weren't necessarily errors and could be confusing. Re #1161.