May 2016 - jbosstools-issues - Jboss List Archives

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

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-214: --------------------------------------- Summary: 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 Priority: Trivial 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, 10 months

1
0
0 / 0

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

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-215: --------------------------------------- Summary: 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 Priority: Trivial 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-171) [ES6] Define a way to enable module parsing [EBZ#492130]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-171?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-171. ------------------------------ Resolution: Done > [ES6] Define a way to enable module parsing [EBZ#492130] > -------------------------------------------------------- > > Key: ERT-171 > URL: https://issues.jboss.org/browse/ERT-171 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: General, bzira > > By default JSDT uses "script" source type parsing, which causes import/exports to be marked as erors. JSDT needs to define a way for projects to opt-int to use "module" parsing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-44) JSON Schema extension for JSON editor [EBZ#485701]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-44?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan resolved ERT-44. ----------------------------- Resolution: Done > JSON Schema extension for JSON editor [EBZ#485701] > -------------------------------------------------- > > Key: ERT-44 > URL: https://issues.jboss.org/browse/ERT-44 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Labels: bzira, wst.json > > JSON editor should have a generic extension for mapping JSON schemas to files.The extension should allow 3rd parties to contribute a JSON schema and get code assist, validation etc. through JSON editor without introducing a new editor type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22426) Connection: authorization strategy is always overwritten (in the client) upon #isConnected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22426?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22426: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1179, https://github.com/jbosstools/jbosstools-openshift/pull/1173, https://github.com/jbosstools/jbosstools-openshift/pull/1185 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1179, https://github.com/jbosstools/jbosstools-openshift/pull/1173) > Connection: authorization strategy is always overwritten (in the client) upon #isConnected > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22426 > URL: https://issues.jboss.org/browse/JBIDE-22426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > The current implementation of Connection#isConnected() will always overwrite the authorization strategy in the client that it is using. This seems wrong given that #getResources, #createResource, #updateResource (and other methods) also set it but check if it already exists beforehand. Making sure that they dont overwrite an existing strategy. > {code:title=Connection#isConnected} > public boolean isConnected(IProgressMonitor monitor) { > client.setAuthorizationStrategy(getAuthorizationStrategy()); > try { > {code} > {code:title=Connection#createResource} > public <T extends IResource> T createResource(T resource) { > try { > if(client.getAuthorizationStrategy() == null) { > client.setAuthorizationStrategy(getAuthorizationStrategy()); > } > return client.create(resource); > {code} > A very likely side-effect of this is in Connection#ownsResource which compares clients (the one in the connection and the one attached to the given resource. The 2 clients are compared with the authorization strategy: > {code:title=com.openshift.internal.restclient.DefaultClient#equals} > @Override > public boolean equals(Object obj) { > ... > return ObjectUtils.equals(strategy, other.strategy); > {code} > the lookup for a connection for a given resource in ConnectionRegistryUtils#safeGetConnectionFor will therefore fail after a Connection#isConnected: > {code:title=ConnectionsRegistryUtil#safeGetConnectionFor(IResource)} > public static Connection safeGetConnectionFor(IResource resource) { > Collection<Connection> all = ConnectionsRegistrySingleton.getInstance().getAll(Connection.class); > for (Connection connection : all) { > if(connection.ownsResource(resource)) { > return connection; > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22390) Forge New and Noteworthy for 4.4.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22390?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22390: ---------------------------------------- Ok, it explains why you were so quite ;) > Forge New and Noteworthy for 4.4.0.Alpha2 > ----------------------------------------- > > Key: JBIDE-22390 > URL: https://issues.jboss.org/browse/JBIDE-22390 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3739: -------------------------------------- [~rgrunber] could you please add a link to the bugzilla issue for that docker tooling bug? And please open an issue for vagrant-service-manager here - https://github.com/projectatomic/vagrant-service-manager It's very important that we don't quietly wait until the issue is fixed somehow. Report it upstream or ping CDK guys if not sure it's an upstream bug or not. There is a free node channel #nulecule where you can ask the ADB/CDK guys. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22426) Connection: authorization strategy is always overwritten (in the client) upon #isConnected

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22426?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22426: ----------------------------------------------- [~adietish], please consider https://github.com/jbosstools/jbosstools-openshift/pull/1185 - prevention of possible unwanted connect() in isConnected(). The hole was not a big one - for the very first access to the connection, but still it might make the start of Deploy image wizard from Docker explorer behave not as planned (separate Sign In dialog instead of Sign In page in the wizard). > Connection: authorization strategy is always overwritten (in the client) upon #isConnected > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22426 > URL: https://issues.jboss.org/browse/JBIDE-22426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > The current implementation of Connection#isConnected() will always overwrite the authorization strategy in the client that it is using. This seems wrong given that #getResources, #createResource, #updateResource (and other methods) also set it but check if it already exists beforehand. Making sure that they dont overwrite an existing strategy. > {code:title=Connection#isConnected} > public boolean isConnected(IProgressMonitor monitor) { > client.setAuthorizationStrategy(getAuthorizationStrategy()); > try { > {code} > {code:title=Connection#createResource} > public <T extends IResource> T createResource(T resource) { > try { > if(client.getAuthorizationStrategy() == null) { > client.setAuthorizationStrategy(getAuthorizationStrategy()); > } > return client.create(resource); > {code} > A very likely side-effect of this is in Connection#ownsResource which compares clients (the one in the connection and the one attached to the given resource. The 2 clients are compared with the authorization strategy: > {code:title=com.openshift.internal.restclient.DefaultClient#equals} > @Override > public boolean equals(Object obj) { > ... > return ObjectUtils.equals(strategy, other.strategy); > {code} > the lookup for a connection for a given resource in ConnectionRegistryUtils#safeGetConnectionFor will therefore fail after a Connection#isConnected: > {code:title=ConnectionsRegistryUtil#safeGetConnectionFor(IResource)} > public static Connection safeGetConnectionFor(IResource resource) { > Collection<Connection> all = ConnectionsRegistrySingleton.getInstance().getAll(Connection.class); > for (Connection connection : all) { > if(connection.ownsResource(resource)) { > return connection; > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3787: ----------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3787: -------------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- 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