[
https://issues.apache.org/jira/browse/FELIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks reopened FELIX-4785:
---------------------------------
IIUC you have added an implementation of the old service to the new service
implementation, and are actually returning some information for the old
interfaces. I object in the strongest possible terms to this. The meaning of
the new interfaces cannot be stuffed back into the old ones, the old ones are
just a wrong model of scr. Freeing the implementation from the mistakes of the
old model means that any attempt to return information in the old format will
differ from what is returned in released felix ds versions.
I would be OK with including the old interfaces but returning absolutely no
information in the SCRInfo service. IMO There's no reason to saddle any
implementation classes with returning deprecated information.
I would have appreciated discussion on this when I originally proposed the
version change rather than months later.
> Incompatible SCR API
> --------------------
>
> Key: FELIX-4785
> URL: https://issues.apache.org/jira/browse/FELIX-4785
> Project: Felix
> Issue Type: Bug
> Affects Versions: scr-2.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: scr-2.0.0
>
>
> Current trunk contains version 2.0.0 of the org.apache.felix.scr API package.
> While this is a logical step, this makes the new implementation unusable as a
> drop-in replacement into existing installations which might use the 1.x
> version of that API.
> I think we should go a more moderate way, leave the 1.x version in but
> deprecate it and also provide the replacement API (if any). Then in one of
> the further versions along the road, we can remove the API. This gives our
> users a chance to migrate slowly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
