What causes "Could not write fixed metadata to {}: {}" in apache/maven?

Fix ownership/permissions of the metadata file and its parent directories (chown -R $USER ~/.m2/repository or chmod -R u+w).

apache/maven · warning

Could not write fixed metadata to {}: {}

Error message

Could not write fixed metadata to {}: {}

What it means

Warning from DefaultRepositoryMetadataManager.fixTimestamp: after detecting and correcting a bad lastUpdated timestamp (see the companion warning), Maven tries to persist the repaired Metadata back to disk via MetadataStaxWriter, and the write fails with IOException or XMLStreamException. This branch logs the message WITH the exception because debug is enabled; the corrected state is then lost and the on-disk file keeps its old timestamps.

Source

Thrown at compat/maven-compat/src/main/java/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.java:318

                            .warn("The last updated timestamp in " + metadataFile + " refers to the future (now = "
                                    + now
                                    + ", lastUpdated = " + lastUpdated + "). Please verify that the clocks of all"
                                    + " deploying machines are reasonably synchronized.");
                    versioning.setLastUpdated(now);
                    changed = true;
                }
            }
        }

        if (changed) {
            getLogger().debug("Repairing metadata in " + metadataFile);

            try (OutputStream out = Files.newOutputStream(metadataFile.toPath())) {
                new MetadataStaxWriter().write(out, metadata.getDelegate());
            } catch (IOException | XMLStreamException e) {
                String msg = "Could not write fixed metadata to " + metadataFile + ": " + e.getMessage();
                if (getLogger().isDebugEnabled()) {
                    getLogger().warn(msg, e);
                } else {
                    getLogger().warn(msg);
                }
            }
        }
    }

    @Override
    public void resolveAlways(
            RepositoryMetadata metadata, ArtifactRepository localRepository, ArtifactRepository remoteRepository)
            throws RepositoryMetadataResolutionException {
        File file;
        try {
            file = getArtifactMetadataFromDeploymentRepository(metadata, localRepository, remoteRepository);
        } catch (TransferFailedException e) {
            throw new RepositoryMetadataResolutionException(
                    metadata + " could not be retrieved from repository: " + remoteRepository.getId()
                            + " due to an error: " + e.getMessage(),

View on GitHub (pinned to e4093d4e12)

Solutions

Fix ownership/permissions of the metadata file and its parent directories (chown -R $USER ~/.m2/repository or chmod -R u+w).
Free disk space / raise quota if the write failed with ENOSPC.
Close other processes locking the file (IDE, another build, antivirus) or delete the metadata file so it is recreated.
Re-run with -X and read the attached exception to confirm the exact I/O cause before changing anything.

Example fix

# before
~/.m2/repository/com/example/... maven-metadata.xml  # read-only, owned by root
# after
sudo chown -R $(id -u):$(id -g) ~/.m2/repository
chmod -R u+w ~/.m2/repository

Defensive patterns

Strategy: validation

Validate before calling

find ~/.m2/repository ! -writable -o ! -user "$USER" | head  # detect unwritable local repo entries

Prevention

Never run Maven under sudo; fix ownership with chown if already done.
Mount local repository read-write in containers; give the build user write access.
Watch disk space (df -h ~/.m2) on busy CI agents.

When it happens

Trigger: fixTimestamp wrote to Files.newOutputStream(metadataFile.toPath()) and the OS refused: file or parent directory read-only, no write permission in ~/.m2/repository, disk full, or the StAX writer hit malformed Metadata content. Logged as warn-with-exception under -X.

Common situations: Local repository owned by root or another user after running Maven with sudo once; corporate-managed read-only repository caches; disk quota exhausted; antivirus/file locks on Windows.

Related errors

AI-assisted analysis of apache/maven@e4093d4e12 (2026-08-21). Data as JSON: /api/errors/45a093607c3355ad. Report an issue: GitHub.