Best way to “restart” Akka after code change to a Scala file?

I'm working with learning Scala and Spray to serve up an API, and each time I make a change to my Scala code, I have to restart the Akka server (currently just breaking out and then doing a container:start). Am I doing this wrong?

Coming from a scripting language I'm used to seeing my changes reflected instantly--but since this is compiled I guess this is a fact of life?


For a long time there were no such way but now we have JRebel and I think it is what you're looking for. There is already plugins (revolver and auxiliary jrebel-plugin) for SBT but generally, JRebel is tool agnostic. Licenses are free for scala developers.

Need Your Help

Spring Security - Authentication's username is null in AuthenticationSuccessHandler

java spring authentication null spring-security

I have a Customer class which has all the account info.(it does NOT extend Spring's userdetails.User class)

Read-Write UDP connected sockets?

networking sockets tcp udp

We are trying to get two programs to communicate with each other in a game-like fashion. They maintain a TCP connection with a central server for "control" type information, which that central ser...

About UNIX Resources Network

Original, collect and organize Developers related documents, information and materials, contains jQuery, Html, CSS, MySQL, .NET, ASP.NET, SQL, objective-c, iPhone, Ruby on Rails, C, SQL Server, Ruby, Arrays, Regex, ASP.NET MVC, WPF, XML, Ajax, DataBase, and so on.