Apache
/
archiva
mirror of https://github.com/apache/archiva.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[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
This commit is contained in:
Jevica Arianne B. Zurbano 2009-10-08 03:29:41 +00:00
parent 8142e83c50
commit 94647f519e
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
archiva-docs/src/site/apt/userguide/deploy.apt
View File

@ -10,6 +10,12 @@ Deploying to Repository
* {{{#Web UI} Deploying via the Web UI Form}}
[]
<<WARNING>> The deployed artifact may not appear immediately in the search results.
The execution of the <<<index-content>>> 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
[[1]] Create a user in Archiva to use for deployment (or use guest if you wish to deploy without a username and password)
@ -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 <<<index-content>>> repository consumer is enabled.
** Deploying Third-Party Artifacts to Archiva using Maven