[
https://issues.apache.org/jira/browse/BEAM-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131685#comment-17131685
]
Beam JIRA Bot commented on BEAM-4103:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Invert JavaNature configuration
> -------------------------------
>
> Key: BEAM-4103
> URL: https://issues.apache.org/jira/browse/BEAM-4103
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Kenneth Knowles
> Priority: P2
> Labels: gradle, stale-P2
>
> Today the applyJavaNature method demonstrates a significant programming and
> build config anti-pattern: one giant method with unclear/no spec and some
> flags to tweak what it does, that can only really be understood by reading
> its full code.
> Instead, best practice would be to separate the functionality controlled by
> each flag into a block that a module can call. It is not wrong to pass
> configuration parameters, but in this case that's not really what is going on.
> Since the flags are "on by default" and serve to suppress things like
> findbugs, this just means breaking out the findbugs into a separate bit. We
> can always also have a convenience three-liner that calls the basics, calls
> findbugs, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
