[
https://issues.apache.org/jira/browse/FLINK-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986223#comment-15986223
]
ASF GitHub Bot commented on FLINK-4370:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2352
@greghogan That could definitely be done.
I was initially trying to do a trick: Check in the inspection profile that
we want (in terms of what qualifies as a warning) but also add it to .gitignore
so that any customization on a developer's end is not committed back.
That way we would set up everyone with the common base and still allow for
customization.
> Offer a default IntelliJ inspection profile with Flink
> ------------------------------------------------------
>
> Key: FLINK-4370
> URL: https://issues.apache.org/jira/browse/FLINK-4370
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
>
> We can commit an inspection profile under {{.idea/inspectionProfiles}} which
> should be automatically picked up when the code is checked out and imported
> into IntelliJ
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
