April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3730: ----------------------------- > Headless standalone installer can be run with xml config that contains eap bundle > --------------------------------------------------------------------------------- > > Key: JBDS-3730 > URL: https://issues.jboss.org/browse/JBDS-3730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > > One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: > {noformat}[ Starting automated installation ] > [INFO] Selected JVM Information > [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 > [INFO] Vendor : Oracle Corporation > [INFO] Version : 1.8.0_72 > [INFO] Arch : 64-bit > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] > [ Processing package: JBoss Enterprise Application Platform (4/4) ] > [ WARNING: Error executing > /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] > [ ERROR: The installation was not completed ] > [ Unpacking finished ] > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) > at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) > at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) > at com.izforge.izpack.installer.Installer.main(Unknown Source) > [ Automated installation FAILED! ]{noformat} > The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3730: -------------------------------- Target Release: 10.0.0.GA > Headless standalone installer can be run with xml config that contains eap bundle > --------------------------------------------------------------------------------- > > Key: JBDS-3730 > URL: https://issues.jboss.org/browse/JBDS-3730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > > One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: > {noformat}[ Starting automated installation ] > [INFO] Selected JVM Information > [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 > [INFO] Vendor : Oracle Corporation > [INFO] Version : 1.8.0_72 > [INFO] Arch : 64-bit > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] > [ Processing package: JBoss Enterprise Application Platform (4/4) ] > [ WARNING: Error executing > /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] > [ ERROR: The installation was not completed ] > [ Unpacking finished ] > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) > at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) > at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) > at com.izforge.izpack.installer.Installer.main(Unknown Source) > [ Automated installation FAILED! ]{noformat} > The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3721?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3721: -------------------------------- > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > 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, 11 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: -------------------------------- Target Release: 10.0.0.GA > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > 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, 11 months

1
0
0 / 0

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3827: ----------------------------- > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > 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, 11 months

1
0
0 / 0

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3827: -------------------------------- > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > 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, 11 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: -------------------------------- Target Release: 10.0.0.GA > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > 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, 11 months

1
0
0 / 0

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3828?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3828: ----------------------------- > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > 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, 11 months

1
0
0 / 0

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3828?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3828: -------------------------------- > 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: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > 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, 11 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: -------------------------------- Target Release: 10.0.0.GA > Run the msi installers with suppressed UI > ----------------------------------------- > > Key: JBDS-3820 > URL: https://issues.jboss.org/browse/JBDS-3820 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > 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, 11 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 April 2016