src/main/resources/net/sf/antcontrib/antcontrib.properties | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 ensure 'for' task is specified correctly.

build.xml | 1 1 + 0 - 0 !
src/main/java/net/sf/antcontrib/net/URLImportTask.java | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 1 deletion(-)

 fixes the compatibility with the version of ivy in debian

pom.xml | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 mark the maven dependencies as optional to match the package dependencies and the pom deployed on maven central

build.xml | 2 1 + 1 - 0 !
test/resources/logic/outofdate.xml | 18 10 + 8 - 0 !
2 files changed, 11 insertions(+), 9 deletions(-)

 address intermittent test failures
 Update "outofdate" test case to ensure that the simulated build artifacts
 (outofdate/gen/*) have dates strictly later than the source files.
 .
 It appears that the tests were failure due to a race where "file.done"
 was considered out of date and thus appeared in the source set, despite
 being configured as up to date in the test case.  
 .
 That said, it's not clear to me how it ever worked in the first place
 given the logic in OutOfData.outOfDate():
 .
        if ((!ret)  && (sourceFile != null)) {
            ret = sourceFile.lastModified() > targetFile.lastModified();
        }
 .
 My assumption is that the test was previously broken/flaky, but that time
 was chunkier (larger quanta) until recently and so the source files had
 the same timestamp and so weren't strictly newer.
 .
 This patch also adds the fork=true attribute to the junit task, which
 resolves spurious test failures observed after the OutOfDate test was
 patched.