From 38130f9ff150039c3620ea20e865372834acca8b Mon Sep 17 00:00:00 2001
From: Conor MacNeill <conor@apache.org>
Date: Tue, 27 May 2003 04:40:10 +0000
Subject: [PATCH] Update documentation to reflect change in inline manifest
 regeneration policy

PR:	20179


git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@274620 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/CoreTasks/jar.html | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/manual/CoreTasks/jar.html b/docs/manual/CoreTasks/jar.html
index 2e42df994..ef2b31d67 100644
--- a/docs/manual/CoreTasks/jar.html
+++ b/docs/manual/CoreTasks/jar.html
@@ -177,10 +177,11 @@ If both an inline manifest and an external file are both specified, the
 manifests are merged.
 </p>
 
-<p>When using inline manifests, the Jar task will check whether the build
-file is more recent that the Jar file when deciding whether to rebuild the
-Jar. This will not take into account property file changes which may affect
-the resulting Jar.
+<p>When using inline manifests, the Jar task will check whether the manifest 
+contents have changed (i.e. the manifest as specified is different in any way 
+from the manifest that exists in the Jar, if it exists. 
+If the manifest values have changed the jar will be updated or rebuilt, as
+appropriate.
 </p>
 
 <h3>Examples</h3>