[jira] [Comment Edited] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

[ https://issues.apache.org/jira/browse/SLING-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728501#comment-15728501 ] Julian Sedding edited comment on SLING-6357 at 12/7/16 11:1

[jira] [Commented] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

[ https://issues.apache.org/jira/browse/SLING-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728501#comment-15728501 ] Julian Sedding commented on SLING-6357: --- Fixed in [r1773046|https://svn.apache

Re: Automatic cleanup of lingering ResourceResolver's

Hi Konrad The only way I can imagine this to be implemented is by fully(!) wrapping the JCR API and maintain a reference to originating ResourceResolver in each object (e.g. Session, Node etc). IMHO this is not worthwhile, as it opens a large can of worms. Imagine you want to cast Session to Jack

Re: LoginAdminWhitelist - do we need amendment support like we have for service users?

Hi all I have created SLING-6357 to track this enhancement. I'll quote my proposed solution from the issue description. Feel free to comment/agree/disagree etc. """ I propose to remove the {{whitelist.bundles.default}} and {{whitelist.bundles.additional}} properties and replace them by "additiona

[jira] [Updated] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

[ https://issues.apache.org/jira/browse/SLING-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6357: -- Fix Version/s: JCR Base 3.0.0 > Allow to extend LoginAdminWhitelist with multi

[jira] [Created] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

Julian Sedding created SLING-6357: - Summary: Allow to extend LoginAdminWhitelist with multiple configurations Key: SLING-6357 URL: https://issues.apache.org/jira/browse/SLING-6357 Project: Sling

Re: LoginAdminWhitelist - do we need amendment support like we have for service users?

ustin Edelson wrote: > Sorry, I missed that mail. Thanks for clearing that up. > > On Tue, Nov 29, 2016 at 1:24 PM Julian Sedding wrote: > >> Hi Justin >> >> I asked the same question before[0] and Carsten seemed to be opposed. >> >> However, after using

Re: LoginAdminWhitelist - do we need amendment support like we have for service users?

Hi Justin I asked the same question before[0] and Carsten seemed to be opposed. However, after using it a little, I believe it would much better to have amendments (or factory configs). This allows for better re-use and modularisation. With modularisation in this case I mean Sling, products built

[jira] [Commented] (SLING-6336) Implement a ResourceResolverWrapper

[ https://issues.apache.org/jira/browse/SLING-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706083#comment-15706083 ] Julian Sedding commented on SLING-6336: --- Thanks! And sorry for the mid

Re: integration test fail due to LoginAdminWhitelist

. Ultimately I agree with Bertrand though. We need to understand the root cause. Regards Julian [0] https://builds.apache.org/job/sling-contrib-extensions-contextaware-config-integration-tests-1.8/214 On Tue, Nov 29, 2016 at 10:25 AM, Julian Sedding wrote: > I mostly agree with Bertrand's interp

Re: integration test fail due to LoginAdminWhitelist

I mostly agree with Bertrand's interpretation. However, I a config can be applied early (i.e. registered with config admin), but components are still lazily instantiated. Does anyone know if there is a guarantee that components are configured (activated) before they become visible? If there is no

Re: What to do about cancelled releases in Jira?

+1 Regards Julian On Monday, November 28, 2016, Stefan Seifert wrote: > >My suggestion would be to: > > > >- move all issues from version N to version N+2 > >- delete Jira version N > > +1 >

Re: svn commit: r1771782 - /sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolverWrapper.java

Hi Radu I would argue that this implementation is incorrect. Consider that with this implementation resolver != resolver.getResource("/foo").getResourceResolver(), which should be the case IMHO. I commented on the issue with two tickets, where the same feature was previously discussed. The ticke

[jira] [Commented] (SLING-6336) Implement a ResourceResolverWrapper

[ https://issues.apache.org/jira/browse/SLING-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702643#comment-15702643 ] Julian Sedding commented on SLING-6336: --- Please note th

Re: integration test fail due to LoginAdminWhitelist

Hi Stefan When analyzing the issue I noticed that the test was waiting for the ResourceResolverFactory service to become available. However, it is possible that the test starts before even all bundles in the repository are active (SLING-6334[0]). Thus, especially on slow systems, the likelihood of

[jira] [Resolved] (SLING-6335) Server-Side Tests: Use ServiceTracker to wait for services rather than polling

[ https://issues.apache.org/jira/browse/SLING-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6335. --- Resolution: Fixed Fix Version/s: JUnit Core 1.0.20 Fixed in [r1771777|https

[jira] [Resolved] (SLING-6334) Server-Side Tests: Wait until all bundles are started before running tests

[ https://issues.apache.org/jira/browse/SLING-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6334. --- Resolution: Fixed Fix Version/s: JUnit Core 1.0.20 Fixed in [r1771776|https

[jira] [Created] (SLING-6335) Server-Side Tests: Use ServiceTracker to wait for services rather than polling

Julian Sedding created SLING-6335: - Summary: Server-Side Tests: Use ServiceTracker to wait for services rather than polling Key: SLING-6335 URL: https://issues.apache.org/jira/browse/SLING-6335

[jira] [Created] (SLING-6334) Server-Side Tests: Wait until all bundles are started before running tests

Julian Sedding created SLING-6334: - Summary: Server-Side Tests: Wait until all bundles are started before running tests Key: SLING-6334 URL: https://issues.apache.org/jira/browse/SLING-6334 Project

Re: integration test fail due to LoginAdminWhitelist

Sorry, forget the last bit about tests passing. I fooled my self when I only built the "package" phase. The tests also don't pass with regexp=junit. Regards Julian On Mon, Nov 28, 2016 at 12:36 PM, Julian Sedding wrote: > Hi Stefan > > I just had a look and noticed

Re: integration test fail due to LoginAdminWhitelist

Hi Stefan I just had a look and noticed the following: Your current configuration looks like this: whitelist.bundles.regexp="^org\.apache\.sling\.junit(\..*)?$" Inside target/slingstart.txt this becomes: whitelist.bundles.regexp="^org.apache.sling.junit(..*)?$" Note: all slashes have disappeare

Re: How to handle minor version updates in API for provider bundles?

27;t think the added method is >>>> generally useful for an API user, because the search-paths are >>>> normally not available. So I could imagine creating a ResourceTypeUtil >>>> class in the resourceresolver project to hold these new methods. We >>>&g

Re: How to handle minor version updates in API for provider bundles?

Sling API and the utility could start out in a private package until we identify other places where we would need it. WDYT? Regards Julian On Fri, Nov 25, 2016 at 6:51 PM, Julian Sedding wrote: > I think the core problem is that we have provider-type classes and > consumer-type class

[jira] [Commented] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696401#comment-15696401 ] Julian Sedding commented on SLING-6329: --- Fixed in [r1771346|https://svn.apache

[jira] [Resolved] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6329. --- Resolution: Fixed Fix Version/s: Resource Resolver 1.5.6 > RR.isResourceType() bro

Re: How to handle minor version updates in API for provider bundles?

I think the core problem is that we have provider-type classes and consumer-type classes mixed in packages of sling.api. Maybe we should start thinking about how to improve the situation there? For now, I think what we normally do is update everything to snapshots that needs it and then start rele

[jira] [Commented] (SLING-5228) Remove loginAdministrative() usage from org.apache.sling.installer.provider.jcr

[ https://issues.apache.org/jira/browse/SLING-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695701#comment-15695701 ] Julian Sedding commented on SLING-5228: --- [~rombert] Thanks, that's fine wi

[jira] [Updated] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6329: -- Attachment: SLING-6329-jsedding.patch Proposed patch. Still working on a test case

[jira] [Created] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

Julian Sedding created SLING-6329: - Summary: RR.isResourceType() broken with jcr.resource 2.8.2 Key: SLING-6329 URL: https://issues.apache.org/jira/browse/SLING-6329 Project: Sling Issue

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should consider resource resolver's search path

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695418#comment-15695418 ] Julian Sedding commented on SLING-6327: --- TL;DR: I think always stripping off

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should consider resource resolver's search path

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693783#comment-15693783 ] Julian Sedding commented on SLING-6327: --- Based on our discussion on the mai

[jira] [Commented] (SLING-5228) Remove loginAdministrative() usage from org.apache.sling.installer.provider.jcr

[ https://issues.apache.org/jira/browse/SLING-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693595#comment-15693595 ] Julian Sedding commented on SLING-5228: --- Not entirely sure. I was under

Re: ResourceResolver.isResourceType() and relative resource types

I undertstand "resource-type" to be a concept that is essentially represented by the relative path (i.e. without search path prefixes). The fact that we allow absolute paths as resource type is probably mostly historical (there may be some edge use-cases like enforcing the use of an otherwise overl

[jira] [Comment Edited] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692743#comment-15692743 ] Julian Sedding edited comment on SLING-6285 at 11/24/16 1:0

[jira] [Comment Edited] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693226#comment-15693226 ] Julian Sedding edited comment on SLING-6285 at 11/24/16 12:5

[jira] [Commented] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693226#comment-15693226 ] Julian Sedding commented on SLING-6285: --- Thanks Betrand! > Im

[jira] [Commented] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693190#comment-15693190 ] Julian Sedding commented on SLING-6285: --- [~bdelacretaz] I have improved the com

[jira] [Commented] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692880#comment-15692880 ] Julian Sedding commented on SLING-6285: --- bq. If we do that the only wa

[jira] [Commented] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692831#comment-15692831 ] Julian Sedding commented on SLING-6285: --- Oh, my apologies. I misread your prev

[jira] [Commented] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692774#comment-15692774 ] Julian Sedding commented on SLING-6285: --- [~bdelacretaz] thanks for your re

[jira] [Commented] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692743#comment-15692743 ] Julian Sedding commented on SLING-6285: --- [~bdelacretaz], your observation a

[jira] [Commented] (SLING-6313) Sling installer can duplicate factory configurations if an invalid RegisteredResourceList.ser is found

[ https://issues.apache.org/jira/browse/SLING-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687352#comment-15687352 ] Julian Sedding commented on SLING-6313: --- [~rombert] I tested your patch locally

Re: [RESULT] [VOTE] Release Apache Sling JCR Base 2.4.2

Thanks Justin! Regards Julian On Tue, Nov 22, 2016 at 2:54 PM, Justin Edelson wrote: > I'll take care of this. > > On Tue, Nov 22, 2016 at 5:28 AM Julian Sedding wrote: > >> Ping. >> >> Can a PMC member please copy the release to Sling dist? Thanks! >>

[jira] [Commented] (SLING-6305) LoginAdminWhitelist configuration is applied too late

[ https://issues.apache.org/jira/browse/SLING-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686875#comment-15686875 ] Julian Sedding commented on SLING-6305: --- [~rombert] yes exactly. I

[jira] [Closed] (SLING-6070) Reduce temporary storage required in JcrResourceListener, call reportChanges earlier

[ https://issues.apache.org/jira/browse/SLING-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-6070. - > Reduce temporary storage required in JcrResourceListener, call reportChanges > e

[jira] [Closed] (SLING-6162) Deprecate PathMapper

[ https://issues.apache.org/jira/browse/SLING-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-6162. - > Deprecate PathMapper > > > Key

[jira] [Closed] (SLING-6104) Improve handling to avoid Oak warning

[ https://issues.apache.org/jira/browse/SLING-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-6104. - > Improve handling to avoid Oak warn

[jira] [Closed] (SLING-6071) JcrModifiableValueMap#remove(key) breaks Map contract

[ https://issues.apache.org/jira/browse/SLING-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-6071. - > JcrModifiableValueMap#remove(key) breaks Map contr

Re: [RESULT] [VOTE] Release Apache Sling JCR Base 2.4.2

Ping. Can a PMC member please copy the release to Sling dist? Thanks! Regards Julian On Mon, Nov 14, 2016 at 12:48 PM, Julian Sedding wrote: > Hi > > The vote has passed with the following result: > > +1 (binding): Stefan Seifert, Carsten Ziegeler, Oliver Lietz > +1 (no

[RESULT][VOTE] Apache Sling JCR Resource version 2.8.2

Hi The vote has passed with the following result: +1 (binding): Carsten Ziegeler, Robert Munteanu, Stefan Seifert +1 (non binding): Julian Sedding Thanks for voting. I will promote the artifacts to the central Maven repository and update the news page. @any PMC member: please copy this

[jira] [Commented] (SLING-6305) LoginAdminWhitelist configuration is applied too late

[ https://issues.apache.org/jira/browse/SLING-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686271#comment-15686271 ] Julian Sedding commented on SLING-6305: --- [~rombert] I have tried to reproduce

[jira] [Commented] (SLING-6313) Sling installer can duplicate factory configurations if an invalid RegisteredResourceList.ser is found

[ https://issues.apache.org/jira/browse/SLING-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686257#comment-15686257 ] Julian Sedding commented on SLING-6313: --- I have never fully analyzed the issue,

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

+1 (only for JCR Resource 2.8.2) Regards Julian On Fri, Nov 18, 2016 at 8:48 PM, Stefan Seifert wrote: > >>We solved 8 issues in the JCR Resource 2.8.2 release: >>https://issues.apache.org/jira/browse/SLING/fixforversion/12336744 > > +1 (only for JCR Resource 2.8.2) > > stefan >

[jira] [Commented] (SLING-6305) LoginAdminWhitelist configuration is applied too late

[ https://issues.apache.org/jira/browse/SLING-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15679215#comment-15679215 ] Julian Sedding commented on SLING-6305: --- [~rombert] Can you share a diff with

Re: Build failed in Jenkins: sling-ide #82

FWIW, I reported https://issues.apache.org/jira/browse/INFRA-12941. Regards Julian On Fri, Nov 18, 2016 at 6:20 PM, Konrad Windszus wrote: > This issue definitely is an infrastructure issue with Maven Central. I opened > https://issues.sonatype.org/browse/MVNCENTRAL-1369 about the wrong > cert

[jira] [Resolved] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6285. --- Resolution: Fixed Fixed by async registration of {{SlingRepository}} service in [r1770390

Re: [VOTE] Release Apache Sling Models Implementation 1.3.2 and Jackson Exporter 1.0.2

+1 (non binding) all checks ok Regards Julian On Fri, Nov 18, 2016 at 9:30 AM, Stefan Seifert wrote: > +1

[jira] [Reopened] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding reopened SLING-6285: --- Reopening, as there is an issue when the {{LoginAdminWhitelist}} is registered late

[jira] [Resolved] (SLING-6299) SCD ClassCastException ServiceRegistration cannot be cast to Comparable

[ https://issues.apache.org/jira/browse/SLING-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6299. --- Resolution: Fixed Fix Version/s: Content Distribution Core 0.1.20 Thanks for the

Re: trunk build does not work // was: mountByFS does not work

Hi Sandro You are right. However, the full build on Jenkins failed too often. Partly due to issues or flaky tests in Sling, partly due to e.g. infrastructure issues. This made the Jenkins builds almost useless, because chances were that it weren't your changes that made the build fail. Therefore

[jira] [Updated] (SLING-6299) SCD ClassCastException ServiceRegistration cannot be cast to Comparable

[ https://issues.apache.org/jira/browse/SLING-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6299: -- Attachment: SLING-6299-jsedding.patch Proposed patch. [~teofili], [~simone.tripodi] could you

[jira] [Created] (SLING-6299) SCD ClassCastException ServiceRegistration cannot be cast to Comparable

Julian Sedding created SLING-6299: - Summary: SCD ClassCastException ServiceRegistration cannot be cast to Comparable Key: SLING-6299 URL: https://issues.apache.org/jira/browse/SLING-6299 Project

Re: Build test failures

Brilliant, thanks a lot! On Wed, Nov 16, 2016 at 3:28 PM, Robert Munteanu wrote: > On Wed, 2016-11-09 at 21:37 +0100, Julian Sedding wrote: >> Hi Robert >> >> Yes absolutely, that sounds great! >> >> Thanks for your prompt replies. > > > Done, see https:

Re: trunk build does not work // was: mountByFS does not work

hme wrote: >> Hi Julian, >> >> thanks for your feedback! >> >> Am 15.11.16 um 10:47 schrieb Julian Sedding: >> > Hi Sandro >> > >> > org/apache/sling/jcr/base/LoginAdminWhitelist looks like your >> > checkout >> > or snapshots

[jira] [Updated] (SLING-5796) Make Oak Lucene optional

[ https://issues.apache.org/jira/browse/SLING-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-5796: -- Fix Version/s: (was: JCR Oak Server 1.1.2) > Make Oak Lucene optio

[jira] [Updated] (SLING-6080) oak-server ITs fail under Java 7

[ https://issues.apache.org/jira/browse/SLING-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6080: -- Fix Version/s: (was: JCR Oak Server 1.1.2) > oak-server ITs fail under Jav

[jira] [Updated] (SLING-6260) oak-server ITs failing with latest org.apache.sling.jcr.repoinit 1.0.3-SNAPSHOT

[ https://issues.apache.org/jira/browse/SLING-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6260: -- Fix Version/s: (was: JCR Oak Server 1.1.2) > oak-server ITs failing with lat

[jira] [Updated] (SLING-6262) oak-server defines two dependencies to org.apache.sling.api

[ https://issues.apache.org/jira/browse/SLING-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6262: -- Fix Version/s: (was: JCR Oak Server 1.1.2) > oak-server defines two dependencies

[jira] [Updated] (SLING-6080) oak-server ITs fail under Java 7

[ https://issues.apache.org/jira/browse/SLING-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6080: -- Fix Version/s: JCR Oak Server 1.1.4 > oak-server ITs fail under Jav

[jira] [Updated] (SLING-5796) Make Oak Lucene optional

[ https://issues.apache.org/jira/browse/SLING-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-5796: -- Fix Version/s: JCR Oak Server 1.1.4 > Make Oak Lucene optio

[jira] [Updated] (SLING-6260) oak-server ITs failing with latest org.apache.sling.jcr.repoinit 1.0.3-SNAPSHOT

[ https://issues.apache.org/jira/browse/SLING-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6260: -- Fix Version/s: JCR Oak Server 1.1.4 > oak-server ITs failing with lat

[jira] [Updated] (SLING-6262) oak-server defines two dependencies to org.apache.sling.api

[ https://issues.apache.org/jira/browse/SLING-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6262: -- Fix Version/s: JCR Oak Server 1.1.4 > oak-server defines two dependencies

[jira] [Resolved] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6285. --- Resolution: Fixed Fix Version/s: JCR Base 3.0.0 JCR Oak Server 1.1.4

[jira] [Updated] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6285: -- Attachment: SLING-6285-jsedding.patch Attached is a patch implementing the proposed solution

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Thanks, I didn't know that. In this case I cancel only the vote for JCR Oak Repository Server 1.1.2. The vote for JCR Resource 2.8.2 is not affected and can continue. Regards Julian On Tue, Nov 15, 2016 at 11:45 AM, Carsten Ziegeler wrote: > Julian Sedding wrote >> Is it

Bump JCR Base bundle major version?

Hi all The JCR Base bundle's package org.apache.sling.jcr.base was recently bumped to 3.x.y. Should the next release of the bundle reflect this? Regards Julian

LoginAdminWhitelist: default bundles vs additional bundles

Hi all The LoginAdminWhitelist has two lists of whitelisted bundles, "default" and "additional". The rational as I understand it was to distinguish between a whitelist that is shipped with a product (default) and a whitelist that a user of the product can administer (additional). This kind of wor

[jira] [Created] (SLING-6285) Implement LoginAdminWhitelist in Jcr Base

Julian Sedding created SLING-6285: - Summary: Implement LoginAdminWhitelist in Jcr Base Key: SLING-6285 URL: https://issues.apache.org/jira/browse/SLING-6285 Project: Sling Issue Type

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Is it possible if to release only part of the staging repository? If so we can continue the vote for JCR Resource. Regards Julian On Tue, Nov 15, 2016 at 11:23 AM, Carsten Ziegeler wrote: > Julian Sedding wrote >> Hi all >> >> I will cancel this vote. In an offline discuss

[jira] [Updated] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6285: -- Summary: Implement LoginAdminWhitelist in JCR Base (was: Implement LoginAdminWhitelist in Jcr

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

who voted already and sorry for the inconvenience. Regards Julian On Mon, Nov 14, 2016 at 5:00 PM, Robert Munteanu wrote: > On Mon, 2016-11-14 at 16:43 +0100, Julian Sedding wrote: >> Please vote to approve this release: > > +1 > > Robert

Re: trunk build does not work // was: mountByFS does not work

Hi Sandro org/apache/sling/jcr/base/LoginAdminWhitelist looks like your checkout or snapshots on your machine are not quite up to date. I removed the method AbstractSlingRepositoryManager.getLoginAdminWhitelist(), so maybe you need to first build a local snapshot of bundles/jcr/base and then try b

Re: Suggestion: use redirectTestOutputToFile for maven-failsafe-plugin

Thanks Robert, that's great! Having a direct correlation between test and stdout would make analysis easier and it would unclutter the build's stdout. Regards Julian On Mon, Nov 14, 2016 at 5:03 PM, Robert Munteanu wrote: > Hi Julian, > > On Mon, 2016-11-14 at 16:19 +0100, J

Re: Build failed in Jenkins: sling-bundles-jcr-oak-server-1.8 #87

This failure is expected, as o.a.s.jcr.oak.server is currently under vote together with o.a.s.jcr.resource 2.8.2. Regards Julian On Mon, Nov 14, 2016 at 4:50 PM, Apache Jenkins Server wrote: > See > > > Changes: > > [js

[VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Hi, We solved 8 issues in the JCR Resource 2.8.2 release: https://issues.apache.org/jira/browse/SLING/fixforversion/12336744 We solved 4 issues in the JCR Oak Repository Server 1.1.2 release: https://issues.apache.org/jira/browse/SLING/fixforversion/12338111 Note: The build of Oak Server 1.1.2 d

[jira] [Updated] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

[ https://issues.apache.org/jira/browse/SLING-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6130: -- Fix Version/s: (was: JCR Oak Server 1.1.2) JCR Oak Server 1.1.4

Suggestion: use redirectTestOutputToFile for maven-failsafe-plugin

Hi all I find using "redirectTestOutputToFile" for the maven-failsafe-plugin makes it easier to see which IT is failing and also helps by providing the logs per IT. What are your opinions on this? Does anyone know if it makes it harder to analyze failures on Jenkins (or can the *-output.txt files

Re: Release of org.apache.sling.testing.paxexam today

Hi Olli Yes, it's the new API that's blocking. I'll follow your suggestion to downgrade and replace with setVersion(). Thanks. Regards Julian On Mon, Nov 14, 2016 at 3:50 PM, Oliver Lietz wrote: > On Monday 14 November 2016 15:02:32 Julian Sedding wrote: >> Hi all >

Release of org.apache.sling.testing.paxexam today

Hi all If no one beats me to it, I will release "org.apache.sling.testing.paxexam" today. It currently blocks the release of "org.apache.sling.jcr.oak.server". Objections anyone? Regards Julian

Re: [VOTE] Release Apache Sling Resource Resolver 1.5.4

+1 (non binding) All checks ok. Regards Julian On Mon, Nov 14, 2016 at 2:04 PM, Carsten Ziegeler wrote: > +1 > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org >

[jira] [Updated] (SLING-5229) Remove getAdministrativeResourceResolver() and loginAdministrative() usage from JCR components

[ https://issues.apache.org/jira/browse/SLING-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-5229: -- Fix Version/s: (was: JCR Base 2.4.2) JCR Base 2.4.4 > Rem

[RESULT] [VOTE] Release Apache Sling JCR Base 2.4.2

Hi The vote has passed with the following result: +1 (binding): Stefan Seifert, Carsten Ziegeler, Oliver Lietz +1 (non binding): Julian Sedding Thanks for voting. I will promote the artifacts to the central Maven repository and update the news page. @any PMC member: please copy this release

Re: [VOTE] Release Apache Sling JCR Base 2.4.2

Fine, thanks for your feedback. +1 (non binding) Regards Julian On Fri, Nov 11, 2016 at 10:43 AM, Oliver Lietz wrote: > On Friday 11 November 2016 09:33:47 Carsten Ziegeler wrote: >> Julian Sedding wrote >> >> > Even though SLING-6263[0] (a blocker for this release)

[jira] [Created] (SLING-6273) Document SLING-5135 - whitelist of legit login admin uses

Julian Sedding created SLING-6273: - Summary: Document SLING-5135 - whitelist of legit login admin uses Key: SLING-6273 URL: https://issues.apache.org/jira/browse/SLING-6273 Project: Sling

Re: svn commit: r1769187 - /sling/trunk/bundles/jcr/oak-server/src/main/java/org/apache/sling/jcr/oak/server/internal/LoginAdminWhitelist.java

Thanks! Must have missed this one. Regards Julian On Thu, Nov 10, 2016 at 8:16 PM, wrote: > Author: olli > Date: Thu Nov 10 19:16:59 2016 > New Revision: 1769187 > > URL: http://svn.apache.org/viewvc?rev=1769187&view=rev > Log: > cleanup (imports) > > Modified: > > sling/trunk/bundles/jcr/

Re: [VOTE] Release Apache Sling JCR Base 2.4.2

Even though SLING-6263[0] (a blocker for this release) is resolved, there are ongoing discussions. I will wait for the discussion to come to a conclusion and if needed cancel the release. Regards Julian [0] https://issues.apache.org/jira/browse/SLING-6263 On Thu, Nov 10, 2016 at 6:48 PM, Stefan

[VOTE] Release Apache Sling JCR Base 2.4.2

Hi, We solved 3 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12337245/ Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1573/ You can use this UNIX script to download the release and verify the signatures: http://svn.apach

[jira] [Resolved] (SLING-5135) Whitelist legit usages of loginAdministrative and administrative ResourceResolver

[ https://issues.apache.org/jira/browse/SLING-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-5135. --- Resolution: Fixed > Whitelist legit usages of loginAdministrative and administrat

[jira] [Assigned] (SLING-5135) Whitelist legit usages of loginAdministrative and administrative ResourceResolver

[ https://issues.apache.org/jira/browse/SLING-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding reassigned SLING-5135: - Assignee: Julian Sedding (was: Bertrand Delacretaz) > Whitelist legit usages

Re: [VOTE] Release Apache Sling Provisioning Model 1.7.0 and Slingstart Maven Plugin 1.6.0

+1 (not binding) Regards Julian On Thu, Nov 10, 2016 at 2:21 PM, Robert Munteanu wrote: > On Thu, 2016-11-10 at 07:20 +0100, Carsten Ziegeler wrote: >> Please vote to approve this release: > > +1 > > Robert

<    3   4   5   6   7   8   9   10   11   12   >