[jbosstools-issues] [JBoss JIRA] (JBIDE-13151) Editing deployed archive doesn't reflect on server

[ https://issues.jboss.org/browse/JBIDE-13151?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13151. --------------------------------- Fix Version/s: 4.1.1.Final (was: 4.1.x) Resolution: Cannot Reproduce Bug I am 100% unable to replicate this. Your symptoms are unclear. To summarize my findings: When the server is NOT started: - renames to the archive are instantly reflected in the server's view - renames to the archive are NOT reflected on filesystem deployments folder until you manually execute a publish. THIS IS NOT A BUG. The servertools auto-publisher is NOT enabled if your server is not started. When the server IS started: - renames to the archive are instantly reflected in the server's view - renames to the archive are VERY QUICKLY reflected on filesystem deployments folder, as the publish job ensures it gets published. Using this workflow, however, is NOT SAFE because the server does NOT clean up the previous deployment. THe server only knows that you publish a module named SomeProjA.war, and then 2 minutes later publish a module named SomeProjB.war. Your deployments folder ends up with 2 deployments inside of it, and the UI does not represent this at all. Either way, I am unable to replicate your usecase. Only when the server is stopped is a manual publish required, and this is intentional, not a workaround. If the server is started, the auto-publish will automatically publish the new module with the new name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira