[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6312) JBoss Server doesn't reflect setting on Server Deployment tab

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-6312:
------------------------------------

I am absolutely not able to replicate this. Changing to metadata, default, or custom, seems to work 100% for me. This is of course depending on that you remove a module from the server (and possibly publish) before changing its deploy location. I have just tested this for 15 minutes and have not replicated any unexpected behaviour. 

> JBoss Server doesn't reflect setting on Server Deployment tab
> -------------------------------------------------------------
>
>                 Key: JBIDE-6312
>                 URL: https://jira.jboss.org/browse/JBIDE-6312
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.GA
>         Environment: JBT 3.1.0 GA
>            Reporter: Jiri Peterka
>            Assignee: Rob Stryker
>             Fix For: 3.2.x
>
>
> Steps:
> 1. Have EAP 5.0 Server defined in Servers view
> 2. In Local Deployment (Double click on server -> Deployment tab) set workspace metadata as deploy server
> 3. Start server, deploy, undeploy
> 4. Stop server
> 5 Set custom folder as default deploy folder, start server, deploy
> Change isn't reflected. Application isn't deployed according custom folder selection. My experience is this setting works very unreliably if ever.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira