Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #499
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/499/
Jenkins build became unstable: sling-trunk-1.8 #499
See https://builds.apache.org/job/sling-trunk-1.8/499/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #1209
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1209/
Jenkins build is still unstable: sling-trunk-1.7 #1209
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build is still unstable: sling-trunk-1.6 #2828
See https://builds.apache.org/job/sling-trunk-1.6/changes
[RESULT] [VOTE] Release Apache Sling Authentication Service 1.3.4
Hi, The vote has passed with the following result : +1 (binding): Robert Munteanu, Antonio Sanso, Oliver Lietz I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #500
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/500/
Jenkins build is still unstable: sling-trunk-1.8 #500
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #1210
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1210/
Jenkins build is still unstable: sling-trunk-1.7 #1210
See https://builds.apache.org/job/sling-trunk-1.7/changes
[jira] [Closed] (SLING-4203) Remove the configurable option for auth.newpassword.parameter
[ https://issues.apache.org/jira/browse/SLING-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso closed SLING-4203. Remove the configurable option for auth.newpassword.parameter - Key: SLING-4203 URL: https://issues.apache.org/jira/browse/SLING-4203 Project: Sling Issue Type: Improvement Components: Authentication Reporter: Antonio Sanso Assignee: Antonio Sanso Fix For: Auth Core 1.3.4 The SlingAuthenticator introduced in SLING-3991 the option to Support Password Change. At the moment is possible to configure the name of the auth.newpassword.parameter . It is not clear how this value can be consumed by the html form. For this reason is better to follow the convention used so far for usernma/password and use the standard like name of j_newpassword -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4207) Add notifications upon tenant changes
[ https://issues.apache.org/jira/browse/SLING-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231443#comment-14231443 ] Timothee Maret commented on SLING-4207: --- Attaching a new patch, taking into account [~fmeschbe] suggestions on the list and pre-patch. Add notifications upon tenant changes - Key: SLING-4207 URL: https://issues.apache.org/jira/browse/SLING-4207 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Tenant 1.0.2 Reporter: Timothee Maret Assignee: Felix Meschberger Fix For: Tenant 1.0.4 Attachments: SLING-4207.patch, SLING-4207.patch, SLING-4207.patch Currently, there is no clean way to detect when a tenant has been added/removed/modified. We may detect when a change is required by implementing the TenantCustomizer interface, however, it tells nothing about the actual completion of the change. We may listen for OSGI events under /etc/tenants but this requires the user to know where the tenants are located (which afaik, currently is not exposed). In order to allow apps reacting on tenant changes, I propose to either: I. extend the current SPI with an interface TenantEventListener that users can implement ; or II. send OSGI events form the current implementation. In both cases, the events should cover * Tenant added * Tenant removed * Property added * Property removed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4207) Add notifications upon tenant changes
[ https://issues.apache.org/jira/browse/SLING-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-4207: -- Attachment: SLING-4207.patch Add notifications upon tenant changes - Key: SLING-4207 URL: https://issues.apache.org/jira/browse/SLING-4207 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Tenant 1.0.2 Reporter: Timothee Maret Assignee: Felix Meschberger Fix For: Tenant 1.0.4 Attachments: SLING-4207.patch, SLING-4207.patch, SLING-4207.patch Currently, there is no clean way to detect when a tenant has been added/removed/modified. We may detect when a change is required by implementing the TenantCustomizer interface, however, it tells nothing about the actual completion of the change. We may listen for OSGI events under /etc/tenants but this requires the user to know where the tenants are located (which afaik, currently is not exposed). In order to allow apps reacting on tenant changes, I propose to either: I. extend the current SPI with an interface TenantEventListener that users can implement ; or II. send OSGI events form the current implementation. In both cases, the events should cover * Tenant added * Tenant removed * Property added * Property removed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Allow the resource-path injector to inject multiple paths
Hello, I was looking at the different injectors and noticed that the resource-path does not support multiple values. I've had different requirements at certain points when this would be very useful. I guess other people probably would find it useful. I've created https://issues.apache.org/jira/browse/SLING-4212 to deal with this. Could you give me your opinion? right now the patch only supports multiple values for injection of resources through the valuemap since I didn't want to change the API. Could this change be accepted? if not, what can I change to make it better? Greetings. -- *Santiago García Pimentel* | Software Engineer Netcentric Ibérica SL Av. Diagonal 123 -8ª 08005 Barcelona España Skype: santiago.garciapimentel santiago.pimen...@netcentric.biz | www.netcentric.es
[jira] [Commented] (SLING-4212) Sling Models: Allow multiple values from ValueMap in the resource-path injector
[ https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14232082#comment-14232082 ] Stefan Seifert commented on SLING-4212: --- i had only a brief look at the patch - it seems you (or your IDE) reformatted a lot of lines, so its difficult to tell what has changed, and what is only reformatted (esp. in ResourcePathInjector.java). can you reproduce the patch and make sure only the lines really changed are included? Sling Models: Allow multiple values from ValueMap in the resource-path injector --- Key: SLING-4212 URL: https://issues.apache.org/jira/browse/SLING-4212 Project: Sling Issue Type: Improvement Components: Extensions Reporter: santiago garcía pimentel The current implementation of the resource-path injector does not support multiple values. I think it could be useful to inject a list of paths from the valuemap. I have created a small patch to allow this. Right now it only allows them from the value map since I didn't want to change the API without consulting you first. I you agree I can do this change as well. I also added a test case for it. You can see a pull request in https://github.com/apache/sling/pull/51 If there anything I can do to improve this patch, please let me know. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
