[
https://issues.apache.org/jira/browse/IGNITE-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328887#comment-16328887
]
ASF GitHub Bot commented on IGNITE-5565:
----------------------------------------
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/3395
IGNITE-5565 replace Cron4J with Quartz
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-5565
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3395.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3395
----
commit 6760c40230dece2f439ffadd5341e0c505bf2a89
Author: Sergey Kosarev <skosarev@...>
Date: 2018-01-17T14:31:49Z
IGNITE-5565 replace Cron4J with Quartz
----
> 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: Sergey Kosarev
> Priority: Major
>
> 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.
> Also spring's scheduler could be considered as Cron4J alternative.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
