[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974457#comment-15974457 ]
Stefan Egli commented on SLING-6739: ------------------------------------ bq. However we should not change the bundle symbolic name, otherwise this bundle could not be used for updating an older version. good point. in that case I guess the most straight-forward way would be to leave the artifactId unchanged indeed - otherwise we have to explicitly set the bundle symbolic name and it might be difficult to argue why a different artifactId vs symbolic name (or at least not as straight-forward as leaving it the same). So let's to go for {{org.apache.sling.event}} 4.3.0 > 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 > > > 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.3.15#6346)