If the grails-melody-plugin loads before the grails-quartz plugin, any re-configurations of the quartz scheduler thread in the Grails application do not happen when melody initializes, which results in the default scheduler thread always loading with the default configuration out of the box. If the Grails application wants to have a different scheduler thread configuration, two are created, causing issues at application shutdown.
Simple solution is to include 'quartz' in the loadAfter property of the grails-melody plugin.
If the grails-melody-plugin loads before the grails-quartz plugin, any re-configurations of the quartz scheduler thread in the Grails application do not happen when melody initializes, which results in the default scheduler thread always loading with the default configuration out of the box. If the Grails application wants to have a different scheduler thread configuration, two are created, causing issues at application shutdown.
Simple solution is to include 'quartz' in the loadAfter property of the grails-melody plugin.
Will add pull request.