We needed a facility to expose logging for the underlying owasp library for debug purposes. I was not really happy about hardcoding path and log4j dependency, but because the plugin launches without project classpath it seemed better convention.
I decided to hardcode the configuration file location instead of relying on facilities in clojure, as the logging tools API assumes configuration is available in clojure classpath. While it may be possible to fake the classpath loading and work backwards it hardly seems worth the effort to get logging functionality.
dgknght
commented
8 years ago
We needed a facility to expose logging for the underlying owasp library for debug purposes. I was not really happy about hardcoding path and log4j dependency, but because the plugin launches without project classpath it seemed better convention.
I decided to hardcode the configuration file location instead of relying on facilities in clojure, as the logging tools API assumes configuration is available in clojure classpath. While it may be possible to fake the classpath loading and work backwards it hardly seems worth the effort to get logging functionality.