How are people handling continues deployment on wildfly, when the artifact version changes between deployments?
Currently I manage it with by calling the wildfly-maven-plugin twice, first I do a wildcard (matchPattern) undeploy and then I do a normal deployment afterwards.
I don't find it very robust, if the deployment fails there is no way to roll back and if there is no initial deployment it also fails (both scenaries requires human intervention to recover).
I decided to write a small tool based on https://blog.codecentric.de/en/2015/01/automated-wildfly-deployments-shell-scripting/ that I could use in maven/gradle/jenkins to automate deployment, but don't feel like reinventing the wheel.
Best regards Jens
Retrieving data ...