[jira] [Resolved] (SLING-6739) split sling.event into event.api and event.resource (was: event.impl)

["Stefan Egli (JIRA)" <ji...@apache.org>]

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

Stefan Egli resolved SLING-6739.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Event 4.3.0)
                   Event 4.2.6

As [mentioned on the list|http://markmail.org/message/x7dkth3t622xzm4y] the original idea was to release this as 4.3.0 but as it was now already released as 4.2.6 that is also fine. Whether to use 4.2.6 or 4.3.0 is really more a _cosmetic_ question. The minor version bump would have indicated something more than just on the patch level to have changed. But we shall leave it at 4.2.6 for now. Hence adjusted the fix version accordingly.
/cc [~karlpauls]

> split sling.event into event.api and event.resource (was: event.impl)
> ---------------------------------------------------------------------
>
>                 Key: SLING-6739
>                 URL: https://issues.apache.org/jira/browse/SLING-6739
>             Project: Sling
>          Issue Type: Task
>          Components: Extensions
>    Affects Versions: Event 4.2.2
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Event API 1.0.0, Event 4.2.6
>
>
> Currently sling.event contains both API and implementation. In order to support different implementation variants it would be good to have two separate bundles, one containing just the API and one with the (current) implementation. I would suggest to create
> bundles/extensions/event/api
> bundles/extensions/event/resource
> and to remove the current
> bundles/extensions/event



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)