July 2016 - jbosstools-issues - Jboss List Archives

[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: ----------------------------- Story Points: 2 (was: 10) > 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-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: ----------------------------- Story Points: 2 (was: 10) > 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

[JBoss JIRA] (JBIDE-22646) Starting cdk creates two processes in debug view

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22646?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22646: --------------------------------------- [~rob.stryker], can you clarify, please? What is the expected behavior? I can see just one process in debug view, but it's terminated once cdk is started ( = vagrant up finishes) and there is no other process in the debug view. > Starting cdk creates two processes in debug view > ------------------------------------------------ > > Key: JBIDE-22646 > URL: https://issues.jboss.org/browse/JBIDE-22646 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, server > Affects Versions: 4.4.1.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > Starting cdk creates two processes in debug view. > One does not disappear when the startup process is complete. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-816) Cannot install SwitchYard tooling from EA zip file in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-816?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-816: ----------------------------------------- Even this is not a critical issue I'm wondering whether there exists any tool for verifying the dependency tree for each zip file. > Cannot install SwitchYard tooling from EA zip file in offline mode > ------------------------------------------------------------------ > > Key: JBTIS-816 > URL: https://issues.jboss.org/browse/JBTIS-816 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.CR3 > Environment: JBDS 9.1.0.GA + devstudio-integration-stack-9.0.1.CR3-earlyaccess.zip > Reporter: Andrej Podhradsky > > Cannot install SwitchYard tooling from EA zip file in offline mode due to missing > * org.eclipse.zest.core 1.5.100 (required by fuse tooling) > * org.eclipse.emf.compare.feature.group 2.1.0 (required by switchayrd tooling) > * org.eclipse.bpel.feature.feature.group [1.0.2,2.0.0) (required by switchyard bpel tooling) > All features mentioned above are available in devstudio-integration-stack-9.0.1.CR3.zip. So, to install all features in offline mode we need both zip files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22634) fix buildflow jobs to correctly represent interdependencies of jbosstools-* projects

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22634?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22634. --------------------------------- I assume this works as expected. Let us know if it doesn't. > fix buildflow jobs to correctly represent interdependencies of jbosstools-* projects > ------------------------------------------------------------------------------------ > > Key: JBIDE-22634 > URL: https://issues.jboss.org/browse/JBIDE-22634 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM1 > > > Some jobs fail when upstream deps have not been published: > * aerogear depends browsersim > * browsersim depends jst > * vpe depends jst > * arquillian depends javaee > * central depends javaee > * javaee depends vpe > So need to retool the buildflow jobs (and the force-push ones too) to correctly align with these dep chains. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-816) Cannot install SwitchYard tooling from EA zip file in offline mode

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-816: --------------------------------------- Summary: Cannot install SwitchYard tooling from EA zip file in offline mode Key: JBTIS-816 URL: https://issues.jboss.org/browse/JBTIS-816 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.1.CR3 Environment: JBDS 9.1.0.GA + devstudio-integration-stack-9.0.1.CR3-earlyaccess.zip Reporter: Andrej Podhradsky Cannot install SwitchYard tooling from EA zip file in offline mode due to missing * org.eclipse.zest.core 1.5.100 (required by fuse tooling) * org.eclipse.emf.compare.feature.group 2.1.0 (required by switchayrd tooling) * org.eclipse.bpel.feature.feature.group [1.0.2,2.0.0) (required by switchyard bpel tooling) All features mentioned above are available in devstudio-integration-stack-9.0.1.CR3.zip. So, to install all features in offline mode we need both zip files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22695: --------------------------------------- [~adietish] I've checked how oc binary is doing it. It modify dc and create a new rc and make the old ones rcs with 0 replicas. So this workflow is correct I suppose. I checked OpenShift docs. There is an option to rollback with a deployment config. There is a revision number attribute for dc and it is possible to rollback with command "oc rollback <deployment_config> --to-version=<revision_number>". So this allow us to rollback. But I was not able to find out how to display content of older revisions so far via oc binary. Maybe REST API allows to do something like this, worth to check. > Environment Variables of application deployment should have different workflow > ------------------------------------------------------------------------------ > > Key: JBIDE-22695 > URL: https://issues.jboss.org/browse/JBIDE-22695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue: > Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest). > There are 2 options: > a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller). > b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-809?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-809: ------------------------------------ Labels: verified_jbdsis-9.0.1 (was: ) > Cannot install Fuse tooling from EA without GA > ---------------------------------------------- > > Key: JBTIS-809 > URL: https://issues.jboss.org/browse/JBTIS-809 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.GA > Environment: JBDS-IS 9.0.1.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Labels: verified_jbdsis-9.0.1 > Fix For: 9.0.1.CR3 > > > Cannot install Fuse tooling from EA without GA due to the following error > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found > {code} > the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-809?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-809. ----------------------------------- Verified with JBDS-IS 9.0.1.CR3 > Cannot install Fuse tooling from EA without GA > ---------------------------------------------- > > Key: JBTIS-809 > URL: https://issues.jboss.org/browse/JBTIS-809 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.GA > Environment: JBDS-IS 9.0.1.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Labels: verified_jbdsis-9.0.1 > Fix For: 9.0.1.CR3 > > > Cannot install Fuse tooling from EA without GA due to the following error > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found > {code} > the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22648. --------------------------------- I think what I saw is expected. Let me know if you feel otherwise. Verified in jbt 4.4.1.AM2. Closing. > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- 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