Got the answer.. KJAR pom.xml should have the dependency of the jars which are KJAR only.. we should not mentioned the dependency of the jars which are not of form KJAR. JBPM identifies whether the given jar is a kjar or not based on whether we have kmodule.xml present in the jar or not if yes that it is a kjar and tries to load it.
Thanks for every one
1 of 1 people found this helpful
dependencies that are present on server classpath (jbpm console) can be marked as scope provided so they will not be loaded during deployment but will be referenced from parent classloader.