August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24676: -------------------------------- Sprint: devex #137 September 2017 > CDK3 server adapter's console view is using wrong coding on all platforms > ------------------------------------------------------------------------- > > Key: JBIDE-24676 > URL: https://issues.jboss.org/browse/JBIDE-24676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.5.0.AM2 > Environment: Windows, Linux, macOS > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: Console_output.png, cdk_console_coding.png > > > Console view on all platforms show strange characters. See the pic. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24293) Lot of blank lines written to terminal when starting the CDK server

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24293?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24293: --------------------------------------- I believe that this jira is duplicate to https://issues.jboss.org/browse/JBIDE-24188. [~jeffmaury] I do not think so that moving back to terminal will help to solve this problem as it was reported during the time that minishift tty output was logged in Terminal View. (If this is what you meant by Eclipse terminal). > Lot of blank lines written to terminal when starting the CDK server > ------------------------------------------------------------------- > > Key: JBIDE-24293 > URL: https://issues.jboss.org/browse/JBIDE-24293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: terminalOutputWhenStartingCDK.txt > > > Windows 10 > Version: 10.4.0.AM3 > Build id: AM3-v20170406-1058-B390 > Build date: 20170406-1058 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24188) CDKv3 terminal output in IDE is ugly when using hyperv

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24188?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24188: -------------------------------- Sprint: devex #137 September 2017 > CDKv3 terminal output in IDE is ugly when using hyperv > ------------------------------------------------------ > > Key: JBIDE-24188 > URL: https://issues.jboss.org/browse/JBIDE-24188 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Environment: Windows 10, x86_64, hyper V. > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.x > > Attachments: Terminal-HyperV.png, cdk3-hyperv-terminal > > > While starting/stopping CDKv3 server adapter, you can observe flashing window (coming from hyperV) in terminal tab. The output looks bit ugly, there is pretty much space. When starting/stoping minishift from windows command prompt, you can see such blue flashing/blinking window, too. When I tried cygwin terminal, this did not happen. I am not sure if we can do anything about it, it seems like upstream/system issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24491: -------------------------------- Sprint: devex #137 September 2017 > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24111: -------------------------------- Sprint: devex #131 April 2017, devex #137 September 2017 (was: devex #131 April 2017) > Verify EAP 7.1 compatibility from EAP team > ------------------------------------------ > > Key: JBIDE-24111 > URL: https://issues.jboss.org/browse/JBIDE-24111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: eap, server > Fix For: 4.5.x > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22613: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM2) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.x > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23869: ------------------------------- Sprint: devex #128 February 2017, devex #130 April 2017, devex #137 September 2017 (was: devex #128 February 2017, devex #130 April 2017) > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.5.x > > Attachments: failure.png, image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24787) Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24787?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24787: ------------------------------------- Story Points: 16 > Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24787 > URL: https://issues.jboss.org/browse/JBIDE-24787 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter, wildfly > Fix For: 4.5.1.AM2 > > > The changes in the PR for JBIDE-24184 is overhauling the server adapter(s) code. We should make sure that the updated code allows individual server adapters (we have per app-type - eap, wildfly, nodejs, etc.) can provide their own defaults in code. As discussed in the parent jira to this: https://issues.jboss.org/browse/JBIDE-24548?focusedCommentId=13428424&pag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24935) CDK3 server adapter: improve error message if it fails bcs no minishift location was set

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24935?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24935: -------------------------------- Fix Version/s: 4.5.1.AM2 Sprint: devex #137 September 2017 > CDK3 server adapter: improve error message if it fails bcs no minishift location was set > ---------------------------------------------------------------------------------------- > > Key: JBIDE-24935 > URL: https://issues.jboss.org/browse/JBIDE-24935 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > Attachments: cdk3-server-adapter-failed-to-start-credentials.png, cdk3-server-adapter-failed-to-start.png > > > # ASSERT: make sure that you have a cdk3/minishift-server adapter which is missing the "Minishift Binary" location. > # EXEC: launch the server adapter > Result: > Server adapter fails to start, which is expected. But then the error message talks about the env vars missing the minishift binary. How would I as a dumb user know that I need to correct/set it in the server editor? IMHO we should tell so in the error message. > !cdk3-server-adapter-failed-to-start.png! > btw. if the username is missing, the error message tells me to open up the server editor, which tells the dump user what exactly to do. > !cdk3-server-adapter-failed-to-start-credentials.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24787) Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24787?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24787: ------------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24787 > URL: https://issues.jboss.org/browse/JBIDE-24787 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter, wildfly > Fix For: 4.5.1.AM2 > > > The changes in the PR for JBIDE-24184 is overhauling the server adapter(s) code. We should make sure that the updated code allows individual server adapters (we have per app-type - eap, wildfly, nodejs, etc.) can provide their own defaults in code. As discussed in the parent jira to this: https://issues.jboss.org/browse/JBIDE-24548?focusedCommentId=13428424&pag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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