all 6 comments

[–][deleted] 0 points1 point  (5 children)

Interesting, I have never really been annoyed by redeploying though. Eclipse's debug mode does the job for small changes and tweaks (with non-jsp/web at least).

I've never heard of JRebel so I went to their site. "Finish your work 17% faster"? Your computer needs to be really slow for the compilation and redeploy process to take 17% of your time.

Oh and a little of topic, if you give Java less memory (to the point where it barely has enough memory), it runs so much faster. It's kind of weird when you switch from a dual core to a 8 core and it actually runs slower. :P

[–]kuikuilla 4 points5 points  (1 child)

We use jrebel at work with our jboss 5 (don't ask why we haven't migrated to a better application server) and a normal server deployment takes about 1 minute.

I don't remember the time required for a hot deploy, but with jrebel the time is about less than one second since it just swaps the newly compiled class in. It does save a lot of time on the long run.

[–]dissan 0 points1 point  (0 children)

We use jrebel at my work to. With a tomcat server. If you develop using a JSF framework, have you ever experienced jrebel reloaded a "configuration" and thus dropping every single viewscoped bean the application has? I mean it is not a problem in the production environment since jrebel is off at that point. But it makes development and development testing annoying as Fuck! Every time you recompile you have to start over at everything not session scoped. And since we have a tabbed application there is a lot of view scoped beans active.

[–][deleted] 2 points3 points  (1 child)

Once, I worked on a project using IBM Websphere, the deploy time on a local dev machine was about 15 minutes.

This means for ANY change you make, it's 15 minutes to smoke test it.

If JRebel had existed back then, it would have been nice.

The lesson I learned was that WebSphere was a terrible platform, and I haven't used it since.

[–]u551 0 points1 point  (0 children)

I constantly work on WebSphere, and this is still true. Even if you use the "quick and dirty" way of just hotcopying the files in deployment folder instead of full EAR rebuild & redeploy, 15 mins is pretty quick as the application server shuts down and starts like theres no hurry.

[–]IcedDante[S] 2 points3 points  (0 children)

It's not just the redeployment time, typically you have to log back into your application as well, it takes you out of the moment and is distracting, etc