[
https://issues.apache.org/jira/browse/FLINK-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495056#comment-16495056
]
ASF GitHub Bot commented on FLINK-9464:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/6093
I agree that the scope and version should be set via dependency management.
If we no longer use the category annotations, then we should indeed be able to
remove the general `flink-test-utils-junit` dependency. I'll rework the PR to
do that.
> Clean up pom files
> ------------------
>
> Key: FLINK-9464
> URL: https://issues.apache.org/jira/browse/FLINK-9464
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
> Fix For: 1.6.0
>
>
> Some of Flink module's {{pom.xml}} files contain unnecessary or redundant
> information. For example, the {{flink-clients}} {{pom.xml}} specifies twice
> the {{maven-jar-plugin}} in the build section. Other modules explicitly
> specify the version and scope of the {{flink-test-utils-junit}} module which
> is managed by the parent's dependency management section. I propose to clean
> these things up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
