What steps will reproduce the problem? 1. Use the JarJarTask in an ant build script 2. run the build script twice 3. notice that even though no classes or jar files that are the input of the JarJarTask, the jar is re-packaged, or at least touched.

What is the expected output? What do you see instead? I expect that the output jar remains untouched if no inputs to the JarJarTask have changed since the last time the jar was touched.

What version of the product are you using? On what operating system? 1.0rc5 on Windows (though I suspect the OS doesn't matter).

Please provide any additional information below. The result of the bug is that any transitively dependent tasks in the ant script will always run. It is possible to work around by using the ant task 'uptodate', however a well behaved ant task has no effects when no input has changed.

JarJarTask just extends the JUnit Jar task. I wonder if it has the same behavior. I'm not sure if it is fixable, but I'll look into it.

I think you mean Ant, not JUnit. Anyhow, the jar task doesn't have this behavior. IIRC, it may be a little tricky to use the same mechanism as the jar task, otherwise I likely would just have posted a patch when I filed the bug.