[jbosstools-issues] [JBoss JIRA] (JBIDE-11308) server adapter adds .dodeploy before Clean/publish has finished

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-11308:
---------------------------------------------

it might be that it is adding .dodeploy after copying, but then it doesn't remove it when doing more copying.


Here is what I did:

1) Opened a file explorer to monitor what is in /deployments.

2) Called clean and watching file explorer.

3) Notice that the directory for the war was created and files were being copied via the progress monitor

4) Sees that .dodeploy gets added *before* the progress monitor finishes in #3

5) See AS7 server writing a .deploying file before #3 is finished.

6) progress monitor dialog closes.

Thus either the progress monitor is lying or something else weird.


                
> server adapter adds .dodeploy before Clean/publish has finished
> ---------------------------------------------------------------
>
>                 Key: JBIDE-11308
>                 URL: https://issues.jboss.org/browse/JBIDE-11308
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>            Reporter: Max Rydahl Andersen
>            Assignee: Max Rydahl Andersen
>            Priority: Critical
>             Fix For: 3.3.0.Beta2
>
>
> EXECUTE: import decent sized project, i.e. GWT project from central and follo the readme regarding tooling
> EXECUTE: after Run As have been done, right click server and press Clean...
> ASSERT: clean is done and publish goes on and then in the end .dodeploy file occurrs
> What actually seem to happen is deploymen is removed, dir added, then .dodeploy and *then* file copying occurs - causing the scanner to pickup partially deployed project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira