[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24803: --------------------------------------- It turns out that our assumptions about DV 6.3 were not 100 % accurate. DV 6.3 actually either installs in a new folder - then it's a complete install including EAP 6.4. Or it installs into a 6.4 folder. But if you point it to an existing directory which is not an eap 6.4 installation, it will give you an error. So assume you want to install DV into /tmp. In our Download dialog, you will set Install Folder to /tmp. Then it will download the 900MB DV 6.3 installer and when it starts, the install path will be pre-filled for you to say /tmp. But the installer will not accept it - it either wants a non-existing directory that it will create for you or a directory containing eap 6.4. OK, so what if I entered the desired target directory in our Download dialog - say /tmp/dv-6.3? What won't work (probably) either - our tooling will tell you that this directory does not exist and will be created for you. But if it's indeed created before the jar installer of dv 6.3 is started, then the installer will complain that eap 6.4 is missing in that folder. I'm not sure what we could do here. We could automatically add a subfolder to the target path when starting the jar installer. But that may be undesirable if the user already enters something like /tmp/dv-6.3. Or we could skip the creation of the folder in this case, that would probably work. But I would say that it's not worth the effort and we can just leave it as is for now - it still works, but you will usually have to change the install folder in the installer. Now what about DV 6.2 where it requires an installation of EAP 6.4? The dialog says: "It is strongly recommended you first install EAP 6.4 before proceeding." Well, this is not strictly correct - it's not recommended, it's required - I am not allowed to proceed without it. But I guess I'm nitpicking. It's not a big deal. {quote} What happens if you download dv 6.2 (that requires path to existing eap 6.4) and you already have it configured in runtime detection? Variant a): You already have this exact path in 'paths to search for runtimes' {quote} Answer: You will get an error: "Unable to initialize some runtime paths." I guess it's kind of expected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)