ammachado opened a new pull request, #24143:
URL: https://github.com/apache/camel/pull/24143
# Description
Adds automated test coverage for `camel-test-infra-jaeger` and hardens the
module
so it is production-ready for use by component integration tests.
Changes:
- **`JaegerRemoteInfraServiceTest`** (unit): covers `host()` fail-fast
behaviour,
default/override port resolution, and URL formatting for all three
endpoints
(OTLP gRPC, OTLP HTTP, Query UI). No Docker required.
- **`JaegerServiceIT`** (integration): spins up the Jaeger Testcontainers
service
via `JaegerServiceFactory`, sends real OTLP spans over both the HTTP and
gRPC
collectors, then queries the Jaeger API to confirm the traces landed. Uses
Awaitility instead of `Thread.sleep` for the polling assertion. Gated
behind
`mvn verify -Djaeger-it-test` so it does not run in the default CI build.
- **`JaegerRemoteInfraService.host()`**: changed from returning `null`
silently
to throwing `IllegalStateException` with an actionable message when the
required
system property is not set.
- **Javadoc `@since 4.21`** added to all public types and new public methods
in
the module, per project convention.
- Minor Javadoc improvement on `JaegerContainer.initContainer()` and
`JaegerInfraService.collectorGrpcEndpoint()` (clarifying the OTel-required
`http://` scheme).
# Target
- [x] I checked that the commit is targeting the correct branch (Camel 4
uses the `main` branch)
# Tracking
- [x] If this is a large change, bug fix, or code improvement, I checked
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for
the change (usually before you start working on it).
JIRA: https://issues.apache.org/jira/browse/CAMEL-23711
# Apache Camel coding standards and style
- [x] I checked that each commit in the pull request has a meaningful
subject line and body.
- [x] I have run `mvn clean install -DskipTests` locally from root folder
and I have committed all auto-generated changes.
_Claude Code on behalf of Adriano Machado_
--
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]