[jira] [Updated] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3502: Attachment: SLING-3502.patch Potential fix for the problem, checking if the queue to

[jira] [Commented] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970567#comment-13970567 ] Stefan Egli commented on SLING-3502: Thanks [~cziegeler] and [~pfa...@adobe.com] for

[jira] [Commented] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970568#comment-13970568 ] Marc Pfaff commented on SLING-3502: --- [~cziegeler]: The attached IT still fails with your

[jira] [Commented] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970572#comment-13970572 ] Stefan Egli commented on SLING-3502: [~pfa...@adobe.com], re bq. The attached IT still

[jira] [Commented] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970573#comment-13970573 ] Stefan Egli commented on SLING-3502: bq. JobManagerImpl.process() is another such

[jira] [Resolved] (SLING-3478) Facilitate writing of integration tests for multiple instances

[ https://issues.apache.org/jira/browse/SLING-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3478. Resolution: Fixed Thanks very much for your patch, I have commited it in

[jira] [Updated] (SLING-3478) Facilitate writing of integration tests for multiple instances

[ https://issues.apache.org/jira/browse/SLING-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3478: --- Fix Version/s: org.apache.sling.testing.tools 1.0.8 Sample

[jira] [Updated] (SLING-3478) Facilitate writing of integration tests for multiple instances

[ https://issues.apache.org/jira/browse/SLING-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3478: --- Affects Version/s: Sample Integration Tests 1.0.6

[jira] [Commented] (SLING-3478) Facilitate writing of integration tests for multiple instances

[ https://issues.apache.org/jira/browse/SLING-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970657#comment-13970657 ] Bertrand Delacretaz commented on SLING-3478: In http://svn.apache.org/r1587856

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2091

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2091/

Jenkins build became unstable: sling-trunk-1.6 #2091

See https://builds.apache.org/job/sling-trunk-1.6/2091/changes

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #462

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/462/

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #462

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/462/changes

[jira] [Created] (SLING-3503) JarExecutor should optionally wait for process in shutdown hook

Bertrand Delacretaz created SLING-3503: -- Summary: JarExecutor should optionally wait for process in shutdown hook Key: SLING-3503 URL: https://issues.apache.org/jira/browse/SLING-3503 Project:

[jira] [Resolved] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3502. Resolution: Fixed fixed, will be shipped in event 3.3.10 Main job queue is not properly outdated

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2092

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2092/

Jenkins build is still unstable: sling-trunk-1.6 #2092

See https://builds.apache.org/job/sling-trunk-1.6/changes

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #463

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/463/

Jenkins build is still unstable: sling-trunk-1.7 #463

See https://builds.apache.org/job/sling-trunk-1.7/changes

[CANCELL][VOTE] Release Apache Sling Event Support 3.3.8

Hi, This vote is cancelled. Reasons: * not enough +1 votes in time * new bugfix requiring release of 3.3.10 encountered * new vote re 3.3.10 will be sent out in a minute Cheers, Stefan On 4/10/14 10:17 AM, Stefan Egli e...@adobe.com wrote: Hi, We solved 1 ticketed issue: *

[VOTE] Release Apache Sling Event Support 3.3.10

Hi, Since 3.3.8 was cancelled, this vote is about cumulative release 3.3.10, which includes the following changes: * 3.3.10: fix for https://issues.apache.org/jira/browse/SLING-3502 * 3.3.8: 1 issue: * https://issues.apache.org/jira/browse/SLING/fixforversion/12326345 * 3.3.8: plus 2

[jira] [Commented] (SLING-3478) Facilitate writing of integration tests for multiple instances

[ https://issues.apache.org/jira/browse/SLING-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13971495#comment-13971495 ] Marius Petria commented on SLING-3478: -- Hi Bertrand, For replication I need to use

Jenkins build is back to stable : sling-trunk-1.7 #464

See https://builds.apache.org/job/sling-trunk-1.7/464/changes

Re: [VOTE] Release Apache Sling Commons Classloader 1.3.2

+1 Regards Felix Am 12.04.2014 um 02:19 schrieb Carsten Ziegeler cziege...@apache.org: Hi, We solved some issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12321292 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1048 You can

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2093

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2093/

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2093

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2093/

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling SLF4J Implementation (Logback) #2093

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.commons.log/2093/

Jenkins build is still unstable: sling-trunk-1.6 #2093

See https://builds.apache.org/job/sling-trunk-1.6/changes

Re: Support REST-ful APIs

Hi Am 14.04.2014 um 10:52 schrieb Alexander Klimetschek aklim...@adobe.com: Thanks Roy for clarifying things. Indeed and I will reply to that on a separate message. I think what it boils down to is that the only real thing that you'd want to move from the sling url (path info) to an

Re: Support REST-ful APIs

Hi Thanks for insights. Very helpful ! Am 13.04.2014 um 23:24 schrieb Roy T. Fielding field...@gbiv.com: On Apr 7, 2014, at 12:24 AM, Felix Meschberger wrote: TL;DR: Use Accept header to set request's selectors and extension. So an example Accept content type of application/x-players+json