grpc-java/netty/shaded
Eric Anderson 2cc24a9bda gradle: Remove version pinning from POMs
The pinning is unreliable in Maven and ignored by Gradle. I'm not at all
convinced that we are pinning/not pinning in appropriate projects. The
pinning also serves less of a purpose since we started encouraging the
BOM and grpc-netty-shaded. Netty's HTTP/2 API has also become somewhat
stable compared to its earlier history. If we notice an up-tick in
version skew, we can reinstate it.

The pinning is annoying in the build.gradle code and causes Maven/Gradle
to download the version list once a day, which can be troublesome to
users unaware of how to tell the tools to work offline.

It also opens our users to platform issues like seen in #10043
and #10086 where Maven Central's version list was incorrectly generated.
Or like #9664 where Gradle Plugin's repository caches packages from
JCenter but the version list is not as cachable so exposed us to JCenter
instability.

This fixes #8357, by way of "we think we won't worry any more." See
90db93b9 when it was originally introduced. And issues
like #8337, #3634.
2023-05-15 13:08:40 -07:00
..
src/testShadow/java/io/grpc/netty/shaded Migrate many usages of TestUtils.loadCert() to the public TlsTesting 2023-05-09 17:01:31 -07:00
BUILD.bazel all: Update netty to 4.1.77.Final and netty_tcnative to 2.0.53.Final (#9027) 2022-06-24 10:47:27 -07:00
build.gradle gradle: Remove version pinning from POMs 2023-05-15 13:08:40 -07:00