Re: [PR] SLING-12322 Stream Reader should Return SC_OK if content length is le… [sling-org-apache-sling-servlets-get]

2024-05-22 Thread via GitHub
abhishekgarg18 closed pull request #14: SLING-12322 Stream Reader should Return SC_OK if content length is le… URL: https://github.com/apache/sling-org-apache-sling-servlets-get/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[jira] [Resolved] (SLING-12322) Stream Reader should Return SC_OK if content length is less than specified range

2024-05-22 Thread Abhishek Garg (Jira)
[ https://issues.apache.org/jira/browse/SLING-12322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Garg resolved SLING-12322. --- Resolution: Not A Problem > Stream Reader should Return SC_OK if content length is less

[jira] [Commented] (SLING-12322) Stream Reader should Return SC_OK if content length is less than specified range

2024-05-22 Thread Abhishek Garg (Jira)
[ https://issues.apache.org/jira/browse/SLING-12322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848822#comment-17848822 ] Abhishek Garg commented on SLING-12322: --- This PR was handling the case when the request with the

[jira] [Commented] (SLING-12322) Stream Reader should Return SC_OK if content length is less than specified range

2024-05-22 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/SLING-12322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848818#comment-17848818 ] Konrad Windszus commented on SLING-12322: - I don’t think this is compliant with

[jira] [Commented] (SLING-12322) Stream Reader should Return SC_OK if content length is less than specified range

2024-05-22 Thread Abhishek Garg (Jira)
[ https://issues.apache.org/jira/browse/SLING-12322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848813#comment-17848813 ] Abhishek Garg commented on SLING-12322: --- create a draft PR

[PR] SLING-12322 Stream Reader should Return SC_OK if content length is le… [sling-org-apache-sling-servlets-get]

2024-05-22 Thread via GitHub
abhishekgarg18 opened a new pull request, #14: URL: https://github.com/apache/sling-org-apache-sling-servlets-get/pull/14 …ss than specified range -- 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

[jira] [Created] (SLING-12322) Stream Reader should Return SC_OK if content length is less than specified range

2024-05-22 Thread Abhishek Garg (Jira)
Abhishek Garg created SLING-12322: - Summary: Stream Reader should Return SC_OK if content length is less than specified range Key: SLING-12322 URL: https://issues.apache.org/jira/browse/SLING-12322

[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #1384 is FIXED

2024-05-22 Thread Apache Jenkins Server
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/1384/ for details. No further emails will be sent until the status of the build is changed.

[jira] [Resolved] (SLING-12317) Make Sling Engine build with Java 21

2024-05-22 Thread Robert Munteanu (Jira)
[ https://issues.apache.org/jira/browse/SLING-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-12317. - Resolution: Fixed > Make Sling Engine build with Java 21 >

Re: [PR] SLING-12317 - Make Sling Engine build with Java 21 [sling-org-apache-sling-engine]

2024-05-22 Thread via GitHub
rombert commented on PR #45: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/45#issuecomment-2124809600 @joerghoh - all done. -- 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

Re: [PR] SLING-12317 - Make Sling Engine build with Java 21 [sling-org-apache-sling-engine]

2024-05-22 Thread via GitHub
rombert merged PR #45: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/45 -- 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:

Re: [PR] SLING-12318 apply spotless formatting [sling-org-apache-sling-engine]

2024-05-22 Thread via GitHub
rombert merged PR #44: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/44 -- 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] [Created] (SLING-12321) Update parent pom to latest

2024-05-22 Thread Joerg Hoh (Jira)
Joerg Hoh created SLING-12321: - Summary: Update parent pom to latest Key: SLING-12321 URL: https://issues.apache.org/jira/browse/SLING-12321 Project: Sling Issue Type: Task Components:

Re: [PR] SLING-12317 - Make Sling Engine build with Java 21 [sling-org-apache-sling-engine]

2024-05-22 Thread via GitHub
joerghoh commented on PR #45: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/45#issuecomment-2124762983 @rombert would appreciate that. I plan to upgrade parent pom afterwards (SLING-12321) -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] SLING-12283 : write config in correct format incase of factoryPid is … [sling-org-apache-sling-installer-provider-jcr]

2024-05-22 Thread via GitHub
jsedding commented on code in PR #9: URL: https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/pull/9#discussion_r1609457830 ## src/main/java/org/apache/sling/installer/provider/jcr/impl/JcrUtil.java: ## @@ -73,4 +75,21 @@ public static Node createPath(final

RE: [VOTE] Release Apache Sling JCR Resource 3.3.2

2024-05-22 Thread Stefan Seifert
+1 stefan

Re: [PR] SLING-12317 - Make Sling Engine build with Java 21 [sling-org-apache-sling-engine]

2024-05-22 Thread via GitHub
rombert commented on PR #45: URL: https://github.com/apache/sling-org-apache-sling-engine/pull/45#issuecomment-2124069446 @joerghoh - do you want to merge #44 first? I can then rebase, if needed. -- This is an automated message from the Apache Git Service. To respond to the message,