One of the reasons I've been preferring haskell and clojure for my work is because scala's toolchain abused me so badly.
Fortunately, I had Clojure to fall back on already from Scala.
Leiningen single-handedly embarrasses the current state of the Scala community and it does SO much more but so effortlessly.
It's more like a Rails framework for Scala.
in your build.sbt too difficult? Admittedly a bit longer than bundling/gem installing, but not too difficult?
(Although I haven't had to use scalatra personally in a project so there might be hackery I'm missing)
Even if you typed that in by hand, you sure took a big detour on your journey of simply declaring "I just want the latest version of Scalatra that works so I can begin coding" by having to go specify Jetty version 7.6.0.v2012012759 and friends.
I don't find it "too difficult". Rather, it's just confusing, nontrivial, and it obstructed my progress with Scala.
*I know g8 just copies down a project from Github like https://github.com/scalatra/scalatra-sbt.g8/blob/master/src/..., but having tools that generate input for other build tools is along my point.
I recently dove into Scala for fun and I enjoy its terse syntax (often more terse than Ruby's!) and principles. I was really excited about it at first.
But the excitement went away pretty quickly last weekend when I actually tried building things with it.
Setting up a Sinatra app in Ruby is a matter of 'gem install sinatra', a 'require "sinatra"', and you're ready to roll.
Meanwhile setting up a Scalatra app in Scala was a far more involved process, every tutorial getting me to use a tool called 'giter8' just to copy down app boilerplate from github. I also ran into general difficulties just setting up IntelliJ/Eclipse, falling back to Vim which makes compilation errors feel like runtime errors since I had to go back to the terminal to see that my program didn't even compile.
I pine for a world where I can just `scale install scalatra` (or pop it into my Scalefile), `$ vim app.scala`, and begin coding.
I still plan on writing some "Scala for Rubyists"-type blog posts, but it's a shame I couldn't figure out and enjoy the actual workflow. I'd have more patience coming from an ecosystem that didn't make things as easy as Ruby's does, but I've realized that tools/workflow/environment are showstoppers no matter how much you enjoy a language.