Excluding folder to solve lines limit

  • ALM used (Maven command from local Machine, but have Bitbucket Cloud subscription)
  • CI system used (Team City)
  • Scanner command used when applicable (mvn verify org.sonarsource.scanner.maven:sonar-maven-plugin:sonar -Dsonar.projectKey=XXX)
  • Languages of the repository: Java
  • Error observed: This analysis will make your organization \XXXX to reach the maximum allowed lines limit (having 144151 lines).

Can you confirm whether exclusion of sudden folders as Test, Source and Target will solve the Limit issue.

Any updates in this Ticket.


Per the FAQ

I created a topic, when can I expect a response?

This is an open community with people volunteering their free time to provide assistance. We’re eager to contribute to the community, but you are not guaranteed a fast response.

Be patient

  • Wait a few days before bumping a topic that hasn’t received a response.
  • Do not @name mention individuals not involved in the topic.

Contribute as much as you expect to receive

  • Contribute to the community (helping others) as much as you expect to receive help.

It is not a replacement for more structured support

  • If you need SLAs, guaranteed response, privacy, SonarSource also offers Commercial Support.

Regarding your initial question, excluding tests from analysis - as tests - will have no impact on your license lines of code, since tests are never counted toward your license usage. If they’re being counted as source code, then that’s a different problem.

In target there shouldn’t be anything that would be analyzed. If there is, then yes, certainly. Exclude it.

Excluding source files/directories will decrease your license lines of code. But that should, of course, be done with caution, since analyzing your source code is the whole point.


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.