August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4002) OpenJDK detection does not work for build 1.8.0_101

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4002: ----------------------------------- Summary: OpenJDK detection does not work for build 1.8.0_101 Key: JBDS-4002 URL: https://issues.jboss.org/browse/JBDS-4002 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Because of changed format for version console output, installer cannot detect installed JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4002) OpenJDK detection does not work for build 1.8.0_101

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4002?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4002: ----------------------------- > OpenJDK detection does not work for build 1.8.0_101 > --------------------------------------------------- > > Key: JBDS-4002 > URL: https://issues.jboss.org/browse/JBDS-4002 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > > Because of changed format for version console output, installer cannot detect installed JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23006: ------------------------------- Story Points: 6 > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23000) Provide bot test for: Application based on builder images should have prefilled configuration

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23000?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23000: ------------------------------- Sprint: devex #119 August 2016 > Provide bot test for: Application based on builder images should have prefilled configuration > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23000 > URL: https://issues.jboss.org/browse/JBIDE-23000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.Final > > > As a follow up on JBIDE-22704, we should provide some bot tests that check that, when opening a New OpenShift Application wizard either from Central or shell menu File - New or the context menu of an OpenShift 3 project, details in builder image part of wizard are not missing. E.g. there should be a default resource name (build configuration wizard page), environment variables (Deployment Configuration and Scalability wizard page) or port mapping (Service and Routing Settings wizard page). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: (was: devex #118 July 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3754) Installer: redirect links for Vagrant and VirtualBox should use https

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3754?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3754: -------------------------------- Sprint: (was: devex #118 July 2016) > Installer: redirect links for Vagrant and VirtualBox should use https > --------------------------------------------------------------------- > > Key: JBDS-3754 > URL: https://issues.jboss.org/browse/JBDS-3754 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.1.0.GA > > > Installer's requirements.json file \[1] declares location of Vagrant and VirtualBox installers like these: > {code} > http://developers.redhat.com/redirect/to/vagrant-1.7.4.download > http://developers.redhat.com/redirect/to/virtualbox-5.0.8.download > {code} > They should use *https* scheme. > \[1] https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3825) Cygwin installs into a different folder when some non-ascii characters are present in folder name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3825?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3825: -------------------------------- Sprint: (was: devex #118 July 2016) > Cygwin installs into a different folder when some non-ascii characters are present in folder name > ------------------------------------------------------------------------------------------------- > > Key: JBDS-3825 > URL: https://issues.jboss.org/browse/JBDS-3825 > 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.1.0.GA > > > The usage of {{ˇ}} character for example makes cygwin installer interpret it as a middle dot character (which jira can't interpret correctly it seems). Thus it creates a separate folder for the cygwin installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3826) JBDS installation fails with folder name containing non-standard characters

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3826?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3826: -------------------------------- Sprint: (was: devex #118 July 2016) > JBDS installation fails with folder name containing non-standard characters > --------------------------------------------------------------------------- > > Key: JBDS-3826 > URL: https://issues.jboss.org/browse/JBDS-3826 > 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.1.0.GA > > > I have tried installing into this folder: > {noformat}c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform{noformat} > And JBDS installation failed immediately, the install.log was not very helpful. > {noformat}Fri, 15 Apr 2016 11:49:50 GMT-INFO: jbds - Execute c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds failed to install: Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3828) Virtualbox fails to install when user has non-ascii characters in the name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3828?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3828: -------------------------------- Sprint: (was: devex #118 July 2016) > Virtualbox fails to install when user has non-ascii characters in the name > -------------------------------------------------------------------------- > > Key: JBDS-3828 > URL: https://issues.jboss.org/browse/JBDS-3828 > 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.1.0.GA > > Attachments: vbox.png > > > Username: Pakoň > Leave everything on default. > While installing, virtualbox shows a pop-up saying > {noformat} > Source file not found: > C:\Users\Pakoň\AppData\Local\Temp\common.cab. > Verify that the file exists and that you an access it > {noformat} > Retry does nothing but show the dialog again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23006: ------------------------------- Sprint: devex #119 August 2016 > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016