You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering why we have to wait to see which profile is loaded in log.
The problem is:
In the Spring Boot application, I can even see my profile, on the first line of the log.
But in Quarkus, After loading everything, and ruining TestContainers, and Flyway scripts,... eventually, I can see my profile.
@ApplicationScopedclassStarter
{
@InjectLoggerLOGGER;
voidonStart(@ObservesStartupEventev)
{
LOGGER.info("#The application is starting... ." + " Profile is: " + ProfileManager.getActiveProfile());
}
voidonStop(@ObservesShutdownEventev)
{
LOGGER.info("#The application is stopping...");
}
}
I used the above code to see, which profile is selected.
Quarkus log it after above code:
2023-03-29 16:29:34,715 INFO [io.quarkus] Profile test activated.
Implementation ideas
I expected there was a way can see which profile is selected in the first lines of the application log.
The text was updated successfully, but these errors were encountered:
Description
I was wondering why we have to wait to see which profile is loaded in log.
The problem is:
In the Spring Boot application, I can even see my profile, on the first line of the log.
But in Quarkus, After loading everything, and ruining TestContainers, and Flyway scripts,... eventually, I can see my profile.
I used the above code to see, which profile is selected.
Quarkus log it after above code:
2023-03-29 16:29:34,715 INFO [io.quarkus] Profile test activated.
Implementation ideas
I expected there was a way can see which profile is selected in the first lines of the application log.
The text was updated successfully, but these errors were encountered: