@fommil @NicolasRinaudo Any idea why, when I do `++2.11.11; coreJVM/publishSigned` (which worked just fine last time...) sbt throws an IOException because it's trying to publish the _2.12 artifacts *again*? Didn't even get a chance to try out `sbt release`...
-
Show this thread
-
No, cross-building was broken, so it was trying to build the 2.12 version twice. I fixed it by hardcoding different Scala versions in the build.
1 reply 0 retweets 0 likes -
Replying to @propensive @fommil
It's good practice to list all supported versions in `scalaVersions` and just run `+publishSigned` anyway, isn't it?
1 reply 0 retweets 0 likes -
-
Replying to @propensive @fommil
That is exactly what I meant, sorry. In my defense, my daughter is being a pest and it's hard to think straight
1 reply 0 retweets 0 likes
Replying to @NicolasRinaudo @fommil
Don't be sorry! It fixed the problem! Now I can see there's a further bug with some cases in the tests with Scala 2.11...
12:42 PM - 25 Feb 2018
from Marrakesh Medina, Morocco
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.