Hi Am 04.07.2013 um 16:36 schrieb Bertrand Delacretaz:
> On Thu, Jul 4, 2013 at 4:30 PM, Felix Meschberger <[email protected]> wrote: >> ...Technically exporting the o.a.s.api.adapter package at 2.2.1 is >> wrong and may lead to erroneous Import-Package statements for >> implementors: [2.2,3) instead of [2.2.1,3).... > > Ok, after discussions here I'm thinking that the new @Adapter > annotation and AdapterProvider interface rather belongs to the > sling.adapter bundle - they don't need to be in the core API, WDYT? No, I think the belong in the API. We moved all that adapter stuff from the Adapter Manager bundle to the API because we thought the API is core to Sling. Also, the AdapterProvider interface and @Adapter annotations are extension mechanisms like the AdapterFactory. Since the AdapterFactory correctly (IMHO) is in the Sling API, the AdapterProvider and @Adapter should also be in the Sling API: The AdapterManager bundle is just a feature implementation bundle. The bundle just exports the deprecated SlingAdaptable for backwards compatibility. Regards Felix
