[jbosstools-issues] [JBoss JIRA] (JBIDE-13825) Workspace metadata deployment is not activated without a server restart

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-13825:
---------------------------------------

Just a note: If you're gonna say that I shouldn't change the deployment settings on a running server, then I will say that the changes are enabled so it should work :)
                
> Workspace metadata deployment is not activated without a server restart
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-13825
>                 URL: https://issues.jboss.org/browse/JBIDE-13825
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.1.Final
>         Environment: JBDS 6.0.1.CR1 B354
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.0.2.Final, 4.1.0.Alpha2
>
>
> When you start an AS7 (I used EAP 6.0.1) server and then change deployment to workspace metadata and save it on the fly, you will notice that the server gets synchronized, so I would assume that the change is applied (and new deployment scanner is created), but when you then deploy something, it isn't deployed.
> After restart the new deployment scanner is added to the server.
> A side issue: Of course the .dodeploy marker stays in the deploy location, because the server doesn't pick it up (the deployment scanner is not set up), but when I delete the module from the server, at least then the .dodeploy should be removed if it's still there - currently it stays there.

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