[
https://issues.jboss.org/browse/JBIDE-11712?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11712:
---------------------------------------------
Jiri, unless i'm misunderstanding what you are doing this is how it have behaved
forever.
Changes to .class does not trigger autoredeploy since you could be debugging and thus if
we redeployed you would not have the benefit of real hot deploy via Java debugger.
Possible workarounds: set the pattern for redeploy to include *.class or use jrebel to
have actual more real "class reloading".
Or are you reporting something else ?
p.s. you mention a very specific EAP6 release here? is it limited to just this or ?
Hot deployment doesn't work on EAP6 ER5 when Java EE Project is
changed
-----------------------------------------------------------------------
Key: JBIDE-11712
URL:
https://issues.jboss.org/browse/JBIDE-11712
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.0.beta3-trunk
Reporter: Jiri Peterka
Assignee: Rob Stryker
Fix For: 3.3.0.CR1
Hot deployment doesn't work on EAP6 ER5 when Java EE Project type (from JBoss
Central) is used
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira