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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-11308:
-------------------------------------

>  .dodeploy have not always been removed by a .deployed since the deployment can happen afterwards.

I'm not sure on your meaning here.  The .dodeploy is removed first, then a .isdeploying is created. Once the module is fully deployed, the .isdeploying gets removed, and a .deployed is added.  So It's not that the .dodeploy is removed by the .deployed. The .dodeploy is removed first. The .deployed is added later.  
                
> 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: Rob Stryker
>            Priority: Critical
>             Fix For: 3.3.0.Beta3
>
>
> 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