[
https://issues.apache.org/jira/browse/AVRO-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876545#action_12876545
]
John Yu commented on AVRO-150:
------------------------------
Hello,
Just to double check and clarify the following two things.
First, we will do the checking of timestamp in
SpecificCompiler#compileToDestination() and write nothing when the existing
file is newer. Out of curiosity, couldn't we write what we have into disk,
since we have already spent the computation power to parse the protocol and
schema? Or would doing that cause logical problems or because writing to disk
could also be very resource intensive in this case?
Second, in the comment you have mentioned "if no new files are written it
should prevent subsequent javac and jar processing." We are thinking that
while the protocols and schemas may not have changed, other java source files
might have. So we are not sure if we should really prevent the javac and jar
from running if no new parsing for avpr/avsc has happened. In addition, since
we can't assume the order in which the tasks are called in Ant, would it be ok
if we stop Ant right then and there?
Thanks!
> Ant tasks re-generate code even if it's up-to-date
> --------------------------------------------------
>
> Key: AVRO-150
> URL: https://issues.apache.org/jira/browse/AVRO-150
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.2.0
> Reporter: Doug Cutting
> Attachments: AVRO-150.patch
>
>
> The Ant tasks for Java's protocol and schema should skip generation when the
> generated files are newer than their source.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
