No publish on save with Eclipse Indigo and JBoss AS Tools

[hwellmann.de]

Scenario:

I'm running a Mavenized web app on JBoss AS 7.0.2 from my Eclipse workspace via Run on Server. While the application is running, I edit and save a Java source file of the web project.

Expected behaviour:

The application gets redeployed automatically. That's how it works with other WTP adapters (e.g. Tomcat, GlassFish).

Actual behaviour:

Nothing happens. Incremental Publish has no effect either. Only Full Publish redeploys the application.

Am I missing anything, or is this a known issue?

I'm using JBoss AS Tools (and only these, not the whole bunch) from JBoss Tools 3.3.0.M3 with Eclipse Indigo 3.7.1, m2e 1.0 and m2e-wtp 0.14.0.

Best regards,

Harald

[maxandersen]

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 ?

[hwellmann.de]

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

[maxandersen]

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 ?