[ https://issues.jboss.org/browse/WFLY-1972?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet commented on WFLY-1972: ----------------------------------------- A little more detail... The original issue was found in domain mode: <deployments> <deployment name="test.war.v1" runtime-name="test.war"> <content sha1="abc..."/> </deployment> <deployment name="test.war.v2" runtime-name="test.war"> <content sha1="def..."/> </deployment> </deployments> <server-groups> <server-group name="main-server-group" profile="full"> <deployments> <deployment name="test.war.v1" runtime-name="test.war"/> <deployment name="test.war.v2" runtime-name="test.war"/> </deployments> </server-group> </server-groups> The first <deployments> section is correct. In that section, only "name" must be unique. But the two entries in <server-group><deployments> is a bug, as runtime-name must be unique there. The test case listed in the original BZ description is the standalone equivalent of the above configuration, where runtime-name *must* be unique but is isn't being enforced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira