XComp commented on code in PR #22996:
URL: https://github.com/apache/flink/pull/22996#discussion_r1263635725


##########
flink-rpc/flink-rpc-akka/src/main/resources/META-INF/NOTICE:
##########
@@ -8,25 +8,24 @@ This project bundles the following dependencies under the 
Apache Software Licens
 
 - com.hierynomus:asn-one:0.5.0
 - com.typesafe:config:1.4.2
-- com.typesafe:ssl-config-core_2.12:0.4.3
-- com.typesafe.akka:akka-actor_2.12:2.6.20
-- com.typesafe.akka:akka-remote_2.12:2.6.20
-- com.typesafe.akka:akka-pki_2.12:2.6.20
-- com.typesafe.akka:akka-protobuf-v3_2.12:2.6.20
-- com.typesafe.akka:akka-slf4j_2.12:2.6.20
-- com.typesafe.akka:akka-stream_2.12:2.6.20
+- com.typesafe:ssl-config-core_2.12:0.6.1

Review Comment:
   Were these other dependencies updated as transitive dependencies of Pekko? 
:thinking: 



##########
flink-rpc/flink-rpc-akka/src/main/resources/META-INF/NOTICE:
##########
@@ -8,25 +8,24 @@ This project bundles the following dependencies under the 
Apache Software Licens
 
 - com.hierynomus:asn-one:0.5.0
 - com.typesafe:config:1.4.2
-- com.typesafe:ssl-config-core_2.12:0.4.3
-- com.typesafe.akka:akka-actor_2.12:2.6.20
-- com.typesafe.akka:akka-remote_2.12:2.6.20
-- com.typesafe.akka:akka-pki_2.12:2.6.20
-- com.typesafe.akka:akka-protobuf-v3_2.12:2.6.20
-- com.typesafe.akka:akka-slf4j_2.12:2.6.20
-- com.typesafe.akka:akka-stream_2.12:2.6.20
+- com.typesafe:ssl-config-core_2.12:0.6.1
 - io.netty:netty:3.10.6.Final
 - org.agrona:agrona:1.15.1
+- org.apache.pekko:pekko-actor_2.12:1.0.0-RC2
+- org.apache.pekko:pekko-remote_2.12:1.0.0-RC2
+- org.apache.pekko:pekko-pki_2.12:1.0.0-RC2
+- org.apache.pekko:pekko-protobuf-v3_2.12:1.0.0-RC2
+- org.apache.pekko:pekko-slf4j_2.12:1.0.0-RC2
+- org.apache.pekko:pekko-stream_2.12:1.0.0-RC2

Review Comment:
   ~RC2 needs to be removed~



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