[
https://issues.jboss.org/browse/JBIDE-20589?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-20589:
-------------------------------------
Hi:
If this is your goal, you'd be better off setting your server to automatically publish
on a build event. Rather than clicking 'publish' directly, you'd want to
perform a build (ctrl+b or other hotkey) and let the server adapter publish automatically
when the build is finished. You can do this in the server editor, in the top-right
corner.
For us to both respond to builds AND initiate builds would not be appropriate. Our
publishing code should not be kicking builds. There do exist some publishers that *do*
kick builds, but this is something we are trying to change. Server adapters should respond
to build commands, not issue them.
clicking 'Publish' should wait until build is complete
------------------------------------------------------
Key: JBIDE-20589
URL:
https://issues.jboss.org/browse/JBIDE-20589
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.3.0.Beta2
Environment: Eclipse 4.5
Reporter: The Alchemist
Assignee: Rob Stryker
It would be nice if Publishing waited for a Build to complete (if it depends on one of
the modules that's building).
I have a few projects that take ~20 seconds to build through Eclipse, but when I hit
'Publish to server', it seems to take effect eventually.
I was thinking a behavior similar to the Eclipse JUnit runner would be nice: if I do
"Run As->JUnit test", it'll wait until the build is complete (if that
project is building).
Not sure how difficult this is to implement.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)