Thanks for the ideas. The cache.properties file was being written, but as far as I could tell, wasn't being re-read. Not sure why. I've given up on that path anyway. (see my note about a patch to DateSelector.java). I liked the idea of creating a single timestamp and checking against that.
David
Thus Spoke [EMAIL PROTECTED]:
<modified> should use its cache.properties file (otherwise the testcases should fail :)
But you can specify it via <modified> <param name="cache.cachefile" value="cache.properties"/> </modified>
Is the file created when using the <copy>? (Maybe the <pathconvert> would be better here.)
Another (theoretical) point: <javac> creates new files with different content. Can you place a <modified> with a different cachefile in the <javac>? Then look for the keys (must be equal...)
Jan
-----Original Message----- From: David Kavanagh [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 3:14 AM To: Ant Developers List Subject: using <modified>
I'm playing with the <modifed> selector. I'm using it to build the cache, then compile code, then run it again to build a set of files that changed to do hotswap on.
Here is how I pre-load the cache.
<!-- no-op copy to build modified cache -->
<copy todir="build/classes">
<fileset dir="build/classes">
<modified seldirs="false" />
</fileset>
</copy>
I'd put an if condition around this in the future... Then... <javac...> Then, my <hotswap>
<hotswap verbose="true" port="9000"> <fileset dir="build/classes"> <modified seldirs="false" /> </fileset> </hotswap>
The <hotswap> target reports that it wants to swap all of the class files! The thing is, none had changed! It seems like the modified selector isn't using the cache.properties file it already built!
Any ideas?
David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
