You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2011/06/08 21:47:58 UTC
[jira] [Created] (SMXCOMP-884) Upgrade to Quartz 2.0.1
Upgrade to Quartz 2.0.1
-----------------------
Key: SMXCOMP-884
URL: https://issues.apache.org/jira/browse/SMXCOMP-884
Project: ServiceMix Components
Issue Type: Improvement
Components: servicemix-quartz
Affects Versions: 2011.01
Reporter: Gert Vanthienen
Fix For: 2011.02
Now that the next major release of Quartz is available, we should upgrade our servicemix-quartz component to leverage that. We probably want to keep an eye on when the camel-quartz component gets updated so we can avoid having to ship multiple versions of the quartz bundles in the same ServiceMix release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SMXCOMP-884) Upgrade to Quartz 2.0.1
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046350#comment-13046350 ]
Freeman Fang commented on SMXCOMP-884:
--------------------------------------
Just one notes.
The latest spring release 3.0.5.RELEASE still need use quartz 1.x, the import quartz package version is version="[1.6.0, 2.0.0)".
And in quartz 2.0.1, the org.quartz.CronTrigger change from a class to interface, this also cause IncompatibleClassChangeError when use spring CronTriggerBean
java.lang.IncompatibleClassChangeError: class org.springframework.scheduling.quartz.CronTriggerBean has interface org.quartz.CronTrigger as super class
We probably need hold this change until spring also upgrade to quartz 2.0.x, the ticket from spring side to track this issue is [1]. And one comment from spring community in related issue[2] is "Quartz 2.0 will be for consideration in Spring 3.2, due to significant API changes."
[1]https://jira.springsource.org/browse/SPR-8275
[2]https://jira.springsource.org/browse/SPR-7987
Freeman
> Upgrade to Quartz 2.0.1
> -----------------------
>
> Key: SMXCOMP-884
> URL: https://issues.apache.org/jira/browse/SMXCOMP-884
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-quartz
> Affects Versions: 2011.01
> Reporter: Gert Vanthienen
> Fix For: 2011.02
>
>
> Now that the next major release of Quartz is available, we should upgrade our servicemix-quartz component to leverage that. We probably want to keep an eye on when the camel-quartz component gets updated so we can avoid having to ship multiple versions of the quartz bundles in the same ServiceMix release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SMXCOMP-884) Upgrade to Quartz 2.0.1
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SMXCOMP-884:
------------------------------------
Fix Version/s: (was: 2011.02)
Unsetting the fix version for now, until we have a suitable Spring release available to support this upgrade.
Thanks for pointing that out, Freeman!
> Upgrade to Quartz 2.0.1
> -----------------------
>
> Key: SMXCOMP-884
> URL: https://issues.apache.org/jira/browse/SMXCOMP-884
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-quartz
> Affects Versions: 2011.01
> Reporter: Gert Vanthienen
>
> Now that the next major release of Quartz is available, we should upgrade our servicemix-quartz component to leverage that. We probably want to keep an eye on when the camel-quartz component gets updated so we can avoid having to ship multiple versions of the quartz bundles in the same ServiceMix release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira