Hi! I'm using a 1.5.5-SNAPSHOT build of apacheds-core-integ (because I need functionality from https://issues.apache.org/jira/browse/DIRSERVER-1300). There are several test classes in a test suite that are run by SiRunner, therefore ApacheDS is started and stopped multiple times inside the JVM that runs Surefire tests during Maven build. Maven Surefire plugin is configured to fork a single JVM for a test suite (<forkMode>once</forkMode>). I've got multiple Maven artifacts that have such test suites.
Recently, tests in one of the artifacts have started interrupting silently. After closer inspection it turned out that the second test in a test suite that's run by SiRunner causes a JVM shutdown (java exists with code 0 - no error - therefore Maven doesn't detect any problems). There are no error messages on the console and no other indicators of failure. Because SiRunner cannot be configured for higher log level (see https://issues.apache.org/jira/browse/DIRSERVER-1350) I cannot really track down the cause of this. However, I'm positive that it has worked fine with earlier apacheds 1.5.5-SNAPSHOT builds. Did anyone commit something lately that could cause SiRunner to malfunction in such a manner? -- Best Regards, Aleksander Adamowski http://olo.org.pl
