[ https://issues.jboss.org/browse/JBIDE-22269?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22269: ------------------------------------- For EAP 7, these are the checks we make: 1) bin/product.conf exists 2) bin/product.conf has slot = "eap" 3) modules/system/layers/base/org/jboss/as/product/eap/dir/META-INF/MANIFEST.MF exists 4) JBoss-Product-Release-Name key in manifest.mf above has value "JBoss EAP" 5) JBoss-Product-Release-Version key in manifest.mf has value starting with "7.0" 6) jboss-modules.jar must exist 7) standalone/configuration/standalone.xml must exist Other checks most likely used by wildfly or older versions (but i'm not 100% sure) 8) modules/system/layers/base/org/jboss/as/server/main/anything.jar exists 9) anything.jar has proper manifest fields Wildfly 9/10 also check: 10) modules/system/layers/base/org/jboss/as/product/wildfly-full/dir/META-INF/MANIFEST.MF exists 11) the above manifest has proper fields JBoss-Product-Release-Name and JBoss-Product-Release-Version So basically, at this point we're introspecting likely places to find the wildfly / eap version and release-name strings. The keys are pretty well established, and I hope those never change. The values are what we compare against. Again, we can respond to key OR value changes, or even file-structure / location changes, if we have advance notice. It may hinder some of our 'tech-preview' functionality, but we should be able to get something up fairly quickly if we know whats' changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)