August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22884) test failure in org.jboss.tools.vpe.jsp.test

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22884?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22884: -------------------------------- Story Points: 2 > test failure in org.jboss.tools.vpe.jsp.test > -------------------------------------------- > > Key: JBIDE-22884 > URL: https://issues.jboss.org/browse/JBIDE-22884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Fix For: 4.4.1.AM3 > > Attachments: _view_.txt, _view_more.txt > > > {code} > 21:32:03 [INFO] org.jboss.tools.vpe.jsp.test ....................... FAILURE [ 01:00 h] > 21:32:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.25.0:test (default-test) on project org.jboss.tools.vpe.jsp.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3627: ------------------------------------- https://www.redhat.com/wapps/ugc/register.html does not help, I can create a user and then if I try to use it with res service it says: "Please, use a valid user name and password!". After I login to developers.redhat.com account and accept T&C's new account works just fine with jdf download manager links and no T&C's related problems. > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23009) Cannot connect to cdk 2.2 docker in Docker Explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23009?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-23009: ---------------------------------- Summary: Cannot connect to cdk 2.2 docker in Docker Explorer (was: Cannot connect to cdk docker in Docker Explorer) > Cannot connect to cdk 2.2 docker in Docker Explorer > --------------------------------------------------- > > Key: JBIDE-23009 > URL: https://issues.jboss.org/browse/JBIDE-23009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Critical > > When I start CDK 2.2, docker connection is correctly created, but it cannot connect. There is no error message anywhere. > If I try to create a connection manually, using details from "vagrant service-manager env", the ping fails and it doesn't work either. > Connection from CLI, on the other hand, to this docker daemon works fine - when I run the export commands: > {code} > export DOCKER_HOST=tcp://172.28.128.3:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.22 > {code} > and then try for example "docker ps" or "docker run hello-world". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-378) [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-378?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-378: ---------------------------- Story Points: 4 (was: 5) > [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579] > -------------------------------------------------------------------------------------- > > Key: ERT-378 > URL: https://issues.jboss.org/browse/ERT-378 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > 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-378) [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-378?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-378: ------------------------------- Assignee: Ilya Buziuk > [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579] > -------------------------------------------------------------------------------------- > > Key: ERT-378 > URL: https://issues.jboss.org/browse/ERT-378 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > 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-346) If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-346?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-346: ------------------------------- Assignee: Ilya Buziuk > If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703] > -------------------------------------------------------------------------------------------------- > > Key: ERT-346 > URL: https://issues.jboss.org/browse/ERT-346 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > > We use feature in node that we can put out modules in a “node_modules” in a parent folder and it will be properly found: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_fol... > Node is working properly but if I add a breakpoint in a source file inside “node_modules” the breakpoint does not get hit. > To reproduce the issue: > 1. Create a JavaScript project “test”. > 2. Add a file “test.js” to the project with content: > var m1 = require("m1"); > console.log("m1.myFunc = " + m1.myFunc(3)); > 3. Create a JavaScript project called “node_modules”. > 4. Add a folder “m1” to the project “node_modules”. > 5. Add a file “index.js” to the folder “m1” with content: > module.exports.myFunc = function( i) { > return i*i; > } > 6. Debug “test.js” as Node – it works. Node is finding property “index.js”. 7. Add a breakpoint to “index.js”. > 8. Debug “test.js” as Node – it runs, but the breakpoint does not suspend the target. > Is there workaround for this issues? > Most of our projects are relying on the “node_modules” being found in the parent folder. That is making most of our code hard to debug. > I tested this on Ubuntu 14.04. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-365) Need to implement hot swap / live edit support for front-end debugging [EBZ#497856]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-365?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-365: ------------------------------- Assignee: Ilya Buziuk > Need to implement hot swap / live edit support for front-end debugging [EBZ#497856] > ----------------------------------------------------------------------------------- > > Key: ERT-365 > URL: https://issues.jboss.org/browse/ERT-365 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ilya Buziuk > 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-388) Grunt plugin doesn't see all tasks [EBZ#499729]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-388?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-388: ---------------------------- Priority: Major (was: Trivial) > Grunt plugin doesn't see all tasks [EBZ#499729] > ----------------------------------------------- > > Key: ERT-388 > URL: https://issues.jboss.org/browse/ERT-388 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: General, bzira > > -- Configuration Details -- > Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.jee.product) > Installed Features: > org.eclipse.jdt 3.12.0.v20160606-1100 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-388) Grunt plugin doesn't see all tasks [EBZ#499729]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-388?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-388: ------------------------------- Assignee: Ilya Buziuk > Grunt plugin doesn't see all tasks [EBZ#499729] > ----------------------------------------------- > > Key: ERT-388 > URL: https://issues.jboss.org/browse/ERT-388 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Priority: Trivial > Labels: General, bzira > > -- Configuration Details -- > Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.jee.product) > Installed Features: > org.eclipse.jdt 3.12.0.v20160606-1100 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-360) Need to create launch shortcut for opening html files in chrome / chromium browser with debug port enabled [EBZ#497853]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-360?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-360. ----------------------------- Resolution: Done > Need to create launch shortcut for opening html files in chrome / chromium browser with debug port enabled [EBZ#497853] > ----------------------------------------------------------------------------------------------------------------------- > > Key: ERT-360 > URL: https://issues.jboss.org/browse/ERT-360 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > > In order to support front-end debugging via file protocol, need to create launch shortcut for opening html files in chrome / chromium browser with debug port enabled (--remote-debugging-port=9222) -- 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