August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-214) Validate JSON file with JSON Schema [EBZ#494111]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-214: ------------------------------ Story Points: 25 (was: 10) > Validate JSON file with JSON Schema [EBZ#494111] > ------------------------------------------------ > > Key: ERT-214 > URL: https://issues.jboss.org/browse/ERT-214 > 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) > > > It's a very big task, but it should be fantastic if WTP Validator could validate JSON file by using JSON Schema. > To do that: > * JSONSchemaDocument should support the full specification of JSON Schema. > * minimal-json should be improved to collect line, column or perhaps we could use IJSONDocument to validate it with JSON Schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-385) [content assist] Don't show existing JSON keys in popup completion [EBZ#499538]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-385?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-385: ------------------------------ Story Points: 2 > [content assist] Don't show existing JSON keys in popup completion [EBZ#499538] > ------------------------------------------------------------------------------- > > Key: ERT-385 > URL: https://issues.jboss.org/browse/ERT-385 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > > Takes a sample: > -------------------------------- > { > "compileOnSave": true, > "compil // Ctrl+Space > } > -------------------------------- > The popup completion should show only "compilerOptions" and not "compileOnSave". Today the popup shows "compilerOnSave" and "compilerOptions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-384) [content assist] Generate comma if need when completion is applied [EBZ#499537]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-384?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-384: ------------------------------ Story Points: 2 > [content assist] Generate comma if need when completion is applied [EBZ#499537] > ------------------------------------------------------------------------------- > > Key: ERT-384 > URL: https://issues.jboss.org/browse/ERT-384 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > > Take a sample: > -------------------------------- > { > "compiler // Ctrl+Space > } > -------------------------------- > The completion apply generates (like today) this content: > -------------------------------- > { > "compilerOptions": {} > } > -------------------------------- > But in the case if user triggers the completion before a JSON key > -------------------------------- > { > "compiler // Ctrl+Space > "compileOnSave": true > } > -------------------------------- > a comma should be generated: > -------------------------------- > { > "compilerOptions": {}, > "compileOnSave": true > } > -------------------------------- -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-385) [content assist] Don't show existing JSON keys in popup completion [EBZ#499538]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-385?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-385: ------------------------------ Sprint: devex #118 July 2016 > [content assist] Don't show existing JSON keys in popup completion [EBZ#499538] > ------------------------------------------------------------------------------- > > Key: ERT-385 > URL: https://issues.jboss.org/browse/ERT-385 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > > Takes a sample: > -------------------------------- > { > "compileOnSave": true, > "compil // Ctrl+Space > } > -------------------------------- > The popup completion should show only "compilerOptions" and not "compileOnSave". Today the popup shows "compilerOnSave" and "compilerOptions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-385) [content assist] Don't show existing JSON keys in popup completion [EBZ#499538]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-385?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-385: ------------------------------ Sprint: (was: devex #119 August 2016) > [content assist] Don't show existing JSON keys in popup completion [EBZ#499538] > ------------------------------------------------------------------------------- > > Key: ERT-385 > URL: https://issues.jboss.org/browse/ERT-385 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > > Takes a sample: > -------------------------------- > { > "compileOnSave": true, > "compil // Ctrl+Space > } > -------------------------------- > The popup completion should show only "compilerOptions" and not "compileOnSave". Today the popup shows "compilerOnSave" and "compilerOptions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-384) [content assist] Generate comma if need when completion is applied [EBZ#499537]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-384?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-384: ------------------------------ Sprint: devex #118 July 2016 > [content assist] Generate comma if need when completion is applied [EBZ#499537] > ------------------------------------------------------------------------------- > > Key: ERT-384 > URL: https://issues.jboss.org/browse/ERT-384 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > > Take a sample: > -------------------------------- > { > "compiler // Ctrl+Space > } > -------------------------------- > The completion apply generates (like today) this content: > -------------------------------- > { > "compilerOptions": {} > } > -------------------------------- > But in the case if user triggers the completion before a JSON key > -------------------------------- > { > "compiler // Ctrl+Space > "compileOnSave": true > } > -------------------------------- > a comma should be generated: > -------------------------------- > { > "compilerOptions": {}, > "compileOnSave": true > } > -------------------------------- -- 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 Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-23015: --------------------------------------- There was another issue logged where we explained service behavior. If I recall, you can only configure a service to either a) point to a specific port, or b)round robin the ports. > 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] (ERT-385) [content assist] Don't show existing JSON keys in popup completion [EBZ#499538]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-385?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco updated ERT-385: ------------------------------ Sprint: devex #119 August 2016 > [content assist] Don't show existing JSON keys in popup completion [EBZ#499538] > ------------------------------------------------------------------------------- > > Key: ERT-385 > URL: https://issues.jboss.org/browse/ERT-385 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > > Takes a sample: > -------------------------------- > { > "compileOnSave": true, > "compil // Ctrl+Space > } > -------------------------------- > The popup completion should show only "compilerOptions" and not "compileOnSave". Today the popup shows "compilerOnSave" and "compilerOptions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-385) [content assist] Don't show existing JSON keys in popup completion [EBZ#499538]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-385?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco reassigned ERT-385: --------------------------------- Assignee: Snjezana Peco > [content assist] Don't show existing JSON keys in popup completion [EBZ#499538] > ------------------------------------------------------------------------------- > > Key: ERT-385 > URL: https://issues.jboss.org/browse/ERT-385 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > > Takes a sample: > -------------------------------- > { > "compileOnSave": true, > "compil // Ctrl+Space > } > -------------------------------- > The popup completion should show only "compilerOptions" and not "compileOnSave". Today the popup shows "compilerOnSave" and "compilerOptions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-384) [content assist] Generate comma if need when completion is applied [EBZ#499537]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/ERT-384?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco reassigned ERT-384: --------------------------------- Assignee: Snjezana Peco > [content assist] Generate comma if need when completion is applied [EBZ#499537] > ------------------------------------------------------------------------------- > > Key: ERT-384 > URL: https://issues.jboss.org/browse/ERT-384 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > > Take a sample: > -------------------------------- > { > "compiler // Ctrl+Space > } > -------------------------------- > The completion apply generates (like today) this content: > -------------------------------- > { > "compilerOptions": {} > } > -------------------------------- > But in the case if user triggers the completion before a JSON key > -------------------------------- > { > "compiler // Ctrl+Space > "compileOnSave": true > } > -------------------------------- > a comma should be generated: > -------------------------------- > { > "compilerOptions": {}, > "compileOnSave": true > } > -------------------------------- -- 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