Are errors in the run.log a cause for concern for CVS_HEAD build? Just want to know if I can safely ignore the runtime errors as a "normal state of alpha craziness".
Also, I tried running the testsuite and the overall build claims success, but one of the targets fails with 12 errors and 43 warnings. The testsuite/output director is an empty skeleton after the run, and I can't seem to find test results. There are probably very n00b questions. Advanced apologies. What I did to get here: cvs co jboss-head (in build dir) build (completes successfully) build run-jboss (starts up with some errors including those below) build run-testsuite (reports success but generates no testsuite/output and has internal build errors) An error from running JBoss (there were about 10 errors with stack traces, but I'd rather not spam the list with that unless it's requested): 14:27:58,056 INFO [ServiceConfigurator] class not found for mbean jboss:service=WorkManager,type=TrunkInvoker ... 14:27:58,928 ERROR [STDERR] javax.management.InstanceNotFoundException: jboss:service=WorkManager,type=TrunkInvoker is not registered. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
