maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <>
Subject [jira] Created: (MNG-2377) maven-metadata not re-read after failure
Date Sat, 17 Jun 2006 02:03:41 GMT
maven-metadata not re-read after failure

         Key: MNG-2377
     Project: Maven 2
        Type: Bug

    Versions: 2.1    
    Reporter: Kenney Westerhof
    Priority: Minor

A bug in deploy (not setting filePermissions correctly on deploy) caused the maven-metadata...xml
and the artifacts/poms
to be unreadable.

When building a project with a dep on a SNAPSHOT artifact on the faulty remote repository,
the maven-metadata can not be read.
Maven creates a maven-metadata...xml with the following content (sample):

<?xml version="1.0" encoding="UTF-8"?><metadata>

After fixing the permissions I restart the build, but the metadata file is not re-read, resulting
in Maven thinking
1.0-SNAPSHOT is the actual version and trying to get  ...artifact/1.0-SNAPSHOT/artifact-1.0-SNAPSHOT.pom
which does not exist.

Touching the files on the remote repo doesn't help either.

Only when running with -U the metadata file is retrieved (another solution is to purge files
the local repository).

I think Maven should not create the metadata file if it can't be retrieved AND if the non-timestamped
SNAPSHOT version doesn't exist.

I can see why the placeholder metadata files reduces future requests for this file,
but that's only useful if there _are_ future requests. There are indeed repeated requests
for the pom
and artifact, even though they also don't exist. I think that only when the artifact 1.0-SNAPSHOT
and the metadata file doesn't, it's safe to put a placeholder metadata file in the local repository.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message