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

Saurabh Khare updated SLING-9688:
---------------------------------
    Description: 
Sling superimposing is still relevant for particular contexts when resource 
mirroring is a necessity. SLING-1778

This ticket is for upgrading the sling superimposing sling extension to use 
OSGI R7 annotations by upgrading pom to use latest sling bundle parent and 
associated dependencies 

  was:
Sling superimposing is still relevant for particular contexts when resource 
mirroring is a necessity. SLING-1778

This ticket is for upgrading the old sling superimposing sling extension with 
latest resource provider API and OSGI annotations.

Following are the upgrades for the extension:
 # Upgrade Resource provider API from 
org.apache.sling.api.resource.ResourceProvider to 
org.apache.sling.spi.resource.provider.ResourceProvider
 # Upgrade to OSGi R7 annotations
 # Use of service resolver instead of administrative resource resolver
 # Upgrade for maven plugins and migration from maven-bundle-plugin to 
bnd-maven-plugin


> Upgrade Sling superimposing to use OSGi R7 annotations
> ------------------------------------------------------
>
>                 Key: SLING-9688
>                 URL: https://issues.apache.org/jira/browse/SLING-9688
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Superimposing Resource Provider 0.2.0
>            Reporter: Saurabh Khare
>            Priority: Major
>              Labels: newbie, pull-request-available
>             Fix For: Superimposing Resource Provider 0.4.0
>
>
> Sling superimposing is still relevant for particular contexts when resource 
> mirroring is a necessity. SLING-1778
> This ticket is for upgrading the sling superimposing sling extension to use 
> OSGI R7 annotations by upgrading pom to use latest sling bundle parent and 
> associated dependencies 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to