Created attachment 844742 [details]
Pointing installer to existing EAP 6.1.1
Description of problem:
Attached screenshots showing installer asking for a new location or an existing eap 6 to install BPM Suite (ER7), point to a new location installs EAP 6.1.1 + BPM suite fine, point to existing EAP 6.x it pops up saying it will install a new eap 6 one level deeper into the existing installed EAP 6.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. see above
Tries to install into existing EAP 6 one level deeper a new EAP 6 + BPM Suite.
Recognise existing EAP 6, test it for EAP 6.1.1 (only one that works), fail if not right version, check for installed BPM Suite and only proceed if not yet installed.
see screenshots attached.
Created attachment 844743 [details]
Pop up showing going to install new eap + bpm suite inside existing install
If you have EAP at /dir/jboss-eap-6.1, please input /dir instead of /dir/jboss-eap-6.1 into installer as existed path.
I think that this behaviour is not intuitive enough.
Let's see if we can checkout both /dir and /dir/jboss-eap-6.1 or add more intiutive instuctions into the UI.
What is the decision regarding this issue?
(In reply to Thomas Hauser from comment #4)
> What is the decision regarding this issue?
It's highly likely that the user is going to select 'jboss-eap-x.x' directory for an existing EAP installation. The installer should identify this EAP installation and use it.
It would be nice to preserve the current behavior (scan for jboss-eap-x.x in any /dir/) as well if customers are used to it.
Short term we can indicate this more clearly through text/examples on the installer screen for choosing an existing EAP.
At this stage, we've decided to display a more verbose message to the user when they specify a directory that the installer considers not to contain EAP.
Created attachment 876063 [details]
New Installer warning
New installer warning. Any comments / further clarifications?
I would recommend adding a note explaining which folder is expected as an input. It can be placed above the installation path field so a user does not need to proceed to the next step to find out the answer. It will also be compatible with bug 1062411. When it is resolved only this note will need to be rewritten.
Due to a bug in IzPack, the previous solution was created. We have gone ahead and fixed the bug preventing us from doing what you detailed in your comment, Tomas. The new note appears directly on the panel instead of in a warning after clicking the next button.