archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joakim Erdfelt <>
Subject Re: RepositoryMetadataExceptions
Date Fri, 19 Oct 2007 22:13:19 GMT
You have hit squarely the 2 bugs surrounding the metadata updates. - metadata-updater is changing 
lastUpdating timestamp when it shouldn't - Versions (latest and release) 
wrong after regeneration of maven-metadata.xml

These have been fixed in archiva/trunk, but, alas, the 1.0-beta-2 
release still has those bugs.

- Joakim

Kristof Jozsa wrote:
> Hi,
> 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.
>   org.apache.maven.plugins:maven-clean-plugin:pom:2.2-SNAPSHOT
> from the specified remote repositories:
>   central (
>  for project org.apache.maven.plugins:maven-clean-plugin

- Joakim Erdfelt
  Open Source Software (OSS) Developer

View raw message