-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
32.0.1.Final, 35.0.0.Beta1
-
None
With WildFly 27 I used the following command for updating a deployed and running app 'MyApp-1.0.0.war' to new version 1.0.1
./jboss-cli.sh --connect --command="deploy MyApp-1.0.1.war --runtime-name=MyApp.war --force"
The --force option led to replacing the the deployment with the new updated WAR file.
The same command now fails with WildFly 32.0.1 with the following error.
WFLYSRV0205: There is already a deployment called MyApp-1.0.1.war with the same runtime name MyApp
Please note that even the error message is wrong. There is no deployment 1.0.1 in WF but the old 1.0.0
- causes
-
WFCORE-7161 Improve deployment message on duplicate runtime name
-
- Resolved
-