Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Carsten Ziegeler
I added the switch. If anyone wants improvements to this, please directly commit or PR Thanks Carsten On 21.07.2023 06:32, Carsten Ziegeler wrote: Sure, we can make this configurable. Nevertheless, I strongly suggest everyone to not rely on this method returning null for the anonymous case

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Carsten Ziegeler
Sure, we can make this configurable. Nevertheless, I strongly suggest everyone to not rely on this method returning null for the anonymous case and rather use the other two methods - which always behaved spec compliant. Otherwise you might run into trouble once you combine two sources of code

[jira] [Commented] (SLING-11975) org.apache.sling.launchpad.base.jar fails to load on jdk 11.0.20 because it has malformed Zip64 extra fields

2023-07-20 Thread Mark Adamcin (Jira)
[ https://issues.apache.org/jira/browse/SLING-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745285#comment-17745285 ] Mark Adamcin commented on SLING-11975: -- [~rombert] [~cziegeler] Would one of you be able to review

[jira] [Updated] (SLING-11975) org.apache.sling.launchpad.base.jar fails to load on jdk 11.0.20 because it has malformed Zip64 extra fields

2023-07-20 Thread Mark Adamcin (Jira)
[ https://issues.apache.org/jira/browse/SLING-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Adamcin updated SLING-11975: - Labels: has-pr (was: ) > org.apache.sling.launchpad.base.jar fails to load on jdk 11.0.20

[jira] [Created] (SLING-11975) org.apache.sling.launchpad.base.jar fails to load on jdk 11.0.20 because it has malformed Zip64 extra fields

2023-07-20 Thread Mark Adamcin (Jira)
Mark Adamcin created SLING-11975: Summary: org.apache.sling.launchpad.base.jar fails to load on jdk 11.0.20 because it has malformed Zip64 extra fields Key: SLING-11975 URL:

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Eric Norman
Carsten, unfortunately, it seems that the problem is more complicated than how you have described it. There have been 2 public releases of org.apache.sling.engine with the fix from SLING-11825 included. People (including me) have already migrated to those releases and made changes to their code

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Carsten Ziegeler
Good point, I updated them https://github.com/apache/sling-org-apache-sling-api/commit/b76ab7e07c79dab4cd89eb25784848c2f5ad2732 Regards Carsten On 20.07.2023 15:22, Robert Munteanu wrote: +/** + * Returns a java.security.Principal object containing + * the name of the current

[jira] [Updated] (SLING-11974) Regression caused by SLING-11825 - change in request getUserPrincipal

2023-07-20 Thread Carsten Ziegeler (Jira)
[ https://issues.apache.org/jira/browse/SLING-11974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-11974: - Fix Version/s: API 2.27.4 > Regression caused by SLING-11825 - change in request

[GitHub] [sling-org-apache-sling-graphql-core] sonarcloud[bot] commented on pull request #29: SLING-11458 - fixed a regresssion for the original Ticket SLING-9626

2023-07-20 Thread via GitHub
sonarcloud[bot] commented on PR #29: URL: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/29#issuecomment-1644034452 Kudos, SonarCloud Quality Gate passed! [![Quality Gate

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Robert Munteanu
On Thu, 2023-07-20 at 14:34 +0200, Carsten Ziegeler wrote: > Sure, the question is where? > > I looked at our existing docs, and we actually document how to check > for > anonymous access. But that is a little bit hidden, embedded in > outdated > docs We can start with the javadoc of the

Re: Integration problem Eclipse <> Sling 12

2023-07-20 Thread Konrad Windszus
Hi Juerg, It would help, if you can try testing the latest SNAPSHOT as outlined in https://sling.apache.org/documentation/development/ide-tooling.html#update-site-installation (there is a p2 update site at https://nightlies.apache.org/sling/eclipse/) The upcoming version has lots of issues fixed

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Carsten Ziegeler
Hi, yes I'm heavily opting for 2) :) you know I initially approved your PR thinking that this should not break any of Sling's users. Well, today I know that this assumption was wrong. I know of several users which currently rely on the wrong behaviour - and changing it breaks them. The

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Konrad Windszus
> On 20. Jul 2023, at 12:53, Carsten Ziegeler wrote: > > I think there is no one solution fits all here. As always it depends. Yes, I agree with that. I was referring to this specific use case. > > In general we should try to be spec compliant - unless there is a good reason > not to. There

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Carsten Ziegeler
Sure, the question is where? I looked at our existing docs, and we actually document how to check for anonymous access. But that is a little bit hidden, embedded in outdated docs Regards Carsten On 20.07.2023 13:06, Jörg Hoh wrote: Should we document that in this case we are not spec

Re: Integration problem Eclipse <> Sling 12

2023-07-20 Thread JCR
On 18.07.23 16:06, JCR wrote: Hello I run Sling 12 docker oak-tar on an Ubuntu Server. Connecting to it with Eclipse, I've seen the pretty weirdest thing ever. The Eclipse plugin 1.2.2, tested with  Eclipse versions 2020-03, 2021-03 and 2022-03 (on 2023-03, the plugin turned out to be not

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Jörg Hoh
Should we document that in this case we are not spec compliant for backwards compatibility reasons? Am Do., 20. Juli 2023 um 12:53 Uhr schrieb Carsten Ziegeler < cziege...@apache.org>: > I think there is no one solution fits all here. As always it depends. > > In general we should try to be spec

Re: SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Carsten Ziegeler
I think there is no one solution fits all here. As always it depends. In general we should try to be spec compliant - unless there is a good reason not to. There could be different reasons. In this particular case, imho there is a good reason to not be compliant. We have a huge user base and

SLING-11974: Spec Compliance vs. Backward compatibility

2023-07-20 Thread Konrad Windszus
Hi, Carsten just reverted the fix from https://issues.apache.org/jira/browse/SLING-11825 in https://issues.apache.org/jira/browse/SLING-11974. The fix is correct according to the Servlet Spec, but it seems some customer rely on Sling behaving not spec compliant here. The question is what weighs

Re: [VOTE] Release Apache Sling Auth Core 1.6.2

2023-07-20 Thread Jörg Hoh
+1 Am Do., 20. Juli 2023 um 07:19 Uhr schrieb Carsten Ziegeler < cziege...@apache.org>: > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING-11867 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2771 > > You can

RE: [VOTE] Release Apache Sling Auth Core 1.6.2

2023-07-20 Thread Stefan Seifert
+1 stefan

Re: [VOTE] Release Apache Sling GraphQL Core 0.0.22

2023-07-20 Thread Andreas Schaefer
+1 (non-binding) Thank to Radu for cutting the release for me due to my travel. - Andy > On Jul 20, 2023, at 9:49 AM, Radu Cotescu wrote: > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12353082 > > Staging repository: >

[VOTE] Release Apache Sling GraphQL Core 0.0.22

2023-07-20 Thread Radu Cotescu
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12353082 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2772/ You can use this UNIX script to download the release and verify the signatures:

[jira] [Updated] (SLING-10901) Allow terminating a GraphQL query after a configured timeout

2023-07-20 Thread Radu Cotescu (Jira)
[ https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-10901: - Fix Version/s: GraphQL Core 0.0.24 (was: GraphQL Core 0.0.22) > Allow

[jira] [Resolved] (SLING-11920) Expose Object Type Names in Selected Field

2023-07-20 Thread Radu Cotescu (Jira)
[ https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-11920. -- Resolution: Fixed > Expose Object Type Names in Selected Field >

[GitHub] [sling-org-apache-sling-graphql-core] schaefa merged pull request #36: SLING-11920 - Expose Object Type Names as replacement for Inlined Fragments

2023-07-20 Thread via GitHub
schaefa merged PR #36: URL: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/36 -- 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: [VOTE] Release Apache Sling Auth Core 1.6.2

2023-07-20 Thread Robert Munteanu
On Thu, 2023-07-20 at 07:19 +0200, Carsten Ziegeler wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part