abgm commented on issue #25746:
URL: https://github.com/apache/beam/issues/25746#issuecomment-1471856879

   
   This is a recursive issue on Beam.
   Can we create version of this lib without it be a uber-jar/fat-jar? ( we can 
even create a different artifactId )
   
   I'm not sure why the lib needs to be an uber-jar. But to be used on beam we 
shouldn't need it to be uber-jar. And that way the clients can control the 
version of the dependencies.
   
   This is the contents of the uber-jar.
   ```
   com.google.api.grpc_proto-google-common-protos   2.9.0
   com.google.auth_google-auth-library-credentials  1.4.0
   com.google.code.gson_gson                        2.9.0
   com.google.errorprone_error_prone_annotations    2.14.0
   com.google.protobuf_protobuf-java                3.21.1
   com.google.protobuf_protobuf-java-util           3.21.1
   io.netty_netty-buffer                            4.1.77
   io.netty_netty-codec                             4.1.77
   io.netty_netty-codec-http                        4.1.77  
   io.netty_netty-codec-http2                       4.1.77
   io.netty_netty-codec-socks                       4.1.77  
   io.netty_netty-common                            4.1.77
   io.netty_netty-handler                           4.1.77
   io.netty_netty-handler-proxy                     4.1.77
   io.netty_netty-resolver                          4.1.77
   io.netty_netty-tcnative-boringssl-static         2.0.53
   io.netty_netty-tcnative-classes                  2.0.53  
   io.netty_netty-transport                         4.1.77
   io.netty_netty-transport-classes-epoll           4.1.77
   io.netty_netty-transport-native-epoll            4.1.77  
   io.netty_netty-transport-native-unix-common      4.1.77  
   org.apache.beam_grpc-1_48_1                      0.1  
   org.codehaus.mojo_animal-sniffer-annotations     1.21
   ```


-- 
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]

Reply via email to