cshannon commented on issue #3086: URL: https://github.com/apache/accumulo/issues/3086#issuecomment-1320300883
> I don't understand how # 1 is a concern if the code in that directory is deleted and then regenerated at release. Well one issue could be is that there would be a long delay from when the issue was introduced vs catching it (if we don't do releases for a long time). So we could be potentially developing/testing against something that is not what will be generated later. And (in the unlikely change) there was something introduced that was malicious it would be loaded on any developer machines still. I wonder if there is some way to auto detect changes to the directory when unintentional (ie we didn't run thrift). Not sure if there is some way to mark a directory as read only in Git or use some kind of git post commit hook or add something in maven to detect changes, etc. Maybe we could do something with Jenkins/CI to detect changes and report so we catch it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
