svn commit: r1083619 - /maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt

[hb...@apache.org]

Author: hboutemy
Date: Mon Mar 21 00:07:16 2011
New Revision: 1083619

URL: http://svn.apache.org/viewvc?rev=1083619&view=rev
Log:
reworked the publication/sync part to better show the special place taken by Sonatype OSS Repository, that is the ability to publish artifacts to any groupId

Modified:
    maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt?rev=1083619&r1=1083618&r2=1083619&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt Mon Mar 21 00:07:16 2011
@@ -120,44 +120,49 @@ Guide to uploading artifacts to the Cent
 
  []
 
-{Sync'ing your own repository to the central repository automatically}
+{Publishing your artifacts to the Central Repository}
 
- This used to be the preferred process until January 2010, but we are no longer accepting rsync requests on a per project basis.
- Over time, we have learned that this process is not scalable. Many of the projects being synced release very infrequently yet
- we have to hit hundreds of servers several times a day looking for artifacts that don't change. Additionally, there is no good
- mechanism currently for validating the incoming data via the rsync, and this leads to bad metadata that affects everyone. 
-
- Rsyncs will be provided for Forges that provide hosting services for OSS projects and other large project repositories that meet
- certain minimum criteria such as validation of PGP keys and pom contents as defined above. If you are interested in becoming an
- approved Forge, contact us at repo-maintainers@maven.apache.org
-
- []
- 
-{Approved Repository Hosting}
+* {Approved Repository Hosting}
 
- Instead of maintaining your own repository rsync feed, we now encourage projects to use an approved repository hosting location.
- Not all of them require code to be hosted at the same location. The aggregation of projects into single larger feeds will allow
- us to sync faster and more often, and ensuring these locations perform sufficient checks increases the quality of metadata for
- everyone. 
- 
- 
+ Instead of maintaining repository rsync feeds for each projects, we now encourage projects to use an approved repository hosting location.
 
  Currently approved repository hosting locations:
- 
+
   * {{{http://www.apache.org/}Apache Software Foundation}} (for all Apache projects)
-  
+
   * {{{http://www.codehaus.org/}Codehaus}} (for Codehaus projects)
-  
-  * {{{http://nexus.sonatype.org/oss-repository-hosting.html}Sonatype Forge}} (open to any OSS Project)
-  
-  * {{{http://www.fusesource.org/forge/}Fusesource Forge}} (Focused on FUSE related projects)
-  
+
+  * {{{http://www.fusesource.org/forge/}FuseSource Forge}} (focused on FUSE related projects)
+
   * {{{http://www.nuiton.org}Nuiton.org}}
 
  []
 
-{Manual upload of artifacts}
+ Automatic publication will be provided for Forges that provide hosting services for OSS projects and other large project repositories
+ that meet certain minimum criteria such as validation of PGP keys and pom contents as defined above. If you are interested in
+ becoming an approved Forge, contact us at <<<...@maven.apache.org>>>.
+
+* {Other Projects}
+
+ {{{http://nexus.sonatype.org/oss-repository-hosting.html}Sonatype OSS Repository}} is a special approved repository provided
+ by Sonatype for <any> OSS Project that want to get their artifacts into Central Repository.
+
+ The service is proposed in two variants:
+
+  * {{{https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide}Maven repository hosting service}}:
+  You can deploy snapshots, stage releases, and promote your releases so they will be published to Central Repository
+
+  * {{{https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central}Manual upload of artifacts}}:
+  The process is mostly automated with turnaround time averaging 1 business day.
+
+* {Explanations}
+
+ Having each project maintain its own repository with rsync to Central Repository used to be the preferred process until January 2010.
+ But we are no longer accepting rsync requests on a per project basis.
+
+ Over time, we have learned that this process is not scalable. Many of the projects being synced release very infrequently, yet
+ we have to hit hundreds of servers several times a day looking for artifacts that don't change. Additionally, there is no good
+ mechanism currently for validating the incoming data via the rsync, and this leads to bad metadata that affects everyone. 
 
- See {{{https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central}here}} for information about
- the new process to get artifacts loaded into Central. The new process is mostly automated with turnaround time averaging
- 1 business day.
+ The aggregation of projects into single larger feeds allows us to sync faster and more often, and ensuring these locations
+ perform sufficient checks increases the quality of metadata for everyone.