August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-215) Improve JSON completion apply according the JSON Schema [EBZ#494114]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-215?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco resolved ERT-215. ------------------------------- Resolution: Done > Improve JSON completion apply according the JSON Schema [EBZ#494114] > -------------------------------------------------------------------- > > Key: ERT-215 > URL: https://issues.jboss.org/browse/ERT-215 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > Fix For: Neon.1 (4.6) > > > Today, when JSON completion item is applied, it generates the "name" and "value" fields. According the JSON Schema, it generates for instance "false" as value if the JSON field is declared as "boolean" in the JSON Schema. > I think we could improve this behaviour: > * apply completion should show a second popup for boolean value ( with "true", "false"). > * apply completion should generate "true" if JSON Schema "default" declare it as "true" > * apply completion should use JSON Schema "enum" to show a second popup with "enum" values. > * apply completion should generate a JSON Object with JSON pair which declare some "name" JSON fields as "required". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-213) Support for JSON Schema Catalog [EBZ#494110]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-213?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco resolved ERT-213. ------------------------------- Resolution: Done > Support for JSON Schema Catalog [EBZ#494110] > -------------------------------------------- > > Key: ERT-213 > URL: https://issues.jboss.org/browse/ERT-213 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > Fix For: Neon.1 (4.6) > > > JSON Schema store provides a JSON Schema catalog at https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catal... > My idea is to have the same thing than XML Catalog : > * System catalog where WTP JSON plugin host https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catal... > * User Catalog to defines your own catalog > When a JSON file is opened, it checks: > * if a JSON Schema exists coming from the existing plugin extension point org.eclipse.wst.json.core.schemaCatalogContributions > * if not, it uses System and User JSON catalog and download the well JSON Schema declared inside JSON Schema Catalog. > Takes samples: > 1) User create a JSON file with name "package.json", the JSON Schema which is used comes from org.eclipse.wst.json.core.schemaCatalogContributions (because it exists) > 2) User create a JSON file with name "babelrc.json". In this case, org.eclipse.wst.json.core.schemaCatalogContributions doesn't define it and http://json.schemastore.org/babelrc is downloaded, because it is declared like this: > ----------------------------------- > "schemas": [ > { > "name": "babelrc.json", > "description": "Babel configuration file", > "fileMatch": [ ".babelrc" ], > "url": "http://json.schemastore.org/babelrc" > }, > ----------------------------------- > inside the system JSON Schema catalog (see at > https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catal...) > It should be good too to give the capability to link a JSON Schema to an image to know which icon should be displayed for the JSON file in the "Project Explorer". > Please note that today it exists JSON Catalog (which is a copy/paste from XML Catalog) in the core. An UI JSON Catalog must be implemented to show system catalog and user catalog (like XML Catalog). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-212) Apply Completion & JSON Schema support for "enum" & "default" [EBZ#494100]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-212?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco resolved ERT-212. ------------------------------- Resolution: Done > Apply Completion & JSON Schema support for "enum" & "default" [EBZ#494100] > -------------------------------------------------------------------------- > > Key: ERT-212 > URL: https://issues.jboss.org/browse/ERT-212 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > Fix For: Neon.1 (4.6) > > > JSON Editor completion should support JSON Schema "enum" when completion is applied. > Takes a samples with tsconfig.json which defines a JSON Schema for "target" like this: > ----------------------------------------------- > "target": { > "description": "Specify ECMAScript target version.", > "enum": [ > "es3", > "es5", > "es6", > "es2015" > ], > "default": "es3" > } > ----------------------------------------------- > When I open completion, it shows "target", and when I apply the completion, it generates only > ----------------------------------------------- > "target" > ----------------------------------------------- > It should be very cool, if apply completion: > * generates > ----------------------------------------------- > "target": "es3" > ----------------------------------------------- > because "es3" is defined as "default". > * and when I do tab on "es3" value, it shows a second completion popup with enum values ("es3", "es5", etc) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-390) [content assist] js editor does not know DOM objects [EBZ#497903]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-390: --------------------------------------- Summary: [content assist] js editor does not know DOM objects [EBZ#497903] Key: ERT-390 URL: https://issues.jboss.org/browse/ERT-390 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Steps to reproduce. 1. Download neon js package 2. Run and start a fresh workspace 3. Start a new js project 4. create a js file 5. edit the file and try content assist. Only language features are available in the content assist. Basic DOM objects like window and document are missing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-391) Enable JSDT Outline view in Neon [EBZ#499788]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-391: --------------------------------------- Summary: Enable JSDT Outline view in Neon [EBZ#499788] Key: ERT-391 URL: https://issues.jboss.org/browse/ERT-391 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Fix For: Neon.1 (4.6) As reported in [#1], the Outline view showing the AST of a JavaScript source file is not working properly. Steps to reproduce: - unzip and start eclipse-javascript-neon-R - create a javascript project and paste the code at: http://pastebin.com/BqnJBy5C - observe the outline does not show the .js AST: http://imgur.com/HMUqjBi.png This issue is urgent as we have one last sprint before shipping Neon.1. [#1] http://stackoverflow.com/questions/38955947/enabling-the-jsdt-outline-vie... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-23015: -------------------------------- Description: When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) To reproduce: - git clone https://github.com/redhat-helloworld-msa/aloha - mvn package - build docker image from Dockerfile, to CDK docker connection - deploy docker image to openshift was: When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > Creating a route should have a default port > ------------------------------------------- > > Key: JBIDE-23015 > URL: https://issues.jboss.org/browse/JBIDE-23015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Fix For: 4.4.1.Final > > > When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. > There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. > The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > To reproduce: > - git clone https://github.com/redhat-helloworld-msa/aloha > - mvn package > - build docker image from Dockerfile, to CDK docker connection > - deploy docker image to openshift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-23015: ----------------------------------- Summary: Creating a route should have a default port Key: JBIDE-23015 URL: https://issues.jboss.org/browse/JBIDE-23015 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Fred Bricon Fix For: 4.4.1.Final When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-373) Node.js "Relaunch" support - not acting as expected [EBZ#498440]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-373?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-373: ---------------------------- Story Points: 15 > Node.js "Relaunch" support - not acting as expected [EBZ#498440] > ---------------------------------------------------------------- > > Key: ERT-373 > URL: https://issues.jboss.org/browse/ERT-373 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Labels: General, bzira > > When selecting a current running node process in the debug view. > There are a few options including "Relaunch", and also "Terminate and Relaunch" > Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-373) Node.js "Relaunch" support - not acting as expected [EBZ#498440]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-373?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-373: ------------------------------- Assignee: Ilya Buziuk > Node.js "Relaunch" support - not acting as expected [EBZ#498440] > ---------------------------------------------------------------- > > Key: ERT-373 > URL: https://issues.jboss.org/browse/ERT-373 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Labels: General, bzira > > When selecting a current running node process in the debug view. > There are a few options including "Relaunch", and also "Terminate and Relaunch" > Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-388) Grunt plugin doesn't see all tasks [EBZ#499729]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-388?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-388: ---------------------------- Story Points: 4 > Grunt plugin doesn't see all tasks [EBZ#499729] > ----------------------------------------------- > > Key: ERT-388 > URL: https://issues.jboss.org/browse/ERT-388 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: General, bzira > > -- Configuration Details -- > Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.jee.product) > Installed Features: > org.eclipse.jdt 3.12.0.v20160606-1100 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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