If our understanding is correct,
the following output from our Jenkins build,
running on SSH Slave and Docker cloud,
reveals that Maven extensions under /lib/ext folder are not considered
This felt similar to Maven non-interactive mode (batch) prevent's project extensions loading
However, we have proven that the relevant Docker image is equipped with the Maven extensions,
by running a Docker container from it and the relevant Maven commands successfully, with the SmartBuilder and Multithreaded Build Logging extensions being used and either with or without interactive mode enabled.
However, when we run the same through a Jenkins job of Maven nature,
Maven falls back to standard mode:
Use of Maven extensions file didn't work either.
Consequently, we cannot take full advantage of Maven parallel builds.
This is most certainly related to a Maven Integration Plugin behavior.