From the meeting minutes, I understand that we have voted to not
support this feature. It's probably worth noting in the installation doc that this way
is available but not supported to prevent potential issues.
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?