Author: carlos
Date: Sun Nov 18 06:37:29 2007
New Revision: 596087
URL: http://svn.apache.org/viewvc?rev=596087&view=rev
Log:
meeper was moved to archiva tools
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=596087&r1=596086&r2=596087&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 Nov 18 06:37:29 2007
@@ -126,7 +126,7 @@
{{{http://sf.net/}Sourceforge}} that provide you
{{{http://sourceforge.net/docman/display_doc.php?docid=4297&group_id=1#shell}ssh
server access}}.
After you are able to deploy to your remote repository <<make sure you only
deploy releases>>. Then you can provide a script like the
-
{{{http://svn.apache.org/viewvc/maven/archiva/trunk/maven-meeper/src/bin/synchronize/m2-sync/conf/}current
scripts}},
+
{{{http://svn.apache.org/viewvc/maven/archiva/tools/trunk/maven-meeper/src/bin/synchronize/m2-sync/conf/}current
scripts}},
open an issue under
{{{http://jira.codehaus.org/browse/MAVENUPLOAD}MAVENUPLOAD}} and attach the
script, and we'll add it to the automatically synced repos.
Make sure you provide proof of owning the domain that matches the groupId
(see groupId considerations above). Proof means either the server to sync from
has a name
