April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3983: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Development Suite Installer should work behind proxy > ---------------------------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: release_notes > Fix For: 10.4.0.GA > > > DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings: > CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation. > To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy: > * http(s)://servername.com:3128 > * http(s)://192.168.0.47:3128 > For auth proxy: > * http(s)://username:password@servername.com:3128 > * http(s)://username:password@192.168.0.47:3128 > If you use email as username then replace @ with %40: > * http(s)://username%40server.com:password@servername.com:3128 > * http(s)://username%40server.com:password@192.168.0.47:3128 > Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4121) Run DevSuite Installer with Elevated privileges on Mac OSX

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4121?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4121: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Run DevSuite Installer with Elevated privileges on Mac OSX > ---------------------------------------------------------- > > Key: JBDS-4121 > URL: https://issues.jboss.org/browse/JBDS-4121 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.4.0.GA > > Attachments: DevSuite.zip > > > During installation PATH environment variable should be updated. For example to make permanent changes for PATH variable /etc/paths file should be modified and that requires administrative privileges. > For Alpha release we could be running installer with sudo > {code}sudo open DevSuite.app{code} > Another option to investigate is using AppleScript and run the same shell script above with elevated privileges like this > {code}do shell script «open DevSuite.app» with administrator privileges{code} > that would trigger standard UI Dialog requesting user login/password with administrative privileges. This should be included int DevSuite.app package configuration after it is assembled by electron packages. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4069) BreadCrumb should be fixed on top of the page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4069?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4069: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > BreadCrumb should be fixed on top of the page > --------------------------------------------- > > Key: JBDS-4069 > URL: https://issues.jboss.org/browse/JBDS-4069 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > > Confirmation and Install pages have scrolling. BreadCrumb should always stay on to of the page to let user see current steps and overall installation progress without scrolling back up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3762) Add logging to configuration page for detection and configured items

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3762?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3762: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Add logging to configuration page for detection and configured items > -------------------------------------------------------------------- > > Key: JBDS-3762 > URL: https://issues.jboss.org/browse/JBDS-3762 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: Havoc > Fix For: 10.4.0.GA > > > Log what was detected and selected on configuration page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4310) Verify checksums for downloaded resources in cache on confirmation page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4310?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4310: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Verify checksums for downloaded resources in cache on confirmation page > ----------------------------------------------------------------------- > > Key: JBDS-4310 > URL: https://issues.jboss.org/browse/JBDS-4310 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.GA > > > This would let to show correct message on 'Download and Install" button. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3635: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Critical > Labels: havoc, ui > Fix For: 10.4.0.GA > > Attachments: Technologies 5.pdf, pdkinstaller.png > > > Generic rules for detection and validation are: > 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio; > 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition. > vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems; > virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning; > jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning; > 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location; > 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use. > 5. When location for required software set manually installer try will try detect version and verify it using (2); > 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning. > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3701: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Add check for an existing Java to find if it is JRE or JDK > ---------------------------------------------------------- > > Key: JBDS-3701 > URL: https://issues.jboss.org/browse/JBDS-3701 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > > JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3839) Change the progress bar color to red in case of failure

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3839?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3839: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Change the progress bar color to red in case of failure > ------------------------------------------------------- > > Key: JBDS-3839 > URL: https://issues.jboss.org/browse/JBDS-3839 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4103) Prefer JDK over JRE as VM set in devstudio.ini

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4103: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Prefer JDK over JRE as VM set in devstudio.ini > ---------------------------------------------- > > Key: JBDS-4103 > URL: https://issues.jboss.org/browse/JBDS-4103 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > When using JBDS, a lot of people will use Maven and having a JDK by default is better. > It allows to launch Maven install with java compilation directly, without extra configuration. > (as a side note, do we really want to set a vm? when the Vm is updated, the link is broken and we need to update it) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4033) Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4033?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4033: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4033 > URL: https://issues.jboss.org/browse/JBDS-4033 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: NB: windows 10 Pro, x86_64 > Virtual machines: > windows 10 Enterprise, x86_64 > windows 7 Pro, x86_64, SP1 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Critical > Labels: release_notes, ui > Fix For: 10.4.0.GA > > > Installation ends up with CDK failed status. Others installation of components is completed. > Error message from install log: > ------------------------------ > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute options { > "env": { > "ALLUSERSPROFILE": "C:\\ProgramData", > "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming", > "CommonProgramFiles": "C:\\Program Files\\Common Files", > "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files", > "CommonProgramW6432": "C:\\Program Files\\Common Files", > "COMPUTERNAME": "SOME-PC", > "ComSpec": "C:\\Windows\\system32\\cmd.exe", > "FP_NO_HOST_CHECK": "NO", > "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q", > "HOMEDRIVE": "C:", > "HOMEPATH": "\\Users\\jbossqa", > "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local", > "LOGONSERVER": "\\\\SOME-PC", > "NUMBER_OF_PROCESSORS": "2", > "OS": "Windows_NT", > "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\DevelopmentSuite\\jdk8\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;C:\\DevelopmentSuite\\vagrant\\bin;bin;C:\\DevelopmentSuite\\virtualbox\\", > "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC", > "PROCESSOR_ARCHITECTURE": "AMD64", > "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel", > "PROCESSOR_LEVEL": "6", > "PROCESSOR_REVISION": "3c01", > "ProgramData": "C:\\ProgramData", > "ProgramFiles": "C:\\Program Files", > "ProgramFiles(x86)": "C:\\Program Files (x86)", > "ProgramW6432": "C:\\Program Files", > "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\", > "PUBLIC": "C:\\Users\\Public", > "SystemDrive": "C:", > "SystemRoot": "C:\\Windows", > "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "USERDOMAIN": "Some-PC", > "USERNAME": "jbossqa", > "USERPROFILE": "C:\\Users\\jbossqa", > "VAGRANT_DETECTED_OS": "cygwin", > "VBOX_MSI_INSTALL_PATH": "C:\\DevelopmentSuite\\virtualbox\\", > "windir": "C:\\Windows", > "windows_tracing_flags": "3", > "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", > "__COMPAT_LAYER": "VistaSetup" > }, > "cwd": "c:\\DevelopmentSuite\\cdk\\boxes" > } > Wed, 31 Aug 2016 11:23:39 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > [0;31mAn error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. > ---------------------- > After manual attempt to add box via cli with commad: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box: > --------------------- > C:\DevelopmentSuite\cdk\boxes>vagrant box add --name cdkv2 rhel-vagrant-virtualb > ox.box > ==> box: Box file was not detected as metadata. Adding it directly... > ==> box: Adding box 'cdkv2' (v0) for provider: > box: Unpacking necessary files from: file://C:/DevelopmentSuite/cdk/boxes/rh > el-vagrant-virtualbox.box > box: > An error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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