releng: add e4.40 and update eStaging targets for 2026-06 M1

[arfio]

What it does

releng: Add e4.40 and update eStaging targets for 2026-06 M1

How to test

Build with tracecompass-e4.40 target

Follow-ups

M2 - 04/24

Review checklist

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

Summary by CodeRabbit

• Chores
  • Added support for Eclipse 4.40 target platform.
  • Updated staging environment with latest versions of CDT, platform, WebTools, and EMF components.
  • Updated base target platform versioning.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates Eclipse P2 target definition files for Trace Compass: decrements the sequence number in e4.39 from 265 to 2, introduces a new e4.40 target file with Java 21 JRE and updated dependencies, and increments eStaging's sequence number while updating repository locations to newer milestone builds.

Changes

Cohort / File(s)	Summary
Sequence number updates releng/org.eclipse.tracecompass.target/tracecompass-e4.39.target, releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target	Updated sequenceNumber attribute in e4.39 from 265 to 2; incremented eStaging from 265 to 266.
New e4.40 target definition releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target	Added new target definition file with P2 repositories, installable units for CDT, SWTBot, foundational libraries, Orbit content, Eclipse IDE/PDE components, and Java 21 JRE configuration.
eStaging repository updates releng/org.eclipse.tracecompass.target/tracecompass-eStaging.target	Updated P2 repository locations: CDT (12.4.0→12.5.0-m1), Orbit (4.39.0 release→milestone), Eclipse platform (4.39→4.40-I builds), WebTools (R3.41.0→R3.42.0-M1), and EMF to latest milestone.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• releng: Build with tracecompass-e4.39 by default #388: Relates to switch in build target platform configuration where e4.39 and e4.40 targets are the primary build infrastructure.
• releng: 11.3.0 release #391: Modifies the same releng target definition artifacts across multiple target files.
• releng: update features for new dependencies, move new product, feature to staging #386: Updates to the same tracecompass-e4.39.target and tracecompass-eStaging.target repository configurations.

Suggested reviewers

• MatthewKhouzam
• bhufmann
• jonahgraham

Poem

🐰 A new target blooms with e4.40 in sight,
Sequence numbers dance, repositories shine bright,
Java 21 whispers, staging milestones align,
Eclipse platforms evolve, targets redesign,
Trace Compass bounds forward with targets so fine! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: adding the e4.40 target file and updating the eStaging target for the 2026-06 M1 milestone, which aligns with the actual modifications in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 the current code and only fix it if needed.

Inline comments:
In `@releng/org.eclipse.tracecompass.target/tracecompass-e4.39.target`:
- Line 1: The target XML's target element currently has sequenceNumber="2" which
breaks monotonic ordering; update the sequenceNumber attribute on the <target
name="tracecompass-e4.39" sequenceNumber="2"> element to sequenceNumber="266" so
the PDE target continues the sequence.

In `@releng/org.eclipse.tracecompass.target/tracecompass-e4.40.target`:
- Line 1: Add a build-helper-maven-plugin artifact entry in
releng/org.eclipse.tracecompass.target/pom.xml for the new target file: create
an <artifact> element matching the existing e4.20–e4.25 entries that references
file "tracecompass-e4.40.target" and sets classifier "tracecompass-e4.40" (same
groupId/artifactId/type as the other target entries) so the plugin publishes the
classifier and the target becomes available via ${target-platform}.

🪄 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: c293478f-11ad-41c9-91a7-e18c7173a041

📥 Commits

Reviewing files that changed from the base of the PR and between fa08339 and 95c651b.

📒 Files selected for processing (3)

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