summaryrefslogtreecommitdiffstats
path: root/checkstyle/src/main/resources/onap-checkstyle/onap-java-style.xml
AgeCommit message (Collapse)AuthorFilesLines
2019-12-09Update checkstyle rules to exclude methodsliamfallon1-0/+3
Checkstyle rules updated to: 1) allow getters and setters not to have javadoc 2) allow methods with less than 2 lines to not have javadoc 3) allow protected and private methods not to have javadoc 4) allow methods with names beginning with test|before|after not to have javaodc Issue-ID: INT-1395 Change-Id: I570cd90034c7b20d45a7e5a6ecacacdef80876a1 Signed-off-by: liamfallon <liam.fallon@est.tech>
2019-12-06Upgrade oparent to checkstyle 8.27liamfallon1-5/+9
Checkstyle 8.27 introduces incompatible changes in the checkstyle rule definition xml file. The latest Eclipse checkstyle plugin (version 8.26) uses this new checkstyle xml rule format. This change brings in the checkstyle 8.27 rule formats into oparent. Issue-ID: INT-1395 Change-Id: I453120e5cc95fa2e30a5d2f24083fd030e960a01 Signed-off-by: liamfallon <liam.fallon@est.tech>
2019-02-07Fix checkstyle build and xmlPamela Dragosh1-1/+0
The XML for onap-java-code style has a bug identified by Eclipse. The maxLineLength field is not allowed. In addition, not sure how any jobs work already, the sourceDirectory appends and extra "src/main/java" to the path so some builds don't always find the correct source files to generate warnings. The plugin is a bit flaky and sometimes seems to find the java files, while other times it does not. So some checkstyle warnings are not generated. Change-Id: Ia07065a0d0df1429643680cb5bd70b5ec13bebde Issue-ID: TSC-71 Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2017-08-21Refactor oparent for independent versioningGary Wu1-0/+220
Change-Id: I543f394b360b6926986f33b48bef4b3355363beb Issue-id: INT-103 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>