This is causing us a problem as well. When we publish code, we look at the generated code and only copy over what the changes are. Any package with a groovy class in it always shows as modified and therefore gets included.
Just taking the timestamp from the source file (where applicable) would be sufficient for us. However, it seems to put the timestamp of when the file was compiled...therefore it is always different. Having a command line option to force the timestamp to either not exist, or to a specific time would work also.
Is there any work-around for this?
Mark