[
https://issues.apache.org/jira/browse/FLINK-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093195#comment-16093195
]
ASF GitHub Bot commented on FLINK-4499:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/4367
License isn't an issue since it's only used during the build:
CAN APACHE PROJECTS DISTRIBUTE COMPONENTS UNDER PROHIBITED LICENSES?
https://www.apache.org/legal/resolved.html#prohibited
Apache projects cannot distribute any such components. This means that no
source code can be from Category X and that any convenience binaries produced
may not include such contents. As with the previous question on platforms, the
component can be relied on if the component's license terms do not affect the
Apache product's licensing. For example, using a GPL'ed tool during the build
is OK, however including GPL'ed source code is not.
> Introduce findbugs maven plugin
> -------------------------------
>
> Key: FLINK-4499
> URL: https://issues.apache.org/jira/browse/FLINK-4499
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Ted Yu
> Assignee: Suneel Marthi
>
> As suggested by Stephan in FLINK-4482, this issue is to add
> findbugs-maven-plugin into the build process so that we can detect lack of
> proper locking and other defects automatically.
> We can begin with small set of rules.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
