Description:
Test plan to add integration tests for "use-legacy-override", behavior of default-controller and default-protocol defined in jboss-cli.xml when connecting to a server. Additionally test that the correct port is used according to specified protocol when no port is explicitly specified.
Added integration tests for server aliases defined in jboss-cli.xml

Usage in bin/jboss-cli.xml:

<controllers>
        <controller name="ServerOne">
            <protocol>http-remoting</protocol>
            <host>localhost</host>
            <port>9990</port>
        </controller>
    </controllers>

./bin/jboss-cli.sh --controller=ServerOne --connect

TEST PLAN for controller aliases

1. set invalid default controller configuration to ensure all settings are being loaded only from controller aliases
2. connect to controller alias with all options (protocol, hostname, port) specified
3. protocol specified in <default-controller> overrides <default-protocol> when calling --connect without --controller
4. empty jboss-cli.xml configuration uses implicit settings for both default controller and controller alias

TEST PLAN for use-legacy-override

./bin/jboss-cli.[sh/bat] --connect [--controller=localhost:$TESTED_PORT]

• <default-protocol use-legacy-override=true> && no protocol specified && port=9999 → use remoting://
• <default-protocol use-legacy-override=false> && no protocol specified && port=9999 → use protocol from <default-protocol>
• no protocol specified in <default-controller> → use <default-protocol>
• <default-protocol> is overridden by protocol defined in <default-controller> (JBEAP 7.0.0 new element)