Hi Adam,
but in the end we decided not to do it. There are two reasons, one is strictly technical, and I would define the other "practical".
* The technical reason is that it would make the Scala IDE build harder. The "issue" is that we build the Scala IDE development branch
against the on development Scala 2.11.0(-SNAPSHOT), and there is no Akka actor artifact published against 2.11.0-SNAPSHOT.
Hence, we would need to build the Akka dependency ourselves, and experience taught us that doing so is time consuming (at best).
* The practical reason is that we are not convinced there is much benefit in having the Akka actor JAR bundled with the Scala IDE. In
most of the cases, you'll have a build file where you list your dependencies, and tools such as sbteclipse can automatically update the
project's classpath for you, which I feel makes pretty much useless having the Akka actor JAR bundled with the Scala IDE. Furthermore,
Akka and Scala have different release cycles, hence it may be (very) possible that the Akka JAR in the distribution is no longer the latest
released Akka, which I think is one more reason for not bundling Akka in the Scala IDE.
The only situation when it would make sense to have the Akka actor JAR bundled in the Scala IDE is the first time you are looking at Akka
actors, and you want to experiment without needing to create a build file for your project. But if that's what you are doing, I believe the best
need to download one more tool - maybe in the future we'll integrate the template catalogue in the Scala IDE, so that you won't need to
download Activator.
-- Mirco