Bug 1021901 - Cannot enter valid name for Program group during console installation
Summary: Cannot enter valid name for Program group during console installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER7
: EAP 6.2.0
Assignee: Francisco Canas
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-22 09:57 UTC by Petr Kremensky
Modified: 2014-09-03 04:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:22:14 UTC
Type: Bug


Attachments (Terms of Use)

Description Petr Kremensky 2013-10-22 09:57:21 UTC
Description of problem:
 User cannot change the name of program group for shortcuts while installing EAP via console installer. First input character is taken as new program group name.

Version-Release number of selected component (if applicable):
 EAP 6.2.0.ER6

How reproducible:
 Always

Steps to Reproduce:
 1. Run console installion: java -jar jboss-eap-6.2.0.ER6-installer.jar -console
 2. Select to Create shortcuts in the Start-Menu once prompted (default value).
 3. Try to change the name of a Program Group for the Shortcuts.

Actual results:
 First character user inputs is taken as Program Group name, installation will instantly move to next step (auto.xml generation)

Expected results:
 User can enter new program group name, installation won't continue to next step unless user press the enter key.

Comment 1 Francisco Canas 2013-10-22 15:14:32 UTC
Changed the method input is gathered for the shortcut panel to use the Shell class, and this change fixes the issue.

http://git.app.eng.bos.redhat.com/izpack.git/commit/?h=izpack-wip&id=be4dd1ee88a85d7c29654276e7b024d2bd02d488

Comment 2 Petr Kremensky 2013-11-01 11:12:52 UTC
Verified on EAP 6.2.0.ER7 installer.


Note You need to log in before you can comment on or make changes to this bug.