You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2011/03/20 18:41:27 UTC
svn commit: r1083517 -
/maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt
Author: hboutemy
Date: Sun Mar 20 17:41:27 2011
New Revision: 1083517
URL: http://svn.apache.org/viewvc?rev=1083517&view=rev
Log:
source formatting
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=1083517&r1=1083516&r2=1083517&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 Sun Mar 20 17:41:27 2011
@@ -9,9 +9,9 @@
Guide to uploading artifacts to the Central Repository
- In order for users of Maven to utilize artifacts produced by your project you must deploy them to
+ In order for users of Maven to utilize artifacts produced by your project, you must deploy them to
a remote repository. Many open source projects want to allow users of their projects who build with
- Maven to have transparent access to their project's artifacts. In order to allow for this a project
+ Maven to have transparent access to their project's artifacts. In order to allow for this, a project
must have their artifacts deployed to the Central Repository.
@@ -20,11 +20,13 @@ Guide to uploading artifacts to the Cent
Only releases can be uploaded to the central repository, that means files that won't change and that only depend on other files
already released and available in the repository.
- There are some requirements for the minimal information in the POMs that are in the central repository. The updated list of requirements can be found {{{https://docs.sonatype.org/display/Repository/Central+Sync+Requirements}here}}.
+ There are some requirements for the minimal information in the POMs that are in the central repository.
+ The updated list of requirements can be found {{{https://docs.sonatype.org/display/Repository/Central+Sync+Requirements}here}}.
{Choosing your coordinates}
- Picking the appropriate coordinates for your project is important. See the guidelines {{{https://docs.sonatype.org/display/Repository/Choosing+your+Coordinates}here}}.
+ Picking the appropriate coordinates for your project is important. See the guidelines
+ {{{https://docs.sonatype.org/display/Repository/Choosing+your+Coordinates}here}}.
* Explanation
@@ -36,7 +38,7 @@ Guide to uploading artifacts to the Cent
We also ask for license now because it is possible that your project's license may change in the course of
its life time and we are trying create tools to help normal people sort out licensing issues. For example, knowing all the licenses
- for a particular graph of artifacts we could have some strategies that would identify potential licensing problems.
+ for a particular graph of artifacts, we could have some strategies that would identify potential licensing problems.
* A basic sample:
@@ -46,11 +48,13 @@ Guide to uploading artifacts to the Cent
<modelVersion>4.0.0</modelVersion>
<groupId>org.apache.maven</groupId>
<artifactId>maven</artifactId>
+ <version>2.0</version>
<packaging>jar</packaging>
+
<name>Maven core</name>
- <version>2.0</version>
<description>The maven main core project description</description>
<url>http://maven.apache.org</url>
+
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
@@ -58,9 +62,11 @@ Guide to uploading artifacts to the Cent
<distribution>repo</distribution>
</license>
</licenses>
+
<scm>
<url>http://svn.apache.org/viewcvs.cgi/maven</url>
</scm>
+
<dependencies>
<dependency>
<groupId>...</groupId>
@@ -69,6 +75,7 @@ Guide to uploading artifacts to the Cent
</dependency>
...
</dependencies>
+
<!--
NOT ALLOWED: (see FAQ)
<repositories></repositories>
@@ -80,15 +87,22 @@ Guide to uploading artifacts to the Cent
* PGP Signature
- When people download artifacts from Central Maven repository, they might want to validate that these artifacts have valid PGP signatures that can be verified against a public key server. If there is no signatures, then users have no guarantee that they are downloading the original artifact.
-
- To improve the quality of the Central Maven repository, we require you to provide PGP signatures for all your artifacts (all files except checksums), and distribute your public key to a key server like hkp://pgp.mit.edu . Read {{{https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven}How to Generate PGP Signatures with Maven}} for more information.
+ When people download artifacts from Central Maven repository, they might want to validate that these artifacts have valid PGP
+ signatures that can be verified against a public key server. If there is no signatures, then users have no guarantee that they
+ are downloading the original artifact.
+
+ To improve the quality of the Central Maven repository, we require you to provide PGP signatures for all your artifacts (all
+ files except checksums), and distribute your public key to a key server like {{{http://pgp.mit.edu}http://pgp.mit.edu}}. Read
+ {{{https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven}How to Generate PGP Signatures with Maven}}
+ for more information.
* FAQ and common mistakes
* I have other <<<repositories>>> or <<<pluginRepositories>>> listed in my POM, is that a problem?
- At present, this won't preclude your project from being included, but we do strongly encourage making sure all your dependencies are included in Central. If you rely on sketchy repositories that have junk in them or disappear, it just creates havok for downstream users. Try to keep your dependencies among reliable repos like Central, Jboss, etc.
+ At present, this won't preclude your project from being included, but we do strongly encourage making sure all your dependencies
+ are included in Central. If you rely on sketchy repositories that have junk in them or disappear, it just creates havok for
+ downstream users. Try to keep your dependencies among reliable repos like Central, Jboss, etc.
* What about artifacts that can't be distributed because of their license?
@@ -108,15 +122,23 @@ Guide to uploading artifacts to the Cent
{Sync'ing your own repository to the central repository automatically}
- 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 serveral 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
+ 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}
- 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 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.
@@ -136,4 +158,6 @@ Guide to uploading artifacts to the Cent
{Manual upload of artifacts}
- 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.
+ 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.