apupier opened a new pull request, #221:
URL: https://github.com/apache/camel-spring-boot-examples/pull/221

   ## Summary
   
   Java 17 support has been dropped in Camel core. This repository already 
builds on Java 21 (`javaVersion` in the root `pom.xml`, the CI workflows, 
`AGENTS.md`), so this PR only removes the leftover Java 17 references.
   
   JIRA: https://issues.apache.org/jira/browse/CAMEL-22996
   
   ## Changes
   
   One commit per change:
   
   1. **Use Java 21 base image for JKube builds**
      The root `pom.xml` set `jkube.generator.from` to 
`registry.access.redhat.com/ubi9/openjdk-17:latest`. It now uses 
`ubi9/openjdk-21:latest`, so container images built by the examples no longer 
run on a JDK older than the baseline. No module overrides this property.
   
   2. **Remove hardcoded Java 17 release from loggingtracer**
      `observation/loggingtracer` was the only module that set 
`maven.compiler.release` to 17. The property is removed.
   
   3. **Update README prerequisites to Java 21**
      `salesforce`, `genai-observability` and `aot-basic` (GraalVM download 
instructions) now say Java 21 instead of Java 17.
   
   ## Notes for reviewers
   
   - `observation/loggingtracer` has no `<parent>`, so it does not inherit 
`javaVersion` (21). Without the property, the compiler level falls back to the 
`maven-compiler-plugin` default. The module still compiles, but the classes are 
now Java 8 bytecode (class file major version 52). If you prefer Java 21 
bytecode there, the module can either get the `examples` parent or set the 
release explicitly. I can add that if you want it in this PR.
   - I left `azure/pom.xml` unchanged. It sets `maven.compiler.source/target` 
to 8, which is not a Java 17 reference, and the build passes.
   - A repo-wide search for Java 17 / JDK 17 / `openjdk-17` finds no remaining 
references.
   
   ## Testing
   
   On JDK 21.0.9 (Temurin):
   
   - `./mvnw -V --no-transfer-progress clean install -DskipTests`: BUILD 
SUCCESS, all 102 modules, including `loggingtracer`.
   - `./mvnw -V --no-transfer-progress test`: BUILD SUCCESS, no test failures.
   
   I did not build or run any container image with the new `openjdk-21` base 
image. I only confirmed that the image exists in the Red Hat catalog.
   
   ---
   _Claude Code on behalf of Aurélien Pupier_


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