[jira] [Commented] (SLING-6739) split sling.event into event.api and event.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965548#comment-15965548 ] Stefan Egli commented on SLING-6739: h6. step 10: sling.event.api 1.0.0 released (staging repo [1686|https://repository.apache.org/content/repositories/orgapachesling-1686/]), vote pending > split sling.event into event.api and 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965530#comment-15965530 ] Stefan Egli commented on SLING-6739: h6. step 9: event/api/pom.xml : port-java8 and surefire-plugin removed (http://svn.apache.org/viewvc?rev=1791086=rev) > split sling.event into event.api and 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965521#comment-15965521 ] Stefan Egli commented on SLING-6739: h6. step 8: event/api/pom.xml : site.jira.version.id set to Event API 1.0.0 (http://svn.apache.org/viewvc?rev=1791084=rev) > split sling.event into event.api and 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964584#comment-15964584 ] Stefan Egli commented on SLING-6739: h6. step 7: event/api/pom.xml : removed unnecessary properties (http://svn.apache.org/viewvc?rev=1790997=rev) > split sling.event into event.api and 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 > > 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946862#comment-15946862 ] Stefan Egli commented on SLING-6739: h6. step 6: event/api/README adjusted (http://svn.apache.org/viewvc?rev=1789319=rev) > split sling.event into event.api and 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 > > 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946855#comment-15946855 ] Stefan Egli commented on SLING-6739: h6. step 5: further cleanup of the event/api/pom.xml (http://svn.apache.org/viewvc?rev=1789318=rev) > split sling.event into event.api and 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 > > 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946810#comment-15946810 ] Stefan Egli commented on SLING-6739: h6. step 4: initial adjustment of event/resource/pom.xml, just renaming the bundle symbolic name and version (http://svn.apache.org/viewvc?rev=1789306=rev) > split sling.event into event.api and 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 > > 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-impl > 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.impl
[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946737#comment-15946737 ] Stefan Egli commented on SLING-6739: h6. step 3: initial adjustment of event/api/pom.xml, removing of non applicable files (http://svn.apache.org/viewvc?rev=1789298=rev) > split sling.event into event.api and 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 > > 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-impl > 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.impl
[
https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946697#comment-15946697
]
Stefan Egli commented on SLING-6739:
h6. step 1: svn renamed event to event-renamed-for-split and svn copied it to
event/api and event/resource
(http://svn.apache.org/viewvc?rev=1789290=rev):
{noformat}
svn mv event event-renamed-for-split
mkdir event
svn add event
cd event
svn cp ../event-renamed-for-split api
svn cp ../event-renamed-for-split resource
svn commit -m "SLING-6739 : copied bundles/extensions/event into event/api and
event/resources - done via svn cp to preserve history of both new parts"
{noformat}
h6. step 2: removed event-renamed-for-split
(http://svn.apache.org/viewvc?rev=1789291=rev)
{noformat}
svn rm event-renamed-for-split
svn commit -m "SLING-6739 : removed temp directory event-renamed-for-split"
{noformat}
> split sling.event into event.api and 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
>
> 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-impl
> and to remove the current
> bundles/extensions/event
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
