If an user uses EAP 8 Builder and runtime images to create an application image with a 3rd party Jar, they will use the S2I env vars to configure the provisioning capabilities of EAP 8 (as explained in [1]).

The S2I assemble script logs warnings if these env vars are configured:

WARN You have activated legacy s2i workflow by setting GALLEON_PROVISION_FEATURE_PACKS or GALLEON_USE_LOCAL_FILE env variable.
WARN This support is deprecated and will be removed in a future release. Provision and configure your server during s2i from your pom.xml file by using the dedicated Maven plugin. 

The intent was to have users configure the eap-maven-plugin to handle the provisioning capabilities instead or relying with S2I.
However we now want to support such valid use cases and let users configure these env vars to create images without having access to their application source code.
This makes these warnings "scary" and misleading as this is a valid use case we want to support with EAP 8.

These logs should be changed to make them more informative:

INFO You have activated legacy s2i workflow by setting GALLEON_PROVISION_FEATURE_PACKS or GALLEON_USE_LOCAL_FILE env variable.

[1] https://access.redhat.com/solutions/7017802