Hi，
There is also an alternative that the community can consider using the scheduling functionality in the spring-context module, for the following reasons: 1.quartz is a very heavy framework, and most functions we don't need; 2., we already have spring dependencies in our project without introducing new dependencies; 3.spring is also Apache 2.0 license; 4.spring's scheduler supports standard CRON, and cron4j does not support standard CRON; 5.spring's code quality is very good, maintainability is good, and the quality of quartz code is not very good. On 06/21/2017 13:26，Alexey Kuznetsov<akuznet...@apache.org> wrote： Hi! 1) Cron4J is very old: Latest Cron4j 2.2.5 released: *28-Dec-2011 * Latest Quarz 2.3.0 released: *20-Apr-2017* 2) Not very friendly license: CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE Quartz is freely usable, licensed under the *Apache 2.0* license. So, if we replace Cron4J with Quartz we can move *ignite-schedule* module from lgpl profile to main distribution. Any objections? If no, I will create JIRA issue and implement this change. -- Alexey Kuznetsov
