You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@archiva.apache.org by oc...@apache.org on 2009/05/12 10:00:00 UTC
svn commit: r773817 -
/archiva/trunk/archiva-docs/src/site/apt/userguide/deploy.apt
Author: oching
Date: Tue May 12 08:00:00 2009
New Revision: 773817
URL: http://svn.apache.org/viewvc?rev=773817&view=rev
Log:
o updated docs for deploying artifacts in archiva
Modified:
archiva/trunk/archiva-docs/src/site/apt/userguide/deploy.apt
Modified: archiva/trunk/archiva-docs/src/site/apt/userguide/deploy.apt
URL: http://svn.apache.org/viewvc/archiva/trunk/archiva-docs/src/site/apt/userguide/deploy.apt?rev=773817&r1=773816&r2=773817&view=diff
==============================================================================
--- archiva/trunk/archiva-docs/src/site/apt/userguide/deploy.apt (original)
+++ archiva/trunk/archiva-docs/src/site/apt/userguide/deploy.apt Tue May 12 08:00:00 2009
@@ -112,8 +112,8 @@
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.
- Note that once the files are deployed into the location of the Archiva managed repository, they will not be detected by Archiva until the
- next scan takes place, so the interval should be configured to a reasonably frequent setting.
+ Once the files are deployed into the location of the Archiva managed repository, they should immediately 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