[jboss-jira] [JBoss JIRA] (WFLY-8867) Legacy protocol property resource operations do not work for legacy protocols

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro moved JBEAP-11254 to WFLY-8867:
--------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8867  (was: JBEAP-11254)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                           (was: Clustering)
    Affects Version/s: 11.0.0.Alpha1
                           (was: 7.1.0.DR18)
                           (was: 7.1.0.DR19)


> Legacy protocol property resource operations do not work for legacy protocols
> -----------------------------------------------------------------------------
>
>                 Key: WFLY-8867
>                 URL: https://issues.jboss.org/browse/WFLY-8867
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Blocker
>
> QE Cc [~mnovak], [~okalman], [~mstyk], [~pkremens]
> Cc [~kabirkhan], [~jason.greene]
> See steps to reproduce. The question is, to what degree should CLI commands be backward compatible with 7.0? XML configurations pasted from 7.0 are OK in this case.
> I previously thought these changes were OK (once documented in migration guide), but after discussion with the rest of the QE team, the most common opinion is that CLI commands should be 100% backward compatible with 7.0, which is not the case here.
> [~bilge] since this is not stated anywhere I know, can you confirm that CLI commands in 7.1 need to be backward compatible with 7.0?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)