Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7.2
    • Labels:
      None
    • Environment:
      maven 2.0
    • Number of attachments :
      1

      Description

      surefire-report reruns the tests. In my case this is not just annoying, but leads to a failure, as the VM (probably) is reused and leftovers from the first tests are (definitly) still present.

      I run maven with: clean package site

        Issue Links

          Activity

          Hide
          Luc Willems added a comment -

          is there a way to set the report-only options using
          the cli using -Dxxxxx.report-only=true ?

          this is would fix my automated builds of project sites .

          Show
          Luc Willems added a comment - is there a way to set the report-only options using the cli using -Dxxxxx.report-only=true ? this is would fix my automated builds of project sites .
          Hide
          Benjamin Bentmann added a comment -

          Luc, report-only is not an option/parameter but a plugin goal and these can in general not be directly activated via a property from the CLI. You can however add a profile to your POM that runs report-only and have this profile be activated via a system property.

          Show
          Benjamin Bentmann added a comment - Luc, report-only is not an option/parameter but a plugin goal and these can in general not be directly activated via a property from the CLI. You can however add a profile to your POM that runs report-only and have this profile be activated via a system property.
          Hide
          Luc Willems added a comment -

          indead , i was going to fast here

          i added the report-only option to ALL report entries in my multi module project. still some project rerun
          the complete project ( 20 modules , 3 levels of grandparent/parent/child)
          this is killing my builds and memory

          i also added this for the javadoc plugin because it was doing the same thing

          i basicly want to do "mvn clean deploy site-deploy" every night so we have new deployed artifacts and update project site after
          every (nightly) build cycle.

          for now , the site-deploy stuff is getting to complex because of all this issues

          Show
          Luc Willems added a comment - indead , i was going to fast here i added the report-only option to ALL report entries in my multi module project. still some project rerun the complete project ( 20 modules , 3 levels of grandparent/parent/child) this is killing my builds and memory i also added this for the javadoc plugin because it was doing the same thing i basicly want to do "mvn clean deploy site-deploy" every night so we have new deployed artifacts and update project site after every (nightly) build cycle. for now , the site-deploy stuff is getting to complex because of all this issues
          Hide
          Benjamin Bentmann added a comment -

          Luc, what you describe (forking the entire multi-module build by a single module) looks like unintended usage of aggregator goals. These are goals whose doc pages say "Executes as an aggregator plugin.".

          The goal report-only from the latest Surefire Report Plugin 2.4.3 does not work as as aggregator and hence should not cause you issues. As for the Javadoc Plugin, its latest release 2.5 includes those problematic aggregator goals. Unless you explicitly configured which report goals to execute, all reports from a plugin are executed. So be sure to setup the Javadoc Plugin as outlined in Selective Javadocs Reports and leave the *-aggregate goals out.

          Show
          Benjamin Bentmann added a comment - Luc, what you describe (forking the entire multi-module build by a single module) looks like unintended usage of aggregator goals. These are goals whose doc pages say "Executes as an aggregator plugin.". The goal report-only from the latest Surefire Report Plugin 2.4.3 does not work as as aggregator and hence should not cause you issues. As for the Javadoc Plugin, its latest release 2.5 includes those problematic aggregator goals. Unless you explicitly configured which report goals to execute, all reports from a plugin are executed. So be sure to setup the Javadoc Plugin as outlined in Selective Javadocs Reports and leave the *-aggregate goals out.
          Hide
          Kristian Rosenvold added a comment -

          Fixed with IT in r1062201.

          2.7.2 will be staged for testing in the next 24 hours12 or so, so if you're one of the numerous watchers of this issue you can contribute by testing the staged release.

          Show
          Kristian Rosenvold added a comment - Fixed with IT in r1062201. 2.7.2 will be staged for testing in the next 24 hours12 or so, so if you're one of the numerous watchers of this issue you can contribute by testing the staged release.

            People

            • Assignee:
              Kristian Rosenvold
              Reporter:
              Dirk Sturzebecher
            • Votes:
              88 Vote for this issue
              Watchers:
              68 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: