[jira] [Commented] (SLING-6782) Sling Job implementation should avoid unnecessary writes to the repository

[ https://issues.apache.org/jira/browse/SLING-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975467#comment-15975467 ] Jörg Hoh commented on SLING-6782: - For this case I adapted the ResourceHelper.getOrCreateResourceInternal

[jira] [Updated] (SLING-6782) Sling Job implementation should avoid unnecessary writes to the repository

[ https://issues.apache.org/jira/browse/SLING-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Hoh updated SLING-6782: Attachment: SLING-6782-jobs-commit-to-often-2.patch > Sling Job implementation should avoid unnecessary

[jira] [Commented] (SLING-6782) Sling Job implementation should avoid unnecessary writes to the repository

[ https://issues.apache.org/jira/browse/SLING-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975316#comment-15975316 ] Jörg Hoh commented on SLING-6782: - Hi Carsten, good point. But from my point of view in the context of

[jira] [Commented] (SLING-6782) Sling Job implementation should avoid unnecessary writes to the repository

[ https://issues.apache.org/jira/browse/SLING-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975448#comment-15975448 ] Carsten Ziegeler commented on SLING-6782: - Right - I thought that's exactly what I wrote :) >

Maven Content Package Plugin

Hi I started working on making the wcm-io content package maven plugin to work with Composum so that JCR content packages can be deployed w/o Adobe’s maven plugin. For that I created a ticket here: https://wcm-io.atlassian.net/browse/WTOOL-29 Cheers - Andy

[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=15974457#comment-15974457 ] Stefan Egli commented on SLING-6739: bq. However we should not change the bundle symbolic name,

[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=15974409#comment-15974409 ] Stefan Egli commented on SLING-6739: h6. step 11 : sling.event.api 1.0.0 vote succeeded, release done

[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=15974445#comment-15974445 ] Carsten Ziegeler commented on SLING-6739: - Not sure if we need to change the artifact id - it

Re: [VOTE] Release Apache Sling Event API 1.0.0 (initial release)

+1 Cheers, Stefan On 12/04/17 10:32, "Stefan Egli" wrote: >Hi, > >This is about the first (API) part of splitting Sling Event into two >bundles (API and Impl). Since it is an initial release it might make sense >to review the pom extra this time. This split is tracked

[RESULT][VOTE] Release Apache Sling Event API 1.0.0 (initial release)

The vote succeeded with 3 binding and one non-binding votes. I'll proceed with the release next. Cheers, Stefan On 12/04/17 10:32, "Stefan Egli" wrote: >Hi, > >This is about the first (API) part of splitting Sling Event into two >bundles (API and Impl). Since it is an