2.0.5 did not print anything in debug about triggers #54

I have a problem, that quartz 2.0.1 stop working and did not run job (seem like my changes in grails app or env somehow affect quartz). I try to update to latest 2.0.5 and I see some problems:

1. I start to play with setting of plugin when it stops start job (before 2.0.1 runs job with default settings) and I done such settings in application.yml:

environments:
development:
dataSource:
...
quartz:
autoStartup: false
pluginEnabled: true
jdbcStore: false

Seems like 2.0.5 catch this settings, because it does not use jdbcStore now, but 2.0.1 can not catch values of settings. By default 2.0.1 works with RamStore, but I set setting with name 'jdbcStore' and does not matter what kind of value I set (false or true), it starts to use jdbcStore. May be I'm doing something wrong because I have read about some files that should be created QuatzConfig.groovy and quartz.properties and there are some mess with configuration of plugin. May be it is worth to show how to configure plugin in a right way for current version in readme?

2. 2.0.1 in debug mode output such line every n seconds:
   DEBUG org.quartz.core.QuartzSchedulerThread - batch acquisition of 0 triggers
   but 2.0.5 does not produce this line at all. So at least I see that in quartz 2.0.1 is running but for some reason could not get my triggers. In 2.0.5 there are not info at all, should I set other log level to get additonal info? Or there are no such message in 2.0.5? May be it is good idea to return this debug message?