[ https://issues.jboss.org/browse/WFCORE-2147?page=com.atlassian.jira.plugi... ] Yeray Borges commented on WFCORE-2147: -------------------------------------- Hello [~a13397] Yes, sure, WildFly code is opensource, and you can build and patch any version by yourself. Keep in mind the changes proposed on this pull request have not been approved yet so that they could change. Sadly there are other priorities above this issue that prevents this one continue moving on, so the pull request is in the queue, pending for review. Anyway, if you want to patch a previous server version, you can do it. The changes proposed to fix this issue are split into two projects: [wildfly|https://github.com/wildfly/wildfly] and [wildfly-core|https://github.com/wildfly/wildfly-core]. Backporting the changes could be easy, but the code changes from one release to another so, maybe you could find conflicts that you will need to resolve by yourself manually, in general terms, you should understand a bit the changes proposed and how the issue is fixed. What you would need to do is to pick up from GitHub the tag of the Wildfly release you want to patch. You will need to inspect the pom.xml to see which wildfly-core version is used in that WildFly release. Once you have this information, get the wildfly-core tag for that version and apply the changes incorporated on this [PR|https://github.com/wildfly/wildfly-core/pull/4002] in the wildfly-core project and build it locally on your computer. You will end up with a patched wildfly-core version on your local maven repository. Once you have patched wildfly-core project, you will need to apply the changes of this [PR|https://github.com/wildfly/wildfly/pull/12768] on the WildFly project you checked out before and build it. Then you will have a WildFly server patched. If you build the server using -Drelease option, you will find under $WFLY_SOURCE_HOME/dist/target/ a zip file which is the version built by you manually. -- This message was sent by Atlassian Jira (v7.13.8#713008)