Hi Mark,<br><br><div class="gmail_quote">On Mon, Jul 11, 2011 at 7:07 AM, Mark Evenson <span dir="ltr">&lt;<a href="mailto:evenson@panix.com">evenson@panix.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Erik reported problems making a binary release yesterday on #abcl related to the presence of the version information in the &quot;build/classes/org/armedbear/<u></u>lisp/version&quot; file.  I did indeed change the build process to try to be smarter about needing to create this file by creating the &#39;abcl.stamp.version.uptodate&#39; task to compare the date of this file to the corresponding class of Version.java.  But I can&#39;t reproduce a problem here via various permutations of manually removing the file, updating the timestamps of various files via touch(1), etc.<br>

<br>
If someone can provide instructions to reproduce the error here, I will endeavor to fix it.  Maybe this is a problem under MSFT Windows environments?<br><br></blockquote><div>My environment: Java 1.6.0_20 (Sun x86-32) with Ant 1.7.1; build target directory on HPFS. Win7-64 (Home Premium, if that matters).</div>
<div><br></div><div>The commands I issued:</div><div><br></div><div> ant abcl.clean</div><div> ant abcl.source.zip abcl.source.tar abcl.binary.zip abcl.binary.tar</div><div><br></div><div>The above bombs out (on my machine)  while processing the third target (abcl.binary.zip).</div>
<div><br></div><div>Which versions are you using?</div><div><br></div><div><br></div><div>Bye,</div><div><br></div><div>Erik.</div></div>