• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Play for beginners - Typesafe stack out of date?

 
chris webster
Bartender
Posts: 2407
33
Linux Oracle Postgres Database Python Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've only just started looking at Play for Scala, and I started out with the stand-alone Play download. Then I decided to try out the Typesafe stack instead (on Linux Mint using the Typesafe repo), as it gives you easy integration with Akka etc. But I get the impression it's based on older versions of the individual stack components.

For example, if you follow the Typesafe getting started tutorial and create a Play project like this:

Then accept all the defaults at the various prompts, it seems you get a Play 2.0.2 project that expects to use SBT 0.11.3 with Scala 2.9.1. All of these are older versions of the respective tools, so what's going on?

It's a bit confusing, as I'm also new to Maven etc, so whenever I fire off a command to Play/SBT I get the usual "downloading the internet" experience, which just adds to the confusion as to what versions of the various libraries I'm actually using.

Is there really much difference between starting out with the Typesafe stack vs. using the stand-alone version of Play? And do you have any particular views/recommendations as to which is the better approach for a relative beginner with Scala and Play?
 
Erik Bakker
author
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Typesafe stack indeed uses older versions of the components, and if you run Play, it will download its own dependencies anyway. So I recommend using the standalone version of Play.

Personally, once I have setup a project (with 'play new'), I use a regular SBT install (from https://github.com/paulp/sbt-extras), but I think this specific one only works on Linux/OS X. The main difference between a regular SBT and using 'play' command from a Play distribution (which is basically a script that calls an included sbt), is that a regular SBT uses your regular ivy directory (~/.ivy2), while Play uses an ivy directory in its own directory. The latter leads to duplicate downloads between Play and non-Play projects.
 
chris webster
Bartender
Posts: 2407
33
Linux Oracle Postgres Database Python Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for clarifying that, Erik. It's worth knowing the pros/cons of both approaches.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic