[jbosstools-issues] [JBoss JIRA] (JBIDE-11982) When you change deployment location for as7 without undeploying projects first they exist in both new and old locations

When you change deployment location for as7 without undeploying projects first they exist in both new and old locations ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-11982 URL: https://issues.jboss.org/browse/JBIDE-11982 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: jbdevstudio-product-universal-5.0.0.v201205220143N-H1345-CR1.jar Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.2, 3.4.0.M1 Attachments: JBIDE-11982.patch I stumbled upon this while verifying JBIDE-11297. When you have an AS7/EAP6 server set up to deploy in the standard deployments directory, have a project deployed, stop the server, change the deployment settings to "Use workspace metadata..." and start the server again, it will be deployed to the metadata dir, but the project will also stay in the standard deployments dir, thus it's duplicated. If you undeploy the module before stopping the server to change the deployment settings it works fine.