Author: carlos
Date: Sat Jun 24 06:51:44 2006
New Revision: 416916
URL: http://svn.apache.org/viewvc?rev=416916&view=rev
Log:
We don't update poms anymore
Modified:
maven/site/trunk/src/site/apt/guides/mini/guide-maven-evangelism.apt
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=416916&r1=416915&r2=416916&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 Sat
Jun 24 06:51:44 2006
@@ -8,42 +8,26 @@
Guide to add, improve or fix metadata in the ibiblio maven 2 repository
- Checkout with subversion the poms you need from
- <<<svn://svn.codehaus.org/maven/repository>>>
- (note that this subversion repo has a lot of files and folders)
-
- If the poms is not yet in subversion you will have to add it.
-
- Fix the poms and open an issue at
{{{http://jira.codehaus.org/browse/MEV}JIRA}} with
- a patch file from subversion in unified diff format, explaining the reasons
why
- it needs to be changed (there were no dependencies, wrong info,...).
-
- *Important:* by default assume that we won't trust your changes, so you must
provide all links
- to the project documentation you can to convince us that your patch is right.
-
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.
+ We don't change dependencies in poms already in the repository anymore as
builds need to be reproducible.
-Developers information
-
-
- The developer connection to the subversion pom repository is at
+ 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.
- <<<svn+ssh://[EMAIL PROTECTED]/home/projects/maven/scm/repository>>>
-
- It only contains m2 poms (manually added), and this poms will overwrite
everything in the maven2 repo.
-
- If a pom doesn't exist or has just the basic information (eg. was
autogenerated) patches can be applied.
- If it has already information, dependencies,... a consensus has to be
reached. NEVER will be changed
- a pom with the <status> tag set to "verified".
+ For any other types of issues related to metadata in the repository, open an
issue at
+ {{{http://jira.codehaus.org/browse/MEV}JIRA MEV}} with the relevant
information and
+ explaining the reasons why it is an issue.
+ *Important:* by default assume that we won't trust your info, so you must
provide all links
+ to the project documentation you can to convince us that your solution is
right.
Information about the current configuration
- The canonical repository is at <<<beaver.codehaus.org>>>, under
<<</home/projects/maven>>>
+ The canonical repository is at <<<maven.org>>>, under <<</home/maven>>>
* repository-staging/to-ibiblio/maven - maven 1 repo
@@ -53,7 +37,7 @@
Every 4 hours a crontab runs
- <<<$HOME/repository-tools/synchronize.sh 2>&1 | tee
$HOME/repository-tools/last-sync-results.txt>>>
+ <<<$HOME/components/maven-meeper/src/bin/synchronize.sh 2>&1 | tee
$HOME/repository-tools/last-sync-results.txt>>>
@@ -69,9 +53,5 @@
* <<<components/maven-meeper/src/bin/ibiblio-sync/>>> scripts to rsync to and
from ibiblio
- * <<<repository-tools/ibiblio-sync/>>> link to
components/maven-meeper/src/bin/ibiblio-sync/
-
- * <<<repository-tools/synchronize.sh>>> link to
components/maven-meeper/src/bin/synchronize.sh
-
- * <<<repository-tools/repoclean>>> snapshot of the repoclean tool
+ * <<<repository-tools/repoclean>>> snapshot of the repoclean tool (20060206
as of today)
<<<https://svn.apache.org/repos/asf/maven/components/trunk/sandbox/repoclean>>>
