[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

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719378#comment-12719378 ] 

Martin Malina edited comment on JBIDE-11982 at 9/18/12 5:59 AM:
----------------------------------------------------------------

OK, so what you're saying is true in trunk, but not in Alpha1b. So I will verify this in Alpha2.
                
      was (Author: mmalina):
    OK, so what you're saying is true in trunk, but not in Alpha1b. So I will move the fix version and check in Alpha2.
                  
> 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: 4.0.0.Alpha2
>
>         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.

--
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