The problem is when using sbt:assembly the default merge strategy excludes all the reference.conf files as per If multiple files share the same relative path (e.g. a resource named application.conf in multiple dependency JARs), the default strategy is to verify that all candidates have the same contents and error out otherwise. The solution is to … Read more
as you said, To make sure this wasn’t the API’s server issue, I replicate the same query using Node.js (Express and Request libs) and it works every time. It makes me almost sure is a spray bug. your code in scala send requests with HTTP pipelining feature, do you send the requests with HTTP pipelining … Read more
Spray is production ready, but the development team (Mathias Doenitz) works for Typesafe on Akka-http now. The status of Akka-http is “development preview”. There are vague promises of a full release “within a few months”, but nothing you can take to the bank. Edited 29-July-2015: The status of Akka-HTTP is now “release candidate” with version … Read more
The conflicts appear because: you’ve specified your Scala version to be 2.11 you’ve explicitly specified the Scala version (2.10) for the reactivemongo and poi-scala libraries. The fix is to use the %% operator for those two libraries as well. “org.reactivemongo” %% “reactivemongo” % reactiveMongoVersion, “info.folone” %% “poi-scala” % foloneVersion That’s the purpose of the %% … Read more
I personally started with spray a long time ago and tried everything else there was out there for Scala. While Scala, spray, akka, shapeless, and scalaz certainly have a bit of a learning curve, once you start digging in and really learning how you are supposed to use the technologies, they make sense and I … Read more