BootstrapApplicationListener overrides custom environment

The BootstrapApplicationListener defines its own environment when it creates the Spring Application using the Spring Builder. This overrides the custom environment we have provided for our application during the initial application run invocation.

We specify a custom environment class for our application for reasons specified in this issue

The BootstrapApplicationListener should provide a way for applications to specify their own environment class instead of defining its bootstrapEnvironment using new StandardEnvironment().

private ConfigurableApplicationContext bootstrapServiceContext( ConfigurableEnvironment environment, final SpringApplication application, String configName) { **StandardEnvironment bootstrapEnvironment = new StandardEnvironment();** MutablePropertySources bootstrapProperties = bootstrapEnvironment .getPropertySources(); for (PropertySource<?> source : bootstrapProperties) { bootstrapProperties.remove(source.getName()); }

Start by reading BootstrapApplicationListener, especially bootstrapServiceContext, and trace how SpringApplication creates and receives its environment. Confirm the behavior with the existing bootstrap-related tests, then define and verify a way for the application's custom environment class to remain in effect during the initial bootstrap run.