October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4047) Uninstaller does not clean up Path

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4047?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4047. ----------------------------- Verified in devsuite-1.1.0-GA-20161014-172-bundle-installer.exe > Uninstaller does not clean up Path > ---------------------------------- > > Key: JBDS-4047 > URL: https://issues.jboss.org/browse/JBDS-4047 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > > After running the uninstall script all the PATH entries pointing to the devsuite install folder remain untouched. My guess is the actual folder these entries are compared to is not the root install folder, but the uninstall one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4079) Typo in folder name "unistaller"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4079?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4079. ----------------------------- Verified in devsuite-1.1.0-GA-20161014-172-bundle-installer.exe > Typo in folder name "unistaller" > -------------------------------- > > Key: JBDS-4079 > URL: https://issues.jboss.org/browse/JBDS-4079 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > Attachments: typo.png > > > !typo.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3813) Using a network path in the target folder causes stuttering

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3813?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3813. ----------------------------- Closing as no longer reproducible. > Using a network path in the target folder causes stuttering > ----------------------------------------------------------- > > Key: JBDS-3813 > URL: https://issues.jboss.org/browse/JBDS-3813 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.AM2 > > > The target folder validator will check (synchronously) if a directory with the given path exists with every change. Using a path such as //domain/folder will trigger a check that takes about a second or two while the UI stops responding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23352: ---------------------------------- Description: In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port. If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. !no_route_selected.png! was: In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port and thus useless routing. User has to edit a port mapping to check checkbox, confirm the dialog and then finish. If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. !no_route_selected.png! > Deploy Docker Wizard: No port is selected by default to be used for routing > --------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port. > If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4104) Include a version of CDK using OpenShift 3.3 in Development suite installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4104?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4104. ----------------------------- Verified in devsuite-1.1.0-GA-20161014-172-bundle-installer.exe > Include a version of CDK using OpenShift 3.3 in Development suite installer > --------------------------------------------------------------------------- > > Key: JBDS-4104 > URL: https://issues.jboss.org/browse/JBDS-4104 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4107) Devstudio install config has wrong java path on windows

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4107?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4107. ----------------------------- Looks like it installs fine again, closing. > Devstudio install config has wrong java path on windows > ------------------------------------------------------- > > Key: JBDS-4107 > URL: https://issues.jboss.org/browse/JBDS-4107 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.2.0.AM2 > > > I'm getting this error whenever I select JDK and Devstudio for installation: > {noformat}"[ERROR] configured java executable 'C:\DevelopmentSuite\jdk8\bin\java' doesn't match regular location inside home directory"{noformat} > I'm guessing the following commit introduced the issue, because the path now doesn't contain an exe file for windows. > https://github.com/redhat-developer-tooling/developer-platform-install/pu... > It actually doesn't matter if JDK is skipped or installed, the path just doesn't point to the exe. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22803: ------------------------------------------ [~jcantrill], thank you for confirmation. I've just dug a bit into WebSockets to understand the nature of {code:java} WatchClient.WatchEndpoint.onFailure(IOException, Response) is called with: _err.getClass()_ = "class java.net.ProtocolException" _err.getMessage()_ = "Expected HTTP 101 response but was '200 OK'" _response_ = "Response{protocol=http/1.1, code=200, message=OK, url=https://10.1.2.2:8443/oapi/v1/projects?watch=true&}" _response.request()_ = Request{method=GET, url=https://10.1.2.2:8443/oapi/v1/projects?watch=true&, tag=Request{method=GET, url=https://10.1.2.2:8443/oapi/v1/projects?watch=true&, tag=null}} {code} why is it failure, when it is ok. So i can say that it is not an OS server issue, it's the way web sockets work. Here is the specification: https://tools.ietf.org/html/rfc6455#page-8 (you can just do Ctrl-F and print 101): {quote} If the |Sec-WebSocket-Accept| value does not match the expected value, if the header field is missing, or if the HTTP status code is not 101, the connection will not be established, and WebSocket frames will not be sent.{quote} So i think we can think of such onFailure as a signal of a disabled project watching feature. I'll try to work it up the right way in resclient and throw an UnsupportedOperationException when its not supported. > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23352: ---------------------------------- Description: In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port and thus useless routing. User has to edit a port mapping to check checkbox, confirm the dialog and then finish. If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. !no_route_selected.png! was: In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port and thus useless routing. User has to edit a port mapping to check checkbox, confirm the dialog and then finish. If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. > Deploy Docker Wizard: No port is selected by default to be used for routing > --------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port and thus useless routing. User has to edit a port mapping to check checkbox, confirm the dialog and then finish. > If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23352: ---------------------------------- Attachment: no_route_selected.png > Deploy Docker Wizard: No port is selected by default to be used for routing > --------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port and thus useless routing. User has to edit a port mapping to check checkbox, confirm the dialog and then finish. > If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23352: ---------------------------------- Steps to Reproduce: ASSERT: Have an OpenShift connection with a project. EXEC: Select the project and select context menu item Deploy Docker Image... EXEC: In the Deploy Image to OpenShift wizard paste image name docker.io/openshift/hello-openshift EXEC: Click Next EXEC: Click Next ASSERT: You are on routing wizard pages. RESULT: No checkbox next to ports is selected. EXPECTED RESULT: One checkbox is selected as default. > Deploy Docker Wizard: No port is selected by default to be used for routing > --------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port and thus useless routing. User has to edit a port mapping to check checkbox, confirm the dialog and then finish. > If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016