Author: carlos
Date: Wed Mar 18 16:58:58 2009
New Revision: 755648
URL: http://svn.apache.org/viewvc?rev=755648&view=rev
Log:
Clarify the central repository rules and add a link to the list of synced repos
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=755648&r1=755647&r2=755648&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
Wed Mar 18 16:58:58 2009
@@ -331,9 +331,12 @@
{Maven partners}
- The following sites automatically sync their project repository with the
central one.
+ There is a list of sites that automatically sync their project repository
with the central one.
If you want a project from any of these sites to be uploaded to the Central
Repository you'll have to
contact their project maintainers.
+ Check the
{{{https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv}updated
list}}
+
+ Some of the most known groups automatically synced are:
* {{{http://www.apache.org/dev/release-publishing.html#maven-repo}The Apache
Software Foundation}}
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=755648&r1=755647&r2=755648&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 Wed
Mar 18 16:58:58 2009
@@ -13,6 +13,13 @@
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 add a POM with no dependencies,
because doing any other way
+ would break previous builds that were using that project.
+
+ An alternative is to create a new version with the fixes. If the broken
project is org.foo/bar/1.0 you can
+ provide a fixed POM,JAR,... under org.foo/bar/1.0-1 (add a comment to the POM
explaining what is being fixed
+ and why). See {{{guide-central-repository-upload.html}Maven Respository
Upload}} for the instructions to
+ get this new version in the repository.
You need to contact the original publisher of the metadata to make sure in
next versions it will
be fixed or improved before getting it into the repository.
