[
https://issues.apache.org/jira/browse/FELIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315905#comment-14315905
]
Carsten Ziegeler commented on FELIX-4785:
-----------------------------------------
[~djencks] After some rethinking of the issue, I agree that doing a compat
bundle that acts on the DTOs is the nicer option. It gets the impl free of the
cruft and people using that simply install the second bundle.
However, org.apache.felix.scr contains also the ScrInfo interface which isn't
really used - as the package version is updated to 2.0 (due to the removal of
the other stuff), this will break clients using this anyway. On the other hand,
I'm not sure if this one is used much.
My suggestion is we complete remove the org.apache.felix.scr package from the
DS implementation and put everything into the compat bundle including
org.apache.felix.scr.ScrInfo and an implementation for that.
> 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)
