[jboss-jira] [JBoss JIRA] (WFLY-1972) CLI command should not allow same runtime-name to be used at another deploy

[Emmanuel Hugonnet (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800502#comment-12800502 ] 

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.
                
> CLI command should not allow same runtime-name to be used at another deploy
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-1972
>                 URL: https://issues.jboss.org/browse/WFLY-1972
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Emmanuel Hugonnet
>            Assignee: Brian Stansberry
>
> Having two deployments with the same runtime-name in the domain content repository, so they can be deployed to different instances, is ok.
> Having two deployments with the same runtime name actually deployed to an instance is not (that's the issue here).
> Same for standalone.

--
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