Update e4.40 and eStaging targets for 2026-06 RC1

[arfio]

What it does

Update e4.40 and eStaging targets for 2026-06 RC1

How to test

Build Trace Compass with staging or e4.40

Follow-ups

N/A

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the instructions in this template

Summary by CodeRabbit

• Chores
  • Updated build target platform configurations with upgraded dependencies, including Java runtime (21.0.11), CDT build tools, Jakarta annotations API, Mortbay JSP, Orbit aggregation, and EMF builds to stable and release candidate versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Both tracecompass-e4.40.target and tracecompass-eStaging.target are updated to reference newer, stable versions of their p2 repository sources and installable unit dependencies, including JRE 21.0.11, CDT rc1 build, updated library versions, and release versions of Orbit, Eclipse 4.40, and EMF.

Changes

Target Platform Dependency Updates

Layer / File(s)	Summary
JRE Runtime Update releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target, releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target	JustJ OpenJDK repository location is bumped from 21.0.10 to 21.0.11 in both target definitions.
CDT Build Repository Update releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target, releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target	CDT build repository is switched from milestone cdt-12.5.0-m2 to release candidate cdt-12.5.0-rc1 across both targets.
Library Dependency Versions releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target, releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target	jakarta.annotation-api is upgraded from 1.3.5 to 2.1.1, and org.mortbay.jasper.mortbay-apache-jsp is bumped from 9.0.111 to 9.0.118 in both targets.
Eclipse Ecosystem Repositories releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target, releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target	Orbit aggregation repository, Eclipse 4.40 I-builds repository, and EMF repository URLs are updated from milestone snapshots to stable release versions: Orbit to 4.40.0, Eclipse to I20260528-0011, and EMF to release/2.46.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• eclipse-tracecompass/org.eclipse.tracecompass#401: Both PRs update the same releng target platform XMLs by changing Orbit and Eclipse 4.40 I-build repository URLs.
• eclipse-tracecompass/org.eclipse.tracecompass#393: Both PRs modify the same Eclipse .target metadata files, updating repository URLs and unit versions in tracecompass-e4.40.target and tracecompass-eStaging.target.
• eclipse-tracecompass/org.eclipse.tracecompass#388: Both PRs adjust Eclipse target-platform versioning/selection in releng builds, though this PR bumps target definition URLs while the related PR switches the default build target.

Suggested reviewers

• MatthewKhouzam
• bhufmann

Poem

🐰 Dependencies flutter and shift,
From milestones to releases swift,
JRE now twenty-one-dot-oh-eleven bright,
CDT candidates gleam in the light,
A version refresh, so tidy and right! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating Eclipse target platform definitions for both e4.40 and eStaging configurations for the 2026-06 RC1 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target`:
- Around line 29-30: Remove the duplicate <unit id="jakarta.annotation-api">
entry that pins version 1.3.5 and keep only the newer <unit
id="jakarta.annotation-api" version="2.1.1"/> declaration; edit the target files
where both entries appear (tracecompass-e4.40.target and
tracecompass-eStaging.target) and delete the line with version="1.3.5" so only
the version="2.1.1" unit remains.

In `@releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target`:
- Around line 29-30: The target pins the same IU twice: <unit
id="jakarta.annotation-api" version="1.3.5"/> and <unit
id="jakarta.annotation-api" version="2.1.1"/>; remove the stale <unit
id="jakarta.annotation-api" version="1.3.5"/> entry and leave only the <unit
id="jakarta.annotation-api" version="2.1.1"/> unit so the target-definition has
a single, unambiguous pin for jakarta.annotation-api.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f31cb6a8-30e3-4cd7-9d88-92c5864d2a00

📥 Commits

Reviewing files that changed from the base of the PR and between b56dba4 and cecbe19.

📒 Files selected for processing (2)

• releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target
• releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target