[jbosstools-issues] [JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior
Pavol Srna (JIRA)
jira-events at lists.jboss.org
Wed Nov 20 09:54:07 EST 2013
[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavol Srna updated JBIDE-16063:
-------------------------------
Description:
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!
was:
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-screen1.png!
> 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
> Fix For: 4.1.1.Final
>
> 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!
--
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
More information about the jbosstools-issues
mailing list