archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristof Jozsa <>
Subject RepositoryMetadataExceptions
Date Fri, 19 Oct 2007 11:13:36 GMT

I think I'm having some progress with my archiva proxy-setup using mirrorOf="*".
I started again from scratch, fetched archiva beta2, unpacked, configured all
remote repositories I'd need and set up the managed internal repo to be a proxy
of them all.

As a test, I'm trying to build archiva-beta3 from svn now via 'mvn clean
install', with a wiped local repository. (This would be the real smoke-test as
other developers will have a clean install of maven with a mirrorOf="*" settings
and no files in their local repository).

The build error looks like this:

Project ID: org.apache.maven.plugins:maven-clean-plugin

Reason: Error getting POM for 'org.apache.maven.plugins:maven-clean-plugin' from
the repository: Failed to resolve artifact, possibly due to a repository list
that is not appropriately equipped for this artifact's metadata.

from the specified remote repositories:
  central (
 for project org.apache.maven.plugins:maven-clean-plugin

and Archiva's console output shows this exceptions:

2007-10-19 13:06:02,345 [SocketListener0-3] WARN
org.apache.maven.archiva.repository.metadata.MetadataTools  - Unable to read
org.apache.maven.archiva.repository.metadata.RepositoryMetadataException: file
does not exist:

Where "codehaus" is the repository name I've chosen for the configured The file does not exists indeed and I get
similar exceptions with full stacktraces for most (but not all) of my configured
remote repositories.

Any ideas what happens here?


View raw message