-
Notifications
You must be signed in to change notification settings - Fork 18
Conversation
@adriaanm compilation with actual sbt (0.13.11) fails in Travis. Maybe drop jdk6 check or compile against openjdk7? |
Thanks for the life support 👍 !
wow -- hadn't seen that one yet! we could just run everything on jdk 8 I guess? |
Just excluded JDK6 from Travis build - now all seems fine. |
@adriaanm what else I need to get continuations build for 2.12?) |
What do you mean exactly? It seems like they build ok against M4 now that you added it. |
I mean any chance it will be shipped with scala 2.12.x series? |
No, but we'll be happy to keep it going in its own repo |
(The same is true for the other modules -- we don't intend to add to the core distribution, but instead make it easier to discover and add modules to your project.) |
@adriaanm oh, I did not mean to merge scala-continuations in core distribution. I mean, will scala-continuations be published to maven? The reason I messed with cross-building (and opening this PR) is I use it in some production code, It's ok for me to maintain it further, but I want to figure out if I need to publish artifacts by my own, or it will be published under 'scala/scala-continuations' as before. |
Sure, if you or someone else steps up to become a maintainer, publishing it to maven is a matter of a few keystrokes on our end. Published artifacts imply a promise of future ones, so as long as we have that potential, I'm okay publishing to maven. |
To publish 2.11 a release, we do need to run on jdk6, though. (Compiling on jdk8 could introduce dependencies on methods not there in jdk6.) |
OK, then i will investigate the reason why jdk6 build fails. |
@adriaanm fixed! Now all builds fine under jdk6 :) |
Gladly! On Wednesday, June 8, 2016, danslapman [email protected] wrote:
|
Hello!
This PR adds cross-compilation with 2.12 scala series. I want this plugin to be alive :)