You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2017/06/21 14:44:00 UTC

[jira] [Updated] (IGNITE-5565) Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.

     [ https://issues.apache.org/jira/browse/IGNITE-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kuznetsov updated IGNITE-5565:
-------------------------------------
    Summary: Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.  (was: Replace Cron4J with Quartz for ignite-schedule module.)

> Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-5565
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5565
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>            Reporter: Alexey Kuznetsov
>            Assignee: Alexey Kuznetsov
>             Fix For: 2.1
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)