[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

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-11982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-11982.
---------------------------------

    Resolution: Done


I am not able to replicate this at all. What I am seeing is as follows:

1) Create project and server
2) Open server editor page. Note deployment page widgets are enabled
3) Start server
4) add web project to server. Note that widgets become DISABLED
5) Stop server. Note widgets are still disabled.
6) Remove module. Note widgets are STILL disabled
7) Click 'publish' button. Note editor widgets become enabled. 
8) Verify no module exists in server's deployment folder any longer
9) change server to 'metadata'
10) save server
11) deploy web project
12) Note web project is now in metadata. 
13) Note widgets are now disabled. 

In short, it is now impossible to change the server setting without first removing all modules from your server and executing a publish request. 
                
> 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