Intellij Incorrectly Saying No Beans of Type Found for Autowired Repository

java

intellij

spring-data-plugin

spring-boot

byNikita Barsukov·Oct 12, 2024

Activate IntelliJ's annotation processing; Settings > Build > Compiler > Annotation Processors > Enable. Make sure @ComponentScan or @SpringBootApplication covers your repository package. Adjust IntelliJ's Spring facet configuration: Project Structure > Modules > Spring. Your repository should extend JpaRepository or CrudRepository and be within Spring's scan range.

If the issue remains, re-index your project: Invalidate Caches / Restart.

@SpringBootApplication
public class YourApp {
  // ...
}

public interface YourRepo extends JpaRepository<Entity, Long> { } //Keep holding on Entity! You've got this!

Breaking Down Composite Annotations

IntelliJ is packed with intelligent inspections but may stumble recognizing beans when using composite annotations such as @SpringBootApplication. Breaking it down into individual ones (@Configuration, @EnableAutoConfiguration,@ComponentScan) could increase the visibility for IntelliJ.

Intelligently Activating IntelliJ's Spring Data Plugin

Verify that the Spring Data plugin is enabled in IntelliJ. Navigate to Settings/Preferences > Plugins and ensure that the Spring Data plugin is enabled and is compatible with your IntelliJ version.

Steering Clear of Compatibility Issues

Make sure your IntelliJ IDEA version and Spring Data plugin are compatible. You may need some adjustments to your IntelliJ IDEA or the plugin itself. If you're using the Ultimate version, do check your Spring facet configurations. IntelliJ juggling too many facets? That’s one facet too many!

Reducing IntelliJ's Overenthusiastic Inspections

Reduce false error alerts with Severity settings found at Settings > Editor > Inspections. Adjust these settings to lower the frequency of error prompts, but remember, this is not the ultimate fix, just a temporary solution.

Package Scanning Basics

Correctly configuring the base packages is crucial. If you’re using @SpringBootApplication(scanBasePackages = "your.package"), ensure the base package path matches with your project's actual package structure. This also applies to @ComponentScan if paths are specified directly.

Direct Package Indication - A Quick Remedy

Desperate times call for desperate measures. Indicate your repository package explicitly in configuration if IntelliJ still fails to play nice:

@ComponentScan(basePackages = "com.example.repositories")

When All Else Fails - Report

IntelliJ not behaving? Might be a bug. Don't panic! Report the issue on YouTrack, provide a link to the community. Furnish your report with screenshots or visual aids. More the merrier!

explain-codes / Java / Intellij Incorrectly Saying No Beans of Type Found for Autowired Repository

Linked

Re-run Spring Boot Configuration Annotation Processor to update generated metadata



Intellij IDEA Java classes not auto compiling on save



Error: Could not find or load main class in IntelliJ IDE



Lombok annotations do not compile under Intellij IDEA



Can't compile project when I'm using Lombok under IntelliJ IDEA

