jja-3 wrote:
Steve Tekell wrote:
maybe I am jumping in too late and saying something you already know, but....
is this not caused by using "grails.app" instead of "grails" in your config?
e.g.,
log4j {
logger {
// this
//grails.app="debug,stdout"
//should be
grails = "debug,stdout"
}}
I'm even later jumping in (found this in the archive), but wanted to add a slight modification that might help somebody. In 1.0.3, I changed to something like this:
environments {
development {
log4j {
logger {
//in 1.0.2 was:
//grails."app"="debug,stdout"
//in 1.0.3 now use:
grails {
app="debug"
}
}
}
}
}
John
Tweaking the log4j section of Config.groovy also fixed this problem for me.
It seem strange that this isn't taken care of by the "grails update"... In any case, things are working now.
