[BAM-10516] Clover artefacts and clover.xml not found if working sub dir is set - Create and track feature requests for Atlassian products.

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

Bug Fix Policy:
View Atlassian Server bug fix policy

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/*/.*

is related to

BAM-8169 Make the automatic clover import more respect working directory

Closed

BAM-11151 Automated Clover artifact creation does not take into account task working directories

Closed

There are no comments yet on this issue.

Assignee:: Marek Parfianowicz

Reporter:: Michael Studman (Inactive)

Affected customers:: 0 This affects my team

Watchers:: 1 Start watching this issue

Created:: 22/Dec/2011 11:39 PM

Updated:: 19/Aug/2019 2:03 AM

Resolved:: 19/Nov/2014 12:13 PM