July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22764) OpenShift 3 doesn't compile with latest changes in Docker tooling

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22764?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22764: ----------------------------------- Assignee: Fred Bricon > OpenShift 3 doesn't compile with latest changes in Docker tooling > ------------------------------------------------------------------ > > Key: JBIDE-22764 > URL: https://issues.jboss.org/browse/JBIDE-22764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > Some temporary hack (https://github.com/jbosstools/jbosstools-openshift/commit/189fd3dfc006086...) no longer compiles against the latest docker tooling (in master) code: > {code:java} > // FIXME: needs to catch DockerCertificateException until > // https://bugs.eclipse.org/bugs/show_bug.cgi?id=495249 is fixed > catch (DockerException | InterruptedException | DockerCertificateException e) { > return new Status(IStatus.ERROR, OpenShiftUIActivator.PLUGIN_ID, > "Failed to push the selected Docker image into OpenShift registry", e); > } > {code} > com.spotify.docker.client.DockerCertificateException is no longer thrown by the Docker API so the catch block fails to compile. > We can fix the compilation problem with Neon.1 while still maintaining Neon.0 compatibility with a different, yet fugly, trick. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22764) OpenShift 3 doesn't compile with latest changes in Docker tooling

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22764: ----------------------------------- Summary: OpenShift 3 doesn't compile with latest changes in Docker tooling Key: JBIDE-22764 URL: https://issues.jboss.org/browse/JBIDE-22764 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM1 Reporter: Fred Bricon Some temporary hack (https://github.com/jbosstools/jbosstools-openshift/commit/189fd3dfc006086...) no longer compiles against the latest docker tooling (in master) code: {code:java} // FIXME: needs to catch DockerCertificateException until // https://bugs.eclipse.org/bugs/show_bug.cgi?id=495249 is fixed catch (DockerException | InterruptedException | DockerCertificateException e) { return new Status(IStatus.ERROR, OpenShiftUIActivator.PLUGIN_ID, "Failed to push the selected Docker image into OpenShift registry", e); } {code} com.spotify.docker.client.DockerCertificateException is no longer thrown by the Docker API so the catch block fails to compile. We can fix the compilation problem with Neon.1 while still maintaining Neon.0 compatibility with a different, yet fugly, trick. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9442) Investigate possibility for remote debug launch of app servers

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9442. -------------------------------- It still seems to work properly for me. The server started fine in debug mode and the process contained "-debug" in the arguments. Verified in devstudio 10.0.1.AM2 B5663 > Investigate possibility for remote debug launch of app servers > -------------------------------------------------------------- > > Key: JBIDE-9442 > URL: https://issues.jboss.org/browse/JBIDE-9442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.1.AM1 > > > When launching a remote server on a remote host, we do not currently connect a remote debugger. It'd be nice if we also connected a remote debugger if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22629) bzira missing mapping for linux tools 5.1.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22629?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22629. --------------------------------- Closing. I just checked Nick's examples and they look fine. > bzira missing mapping for linux tools 5.1. > ------------------------------------------ > > Key: JBIDE-22629 > URL: https://issues.jboss.org/browse/JBIDE-22629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.4.1.AM1 > > > bzira/jiralint is failing on missing version mapping for linux tools 5.1.0 - what release train is 5.1.0 targetd for ? Neon.1 ? > Related log from build fail mails: > {code} > [ERROR] Unknown version for Linux Tools / 5.1.0 > [ERROR] No mapping for '5.1.0'. Please fix the mapping. Bug: #496333 ASSIGNED - jjohnstn(a)redhat.com - Run Image Launch Configuration doesn't preserve command quotes > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22763) [regression] deploying an docker image doesn't select proper project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22763?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22763: ------------------------------------- Fix Version/s: 4.4.1.AM2 > [regression] deploying an docker image doesn't select proper project > -------------------------------------------------------------------- > > Key: JBIDE-22763 > URL: https://issues.jboss.org/browse/JBIDE-22763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Fix For: 4.4.1.AM2 > > > There's a regression in the Deploy Docker image wizard, where, when you have multiple projects, the selected project in OS explorer is ignored in the wizard. > This works fine in devstudio 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22763) [regression] deploying an docker image doesn't select proper project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22763?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22763: ---------------------------------------- Assignee: Andre Dietisheim > [regression] deploying an docker image doesn't select proper project > -------------------------------------------------------------------- > > Key: JBIDE-22763 > URL: https://issues.jboss.org/browse/JBIDE-22763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.1.AM2 > > > There's a regression in the Deploy Docker image wizard, where, when you have multiple projects, the selected project in OS explorer is ignored in the wizard. > This works fine in devstudio 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22517) Feature org.jboss.tools.wtp.server.launchbar.feature has wrong name in .project file

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22517?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22517. --------------------------------- Verified in git. > Feature org.jboss.tools.wtp.server.launchbar.feature has wrong name in .project file > ------------------------------------------------------------------------------------ > > Key: JBIDE-22517 > URL: https://issues.jboss.org/browse/JBIDE-22517 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > Feature org.jboss.tools.wtp.server.launchbar.feature has wrong name in .project file and needs to be fixed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22761) Connection to local EAP 7 via jmx fails

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22761?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-22761: ------------------------------------ {noformat:title=Error connecting to jmx for server jboss-eap-7.0} org.jboss.tools.jmx.core.JMXException: There was an error connecting to jboss-eap-7.0 via JMX. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com launch arguments at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:98) 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.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:288) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:269) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:367) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:239) at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:158) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:105) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) ... 6 more{noformat} Clean workspace don't help. Fedora 24 OpenJDK 1.8.0_92 Devstudio 10.0.1.AM2-v20160715-2233-B5663 > Connection to local EAP 7 via jmx fails > --------------------------------------- > > Key: JBIDE-22761 > URL: https://issues.jboss.org/browse/JBIDE-22761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > > This was spotted by Radim on linux today - he added EAP 7 via runtime detection, then started it and then tried to connect via jmx and it failed for him. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22763) [regression] deploying an docker image doesn't select proper project

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22763: ----------------------------------- Summary: [regression] deploying an docker image doesn't select proper project Key: JBIDE-22763 URL: https://issues.jboss.org/browse/JBIDE-22763 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM1 Reporter: Fred Bricon There's a regression in the Deploy Docker image wizard, where, when you have multiple projects, the selected project in OS explorer is ignored in the wizard. This works fine in devstudio 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22472) Improve UI of per-module zip settings

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22472?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22472. --------------------------------- Verified in devstudio 10.0.1.AM2 B5663 > Improve UI of per-module zip settings > ------------------------------------- > > Key: JBIDE-22472 > URL: https://issues.jboss.org/browse/JBIDE-22472 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > This is a follow up of JBIDE-22157 and JBIDE-20577. > When you were implementing JBIDE-22157, you asked me for feedback which I gave you but there was no further reply from you: > https://github.com/jbosstools/jbosstools-server/pull/412 > {quote} > what happens if I select to zip all? the new column does not apply then? it would be good to make this obvious somehow. > also, could it be a checkbox instead of false/true? > {quote} > 1) Could we have checkboxes instead of true/false? > 2) On a new server adapter, a "false" actually means "see default above" - once you change the default to compress all, each "false" will change to "true". But once you change a module to true and then back to false, changing the default will no longer affect the module settings anymore. This is counter intuitive. > So what would make more sense in my opinion is to have checkboxes for each module and then perhaps a link called "all" at the column header? And get rid of the default settings? What do you think? -- 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