May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-195) Generification of IJavaCompletionProposalComputer has type of computeContextInformation wrong [EBZ#493810]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-195?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-195: ----------------------------------- Assignee: Victor Rubezhny > Generification of IJavaCompletionProposalComputer has type of computeContextInformation wrong [EBZ#493810] > ---------------------------------------------------------------------------------------------------------- > > Key: ERT-195 > URL: https://issues.jboss.org/browse/ERT-195 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC2, General, bzira > Fix For: Neon (4.6) RC2 > > > The return type of IJavaCompletionProposalComputer.computeContextInformation was recently changed from "List" to "List<ICompletionProposal>", it should have been "List<IContextInformation>". > At the moment all the implementations of IJavaCompletionProposalComputer.computeContextInformation in the code base have return type still as "List" with unchecked conversions. That is why there is no compile error within JSDT on its own. > Note that IJavaCompletionProposalComputer was originally copied from JDT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3898) Make sure eclipse JSON editor is included in devstudio

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3898?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3898: --------------------------------- Sprint: devex #115 May 2016 > Make sure eclipse JSON editor is included in devstudio > ------------------------------------------------------ > > Key: JBDS-3898 > URL: https://issues.jboss.org/browse/JBDS-3898 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.0.0.Alpha3 > > > We should make sure JSON Editor is included in devstudio and JBT target platforms/Market place/installation. > [~vrubezhny] please provide all needed information for [~nickboldt] regarding this plugin. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-195) Generification of IJavaCompletionProposalComputer has type of computeContextInformation wrong [EBZ#493810]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-195?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-195. --------------------------------- Resolution: Done > Generification of IJavaCompletionProposalComputer has type of computeContextInformation wrong [EBZ#493810] > ---------------------------------------------------------------------------------------------------------- > > Key: ERT-195 > URL: https://issues.jboss.org/browse/ERT-195 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC2, General, bzira > Fix For: Neon (4.6) RC2 > > > The return type of IJavaCompletionProposalComputer.computeContextInformation was recently changed from "List" to "List<ICompletionProposal>", it should have been "List<IContextInformation>". > At the moment all the implementations of IJavaCompletionProposalComputer.computeContextInformation in the code base have return type still as "List" with unchecked conversions. That is why there is no compile error within JSDT on its own. > Note that IJavaCompletionProposalComputer was originally copied from JDT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-198) Content assist displays only top level properties as proposals [EBZ#490639]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-198?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-198: ----------------------------------- Assignee: Victor Rubezhny > Content assist displays only top level properties as proposals [EBZ#490639] > --------------------------------------------------------------------------- > > Key: ERT-198 > URL: https://issues.jboss.org/browse/ERT-198 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC2, bzira, wst.json > Fix For: Neon (4.6) RC2 > > > When I invoke content assist on a JSON object, I expect to see the list of properties in the context of the selected object but I see a list of top level properties instead. > I think the problem is in the JSONSchemaNode.walk() method, where the 'json' object that gets passed in is always the schema root, so the properties always correspond to that object. > private static void walk(JsonObject json, JSONSchemaNode schemaNode) { > Member member = null; > JsonObject properties = (JsonObject) json.get("properties"); > if (properties != null) { > Iterator<Member> members = properties.iterator(); > while (members.hasNext()) { > member = members.next(); > schemaNode.addProperty(new JSONSchemaProperty(member.getName(), > (JsonObject) member.getValue(), schemaNode)); > } > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-198) Content assist displays only top level properties as proposals [EBZ#490639]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-198?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-198: ----------------------------------- Assignee: Snjezana Peco (was: Victor Rubezhny) > Content assist displays only top level properties as proposals [EBZ#490639] > --------------------------------------------------------------------------- > > Key: ERT-198 > URL: https://issues.jboss.org/browse/ERT-198 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: 3.8_RC2, bzira, wst.json > Fix For: Neon (4.6) RC2 > > > When I invoke content assist on a JSON object, I expect to see the list of properties in the context of the selected object but I see a list of top level properties instead. > I think the problem is in the JSONSchemaNode.walk() method, where the 'json' object that gets passed in is always the schema root, so the properties always correspond to that object. > private static void walk(JsonObject json, JSONSchemaNode schemaNode) { > Member member = null; > JsonObject properties = (JsonObject) json.get("properties"); > if (properties != null) { > Iterator<Member> members = properties.iterator(); > while (members.hasNext()) { > member = members.next(); > schemaNode.addProperty(new JSONSchemaProperty(member.getName(), > (JsonObject) member.getValue(), schemaNode)); > } > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-198) Content assist displays only top level properties as proposals [EBZ#490639]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-198?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-198. --------------------------------- Resolution: Done > Content assist displays only top level properties as proposals [EBZ#490639] > --------------------------------------------------------------------------- > > Key: ERT-198 > URL: https://issues.jboss.org/browse/ERT-198 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: 3.8_RC2, bzira, wst.json > Fix For: Neon (4.6) RC2 > > > When I invoke content assist on a JSON object, I expect to see the list of properties in the context of the selected object but I see a list of top level properties instead. > I think the problem is in the JSONSchemaNode.walk() method, where the 'json' object that gets passed in is always the schema root, so the properties always correspond to that object. > private static void walk(JsonObject json, JSONSchemaNode schemaNode) { > Member member = null; > JsonObject properties = (JsonObject) json.get("properties"); > if (properties != null) { > Iterator<Member> members = properties.iterator(); > while (members.hasNext()) { > member = members.next(); > schemaNode.addProperty(new JSONSchemaProperty(member.getName(), > (JsonObject) member.getValue(), schemaNode)); > } > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3910) Include EAP 7.0 in JBDS installer

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-3910?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-3910: ------------------------------- Description: Include EAP 7.0.0 in JBDS 9.1.0 installer. Once ready, add it to http://www.jboss.org/products/devstudio/download/ (was: Include EAP 7.0.0 in JBDS 9.1.0 installer.) > Include EAP 7.0 in JBDS installer > --------------------------------- > > Key: JBDS-3910 > URL: https://issues.jboss.org/browse/JBDS-3910 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Component Upgrade > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > > Include EAP 7.0.0 in JBDS 9.1.0 installer. Once ready, add it to http://www.jboss.org/products/devstudio/download/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3910) Include EAP 7.0 in JBDS installer

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-3910?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-3910: ------------------------------- Parent: (was: JBDS-3299) Issue Type: Component Upgrade (was: Component Upgrade Subtask) > Include EAP 7.0 in JBDS installer > --------------------------------- > > Key: JBDS-3910 > URL: https://issues.jboss.org/browse/JBDS-3910 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Component Upgrade > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > > Include EAP 7.0.0 in JBDS 9.1.0 installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21648. --------------------------------- Resolution: Done pushed better url to stacks > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Assignee: Rafael Benevides > Fix For: 4.3.2.Final, 4.4.0.Alpha2 > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21648: -------------------------------- Fix Version/s: 4.4.0.Alpha2 > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Assignee: Rafael Benevides > Fix For: 4.3.2.Final, 4.4.0.Alpha2 > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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