Skip to content

Replace InfiniteSubProgressMonitor with SubMonitor in org.eclipse.team.core#2660

Merged
vogella merged 1 commit into
masterfrom
replace-infinite-sub-progress-monitor
Jun 12, 2026
Merged

Replace InfiniteSubProgressMonitor with SubMonitor in org.eclipse.team.core#2660
vogella merged 1 commit into
masterfrom
replace-infinite-sub-progress-monitor

Conversation

@vogella

@vogella vogella commented May 14, 2026

Copy link
Copy Markdown
Contributor

Planned for 4.41

InfiniteSubProgressMonitor was an internal class in org.eclipse.team.core that worked around the old SubProgressMonitor limitation of overshooting allocated parent ticks. SubMonitor's built-in proportional scaling handles this naturally, making the custom halving algorithm unnecessary.

This removes InfiniteSubProgressMonitor, the infiniteSubMonitorFor helper in Policy, and replaces the two call sites in BackgroundEventHandler and AbstractResourceVariantTree with direct SubMonitor usage.

@vogella vogella force-pushed the replace-infinite-sub-progress-monitor branch from f35d4ac to c75e9ff Compare May 14, 2026 04:09
@eclipse-platform-bot

Copy link
Copy Markdown
Contributor

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

team/bundles/org.eclipse.team.core/META-INF/MANIFEST.MF

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch
From 9d03eebeac4735b7bfb8f41a2ac6f4ed316d9cbb Mon Sep 17 00:00:00 2001
From: Eclipse Platform Bot <platform-bot@eclipse.org>
Date: Thu, 14 May 2026 04:14:58 +0000
Subject: [PATCH] Version bump(s) for 4.40 stream


diff --git a/team/bundles/org.eclipse.team.core/META-INF/MANIFEST.MF b/team/bundles/org.eclipse.team.core/META-INF/MANIFEST.MF
index 0a67c9ef3d..dddea179e5 100644
--- a/team/bundles/org.eclipse.team.core/META-INF/MANIFEST.MF
+++ b/team/bundles/org.eclipse.team.core/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %pluginName
 Bundle-SymbolicName: org.eclipse.team.core; singleton:=true
-Bundle-Version: 3.10.1000.qualifier
+Bundle-Version: 3.10.1100.qualifier
 Bundle-Activator: org.eclipse.team.internal.core.TeamPlugin
 Bundle-Vendor: %providerName
 Bundle-Localization: plugin
-- 
2.53.0

Further information are available in Common Build Issues - Missing version increments.

@github-actions

github-actions Bot commented May 14, 2026

Copy link
Copy Markdown
Contributor

Test Results

    54 files  ±0      54 suites  ±0   56m 6s ⏱️ + 1m 55s
 4 677 tests ±0   4 655 ✅ ±0   22 💤 ±0  0 ❌ ±0 
11 925 runs  ±0  11 772 ✅ ±0  153 💤 ±0  0 ❌ ±0 

Results for commit 2361c1e. ± Comparison against base commit bc1c7f1.

♻️ This comment has been updated with latest results.

@vogella vogella marked this pull request as ready for review June 11, 2026 16:41
@vogella vogella force-pushed the replace-infinite-sub-progress-monitor branch from aab9c6a to 15e24b6 Compare June 11, 2026 16:41
SubMonitor's proportional scaling handles the same use case as
InfiniteSubProgressMonitor without the custom halving algorithm.
The anonymous SubProgressMonitor subclass in SubscriberSyncInfoEventHandler
is replaced with ProgressMonitorWrapper, which allows the same
override-and-delegate pattern without subclassing the deprecated class.

Removes InfiniteSubProgressMonitor and the infiniteSubMonitorFor helper
in Policy since both are internal and unused after this change.
@vogella vogella force-pushed the replace-infinite-sub-progress-monitor branch from 15e24b6 to 2361c1e Compare June 12, 2026 13:14
@vogella vogella merged commit 89cdaca into master Jun 12, 2026
18 checks passed
@vogella vogella deleted the replace-infinite-sub-progress-monitor branch June 12, 2026 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants