Skip to content
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

Change autoconfiguration from one module into multiple #2269

Open
markpollack opened this issue Feb 18, 2025 · 1 comment
Open

Change autoconfiguration from one module into multiple #2269

markpollack opened this issue Feb 18, 2025 · 1 comment
Assignees
Milestone

Comments

@markpollack
Copy link
Member

We need to avoid conflicting versions by having one module for autoconfiguration as client libraries use libraries that are known to cause issues (grpc, guava, etc). To avoid this we should break up the current one module for auto-configuration into finer grained autoconfiguration dependencies. This work as started for the MCP support under the auto-configurations directory.

The starters that pick up autononfiguration deps will need to be change, but overall there should be no impact to uses who are picking up starter dependencies. It is an internal refactoring.

@ilayaperumalg
Copy link
Member

PR for chat client and models: #2289

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants