Upgrade to Java 17 (LTS)

[devin-ai-integration]

Summary

Upgrades this Maven project from Java 9 to Java 17 (LTS) with the minimal diff. Only pom.xml changes — no source changes were needed.

• Language level 9 → 17: replaced the maven-compiler-plugin <source>1.9</source>/<target>1.9</target> with <release>17</release>.
• Bumped maven-compiler-plugin 3.1 → 3.13.0 (3.1 cannot target JDK 17).
• JMH (jmh-core/jmh-generator-annprocess 1.17.4), JUnit 4.11, and maven-shade-plugin were left unchanged — they compile and run fine under JDK 17.

 <artifactId>maven-compiler-plugin</artifactId>
-<version>3.1</version>
+<version>3.13.0</version>
 <configuration>
-  <source>1.9</source>
-  <target>1.9</target>
+  <release>17</release>
 </configuration>

Validation

• mvn clean verify succeeds on JDK 17 (Temurin/OpenJDK 17.0.19).
• Compiled bytecode is Java 17 (major version: 61).
• No CI config present in the repo, so none changed.
• Ran a representative example main class (lambdasinaction.chap4.StreamBasic) on JDK 17 successfully.

Residual risks

• This repo has no src/test, so a green build is not proof of full runtime correctness. Validation was limited to compilation, the JMH/shade packaging, and running a sample main class.

Link to Devin session: https://app.devin.ai/sessions/2a0cfce02fe34a248e76dd79872dc22c
Requested by: @vibhaseshadri-cognition

---

Devin Review

Status	Commit
⚪ Not started	—

Run Devin Review

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring