From c4dcc9c319d9c285009b483183f45b8ce1b6a84a Mon Sep 17 00:00:00 2001 From: Brett Leslie Porter Date: Tue, 1 Nov 2005 21:52:19 +0000 Subject: [PATCH] fix line endings git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@330132 13f79535-47bb-0310-9956-ffa450edef68 --- .../guides/mini/guide-maven-evangelism.apt | 138 +++++++++--------- 1 file changed, 69 insertions(+), 69 deletions(-) diff --git a/maven-site/src/site/apt/guides/mini/guide-maven-evangelism.apt b/maven-site/src/site/apt/guides/mini/guide-maven-evangelism.apt index f1087c4aa7..ea02691925 100644 --- a/maven-site/src/site/apt/guides/mini/guide-maven-evangelism.apt +++ b/maven-site/src/site/apt/guides/mini/guide-maven-evangelism.apt @@ -1,69 +1,69 @@ - ------ - Guide to Maven Evangelism - ------ - Carlos Sanchez - ------ - 31 October 2005 - ------ - -Guide to add, improve or fix metadata in the ibiblio maven 2 repository - - Checkout with subversion the poms you need from - <<>> - (note that this subversion repo has a lot of files and folders) - - 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,...). - - - -Developers information - - - The developer connection to the subversion pom repository is at - - <<>> - - 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 tag set to "verified". - - - -Information about the current configuration - - The canonical repository is at <<>>, under <<>> - - * repository-staging/to-ibiblio/maven - maven 1 repo - - * repository-staging/to-ibiblio/maven2 - maven 2 repo - - - - Every 4 hours a crontab runs - - <<<$HOME/repository-tools/synchronize.sh 2>&1 | tee $HOME/repository-tools/last-sync-results.txt>>> - - - - Folder contents: - - * <<>> - svn checkout from maven/components svn - - * <<>> script to deploy an upload bundle from JIRA MAVENUPLOAD - - * <<>> scripts to rsync from partner repos - - * <<>> syncopate configuration for each of the partners - - * <<>> scripts to rsync to and from ibiblio - - * <<>> link to components/maven-meeper/src/bin/ibiblio-sync/ - - * <<>> link to components/maven-meeper/src/bin/synchronize.sh - - * <<>> snapshot of the repoclean tool - <<>> + ------ + Guide to Maven Evangelism + ------ + Carlos Sanchez + ------ + 31 October 2005 + ------ + +Guide to add, improve or fix metadata in the ibiblio maven 2 repository + + Checkout with subversion the poms you need from + <<>> + (note that this subversion repo has a lot of files and folders) + + 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,...). + + + +Developers information + + + The developer connection to the subversion pom repository is at + + <<>> + + 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 tag set to "verified". + + + +Information about the current configuration + + The canonical repository is at <<>>, under <<>> + + * repository-staging/to-ibiblio/maven - maven 1 repo + + * repository-staging/to-ibiblio/maven2 - maven 2 repo + + + + Every 4 hours a crontab runs + + <<<$HOME/repository-tools/synchronize.sh 2>&1 | tee $HOME/repository-tools/last-sync-results.txt>>> + + + + Folder contents: + + * <<>> - svn checkout from maven/components svn + + * <<>> script to deploy an upload bundle from JIRA MAVENUPLOAD + + * <<>> scripts to rsync from partner repos + + * <<>> syncopate configuration for each of the partners + + * <<>> scripts to rsync to and from ibiblio + + * <<>> link to components/maven-meeper/src/bin/ibiblio-sync/ + + * <<>> link to components/maven-meeper/src/bin/synchronize.sh + + * <<>> snapshot of the repoclean tool + <<>>