[
https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-19350:
---------------------------------------
OK, so I went ahead and created a separate issue here: JBIDE-19641 . So this JIRA will
only be about being able to stop the stuck transfer. And it seems to be working.
But I would like to ask for clarification, [~rob.stryker]: Is it desirable that the module
is still shown in the Servers view under the server when the deployment was canceled?
Shouldn't it be removed from there?
Deployment/transfer operations cannot be canceled
-------------------------------------------------
Key: JBIDE-19350
URL:
https://issues.jboss.org/browse/JBIDE-19350
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Alpha1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Alpha2
Attachments: remote-publishing-stuck.png
I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with
the management profile and it got stuck during publishing (10 %).
I used the project from JBIDE-19043 - see "Steps to Reproduce".
!remote-publishing-stuck.png!
I wanted to get a more general use case before reporting this, but I'm still stuck at
canceling of the publish task, so I decided to write this JIRA before killing off Eclipse
- that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)