Skip to content

Conversation

@He-Pin
Copy link
Member

@He-Pin He-Pin commented Dec 14, 2025

(cherry picked from commit f735cca)

(cherry picked from commit f735cca)

# Conflicts:
#	stream/src/main/scala-2.13/org/apache/pekko/stream/javadsl/CollectionUtil.scala
#	stream/src/main/scala/org/apache/pekko/stream/javadsl/Flow.scala
#	stream/src/main/scala/org/apache/pekko/stream/javadsl/Sink.scala
#	stream/src/main/scala/org/apache/pekko/stream/javadsl/Source.scala
#	stream/src/main/scala/org/apache/pekko/stream/javadsl/SubFlow.scala
#	stream/src/main/scala/org/apache/pekko/stream/javadsl/SubSource.scala
#	stream/src/main/scala/org/apache/pekko/stream/javadsl/Tcp.scala
@He-Pin He-Pin added the t:stream Pekko Streams label Dec 14, 2025
@He-Pin He-Pin added this to the 1.5.0 milestone Dec 14, 2025
@He-Pin He-Pin requested a review from pjfanning December 14, 2025 11:55
@He-Pin
Copy link
Member Author

He-Pin commented Dec 15, 2025

@pjfanning This is ready for 1.5.x

@pjfanning
Copy link
Member

I can half understand backporting #2583 but I don't see any benefit to backporting this.

@pjfanning
Copy link
Member

In particular, I would be worried that some pekko module uses CollectionUtil. We have broken releases before by removing classes.
So removing any classes in 1.x is a no for me.
-1.

If I get outvoted on this, the one thing that is a blocker for me is removing the class. We could backport the code changes without deleting the class.

But my preference is not to bother. 2.0.0 will be finished faster if we don't waste so much time on 1.x.

@He-Pin
Copy link
Member Author

He-Pin commented Dec 15, 2025

OK isee

@He-Pin He-Pin closed this Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t:stream Pekko Streams

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants