[jbosstools-issues] [JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

[Martin Malina (JIRA)]

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

Martin Malina edited comment on JBIDE-23039 at 9/2/16 8:30 AM:
---------------------------------------------------------------

Now I cannot start cdk at all :(

I just installed devstudio [1] on Mac, launched it, added cdk 2.2 rc3 and then tried to start.
I got an error in the error log view:
Server Container Development Environment failed to start.
An exception stack trace is not available.

Terminal view was opened and this was inside:
{code}
/usr/bin/script: illegal option -- f
                                    usage: script [-adkpqr] [-t time] [file [command ...]]
{code}

As you can see, the option -f is not supported in this Mac version of /usr/bin/script.

BTW, even if this worked, is it intentional that we will now use the terminal view instead of console? Or will both be used? It could be confusing. And note that in most cases no input will be needed (especially now with landrush removed for cdk 2.2).


[1] devstudio-10.1.0.GA-v20160901-1658-B5921-installer-standalone.jar 


was (Author: mmalina):
Now I cannot start cdk at all :(

I just installed devstudio [1], launched it, added cdk 2.2 rc3 and then tried to start.
I got an error in the error log view:
Server Container Development Environment failed to start.
An exception stack trace is not available.

Terminal view was opened and this was inside:
{code}
/usr/bin/script: illegal option -- f
                                    usage: script [-adkpqr] [-t time] [file [command ...]]
{code}

BTW, even if this worked, is it intentional that we will now use the terminal view instead of console? Or will both be used? It could be confusing. And note that in most cases no input will be needed (especially now with landrush removed for cdk 2.2).


[1] devstudio-10.1.0.GA-v20160901-1658-B5921-installer-standalone.jar 

> Need an interactive terminal that fits specific requirements
> ------------------------------------------------------------
>
>                 Key: JBIDE-23039
>                 URL: https://issues.jboss.org/browse/JBIDE-23039
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.4.1.AM2
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 4.4.1.Final
>
>         Attachments: vagranttty.png
>
>
> CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. 
> 1) I must be able to get a Process or IProcess object when a command is run
> 2) I must be able to get an event or know when the process terminates
> 3) The terminal or console must be interactive and allow user input when prompted. 
> 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. 
> These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
> 1) Creating a java Process by myself via Runtime.exec.  The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. 
> 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
>    a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
>    b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
> 3) Launching / Opening a tm.terminal view.  This solution fails requirements 1 and 2.  We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. 
> Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. 
> Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? 
> No other obvious solutions have presented themselves in the past year. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)