Lines Matching +full:runtime +full:- +full:versions
9 - The timing of underlying client-server communication
10 - Request and response message headers
11 - Verbose messages in underlying dependency libraries
19 # -Djava.util.logging.config.file=path/to/logging.properties
21 java.util.logging.SimpleFormatter.format=%1$tF %1$tT,%1$tL %4$-8s %3$-50s - %5$s %6$s%n
23 # --- ConsoleHandler ---
28 # --- Specify logging level for certain packages ---
41 and run your application with `-Djava.util.logging.config.file=path/to/logging.properties`
49 the FINE-level logging in your console. Example output:
52 2023-04-05 13:03:01,761 FINE com.google.auth.oauth2.DefaultCredentialsProvider - Attempting to…
53 2023-04-05 13:03:01,847 FINE io.grpc.ManagedChannelRegistry - Unable to fin…
75 …Exception: ALPN is not configured properly. See https://github.com/grpc/grpc-java/blob/master/SECU…
78 …ogleapis/google-cloud-java/tree/master/google-cloud-util/google-cloud-compat-checker) to see if yo…
79 - You are not on a [supported platform](https://github.com/googleapis/google-cloud-java/#supported-…
80 - There are classpath conflicts with `netty`.
81 - Or, you are seeing any of the conflicts specified in [gRPC Troubleshooting guide](https://github.…
85 These errors are usually caused by having multiple versions or conflicting versions of the same dep…
86 Usually these dependency conflicts occur with `guava` or `protobuf-java`.
89 - Multiple versions of the same transitive dependency in the dependency tree
90 - Your runtime classpath has different versions of dependencies than what you specified in the build
93 and `google-cloud-java` uses Guava version 30.0,
94 then `google-cloud-java` could be using Guava methods that don't exist in Guava 19.0,
97 Similarily, if your classpath has an older version of `protobuf-java`,
98 but `google-cloud-java` requires a newer version,
99 …then you might see `NoClassDefFoundError` that fails to initialize `google-cloud-java` classes. Fo…
107 Check the dependency tree to see if you have multiple versions of the same dependencies:
113 Look for versions of potentially conflicting dependencies like `guava`, `protobuf-java`, etc.
115 If you experience the error only during runtime, then your runtime environment
116 might be introducing conflicting JARs into your runtime classpath. A typical case
118 has conflicting versions `netty`, `guava`, or `protobuf-java` JARs in the classpath.
123 …forcer Rule](https://github.com/GoogleCloudPlatform/cloud-opensource-java/tree/master/enforcer-rul…
129 <artifactId>maven-enforcer-plugin</artifactId>
130 <version>3.0.0-M3</version>
134 <artifactId>linkage-checker-enforcer-rules</artifactId>
140 <id>enforce-linkage-checker</id>
141 <!-- Important! Should run after compile -->
157 There is no way to detect runtime classpath conflicts though. You need to be fully
158 aware of which JARs/classes are included in the runtime classpath
165 - If you have control over the dependency tree, upgrade
169 - If you can't modify and push new versions of your dependencies, import
170 `com.google.cloud:libraries-bom:25.1.0` (or a more recent version) and use that to
171 select consistent dependency versions. This is the easiest route.
172 For example, this is how you can depend on consistent versions of Guava and
173 `com.google.cloud:google-cloud-storage` without explicitly setting the version of either one:
181 <artifactId>libraries-bom</artifactId>
192 <artifactId>google-cloud-storage</artifactId>
203 - If changing dependency versions causes other failures,
204 consider [shading dependencies](https://maven.apache.org/plugins/maven-shade-plugin/)
205 that conflict with `google-cloud-java`.
207 For example, to shade `guava` and `protobuf-java`:
212 <artifactId>maven-shade-plugin</artifactId>
223 <!-- move protobuf to a shaded package -->
228 <!-- move Guava to a shaded package -->