[
https://issues.jboss.org/browse/JBIDE-18372?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-18372:
-------------------------------------
So with some small changes to the publish controller, I was able to show *some* progress,
specifically during the zipping procedure. But there are a few problems here in general.
It seems that the majority of the progress monitor for the publish operation is actually
taken up by things like publishStart(), publishFinish(), etc, things that (for us) are
essentially no-op. So the 30 or 40% of the progress monitor we can actually affect is
then split between however many modules we have. If we're publishing 2 projects, then
half. For this example, let's say only 1 project.
10% of this monitor is allocated to zipping, the other 90% for the remote operations.
This means the user could possibly see progress of up to 4% during the zip ;)
The remaining 90% of this monitor, though, is for the remote publish request, and the
wildfly / as7 management API does not provide any progress feedback in the futures they
return.
Remote EAP server with mgmt profile - Publishing to server shows 0 %
until done
-------------------------------------------------------------------------------
Key: JBIDE-18372
URL:
https://issues.jboss.org/browse/JBIDE-18372
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.1.Final, 4.3.x
When I publish a very big project to a remote server and it's taking minutes, the
status bar still keeps saying 0 % is complete.
I got this issue with a remote EAP 6.3 with management profile. Not sure about file
operations profile.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)