[
https://issues.jboss.org/browse/JBIDE-17268?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-17268:
---------------------------------------------
so since as far as i understand from koen he fixed it so wizards progressmonitor is now
honored - cant you just have the progressmonitor in forge call this interruprt ?
Making all forge wizards backgroundable seems risky...does it not ? no idea what they
might actually do and rely on.
i.e. if touching maven repo or editing files etc ?
my biggest concern is that users are told nothing - its just blocking...thus for that Koen
already fixed it so it reports it (haven't tried it yet though), but need to get more
plugins to report back what it is doing.
Forge wizards block eclipse UI while executing - need to be
backgroundable
--------------------------------------------------------------------------
Key: JBIDE-17268
URL:
https://issues.jboss.org/browse/JBIDE-17268
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: forge
Affects Versions: 4.2.0.Beta1
Reporter: Lincoln Baxter III
Assignee: Koen Aers
Priority: Blocker
Fix For: 4.2.0.Beta2
Forge wizards currently can block the eclipse UI. Run any non-trivial command and the
Eclipse interface will be completely blocked until the forge command is cancelled, which
may not be possible if the command is not using a fine-grained progress monitor and checks
frequently.
Introducing a threaded command execution would allow the use of
{code}commandThread.interrupt(){code}
And should allow both backgrounding of running wizards, but also more reliable
cancellation with Forge's proxy support for thread interrupt handling.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)