Re: Error migrating to latest version of the bundles - Can neither derive user name nor principal names (was: Slow queries and unexpected results)

Hi all, I think I have a theory for our issues here, and it may have to do with the fact that we are running on a heavily containerized environment (kubernetes). I wanted to consult with the community experts to see what you thought. The way our container platform works on an update is that it wi

[jira] [Updated] (SLING-9054) [HTL] htl-maven-plugin: show warning for redundant use of data-sly-unwrap

[ https://issues.apache.org/jira/browse/SLING-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Yelizarenko updated SLING-9054: - Priority: Minor (was: Major) > [HTL] htl-maven-plugin: show warning for redundant use of

[jira] [Created] (SLING-9054) [HTL] htl-maven-plugin: show warning for redundant use of data-sly-unwrap

Maxim Yelizarenko created SLING-9054: Summary: [HTL] htl-maven-plugin: show warning for redundant use of data-sly-unwrap Key: SLING-9054 URL: https://issues.apache.org/jira/browse/SLING-9054 Proje

Re: [RESULT][VOTE] Release Apache Sling JCR Packageinit 1.0.0

On Tue, 2020-02-04 at 10:13 -0800, Andreas Schaefer wrote: > In order to promote the release can a PMC push the release to > https://dist.apache.org/repos/dist/release/sling/ e.org/repos/dist/release/sling/> ? Done in r37890. Thanks! Robert

Re: [mocks] Injecting references for a class with no SCR metadata?

Hello Stefan, On Wed, 2020-01-29 at 10:56 +, Stefan Seifert wrote: > hello robert. > > the SCR metadata is currently only found if the class name matches > exactly. not sure if we should change the default behavior of osgi > mocks here as this should be the same in a real OSGi behavior (like

[jira] [Updated] (SLING-9045) Add option to process requests with querystring parameters

[ https://issues.apache.org/jira/browse/SLING-9045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-9045: --- Fix Version/s: Dynamic Include 3.2.0 > Add option to process requests with querystring parame

[GitHub] [sling-org-apache-sling-dynamic-include] rombert commented on issue #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check

rombert commented on issue #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/13#issuecomment-582643896 ... and note that I merged the PR that removes the package exports, so you do not n

[jira] [Resolved] (SLING-8987) Remove exported packages

[ https://issues.apache.org/jira/browse/SLING-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-8987. Assignee: Robert Munteanu Resolution: Fixed > Remove exported packages >

[jira] [Resolved] (SLING-8982) dynamic-include: upgrade to parent pom 35

[ https://issues.apache.org/jira/browse/SLING-8982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-8982. Resolution: Fixed > dynamic-include: upgrade to parent pom 35 > ---

[jira] [Updated] (SLING-8987) Remove exported packages

[ https://issues.apache.org/jira/browse/SLING-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8987: --- Summary: Remove exported packages (was: Review exported packages) > Remove exported packages

[GitHub] [sling-org-apache-sling-dynamic-include] rombert merged pull request #12: SLING-8982 - dynamic-include: upgrade to parent pom 35

rombert merged pull request #12: SLING-8982 - dynamic-include: upgrade to parent pom 35 URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/12 This is an automated message from the Apache Git Service.

[GitHub] [sling-org-apache-sling-dynamic-include] rombert edited a comment on issue #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check

rombert edited a comment on issue #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/13#issuecomment-582642037 Thanks for picking this up @jfmitchell ! Some notes: 1. the build fail

[GitHub] [sling-org-apache-sling-dynamic-include] rombert commented on issue #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check

rombert commented on issue #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/13#issuecomment-582642037 Thanks for picking this up @jfmitchell ! Some notes: # the build fails ( see

[GitHub] [sling-org-apache-sling-dynamic-include] rombert commented on issue #1: Option to disable the URL params check when there is need to process all GET requests

rombert commented on issue #1: Option to disable the URL params check when there is need to process all GET requests URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/1#issuecomment-582640685 Closing in favour of #13 --

[GitHub] [sling-org-apache-sling-dynamic-include] rombert closed pull request #1: Option to disable the URL params check when there is need to process all GET requests

rombert closed pull request #1: Option to disable the URL params check when there is need to process all GET requests URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/1 This is an automated message

Re: Redirect Provider

Hi, Ok. o.a.s.api.redirect for the API, and a patch to the Get servlet to use the API. Will do PRs shortly. Best Regards Ian On Tue, 4 Feb 2020 at 14:13, Bertrand Delacretaz wrote: > On Tue, Feb 4, 2020 at 1:58 PM Ian Boston wrote: > > ...New package, agreed, no ripples. > > o.a.s.api.respon

[jira] [Assigned] (SLING-9051) Package handling should not auto save the session

[ https://issues.apache.org/jira/browse/SLING-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret reassigned SLING-9051: - Assignee: Timothee Maret > Package handling should not auto save the session > -

[jira] [Assigned] (SLING-9052) DistributionSubscriber is not failing correctly on OakConstraint0025

[ https://issues.apache.org/jira/browse/SLING-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret reassigned SLING-9052: - Assignee: Timothee Maret > DistributionSubscriber is not failing correctly on OakConstr

[jira] [Assigned] (SLING-9050) Failures to extract or install the packages are not reported to the upper layer

[ https://issues.apache.org/jira/browse/SLING-9050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret reassigned SLING-9050: - Assignee: Timothee Maret > Failures to extract or install the packages are not reported

[jira] [Assigned] (SLING-9049) ExtendedDistributionServiceResourceProvider fails with unknown nodestructures

[ https://issues.apache.org/jira/browse/SLING-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret reassigned SLING-9049: - Assignee: Timothee Maret > ExtendedDistributionServiceResourceProvider fails with unknow

[jira] [Created] (SLING-9053) Implement retries mechanism for AbstractSlingClient.doRequest(...)

Thierry Ygé created SLING-9053: -- Summary: Implement retries mechanism for AbstractSlingClient.doRequest(...) Key: SLING-9053 URL: https://issues.apache.org/jira/browse/SLING-9053 Project: Sling

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

Many things are named quickstart, for example bnd uses the term as well. I personally don't think that this is a problem, as the term "quickstart" is always used in a context, being it Sling, Adobe, bnd etc. If we think that quickstart is confusing, than I think kickstart or cloudstart are con

[jira] [Commented] (SLING-9046) Provide analyser that checks bundles for embedded bundles

[ https://issues.apache.org/jira/browse/SLING-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030898#comment-17030898 ] Carsten Ziegeler commented on SLING-9046: - It is probably not reliable - especial

[jira] [Created] (SLING-9052) DistributionSubscriber is not failing correctly on OakConstraint0025

Dominik Süß created SLING-9052: -- Summary: DistributionSubscriber is not failing correctly on OakConstraint0025 Key: SLING-9052 URL: https://issues.apache.org/jira/browse/SLING-9052 Project: Sling

[jira] [Created] (SLING-9051) Package handling should not auto save the session

Dominik Süß created SLING-9051: -- Summary: Package handling should not auto save the session Key: SLING-9051 URL: https://issues.apache.org/jira/browse/SLING-9051 Project: Sling Issue Type: Bug

[GitHub] [sling-org-apache-sling-commons-scheduler] ieb commented on issue #3: Adding target name=sling for MetricRegistry referene

ieb commented on issue #3: Adding target name=sling for MetricRegistry referene URL: https://github.com/apache/sling-org-apache-sling-commons-scheduler/pull/3#issuecomment-582499467 lgtm, the name of the metrics registry doesnt change compared to systems running in production now. They alr

[GitHub] [sling-org-apache-sling-commons-scheduler] ieb merged pull request #3: Adding target name=sling for MetricRegistry referene

ieb merged pull request #3: Adding target name=sling for MetricRegistry referene URL: https://github.com/apache/sling-org-apache-sling-commons-scheduler/pull/3 This is an automated message from the Apache Git Service. To resp

[jira] [Created] (SLING-9050) Failures to extract or install the packages are not reported to the upper layer

Dominik Süß created SLING-9050: -- Summary: Failures to extract or install the packages are not reported to the upper layer Key: SLING-9050 URL: https://issues.apache.org/jira/browse/SLING-9050 Project: Sl

[jira] [Created] (SLING-9049) ExtendedDistributionServiceResourceProvider fails with unknown nodestructures

Dominik Süß created SLING-9049: -- Summary: ExtendedDistributionServiceResourceProvider fails with unknown nodestructures Key: SLING-9049 URL: https://issues.apache.org/jira/browse/SLING-9049 Project: Sli

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

Hi As an motorbike driver I would suggest “kickstart” as the name making it: - sling-kickstart - sling-kickstart-maven-plugin Let me know if that works and I’ll adjust the Whiteboard - Andy > On Feb 5, 2020, at 7:39 AM, Bertrand Delacretaz > wrote: > > On Wed, Feb 5, 2020 at 4:32 PM Ruben R

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

On Wed, Feb 5, 2020 at 4:32 PM Ruben Reusser wrote: > > how about crankstart, cloudstart or jumpstart?... Crankstart was already used for a previous experimental launcher. The other ones work for me. I think we should let Andy decide on a name, considering how much work he's put into this! -Be

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

how about crankstart, cloudstart or jumpstart? On 2/5/2020 1:42 AM, Bertrand Delacretaz wrote: On Wed, Feb 5, 2020 at 10:12 AM Robert Munteanu wrote: ...First all all - thanks Andy for your persistence Indeed, I think we owe Andy multiple beverages-of-his-choice! ...I see some confusion

[jira] [Commented] (SLING-9046) Provide analyser that checks bundles for embedded bundles

[ https://issues.apache.org/jira/browse/SLING-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030718#comment-17030718 ] A. J. David Bosschaert commented on SLING-9046: --- Right I was wondering how

Re: [VOTE] Release Apache Sling Parent 37 and Sling Bundle Parent 37

+1 On Tue, Feb 4, 2020 at 2:35 PM wrote: > +1 > > David > > On Tue, 4 Feb 2020 at 15:47, Konrad Windszus wrote: > > > Hi, > > > > We solved several issues in this release: > > https://issues.apache.org/jira/projects/SLING/versions/12346744 (Parent > > 37) > > https://issues.apache.org/jira/proj

[jira] [Resolved] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[ https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-9048. - Resolution: Fixed Fixed in [commit a584639|https://github.com/apache/sling-org-apache-sling-scri

[jira] [Assigned] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[ https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-9048: --- Assignee: Radu Cotescu > The HTL engine does not specify the correct io.sightly.runtime requ

[jira] [Updated] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[ https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-9048: Priority: Minor (was: Major) > The HTL engine does not specify the correct io.sightly.runtime requ

[jira] [Created] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

Radu Cotescu created SLING-9048: --- Summary: The HTL engine does not specify the correct io.sightly.runtime requirement version range Key: SLING-9048 URL: https://issues.apache.org/jira/browse/SLING-9048

[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #568 is BROKEN

Please see https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/568/ for details. No further emails will be sent until the status of the build is changed. Build log follows below: [...truncated 2663 lines...] [INFO] Tests run: 2, Failures: 0, Errors: 0, Sk

[jira] [Resolved] (SLING-9047) The CIStatusValidator cannot verify multi-module releases

[ https://issues.apache.org/jira/browse/SLING-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-9047. - Resolution: Fixed Fixed in [commit 646b413|https://github.com/apache/sling-org-apache-sling-comm

[jira] [Created] (SLING-9047) The CIStatusValidator cannot verify multi-module releases

Radu Cotescu created SLING-9047: --- Summary: The CIStatusValidator cannot verify multi-module releases Key: SLING-9047 URL: https://issues.apache.org/jira/browse/SLING-9047 Project: Sling Issue T

[jira] [Assigned] (SLING-9047) The CIStatusValidator cannot verify multi-module releases

[ https://issues.apache.org/jira/browse/SLING-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-9047: --- Assignee: Radu Cotescu > The CIStatusValidator cannot verify multi-module releases > ---

[jira] [Commented] (SLING-8946) Non-deterministic shadowing of resource observation

[ https://issues.apache.org/jira/browse/SLING-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030589#comment-17030589 ] Sonal Gupta commented on SLING-8946: [~diru] Can you please look into these failures

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

On Wed, Feb 5, 2020 at 10:12 AM Robert Munteanu wrote: > ...First all all - thanks Andy for your persistence Indeed, I think we owe Andy multiple beverages-of-his-choice! > ...I see some confusion potential where people would be applying AEM > quickstart knowledge to the Sling quickstart and

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.8

+1 > On 4 Feb 2020, at 16:23, dav...@apache.org wrote: > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours.

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

Hi, On Wed, 2020-02-05 at 09:54 +0100, Bertrand Delacretaz wrote: > Hi, > > On Wed, Feb 5, 2020 at 1:19 AM Andreas Schaefer > wrote: > > ...This is a vote to promote the sling-org-apache-sling-quickstart > > and > > sling-quickstart-maven-plugin to their own Sling Module... First all all - than

Re: [VOTE] Promote sling-org-apache-sling-quickstart / sling-quickstart-maven-plugin to their own Sling Modules

Hi, On Wed, Feb 5, 2020 at 1:19 AM Andreas Schaefer wrote: > ...This is a vote to promote the sling-org-apache-sling-quickstart and > sling-quickstart-maven-plugin to their own Sling Module... I'm sorry if I missed a discussion about this name change (can't see it in this list's archives) but I'