Document (and verify) the current operation of the platform installer ---------------------------------------------------------------------- Key: JBDS-3942 URL: https://issues.jboss.org/browse/JBDS-3942 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.0.0.GA Reporter: Len DiMaggio Priority: Critical Fix For: 10.0.0.GA We have to be careful to test and document the operation of the installer for the release: Component detection as performed that the bundled platform installer has recently changed. It's important that we communicate clearly to our users how this detection is functioning as of today, and what their options are for running the installer. The installer installs these (6) high-level components: * CDK * Cygwin * VirtialBox * Vagrant * JDK * DevStudio Topic: Component Detection Performed by The Installer: As of today, the installer is able to detect these components: * Java * VirtualBox * Vagrant If a user runs the installer, and one of these detectable components is installed, the installer will verify that the version of the installed component is supported by the Developer Platform. If the version of the detected component installed is not supported, an error will be reported to the user. The installer will not automatically update the detected installed component to a supported version. If the version of the installed component is supported by the Developer Platform, the installer will not overwrite that installed component. Topic: Components Auto-Selected by the Installer If the installer is run on a system with none of the high level components pre-installed, the installer should have all components auto-selected to be installed. Topic: Optionally Installing Components As of today, users can choose to install selected components singly with the installer. The only dependency should be that if the user attempts to install DevStudio alone, the installer will require the user to also install the JDK at the same time.