August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-390) [content assist] js editor does not know DOM objects [EBZ#497903]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-390?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-390: ---------------------------- Sprint: devex #119 August 2016 > [content assist] js editor does not know DOM objects [EBZ#497903] > ----------------------------------------------------------------- > > Key: ERT-390 > URL: https://issues.jboss.org/browse/ERT-390 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Steps to reproduce. > 1. Download neon js package > 2. Run and start a fresh workspace > 3. Start a new js project > 4. create a js file > 5. edit the file and try content assist. > Only language features are available in the content assist. Basic DOM objects like window and document are missing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting

by Brian Exelbierd (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ] Brian Exelbierd commented on JBIDE-23010: ----------------------------------------- So doing some very basic research, this appears to be a manifestation of the same issues that were present in vagrant-sshfs. In both of these plugins cases, I am not sure that blocking on these streams closing is a good idea. The return code of vagrant, I believe, will tell you if the box started. If these plugins later run into trouble and need to make an error report, DevStudio should be able to react to that. As it is now, our fix consists of basically shunting error logging off to the side and never telling DevStudio about problems if they arise. We can probably get this fixed in landrush without too much trouble, however, we may eventually need a plugin that is not so keen on this patch. Is this something we can resolve on the DevStudio side? > landrush plugin prevents CDK server adapter from starting > --------------------------------------------------------- > > Key: JBIDE-23010 > URL: https://issues.jboss.org/browse/JBIDE-23010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > > Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.) > Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...". > This is the console output: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: [landrush] virtualbox requires an additional private network; adding it > ==> default: [landrush] starting dns server > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Registering box with vagrant-registration... > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Setting hostname... > ==> default: Configuring and enabling network interfaces... > [landrush] Using eth1 (172.28.128.3) > ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3 > ==> default: [landrush] adding static DNS entry: cdk => cdk.vm > [landrush] Using eth1 (172.28.128.3) > [landrush] Host DNS resolver config looks good. > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Mounting SSHFS shared folder... > ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp > ==> default: Checking Mount.. > ==> default: Checking Mount.. > ==> default: Folder Successfully Mounted! > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} > These are my plugins: > {code} > $ vagrant plugin list > landrush (1.1.1) > - Version Constraint: 1.1.1 > vagrant-registration (1.2.3) > - Version Constraint: 1.2.3 > vagrant-service-manager (1.3.0) > - Version Constraint: 1.3.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.2.0) > - Version Constraint: 1.2.0 > {code} > [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-214: ---------------------------- Story Points: 4 (was: 25) > 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-214) Validate JSON file with JSON Schema [EBZ#494111]

by Ilya Buziuk (JIRA)

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

1
0
0 / 0

[JBoss JIRA] (ERT-51) JavaScript Debugger integration tests for node.js [EBZ#486075]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-51?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk updated ERT-51: --------------------------- Story Points: 25 (was: 20) > JavaScript Debugger integration tests for node.js [EBZ#486075] > -------------------------------------------------------------- > > Key: ERT-51 > URL: https://issues.jboss.org/browse/ERT-51 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Pavol Srna > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-51) JavaScript Debugger integration tests for node.js [EBZ#486075]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-51?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk updated ERT-51: --------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016) > JavaScript Debugger integration tests for node.js [EBZ#486075] > -------------------------------------------------------------- > > Key: ERT-51 > URL: https://issues.jboss.org/browse/ERT-51 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Pavol Srna > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22225: -------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 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, 7 months

1
0
0 / 0

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

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-329?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-329: ---------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-110) CA shows property names in dependency proposals for bower/npm [EBZ#488100]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-110?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-110: ---------------------------- Story Points: 25 (was: 5) > CA shows property names in dependency proposals for bower/npm [EBZ#488100] > -------------------------------------------------------------------------- > > Key: ERT-110 > URL: https://issues.jboss.org/browse/ERT-110 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > There shouldn't be any of property proposals shown when a user invokes content assistant for dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-833) Extend transformers tests by the new attribute in JAXB transformer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-833?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-833: ------------------------------------ Attachment: switchyard-example.zip > Extend transformers tests by the new attribute in JAXB transformer > ------------------------------------------------------------------ > > Key: JBTIS-833 > URL: https://issues.jboss.org/browse/JBTIS-833 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Attachments: switchyard-example.zip > > > See SWITCHYARD-2923 -- 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