Hi, On Wed, Jan 25, 2012 at 1:06 AM, Tobias Bocanegra <[email protected]> wrote: > how about adding getSelectorJcrNames() and deprecate the other one?
Yes, we can do that. It just feels silly that we have to go through hoops like that when AFAICT were the only ones using and implementing this interface. And (correct me if I'm wrong), isn't the OSGi framework supposed to be able to deal with cases where for backwards compatibility reasons more than one version of a package needs to be present? I'd understand this desire better if the objection was about 1233468 (the actual API change) rather than 1227240 (the OSGi package version update). Is there any actual client or implementation code that gets broken by revision 1233468 but that I didn't already update? Why then is revision 1227240 causing trouble? BR, Jukka Zitting
