zentol opened a new pull request #17518:
URL: https://github.com/apache/flink/pull/17518


   This PR removes the Scala dependencies from `flink-streaming-java` and 
`flink-cep.`
   Nothing should change for users when actually running stuff in production.
   
   However, this _does_ change the dependency tree, and can for example cause 
issues for Scala API users which never had a direct dependency but relied on 
flink-streaming-java instead.
   
   As a result a large number of modules are losing their scala suffix:
   ```
   flink-cep
   flink-clients
   flink-clients
   flink-connector-elasticsearch-base
   flink-connector-elasticsearch5
   flink-connector-elasticsearch6
   flink-connector-elasticsearch7
   flink-connector-gcp-pubsub
   flink-connector-hbase-1.4
   flink-connector-hbase-2.2
   flink-connector-hbase-base
   flink-connector-jdbc
   flink-connector-kafka
   flink-connector-kinesis
   flink-connector-nifi
   flink-connector-pulsar
   flink-connector-rabbitmq
   flink-connector-testing
   flink-connector-twitter
   flink-connector-wikiedits
   flink-container
   flink-distributed-cache-via-blob-test
   flink-dstl-dfs
   flink-gelly
   flink-hadoop-bulk
   flink-kubernetes
   flink-parent-child-classloading-test-lib-package
   flink-parent-child-classloading-test-program
   flink-queryable-state-test
   flink-runtime-web
   flink-sql-connector-elasticsearch6
   flink-sql-connector-elasticsearch7
   flink-sql-connector-hbase-1.4
   flink-sql-connector-hbase-2.2
   flink-sql-connector-kafka
   flink-sql-connector-kinesis
   flink-sql-connector-rabbitmq
   flink-state-processor-api
   flink-statebackend-rocksdb
   flink-streaming-java
   flink-table-api-java-bridge
   flink-test-utils
   flink-walkthrough-common
   flink-yarn
   flink-streaming-java
   ```


-- 
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...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to