Bamboo automatically integrates Clover with Ant, Maven and Grails even when the build is configured with manual Clover integration:
Starting to build 'TEST - Default' ... running command line: /Applications/dev/apache-ant-1.7.1/bin/ant clover.fullclean -Djava.io.tmpdir=/var/folders/i5/i5k0y8P7GOagFji106y-0++++TM/-Tmp-/TEST-DEF -f build.xml build -Dclover.skip.json=true -Dclover.skip.report=true -Dclover.optimization.enabled=false -lib /Users/asridhar/.m2/repository/com/cenqua/clover/clover/3.0.1/clover-3.0.1.jar -listener com.atlassian.clover.ci.AntIntegrationListener -Dclover.license.path=/Users/asridhar/Bamboo/code/atlassian-bamboo-2.6/bamboo-homes/8085/xml-data/build-dir/131073/TEST-DEF/.clover/clover.license ... in : /Users/asridhar/Bamboo/code/atlassian-bamboo-2.6/bamboo-homes/8085/xml-data/build-dir/131073/TEST-DEF ... using java.home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Workaround
There is a patched Clover plugin JAR (with the fix) attached to this ticket. To apply the patch:
- Shutdown Bamboo 2.6
- Remove <Bamboo>/webapp/WEB-INF/lib/atlassian-bamboo-plugin-clover-2.6.jar
- Download the atlassian-bamboo-plugin-clover-2.6_BAM-5920.jar file to <Bamboo>/webapp/WEB-INF/lib/ directory.
- Restart Bamboo.
Warning message will be fixed in
BAM-5933