deployed JSP throws java.lang.NoClassDefFoundError


Hi I am trying to demo clover test optimization in my company do decrease the test execution time. I have a simple JSP Page that refers one of the class file. Project builds fine and get deployed. When I use clover code coverage then only the deployed JSP doesnt work. when i deploy with clover using

 mvn clean clover2:setup verify clover2:clover.

if I open the JSP deployed using :- http://localhost:8080/demo/Math2.jsp it throws error as below :-

java.lang.NoClassDefFoundError: Could not initialize class com.ariba.demo.App

I do see instrumented classes refer this image . In Atlasian answers somebody informed to downgrade to tomcat 6. I did. Still i see the same issue. I need to demo this tomorrow to our team. Here is the project source code  . Please help me to get rid of this.



1 answer

1 accepted

1 vote
Accepted answer

Hi Shankar,

1) You have an unnecessary dependency to maven-clover2-plugin:


instead of this, you shall declare a dependency to Clover Core:



2) By the way: the maven-clover2-plugin's version number is missing:

      <version>4.0.1</version> <!-- add this -->


3) It's also good to define a <jdk> property for maven-clover2-plugin and/or to define <source> property for maven-compiler-plugin. Otherwise your demo project will not compile under JDK8 (a reason is that Clover sees Java 8 and assumes "1.8" source level for instrumentation; at the same time maven-compiler-plugin assumes "1.3" source level).


Nevertheless, compilation of your demo project fails (mvn clean verify):

...\[48,35] error: no suitable constructor found for ProcessBuilder(String,String)
could not parse error message:     constructor ProcessBuilder.ProcessBuilder(List) is not applicable
      (actual and formal argument lists differ in length)
    constructor ProcessBuilder.ProcessBuilder(String...) is not applicable
      (actual and formal argument lists differ in length)
...\ error: method executeScript in interface JavascriptExecutor cannot be applied to given types;
        return js.executeScript(script);


4) Furthermore, the cargo-maven2-plugin does not have a dependency on com.atlassian.clover:clover artifact. Due to this, the clover.jar is not available on Tomcat's class path and the most probably this is a source of the error you have. Please try adding something like this:


        &lt;!-- We need clover.jar to be present in container classpath --&gt;


See also this KB article:



Wow Marek,

Thank you Thank you Thank you. Your answer was the exact solution. I made the changes you suggested. It worked like a charm. 

Thank you once again.

You're welcome! :-)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Friday in Jira Service Desk

Are you a Jira Service Desk agent? We want to talk to you!

Are you a whiz at handling tickets and looking at how you can further optimize your workflow with automation? Do you tackle detailed customer support questions while simultaneously getting flooded wi...

138 views 0 7
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