Fix improper use of sub-monitor in Workspace.write()

SubMonitor.split() should not be called without providing any ticks,
which might happen if the map of to-be-created files is empty. Given
that the called method is private and only called from this method, the
empty check can simply be pulled up.

Author: ptziegler

resources/bundles/org.eclipse.core.resources/src/org/eclipse/core/internal/resources/Workspace.java

@@ -1,5 +1,5 @@
 /*******************************************************************************
- * Copyright (c) 2000, 2022 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
@@ -2829,15 +2829,14 @@ public void write(Map<IFile, byte[]> contentMap, boolean force, boolean derived,
 			byte[] content = e.getValue();
 			file.setContents(content, updateFlags, subMon.split(1));
 		}
-		createMultiple(filesToCreate, createFlags, subMon.split(filesToCreate.size()), executorService);
+		if (!filesToCreate.isEmpty()) {
+			createMultiple(filesToCreate, createFlags, subMon.split(filesToCreate.size()), executorService);
+		}
 	}
 
 	/** @see File#create(byte[], int, IProgressMonitor) **/
 	private void createMultiple(ConcurrentMap<File, byte[]> filesToCreate, int updateFlags, IProgressMonitor monitor,
 			ExecutorService executorService) throws CoreException {
-		if (filesToCreate.isEmpty()) {
-			return;
-		}
 		Set<File> files = filesToCreate.keySet();
 		for (File file : files) {
 			file.checkValidPath(file.path, IResource.FILE, true);