Libraries probably shouldn't ship with a log4j configuration. The logging
configuration should be left entirely to the application IMO.
On 26 November 2011 19:37, Ivan Koblik wrote:
> I'm pretty sure this is because of log4j.xml [1] in src directory of
> Korma. I think it's take from here [2]. I
It looks like a bug in Drift. Try adding an init function which takes
one argument but doesn't do anything.
Your new migrate-config should look something like:
(defn migrate-config []
{:init (fn [_] )
:directory "/db/migrations"
:current-version db-version
:update-version update-db
I'm happy to announce the release of Cheshire 2.0.3. Cheshire is a
very fast
JSON encoding library that supports custom type encoding. You should
be
able to use it from Clojars with the following:
[cheshire "2.0.3"]
New features:
* Support for Ratio and BigDecimal encoding for both regular and
c
I'm happy to announce the release of clj-http 0.2.5. You should be
able to use it from Clojars with the following:
[clj-http "0.2.5"]
New feature:
* Multipart form uploads
Many people have requested this feature, please give it a try and open
any
issues on the github repo[1] that you find. Chec
Hello,
Thanks for this library, it'll really help me out. I'm a little
stuck on getting bootstrapped, can you perhaps give me some guidance ?
Basically I'm stuck at step 5, attempting to create my first
migration, what am I missing ?
Thanks,
Edmund
--
I'm pretty sure this is because of log4j.xml [1] in src directory of Korma.
I think it's take from here [2]. If you take a look at it, it sets root
debug level to "debug".
Try creating your own configuration and pointing to it with command line
argument:
-Dlog4j.configuration=your_log4j.xml
What
