It seems the plugin does not understand application.groovy

[kefirfromperm]

I try to prevent start of the scheduler but it starts anyway.

application.groovy

quartz.autoStartup = false

doesn't work.

[rvanderwerf]

hmm this is odd, we have this working in our app:
environments {
development {
quartz {
autoStartup = false
jdbcStore = true
purgeQuartzTablesOnStartup = true
pluginEnabled = true
props(jdbcProps)
}
}
}
and it does not start

[jglapa]

I'm observing the same but funnily enough this behaved like that also with Grails 2.x and plugin v1

[davydotcom]

autoStartup behaves weird with the scheduler. this has been addressed I believe in 2.0.10