Croway opened a new pull request, #1978:
URL: https://github.com/apache/camel-spring-boot/pull/1978

   ## Summary
   
   Adds the Spring Boot starter for every Camel core component that didn't have 
one yet, checked against `apache/camel` upstream/main:
   
   - `camel-camunda-starter` — Camunda 8 Orchestration Clusters
   - `camel-event-starter` — subscribing to Camel internal events
   - `camel-shell-starter` — interactive JLine shell endpoint
   - `camel-spiffe-starter` — SPIFFE Workload Identity
   - `camel-state-store-starter` — pluggable key-value store operations
   - `camel-ai-resource-starter` — route-based read-only AI resources
   - `camel-pgvector-starter` — PostgreSQL pgvector vector database
   - `camel-langchain4j-ingest-starter` — LangChain4j document ingestion
   - `camel-ibm-watsonx-data-starter` — IBM watsonx.data lakehouse
   
   Each is its own commit: generated with `starter-create`, then built to 
regenerate the auto-configuration, `@ConfigurationProperties`, catalog entries, 
docs page/nav, and dependencies BOM entry, plus a smoke test asserting 
`camel.component.<name>.*` properties are correctly bound onto the component 
bean.
   
   Two smoke tests are worth calling out:
   - `camel-shell-starter`'s test resolves the component with 
`autoStart=false`, since `ShellComponent.doStart()` opens a real system 
terminal and must not run in a headless test.
   - The others start the component normally; none of their `doStart()` 
implementations make eager network/IO calls (verified by inspection), so 
property binding can be asserted safely without live external services.
   
   ## Test plan
   
   - [x] `mvn verify` passes for each new starter module individually
   - [x] `mvn verify` passes for all 9 new starter modules built together in 
one reactor run (no cross-module conflicts in the shared catalog/BOM/docs files)


-- 
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]

Reply via email to