[jira] Resolved: (FELIX-1933) Rename ScrService

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved FELIX-1933.
--------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was:  scr-1.2.2)

The Eclipse project has dropped the idea of renaming the service for now.

In case of later standardizing this API it must be repackaged anyway and may then be renamed to a better name.

For now, this issue is resolved without fixing it.

> Rename ScrService
> -----------------
>
>                 Key: FELIX-1933
>                 URL: https://issues.apache.org/jira/browse/FELIX-1933
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.2.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> The Eclipse project is currently considering adding our ScrService API into their Declarative Services implementation. But there are concerns with the current service name: ScrService.
> The current proposals from the Eclipse community are: ScrAdmin or ComponentAdmin.
> I agree with the ScrService not being the best possible name, so I threw DeclarativeServicesAdmin or DSAdmin into the pot (based on similar naming in the Configuration Admin and Event Admin specifications).
> Whatever will be the outcome, we will probably have to change the name, too. But we will have to do so in a backwards compatible manner.
> An option would be to keep the old service interface and name as deprecated for the near future (or until the OSGi would eventually officially define the API and service). The Felix DS implementation would register both services and thus support backward compatible and current service names.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.