Hi Team
--- clover-maven-plugin:4.4.1:instrumentInternal (clover.inst) @ project1 ---
[INFO] No Clover instrumentation done on source files in: [/Users/paritosh/ABC/project1/src/main/java] as no matching sources files found (JAVA_LANGUAGE)
[INFO] No Clover instrumentation done on source files in: [/Users/paritosh/ABC/project1/src/test/java] as no matching sources files found (JAVA_LANGUAGE)
[INFO]
I tried providing the exact path of the java file as well in the configuration but every time it threw the same error message. Even I tried the goal of maven clover:setup but it threw the same message.
Due to this, no clover database is getting generated hence there are no reports.
No Clover database found, skipping report generation
My project uses java 11. I read somewhere that there is no support for java 11 as of now but is there any upcoming plan for this.
Also, is the error which is coming up due to this java version? Is there any work around for now.
Code snippet from pom.xml:
<groupId>org.openclover</groupId>
<artifactId>clover-maven-plugin</artifactId>
<configuration>
<targetPercentage>10%</targetPercentage> <cloverDatabase>${project.build.directory}/clover/clover.db</cloverDatabase>
<debug>true</debug>
<includes> <include>${project.source.directory}/</include>
</includes>
</configuration>
<executions>
<execution>
<id>clover.inst</id>
<phase>validate</phase>
<goals>
<goal>instrument-test</goal>
<!-- <goal>setup</goal> -->
</goals>
</execution>
It would be really great if I can get some ideas on this. Please let me know if any other information is required.
Recommended Learning For You
Level up your skills with Atlassian learning
Reporting for DevOps
Identify four key DevOps metrics and learn how to use Jira reports to track your team's progress and performance.
Explore Atlassian Cloud products for agile and DevOps
Coordinate a suite of Atlassian Cloud products for greater collaboration and trust, higher-quality solutions, faster releases, and more.
Monitor component health with scorecards in Compass
Learn what scorecards are and their purpose in measuring the health of software components and improving DevOps practices.