[
https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-4201:
-------------------------------------
IzPack provides three way to run installation from installer jar:
1. GUI installation {code}java -jar installer.jar{code}
2. Automated headless (no GUI) installation, when all required input like target location,
what to install and etc comes from xml file {code}java -jar installer.jar
automation-data.xml{code}
3. Console headless installation, when all user interaction is done through console
input/output in terminal {code}java -jar installer.jar -console{code}
4. (1) in some cases triggers (3) when executed from console probably due to upstream
issue in older releases of OpenJDK on Fedora.
I think it worth to mention installation types and say that (3) is not supported in case
someone hit (4) scenario. Because they now removed old documentation site for IzPack 4 and
created new one here
https://izpack.atlassian.net/wiki/display/IZPACK/IzPack+4. Problem is
it has no info about installation types at all.
CLI-only installation is available but does not provide necessary
info
----------------------------------------------------------------------
Key: JBDS-4201
URL:
https://issues.jboss.org/browse/JBDS-4201
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: installer
Affects Versions: 10.2.0.GA
Reporter: Misha Ali
Assignee: Denis Golovin
Fix For: 10.x
Attachments: InstallConfigRecord.xml
I had some feedback from another writer testing a procedure with devstudio. He was using
a CLI-only VM and was confused because the installer worked but offered little
information, as would be expected.
Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did
not ask where to install devstudio, nor did it provide the default target folder it used.
The GUI version asks if the user wants to deploy devstudio after the installation, but the
non-GUI version does nothing. The resulting user experience was confusion, not knowing
where devstudio was installed or how to start it.
My questions here are:
- is the non-GUI way a valid installation path? If yes, we should document it, and if
not, we should mention it, either in the docs or when installation happens.
- If the non-GUI installation is a valid path, it should replicate the questions in the
wizard, such as where to install devstudio and which jdk to use, etc. The difference
between the two installation paths causes confusion.
Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)