[jbosstools-issues] [JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

[Pavol Srna (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925607#comment-12925607 ] 

Pavol Srna commented on JBIDE-16063:
------------------------------------

Hi Lincoln, I agree with you that this is rather a minor issue. Feel free to resolve as won't fix.
                
> Aborting a command has strange behavior 
> ----------------------------------------
>
>                 Key: JBIDE-16063
>                 URL: https://issues.jboss.org/browse/JBIDE-16063
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>            Reporter: Pavol Srna
>            Assignee: Koen Aers
>              Labels: respin-a
>             Fix For: 4.1.1.CR1
>
>         Attachments: forge-screen-1.png, forge-screen-2.png
>
>
> I see 2 problems how aborting a command currently works.
> * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot:
> !forge-screen-1.png!
> * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error.
> !forge-screen-2.png!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira