[jira] [Commented] (SLING-6739) split sling.event into event.api and event.resource (was: event.impl)
[
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)
[jira] [Commented] (SLING-6739) split sling.event into event.api and event.resource (was: event.impl)
[
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)
[jira] [Commented] (SLING-6739) split sling.event into event.api and event.resource (was: event.impl)
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974445#comment-15974445 ] Carsten Ziegeler commented on SLING-6739: - Not sure if we need to change the artifact id - it might make sense. However we should not change the bundle symbolic name, otherwise this bundle could not be used for updating an older version. Therefore we continue with version in the 4.x range. 4.3.0 sounds good to me > 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)
[jira] [Commented] (SLING-6739) split sling.event into event.api and event.resource (was: event.impl)
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974409#comment-15974409 ] Stefan Egli commented on SLING-6739: h6. step 11 : sling.event.api 1.0.0 vote succeeded, release done next step: embedding event.api into event.resource and releasing it. In theory nothing changes for users of the event.resource bundle, but we're likely going to change the artifactId. So the question is, what version should event.resource be getting, is it 1.0.0 or 4.3.0 or 4.2.4. [~cziegeler], wdyt? > 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)
