Clover can't instrument Groovy test classes due to on creating ConfigDir

We have our maven build setup to run Groovy based integration tests. We want to be able to instrument our tests using distributed coverage while our app runs on a local jetty instance. This works great with Java based Junit tests but we are having trouble getting the Groovy tests instrumented.

When the build starts up with Clover the plugin throws the following stacktrace:


ERROR Could not create Clover Groovy configuration file. No Groovy instrumentation will occur. com.atlassian.maven.plugin.clover.DistributedCoverage com.atlassian.maven.plugin.clover.DistributedCoverage








at com.atlassian.clover.ant.groovy.GroovycSupport.newConfigDir(

at com.atlassian.maven.plugin.clover.CloverInstrumentInternalMojo.injectGrover(

at com.atlassian.maven.plugin.clover.CloverInstrumentInternalMojo.execute(

at com.atlassian.maven.plugin.clover.CloverSetupMojo.execute(

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(

at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(

at org.apache.maven.DefaultMaven.doExecute(

at org.apache.maven.DefaultMaven.execute(

at org.apache.maven.cli.MavenCli.execute(

at org.apache.maven.cli.MavenCli.doMain(

at org.apache.maven.cli.MavenCli.main(

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(

at sun.reflect.DelegatingMethodAccessorImpl.invoke(

at java.lang.reflect.Method.invoke(

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(

at org.codehaus.plexus.classworlds.launcher.Launcher.main(


1 answer

Hi Dustin,

I've made a SNAPSHOT release of the Clover plugin for Maven2 that contains a candidate fix for this problem. To use it, you'll need to specify the snapshot version:






Note that this snapshot version is only available from Atlassian's public snapshot repository, which you may need to add to your pom also:




          <name>Atlassian Public Snapshot Repository</name>




Please let me know how you get on with this build.



Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

529 views 1 15
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot