July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-369) Node.js "Relaunch" support - not acting as expected [EBZ#498440]

by Nick Boldt (JIRA)

Nick Boldt created ERT-369: ------------------------------ Summary: Node.js "Relaunch" support - not acting as expected [EBZ#498440] Key: ERT-369 URL: https://issues.jboss.org/browse/ERT-369 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt When selecting a current running node process in the debug view. There are a few options including "Relaunch", and also "Terminate and Relaunch" Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-368) Node.js "Relaunch" support - not acting as expected [EBZ#498440]

by Nick Boldt (JIRA)

Nick Boldt created ERT-368: ------------------------------ Summary: Node.js "Relaunch" support - not acting as expected [EBZ#498440] Key: ERT-368 URL: https://issues.jboss.org/browse/ERT-368 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt When selecting a current running node process in the debug view. There are a few options including "Relaunch", and also "Terminate and Relaunch" Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-367) Node.js "Relaunch" support - not acting as expected [EBZ#498440]

by Nick Boldt (JIRA)

Nick Boldt created ERT-367: ------------------------------ Summary: Node.js "Relaunch" support - not acting as expected [EBZ#498440] Key: ERT-367 URL: https://issues.jboss.org/browse/ERT-367 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt When selecting a current running node process in the debug view. There are a few options including "Relaunch", and also "Terminate and Relaunch" Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-363) Need to enable Chrome / chromium launch shortcut on server adapters [EBZ#497854]

by Nick Boldt (JIRA)

Nick Boldt created ERT-363: ------------------------------ Summary: Need to enable Chrome / chromium launch shortcut on server adapters [EBZ#497854] Key: ERT-363 URL: https://issues.jboss.org/browse/ERT-363 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt shortcut implemented as part of Bug 497853 should be available on Server Adapters in order to support debugging javascript debugging for apps running on tomcat / jboss -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-364) Need to automate source lookup detection for front-end debugging [EBZ#497855]

by Nick Boldt (JIRA)

Nick Boldt created ERT-364: ------------------------------ Summary: Need to automate source lookup detection for front-end debugging [EBZ#497855] Key: ERT-364 URL: https://issues.jboss.org/browse/ERT-364 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt For now source lookup for front-end debugging via Web Inspector Protocol (WIP) can be only manually set. Need to implement automatic source lookup detection that will support both file & http protocols. This will allow to debug javascript from JSDT editor OOTB -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-366) Error shows when running a "deleted" image [EBZ#497912]

by Nick Boldt (JIRA)

Nick Boldt created ERT-366: ------------------------------ Summary: Error shows when running a "deleted" image [EBZ#497912] Key: ERT-366 URL: https://issues.jboss.org/browse/ERT-366 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Nick Boldt Priority: Minor When I have two connections in Explorer View to the same Docker instance, it shown error when I try to run image deleted in other connection. Steps to reproduce: 1. Have two connections to the same instance of Docker: one with TCP, one with Linux socket. 2. Delete image from socket connection. 3. Image is still showing in TCP connection. 4. When I click on run on "deleted" image an error is shown in error log, but the Wizard for running an image is shown. Error description from error log: Failed to inspect container 'sha256:6b362a9f73eb8c33b48c95f4fcce1b6637fc25646728cf7fb0679b2da273c3f4' Stacktrace: com.spotify.docker.client.ImageNotFoundException: Image not found: sha256:6b362a9f73eb8c33b48c95f4fcce1b6637fc25646728cf7fb0679b2da273c3f4 at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:949) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:777) at org.eclipse.linuxtools.internal.docker.ui.jobs.FindImageInfoRunnable.run(FindImageInfoRunnable.java:24) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) Caused by: com.spotify.docker.client.DockerRequestException: Request error: GET unix://localhost:80/images/sha256:6b362a9f73eb8c33b48c95f4fcce1b6637fc25646728cf7fb0679b2da273c3f4/json: 404 at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1306) at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1255) at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:945) ... 3 more Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:956) at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:795) at org.glassfish.jersey.client.JerseyInvocation.access$500(JerseyInvocation.java:91) at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:756) at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:189) at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:74) at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:171) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320) at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 5. When I click on Run, an error dialog is shown: Image not found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created ERT-365: ------------------------------ Summary: 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 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-22283: ----------------------------------- I have fixed the issue in the hibernate tools runtime (versions 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3) and included these runtimes in the respective JBoss Tools plugins. I did not incorporate fancy heuristics like getting the first possible non-clashing available name as suggested above by [~dlmiles] as that would need a big refactoring (the properties and accessor methods are generated in different templates, do a lot more bookkeeping would be needed). I also don't think that there is a good use case of having multiple columns mapping to properties with the same name. I used the simple heuristic of adding an underscore after the name just like the default reveng strategy does with table and column names that are reserved words. If something more sophisticated is really needed, please open a different issue. > reveng *.java emitter does not escape java keyword 'return' as variable name > ---------------------------------------------------------------------------- > > Key: JBIDE-22283 > URL: https://issues.jboss.org/browse/JBIDE-22283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.x > Environment: Eclipse Mars > Reporter: Darryl Miles > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > > reveng *.java emitter does not escape java keyword 'return' as variable name > <table name="oc_return_history"> > <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return"> > <column-ref local-column="return_id" foreign-column="return_id"/> >  > <many-to-one property="return"/> > </foreign-key> > </table> > The expected output would be: > private Return _return; > but actual output is: > private Return return; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22283. ------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) Resolution: Done > reveng *.java emitter does not escape java keyword 'return' as variable name > ---------------------------------------------------------------------------- > > Key: JBIDE-22283 > URL: https://issues.jboss.org/browse/JBIDE-22283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.x > Environment: Eclipse Mars > Reporter: Darryl Miles > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > > reveng *.java emitter does not escape java keyword 'return' as variable name > <table name="oc_return_history"> > <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return"> > <column-ref local-column="return_id" foreign-column="return_id"/> >  > <many-to-one property="return"/> > </foreign-key> > </table> > The expected output would be: > private Return _return; > but actual output is: > private Return return; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22849) Update Hibernate Tools dependencies to 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22849?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22849. ------------------------------- Resolution: Done > Update Hibernate Tools dependencies to 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22849 > URL: https://issues.jboss.org/browse/JBIDE-22849 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > -- 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