You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (Jira)" <ji...@apache.org> on 2020/03/26 16:37:00 UTC
[jira] [Updated] (SLING-9259) Prepare distribution journal code for
an external distribution service
[ https://issues.apache.org/jira/browse/SLING-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothee Maret updated SLING-9259:
----------------------------------
Fix Version/s: (was: Content Distribution Journal Core 0.1.10)
Content Distribution Journal 0.1.14
> Prepare distribution journal code for an external distribution service
> ----------------------------------------------------------------------
>
> Key: SLING-9259
> URL: https://issues.apache.org/jira/browse/SLING-9259
> Project: Sling
> Issue Type: Bug
> Components: Content Distribution
> Affects Versions: Content Distribution Journal Core 0.1.8
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Priority: Major
> Fix For: Content Distribution Journal 0.1.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the distribution.journal bundle directly talks to the messaging system. We would like to introduce a service that extracts this functionality from sling.
> To allow a smooth transition I would like to split the code into a part that stay in the sling instance and the part that will be moved to the service impl.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)