The current version of the cccc plugin allows the user to specify the cccc output file that will be processed to generate the report. While this is good enough for most cases where all files in the project source code are related to some degree, there are many cases where such a processing is not sufficient.

The project I'm building is made of multiple parts which are not related to each other:

• vendor1/project1
• vendor1/project2
• vendor2/project1
• vendor3/project1

The project themselves are completely unrelated (let's say they build executables for a specific target). I can run cccc on all the source code, but this will produce a single output file which will contain informations that are not related to each other. In our build process, cccc is ran for every project, and we have as many .cccc directory as the number of different projects.

But then, the plugin itself cannot be used to get the generated information back, as only one of these directories can be processed. To work around this limitation I currently use one job per project that I want to analyse. With a small number of projects, this solution is workable. But as the number of project grows, it begins to be painful.