I am in context where an embedded server version 12.x is started for a version 11 (or 10) of wildfly-core.

This occurs with Bootable JAR maven plugin that depends on 12.x for its CLI support.

This can also happen using CLI shaded client JAR of WildFly 20 to start an embedded server for a WildFly 19 installation.

The problem has been introduced by https://issues.redhat.com/browse/WFCORE-4893 that defined a new method not supported by older versions.

The EmbeddedServer should be able to fallback to legacy logic if the new method is not present.