Howdy,
As mentioned in a previous message, my goal is to have some sources
recompiled after they were modified. The modification requires the
binary project information and therefore happens after the standard
compile phase.
As the recompile task copies the configuration from the default compile
task, I was originally running into the problem that Gradle was thinking
that no recompilation was necessary. I did not investigate why, but
simply disabled the up-to-date check for the output as there really is
no need to perform up-to-date checking here. This seemed to make things
work as expected. Until I realized that there is one additional factor: Ant.
The modification might be performed very fast, such that the time stamps
of the source files and the corresponding .class files are not
recognized as different by Ant. Ant applies some platform heuristics and
might assume a 1 sec timestamp resolution which is clearly not enough
for my use case.
I can workaround the problem (manually deleting the .class files in
question), but I wonder how you would assess the situation. Isn't the
additional Ant checking superfluous and only adds overhead, as Gradle
performs it's own logic and invokes the compile task only when deemed
necessary anyway? Are there plans to move away from Ant under the hood
to eliminate such idiosyncrasies?
Please let me know if you think the issue warrants a Jira. Thanks.
Cheers,
Marco
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
