As we work on Jakarta EE 11 we will begin to see components that require SE 17 (and perhaps SE 21 if the Jakarta EE platform group's decision to baseline on 17 and not 21 is reversed.) So, to compile against these components we will need to require a compiler at SE 17 level or later.

But the WildFly code itself does not require language features or SE APIs beyond the SE 11 level, so when compiling with 17+, we should restrict the source level to 11 and build SE 11 binaries. This will allow the greatest flexibility in using our artifacts in different environments (e.g. in an EE 10 server.)

To execute the maven 'deploy' phase, the compiler must be at SE 17 level. That is we lock down the level, same as we currently do where we lock it down to SE 11 only.