Hi Supun, Can you look at following which I came across running AS test cases for coverage stats.
java.lang.AssertionError: Unsatisfied components detected in server startup. [org.wso2.carbon.deployment.synchronizer.XXX] expected:<0> but was:<1> at org.wso2.carbon.integration.common.tests.OSGIServerBundleStatusTest.testOSGIUnsatisfiedComponents(OSGIServerBundleStatusTest.java:80) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) ... Removed 26 stack frames org.wso2.carbon.deployment.synchronizer is in a unsatisfied state. Thanks, Waruna
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
