You can clone with
HTTPS or Subversion.
We've been looking at migrating to the new Quartz Plugin: https://github.com/9ci/grails-quartz2 since the existing Quartz plugin which external-config-reload depends upon doesn't look to migrating to Quartz 2 anytime soon.
Was curious if you're considering updating this plugin so it'd work on newer versions of Quartz???
Yes, I would definitely consider updating this, but as I haven't looked into the grails-quartz2 integration, I'm not sure of the scope or scale of this. I do have a ticket on that project however to add backwards compatibility with the current quartz plugin, which may be a better option for us since we have many projects depending upon quartz.
Looks like they updated the quartz 2 plugin to be backwards compatible. Not sure if I can get it to work with both, but I'll try :)
I've been considering converting the quartz job to actually use a simple timer instead. We don't need the complexity that quartz gives us - it was just an easy way to do it. This will allow it to work with both quartz plugins. Any thoughts on this? Any reason why this would not be a good idea?
Off the top of my head, I don't see why not. I'd prefer to have no dependencies when using this plugin. As long as there is a some management interface should we want to change something at runtime I think simplification is a good thing.
Fix #3 - Removed quartz dependency and rely on simple Timers instead
Finished #3 and updated documentation for new release
NIce work! Will try it out today