Declare 4.25 RC2

[SDawley]

A "go" is needed from all the components below to declare this milestone.

Current Candidate

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20220831-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20220831-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.25-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.25-I-builds/I20220831-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20220831-1800

---

Deadlines:

• Friday, 2022-September-02, around 1 AM (Eastern): deadline for sign-off (or, by then, comment in this issue when you expect to sign-off).
• Friday, 2022-September-02, around 3 AM (Eastern): promote approved build to S-4.25RC2-*, contribute to simultaneous release repo, and announce to mailing lists.

Remember to investigate and document here any failing JUnit tests.

---

• Platform:

• • Resources
• • UI
• • Debug
• • Ant
• • SWT
• • Releng

• JDT:

• • Core
• • Debug
• • UI

• PDE

• Equinox

[sravanlakkimsetti]

Go from platform releng

[ktatavarthi]

Go from Platform UI
The Windows and Mac test failures are captured by the below issues

• No code mining updated when using Ctrl+End (was: CodeMiningTest are failing on Windows and Mac) eclipse.platform.text#34
• JUnit tests in org.eclipse.jface.text.tests.contentassist are failing on Windows and Mac eclipse.platform.ui#890
• org.eclipse.search.tests.filesearch.PositionTrackerTest fails randomly eclipse.platform.ui#882

[SarikaSinha]

Go from Platform Debug, Ant
JDT Debug
Test failures in JDT Debug are tracked by -

• OpenFromClipboardTests still randomly fail eclipse-jdt/eclipse.jdt.debug#28
• [Tests] Cannot connect to VM eclipse-jdt/eclipse.jdt.debug#116

[vik-chand]

Go from PDE.

Test failure (intermittent on 1 platform) tracked by

• Intermittent failures in WorkspaceModelManagerTest eclipse-pde/eclipse.pde#300

[noopur2507]

Go from JDT UI.

The intermittent test failure is tracked in

• Avoid random failures of SaveParticipantTest eclipse-jdt/eclipse.jdt.ui#79

[niraj-modi]

Go from SWT.
Failing browser JUnits are tracked by:

• Some of the browser test fail on different platforms eclipse.platform.swt#103

[jarthana]

Go from JDT Core.
For the new failure (which doesn't occur locally), I have raised
eclipse-jdt/eclipse.jdt.core#364