-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
@tpolecat Should I nag about this? Or is that annoying? :-) |
No, nagging is good. Thanks. Now that doobie 0.5.0 is out I'll try to spend some time on tut. |
I need this, too! |
You can test 0.6.3-M1 if you like. |
@tpolecat Doesn't work with Scala 2.11 as the project Scala version (required for Spark users). My
On
so I tried switching to
and now
|
Hm, nothing has changed in the 2.11 version and the scripted tests use it. I just did a sample project with 2.11 and it works for me. Can you make a reproduction? |
You likely have http://dl.bintray.com/tpolecat/maven/org/tpolecat/tut-core_2.11/0.6.3-M1/tut-core_2.11-0.6.3-M1.pom |
It works with M5 … no point trying M1
|
@metasim can you confirm or deny that this patch works? The fork test runs in 2.11 and passes. |
@tpolecat No, it doesn't work for me, but I haven't had time to determine why. I need to blow away my ivy cache, incrementally remove plugins, etc. to figure out what's going on. I can just file another PR if it does end up having something to do with tut. |
PS: Doesn't work with M5 because I get the exception above. |
But it works ok with 0.6.2? |
0.6.2 worked in sbt 0.13.13 with Scala 2.11.12. This (0.6.3-M5) is failing with
|
Ok. The fork test passes for sbt 1.1.1 with scala 2.11.12 so I'm not sure where to go. If you can make a reproduction I'll certainly try to chase it down. |
@tpolecat Thanks for you patience with this. I refactored my build (for other reasons), breaking it up into more subprojects, and now it works. My guess is that one of the other plugins I was using was colliding with it, but not really pressing enough for me to go back and diagnose it. So I say let's call this done. Thanks again for all your help. |
Great! |
Fixes #206. Same feature as #198.
NB: Scripted tests don't seem to be working on this branch (even before this merge).