Skip to content
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

Publish for Play 2.7 + slick 3.2? #492

Closed
ashleymercer opened this issue Jul 19, 2019 · 2 comments
Closed

Publish for Play 2.7 + slick 3.2? #492

ashleymercer opened this issue Jul 19, 2019 · 2 comments

Comments

@ashleymercer
Copy link

Would it be easy / possible to publish a version that is compatible with Play 2.7, but slick 3.2?

It looks like there are some moderately serious issues with the new java.time support in slick 3.3 (see here, and here, and here, ...) and so not being able to upgrade slick for the time becomes a blocker for upgrading to Play 2.7.

@octonato
Copy link
Member

@ashleymercer, that won't be possible because Play 2.7.x uses a version of Hikari that is incompatible with Slick 3.2.

Basically, Slick 3.2 was using an old version of Hikari and was calling a deprecated method that was then removed. See slick/slick#1821

Play 2.7.x uses a recent version of Hikari and when mixed with Slick 3.2, that removed method is not found and blows up at runtime.

@octonato octonato removed the triage label Jul 29, 2019
@ashleymercer
Copy link
Author

Ahh thanks for the explanation - suspected / feared there would be something like this! Fortunately it looks like the slick people are working on making the support for java.time optional (or allowing overrides with local implicits) so I'll wait for that work to be finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants