You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/08/13 09:47:16 UTC
[jira] Updated: (SLING-1460) Move SlingSettingsService to new
Settings bundle
[ https://issues.apache.org/jira/browse/SLING-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1460:
------------------------------------
Summary: Move SlingSettingsService to new Settings bundle (was: Move SlingSettingsService to API bundle)
Fix Version/s: Settings 0.1.0
(was: API 2.1.0)
Affects Version/s: (was: API 2.0.8)
Component/s: Extensions
(was: API)
> Move SlingSettingsService to new Settings bundle
> ------------------------------------------------
>
> Key: SLING-1460
> URL: https://issues.apache.org/jira/browse/SLING-1460
> Project: Sling
> Issue Type: Improvement
> Components: Engine, Extensions
> Affects Versions: Engine 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Engine 2.1.0, Settings 0.1.0
>
>
> As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:
> - Add the interface to the API in the o.a.s.api.services package
> - Deprecate the interface in the enigne bundle and let it extend
> from the interface in the API
> - Let the service impl in the engine bundle register itself for
> both interfaces.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.