-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Logging beans are missing during AOT processing #32483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I see the same problem on the JVM with AOT enabled. Looking at the generated code, there's no definition for the package org.springframework.boot.actuate.autoconfigure.logging;
import java.lang.Class;
import org.springframework.beans.factory.config.BeanDefinition;
import org.springframework.beans.factory.support.RootBeanDefinition;
/**
* Bean definitions for {@link LoggersEndpointAutoConfiguration}
*/
public class LoggersEndpointAutoConfiguration__BeanDefinitions {
/**
* Get the bean definition for 'loggersEndpointAutoConfiguration'
*/
public static BeanDefinition getLoggersEndpointAutoConfigurationBeanDefinition() {
Class<?> beanType = LoggersEndpointAutoConfiguration.class;
RootBeanDefinition beanDefinition = new RootBeanDefinition(beanType);
beanDefinition.setInstanceSupplier(LoggersEndpointAutoConfiguration::new);
return beanDefinition;
}
} It looks like the conditions didn't match when evaluated at build time. I suspect it's because the |
The |
Closed by 26eff5a. |
When running https://github.com/spring-projects/spring-aot-smoke-tests/tree/main/actuator-webmvc on the JVM,
http://localhost:8080/actuator/loggers
is accessible. On native, it is not and returns a 404.The text was updated successfully, but these errors were encountered: