Skip to content

[spring framework 7] support bean registrars that are defined in libraries #1525

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

Open
martinlippert opened this issue Mar 24, 2025 · 0 comments
Assignees
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: spring index & symbols theme: validation type: enhancement
Milestone

Comments

@martinlippert
Copy link
Member

As described here:
spring-projects/spring-framework#21497 (comment)

We might arrive at the point where spring projects provide pre-defined bean registrars and users can basically opt-in by defining and importing a concrete specialization of the pre-defined registrar.

For the indexing that we do inside of the language server, this opens up a whole new area: looking into bean definitions from JAR files on the classpath instead of the source files of the projects only (as we do at the moment).

So we need a lot of groundwork for this to have a general mechanism in place that integrates spring index information from JAR files into the index that the language server creates from the source files (see #1524). Once we have that, we can work on taking bean registrars from libraries into account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: spring index & symbols theme: validation type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants