4 ms·
On my wimpy Macbook Air, most Java changes reload in < 3 seconds. Compared to redeploying an entire Tomcat/Jetty app, this is several orders of magnitude better
by brikis98 14y ago
On my wimpy Macbook Air, most Java changes reload in < 3 seconds. Compared to redeploying an entire Tomcat/Jetty app, this is several orders of magnitude better. Combined with the scala console in sbt for interactive coding, the ~test command in sbt for automatically rerunning tests on each change, and the amazing error handling, this is a massive step forward for Java/Scala web development.
- papsosouid 14y ago>Compared to redeploying an entire Tomcat/Jetty app, this is several orders of magnitude better. It is? Are you building a war/ear and copying it to a server to deploy or something? I think every java IDE has support for locally building and deploying within the IDE, which is no slower than play's reloading.
- brikis98 14y agoFor simple setups, that can work. JRebel can help. For more complex servlet apps, especially those with Spring lifecycle management, this rarely works, which means a full redeploy after almost every Java change.
- sparx 14y agoIntellij Idea + JRebel, I dont have to reload stuff with my Java application.
- Uchikoma 14y agoOne usually uses JRebel instead of redeploying an app in TC/Jetty.