fix: Eagerly load DBSchedulerStarter (491) #492
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NicklasWallgren
changed the title
NicklasWallgren
force-pushed
the
491-eagerly-load-db-scheduler-starter
branch
from
39d792d
to
d751b37
Compare
NicklasWallgren
changed the title
kagkarlsson
approved these changes
May 28, 2024
|
🎉 This issue has been resolved in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief, plain english overview of your changes here
Excludes DbSchedulerStarter from being lazily initialized.
Fixes
The DbSchedulerStarter isn't created in a application where lazy initialization is enabled via
spring.main.lazy-initialization=true.Fixes: #491
Reminders
mvn spotless:applycc @kagkarlsson