[jbosstools-issues] [JBoss JIRA] (JBIDE-17668) JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x)

[ https://issues.jboss.org/browse/JBIDE-17668?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-17668 at 6/25/14 9:09 AM: ---------------------------------------------------------------- Nero, I can reproduce this on Windows. I think we will be able to take it from here. Steps are easy (just like Nero reported): 1. Start JBoss Tools/JBDS 2. Add JBoss AS 4.2.3 server 3. Open server editor, go to Deployment tab, change deployment settings to Use the JBoss deploy folder, save 4. Create a an empty EAR project 5. Start the JBoss server 6. Wait a few seconds, you will get errors - see Nero's screenshot above. It seems the tooling tries to deploy everything in the deploy folder again (which in case of JBoss AS 4.2.3 means many of the services). I think this is the culprit - see that the deploy folder is twice there: !duplicate-scanner.png! Workaround: Use workspace metadata for the deployment (this is the default) or a custom directory. I suspect that this may affect JBoss AS 5/6 and EAP 5.x as well. was (Author: mmalina): Nero, I can reproduce this on Windows. I think we will be able to take it from here. Steps are easy (just like Nero reported): 1. Start JBoss Tools/JBDS 2. Add JBoss AS 4.2.3 server 3. Open server editor, go to Deployment tab, change deployment settings to Use the JBoss deploy folder, save 4. Create a an empty EAR project 5. Start the JBoss server 6. Wait a few seconds, you will get errors - see Nero's screenshot above. It seems the tooling tries to deploy everything in the deploy folder again (which in case of JBoss AS 4.2.3 means many of the services). I think this is the culprit: Workaround: Use workspace metadata for the deployment (this is the default) or a custom directory. I suspect that this may affect JBoss AS 5/6 and EAP 5.x as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264)