From 94647f519e872ce4aa13254c5312dec8278768a5 Mon Sep 17 00:00:00 2001 From: "Jevica Arianne B. Zurbano" Date: Thu, 8 Oct 2009 03:29:41 +0000 Subject: [PATCH] [MRM-1251] - Update documentation - Artifacts not displayed in Archiva GUI after release Submitted by: Gwen Harold Autencio git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@823011 13f79535-47bb-0310-9956-ffa450edef68 --- archiva-docs/src/site/apt/userguide/deploy.apt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/archiva-docs/src/site/apt/userguide/deploy.apt b/archiva-docs/src/site/apt/userguide/deploy.apt index 96e6d80c2..e552df3c5 100644 --- a/archiva-docs/src/site/apt/userguide/deploy.apt +++ b/archiva-docs/src/site/apt/userguide/deploy.apt @@ -9,6 +9,12 @@ Deploying to Repository * {{{#Maven} Configuring Maven to deploy to an Archiva repository}} * {{{#Web UI} Deploying via the Web UI Form}} + + [] + + <> The deployed artifact may not appear immediately in the search results. + The execution of the <<>> repository consumer and other scanning consumers are queued for execution + to prevent concurrent updates to the index. * Configuring {Maven} to deploy to an Archiva repository @@ -112,7 +118,7 @@ Deploying to Repository You can also deploy to the Archiva server using traditional means such as SCP, FTP, etc. For more information on these deployment techniques, refer to the Maven documentation. - Once the files are deployed into the location of the Archiva managed repository, they should immediately appear in the Browse page. + Once the files are deployed into the location of the Archiva managed repository, they should appear in the Browse page. The artifacts should also be searcheable as long as the <<>> repository consumer is enabled. ** Deploying Third-Party Artifacts to Archiva using Maven -- 2.39.5