Mailing-List: contact dev-help@sling.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sling.apache.org
Date: Mon, 3 Nov 2014 12:53:33 +0000 (UTC)
From: "Marius Petria (JIRA)" <jira@apache.org>
To: dev@sling.apache.org
Message-ID: <JIRA.12750744.1414415611000.397648.1415019213701@Atlassian.JIRA>
In-Reply-To: <JIRA.12750744.1414415611000@Atlassian.JIRA>
References: <JIRA.12750744.1414415611000@Atlassian.JIRA>
 <JIRA.12750744.1414415611911@arcas>
Subject: [jira] [Commented] (SLING-4106) Cleanup Sling Replication APIs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SLING-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194509#comment-14194509 ] 

Marius Petria commented on SLING-4106:
--------------------------------------

In revision 1636343: adding ConsumerType/ProviderType annotations to replication API 

> Cleanup Sling Replication APIs
> ------------------------------
>
>                 Key: SLING-4106
>                 URL: https://issues.apache.org/jira/browse/SLING-4106
>             Project: Sling
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>
> The Sling Replication API has evolved a lot since its inception so, before the first release, it'd be good to perform a proper review and cleanup to remove the methods / classes that are not needed, avoid exported packages that do not need to be exposed.
> Also a good thing would be to separate the API itself in a separate bundle.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)