Well. Maven Central repo is the official Maven repository where all "official" jars are published. It's part of the super pom.xml which is implicitly included by every Maven project and is visible to all Maven users without any special effort. Some "strict" companies can't download artefacts from anywhere else. They require verification of downloaded artefacts (artefacts are PGP signed in Maven central repo). These identifiers are essential as they will be seen by anyone downloading a software artifact and validating a signatute. Deployment in Maven central is simple good manner. I will not write more sentencies (there are many other reasons) because these arguments above aren't the main arguments for us. We have another problem. Projects dependent on PrimeFaces can not be released (or deployed as shapshot versions) in Maven central repo. PrimeFaces Extensions project has e.g. an access to Maven Central repo, but we are not allowed to deploy project / sub-projects into this until at least one dependency from other repo exists in pom.xml. References to artefracts from other repos except Maven central are not allowed. https://issues.sonatype.org/browse/OSSRH-2317
PrimeFaces is only one such dependency, we don't have any other dependencies outside of central repo. So, we have to look for an alternative way. Bad, but no problem.
BTW, putting repos in pom.xml is a bad idea http://www.sonatype.com/people/2009/02/ ... -bad-idea/
You don't need actually maven2-repository.dev.java.net and repository.jboss.org as repositories in your pom.xml. Keep it simple
What is necessary are missing "description", "license", "scm", and "developers" tags.