Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-43

Builds Fail with errors relating to JVM memory settings when entries for clover are put in a projects parent pom file.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • won't fix
    • None
    • Maven plugin for clover version 3.0 beta 5 , bamboo war version 1.2.1 build 409.

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      We have created an organisational pom file which includes a profile called bamboo which contains the entries required to use clover. When we run a build in bamboo we set the maven goal to test site -Pbamboo, so that the profile is activated. The idea behind this is so that bamboo can generate clover reports for all projects and developers can still build projects on their workstations, without the need for clover licenses on every workstation, only a single license on the development server on which bamboo runs would be required.

      However, since upgrading to version 3.0 beta 5 of the maven clover plug in, builds fail when the above approach is taken, but build successfully when the clover entries are put directly into the project pom file.

            [CLOV-43] Builds Fail with errors relating to JVM memory settings when entries for clover are put in a projects parent pom file.

            No work has yet been logged on this issue.

              tom@atlassian.com Tom Davies
              1d6c5a7445c5 Peter Johnstone
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: