On May 3, 2010, at 12:10 PM, Benjamin Bentmann wrote: > Hi, > > somehow related to my previous question about the checksums, what are our > chances to automatically detect and fix bad maven-metadata.xml's deployed to > Central like seen in [0]? >
While the content of the POMs is not something we can't really change, the information about what artifacts exist I believe is something we can fix. I suppose the only downside is we might potentially change the results someone is getting if they are using ranges. But ranges are used so infrequently, and it really is undefined right now whether you would deploy something with this range resolved or resolve against a repository with fixed versions (more like OSGi). I think we could probably correct the metadata with very little, if any, harmful impact. This is one area where I would likely side on changing the contents in Maven Central. But how it's changed is another question. We could simply run over it with Nexus and fix it all. But if it's not fixed at the source the cat will just come back. I think a real solution involves something Brian and I have been talking about for a while where project registers for ownership of a groupId. We could suggest fixes which can be accepted and then tracking to any changes to this metadata would also need to be recorded. > > Benjamin > > > [0] http://jira.codehaus.org/browse/MEV-658 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa
