Grails

Externalize Quartz scheduler plugin

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 0.5.5-RC1
  • Component/s: Commons, Plugins
  • Labels:
    None

Description

Move the Quartz plugin out of Grails core. The quartz will be available as separate plugin.

The current code needs to be refactored in some parts. All properties are now defined as Strings, but should be long/int dependent on the type.
Properties will be matched with Quartz.

Issue Links

This issue relates to:
GRAILS-543 Job Template is still invalid? Major Closed
This issue depends on:
GRAILS-820 Make plugins register their arefact handlers as part of bootstrapping lifecycle Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Marc Palmer added a comment -

Marcel - I think you will be dependent on GRAILS-820

Show
Marc Palmer added a comment - Marcel - I think you will be dependent on GRAILS-820
Hide
Permalink
Steven Devijver added a comment -

Don't forget about the concurrent property which should take a boolean.

Show
Steven Devijver added a comment - Don't forget about the concurrent property which should take a boolean.
Hide
Permalink
Marcel Overdijk added a comment -

Off course Steven.

The concurrent property will take a boolean.

I'm aligning the property types (and names) with the equivalent ones in the Quartz/Spring api.

Show
Marcel Overdijk added a comment - Off course Steven. The concurrent property will take a boolean. I'm aligning the property types (and names) with the equivalent ones in the Quartz/Spring api.
Hide
Permalink
Graeme Rocher added a comment -

I'm glad you've picked this up. The job stuff has needed a little bit of love since Michal stopped working on Grails

Show
Graeme Rocher added a comment - I'm glad you've picked this up. The job stuff has needed a little bit of love since Michal stopped working on Grails
Hide
Permalink
Marcel Overdijk added a comment -

I've refactored the Quartz plugin in Grails core. Property types are aligned with Spring API and I also upgraded to the latest Quartz release (1.6.0).
So GRAILS-543 is fixed now.

I'm putting externalizing the plugin itself on hold. This because of some open task/discussions about the plugin mechanism (GRAILS-872) and custom registration of Artefact handler (GRAILS-820). When these are stable, I will externalize the plugin.

Show
Marcel Overdijk added a comment - I've refactored the Quartz plugin in Grails core. Property types are aligned with Spring API and I also upgraded to the latest Quartz release (1.6.0). So GRAILS-543 is fixed now. I'm putting externalizing the plugin itself on hold. This because of some open task/discussions about the plugin mechanism (GRAILS-872) and custom registration of Artefact handler (GRAILS-820). When these are stable, I will externalize the plugin.
Hide
Permalink
Sergey Nebolsin added a comment -

fixed now

Show
Sergey Nebolsin added a comment - fixed now

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.1#660-r161644) | Report a problem
Powered by a free Atlassian JIRA open source license for Grails project. Try JIRA - bug tracking software for your team.