Clover artefacts and clover.xml not found if working sub dir is set

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 5.7.0
    • Affects Version/s: 3.2, 3.3, 3.4
    • Component/s: Clover integration, Plugins
    • None

      Steps to reproduce:

      • Create a Maven project in directory "sub" underneath a top-level directory "top"
      • Add a plan with a Maven job to build it, specifying the working sub directory as "top"
      • Enable Clover automatic integration
      • Clover results are not collected

      Workaround:

      • Disable Clover autointegration
      • manually specify the glob for clover.xml as top/target/site/clover/**/clover.xml
      • Edit the "Clover Report (System)" artefact defintion's location to be top/target/site/clover/*/.*

              Assignee:
              Marek Parfianowicz
              Reporter:
              Michael Studman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: