That sounds good to me. I think the same holds for jmx-blueprint which also has an inconsistency. It also has another problem: it exports the org.apache.aries.jmx.blueprint.impl.codec package. If we really need to export it, then it should be org.apache.aries.jmx.blueprint.codec (wihtout the "impl" package in the name). I'll go ahead and make the change asap unless someone objects.
On Mon, Mar 15, 2010 at 17:25, Jarek Gawor <[email protected]> wrote: > Hi, > > The set of packages exported by blueprint-bundle is different from all > packages exported by the individual bundles that make up the > blueprint-bundle (blueprint-api, blueprint-core, and blueprint-cm). > Which means that things that work when the individual blueprint > bundles are installed do not work when the blueprint-bundle is > installed. > > So I think we should make sure the same set of packages are exported > by the blueprint-bundle as by the individual bundles. > > Jarek > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
