[
https://issues.jboss.org/browse/WFLY-1972?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-1972:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug
983980|https://bugzilla.redhat.com/show_bug.cgi?id=983980] from VERIFIED to CLOSED
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
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Fix For: 8.0.0.Beta1
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