Description of problem: If a user attempts to use the UI installer to install SOA6.0.ER2, and that user selects as the installation destination directory an existing directory, this warning message is displayed: "The given directory exists, and must contain an EAP installation. Do you want to continue?" There are 2 issues with this message: 1) The message is displayed regardless of whether the directory is empty or not 2) ER2 bundles an EAP installation. There is no need for the user to install EAP before installing ER2. Version-Release number of selected component (if applicable): SOA6.0.ER2 How reproducible: 100% Steps to Reproduce: 1. Run the installer, direct it at an existing directory 2. 3. Actual results: See attached screenshot. Expected results: Additional info:
Created attachment 794676 [details] Screenshot
The installer should support installing on an existing EAP according to the Installer Requirements document.
The idea behind this message is that, if the user selects an already existing directory, that they already have EAP laid down in that directory, and we use this fact to toggle the laying down of the EAP bits. If this should change, we should have a short discussion around what should change :)
Message has been changed to a more general message warning about the directory existing. No mention of EAP is made, unless the given directory contains a jboss-eap-6.1 directory. If this is the case, the jboss-eap-6.1 subdirectory is checked in the following ways: a) jboss-eap-6.1/bin/product.conf i) it exists. ii) it contains "slot=eap". A specific error message is printed if this is not true. b) jboss-eap-6.1/modules/layers.conf i) Does not exist. If it does, the EAP installation is not unmodified, and installation cannot continue. c) At least one of the following sets of files must exist: i) jboss-eap-6.1/bin/domain.sh & jboss-eap-6.1/domain/configuration/domain.xml ii) jboss-eap-6.1/bin/standalone.sh & jboss-eap-6.1/standalone/configuration/standalone.xml These should probably be refined, as these checks were designed when the installer was still going to be installed on varying EAP / SOA / SRAMP installations.
The text has been modified.
Verified fixed in ER3 (Sept 20 repin)