March 2016 - jbosstools-issues - Jboss List Archives

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21869: ------------------------------------- The web console displays the characters properly: {noformat} express(a)4.13.4 node_modules/express 776 ├── escape-html(a)1.0.3 777 ├── array-flatten(a)1.1.1 778 ├── utils-merge(a)1.0.0 779 ├── cookie-signature(a)1.0.6 780 ├── merge-descriptors(a)1.0.1 781 ├── fresh(a)0.3.0 782 ├── range-parser(a)1.0.3 783 ├── methods(a)1.1.2 784 ├── vary(a)1.0.1 785 ├── path-to-regexp(a)0.1.7 786 ├── parseurl(a)1.3.1 787 ├── cookie(a)0.1.5 788 ├── content-type(a)1.0.1 789 ├── etag(a)1.7.0 790 ├── content-disposition(a)0.5.1 791 ├── serve-static(a)1.10.2 792 ├── depd(a)1.1.0 793 ├── qs(a)4.0.0 794 ├── finalhandler(a)0.4.1 (unpipe(a)1.0.0) 795 ├── on-finished(a)2.3.0 (ee-first(a)1.1.1) 796 ├── debug(a)2.2.0 (ms(a)0.7.1) 797 ├── proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5) 798 ├── 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) 799 ├── type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10) 800 └── accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10) 801 802 mongodb(a)2.1.7 node_modules/mongodb 803 ├── es6-promise(a)3.0.2 804 ├── 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) 805 └── mongodb-core(a)1.3.1 (bson(a)0.4.22, require_optional(a)1.0.0) {noformat} > 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 > > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ] Ilya Buziuk edited comment on JBDS-3684 at 3/17/16 8:53 AM: ------------------------------------------------------------ [~ldimaggio], but AFAIK IE also exists - http://www.windowscentral.com/how-find-internet-explorer-windows-10-if-yo... I'm not 100 % sure about Windows 10, but for previous versions IE was used as a default render for SWT.NONE was (Author: ibuziuk): [~ldimaggio], but AFAIK IE also exists - http://www.windowscentral.com/how-find-internet-explorer-windows-10-if-yo... I'm not 100 % sure about Windows 10, but for previous versions IE was used as a default render > Preview pane in HTML editor fails with 404 error with OpenJDK > ------------------------------------------------------------- > > Key: JBDS-3684 > URL: https://issues.jboss.org/browse/JBDS-3684 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Priority: Critical > Labels: openjdk > Fix For: 9.1.0.CR1 > > Attachments: preview.png > > > The editor opens the file, and its palette is displayed - the preview pane shows a 404 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21884) Not able to edit bc continously in eclipse editor

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21884?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-21884. ------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-21823 > Not able to edit bc continously in eclipse editor > ------------------------------------------------- > > Key: JBIDE-21884 > URL: https://issues.jboss.org/browse/JBIDE-21884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202 > OS: Fedora 22 & Windows 10 > Reporter: Xia Zhao > Priority: Minor > Labels: openshift_v3 > > Not able to save edited bc since the 2nd time editing it in eclipse editor, have to reopen it everytime, or will get this error: > Could not update "[xiazhao] Build Config : cakephp-example.json" for project "xiazhao" : buildconfigs "cakephp-example" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource cakephp-example: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"buildconfigs \"cakephp-example\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again","reason":"Conflict","details":{"name":"cakephp-example","kind":"buildconfigs"},"code":409} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21885) Remvoe "()" from context-menu name of Start Build

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21885: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Remvoe "()" from context-menu name of Start Build > -------------------------------------------------- > > Key: JBIDE-21885 > URL: https://issues.jboss.org/browse/JBIDE-21885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202 > OS: Fedora 22 & Windows 10 > Reporter: Xia Zhao > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: build-config-properties-menu.png > > > The "()" from context-menu name of Start Build should be removed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21885) Remvoe "()" from context-menu name of Start Build

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21885: -------------------------------- Attachment: build-config-properties-menu.png I don't see that problem !build-config-properties-menu.png|width=500! > Remvoe "()" from context-menu name of Start Build > -------------------------------------------------- > > Key: JBIDE-21885 > URL: https://issues.jboss.org/browse/JBIDE-21885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202 > OS: Fedora 22 & Windows 10 > Reporter: Xia Zhao > Priority: Minor > Labels: openshift_v3 > Attachments: build-config-properties-menu.png > > > The "()" from context-menu name of Start Build should be removed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-3684: ----------------------------------- [~ldimaggio], but AFAIK IE also exists - http://www.windowscentral.com/how-find-internet-explorer-windows-10-if-yo... I'm not 100 % sure about Windows 10, but for previous versions IE was used as a default render > Preview pane in HTML editor fails with 404 error with OpenJDK > ------------------------------------------------------------- > > Key: JBDS-3684 > URL: https://issues.jboss.org/browse/JBDS-3684 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Priority: Critical > Labels: openjdk > Fix For: 9.1.0.CR1 > > Attachments: preview.png > > > The editor opens the file, and its palette is displayed - the preview pane shows a 404 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3566: ----------------------------- Fix Version/s: 9.1.0.CR1 > include AERI in JBDS 9.1 > ------------------------ > > Key: JBDS-3566 > URL: https://issues.jboss.org/browse/JBDS-3566 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aeri, build, target-platform > Affects Versions: 9.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.CR1 > > Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png > > > Include required bundles for AERI in JBDS. Details TBD. > Maybe need these? > {code} > org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716 > org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar > org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3682: ------------------------------------- Also found that while was replacing mingw back with cygwin. LastIndex works for me. > Online installer reports missing package.js file > ------------------------------------------------ > > Key: JBDS-3682 > URL: https://issues.jboss.org/browse/JBDS-3682 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > > Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. > Right way to reference package json would be: > {code}var pjson = require(path.join(__dirname,'../package.json'));{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-571: ----------------------------------------- Nicolas, are you seeing anything in the log when it doesn't start? I'm seeing similar behavior to what is in Andrej's video, but can't get the IDE to fail on start-up. > Error loading file switchyard.xml. Unable to load the generated resource. > ------------------------------------------------------------------------- > > Key: JBTIS-571 > URL: https://issues.jboss.org/browse/JBTIS-571 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: nicolas duminil > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 9.0.0.Beta1 > > Attachments: jbtis-571_1.png, jbtis-571_2.png, Screencast_JBDS900GA_JBDSISAlpha2.webm > > > After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process. > Tested on Windows 7 and Windows 10 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21802. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B233. > Content assist for image names in "Deploy Docker Image" wizard > --------------------------------------------------------------- > > Key: JBIDE-21802 > URL: https://issues.jboss.org/browse/JBIDE-21802 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection. > If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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