[
https://issues.apache.org/jira/browse/IGNITE-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729495#comment-16729495
]
Ignite TC Bot commented on IGNITE-5565:
---------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2636473]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2636533&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Labels: newbie
>
> 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)
