[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074904#comment-16074904 ]
Stefan Egli commented on SLING-6739: ------------------------------------ h6. step 12 : embedding event.api 1.0.0 in event and explicitly exporting event.jobs, event.jobs.consumer, event.jobs.jmx done in http://svn.apache.org/viewvc?rev=1800888&view=rev [~karlpauls], [~cziegeler] would appreciate a quick review of 1800888, thx! final remaining step 13 would be to release sling.event in version {{4.3.0}} (without any further changes). > 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.3.0 > > > 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)