Hi, I'm not sure what the reason was for moving it, and it did happen a while ago so it may be that noone remembers. One possibility is that it was done to rationalise the large org.apache.aries.blueprint package. Both the old and new packages are exported, so it isn't a visibility thing.
We possibly do need a larger API discussion for blueprint. Things are better now we aren't exposing every package, but it has grown a bit organically and the packages may not be structured as well as they could be. Regards Tim Ward ------------------- Apache Aries PMC member & Enterprise OSGi advocate Enterprise OSGi in Action (http://www.manning.com/cummins) ------------------- > From: [email protected] > To: [email protected] > Subject: ExtendedBlueprintContainer moved.... > Date: Fri, 18 Nov 2011 17:37:06 -0500 > > > The ExtendedBlueprintContainer interface moved from > org.apache.aries.blueprint > to org.apache.aries.blueprint.services in 0.4. Thus, both Camel and CXF > that > use that interface will no longer work with 0.4. > > Was that intentional? Is there anything we can do, at least for 0.4.1, that > would allow things to keep working? > > For CXF, the only thing we need is the Repository out of it. Is there > another way of obtaining the repository that would work for both 0.3 and 0.4? > > Haven't checked what methods camel needs. > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > >
