May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-732) JBDS-IS 9.0.0 GA Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-732?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-732: ------------------------------------ No problem. Tagged build public and will update the splash page link later tonight. Setting this issue to resolved since we have content approval. > JBDS-IS 9.0.0 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-732 > URL: https://issues.jboss.org/browse/TOOLSDOC-732 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create Release Notes for GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-732) JBDS-IS 9.0.0 GA Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-732?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-732. -------------------------------- Resolution: Done > JBDS-IS 9.0.0 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-732 > URL: https://issues.jboss.org/browse/TOOLSDOC-732 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create Release Notes for GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-740) Update guide is a beta revision - https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio/9.1/html-single/Update_Red_Hat_JBoss_Developer_Studio/

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-740?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-740. -------------------------------- Resolution: Done Change is in the published version of this document so I'm resolving this. Len, feel free to reopen if there is still feedback about this. > Update guide is a beta revision - https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-740 > URL: https://issues.jboss.org/browse/TOOLSDOC-740 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Update > Affects Versions: 4.1.1 > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.1.1 > > > The revision history in the update guide - https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... - indicates that it is a beta guide. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21785: ------------------------------------ using my credentials and the github API, I can now leave a status (pending, success, error, failure) on a commit in a PR, or leave comments on a PR. example: https://github.com/jbosstools/jbosstools-build-sites/pull/240 code: https://gist.github.com/nickboldt/61b9f5f7558f859787f6c688e16adac9 > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21394) Deploy docker: "Resource Name" should not error (but "*" required) if empty

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21394?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21394: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Deploy docker: "Resource Name" should not error (but "*" required) if empty > --------------------------------------------------------------------------- > > Key: JBIDE-21394 > URL: https://issues.jboss.org/browse/JBIDE-21394 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: resource-name-empty.png > > > how to reproduce: > # EXEC: in explroer: open up context menu on an openshift 3 project and choose "Deploy Docker Image..." > # ASSERT: Deploy Docker Image wizard pops up empty > Result: > The "Resource Name" field is decorated with an error marker, it should be decorated with a "*" which is used all across OpenShift when required values are missing/empty > !resource-name-empty.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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 updated JBIDE-21869: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Truncated error message display connecting to server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22115: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Truncated error message display connecting to server > ---------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.x > > Attachments: bad_token_1.png, bad_token_2.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21290: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.x > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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 has the same issue, but everything is ok when using the oc client > 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.0.Alpha1 > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22159?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22159: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Docker image is empty after selecting it from Image search wizard > ----------------------------------------------------------------- > > Key: JBIDE-22159 > URL: https://issues.jboss.org/browse/JBIDE-22159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection: > - In OpenShift Explorer, select the Deploy Image menu > - select the docker connection > - type a docker image name already pulled in the docker daemon > - delete it and click the search... button > - select the same docker image as previously typed > - once the search wizard closes, the docker Image name field is still empty. > See http://screencast.com/t/iTJX7SjB > As per [~scabanovich]: > {quote} > it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change > {quote} > and his fix proposal: > {quote} > before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue). > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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