February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3624) Error while parsing response from auth server

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3624?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3624: ------------------------------- Component/s: installer > Error while parsing response from auth server > --------------------------------------------- > > Key: JBDS-3624 > URL: https://issues.jboss.org/browse/JBDS-3624 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: auth-error.png > > > # npm start > # type "asdf" to username field > # type "asdf" to password field > # open dev tools (Ctrl + Shift + i on Linux) > # click "Log in" button > result: > This stack trace appears in console log: > {code} > SyntaxError: Unexpected token I > at Object.parse (native) > at fromJson (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:1274:14) > at defaultHttpResponseTransform (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9463:16) > at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9554:12 > at forEach (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:343:20) > at transformData (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9553:3) > at transformResponse (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:10322:21) > at processQueue (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14795:28) > at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14811:27 > at Scope.$eval (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:16055:28) > {code} > JSON.parse failes because the server returned "Invalid user credentials for user asdf" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3626) Error message about not signed T&C agreement should give users info how to sign it

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3626?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3626: ------------------------------- Component/s: installer > Error message about not signed T&C agreement should give users info how to sign it > ---------------------------------------------------------------------------------- > > Key: JBDS-3626 > URL: https://issues.jboss.org/browse/JBDS-3626 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3622) Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3622?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3622: ------------------------------- Component/s: installer > Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3622 > URL: https://issues.jboss.org/browse/JBDS-3622 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: install_error.png > > > See the attached screenshot - the install has failed - the only option for the user is to close the installer window. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3625) Vagrant delivered by installer has no vagrant.exe

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3625?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3625: ------------------------------- Component/s: installer > Vagrant delivered by installer has no vagrant.exe > ------------------------------------------------- > > Key: JBDS-3625 > URL: https://issues.jboss.org/browse/JBDS-3625 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows x86_64 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > As [~hardy.ferentschik] pointed out in DEVEX-90 vagrant from installer (see https://github.com/redhat-developer-tooling/vagrant-distribution) has no vagrant.exe, but original vagrant installer does have it. > That should be fixed in vagrant distributed by installer, because current tools implementation expects vagrant.exe to be available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3623) VirtualBox installation fails

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3623?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3623: ------------------------------- Component/s: installer > VirtualBox installation fails > ----------------------------- > > Key: JBDS-3623 > URL: https://issues.jboss.org/browse/JBDS-3623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > VirtualBox installation fails very often. We need to investigate it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21781?page=com.atlassian.jira.plugi... ] Vineet Reynolds updated JBIDE-21781: ------------------------------------ Description: Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS. This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator. Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported: {{deviceready has not fired after 5 seconds.}} {{Channel not fired: onCordovaInfoReady}} which indicates that Cordova failed to initialise. As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w... In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}. A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot. was: Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS. This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator. Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported: {{deviceready has not fired after 5 seconds.}} {{Channel not fired: onCordovaInfoReady}} which indicates that Cordova failed to initialise. As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w... > Running Cordova projects with Cordova plugins fails on iOS simulators > --------------------------------------------------------------------- > > Key: JBIDE-21781 > URL: https://issues.jboss.org/browse/JBIDE-21781 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.1.Beta2 > Environment: Mac OS X 10.11.3 (El Capitan); > XCode 7.2.1; > JBDS 9.1.0 Beta2 > iPhone 6 Simulator (iOS 9.2) among others > Reporter: Vineet Reynolds > Priority: Blocker > > Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS. > This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator. > Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported: > {{deviceready has not fired after 5 seconds.}} > {{Channel not fired: onCordovaInfoReady}} > which indicates that Cordova failed to initialise. > As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w... > In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}. > A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-21781: --------------------------------------- Summary: Running Cordova projects with Cordova plugins fails on iOS simulators Key: JBIDE-21781 URL: https://issues.jboss.org/browse/JBIDE-21781 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.1.Beta2 Environment: Mac OS X 10.11.3 (El Capitan); XCode 7.2.1; JBDS 9.1.0 Beta2 iPhone 6 Simulator (iOS 9.2) among others Reporter: Vineet Reynolds Priority: Blocker Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS. This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator. Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported: {{deviceready has not fired after 5 seconds.}} {{Channel not fired: onCordovaInfoReady}} which indicates that Cordova failed to initialise. As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21780) Cordova projects exported as native projects fails to run in iOS simulator under XCode

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-21780: --------------------------------------- Summary: Cordova projects exported as native projects fails to run in iOS simulator under XCode Key: JBIDE-21780 URL: https://issues.jboss.org/browse/JBIDE-21780 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.1.Beta2 Environment: Mac OS X 10.11.3 (El Capitan); XCode 7.2.1; JBDS 9.1.0 Beta2 iPhone 6 Simulator (iOS 9.2) among others Reporter: Vineet Reynolds Cordova projects with Cordova plugins when exported as native projects appear to have incorrect locations set for config.xml. A new config.xml appears to be created with default content and none of the Cordova plugins in the configuration, which is incorrect. In addition, the original config.xml file is created/copied into the www/ directory, which is ignored by the build and/or runtime. When the native project is run in the iOS simulator, it shows errors/warnings that indicate failure in initialising Cordova. Plugins like the Device plugin are not loaded since they cannot be found in the config.xml (assuming the newly created config is overridding the original config), resulting in a failed application start. The output window shows the following message: {{ERROR: Plugin 'Device' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21463) Port Forwarding: No error message pop up when attempt to port-forward to a port in use

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21463?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21463. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B197. If a port is in use, triggering of port forwarding is disabled. > Port Forwarding: No error message pop up when attempt to port-forward to a port in use > -------------------------------------------------------------------------------------- > > Key: JBIDE-21463 > URL: https://issues.jboss.org/browse/JBIDE-21463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149 > OS: Fedora 17 & MAC OS 10 > Reporter: Xia Zhao > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.CR1 > > > No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21763) Environment variables validation in deploy docker image wizard is not correct/consistent

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21763?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21763. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B197. > Environment variables validation in deploy docker image wizard is not correct/consistent > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21763 > URL: https://issues.jboss.org/browse/JBIDE-21763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: env_var_validation.png, invalid_env_var_value.png > > > On 2nd page of Deploy Docker Image wizard is page containing environment variable. Dialog to create a new environment variable has a validation message but it is not correct, or at least validation message content does not fit reality. See following screenshots: > First one is when entered invalid environment variable name. Notice message contains info about invalid value, not name, although it is name what is not valid. > !env_var_validation.png! > Second screeshoot displays so-called invalid value (regarding to validation message in first screenshot), but there is no validation error. > !invalid_env_var_value.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016