LUCENE-2024: Fix: "ant dist" no longer generates md5's for the top-level artifacts

git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@835889 13f79535-47bb-0310-9956-ffa450edef68

BUILD.txt

@@ -3,14 +3,14 @@ Lucene Build Instructions
 $Id$
 
 Basic steps:
-  0) Install JDK 1.5 (or greater), Ant 1.6.3 (or greater)
+  0) Install JDK 1.5 (or greater), Ant 1.7.0 (or greater)
   1) Download Lucene from Apache and unpack it
   2) Connect to the top-level of your Lucene installation
   3) Install JavaCC (optional)
   4) Run ant
 
 Step 0) Set up your development environment (JDK 1.5 or greater,
-Ant 1.6.3 or greater)
+Ant 1.7.0 or greater)
 
 We'll assume that you know how to get and set up the JDK - if you
 don't, then we suggest starting at http://java.sun.com and learning
@@ -18,7 +18,7 @@ more about Java, before returning to this README. Lucene runs with
 JDK 1.5 and later.
 
 Like many Open Source java projects, Lucene uses Apache Ant for build
-control.  Specifically, you MUST use Ant version 1.6.3 or greater.
+control.  Specifically, you MUST use Ant version 1.7.0 or greater.
 
 Ant is "kind of like make without make's wrinkles".  Ant is
 implemented in java and uses XML-based configuration files.  You can

CHANGES.txt

@@ -153,7 +153,10 @@ Build
 
 * LUCENE-486: Remove test->demo dependencies. (Michael Busch)
 
-Test Cases
+Build
+
+ * LUCENE-2024: Raise build requirements to Java 1.5 and ANT 1.7.0
+   (Uwe Schindler, Mike McCandless)
 
 ======================= Release 2.9.1 2009-11-06 =======================
 

build.xml

@@ -28,9 +28,6 @@
   <property name="demo.name" value="lucene-demos-${version}"/>
   <property name="demo.war.name" value="luceneweb"/>
 
-  <!-- Type of checksum to compute for distribution files -->
-  <property name="checksum.algorithm" value="md5" />
-	
   <!-- Build classpath -->
   <path id="classpath">
     <pathelement location="${build.dir}/classes/java"/>
@@ -692,25 +689,9 @@
    -->
   <macrodef name="lucene-checksum">
     <attribute name="file"/>
-    <!-- NOTE: we use the value of @{file} in the names any properties
-         set because macro's don't have variables, and otherwise we
-         wouldn't be able to checksum more then one file per build
-      -->
     <sequential>
-      <checksum file="@{file}"
+      <checksum file="@{file}" algorithm="md5" pattern="{0}  {1}" forceoverwrite="yes" readbuffersize="65536"/>
-                property="@{file}.sum"
+      <checksum file="@{file}" algorithm="sha1" pattern="{0}  {1}" forceoverwrite="yes" readbuffersize="65536"/>
-                algorithm="${checksum.algorithm}" />
-      <basename file="@{file}" property="@{file}.base" />
-      <concat destfile="@{file}.${checksum.algorithm}"
-              force="yes"
-              append="false"
-              fixlastline="yes">
-        <header trimleading="yes">${@{file}.sum}  </header>
-        <!-- empty fileset to trick concat -->
-        <fileset dir="." excludes="**" />
-        <footer trimleading="yes">${@{file}.base}
-        </footer>
-      </concat>
     </sequential>
   </macrodef>