February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23783: ------------------------------- Sprint: devex #128 February 2017 > Server adapter editor: Project settings composite is badly layouted > ------------------------------------------------------------------- > > Key: JBIDE-23783 > URL: https://issues.jboss.org/browse/JBIDE-23783 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.4.AM1 > > Attachments: adapter.png, corrected-project-settings-composite.png, project-settings-composite.png, resized-project-settings-composite.png > > > steps to reproduce: > # ASSERT: make sure that you have a server adapter defined > # EXEC: open up the editor for your server adapter > Result: > The project settings composite is badly layouted, especially the right border boundaries are not even: > !project-settings-composite.png! > # EXEC: maximise the editor > Result: > The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes. > !resized-project-settings-composite.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20108: ------------------------------- Sprint: devex #123 November 2016, devex #128 February 2017 (was: devex #123 November 2016) > Cannot connect to remote server in JMX Navigator - Authentication fails > ----------------------------------------------------------------------- > > Key: JBIDE-20108 > URL: https://issues.jboss.org/browse/JBIDE-20108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.4.AM1 > > > When I try to connect to a remote server via JMX Navigator, it fails on authentication: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854 > !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > ... 7 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854 > !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > !STACK 0 > javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work. > Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21065: ------------------------------- Sprint: devex #123 November 2016, devex #128 February 2017 (was: devex #123 November 2016) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.4.AM1 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23905) Wrong layout in cdk3 server editor

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23905?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23905: ------------------------------- Sprint: devex #128 February 2017 > Wrong layout in cdk3 server editor > ---------------------------------- > > Key: JBIDE-23905 > URL: https://issues.jboss.org/browse/JBIDE-23905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, server_adapter, server_adapter_editor > Fix For: 4.4.4.AM1 > > Attachments: screenshot-1.png > > > The cdk v3 server editor shows a wrong layout (at least on Windows) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23961: ------------------------------- Sprint: devex #128 February 2017 > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23833) Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23833?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23833: ------------------------------------ Can the user still install the JIRA connector (from Central) ? Because removing it because of an error message seems silly to me. So +1 if user has no way to install the connector > Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira' > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23833 > URL: https://issues.jboss.org/browse/JBIDE-23833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, common > Affects Versions: 4.4.3.AM2 > Reporter: Mat Booth > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > > Doing a smoke test for the release of 4.4.3.AM2 when I saw this error: > {noformat} > !ENTRY org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127 > !MESSAGE Unexpected error while loading repository template extensions > !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127 > !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira' > {noformat} > I saw this in the log after performing the following: > 0. Downloaded Neon.2 (I happened to choose the C/C++ distribution) > 1. Install Abridged category from http://download.jboss.org/jbosstools/neon/development/updates/ > 2. Open Central Software/Updates tab, enable Early Access select and install everything -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 #128 February 2017 (was: devex #118 July 2016, devex #127 February 2017) > 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: Victor Rubezhny > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-389: ---------------------------- Sprint: devex #128 February 2017 (was: devex #127 February 2017) > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-481) Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-481?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-481: ----------------------------------- Assignee: Pavol Srna > Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025] > --------------------------------------------------------------------------------- > > Key: ERT-481 > URL: https://issues.jboss.org/browse/ERT-481 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Pavol Srna > Labels: General, bzira > Fix For: Oxygen (4.7) > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-481) Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-481?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-481. --------------------------------- Fix Version/s: Oxygen (4.7) Resolution: Done > Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025] > --------------------------------------------------------------------------------- > > Key: ERT-481 > URL: https://issues.jboss.org/browse/ERT-481 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > Fix For: Oxygen (4.7) > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017