From c1a419aa2c51a8d3a1b4de326691cb2315fee0a4 Mon Sep 17 00:00:00 2001
From: Ian Young <ian@iay.org.uk>
Date: Tue, 12 Apr 2011 16:13:59 +0000
Subject: [PATCH] Perform "future" check on its own.

---
 build.xml | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/build.xml b/build.xml
index d9107700..b4b341b6 100644
--- a/build.xml
+++ b/build.xml
@@ -409,7 +409,7 @@
 	
 	<target name="test.uk.future" depends="gen.uk">
 		<echo>Checking against future rulesets.</echo>
-        <CHECK i="${xml.dir}/${uk.master.file}" s="check_future.xsl"/>
+        <CHECK.one i="${xml.dir}/${uk.master.file}" s="check_future.xsl"/>
 	</target>
 	
 	<target name="gen.uk.unsigned" depends="gen.uk.master">
@@ -891,12 +891,21 @@
         </sequential>
 	</macrodef>
 	
+    <!--
+        Check a metadata document against a single ruleset file.
+        
+        Parameter 'i' is the file to be checked; no assumption is made
+        about its location so this must contain a full path.
+        
+        Parameter 's' is the primary checking stylesheet to use; assumed to be
+        present in the build.dir.
+    -->
 	<macrodef name="CHECK.one">
         <attribute name="i"/>
 		<attribute name="s"/>
         <sequential>
             <CHECK.base i="@{i}">
-                <arg value="${s}"/>
+                <arg value="${build.dir}/@{s}"/>
             </CHECK.base>
         </sequential>
 	</macrodef>