SonarQube
  1. SonarQube
  2. SONAR-1227

Ability to specify the Cobertura maxmem property in the Settings page

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      This property specifies the maximum memory to pass to JVM of Cobertura processes.

        Activity

        Hide
        Freddy Mallet added a comment -

        In fact this property is only used to generate the xml report but not to specify the memory to be used by the forked Surfire process. As we have never encountered such memory limitation, I'm closing this issue with resolution "won't fix".

                ReportTask task = new ReportTask();
                ...
                // task specifics
                task.setMaxmem( maxmem );
                task.setOutputDirectory( outputDirectory );
                task.setCompileSourceRoots( getCompileSourceRoots() );
        
        Show
        Freddy Mallet added a comment - In fact this property is only used to generate the xml report but not to specify the memory to be used by the forked Surfire process. As we have never encountered such memory limitation, I'm closing this issue with resolution "won't fix". ReportTask task = new ReportTask(); ... // task specifics task.setMaxmem( maxmem ); task.setOutputDirectory( outputDirectory ); task.setCompileSourceRoots( getCompileSourceRoots() );
        Hide
        Simon Brandhof added a comment -

        Hi Freddy,
        The parameter maxmem is not only used for the report goal. See AbstractCoberturaMojo

        Show
        Simon Brandhof added a comment - Hi Freddy, The parameter maxmem is not only used for the report goal. See AbstractCoberturaMojo
        Hide
        molpet khedi added a comment -

        In my case the cobertura:instrument goal fails with a "outOfMemoryError" and the cobertura.maxmem seems to be useless in this case. Is there a turnaround to increase the java heap memory (like with the arg -Xmx) when launching the new JVM for this goal?

        Show
        molpet khedi added a comment - In my case the cobertura:instrument goal fails with a "outOfMemoryError" and the cobertura.maxmem seems to be useless in this case. Is there a turnaround to increase the java heap memory (like with the arg -Xmx) when launching the new JVM for this goal?
        Hide
        Freddy Mallet added a comment -

        Could you send an email to the Sonar User mailing list with your error Maven log file ? Thanks

        Show
        Freddy Mallet added a comment - Could you send an email to the Sonar User mailing list with your error Maven log file ? Thanks
        Hide
        Evgeny Mandrikov added a comment -

        You should use property "sonar.cobertura.maxmen" (also see SONAR-2897) or specify maxmem directly in pom.xml for cobertura-maven-plugin. And of course in case of problems - it's better to use Users Mailing List.

        Show
        Evgeny Mandrikov added a comment - You should use property "sonar.cobertura.maxmen" (also see SONAR-2897 ) or specify maxmem directly in pom.xml for cobertura-maven-plugin. And of course in case of problems - it's better to use Users Mailing List.

          People

          • Assignee:
            Freddy Mallet
            Reporter:
            Freddy Mallet
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: