Jason and Brian, thanks for the explanations. Understood, the policy of not removing anything from Maven Central serves a purpose.
I wish there would be another publicly Maven repository, which is maintained with rules enforced. This repo could even have a rule (additional to the old and unenforced rules) that only Maven built projects can enter, maybe even more restriction: only the designated Continuous Integration server can upload to it. This pure Maven repo would not be able to compete with Maven Central regarding size or the number of artifacts, but some OSS developers might prefer to use from and supply to this one instead of the big and ugly. On Thu, Sep 24, 2009 at 6:44 PM, Brian Fox <[email protected]> wrote: > On Thu, Sep 24, 2009 at 3:16 PM, Albert Kurucz <[email protected]> > wrote: >> Requirements for the POMs are defined as: >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html >> I call the artifact corrupt (regarding Maven Central Compliance) if >> the POM of the artifact does not fulfills the above requirements. >> There are corrupt ones have made it to the Central, because the guard >> was sleeping. >> > > Correct, but changing them is not an option because it will > destabilize builds. This is a long standing rule that we do not remove > or change the contents of central. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
