spring-cloud / spring-cloud/spring-cloud-netflix
Why isn't spring-cloud-netflix using AutoConfigurationPackages as an input for component scan ?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
I was hoping to create an spring boot starter having an AutoConfiguration annotated with @EnableFeignClients and naively hoping it would scan automatically packages in my application for @FeignClient annotated classes. While investigating I read a lot of spring-boot/spring-cloud source to understand how these components work/are implemented and found out that spring-cloud was just not using auto configuration packages.
Is there any reason why spring-cloud isn't making use of AutoConfigurationPackages ? Could it be possible to have it implemented ? Thanks for your feedback.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how @EnableFeignClients discovers @FeignClient classes and compare that path with Spring Boot's AutoConfigurationPackages behavior. Read the relevant Spring Cloud Netflix and Spring Boot source around these entry points, then determine whether an auto-configuration package can be used without breaking existing package-selection options. Done means the proposed starter behavior is implemented and covered by tests for automatic application-package scanning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100