[jira] [Commented] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584358#comment-16584358 ] Robert Munteanu commented on SLING-7833: [~jebailey] - not really, it was more of an educated

Re: [VOTE] Release Apache Sling API 2.18.4, Resource Resolver 1.6.6

+1 On Fri, Aug 17, 2018 at 1:02 PM Robert Munteanu wrote: > On Fri, 2018-08-17 at 19:02 +0200, Robert Munteanu wrote: > > Please vote to approve this release: > > +1 > > Robert >

[jira] [Commented] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584293#comment-16584293 ] Jason E Bailey commented on SLING-7833: --- [~rombert] any idea why that particular change caused the

Re: [VOTE] Release Apache Sling API 2.18.4, Resource Resolver 1.6.6

On Fri, 2018-08-17 at 19:02 +0200, Robert Munteanu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[VOTE] Release Apache Sling API 2.18.4, Resource Resolver 1.6.6

Hi, We solved 6 issues in these releases: https://issues.apache.org/jira/projects/SLING/versions/12343385 https://issues.apache.org/jira/browse/SLING/fixforversion/12343801 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1938 You can use this UNIX script

[jira] [Updated] (SLING-7510) UriProvider throws unchecked IllegalArgumentException that must be handled by consumers

[ https://issues.apache.org/jira/browse/SLING-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7510: --- Fix Version/s: (was: API 2.18.4) API 2.18.6 > UriProvider throws

[jira] [Updated] (SLING-7544) Make optimized alias lookup non-blocking

[ https://issues.apache.org/jira/browse/SLING-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7544: --- Fix Version/s: (was: Resource Resolver 1.6.6) Resource Resolver 1.6.8

[jira] [Closed] (SLING-7828) Generating adapter metadata fails when using Java 8 features: invalid constant type: 18

[ https://issues.apache.org/jira/browse/SLING-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7828. -- > Generating adapter metadata fails when using Java 8 features: invalid > constant type: 18 >

[RESULT] [VOTE] Release Apache Sling Maven Sling Plugin 2.3.8

Hi, The vote has passed with the following result : +1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert, Radu Cotescu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Robert

[jira] [Resolved] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7833. Resolution: Fixed Reverted changed to API bundle so that - test passes now (older

[jira] [Comment Edited] (SLING-7593) ResourceTraversor doesn't support ResourceDecorator pattern

[ https://issues.apache.org/jira/browse/SLING-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584111#comment-16584111 ] Robert Munteanu edited comment on SLING-7593 at 8/17/18 3:54 PM: -

[jira] [Commented] (SLING-7593) ResourceTraversor doesn't support ResourceDecorator pattern

[ https://issues.apache.org/jira/browse/SLING-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584111#comment-16584111 ] Robert Munteanu commented on SLING-7593: [~joana] - I unfortunately had to revert the changes to

[jira] [Commented] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584077#comment-16584077 ] Robert Munteanu commented on SLING-7833: Reverting the updates to the resourceresolver and api

[jira] [Updated] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7833: --- Fix Version/s: Resource Resolver 1.6.6 >

[jira] [Assigned] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-7833: -- Assignee: Robert Munteanu >

[jira] [Updated] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7792: --- Labels: Sling-11-ReleaseNotes (was: ) > Resource Resolver should return more than one

[jira] [Commented] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584022#comment-16584022 ] Robert Munteanu commented on SLING-7792: I've also updated the web console in

[jira] [Updated] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7792: --- Attachment: console.png > Resource Resolver should return more than one resolved path if

[jira] [Resolved] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-7832. Resolution: Fixed Jenkins build passed, there's one failure but from a different

[jira] [Resolved] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7792. Resolution: Fixed Fixed edge case in [sling-org-apache-sling-resourceresolver commit

[jira] [Updated] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-7832: --- Fix Version/s: Launchpad Testing Services 2.0.16 Launchpad

[jira] [Updated] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-7834: --- Fix Version/s: Launchpad Testing Services 2.0.16 > Transform

[jira] [Updated] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-7834: --- Fix Version/s: Launchpad Integration Tests 1.0.8 > Transform

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583961#comment-16583961 ] Bertrand Delacretaz commented on SLING-7832: Found the weirdness, the test uses the

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583956#comment-16583956 ] Robert Munteanu commented on SLING-7832: I think that this test fails only when run standalone,

[jira] [Commented] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583863#comment-16583863 ] Robert Munteanu commented on SLING-7834: Confirmed, thank you! > Transform

[jira] [Commented] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583858#comment-16583858 ] Bertrand Delacretaz commented on SLING-7834:

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583852#comment-16583852 ] Robert Munteanu commented on SLING-7832: I am running {{mvn clean verify}} in the

[jira] [Commented] (SLING-7830) Defined leader switch

[ https://issues.apache.org/jira/browse/SLING-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583848#comment-16583848 ] Carsten Ziegeler commented on SLING-7830: - Are those changes to the leaderElectionIds in the

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583843#comment-16583843 ] Bertrand Delacretaz commented on SLING-7832: You mean that it passes against a fresh Sling

[jira] [Reopened] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reopened SLING-7792: Reopening, seems I did not preserve some backwards compatibility scenarios {noformat}[ERROR]

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583833#comment-16583833 ] Robert Munteanu commented on SLING-7832: [~bdelacretaz] - actually the test passes for me, maybe

[jira] [Commented] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583832#comment-16583832 ] Bertrand Delacretaz commented on SLING-7834: Yes, those changes are certainly related. I

[jira] [Commented] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583828#comment-16583828 ] Robert Munteanu commented on SLING-7834: [~bdelacretaz] - that helps, thank you! I'm getting two

[jira] [Commented] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583776#comment-16583776 ] Bertrand Delacretaz commented on SLING-7834: oops, forgot something, one more commit:

[jira] [Assigned] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-7832: -- Assignee: Bertrand Delacretaz > ResourceResolverProxyTest fails: write(param)

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583769#comment-16583769 ] Bertrand Delacretaz commented on SLING-7832: That test was using the old proxied remote

[jira] [Resolved] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

[ https://issues.apache.org/jira/browse/SLING-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-7834. Resolution: Fixed Implemented by the below commits, the test is now in the main

[jira] [Created] (SLING-7834) Transform ResourceResolverProxyTest into a teleported test

Bertrand Delacretaz created SLING-7834: -- Summary: Transform ResourceResolverProxyTest into a teleported test Key: SLING-7834 URL: https://issues.apache.org/jira/browse/SLING-7834 Project: Sling

[jira] [Commented] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

[ https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583691#comment-16583691 ] Robert Munteanu commented on SLING-7832: [~bdelacretaz] - maybe you can shed some light into

[jira] [Resolved] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7792. Resolution: Fixed Fixed, with * [sling-org-apache-sling-api commit

[jira] [Commented] (SLING-7792) Resource Resolver should return more than one resolved path if available

[ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583663#comment-16583663 ] Robert Munteanu commented on SLING-7792: Thanks for the confirmation [~cziegeler]. For the

[GitHub] rombert closed pull request #9: SLING-7792 - Resource Resolver should return more than one resolved path if available

rombert closed pull request #9: SLING-7792 - Resource Resolver should return more than one resolved path if available URL: https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/9 This is an automated

[jira] [Updated] (SLING-7833) BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

[ https://issues.apache.org/jira/browse/SLING-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7833: --- Summary: BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected

[jira] [Created] (SLING-7833) .BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder

Robert Munteanu created SLING-7833: -- Summary: .BundleContentTest.testBundleContentParentFromMultipleBundles fails: Expected sling.js in the /system folder Key: SLING-7833 URL:

[jira] [Created] (SLING-7832) ResourceResolverProxyTest fails: write(param) is only valid in arrays

Robert Munteanu created SLING-7832: -- Summary: ResourceResolverProxyTest fails: write(param) is only valid in arrays Key: SLING-7832 URL: https://issues.apache.org/jira/browse/SLING-7832 Project:

Re: ResourceProviderTrackerTest#testReactivation fails after updating to osgi-mock 2

Perfect, thanks Carsten and Stefan for looking into this! Robert On Fri, 2018-08-17 at 07:50 +, Stefan Seifert wrote: > ok - i've fixed the unit test accordingly and merged my branch. > > stefan > > > -Original Message- > > From: Carsten Ziegeler [mailto:cziege...@apache.org] > >

RE: ResourceProviderTrackerTest#testReactivation fails after updating to osgi-mock 2

ok - i've fixed the unit test accordingly and merged my branch. stefan >-Original Message- >From: Carsten Ziegeler [mailto:cziege...@apache.org] >Sent: Friday, August 17, 2018 7:42 AM >To: dev@sling.apache.org; Robert Munteanu >Subject: Re: ResourceProviderTrackerTest#testReactivation