vtutrinov commented on PR #5668: URL: https://github.com/apache/ozone/pull/5668#issuecomment-1909804555
> > > > ...once my question about the proto.lock will be answered > > > > > > > > > Sorry, I didn't see your question, which question are you referring to? > > > > > > @ivandika3 the question was from @adoroszlai - https://github.com/apache/ozone/pull/5668/files/48a1af2d2a82ab6c4780b2fb88502530ddf33362#r1464366194 > > I didn't see any question either. The notice from @adoroszlai was: > proto.lock should not be updated as part of the PR. The reason for having this file is to ensure backwards compatibility of any changes to .proto definitions. Lock files are used as the reference against which proto definitions are validated. My reply to the notice above was: > How should we resolve the compatibility check failure in a maven build if the proto.lock won't be updated? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
