WFLY-18324 introduce new user-name and password attributes and drop user-name and password elements in configuration. Although I understand the reasoning behind the need of introducing attributes, dropping the elements breaks the hard requirement for backward compatibility changes in new non-major releases (EAP 8.1 in this case). Would be possible to keep both ways (attributes and elements), so customers can use both of them? Or maybe adding some transformers? Now the EAP 8.0 configuration files wouldn't work with EAP 8.1.

Examples of configurations are here

If this jira will be rejected, we need to:

• mention this in a documentation
• prepare migration rules
• update creaper offline commands in wildfly-extras here