I am still getting unit test failures on MC kernel trunk. There are two efforts that I want to help with/work on but this unit test failure could impact them. I am interested in feedback on whether this is likely to be causing problems for me. 1. I couldn't integrate the jboss-mdr trunk to mc kernel trunk. I'm not sure how to resolve the classdefnotfound errors that I got only when trying to bring in the newer jboss commons jar. I updated as many sub projects to use JBoss Commons 2.2.14.GA as I could identify, but this error still occurred. This failure may be separate from this threads unit test failures but I would like help with getting the intregration going. Should I open a new thread for this effort and should I wait until these unit test failures are fixed? 2. I would like to start testing AS with the Parallel deployment support soon. I assume that I need to wait until these unit test failures are fixed as well. Should I ignore these failures and do a maven build with unit tests skipped to work around this? I will also need the AS configuration files that were previously tested with (maybe we can share via pastebin. 3. I have further ScopeKey improvements (changing some callers to pass in optimized scopekey for lookup) but need to get past #1 above first so I can test... 4. I started looking at the AE integration with Papaki but I will post about that on a different thread. That effort is not impacted by the unit test failure, but thought I would mention it here (since I'm give status). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256219#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...