PrimeFaces in Maven central repo

Dear PrimeFaces team,

Would it be possible to transfer PF artefacts to Maven Central repository after major releases? Is it much work for you, Cagatay? Some companies are restrict and can only use Maven central. In my company we always have to download PF releases (+ themes) from Prime repo manually and deploy them manually into our repo.

Thanks.

[optimus.prime]

No plans to push it in other repos.

But you don't need to do that manually, your effort is quite minimal. Sonatype does it for your! Google maven projects are deployed to Maven central repo automatically. All you need is to register PrimeFaces by Sonatype and adjust a little pom.xml. I have already done that twice, it takes 5 min. Please follows these instructions:

http://code.google.com/p/google-maven-r ... enProjects
https://docs.sonatype.org/display/Repos ... sage+Guide

I'm pretty sure PF Community will be thankful. Thanks a lot.

Actually it's a pity. Every great project belongs to the Maven Central repository. Starting with 2.1.2 Mojarra is now published to the Maven Central repo too http://javaserverfaces.java.net/nonav/rlnotes/2.1.3/

Dear Cagatay,

I would like to ask you if you allow me to bring PrimeFaces 3.0 into Maven central (released version of course). I wanted to ask you whether I can do that at all before I will deploy PF how it's described here https://docs.sonatype.org/display/Repos ... Repository I mean, PF is open source, but better to ask at first.

Many thanks in advance.

[optimus.prime]

Not sure, what is the advantage of central repo, don't users still need to add prime repo to pom.xml to access snapshot builds?

I can confirm what Oleg says.
Large company and banks (read money) often put some restrictions and it is a real burden to make them register a new repository.
The simpler the access to primefaces is the larger your audience will be in large company.
Remember, it's often thanks to a demo that people convince their peers to make a switch... but if the demo is painful to build, it may be a show stopper.

so +1 for maven central

[optimus.prime]

Thanks, I'd love to get more input from PrimeFaces Community, I didn't know this was that much important

I agree that stable releases can be published in Maven central repository.

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.

Thanks.