Author: brett
Date: Mon Dec 13 00:26:46 2010
New Revision: 1044975
URL: http://svn.apache.org/viewvc?rev=1044975&view=rev
Log:
clean up language a little
Modified:
maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt
maven/site/trunk/src/site/apt/guides/mini/guide-maven-evangelism.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=1044975&r1=1044974&r2=1044975&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 Dec 13 00:26:46 2010
@@ -114,17 +114,17 @@ Guide to uploading artifacts to the Cent
[]
-{Approved Forges}
+{Approved Repository Hosting}
- Instead of maintaining your own repository rsync feed, we now encourage
projects to use an approved Forge that provides repository hosting. (Not all of
them require code to be hosted at the same Forge) The aggregation of projects
into single larger feeds will allow us to sync faster and more often, and the
checks provided by approved Forges 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.
- Currently approved Forges:
+ Currently approved repository hosting locations:
- * {{{http://incubator.apache.org/}Apache}} (open to Apache Projects)
+ * {{{http://www.apache.org/}Apache Software Foundation}} (for all Apache
projects)
- * {{{http://codehaus.org/customs/selection.html}Codehaus}} (open to Codehaus
Projects)
+ * {{{http://www.codehaus.org/}Codehaus}} (for Codehaus projects)
* {{{http://nexus.sonatype.org/oss-repository-hosting.html}Sonatype Forge}}
(open to any OSS Project)
@@ -135,4 +135,4 @@ 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.
\ No newline at end of file
+ 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.
Modified: maven/site/trunk/src/site/apt/guides/mini/guide-maven-evangelism.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-maven-evangelism.apt?rev=1044975&r1=1044974&r2=1044975&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-maven-evangelism.apt
(original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-maven-evangelism.apt Mon
Dec 13 00:26:46 2010
@@ -8,9 +8,10 @@
Guide to add, improve or fix metadata in the Central Maven 2 repository
- There are artifacts in the repository that don't have POMs. They come from
the Maven 1 repositories of our
- partners (Apache Software Foundation, Codehaus,...). We know it but can't do
anything unless you provide
- a POM for it or you ask the project in question to add the POM when they add
the artifacts.
+ There are artifacts in the repository that don't have POMs. They come from
projects with repositories that have
+ been synced into central without extra checks (particularly historical ones
that were in Maven 1 format). We
+ know about the problems but can't do anything unless you provide a POM for it
or you ask the project in
+ question to add the POM when they add the artifacts.
We don't change dependencies in POMs already in the repository anymore as
builds need to be reproducible.
Same applies to POMs that don't exist. We can only add a POM with no
dependencies, because doing any other way
