Now usually one would say, this is the problem of the very project, and just hits the reputation of this project if the documentation or build configuration is made sloppy. Unfortunately this is not the case when Maven 2 is concerned. The reason simply is, that other projects that do depend on such a project with sloppy POMs is now running into problems, and the whole Maven build idea suffers.
- Check XML for well-formedness and POM File syntax
- Check if really all dependencies declared are really needed (not just drop anything in that might be needed, and remove "historic legacy")
- Test your pom on a clean local repository!
Additionally I want to suggest a tool that checks public repositories for invalid POMs, if e.g. a student would like to program that as a student-project, please contact me!