Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.eclipse.core.resources; singleton:=true
Bundle-Version: 3.22.100.qualifier
Bundle-Version: 3.22.200.qualifier
Bundle-Activator: org.eclipse.core.resources.ResourcesPlugin
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
/*******************************************************************************
* Copyright (c) 2000, 2023 IBM Corporation and others.
* Copyright (c) 2000, 2025 IBM Corporation and others.
*
* This program and the accompanying materials
* are made available under the terms of the Eclipse Public License 2.0
Expand Down Expand Up @@ -1188,7 +1188,7 @@ class InternalMonitorWrapper extends ProgressMonitorWrapper {
private boolean ignoreCancel;

public InternalMonitorWrapper(IProgressMonitor monitor) {
super(SubMonitor.convert(monitor));
super(Policy.monitorFor(monitor));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that Policy.monitorFor

public static IProgressMonitor monitorFor(IProgressMonitor monitor) {
return monitor == null ? new NullProgressMonitor() : monitor;
}

and IProgressMonitor.nullSafe(...)

static IProgressMonitor nullSafe(IProgressMonitor monitor) {
    if (monitor == null) {
        return new NullProgressMonitor();
    }
    return monitor;
}

are functionally identical. It probably makes sense to get rid of the former altogether...

}

public void ignoreCancelState(boolean ignore) {
Expand Down
Loading