Fixing Svarog resource paths and log4j
All svarog resource paths have been updated to avoid namespace colision. The log4j has been updated to be loaded from the svarog working directory.
- log4j config file is loaded from the working directory if any
- At boot Svarog will print version and build number
- Reading the configuration in SvConf has been cleaned and error handling has been improved
- InitSvCore has been updated to return boolean, so the daemon will be able to exit if init has failed
- SvException has been removed from svarog, since it overrides the SvException in svarog-interface. The new SvException needs I18n if you expect localised messages
- Finally all project resources are now in the com.prtech.svarog namespace