zbendhiba opened a new pull request, #25276:
URL: https://github.com/apache/camel/pull/25276
## Why remove instead of deprecate?
`camel-spring-ai-tools` was a consumer-only component. No producer. Its only
job was registering Camel routes as Spring AI `ToolCallback` objects into
`CamelToolExecutorCache`. Then `spring-ai-chat` would read from that cache.
Step 3 already changed `spring-ai-chat` to use `AiToolRegistry` instead.
Nothing reads from `CamelToolExecutorCache` anymore. The component is dead in
4.22.
Deprecating it would leave a component that silently drops tool
registrations. Users would see no errors but tools would stop working. A clean
removal with a clear upgrade guide is more honest than a silent no-op.
This is different from `camel-langchain4j-tools` (deprecated in Step 4).
## Summary
- Remove the `camel-spring-ai-tools` module
- Remove from BOM, parent, catalog, coverage, and MojoHelper
- Update upgrade guide: component "has been removed"
- Generated files (DSL, catalog, SBOM, nav) cleaned up by the build
## Migration
Replace `spring-ai-tools:` consumer routes with `ai-tool:`:
```java
// Before
from("spring-ai-tools:weather?tags=weather&description=Get
weather¶meter.city=string")
// After
from("ai-tool:weather?tags=weather&description=Get
weather¶meter.city=string")
```
Add camel-ai-tool dependency. Remove camel-spring-ai-tools.
## Roadmap
- [x] Step 1: Create the new camel-ai-tool module - PR
https://github.com/apache/camel/pull/24473
- [x] Step 2: Wire camel-langchain4j-agent producer to AiToolRegistry - PR
https://github.com/apache/camel/pull/24988
- [x] Step 3: Wire camel-spring-ai-chat producer to AiToolRegistry - PR
https://github.com/apache/camel/pull/24862
- [ ] Step 4: Deprecate camel-langchain4j-tools
- [x] Step 5: Remove camel-spring-ai-tools (this PR)
- [ ] Step 6: camel-ollama-chat tool-calling via AiToolRegistry
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]