[
https://issues.apache.org/jira/browse/APEXCORE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090763#comment-15090763
]
ASF GitHub Bot commented on APEXCORE-268:
-----------------------------------------
Github user amberarrow commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/199#issuecomment-170275846
Since command line parameter definitions override those in pom.xml,
developers can use aliases to toggle these flags in any desired way, for
example:
* alias vfy-none="mvn verify -Dcheckstyle.console=false
-Dcheckstyle.consoleOutput=false -DskipTests"
* alias vfy-both="mvn verify -Dcheckstyle.console=true
-Dcheckstyle.consoleOutput=true -DskipTests"
* alias vfy-cc="mvn verify -Dcheckstyle.console=true
-Dcheckstyle.consoleOutput=false -DskipTests"
* alias vfy-co="mvn verify -Dcheckstyle.console=false
-Dcheckstyle.consoleOutput=true -DskipTests"
We can then use these aliases:
vfy-cc > cc.txt
vfy-co > co.txt
vfy-none > none.txt
vfy-both > both.txt
And finally examine the results:
grep -ic warn both.txt none.txt co.txt cc.txt
both.txt:1270
none.txt:0
co.txt:1268
cc.txt:2
grep -ic error both.txt none.txt co.txt cc.txt
both.txt:6564
none.txt:2
co.txt:3283
cc.txt:3283
(I'm not arguing for the decision to go one way or the other, just
suggesting that developers can cope with either with minimal inconvenience).
> 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)
