-
1. Re: No publish on save with Eclipse Indigo and JBoss AS Tools
maxandersen Oct 26, 2011 3:20 AM (in response to hwellmann.de)You can also just right click on the module and choose restart.
Currently we've decided to not force a restart on .class changes because of two things:
1) when you use debugging you would no longer benefit from JDT/Java's hotcode replace when just changing the body of a class.
2) if we restart modules on every .class save you sessions will get lost. (This one was a bigger problem in previous AS's because of slower restarts)
...but just these 2 last weeks we got so many people saying this exact feature request so we will look into it - but I would love to hear if (especially #1) doesn't bother you during tomcat/glassfish usage ?
-
2. Re: No publish on save with Eclipse Indigo and JBoss AS Tools
hwellmann.de Oct 27, 2011 1:54 PM (in response to maxandersen)I hardly ever use hot swap, and more often than not, stale saved sessions get in my way when debugging.
So these two points wouldn't bother me. Anyway, when you get round to implementing the "redeploy on save" feature, if you provide a configurable timeout (which may be infinite), then the users can decide on their own how to work with the plugin.
Best regards,
Harald
-
3. Re: No publish on save with Eclipse Indigo and JBoss AS Tools
maxandersen Oct 28, 2011 5:45 AM (in response to hwellmann.de)I hardly ever use hot swap, and more often than not, stale saved sessions get in my way when debugging.
I use hotswap constantly and get annoyed when I have to navigate through stateful apps again
So these two points wouldn't bother me. Anyway, when you get round to implementing the "redeploy on save" feature, if you provide a configurable timeout (which may be infinite), then the users can decide on their own how to work with the plugin.
Which timeout exactly do you mean here ?