Oh, I should also mention that I had to reinstall sbt because it started throwing `NoSuchMethodError: sbt.package$.Zero()Lsbt/Global$`. No idea where *this* came from either. Basically nothing changed since the last release except one line of code, and some source headers.
@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
-
While I'm on a moaning streak, given that I now have to log into the Nexus Repository Manager to close the "broken" staging repository, the website hangs with a spinner. All this infrastructure we rely on is so fragile... :(
Show this thread -
Don't worry, everyone! I've found a workaround, and I'll live for another day!
Show this thread
End of conversation
New conversation -
-
-
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.
-
It's good practice to list all supported versions in `scalaVersions` and just run `+publishSigned` anyway, isn't it?
- Show replies
New conversation -
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.