[jira] [Commented] (SLING-11988) Apache Sling Testing Sling Mock Core Vulnerabilities

[ https://issues.apache.org/jira/browse/SLING-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754844#comment-17754844 ] Nok Arrenu commented on SLING-11988: [~sseifert] - Thank you so much for responding to this ticket

[GitHub] [sling-maven-enforcer-rules] dependabot[bot] opened a new pull request, #4: Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1

dependabot[bot] opened a new pull request, #4: URL: https://github.com/apache/sling-maven-enforcer-rules/pull/4 Bumps [org.apache.maven:maven-core](https://github.com/apache/maven) from 3.2.5 to 3.8.1. Commits

Re: [VOTE] Release Apache Sling Testing ResourceResolver Mock 1.4.4, Testing OSGi Mock 3.3.10, Testing Sling Mock 3.4.12

On Tue, 2023-08-15 at 13:57 +, Stefan Seifert wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Engine 2.15.6

+1 (non-binding) - Andy > On Aug 15, 2023, at 6:26 AM, Radu Cotescu wrote: > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353543=Text > > Staging repository: >

Re: [VOTE] Release Apache Sling Testing ResourceResolver Mock 1.4.4, Testing OSGi Mock 3.3.10, Testing Sling Mock 3.4.12

+1 Carsten On 15.08.2023 15:57, Stefan Seifert wrote: Hi, Testing ResourceResolver Mock 1.4.4 (2 issues) https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353251 Testing OSGi Mock 3.3.10 (3 issues)

RE: [VOTE] Release Apache Sling Testing ResourceResolver Mock 1.4.4, Testing OSGi Mock 3.3.10, Testing Sling Mock 3.4.12

+1 stefan

RE: [VOTE] Release Apache Sling Engine 2.15.6

+1 stefan

[VOTE] Release Apache Sling Testing ResourceResolver Mock 1.4.4, Testing OSGi Mock 3.3.10, Testing Sling Mock 3.4.12

Hi, Testing ResourceResolver Mock 1.4.4 (2 issues) https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353251 Testing OSGi Mock 3.3.10 (3 issues) https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353250 Testing Sling Mock 3.4.12 (4 issues)

[jira] [Resolved] (SLING-11796) The ResourceResolverFactory dependency should be dynamic

[ https://issues.apache.org/jira/browse/SLING-11796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-11796. -- Resolution: Fixed > The ResourceResolverFactory dependency should be dynamic >

[GitHub] [sling-org-apache-sling-servlets-resolver] cziegeler merged pull request #41: SLING-11796 - The ResourceResolverFactory dependency should be dynamic

cziegeler merged PR #41: URL: https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/41 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [VOTE] Release Apache Sling Engine 2.15.6

+1 Carsten On 15.08.2023 15:26, Radu Cotescu wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353543=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2778/ You can use this

[GitHub] [sling-org-apache-sling-servlets-resolver] sonarcloud[bot] commented on pull request #41: Manage updates of search paths with separate service/component

sonarcloud[bot] commented on PR #41: URL: https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/41#issuecomment-1678949130 SonarCloud Quality Gate failed. [![Quality Gate

[VOTE] Release Apache Sling Engine 2.15.6

Hi, We solved 1 issue in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353543=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2778/ You can use this UNIX script to download the release and verify the

[jira] [Resolved] (SLING-12003) The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

[ https://issues.apache.org/jira/browse/SLING-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-12003. -- Resolution: Fixed > The RequestDispatcher should flush the buffer on forward only if the

[GitHub] [sling-org-apache-sling-engine] raducotescu merged pull request #39: SLING-12003 - The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

raducotescu merged PR #39: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/39 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[jira] [Updated] (SLING-11916) MockEventAdminTest.testPostEvents times out on Jenkins/Windows

[ https://issues.apache.org/jira/browse/SLING-11916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-11916: --- Fix Version/s: (was: Testing OSGi Mock 3.3.10) the latest builds i observed did run

[jira] [Closed] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu closed SLING-11458. > Regress - "Writer has already been closed" exception in GraphQLServlet >

[jira] [Resolved] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-11458. -- Assignee: Radu Cotescu (was: Andreas Schaefer) Resolution: Not A Problem > Regress -

[GitHub] [sling-org-apache-sling-engine] sonarcloud[bot] commented on pull request #39: SLING-12003 - The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been cl

sonarcloud[bot] commented on PR #39: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/39#issuecomment-1678878207 Kudos, SonarCloud Quality Gate passed! [![Quality Gate

[jira] [Commented] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754634#comment-17754634 ] Robin Brouns commented on SLING-12001: -- Cool thanks [~sseifert]! > Can't use

[GitHub] [sling-org-apache-sling-engine] raducotescu opened a new pull request, #39: SLING-12003 - The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been close

raducotescu opened a new pull request, #39: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/39 * flush only if the response has not been committed -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[jira] [Resolved] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-12001. Resolution: Fixed ok, we're going with PR #11 keeping the handlers centrally in

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] stefanseifert merged pull request #11: SLING-12001 Store MockFindResourcesHandler/MockQueryResourceHandler in MockResourceResolverFactor

stefanseifert merged PR #11: URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] stefanseifert commented on pull request #10: SLING-12001 Allow to set MockFindResourcesHandler/MockQueryResourceHandler on MockResourceR

stefanseifert commented on PR #10: URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/10#issuecomment-1678826719 Replaced by #11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] stefanseifert closed pull request #10: SLING-12001 Allow to set MockFindResourcesHandler/MockQueryResourceHandler on MockResourceResolve

stefanseifert closed pull request #10: SLING-12001 Allow to set MockFindResourcesHandler/MockQueryResourceHandler on MockResourceResolverFactory URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/10 -- This is an automated message from the Apache Git

[jira] [Commented] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754534#comment-17754534 ] Robin Brouns commented on SLING-12001: -- True, for the unit tests, it doesn't matter that much. If

[jira] [Resolved] (SLING-12002) sling-mock: Prevent StdOut logging from ESAPI

[ https://issues.apache.org/jira/browse/SLING-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-12002. Resolution: Fixed

[GitHub] [sling-org-apache-sling-testing-sling-mock] stefanseifert merged pull request #29: SLING-12002 Discard "special logging" to stdout from ESAPI

stefanseifert merged PR #29: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/29 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

[GitHub] [sling-org-apache-sling-testing-sling-mock] stefanseifert commented on pull request #29: SLING-12002 Discard "special logging" to stdout from ESAPI

stefanseifert commented on PR #29: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/29#issuecomment-1678644599 lets keep it simple for now... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[jira] [Assigned] (SLING-12003) The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

[ https://issues.apache.org/jira/browse/SLING-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-12003: Assignee: Radu Cotescu > The RequestDispatcher should flush the buffer on forward only

[jira] [Commented] (SLING-11998) SlingPostServlet responds with wrong status code upon Oak Access error

[ https://issues.apache.org/jira/browse/SLING-11998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754507#comment-17754507 ] Juerg Meier commented on SLING-11998: - [~rombert] The version used is the offical Sling12 "LTS"

[jira] [Commented] (SLING-12003) The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

[ https://issues.apache.org/jira/browse/SLING-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754504#comment-17754504 ] Radu Cotescu commented on SLING-12003: -- Exactly. I could submit a PR, unless you want to take this

[jira] [Commented] (SLING-12003) The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

[ https://issues.apache.org/jira/browse/SLING-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754501#comment-17754501 ] Carsten Ziegeler commented on SLING-12003: -- So we could the isCommitted() check around the

[jira] [Comment Edited] (SLING-12003) The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

[ https://issues.apache.org/jira/browse/SLING-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754501#comment-17754501 ] Carsten Ziegeler edited comment on SLING-12003 at 8/15/23 9:00 AM: --- So

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] sonarcloud[bot] commented on pull request #11: SLING-12001 Store MockFindResourcesHandler/MockQueryResourceHandler in MockResourceResolv

sonarcloud[bot] commented on PR #11: URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/11#issuecomment-1678622181 Kudos, SonarCloud Quality Gate passed! [![Quality Gate

[jira] [Commented] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754499#comment-17754499 ] Stefan Seifert commented on SLING-12001: well, this would be a completely different but also

[jira] [Commented] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754497#comment-17754497 ] Radu Cotescu commented on SLING-11458: -- The GraphQL Servlet doesn't do anything wrong. The error

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] stefanseifert opened a new pull request, #11: SLING-12001 Store MockFindResourcesHandler/MockQueryResourceHandler in MockResourceResolve

stefanseifert opened a new pull request, #11: URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/11 https://issues.apache.org/jira/browse/SLING-12001 -- This is an automated message from the Apache Git Service. To respond to the message, please log

[jira] [Created] (SLING-12003) The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed

Radu Cotescu created SLING-12003: Summary: The RequestDispatcher should flush the buffer on forward only if the buffer hasn't already been closed Key: SLING-12003 URL:

[jira] [Commented] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754489#comment-17754489 ] Robin Brouns commented on SLING-12001: -- Looks good to me [~sseifert]! This will fix indeed the

[jira] [Updated] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-12001: --- Fix Version/s: Testing ResourceResolver Mock 1.4.4 > Can't use MockFindQueryResources when

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] sonarcloud[bot] commented on pull request #10: SLING-12001 Allow to set MockFindResourcesHandler/MockQueryResourceHandler on MockResourc

sonarcloud[bot] commented on PR #10: URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/10#issuecomment-1678578435 Kudos, SonarCloud Quality Gate passed! [![Quality Gate

[jira] [Commented] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754480#comment-17754480 ] Stefan Seifert commented on SLING-12001: [~robin.bro...@amplexor.com] good idea, i've created a

[GitHub] [sling-org-apache-sling-testing-resourceresolver-mock] stefanseifert opened a new pull request, #10: SLING-12001 Allow to set MockFindResourcesHandler/MockQueryResourceHandler on MockResource

stefanseifert opened a new pull request, #10: URL: https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/10 https://issues.apache.org/jira/browse/SLING-12001 -- This is an automated message from the Apache Git Service. To respond to the message, please log

[jira] [Assigned] (SLING-12001) Can't use MockFindQueryResources when making use of getServiceResourceResolver

[ https://issues.apache.org/jira/browse/SLING-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert reassigned SLING-12001: -- Assignee: Stefan Seifert > Can't use MockFindQueryResources when making use of

[jira] [Updated] (SLING-12002) sling-mock: Prevent StdOut logging from ESAPI

[ https://issues.apache.org/jira/browse/SLING-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-12002: --- Description: since SLING-10391 the ESAPI outputs a bunch of log messages to stdout each

[GitHub] [sling-org-apache-sling-testing-sling-mock] sonarcloud[bot] commented on pull request #29: SLING-12002 Discard "special logging" to stdout from ESAPI

sonarcloud[bot] commented on PR #29: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/29#issuecomment-1678534816 Kudos, SonarCloud Quality Gate passed! [![Quality Gate

[GitHub] [sling-org-apache-sling-testing-sling-mock] sonarcloud[bot] commented on pull request #29: SLING-12002 Discard "special logging" to stdout from ESAPI

sonarcloud[bot] commented on PR #29: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/29#issuecomment-1678534571 Kudos, SonarCloud Quality Gate passed! [![Quality Gate

[GitHub] [sling-org-apache-sling-testing-sling-mock] stefanseifert opened a new pull request, #29: SLING-12002 Discard "special logging" to stdout from ESAPI

stefanseifert opened a new pull request, #29: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/29 https://issues.apache.org/jira/browse/SLING-12002 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[jira] [Created] (SLING-12002) sling-mock: Prevent StdOut logging from ESAPI

Stefan Seifert created SLING-12002: -- Summary: sling-mock: Prevent StdOut logging from ESAPI Key: SLING-12002 URL: https://issues.apache.org/jira/browse/SLING-12002 Project: Sling Issue

[jira] [Commented] (SLING-10391) Improve MockXSSAPIImpl

[ https://issues.apache.org/jira/browse/SLING-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754462#comment-17754462 ] Stefan Seifert commented on SLING-10391: i've found a separate system property

[jira] [Updated] (SLING-12002) sling-mock: Prevent StdOut logging from ESAPI

[ https://issues.apache.org/jira/browse/SLING-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-12002: --- Fix Version/s: Testing Sling Mock 3.4.12 > sling-mock: Prevent StdOut logging from ESAPI >