You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/12/12 14:16:00 UTC
[jira] [Closed] (FLINK-30372) dependencyManagement bom for flink-dist
[ https://issues.apache.org/jira/browse/FLINK-30372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-30372.
------------------------------------
Resolution: Duplicate
This is essentially a duplicate of FLINK-29866 which tries to address the same issue, but in a different way.
> dependencyManagement bom for flink-dist
> ---------------------------------------
>
> Key: FLINK-30372
> URL: https://issues.apache.org/jira/browse/FLINK-30372
> Project: Flink
> Issue Type: New Feature
> Components: API / Core
> Reporter: James Z.M. Gao
> Priority: Major
>
> The flink-dist and other artifacts shipped within the prebuilt .tgz archives should be depended with the 'provided' scope when developing a flink app. But many artifacts are shaded directly or indirectly, and not clear to a flink app developer.
> Can we publish a new pom in bom style for org.apache.fink:flink-dist with only <dependencyManagement> section, which declares all the shaded or shipped dependencies with 'provided' or 'test' scopes. Then we can import this pom when in the app pom like this:
>
> {noformat}
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.apache.flink</groupId>
> <artifactId>flink-dist-bom</artifactId>
> <version>1.16.0</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)