[jbosstools-issues] [JBoss JIRA] (JBIDE-17611) Error when calling Tern code assist via command

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-17611:
---------------------------------------

[~fbricon], could you please review latest request. It does simple thing, switching to first tern embeded nodejs delivered inside bundle. If user manually switch to native nodejs, it is going to be overridden at next restart. Native nodejs is used if there is no embedded one. We kept it this way to simplify the fix.

It is not easy to verify that native nodejs is present, for example under ubuntu there is possibility that node executable in PATH doesn't come from nodejs. In this case check if node file exists doesn't guarantee it is going to work. 

One more problem under ubuntu is to have node executable in path two packages should be installed nodejs and nodejs-legacy, going to check tomorrow if that is also the case under fedora 20.

> Error when calling Tern code assist via command
> -----------------------------------------------
>
>                 Key: JBIDE-17611
>                 URL: https://issues.jboss.org/browse/JBIDE-17611
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common/jst/core
>    Affects Versions: 4.2.0.Beta2
>         Environment: JBT 4.2.0.Beta2-v20140613-0238-B137
>            Reporter: Vlado Pakan
>            Assignee: Victor Rubezhny
>            Priority: Blocker
>              Labels: respin-d
>             Fix For: 4.2.0.Beta2, 4.2.0.Beta3
>
>         Attachments: TernCompletionWithConsole.png, TernConsole.png, TernFacets.png
>
>
> See this comment https://issues.jboss.org/browse/JBIDE-17566?focusedCommentId=12975919&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975919
> Seems reproducible only for first attempt and then need to restart JBT to get exception again



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)