Here a heads-up on the MSC based Core Framework.

All standard osgi core framework tests have been copied to the new code base and we pass most of them already

Tests run: 126, Failures: 0, Errors: 0, Skipped: 15

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40.998s

There are a number of tests that are currently commented out

> git grep @Ignore

SimpleArquillianTestCase.java:@Ignore
BundleEntriesTestCase.java:   @Ignore
BundleLifecycleTestCase.java:   @Ignore
BundleTestCase.java:   @Ignore
FragmentTestCase.java:@Ignore
OSGi323TestCase.java:@Ignore
OSGi342TestCase.java:@Ignore
NativeCodeTestCase.java:@Ignore
GetServiceReferencesTestCase.java:@Ignore
GetUnGetServiceTestCase.java:@Ignore
RegisterServiceTestCase.java:@Ignore
ServiceEventHookTestCase.java:@Ignore
ServiceFactoryTestCase.java:@Ignore
ServiceFindHookTestCase.java:@Ignore
ServiceListenerHookTestCase.java:@Ignore
ServiceListenerTestCase.java:@Ignore
ServiceReferenceTestCase.java:@Ignore
ServiceRegistrationTestCase.java:@Ignore

These need to be looked at with high priority. NativeCode and Fragments are not implemted at all. We have reasonable coverage for services and some of the service tests may work already or can be fixed with little effort.

There is currently no aggregate jar that can be used in the TCK setup. JBOSGI-361

Our latest stable release has been integrated into the AS6-M4 code base (JBAS-8122) The MC based framework is now in maintenance mode and would only require work when the OSGi AS6 hudson job (JBoss-6.0.1) shows regression. The AS6 target containers can be removed from QA matrix. When ready, we add AS7 on the MSC Framework. We might also decide to drop OSGi support in AS6 completely (M4 and after) if it is too much of a time sink and distracts us from our AS7 M1 (01-Nov-2010) goal.

The Standalone Runtime, currently still runs on the MC Framework. The installer needs to be updated to use the MSC Framework instead.

We do not offer multiple frameworks, instead we do a switch from MC to MSC. The criteria for the switch is that MSC passes all our enterprise example tests on the Remote Runtime. JBOSGI-362

Service-Mix currently works for these use cases

   public void testSimpleModule() throws Exception
   public void testModuleDependsOnBundle() throws Exception
   public void testBundleDependsOnModule() throws Exception

This only covers Require-Bundle style dependencies. Service lookup/injection is not done yet, but it's the next thing on my plate. When I'm through I'll document this comprehensively so AS7 can include well defined behaviour for cross-component service use.

The MSC Framework (as well as the MC Framework) uses our new Standalone OSGi Resolver. The current implementation uses a snapshot of the Apache Felix 2.1.0 code base. This needs to be upgraded to the latest Felix 3.0.x release. JBOSGI-363

Our main focus for OSGi functionality is to make it available in AS. I suggest we integrate early with the AS7 code base to catch issues we might not see otherwise and give AS folks the needed OSGi feedback. JBOSGI-364

Anything else?