On 9 October 2013 16:48, Richard S. Hall <[email protected]> wrote: > On 10/9/13 11:23 , CLEMENT Jean-Philippe wrote: >> >> I guess this is not the issue. From my understanding, Aries in itself is >> already too heavy for him and he would like the "Subsystems specification >> and Common Namespaces Specification" implementation alone. > > > Ah. I would have assumed that the implementation from Aries would be usable > independently from anything else in Aries...if not, then I see.
When I looked at it last the implementation in Aries had the following bundles/dependencies: org.apache.aries.subsystem.api_1.0.0 org.apache.aries.subsystem.core_1.0.0 org.apache.aries.subsystem.obr_1.0.0 org.apache.aries.application.api_1.0.0 org.apache.aries.application.modeller_1.0.0 org.apache.aries.application.utils_1.0.0 org.apache.aries.blueprint_1.1.0 org.apache.aries.proxy_1.0.1 org.apache.aries.util_1.1.0 org.apache.felix.bundlerepository_1.6.6 org.apache.felix.resolver_1.0.0 org.eclipse.equinox.coordinator_1.1.0.v20120522-1841 org.eclipse.equinox.region_1.1.0.v20120522-1841 slf4j.api_1.7.5 slf4j.simple_1.7.5 So while it has a number of dependencies, it certainly doesn't depend on everything in Aries... Cheers, David --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
