May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-719) Fix 'DataTransformationDeploymentEAPTest'

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-719?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík edited comment on JBTIS-719 at 5/31/16 8:24 AM: ------------------------------------------------------------- On Mac only: {code} Timeout after: 300 s.: server's state is: Started {code} --> set runtime JRE (JavaSE-1.6 is set as default) was (Author: tsedmik): On Mac only: {code} Timeout after: 300 s.: server's state is: Started {code} > Fix 'DataTransformationDeploymentEAPTest' > ----------------------------------------- > > Key: JBTIS-719 > URL: https://issues.jboss.org/browse/JBTIS-719 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Environment: Fuse on EAP 6.3.0.ER1 > JBDS 9.1.0.GA > JBDSIS 9.0.0.GA > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > > Fuse on EAP log was slightly changed. > {code} > ...file://src/data) Creating JAXBContext... > {code} > to > {code} > ...file://src/data) Created XMLInputFactory... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22465) npm, bower not recognized as an internal or external command on windows

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22465?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22465: ------------------------------------ I'll try on win7 and let you know. > npm, bower not recognized as an internal or external command on windows > ----------------------------------------------------------------------- > > Key: JBIDE-22465 > URL: https://issues.jboss.org/browse/JBIDE-22465 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.4.0.Alpha3 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > Attachments: bower.png, cmd.png, npm.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-204. ------------------------------- Resolution: Done Patch reviewed and merged by [~jjohnstn] > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22465) npm, bower not recognized as an internal or external command on windows

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22465?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22465: ------------------------------------- [~psrna], not able to reproduce against studio Alpha 3 on windows 7. Could you please confirm that this behaviour is Winodows 10 specific ? If yes, I'm going to update my Windows machine > npm, bower not recognized as an internal or external command on windows > ----------------------------------------------------------------------- > > Key: JBIDE-22465 > URL: https://issues.jboss.org/browse/JBIDE-22465 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.4.0.Alpha3 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > Attachments: bower.png, cmd.png, npm.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-719) Fix 'DataTransformationDeploymentEAPTest'

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-719?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík commented on JBTIS-719: ------------------------------------ On Mac only: {code} Timeout after: 300 s.: server's state is: Started {code} > Fix 'DataTransformationDeploymentEAPTest' > ----------------------------------------- > > Key: JBTIS-719 > URL: https://issues.jboss.org/browse/JBTIS-719 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Environment: Fuse on EAP 6.3.0.ER1 > JBDS 9.1.0.GA > JBDSIS 9.0.0.GA > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > > Fuse on EAP log was slightly changed. > {code} > ...file://src/data) Creating JAXBContext... > {code} > to > {code} > ...file://src/data) Created XMLInputFactory... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Thomas Mäder updated JBIDE-21828: --------------------------------- Story Points: 40 (was: 60) > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Thomas Mäder > Fix For: 4.4.0.Alpha3 > > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21720. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Server Adapter: user choose default route when creating the server > ------------------------------------------------------------------ > > Key: JBIDE-21720 > URL: https://issues.jboss.org/browse/JBIDE-21720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.0.Alpha2 > > > Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available. > I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22465) npm, bower not recognized as an internal or external command on windows

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22465?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-22465: ---------------------------------- Assignee: Ilya Buziuk > npm, bower not recognized as an internal or external command on windows > ----------------------------------------------------------------------- > > Key: JBIDE-22465 > URL: https://issues.jboss.org/browse/JBIDE-22465 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.4.0.Alpha3 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > Attachments: bower.png, cmd.png, npm.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20988) Preference validation fails on windows if node executable called node64.exe

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20988?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20988. ------------------------------ > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20988 > URL: https://issues.jboss.org/browse/JBIDE-20988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21076) [npm] cannot find module

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21076?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21076. ------------------------------ > [npm] cannot find module > ------------------------ > > Key: JBIDE-21076 > URL: https://issues.jboss.org/browse/JBIDE-21076 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.4.0.Alpha1 > Environment: windows > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > Attachments: screen.png > > > {code} > module.js:339 > throw err; > ^ > Error: Cannot find module 'C:\Program' > at Function.Module._resolveFilename (module.js:337:15) > at Function.Module._load (module.js:287:25) > at Function.Module.runMain (module.js:467:10) > at startup (node.js:136:18) > at node.js:963:3 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016