]
Jason Greene commented on WFLY-8867:
------------------------------------
Yes the management model is supposed to retain compatibility. The exception is a major
release, and in that case it's ok if we have a migration operation. In the case of
elytron we have addressed compatibility by preserving the old and new subsystems.
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?