July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22628) Zoom in / out functionality is not working with Visual Page Editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22628?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22628: ----------------------------------- Fix Version/s: (was: 4.4.x) > Zoom in / out functionality is not working with Visual Page Editor > -------------------------------------------------------------------- > > Key: JBIDE-22628 > URL: https://issues.jboss.org/browse/JBIDE-22628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core > Affects Versions: 4.4.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.2.AM1 > > > New zoom in / out functionality (Cntl + / -) which is available in Neon is not working in Visual Page Editor. The interesting thing, that if you do Zoom in / out in the html editor which supports this functionality and reopen file again in the Visual Editor the new scale will be adjusted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22628) Zoom in / out functionality is not working with Visual Page Editor

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22628?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22628: ---------------------------------------- In best case, this will be fixed when we move to Neon.1. [~nickboldt] what fix version should we set then? > Zoom in / out functionality is not working with Visual Page Editor > -------------------------------------------------------------------- > > Key: JBIDE-22628 > URL: https://issues.jboss.org/browse/JBIDE-22628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.2.AM1, 4.4.x > > > New zoom in / out functionality (Cntl + / -) which is available in Neon is not working in Visual Page Editor. The interesting thing, that if you do Zoom in / out in the html editor which supports this functionality and reopen file again in the Visual Editor the new scale will be adjusted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22628) Zoom in / out functionality is not working with Visual Page Editor

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22628?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22628: ----------------------------------- Component/s: upstream > Zoom in / out functionality is not working with Visual Page Editor > -------------------------------------------------------------------- > > Key: JBIDE-22628 > URL: https://issues.jboss.org/browse/JBIDE-22628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core > Affects Versions: 4.4.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.2.AM1, 4.4.x > > > New zoom in / out functionality (Cntl + / -) which is available in Neon is not working in Visual Page Editor. The interesting thing, that if you do Zoom in / out in the html editor which supports this functionality and reopen file again in the Visual Editor the new scale will be adjusted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-49) Launch Configuration for Browser based applications [EBZ#486066]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-49?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-49: ---------------------------- Sprint: devex #117 July 2016 > Launch Configuration for Browser based applications [EBZ#486066] > ---------------------------------------------------------------- > > Key: ERT-49 > URL: https://issues.jboss.org/browse/ERT-49 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19081: ------------------------------------- PR applied on jbosstools-base, enabling 40 new tests: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21580) TernError: No type found at the given position when invoking Open On for taglib definition

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21580?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-21580: --------------------------------- Sprint: devex #117 July 2016 > TernError: No type found at the given position when invoking Open On for taglib definition > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21580 > URL: https://issues.jboss.org/browse/JBIDE-21580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160122-0528-B256 + Mobile Tooling + AngularJS > Oracle Java 1.8 > Fedora 22 64 bit > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.x > > > 1. Create JSF 1.2 project > 2. Open inputUserName.jsp in VPE > 3. Hover over <%@ taglib uri="http://java.sun.com/jsf/core" > 4. Press Ctrl > ERROR: > {noformat} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21580) TernError: No type found at the given position when invoking Open On for taglib definition

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21580?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-21580: --------------------------------- Story Points: 5 > TernError: No type found at the given position when invoking Open On for taglib definition > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21580 > URL: https://issues.jboss.org/browse/JBIDE-21580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160122-0528-B256 + Mobile Tooling + AngularJS > Oracle Java 1.8 > Fedora 22 64 bit > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.x > > > 1. Create JSF 1.2 project > 2. Open inputUserName.jsp in VPE > 3. Hover over <%@ taglib uri="http://java.sun.com/jsf/core" > 4. Press Ctrl > ERROR: > {noformat} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-219) Node.js application children processes can not be killed from eclipse console [EBZ#494592]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-219?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-219: ----------------------------- Story Points: 20 > Node.js application children processes can not be killed from eclipse console [EBZ#494592] > ------------------------------------------------------------------------------------------ > > Key: ERT-219 > URL: https://issues.jboss.org/browse/ERT-219 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > When running a simple Node.js application like: > var child_process = require('child_process'); > child_process.exec('ping www.google.com -t', function (err, stdout, stderr){ > if (err) { > console.log("child processes failed with error code: " + > err.code); > } > console.log(stdout); > }); > If you terminate the running process the "ping www.google.com -t" child process is still running even when the parent process is already killed. > This happens with one or more children processes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-89) Spike for changes on JSDT Search

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-89?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-89: ------------------------------- Story Points: 25 (was: 15) Assignee: Angel Misevski > Spike for changes on JSDT Search > -------------------------------- > > Key: ERT-89 > URL: https://issues.jboss.org/browse/ERT-89 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Gorkem Ercan > Assignee: Angel Misevski > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out the action plan for search after the new parser -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-89) Spike for changes on JSDT Search

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-89?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-89: ---------------------------- Sprint: devex #4 March 2016, devex #113 April 2016, devex #117 July 2016 (was: devex #4 March 2016, devex #113 April 2016) > Spike for changes on JSDT Search > -------------------------------- > > Key: ERT-89 > URL: https://issues.jboss.org/browse/ERT-89 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Gorkem Ercan > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out the action plan for search after the new parser -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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