Second part of a story is to format old code base to match current format and change config of maven-checkstyle-plugin to match new format.
After code is formatted this should be changed in checkstyle.xml file:
After this change maven build will fail on validate goal if code does not follow google standard.
Also update from @dsmf - please also update PMD rule to match max length of a comment size:
Acceptance Criteria
Old code is formatted to match google java code standard
checkstyle.xml is adapted to new format so any violation of it's rules will result in failed build
update pmd rules to match new code formatting settings
First part of a story has covered preparation for code formatting settings including plugin configuration to support auto-format code to match google standard. https://github.com/eclipse-tractusx/item-relationship-service/issues/319
Second part of a story is to format old code base to match current format and change config of
maven-checkstyle-plugin
to match new format. After code is formatted this should be changed incheckstyle.xml
file:After this change maven build will fail on![image](https://github.com/eclipse-tractusx/item-relationship-service/assets/148042911/e8488c7a-a4a1-42f5-a377-565c32266f19)
validate
goal if code does not follow google standard. Also update from @dsmf - please also update PMD rule to match max length of a comment size:Acceptance Criteria
checkstyle.xml
is adapted to new format so any violation of it's rules will result in failed build