November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21005: ---------------------------------------- And for the record, here are my suggestions how we could improve it: 1. Look through the system path and find the node js binary. It should be very fast so I suggest do it when we reset the preference to default setting (but make sure we can't block UI here or something) 2. Look for npm and bower using the system path for Mac and Linux. For Windows look for either npm-cli.js or npm.cmd whatever is easier. Windows code should be smart enough to distinguish one from another and use "/path/to/node.exe /path/to/npm.cli.js" or "/path/to/npm.cmd" depending on the preference setting for the npm bin file. > Node / Bower / npm location should point to the node executable file instead of the parent folder of it > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky resolved JBTIS-399. ------------------------------------- Resolution: Done Verified the offline installation of JBDS-IS 9.0.0.Alpha2 into - JBDS 9.0.0.GA (standalone installer) - Eclipse Mars-1 JEE + JBDS from Marketplace - Eclipse Mars-1 JEE + BYOE from https://devstudio.redhat.com/9.0/stable/updates/ > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha1 > > Attachments: error.txt, j399-1.png, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-399: ------------------------------------ Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha2 > > Attachments: error.txt, j399-1.png, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-399. ----------------------------------- > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha2 > > Attachments: error.txt, j399-1.png, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21005: ---------------------------------------- Thanks for researching. So, yes, please start a SQ ASAP with the current code. And continue to improve node/npm/bower detection in a new fork which we will merge later. > Node / Bower / npm location should point to the node executable file instead of the parent folder of it > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-21005 at 11/9/15 1:36 PM: ----------------------------------------------------------------- Thanks for researching. So, yes, please start a CQ ASAP with the current code. And continue to improve node/npm/bower detection in a new fork which we will merge later. was (Author: akazakov): Thanks for researching. So, yes, please start a SQ ASAP with the current code. And continue to improve node/npm/bower detection in a new fork which we will merge later. > Node / Bower / npm location should point to the node executable file instead of the parent folder of it > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective?

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.... ] Daniel Azarov commented on JBDS-3507: ------------------------------------- There already is a bug in bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=460277 I asked them to merge it into branch for mars - 4.0_mars_bugfix, and they did it. So we just need to update our target platform now. > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBDS-3507 > URL: https://issues.jboss.org/browse/JBDS-3507 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-certification, 3rd-party-dependencies, upstream > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Daniel Azarov > Fix For: 9.x, 10.x > > Attachments: terminal.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-399: ---------------------------------- [~apodhrad] - hey - could you perform Nick's recipe from the previous post - see !j399-1.png|thumbnail! - I've disabled the network and can't get the thing to fail. I'd like to close this one if possible. Thkx! > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha1 > > Attachments: error.txt, j399-1.png, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-399: ----------------------------- Attachment: j399-1.png > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha1 > > Attachments: error.txt, j399-1.png, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-21005: ------------------------------------- [~akazakov], So here is the result of my investigation about ${system_path:node / bower / npm } 1) Linux - Works fine assuming that node / bower / npm where preinstalled on the system 2) Mac OS - Works fine if eclipse was launched from the *terminal* only. For desktop launch those vars are not available 3) Windows - Node detection works fine (points to *node.exe*). For npm and bower it gives not valid file for launch. Basically it points to bash node / npm scripts that are useless for windows, cause if we want to launch those tools directly (*without node*), on windows we will need *bower.cmd / npm.cmd*, and if we will will launch them via *node* the actuall nodejs scripts are required - */node_modules/npm/bin/npm-cli.js* & */node_modules/bower/bin/bower* So, I do believe that the process of detection can be definitely improved, but in order to make a cq ASAP (who knows how much time the eclipse guys will need for approving it?) I propose to start it with the code that is in master right now. I guess [~psrna] would be able to test it on nightly and I will work on a brunch with contribution for *webtools.jsdt.core*. WDYT ? > Node / Bower / npm location should point to the node executable file instead of the parent folder of it > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2015