Phillip Webb

Looks like we both got there at the same time!

@spencergibb take a look at `ServerPortInfoApplicationContextInitializer` for an example. The context name is always management I think. See [ManagementContextAutoConfiguration](https://github.com/spring-projects/spring-boot/blob/23a923d1894d0bb11a7554be74f4674bb4317978/spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/web/server/ManagementContextAutoConfiguration.java#L147)

Spring Boot is just delegating to `MetadataNamingStrategy` so I think it would be a Framework problem.

@mp911de I think so, but it's likely to be risky so I'd rather not do it in the existing releases. I've opened https://github.com/spring-projects/spring-boot/issues/28849

We'll look at detecting this, but we'll also want to offer a property to opt-out in case the user has a different JVM.

I'm not sure we can skip running `ApplicationContextInitializers` in AOT mode. In this example, the initializer is registering a bean but it's entirely possible that an initializer does something else...

It's probably going to be pretty hard to make `@ConditionalOnProperty` look at the default values of the `@ConfigurationProperties`. As you said, currently the bind occurs after the bean has been...

Yeah, lets keep this open and take a look when the 1.2 bugs die down. It might be possible to update `@ConditionalOnProperty` to direct inspect the class that it's on...

@albertocavalcante The issue is open an in the "General Backlog" milestone which means we're still considering it. Having said that, this we have a number of other tasks that are...

Some history about why we added this restriction can be found in #22963. If we remove it then we're likely to break folks that have comments such as: ``` #----...