You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by co...@apache.org on 2003/05/27 06:40:10 UTC

cvs commit: ant/docs/manual/CoreTasks jar.html

conor       2003/05/26 21:40:10

  Modified:    docs/manual/CoreTasks jar.html
  Log:
  Update documentation to reflect change in inline manifest regeneration
  policy
  
  PR:	20179
  
  Revision  Changes    Path
  1.27      +5 -4      ant/docs/manual/CoreTasks/jar.html
  
  Index: jar.html
  ===================================================================
  RCS file: /home/cvs/ant/docs/manual/CoreTasks/jar.html,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -w -u -r1.26 -r1.27
  --- jar.html	11 Apr 2003 13:31:18 -0000	1.26
  +++ jar.html	27 May 2003 04:40:10 -0000	1.27
  @@ -177,10 +177,11 @@
   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>