bdw-g commented on PR #673: URL: https://github.com/apache/commons-compress/pull/673#issuecomment-2930647891
Hi, thanks for your response. Google maintains internal 'forks' for all third party libraries that it uses, although we try to keep them as close to upstream as possible. We're also not using maven for building, but blaze (bazel externally). We used to build the library wholistically, but that has the problems we've discussed. Because blaze works on a source code level, we'd really prefer it if javac could compile the parts independently. This is also - to be quite frank - much more reliable and transparent than relying on binary analysis, because the results of that can change undetected with the next source code change. But that's neither here nor there. As for providing engineering time, the truth is that maintaining third party libraries is a part-time obligation for a subset of googlers. I got rolled into it because there was a feature we just had to have at some point :-) but I don't see my team providing significant engineering resources in the near term. But I can discuss this internally with some of the other maintainers. Thanks again! -- 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: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
