-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans to release 2.4.0? #409
Comments
Guys, you really need to move HikariCP (or any other db pool dependency) as |
@PawelLipski thx, I overlooked that 👍 |
See my reservations to that approach, though #306 (comment) |
Hi all, I plan to work on rest of the issues/PR's whenever I can on the master branch (target 2.4.0). Unless we have more volunteer contributors, it will be a while before a release comes. But again, I don't make releases, so if you guys will up vote this issue, folks from Terracotta might do a quick release if that's what you want. However for those who can't wait, you can get pre-releases or snapshot here: |
Any status on this? We're a year out from the last release.. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Very relevant, but I'm afraid closed anyway. |
It has been three years since the last release. |
2.4.0 should be released in the near future. |
Why is this closed if there's no release? |
Looks like no issues are pending... https://github.com/quartz-scheduler/quartz/milestone/5
Quartz 2.4.0 will bump HikariCP version to 3.2.0 (from current 2.x) which also happens to be a transitive dependency of Play Framework 2.7.x (via play-slick 4.0.0). Also see enragedginger/akka-quartz-scheduler#83.
The text was updated successfully, but these errors were encountered: