Skip to content

Use TypeScanner to scan for initial entities #1284

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.

Sign up for GitHub

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

Jump to bottom
Closed
mp911de opened this issue Jul 6, 2022 · 0 comments
Closed

Use TypeScanner to scan for initial entities #1284

mp911de opened this issue Jul 6, 2022 · 0 comments
Labels
type: enhancement A general enhancement
Milestone
4.0 M6 (2022.0.0)

Comments

@mp911de
Copy link
Member

mp911de commented Jul 6, 2022

With our AOT efforts, we introduced TypeScanner as general abstraction for type scanning to avoid store-specific implementations. We should switch to TypeScanner instead of using ClassPathScanningCandidateComponentProvider directly.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jul 6, 2022
@schauder schauder added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Jul 11, 2022
@mp911de mp911de added this to the 4.0 M6 (2022.0.0) milestone Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement A general enhancement
Projects
None yet
Milestone
4.0 M6 (2022.0.0)
Development

No branches or pull requests
3 participants
@schauder @mp911de @spring-projects-issues