chore: Update POM to Java 25 and rename artifactId/groupId

[kristinaxm]

This PR updates the Maven POM for the project.
Renamed groupId from org.example to org.juv25d
Renamed artifactId from JavaTemplate to JavaHttpServer
Updated maven.compiler.release to 25 for Java 25 compilation
Kept existing test dependencies (JUnit, Mockito, AssertJ) for testing

No other functionality is changed.

Branch: chore/update-pom-java25.

Closes #5

Summary by CodeRabbit

• Chores

  • Updated Java requirement to version 25.
  • Updated project coordinates and naming.

• Refactor

  • Adjusted internal package structure and namespaces across the codebase.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated Maven coordinates in pom.xml (groupId → org.juv25d, artifactId → JavaHttpServer) and bumped maven.compiler.release from 23 to 25. Aligned Java source and test files by changing package declarations from org.example to org.juv25d.

Changes

Cohort / File(s)	Summary
Maven Configuration pom.xml	Changed groupId to org.juv25d, artifactId to JavaHttpServer, and maven.compiler.release from 23 → 25.
Application Sources src/main/java/.../App.java, src/main/java/org/juv25d/SocketServer.java	Updated package declarations from org.example → org.juv25d. No logic changes; minor EOF newline addition.
Tests src/test/java/.../AppTest.java, src/test/java/.../AppIT.java	Updated package declarations from org.example → org.juv25d. Tests otherwise unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through pom and files with cheer,
Names rearranged, the path is clear,
From twenty-three to twenty-five we bound,
Packages aligned, no bugs were found,
A little thump — the build draws near!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: updating the POM to Java 25 and renaming Maven coordinates (artifactId/groupId).
Linked Issues check	✅ Passed	The PR directly addresses issue #5 by updating pom.xml with new Maven coordinates and Java 25 compiler configuration as required.
Out of Scope Changes check	✅ Passed	All changes are in-scope: package declarations updated to match new namespace, pom.xml configuration updated, and test files updated accordingly.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-pom-#5

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@pom.xml`:
- Around line 11-12: pom.xml sets maven.compiler.release to 25 but the repo
lacks any CI or toolchain configuration to guarantee JDK 25; update the CI
(e.g., .github/workflows) to use JDK 25 (actions/setup-java or equivalent) or
add a Maven toolchains.xml and corresponding <pluginManagement>/<plugin>
configuration so the build uses JDK 25, or alternatively lower
<maven.compiler.release> to a supported JDK; reference the
maven.compiler.release property in pom.xml and the repository CI workflow or a
new toolchains.xml when making the change.

🧹 Nitpick comments (1)

pom.xml (1)

7-8: Maven coordinates references are clean in docs, CI, and consuming modules.

No lingering references to the old Maven coordinates (org.example:JavaTemplate) were found in documentation, CI/CD configuration, or other pom.xml files. However, the Java source files still declare package org.example; — while these are not Maven coordinates, consider updating the package names to org.juv25d for consistency with the new groupId.

[fmazmz]

Great!
Make sure to update the folder name "example" to match the groupId -> "juv25d"

[fmazmz]

Fire!

[LinusWestling]

Speed of light development

[fmazmz]

@LinusWestling can you approve the new changes please so we can merge this!