July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3721) Installer - Installer should check for required free disk space, ala the JBDS installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3721?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3721: -------------------------------- Sprint: devex #118 July 2016 > Installer - Installer should check for required free disk space, ala the JBDS installer > --------------------------------------------------------------------------------------- > > Key: JBDS-3721 > URL: https://issues.jboss.org/browse/JBDS-3721 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > The current installer is 1.5+GB in size. I have not gotten the installer to run cleanly to a complete installation, but it looks like it requires an additional 4-6 GB. Given that large free space requirement, the installer itself should perform a check and verify that sufficient free space is available before it attempts to perform an install. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3628) Cache downloaded files to reuse them in case of installation failure

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3628?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3628: -------------------------------- Sprint: devex #118 July 2016 > Cache downloaded files to reuse them in case of installation failure > -------------------------------------------------------------------- > > Key: JBDS-3628 > URL: https://issues.jboss.org/browse/JBDS-3628 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Labels: havoc > Fix For: 10.1.0.AM3 > > > This would be time saver for testing and in case of error during installation. Instead of downloading the same files over and over again installer would continue to download only missing ones. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3827) JBDS installation fails when (windows) user has non-ascii chars in the name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3827: -------------------------------- Sprint: devex #118 July 2016 > JBDS installation fails when (windows) user has non-ascii chars in the name > --------------------------------------------------------------------------- > > Key: JBDS-3827 > URL: https://issues.jboss.org/browse/JBDS-3827 > 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.AM3 > > > I have created a user named Pakoň and tried to install everything into the default folder. JBDS failed with: > {noformat}Fri, 15 Apr 2016 12:38:40 GMT-ERROR: jbds - Error: Command failed: c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true -jar C:\WINDOWS\7zS9F06.tmp\jbds.jar C:\Users\Pakoň\AppData\Local\Temp\jbds-autoinstall.xml > - ERROR - > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.<init>(FileInputStream.java:138) > at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(AutomatedInstaller.java:564) > at com.izforge.izpack.installer.AutomatedInstaller.<init>(AutomatedInstaller.java:86) > at com.izforge.izpack.installer.Installer.main(Unknown Source){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3731) Installer - Failure to install a component does not halt the installer's progress bar

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3731?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3731: -------------------------------- Sprint: devex #118 July 2016 > Installer - Failure to install a component does not halt the installer's progress bar > ------------------------------------------------------------------------------------- > > Key: JBDS-3731 > URL: https://issues.jboss.org/browse/JBDS-3731 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Environment: Windows10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Screenshot (20).png, Screenshot (24).png > > > See the attached screenshots - when the bug described in JBDS-3722 was encountered, the virtualbox installation status bar continued to proceed, even though the installation of the affected component had stopped. This will be confusing to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3757) Add some logging to setup routines

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3757: -------------------------------- Sprint: devex #118 July 2016 > Add some logging to setup routines > ---------------------------------- > > Key: JBDS-3757 > URL: https://issues.jboss.org/browse/JBDS-3757 > 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: havoc > Fix For: 10.1.0.AM3 > > > We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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: 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.AM3 > > > 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, 8 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: 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.AM3 > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3820) Run the msi installers with suppressed UI

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3820?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3820: -------------------------------- Sprint: devex #118 July 2016 > Run the msi installers with suppressed UI > ----------------------------------------- > > Key: JBDS-3820 > URL: https://issues.jboss.org/browse/JBDS-3820 > 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: havoc > Fix For: 10.1.0.AM3 > > > If I remember correctly, we've been running the msi installers with reduced UI (/qb) because suppressing the UI required administrative privileges. > Since the 7zipped installer needs those privileges to start, we could switch to using suppressed UI (/qn), could we not? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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: 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.AM3 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3798: -------------------------------- Sprint: devex #118 July 2016 > Repeated component detection keeps stale values > ----------------------------------------------- > > Key: JBDS-3798 > URL: https://issues.jboss.org/browse/JBDS-3798 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Environment: Setup-bundled-0.0.2-20160413-107 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: screenshot-1.png > > > Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same. > Using the existing (no longer existing in fact) installation fails, naturally. -- 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