Cagatay, I can understand you, often I don't have time as well to look deeper into some things and need a quick introduction. I try to explain major steps. You can find a detailed explaination in this offcial document
https://docs.sonatype.org/display/Repos ... sage+Guide
First of all - this is a service from Sonatype OSS Repository Hosting Service for open source projects. Sonatype doesn't synchronize any repos with Maven central repo. You can deploy snapshots and releases to Sonatype. Only released versions go to Maven central (central repo doesn't have snapshots at all). Sonatype synchronizes released versions with Maven central. Snapshots stay in Sonatype OSS repo. I suggest to deploy only released versions of PrimeFaces. You can still deploy snaphsots to Prime repo (time to time). Prime repo is okey for snapshots and it dosn't hurt. Of course you are free to deploy released versions to Prime repo as well (if it makes sense).
1) The first step is a Sonatype JIRA account if you don't have already one. Such account can be got here
https://issues.sonatype.org/ and it takes max. 5 min. You just create a JIRA ticket with your small project description (see the mentioned above document what you should input there).
2) The second step is a preparation of your pom.xml. You already have almost all nessesary tags (except 3-4, see the mentioned above document). The most important thing is this section in your (master) pom.
Code: Select all
<project>
...
<parent>
<groupId>org.sonatype.oss</groupId>
<artifactId>oss-parent</artifactId>
<version>7</version>
</parent>
...
</project>
3) The third step is a PGP installation and generation of public / private keys. This step have to be done just once. Artefact will be signed with private key. Artifact signing is only necessary when it's time to release project. I suggest to use a Maven PGP plugin which does all work automatically. Here is an offcial document how to do this step
https://docs.sonatype.org/display/Repos ... With+Maven
4) The last step is to call
Code: Select all
mvn -Prelease release:clean
mvn -Prelease release:prepare
mvn -Prelease release:perform -Darguments=-Dgpg.passphrase=<your passphrase you input when created PGP keys>
That's all. These calls create a SVN tag for released version, update project version (you will be asked), transfer files to your SVN, Sonatype, checkin/out and do all work. After that you have to go to Sonatype Nexus
https://oss.sonatype.org/index.html#welcome, log in and press Close / Release button for the uploaded (staged) in the step 4 artefact (chapter 8 in the first mentioned document). In 2 hour you have it in Maven central repo. Yesterday deployed by me artefacts were available today morning
http://search.maven.org/#search|ga|1|pr ... extensions
BTW, I have a Sonatype account and could do this job quickly for you if you want. After PF release. Probably I will write yet a blog post with all details soon. Hope it will help you to make a right decision. Thanks for your effort.
P.S. You know, this is a nice to have thing, PrimeFaces works without that of course. But it's a good style to do that. For instance, Java code can be either formatted or can stay unformatted. The program is still working, but formatted code looks nicer, more readable and is a big plus for project owner. PrimeFaces in Maven central repo would be a very big plus for your great project.