News for hackers. Stuff that matters.
Re:From Ruby to Haskell, Part 1: Testing by octo_t on Thursday December 06, 2012 @07:57PM (#4884868)
libraryDependencies ++= Seq( "org.scalatra" %% "scalatra" % "2.0.4", "org.scalatra" %% "scalatra-scalate" % "2.0.4", "org.scalatra" %% "scalatra-specs2" % "2.0.4" % "test", "ch.qos.logback" % "logback-classic" % "1.0.0" % "runtime", "org.eclipse.jetty" % "jetty-webapp" % "7.6.0.v20120127" % "container", "javax.servlet" % "servlet-api" % "2.5" % "provided" )

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)

Re:From Ruby to Haskell, Part 1: Testing by danneu on Thursday December 06, 2012 @09:02PM (#4885099)
You just copy and pasted the output of giter8's black magic* and asked me if I think the resulting magical incantation is too difficult? Look at Scalatra's installation steps: http://www.scalatra.org/getting-started/installation.html. They don't even give you the sbt dependency. They just direct you to the tool that generates it for you. -- A tool that's only used for a couple other dozen projects: https://github.com/n8han/giter8/wiki/giter8-templates.

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.

Re:From Ruby to Haskell, Part 1: Testing by octo_t on Thursday December 06, 2012 @10:30PM (#4885338)
Is Maven too complicated for you or something?

Those are just the latest version of the various libs.