The MEV project on jira.codehaus.org is where we collect data to fix these known issues. In general the policy is not to change existing files (checksums is one exception), and also we need to be careful to not insert pom files in place of missing ones. Even doing this can cause user's builds to change in subtle ways.
There are plans to get some of this cleaned up and mainly focus on stopping the garbage from getting in there in the first place. On Thu, Sep 24, 2009 at 7:40 AM, Albert Kurucz <albert.kur...@gmail.com> wrote: > According to http://www.think88.com/resources/Maven_white_paper_june_2009.pdf > > " > Sonatype maintains a central repository with more than 90,000 artifacts, > consuming more than 60 GB of storage. In addition to the artifacts > themselves, the > Maven Central Repository also contains a POM-file for each of the artifacts, > containing the meta data for these artifacts. To protect the integrity of the > repository, Sonatype checks the meta data for correctness. If the meta data is > erroneous, the artifact can’t be uploaded. > " > > There are some artifacts on the Maven Central Repo, with corrupt meta data. > Is there an issue tracker where such corrupt artifacts could be reported? > > What is the policy of Sonatype handling this issue? > 1. Will corrupt artifacts be removed (causing a chain reaction, > because Central hosted dependents will loose their dependencies, which > are required to be also on Central)? > 2. Or is it in Sonatype's plan to start a new Central Repo, which is > now better scanned? > 3. Or ignorance? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
