July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-179) StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-179?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-179: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145] > ----------------------------------------------------------------------------- > > Key: ERT-179 > URL: https://issues.jboss.org/browse/ERT-179 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Critical > Labels: bzira, wst.sse > > I have a custom IDocumentProvider that is used to get events from the text editor framework (document loaded, modified, closed). > The StructuredTextEditor does not call all methods on my implementation because it uses its own internal document provider. I think this would be great to support that -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22619. --------------------------------- > Decide strategy for fixversion targets in JIRA > ---------------------------------------------- > > Key: JBIDE-22619 > URL: https://issues.jboss.org/browse/JBIDE-22619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM1 > > > We need to decide the strategy for milestones / fixversions in JIRA. > One suggestion has been to align fixversions w/ sprint numbers, thus: > * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...? > instead of > * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ? > Questions/concerns: > * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies? > * whatever schema we adopt has to work with bzira and jiralint > * any other systems that parse JIRA for integration purposes? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22225: --------------------------------- Story Points: 5 (was: 15) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.x > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22225: --------------------------------- Sprint: devex #118 July 2016 (was: devex #117 July 2016) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.x > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-215?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-215: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-329) Use Closure compiler [EBZ#497249]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-329?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-329: ----------------------------- Sprint: devex #118 July 2016 (was: devex #117 July 2016) > Use Closure compiler [EBZ#497249] > --------------------------------- > > Key: ERT-329 > URL: https://issues.jboss.org/browse/ERT-329 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Labels: 3.9, General, bzira > Fix For: Oxygen (4.7) > > > Take closure compiler into use instead of the Esprima Parser to creates ASTs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-212?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-212: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > 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, 8 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-213?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-213: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > 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, 8 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-214: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-211) JSON Hover should use JSON Schema description [EBZ#494046]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-211?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-211: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > JSON Hover should use JSON Schema description [EBZ#494046] > ---------------------------------------------------------- > > Key: ERT-211 > URL: https://issues.jboss.org/browse/ERT-211 > 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) > > > Takes a sample with package.json: > ---------------------- > { > "name": "..." > } > ---------------------- > When "name" is hovered, it should show "The name of the package." which comes from the JSON Schema http://json.schemastore.org/package (properties/name/description) > This feature will be possible once https://bugs.eclipse.org/bugs/show_bug.cgi?id=490639 will be fixed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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