[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1177) .metadata deploy issues

[Snjezana Peco (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBDS-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12521253#action_12521253 ] 

Snjezana Peco commented on JBDS-1177:
-------------------------------------

There is a problem when changing the deploy folder. The JBoss AS adapter doesn't  register that change sometimes.
If you open the Server editor, change the deploy folder, close the editor, open it again, you will notice that the deploy folder isn't always changed.
That is a bug in the Server editor. What you can do for now is to check if the deploy folder is changed by closing and opening the editor.


> .metadata deploy issues
> -----------------------
>
>                 Key: JBDS-1177
>                 URL: https://jira.jboss.org/jira/browse/JBDS-1177
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>         Environment: WinXP SP2, jdk1.5.0_13, eclipse-jee-galileo-sr2, jboss_tools 3.1 final, m2e 0.10
>            Reporter: Brice Ruth
>
> From #JbossTools on IRC:
> [11:07] <bruth> Another issue: apparently when I change from the default of deploying to .metadata to using the JBoss deploy/ folder, two things don't happen, (1) the files aren't cleaned out from .metadata and (2) the references that tell the JBoss instance to deploy things in the  .metadata folder aren't removed, so JBoss starts, deploys from deploy/ then also tries to deploy from .metadata, generating all sorts of duplicate MBean errors

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