[
https://issues.apache.org/jira/browse/BEAM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179928#comment-17179928
]
Beam JIRA Bot commented on BEAM-1278:
-------------------------------------
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.
> Use checkstyle on everything
> ----------------------------
>
> Key: BEAM-1278
> URL: https://issues.apache.org/jira/browse/BEAM-1278
> Project: Beam
> Issue Type: Task
> Components: build-system
> Reporter: Benson Margulies
> Priority: P2
> Labels: stale-P2
>
> It is desirable to run checkstyle on everything, including poms.
> The problem is that the checkstyle rules come from the classpath, and that
> you can't have a dependency at the top level on a module of the project.
> There are some alternatives:
> * As of Maven 3.x, the entire checkstyle rule set can be inlined in the pom.
> A cure worse than the disease? You decide.
> * What other projects *(e.g. CXF) do is separately release an artifact with
> checkstyle and PMD rules. You can do that with a new github repo, or using
> the necessary Maven magic to have a subdirectory which is _not_ a module and
> contains a releasable pom. (It's all in how you configure the Maven release
> plugin).
> * You can just arrange for the rules to be at a URL. A URL, for example, to a
> specific version of a specific file on github?
> [[email protected]]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
