[
https://issues.apache.org/jira/browse/FLINK-36316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferenc Csaky resolved FLINK-36316.
----------------------------------
Resolution: Fixed
[8302e12|https://github.com/apache/flink/commit/8302e12e7842726a442d07bc80e4c0a9e1a319f4]
in master
> Move PortRange util to flink-core
> ---------------------------------
>
> Key: FLINK-36316
> URL: https://issues.apache.org/jira/browse/FLINK-36316
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Reporter: Ferenc Csaky
> Assignee: Arkadiusz Dankiewicz
> Priority: Minor
> Fix For: 2.0-preview
>
>
> The only thing what the {{PortRange}} utility does is wrapping a
> {{NetUtils#getPortRangeFromString}} to help keeping track of the original
> config string.
> Considering this, it makes sense to move it to the same module, as currently
> {{PortRange}} is in {{flink-runtime}}, which limits its usage to that module,
> or requiring to add it as a dependency, which is not a very good option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
