Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3466

Define proper Narayana checkstyle ruleset that aligns with the team practices

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 5.12.0.Final
    • 5.11.1.Final
    • Documentation
    • None

    Description

      Until now the Narayana project uses WildFly checkstyle config - https://github.com/wildfly/wildfly-checkstyle-config

      That's pretty good but the rules do not cover some code style rules that we are used to use in codebase. For example the WildFly style do not enforce a space between operand and operator or between parentheses '){' is fine as well as ') {'.

      We should create our own codestyle rules which can be adapted to our needs.

      Attachments

        Issue Links

          duplicates

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-3425 Create Narayana specific coding style instead of using not much restrictive WFLY one

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3476 Maven Checkstyle plugin fails because of dependency

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: