Maven Checkstyle Plugin
  1. Maven Checkstyle Plugin
  2. MCHECKSTYLE-22

Ability to specify more than 1 check configuration file and file sets for each of these configurations

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      I'm using Eclipse Checkstyle Plug-in, and there's a functionnality I enjoy a lot: the ability to specify as many check configuration files as I want for a projet, and to tell which file sets those configurations should be run on.
      And as I use this functionnality extensively, I'd love to have it also in the Maven Checkstyle Plug-in :o)

      To get a look at what the Eclipse plugin does: http://eclipse-cs.sourceforge.net/advanced_file_sets.html

        Activity

        Hide
        Joakim Erdfelt added a comment -

        I was working on a ...

        <configuration>
        <configLocations>
        <configLocation>...</configLocation>
        <configLocation>...</configLocation>
        </configLocations>
        </configuration>

        ... concept earlier, but my attempts to 'merge' the configs together and run a single checkstyle run against the codebase was fruitless.

        Instead, I feel that multiple checkstyle runs against the codebase made the most sense.
        But that introduces the potential for different configurations for the other parts too.

        Course, in that case, you could just as well make multiple checkstyle plugin entries in your pom. (but that would require the ability to specify the report output filename and title in the project reports navigation links.)

        Show
        Joakim Erdfelt added a comment - I was working on a ... <configuration> <configLocations> <configLocation>...</configLocation> <configLocation>...</configLocation> </configLocations> </configuration> ... concept earlier, but my attempts to 'merge' the configs together and run a single checkstyle run against the codebase was fruitless. Instead, I feel that multiple checkstyle runs against the codebase made the most sense. But that introduces the potential for different configurations for the other parts too. Course, in that case, you could just as well make multiple checkstyle plugin entries in your pom. (but that would require the ability to specify the report output filename and title in the project reports navigation links.)
        Hide
        Joakim Erdfelt added a comment -

        I was working on a ...

        <configuration>
        <configLocations>
        <configLocation>...</configLocation>
        <configLocation>...</configLocation>
        </configLocations>
        </configuration>

        ... concept earlier, but my attempts to 'merge' the configs together and run a single checkstyle run against the codebase was fruitless.

        Instead, I feel that multiple checkstyle runs against the codebase made the most sense.
        But that introduces the potential for different configurations for the other parts too.

        Course, in that case, you could just as well make multiple checkstyle plugin entries in your pom. (but that would require the ability to specify the report output filename and title in the project reports navigation links.)

        Show
        Joakim Erdfelt added a comment - I was working on a ... <configuration> <configLocations> <configLocation>...</configLocation> <configLocation>...</configLocation> </configLocations> </configuration> ... concept earlier, but my attempts to 'merge' the configs together and run a single checkstyle run against the codebase was fruitless. Instead, I feel that multiple checkstyle runs against the codebase made the most sense. But that introduces the potential for different configurations for the other parts too. Course, in that case, you could just as well make multiple checkstyle plugin entries in your pom. (but that would require the ability to specify the report output filename and title in the project reports navigation links.)
        Hide
        Fabrice Bellingard added a comment -

        Well, I don't want to have multiple reports, but only one.
        So I don't know if that would be possible, but as you said, there could be multiple Checkstyle runs, one for each check configuration file associated to its File set. And the results would be gathered into one single report.

        Show
        Fabrice Bellingard added a comment - Well, I don't want to have multiple reports, but only one. So I don't know if that would be possible, but as you said, there could be multiple Checkstyle runs, one for each check configuration file associated to its File set. And the results would be gathered into one single report.

          People

          • Assignee:
            Unassigned
            Reporter:
            Fabrice Bellingard
          • Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated: