We want to test this change in Branch_4_2, so we can backport it to the EAP branch. So the timeframe is really that of the next EAP CP release - I'll find out.
I think the emphasis here would be not to break what's working now.
Well, the cutoff date for the next CP is ... today (Jan/21st).
I'm running the Branch_4_2 testsuite with the change. If it looks good I'll commit it, otherwise I'll hold it to the next release.
All the tests passed, so I committed the change to the Branch_4_2.
Committed also to Branch_5_x, thanks!
Still, it is not clear to me how to get the testsuite running with an IPV6 address. Even if I specify JNDI url using @ syntax (node0.jndi.url=jnp://::1@1099) lots of test cases are just ignoring this property and assuming jnp://$HOST:$PORT syntax. As far as I understand, it would be required to:
a) add support for standard IPV6 url in form: jnp://[$IPV6_ADDR]:$PORT
b) fix those test cases