Declare 4.25 M1

[SDawley]

Declare 4.25 M1

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

Current Candidate

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

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20220706-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/I20220706-1800

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

---

Deadlines:

• Friday, 2022-July-8, around 1 AM (Eastern): deadline for sign-off (or, by then, comment in this issue when you expect to sign-off).
• Friday, 2022-July-8, around 3 AM (Eastern): promote approved build to S-4.25M1-*, 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

[noopur2507]

Go from JDT UI.

Intermittent SaveParticipantTest failures are captured in eclipse-jdt/eclipse.jdt.ui#79.

[jarthana]

Go from JDT Core.
The known and transient failures are being tracked by https://bugs.eclipse.org/bugs/show_bug.cgi?id=565083

[niraj-modi]

Go from SWT.
Failing browser JUnits are tracked by:

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

[SarikaSinha]

Go from
Platform

• Ant
• Debug

JDT

• Debug

[ktatavarthi]

Go from Platform UI

The Windows(6) failures are captured by

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

The Mac(3) test failures are captured by

• org.eclipse.search.tests.filesearch.PositionTrackerTest fails randomly eclipse.platform.ui#882
• [Tests] ProgressViewTests.testItemOrder is flaky  eclipse.platform.ui#195

The linux(3) test failure is captured by

• [TEST] Intermittent test failures in FileBufferFunctions.test6 on Windows/ Linux  eclipse.platform.text#11
• [Test] org.eclipse.ui.tests.navigator.resources.NestedResourcesTests.testProjectHierarchy fails on linux intermittently eclipse.platform.ui#196
• [Test] org.eclipse.e4.ui.tests.css.swt.CTabItemTest.testFontBold fails intermittently in the I-build eclipse.platform.ui#197

[vik-chand]

Go from PDE

pde.build error is tracked by

• testBug206679_247198 fails since update to jetty 10.0.11 eclipse-pde/eclipse.pde#201

The failures on pde.ui only on 1 platform looks intermittent.

[iloveeclipse]

I see following issue with M1 that could be critical for some consumers: eclipse-platform/eclipse.platform.releng#69.

We see it in our product build that runs "offline" and doesn't pull any additional packages from Internet as maven/tycho it usually does.

• With "usual" p2 / maven/tycho builds the target platform will end up containing two different com.ibm.icu bundles - bad one from SDK (67.1 version from which PDE & equinox can't resolve versioned packages) and good one from some p2 update sites (com.ibm.icu 67.1.0.v20200706-1749). Later wins because it has qualifier and therefore it "usually" works.
• With the build that is restricted in the available update sites (or update sites not resolving to "good" com.ibm.icu 67.1.0.v20200706-1749) the resulting platform will fail to resolve com.ibm.icu packages if the application bundle specified a (valid) version range on any of com.ibm.icu packages, like GEF or Webtools that do.