-
Suggestion
-
Resolution: Fixed
-
None
-
Maven plugin for clover version 3.0 beta 5 , bamboo war version 1.2.1 build 409.
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.
Form Name |
---|
[CLOV-43] Builds Fail with errors relating to JVM memory settings when entries for clover are put in a projects parent pom file.
Workflow | Original: JAC Suggestion Workflow [ 3342802 ] | New: JAC Suggestion Workflow 3 [ 3585227 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: New Clover Workflow - Restricted [ 1473084 ] | New: JAC Suggestion Workflow [ 3342802 ] |
Issue Type | Original: Task [ 3 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: New Clover Workflow [ 896692 ] | New: New Clover Workflow - Restricted [ 1473084 ] |
Backlog Order (Obsolete) | Original: 2840000000 | |
Issue Type | Original: Support Request [ 5 ] | New: Task [ 3 ] |
Labels | New: support-request |
Workflow | Original: Clover Workflow [ 895098 ] | New: New Clover Workflow [ 896692 ] |
Workflow | Original: reviewflow [ 119989 ] | New: Clover Workflow [ 895098 ] |
Issue Type | Original: Bug [ 1 ] | New: Support Request [ 5 ] |
Fix Version/s | New: won't fix [ 38394 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |