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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

Clover-Historypoint target error

Hi all,

when I am executing clover  historypoint target it gave me error like this 

home/IdeaProjects/WebApp/build.xml:301: com.atlassian.clover.registry.NoSuchRegistryException: Clover registry file "/home/IdeaProjects/WebApp/.clover/clover4_1_1.db" does not exist, cannot be read or is a directory.
Please ensure Clover has instrumented your source files. My report target as follow


<target name="" >

<clover-report initstring="/home/Desktop/Clover/.clover/clover4_1_1.db">

<current outfile="/home/tomcat/webapps/common/pages/Clover-report" title=" Code Coverage Report">
<format type="html"/>
<fileset dir="src/server"/>

<historical outfile="/home/tomcat/webapps/common/pages/historical-report" title="Historical Report" historyDir="/home/Desktop/Clover/historypoints">
<format type="html"/>


<clover-historypoint historyDir="/home/Desktop/Clover/historypoints" overwrite="true">
<fileset dir="src/server"/>

Why this error come? in most cases, most people told about instrument or clover db file problem
 But my case report is generated, but they could not run <clover-historypoint> target. Build failed because of this target execution fail. So I can't generate historical report, only generate current report and build failed. How do I over come this problem?

2 answers

1 accepted

1 vote
Answer accepted

Hello Dulsara,

As you can see, the clover-historypoint task is looking for a database file in:


and in clover-report you use:


You have to use:

&lt;clover-historypoint initstring="/home/Desktop/Clover/.clover/clover4_1_1.db" historyDir="/home/Desktop/Clover/historypoints" overwrite="true"&gt;

Alternatively, you can call clover-setup task before, as described here:


Thank you very much, It works fine


 I think it's connected with the fact you're not passing the initstring parameter to clover-historypoint.  According to the message it looks for the DB in a default location. 

Just try to modify it in somewhat in this way:

&lt;clover-historypoint historyDir="/home/Desktop/Clover/historypoints" overwrite="true"  initstring="/home/Desktop/Clover/.clover/clover4_1_1.db"&gt;
&lt;fileset dir="src/server"/&gt;
Thank you very much, it works properly.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Learn how to request and manage app requests in the Marketplace

G’day everyone! Super exciting news coming from the Marketplace. We have now fully rolled out the ability for end-users to submit app requests to admins directly from within the product! No longer ...

43 views 1 5
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