[
https://issues.apache.org/jira/browse/BEAM-4394?focusedWorklogId=116771&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-116771
]
ASF GitHub Bot logged work on BEAM-4394:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jun/18 04:46
Start Date: 28/Jun/18 04:46
Worklog Time Spent: 10m
Work Description: kennknowles commented on a change in pull request
#5797: [BEAM-4394] Spotless Java everywhere
URL: https://github.com/apache/beam/pull/5797#discussion_r198706423
##########
File path: sdks/java/build-tools/src/main/resources/beam/checkstyle.xml
##########
@@ -117,7 +117,9 @@ page at http://checkstyle.sourceforge.net/config.html -->
</module>
<!-- Check that paragraph tags are used correctly in Javadoc. -->
- <!-- <module name="JavadocParagraph"/> -->
+ <!--
+ TODO(https://issues.apache.org/jira/browse/BEAM-4670): re-enable after
fixing after spotless
Review comment:
I have a slight difference of opinion in that it drives me bananas when
people refer to tickets without the full URL for me to mindlessly copy/paste
:-). But I get what you mean - it is more readable to just have the identifier
rather than all the cruft.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 116771)
Time Spent: 2h 20m (was: 2h 10m)
> Consider enabling spotless java format throughout codebase
> ----------------------------------------------------------
>
> Key: BEAM-4394
> URL: https://issues.apache.org/jira/browse/BEAM-4394
> Project: Beam
> Issue Type: New Feature
> Components: build-system
> Reporter: Kenneth Knowles
> Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> "Spotless" can enforce - and automatically restore - automatic Java
> formatting. Whenever formatting is off, it tells a user the exact command to
> fix it.
> It isn't (just) about code layout, it is about automation. We have pretty
> strict style rules enforced by checkstyle. The most efficient way to fix up a
> file is with autoformat. But if the autoformat hits a bunch of irrelevant
> lines, that is annoying for a reviewer and obscures git blame.
> If we enforce autoformat all the time, then it makes sure that autoformatting
> a particular PR has minimal effects and is always safe to do.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
