QuartzConfig.groovy still doesn't have an externalized configuration mechanism built-in.
We had the same question back in '10. Our solution was to fork the plugin and use the built-in configuration with it's externalized config
Fast forward to now (March '11) and It looks like the quartz plugin has implemented some new features.
https://github.com/grails-plugins/grails-quartz/blob/master/QuartzGrailsPlugin.groovy
(checkout the loadQuartzConfig()
section at the end of the file)
It looks like the functionality is extensible via the default Config.groovy config.locations mechanism.
This is what it appears to be doing:
- loads the default config (
Config.groovy
)
- merges in the
DefaultQuartzConfig
on from the classLoader
- merges in the
QuartzConfig
from the classLoader
- loads the
quartz.properties
from the classLoader
You can setup your configuration in Config.groovy now if you want.