[maven-site] 01/01: clarify "never" value for "updatePolicy"

[kw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kwin pushed a commit to branch bugfix/clarify-update-policy
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit c716f0f66dea39ff5e2b1f406ead96297d1789d6
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Mon Jun 12 17:11:38 2023 +0200

    clarify "never" value for "updatePolicy"
---
 content/apt/pom.apt.vm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/apt/pom.apt.vm b/content/apt/pom.apt.vm
index 137cdf5d..4a877dad 100644
--- a/content/apt/pom.apt.vm
+++ b/content/apt/pom.apt.vm
@@ -1739,7 +1739,8 @@ scm:cvs:pserver:127.0.0.1:/cvs/root:my-project
   * <<updatePolicy>>:
   This element specifies how often updates should attempt to occur. Maven will compare the local
   POM's timestamp (stored in a repository's maven-metadata file) to the remote. The choices are:
-  <<<always>>>, <<<daily>>> (default), <<<interval:X>>> (where X is an integer in minutes) or <<<never>>>.
+  <<<always>>>, <<<daily>>> (default), <<<interval:X>>> (where X is an integer in minutes) or <<<never>>>
+  (only downloads if not yet existing in the local repository).
 
   * <<checksumPolicy>>:
   When Maven deploys files to the repository, it also deploys corresponding checksum files. Your options