Add Java 25 devcontainer and SDKMAN setup documentation

[Copilot]

Description

Adds devcontainer configuration and SDKMAN instructions for Java 25 setup to streamline contributor onboarding.

Changes

.github/copilot-instructions.md:

• Updated Java requirement to 25
• Added SDKMAN workflow with pinned identifier example (25.0.1-tem)
• Noted identifiers vary by platform—contributors should run sdk list java to find their specific version
• Added devcontainer setup section referencing the configuration file

.devcontainer/devcontainer.json (new):

• Uses official DevContainers Java feature for Java 25
• Includes SDKMAN feature for manual version management
• Fallback postCreateCommand attempts pinned Temurin install (|| true ensures container builds regardless)
• Pre-configures VS Code Java extensions

README.md:

• Updated Java requirement from "Java 17 or newer" to "Java 25"

Example Setup

Contributors can now use SDKMAN:

sdk list java | grep 25
sdk install java 25.0.1-tem  # Platform-specific identifier
sdk default java 25.0.1-tem

Or simply open the repo in Codespaces/devcontainer—Java 25 configures automatically.

Checklist:

• Public methods are documented
• Public methods are tested
• New and existing tests pass when run locally
• There are no new warnings or errors

Original prompt

Update .github/copilot-instructions.md and add a devcontainer configuration so contributors can reliably use Java 25 in local GitHub workspaces/devcontainers.

Changes to make:

1. Modify .github/copilot-instructions.md (existing file) to:

   • Keep the Technology Stack Java 25 requirement.
   • Add a short, explicit SDKMAN workflow that demonstrates how to pin a specific JVM identifier instead of relying on unspecified defaults. Include guidance to run sdk list java to find the exact identifier for the developer's platform, and give an example using a Temurin 25 identifier (example: 25.0.1-tem) while noting identifiers vary by OS/arch.
   • Add a new section showing a devcontainer snippet to set up Java 25 automatically for Codespaces/devcontainer users, with a short explanation and a sample JSON snippet.

   The updated markdown should be a clear, copy-pastable set of instructions. Use the existing file at .github/copilot-instructions.md as the base. Include the example devcontainer snippet inline in the markdown.

2. Add a new file .devcontainer/devcontainer.json that explicitly requests Java 25 using the devcontainers features and provides a fallback postCreateCommand that attempts to install a pinned SDKMAN identifier. The file contents should be:

{
"name": "xapi-java (Java 25)",
"image": "mcr.microsoft.com/devcontainers/base:latest",
"features": {
"ghcr.io/devcontainers/features/java:2": {
"version": "25"
},
"ghcr.io/devcontainers/features/sdkman:1": {}
},
"postCreateCommand": "sdk install java 25.0.1-tem || true",
"customizations": {
"vscode": {
"extensions": [
"vscjava.vscode-java-pack",
"redhat.java"
]
}
}
}

Notes and rationale to include in the PR description/problem statement:

• SDKMAN identifiers vary by OS and CPU architecture (see sdk list java). Pinning a concrete example helps reproducibility but developers should run sdk list java and replace the example identifier with the one that matches their platform when necessary.
• The devcontainer feature uses the official devcontainers Java feature to install Java 25; the postCreateCommand attempts a conservative SDKMAN install as an extra fallback for manual workspaces.

Make the PR branch name something like: ci/java25-devcontainer and create the PR with a concise title and description capturing the above.

Files to edit/create and their paths:

• .github/copilot-instructions.md (update: add SDKMAN pinned example and devcontainer snippet)
• .devcontainer/devcontainer.json (new file)

Please create a pull request in the BerryCloud/xapi-java repository that implements these changes. Do not assign the PR; use an informative commit message and PR title.

This pull request was created as a result of the following prompt from Copilot chat.

Update .github/copilot-instructions.md and add a devcontainer configuration so contributors can reliably use Java 25 in local GitHub workspaces/devcontainers.

Changes to make:

1. Modify .github/copilot-instructions.md (existing file) to:

   • Keep the Technology Stack Java 25 requirement.
   • Add a short, explicit SDKMAN workflow that demonstrates how to pin a specific JVM identifier instead of relying on unspecified defaults. Include guidance to run sdk list java to find the exact identifier for the developer's platform, and give an example using a Temurin 25 identifier (example: 25.0.1-tem) while noting identifiers vary by OS/arch.
   • Add a new section showing a devcontainer snippet to set up Java 25 automatically for Codespaces/devcontainer users, with a short explanation and a sample JSON snippet.

   The updated markdown should be a clear, copy-pastable set of instructions. Use the existing file at .github/copilot-instructions.md as the base. Include the example devcontainer snippet inline in the markdown.

2. Add a new file .devcontainer/devcontainer.json that explicitly requests Java 25 using the devcontainers features and provides a fallback postCreateCommand that attempts to install a pinned SDKMAN identifier. The file contents should be:

{
"name": "xapi-java (Java 25)",
"image": "mcr.microsoft.com/devcontainers/base:latest",
"features": {
"ghcr.io/devcontainers/features/java:2": {
"version": "25"
},
"ghcr.io/devcontainers/features/sdkman:1": {}
},
"postCreateCommand": "sdk install java 25.0.1-tem || true",
"customizations": {
"vscode": {
"extensions": [
"vscjava.vscode-java-pack",
"redhat.java"
]
}
}
}

Notes and rationale to include in the PR description/problem statement:

• SDKMAN identifiers vary by OS and CPU architecture (see sdk list java). Pinning a concrete example helps reproducibility but developers should run sdk list java and replace the example identifier with the one that matches their platform when necessary.
• The devcontainer feature uses the official devcontainers Java feature to install Java 25; the postCreateCommand attempts a conservative SDKMAN install as an extra fallback for manual workspaces.

Make the PR branch name something like: ci/java25-devcontainer and create the PR with a concise title and description capturing the above.

Files to edit/create and their paths:

• .github/copilot-instructions.md (update: add SDKMAN pinned example and devcontainer snippet)
• .devcontainer/devcontainer.json (new file)

Please create a pull request in the BerryCloud/xapi-java repository that implements these changes. Do not assign the PR; use an informative commit message and PR title.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[thomasturrell]

@copilot remove example section

[Copilot]

Done. Removed the example section in commit d3e3463.

[thomasturrell]

@copilot see comments also update project readme with correct java version

[Copilot]

@copilot see comments also update project readme with correct java version

Updated README.md with Java 25 requirement in commit b3cf6f1.

[thomasturrell]

updated in PR #379