[jbosstools-issues] [JBoss JIRA] (JBIDE-11308) server adapter adds .dodeploy before Clean/publish has finished
[
https://issues.jboss.org/browse/JBIDE-11308?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11308.
---------------------------------
Resolution: Done
I just did it and can reproduce it - what happens is that .dodeploy
and then .deploying are both appearing in the deployments dir way before the progress
dialog finishes.
This is not a bug. Publish can not be "finished" until a .dodeploy is added.
Publish cannot also be considered 'finished' until the full module state is
deployed, however currently we do not wait for the entire .deployed because it would slow
things down tremendously.
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.CR1
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