[
https://issues.apache.org/jira/browse/THRIFT-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458919#comment-16458919
]
ASF GitHub Bot commented on THRIFT-4532:
----------------------------------------
jeking3 commented on issue #1541: THRIFT-4532: Do not update previously
generated output files if the contents have not changed
URL: https://github.com/apache/thrift/pull/1541#issuecomment-385504032
Hi, sorry I just switched jobs so my time here has been lower than normal
the last couple weeks. I would recommend documenting this as a breaking change
for anyone who has written their own compiler output module. Problem is that I
don't see a good place to document breaking changes outside language-specific
readme file. Documenting breaking changes has not been a strong suit for the
project; while I'd love to improve it, perhaps for this it isn't necessary. I
restarted the two travis failing build jobs for you.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Avoid updating Thrift compiler generated code if the output has not changed
> ---------------------------------------------------------------------------
>
> Key: THRIFT-4532
> URL: https://issues.apache.org/jira/browse/THRIFT-4532
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (General)
> Affects Versions: 0.11.0
> Reporter: Buğra Gedik
> Priority: Minor
> Fix For: 0.12.0
>
>
> We would like to contribute an improvement to the Thrift compiler that would
> avoid regenerating target file(s) if they are going to be exactly the same as
> the ones already present in the same place. This will help when running the
> Thrift compiler in our build, especially in recursive mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
