June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19506: ------------------------------------------ merged [#1199|https://github.com/jbosstools/jbosstools-openshift/pull/1199] into master > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3829) Installer does not start properly when the user has control characters in the name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3829?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3829: -------------------------------- Priority: Minor (was: Major) > Installer does not start properly when the user has control characters in the name > ---------------------------------------------------------------------------------- > > Key: JBDS-3829 > URL: https://issues.jboss.org/browse/JBDS-3829 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Surprisingly, windows allows usernames such as n&o#t.e-r!u(e)r > With such a name, the installer does not even load the first page. It looks like it can't load some file, but I didn't get any error message out of it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3653. --------------------------------- Resolution: Done > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3841: -------------------------------- Labels: user-docs (was: ) > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Critical > Labels: user-docs > Fix For: 10.0.0.Alpha3 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3841: -------------------------------- Priority: Critical (was: Blocker) > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.Alpha3 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3653: -------------------------------- Priority: Critical (was: Blocker) > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3653: -------------------------------- Comment: was deleted (was: VirtualBox installation runs now without major problems, resolving this issue.) > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20337) Add unit tests for exploded utility projects

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20337?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20337. --------------------------------- The new test is here: https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... It seems it tests different scenarios that were added in JBIDE-22157 . And the test is passing here in master: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... So I'm closing this. > Add unit tests for exploded utility projects > -------------------------------------------- > > Key: JBIDE-20337 > URL: https://issues.jboss.org/browse/JBIDE-20337 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Add unit tests for the logic change in JBIDE-15250 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3615) virtual box cannot be installed reliably on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3615?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3615. --------------------------------- Resolution: Done VirtualBox installation runs now without major problems, resolving this issue. > virtual box cannot be installed reliably on windows > --------------------------------------------------- > > Key: JBDS-3615 > URL: https://issues.jboss.org/browse/JBDS-3615 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: vbox.log > > > look at docker-toolbox what they do that is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21869: --------------------------------------- I believe these characters to be ANSI terminal control codes. This article alludes to it http://wiki.bash-hackers.org/scripting/terminalcodes and I have seen similiar when the terminal doesnt interpret all the characters. We could probably display this correctly if we have an ANSI compatible component. > Encoding issue in when streaming Build Logs to the console > ---------------------------------------------------------- > > Key: JBIDE-21869 > URL: https://issues.jboss.org/browse/JBIDE-21869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.4.x > > Attachments: screenshot-1.png, screenshot-2.png > > > Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu. > It'll start to spew weird characters eventually : > {noformat} > I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ... > I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ... > I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble" > I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run" > I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts" > ---> Installing application source > ---> Building your Node application from source > E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok > E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13 > E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40 > ... > E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1 > ejs(a)2.4.1 node_modules/ejs > express(a)4.13.4 node_modules/express > �� escape-html(a)1.0.3 > �� array-flatten(a)1.1.1 > �� utils-merge(a)1.0.0 > �� cookie-signature(a)1.0.6 > �� merge-descriptors(a)1.0.1 > �� fresh(a)0.3.0 > �� methods(a)1.1.2 > �� range-parser(a)1.0.3 > �� vary(a)1.0.1 > �� path-to-regexp(a)0.1.7 > �� cookie(a)0.1.5 > �� parseurl(a)1.3.1 > �� content-type(a)1.0.1 > �� etag(a)1.7.0 > �� content-disposition(a)0.5.1 > �� serve-static(a)1.10.2 > �� depd(a)1.1.0 > �� qs(a)4.0.0 > �� finalhandler(a)0.4.1 (unpipe(a)1.0.0) > �� on-finished(a)2.3.0 (ee-first(a)1.1.1) > �� debug(a)2.2.0 (ms(a)0.7.1) > �� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5) > �� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1) > �� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10) > �� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10) > mongodb(a)2.1.8 node_modules/mongodb > �� es6-promise(a)3.0.2 > �� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0) > �� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2) > E0315 10:39:27.684535 1 util.go:91] npm info ok > I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image > I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ... > {noformat} > I'm running on OSX -- 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 June 2016