[ https://issues.jboss.org/browse/JBDS-4409?page=com.atlassian.jira.plugin.... ] Dmitrii Bocharov commented on JBDS-4409: ---------------------------------------- As i said during the call, i suspect what is the reason of this issue. Recently we've had the issue JBIDE-23603. As you can find in the comments, i'm not happy with the fix i've done. What i did is a clean publish for eap server adapters. [See here|https://github.com/jbosstools/jbosstools-openshift/blob/a64fef55bbb4...] The detection whether our server adapter is eap or anything else happens [here|https://github.com/jbosstools/jbosstools-openshift/blob/a64fef55bbb4...]. You can find there that there is a EAP_LIKE_KEYWORDS collection that contains both "eap" and "wildfly". But i suspect that something in this detector doesn't work correctly for eap, and the server adapter is considered to be a general one (not wildfly\eap - like), that's why a usual publish runs ( without clean). So there're 2 possible ways now: 1) Find the reason why does clean publish work and simple publish doesn't. I remember, that i spent some time for this, but we had a code freeze soon, so i made this quick fix. 2) Quick fix. As said above i suspect there is some error logic of eap\wildfly detector. So we need to find it so that the same clean publish is applied for wildfly as for eap. -- This message was sent by Atlassian JIRA (v7.2.3#72005)