Skip to content

Change autoconfiguration from one module into multiple #2269

@markpollack

Description

@markpollack

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.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions