Scala 2.12 support about jwt-scala HOT 14 CLOSED

@daniel-harrison It is fully decoupled actually, like 100%. I'm just having troubles with SBT. It looks like as soon as I enable cross-compilation, it will cross compile all projects with the same Scala versions even if they are different in their respective settings. I don't understand at all...

As we can see here, I only enable 2.12 for some projects and not the Play ones. But still, trying to compile Play in 2.12

Right now, I'm considering dropping Play support from the project (already published versions will stay on Maven obviously) and putting it back when they support Scala 2.12.

from jwt-scala.

Done in 0.10.0

from jwt-scala.

I wanted to do it last weekend but Play does not support 2.12 yet and I didn't have time to dive into my SBT build. So either I will find some time at some point, or wait for Play framework, or a nice PR will pop out.

from jwt-scala.

I gave it a try just now and pushed the resulting work but I couldn't find a way to properly isolate Play framework projects. Every single time I try to publish, SBT will try to build them using Scala 2.12. So frustrating as all other projects compile just fine and all tests are green...

from jwt-scala.

The truth is that I've completely forgotten about the Play dependency in your library. Maybe the easier way will be just wait till Play is be released for 2.12. Version 2.5.10 has been released few days ago, however, still no 2.12 support. I'll try to research the current state of Play 2.5.x for Scala 2.12. Anyway, thanks for your effort.

from jwt-scala.

So according to the discussion I initiated on r/scala it seems that there won't be any 2.12 support for 2.5.x Play Framework and 2.6.0 ETA is March-April 2017 (source: Play Framework Roadmap).

from jwt-scala.

it's suck that this is the only thing blocking us from upgrading to 2.12 now.

from jwt-scala.

I was able to get this building for 2.12 as made the mistake of moving things to 2.12 chasing the rabbit. Had to use snapshot deps but it seems odd that play ETA won't be out for months and no 2.12, J. I'm "only" using the jwt-json4s-jackson libraries. Is there any way this could be decoupled from play maybe or is this an architectural desire?

from jwt-scala.

dropping Play support from the project and putting it back when they support Scala 2.12

This seems as a pragmatic solution.

from jwt-scala.

@pauldijou Cool decoupled, I'm with @jurisk voting to drop play till they support; as would prefer to be on a supported 2.12 branch. Thanks for the library BTW, did everything advertised and apart from 2.12 ;) worked great.

from jwt-scala.

Hi @pauldijou , just for your info, Play Framework team just released milestone version of Play 2.6 for Scala 2.12

• https://mvnrepository.com/artifact/com.typesafe.play/play_2.12/2.6.0-M1
• https://www.playframework.com/documentation/2.6.0-M1/Migration26

from jwt-scala.

Play support is back in 0.11.0

from jwt-scala.

cool, thank you 👍

from jwt-scala.

Hey folks, if any of you have too much free time, I'm looking for feedback on this PR : #45

from jwt-scala.