Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Any pointers on what might be wrong using Clover with Gradle for Groovy

I get the following error:

ERROR: Clover-for-Groovy encountered an error while loading config:

Basically, when I use ant.'clover-setup' I get this error and no instrumentation is performed. I can leave off all params to the ant task (i.e. accepting all defaults) and still get this error.

3 answers

0 votes
Nick Atlassian Team Aug 21, 2011

Hi Paul,

Is there a stack-trace accompanying that error message?

Do you see any more log messages when you run Gradle in debug mode ?

Cheers,
Nick

No stacktraces near that error. There is a stacktrace later on because the ant.'clover-report' can't find the coverage database - but it isn't there (as it is never created) so it seems to be working as expected.

The previous line is execing java with this class 'org.codehaus.groovy.tools.FileSystemCompiler' and has the clover jar and a temp groverxxxx.jar in the classpath.

Then the error line.

Then:
[ant:clover-setup] Cleaning up Clover directory ...

Which logging library is being used under the covers?

0 votes
Nick Atlassian Team Aug 21, 2011

By default, Clover should log to stdout. You can specify the log level by setting the clover.logging.level to either

  • debug
  • verbose

You can also specify which framework gets used via the clover.logging.adapter System property. Valid values are:

  • log4j
  • jdk
  • stderr

e.g. -Dclover.logging.adapter=log4j

will force Clover to use log4j.

0 votes

Such error might happen when Ant jar is missing in class path. In such case the error message with a stack trace looks this:

  [groovyc] ERROR: Clover-for-Groovy encountered an error while loading config: Clover-for-Groovy encountered an error while loading config:  : org/apache/tools/ant/BuildException
  [groovyc] java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException
  [groovyc] 	at java.lang.Class.getDeclaredFields0(Native Method)
  ...
[groovyc] at com.atlassian.clover.instr.java.InstrumentationConfig.loadFromStream(InstrumentationConfig.java:439) [groovyc] at com.atlassian.clover.instr.groovy.Grover.newConfigFromResource(Grover.java:241) [groovyc] at com.atlassian.clover.instr.groovy.Grover.<init>(Grover.java:210)
...

If this is your case, then please use includeAntRuntime="true" in your build configuration.

See also clover-for-groovy-encountered-an-error-while-loading-config.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

173 views 2 9
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you