Downgrading to the 1.3 version of the plugin makes it work as expected. Added the information to bug ticket https://issues.jenkins-ci.org/browse/JENKINS-14552
On Wed, Jul 25, 2012 at 2:01 PM, Miguel Almeida <migueldealme...@gmail.com>wrote: > Dear all, > > I have a multi-module maven project. I'm currently running the goal > install and have a post-build step running the cobertura:cobertura goal. > > Cobertura is configured to produce the xml report (which I see in the > workspace). However, I am getting the following console output [1], where > it reads "Skipping Cobertura coverage report as mojo did not run.". > > Doesn't the cobertura plugin work with a post-build step? My idea for > having a post-build step instead of running the goal directly is to > accelerate feedback regarding the commit. > > > Cheers, > > Miguel Almeida > > [1] > > [INFO] Cobertura Report generation was successful. > [INFO] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file > Cobertura: Loaded information on 53 classes. > Report time: 1670ms > > [INFO] Cobertura Report generation was successful. > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Parent .............................................. SUCCESS [2.882s] > [INFO] Model .............................................. SUCCESS [5.370s] > [INFO] Web ................................................. SUCCESS [33.970s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 2:40.478s > [INFO] Finished at: Wed Jul 25 13:08:43 WEST 2012 > [INFO] Final Memory: 14M/35M > [INFO] > ------------------------------------------------------------------------ > Archiving workspace > Deleting old workspace snapshot from #412. > Skipping Cobertura coverage report as mojo did not run. > Finished: SUCCESS > > >
