Uploaded image for project: 'SonarQube Scanner for Maven'
  1. SonarQube Scanner for Maven
  2. MSONAR-106

Out of memory when analyzing a project with many pom properties and many modules

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Because of the strategy used to name modules (parentKey + groupId+artifactId) when a project have a combination of:

      • long groupId
      • deeply nested modules
      • lots of pom properties

      this result in having tons of SQ properties with very long keys. Several ideas:

      • we should apply a new strategy for modules internal key (for example use Maven moduleId instead of groupId:aftifactId).
      • use relative paths when possible
      • don't repeat property on a module when it is inherited/same than parent since SQ will handle this automatically

      See http://sonarqube.15.x6.nabble.com/Memory-Issues-4-3-td5029958.html

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              henryju OLD - Julien HENRY
              Reporter:
              henryju OLD - Julien HENRY
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: