mirror of https://github.com/apache/archiva.git
[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:
parent
8142e83c50
commit
94647f519e
|
@ -9,6 +9,12 @@ Deploying to Repository
|
|||
* {{{#Maven} Configuring Maven to deploy to an Archiva 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
|
||||
|
||||
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue