[
https://issues.apache.org/jira/browse/APEXCORE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091422#comment-15091422
]
ASF GitHub Bot commented on APEXCORE-268:
-----------------------------------------
Github user chandnisingh commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/199#issuecomment-170428652
@vrozov Couple of reasons why I am insisting on starting a discussion on dev
1. There is no consensus here. So the change in the pull request is Not
something which everyone has agreed on. From what I see in these cases, is that
developers are required to start a discussion so that a consensus is reached.
2. Here is a subject of a pull request email.
`[GitHub] incubator-apex-core pull request: APEXCORE-268 #resolve #comment
f...`
These subject lines doesn't help in capturing everyone's attention.
Developers participate in check-style related changes actively so why
inhibit it?
I don't see any harm in starting a discussion about this so that we can
reach a consensus by involving the community.
> Fix existing checkstyle violations in common module
> ---------------------------------------------------
>
> Key: APEXCORE-268
> URL: https://issues.apache.org/jira/browse/APEXCORE-268
> Project: Apache Apex Core
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
