Re: [RESULT][VOTE] Release Apache Sling Scripting Sightly 1.0.0
On Mon, Mar 30, 2015 at 2:45 PM, Radu Cotescu r...@apache.org wrote: Hi, The vote has passed with the following result : +1 (binding): Justin Edelson, Robert Munteanu, Bertrand Delacretaz I can handle all the remaining release tasks except for copying the artifacts to the Sling dist directory. Can somebody from the PMC please do this for me? Done. Robert Thanks, Radu
Re: [RESULT] [VOTE] Release Apache Sling XSS Protection Bundle version 1.0.2
On Mon, Mar 30, 2015 at 2:26 PM, Radu Cotescu r...@apache.org wrote: Hi, The vote has passed with the following result : +1 (binding): Stefan Egli, Daniel Klco, Robert Munteanu I can handle all the remaining release tasks except for copying the artifacts to the Sling dist directory. Can somebody from the PMC please do this for me? Done, Robert Thanks, Radu
Sling Content Distribution bugfix release
Hi all, since Marius found and fixed an important bug [1] right after the cut of the 0.1.0 Sling Content Distribution release I'd like to create an RC just for sling.distribution.core 0.1.1 and start the vote shortly. Thanks and regards, Tommaso [1] : https://issues.apache.org/jira/browse/SLING-4550
Re: Documentation for the Sling Resource Editor
Hi Sandro, On Mon, Mar 30, 2015 at 10:40 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Or if it's better to use the Confluence wiki. Can somebody tell me how to get write access if I should use the latter?... Let us know your user ID there and we can hopefully give you access. -Bertrand (who started to hate Confluence the day it stopped being a wiki)
Re: Sling Content Distribution bugfix release
p.s. could anyone having administration permission on Sling Jira (maybe Carsten?) create a Content Distribution Core 0.1.1 version to correctly set the fixversion for SLING-4550? Thanks and regards, Tommaso 2015-03-31 10:34 GMT+02:00 Tommaso Teofili tommaso.teof...@gmail.com: Hi all, since Marius found and fixed an important bug [1] right after the cut of the 0.1.0 Sling Content Distribution release I'd like to create an RC just for sling.distribution.core 0.1.1 and start the vote shortly. Thanks and regards, Tommaso [1] : https://issues.apache.org/jira/browse/SLING-4550
[VOTE] Release Apache Sling Event 3.6.0
Hi, We solved 4 issues for this release https://issues.apache.org/jira/browse/SLING/fixforversion/12329661 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1224/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1224 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Commented] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle
[
https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388400#comment-14388400
]
Amit Gupta commented on SLING-4512:
---
Applied the patch At revision: 1670310
Traversal Warnings in OAK while creating i18n JcrResourceBundle
---
Key: SLING-4512
URL: https://issues.apache.org/jira/browse/SLING-4512
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Srijan Bhatnagar
Assignee: Amit Gupta
Attachments: SLING-4512-alex.patch, SLING-4512.diff
org.apache.sling.i18n.impl.JcrResourceBundle#loadFully uses an XPath query to
load [sling:Message] nodes under given paths. If the subtree under the path
is too big (1000), we receive traversal warnings in Oak. The following
warning is generated if the path is /libs/wcm/core/i18n/de :
{code}
GET /content/geometrixx/de.html HTTP/1.1]
org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 1000
nodes with filter Filter(query=select [jcr:path], [jcr:score], * from
[sling:Message] as a where isdescendantnode(a, '/libs/wcm/core/i18n/de') /*
xpath: /jcr:root/libs/wcm/core/i18n/de//element(*,sling:Message) */,
path=/libs/wcm/core/i18n/de//*); consider creating an index or changing the
query
{code}
A suggestion would be to use
[TreeTraverser|http://jackrabbit.apache.org/api/2.4/org/apache/jackrabbit/commons/flat/TreeTraverser.html]
instead of XPath query since the subtree is mostly a flat list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle
[
https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388392#comment-14388392
]
Amit Gupta commented on SLING-4512:
---
Applying the latest patch from Alex, now. Thanks
Traversal Warnings in OAK while creating i18n JcrResourceBundle
---
Key: SLING-4512
URL: https://issues.apache.org/jira/browse/SLING-4512
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Srijan Bhatnagar
Assignee: Amit Gupta
Attachments: SLING-4512-alex.patch, SLING-4512.diff
org.apache.sling.i18n.impl.JcrResourceBundle#loadFully uses an XPath query to
load [sling:Message] nodes under given paths. If the subtree under the path
is too big (1000), we receive traversal warnings in Oak. The following
warning is generated if the path is /libs/wcm/core/i18n/de :
{code}
GET /content/geometrixx/de.html HTTP/1.1]
org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 1000
nodes with filter Filter(query=select [jcr:path], [jcr:score], * from
[sling:Message] as a where isdescendantnode(a, '/libs/wcm/core/i18n/de') /*
xpath: /jcr:root/libs/wcm/core/i18n/de//element(*,sling:Message) */,
path=/libs/wcm/core/i18n/de//*); consider creating an index or changing the
query
{code}
A suggestion would be to use
[TreeTraverser|http://jackrabbit.apache.org/api/2.4/org/apache/jackrabbit/commons/flat/TreeTraverser.html]
instead of XPath query since the subtree is mostly a flat list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Sling Content Distribution bugfix release
Am 31.03.15 um 11:04 schrieb Tommaso Teofili: p.s. could anyone having administration permission on Sling Jira (maybe Carsten?) create a Content Distribution Core 0.1.1 version to correctly set the fixversion for SLING-4550? I've created content distribution core 0.1.2 Regards Carsten Thanks and regards, Tommaso 2015-03-31 10:34 GMT+02:00 Tommaso Teofili tommaso.teof...@gmail.com: Hi all, since Marius found and fixed an important bug [1] right after the cut of the 0.1.0 Sling Content Distribution release I'd like to create an RC just for sling.distribution.core 0.1.1 and start the vote shortly. Thanks and regards, Tommaso [1] : https://issues.apache.org/jira/browse/SLING-4550 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[VOTE] Release Apache Sling Content Distribution Core version 0.1.1
Hi all, This is the vote for the first Sling Content Distribution Core release 0.1.1. We solved 1 issues there: https://issues.apache.org/jira/browse/SLING/fixforversion/12329868 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1223/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1223 /tmp/sling-staging Please cast your vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks and regards, Tommaso
[jira] [Updated] (SLING-4550) Last distribution package in a pull series is dropped
[ https://issues.apache.org/jira/browse/SLING-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-4550: --- Fix Version/s: (was: Content Distribution 0.2.0) Content Distribution Core 0.1.1 Last distribution package in a pull series is dropped - Key: SLING-4550 URL: https://issues.apache.org/jira/browse/SLING-4550 Project: Sling Issue Type: Bug Affects Versions: Content Distribution 0.1.0 Reporter: Marius Petria Fix For: Content Distribution Core 0.1.1 Configure a reverse agent pulling items from a remote queue agent. Have the reverse agent pull max item, and add 2 items in the queue agent. The second item will be dropped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Sling Content Distribution bugfix release
2015-03-31 11:14 GMT+02:00 Carsten Ziegeler cziege...@apache.org: Am 31.03.15 um 11:13 schrieb Carsten Ziegeler: Am 31.03.15 um 11:04 schrieb Tommaso Teofili: p.s. could anyone having administration permission on Sling Jira (maybe Carsten?) create a Content Distribution Core 0.1.1 version to correctly set the fixversion for SLING-4550? I've created content distribution core 0.1.2 and renamed it to 0.1.1 :) Usually we use even numbers for releases, but as you already started the release we can go with 0.1.1 sorry for that, I'll keep it in mind for the next time. Thanks, Tommaso Carsten Regards Carsten Thanks and regards, Tommaso 2015-03-31 10:34 GMT+02:00 Tommaso Teofili tommaso.teof...@gmail.com: Hi all, since Marius found and fixed an important bug [1] right after the cut of the 0.1.0 Sling Content Distribution release I'd like to create an RC just for sling.distribution.core 0.1.1 and start the vote shortly. Thanks and regards, Tommaso [1] : https://issues.apache.org/jira/browse/SLING-4550 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Documentation for the Sling Resource Editor
Hi Bertrand and Robert, thanks for your quick answers! I will use the website now for documentation. And thanks for configuring the access Bertrand! Best, Sandro Am 31.03.15 um 10:56 schrieb Bertrand Delacretaz: Hi Sandro, On Mon, Mar 30, 2015 at 10:40 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Or if it's better to use the Confluence wiki. Can somebody tell me how to get write access if I should use the latter?... Let us know your user ID there and we can hopefully give you access. -Bertrand (who started to hate Confluence the day it stopped being a wiki)
[jira] [Updated] (SLING-4550) Last distribution package in a pull series is dropped
[ https://issues.apache.org/jira/browse/SLING-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-4550: - Component/s: Distribution Last distribution package in a pull series is dropped - Key: SLING-4550 URL: https://issues.apache.org/jira/browse/SLING-4550 Project: Sling Issue Type: Bug Components: Distribution Affects Versions: Content Distribution 0.1.0 Reporter: Marius Petria Fix For: Content Distribution Core 0.1.1 Configure a reverse agent pulling items from a remote queue agent. Have the reverse agent pull max item, and add 2 items in the queue agent. The second item will be dropped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.1
+1 (non binding) Tommaso 2015-03-31 11:28 GMT+02:00 Tommaso Teofili tommaso.teof...@gmail.com: Hi all, This is the vote for the first Sling Content Distribution Core release 0.1.1. We solved 1 issues there: https://issues.apache.org/jira/browse/SLING/fixforversion/12329868 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1223/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1223 /tmp/sling-staging Please cast your vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks and regards, Tommaso
Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.1
+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Build failed in Jenkins: sling-trunk-1.6 #3234
See https://builds.apache.org/job/sling-trunk-1.6/3234/changes Changes: [tommaso] [maven-release-plugin] prepare for next development iteration [tommaso] [maven-release-plugin] prepare release org.apache.sling.distribution.core-0.1.1 -- [...truncated 236 lines...] [INFO] Apache Sling System Bundle Extension: WS APIs . SKIPPED [INFO] Apache Sling Dynamic Class Loader Support . SKIPPED [INFO] Apache Sling Commons Java Compiler SKIPPED [INFO] Apache Sling JSON Library . SKIPPED [INFO] Apache Sling SLF4J Implementation (Logback) ... SKIPPED [INFO] Apache Sling OSGi LogService Implementation ... SKIPPED [INFO] Apache Sling MIME type mapping support SKIPPED [INFO] Apache Sling Commons OSGi support . SKIPPED [INFO] Apache Sling Scheduler Support SKIPPED [INFO] Apache Sling Testing Utilities SKIPPED [INFO] Apache Sling Thread Dumper SKIPPED [INFO] Apache Sling Thread Support ... SKIPPED [INFO] Apache Sling Authentication Service ... SKIPPED [INFO] Apache Sling Form Based Authentication Handler SKIPPED [INFO] Apache Sling Engine Implementation SKIPPED [INFO] Apache Sling Repository API Bundle SKIPPED [INFO] Apache Sling Testing JCR Mock . SKIPPED [INFO] Apache Sling JCR Base Bundle .. SKIPPED [INFO] Apache Sling JCR ClassLoader .. SKIPPED [INFO] Apache Sling Initial Content Loader ... SKIPPED [INFO] Apache Sling Jackrabbit Embedded Repository ... SKIPPED [INFO] Apache Sling Jackrabbit UserManager Support ... SKIPPED [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SKIPPED [INFO] Apache Sling Wrapper Bundle for the JCR API ... SKIPPED [INFO] Apache Sling JCR Resource Resolver SKIPPED [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SKIPPED [INFO] Apache Sling Versioning Integration Tests . SKIPPED [INFO] Apache Sling JCR Repository Registration .. SKIPPED [INFO] Apache Sling Simple WebDAV Access to repositories . SKIPPED [INFO] Apache Sling DavEx Access to repositories . SKIPPED [INFO] Apache Sling JCR WebConsole Bundle SKIPPED [INFO] Apache Sling Oak Repository Server SKIPPED [INFO] Apache Sling SlingRepository Integration Tests SKIPPED [INFO] Apache Sling Servlet Resolver . SKIPPED [INFO] Apache Sling Default GET Servlets . SKIPPED [INFO] Apache Sling Default POST Servlets SKIPPED [INFO] Apache Sling Compat Servlets .. SKIPPED [INFO] Apache Sling Scripting Implementation API . SKIPPED [INFO] Apache Sling Scripting Core implementation SKIPPED [INFO] Apache Sling Scripting JavaScript Support . SKIPPED [INFO] Apache Sling Scripting JSP Support SKIPPED [INFO] Apache Sling JSP Tag Library .. SKIPPED [INFO] Apache Sling JSP Standard Tag Library . SKIPPED [INFO] Apache Sling Adapter Manager Implementation ... SKIPPED [INFO] Apache Sling Bundle Resource Provider . SKIPPED [INFO] Apache Sling Distributed Event Admin .. SKIPPED [INFO] Apache Sling Discovery API SKIPPED [INFO] Apache Sling Resource-Based Discovery Service . SKIPPED [INFO] Apache Sling Discovery Support Bundle . SKIPPED [INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED [INFO] Apache Sling Event Support SKIPPED [INFO] Apache Sling Feature Flags SKIPPED [INFO] Apache Sling Filesystem Resource Provider . SKIPPED [INFO] Apache Sling javax.activation bundle .. SKIPPED [INFO] Apache Sling Service User Mapper .. SKIPPED [INFO] Apache Sling Settings . SKIPPED [INFO] Apache Sling Web Console Branding . SKIPPED [INFO] Apache Sling Web Console Security Provider SKIPPED [INFO] Apache Sling Explorer . SKIPPED [INFO] Apache Sling Health Check Core SKIPPED [INFO] Apache Sling Health Check Annotations . SKIPPED [INFO] Apache Sling Health Check Samples . SKIPPED [INFO] Apache Sling Health Check Support Components .. SKIPPED [INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED [INFO] Apache Sling Health Check JUnit Bridge SKIPPED [INFO] Apache Sling Health Check Integration Tests ... SKIPPED [INFO] Apache Sling Health Check Reactor POM . SKIPPED [INFO] Apache Sling Resource Access Security . SKIPPED [INFO] Apache Sling Resource Access Security Integration Tests SKIPPED [INFO] Apache Sling Models API
Build failed in Jenkins: sling-contrib-1.6 #1719
See https://builds.apache.org/job/sling-contrib-1.6/1719/changes Changes: [tommaso] [maven-release-plugin] prepare for next development iteration [tommaso] [maven-release-plugin] prepare release org.apache.sling.distribution.core-0.1.1 -- [...truncated 11993 lines...] Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/project/4.1.1/project-4.1.1.pom (17 KB at 481.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1/httpclient-4.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1/httpclient-4.1.pom (6 KB at 178.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1/httpcomponents-client-4.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1/httpcomponents-client-4.1.pom (12 KB at 333.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/commons-codec/commons-codec/1.4/commons-codec-1.4.pom Downloaded: http://repo.maven.apache.org/maven2/commons-codec/commons-codec/1.4/commons-codec-1.4.pom (11 KB at 310.5 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1/httpmime-4.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1/httpmime-4.1.pom (6 KB at 149.8 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.json/2.0.6/org.apache.sling.commons.json-2.0.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.json/2.0.6/org.apache.sling.commons.json-2.0.6.pom (4 KB at 95.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/sling/10/sling-10.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/sling/10/sling-10.pom (26 KB at 737.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.discovery.impl/1.0.12/org.apache.sling.discovery.impl-1.0.12.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.discovery.impl/1.0.12/org.apache.sling.discovery.impl-1.0.12.pom (10 KB at 194.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/org.apache.jackrabbit.vault/3.1.0/org.apache.jackrabbit.vault-3.1.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/org.apache.jackrabbit.vault/3.1.0/org.apache.jackrabbit.vault-3.1.0.pom (10 KB at 194.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/parent/3.1.0/parent-3.1.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/parent/3.1.0/parent-3.1.0.pom (14 KB at 361.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.3.1/httpcore-osgi-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.3.1/httpcore-osgi-4.3.1.pom (4 KB at 60.5 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.3.1/httpcomponents-core-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.3.1/httpcomponents-core-4.3.1.pom (12 KB at 359.7 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.3.1/httpcore-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.3.1/httpcore-4.3.1.pom (5 KB at 136.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.3.1/httpcore-nio-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.3.1/httpcore-nio-4.3.1.pom (5 KB at 141.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.3.2/httpclient-osgi-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.3.2/httpclient-osgi-4.3.2.pom (8 KB at 234.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.3.2/httpcomponents-client-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.3.2/httpcomponents-client-4.3.2.pom (16 KB at 456.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.3.2/httpclient-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.3.2/httpclient-4.3.2.pom (6 KB at 154.3 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.3.2/httpmime-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.3.2/httpmime-4.3.2.pom (5 KB at 141.7 KB/sec) Downloading:
Build failed in Jenkins: sling-trunk-1.6 #3235
See https://builds.apache.org/job/sling-trunk-1.6/3235/changes Changes: [cziegeler] [maven-release-plugin] prepare for next development iteration [cziegeler] [maven-release-plugin] prepare release org.apache.sling.event-3.6.0 -- [...truncated 442 lines...] [INFO] Apache Sling JSON Library . SKIPPED [INFO] Apache Sling SLF4J Implementation (Logback) ... SKIPPED [INFO] Apache Sling OSGi LogService Implementation ... SKIPPED [INFO] Apache Sling MIME type mapping support SKIPPED [INFO] Apache Sling Commons OSGi support . SKIPPED [INFO] Apache Sling Scheduler Support SKIPPED [INFO] Apache Sling Testing Utilities SKIPPED [INFO] Apache Sling Thread Dumper SKIPPED [INFO] Apache Sling Thread Support ... SKIPPED [INFO] Apache Sling Authentication Service ... SKIPPED [INFO] Apache Sling Form Based Authentication Handler SKIPPED [INFO] Apache Sling Engine Implementation SKIPPED [INFO] Apache Sling Repository API Bundle SKIPPED [INFO] Apache Sling Testing JCR Mock . SKIPPED [INFO] Apache Sling JCR Base Bundle .. SKIPPED [INFO] Apache Sling JCR ClassLoader .. SKIPPED [INFO] Apache Sling Initial Content Loader ... SKIPPED [INFO] Apache Sling Jackrabbit Embedded Repository ... SKIPPED [INFO] Apache Sling Jackrabbit UserManager Support ... SKIPPED [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SKIPPED [INFO] Apache Sling Wrapper Bundle for the JCR API ... SKIPPED [INFO] Apache Sling JCR Resource Resolver SKIPPED [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SKIPPED [INFO] Apache Sling Versioning Integration Tests . SKIPPED [INFO] Apache Sling JCR Repository Registration .. SKIPPED [INFO] Apache Sling Simple WebDAV Access to repositories . SKIPPED [INFO] Apache Sling DavEx Access to repositories . SKIPPED [INFO] Apache Sling JCR WebConsole Bundle SKIPPED [INFO] Apache Sling Oak Repository Server SKIPPED [INFO] Apache Sling SlingRepository Integration Tests SKIPPED [INFO] Apache Sling Servlet Resolver . SKIPPED [INFO] Apache Sling Default GET Servlets . SKIPPED [INFO] Apache Sling Default POST Servlets SKIPPED [INFO] Apache Sling Compat Servlets .. SKIPPED [INFO] Apache Sling Scripting Implementation API . SKIPPED [INFO] Apache Sling Scripting Core implementation SKIPPED [INFO] Apache Sling Scripting JavaScript Support . SKIPPED [INFO] Apache Sling Scripting JSP Support SKIPPED [INFO] Apache Sling JSP Tag Library .. SKIPPED [INFO] Apache Sling JSP Standard Tag Library . SKIPPED [INFO] Apache Sling Adapter Manager Implementation ... SKIPPED [INFO] Apache Sling Bundle Resource Provider . SKIPPED [INFO] Apache Sling Distributed Event Admin .. SKIPPED [INFO] Apache Sling Discovery API SKIPPED [INFO] Apache Sling Resource-Based Discovery Service . SKIPPED [INFO] Apache Sling Discovery Support Bundle . SKIPPED [INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED [INFO] Apache Sling Event Support SKIPPED [INFO] Apache Sling Feature Flags SKIPPED [INFO] Apache Sling Filesystem Resource Provider . SKIPPED [INFO] Apache Sling javax.activation bundle .. SKIPPED [INFO] Apache Sling Service User Mapper .. SKIPPED [INFO] Apache Sling Settings . SKIPPED [INFO] Apache Sling Web Console Branding . SKIPPED [INFO] Apache Sling Web Console Security Provider SKIPPED [INFO] Apache Sling Explorer . SKIPPED [INFO] Apache Sling Health Check Core SKIPPED [INFO] Apache Sling Health Check Annotations . SKIPPED [INFO] Apache Sling Health Check Samples . SKIPPED [INFO] Apache Sling Health Check Support Components .. SKIPPED [INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED [INFO] Apache Sling Health Check JUnit Bridge SKIPPED [INFO] Apache Sling Health Check Integration Tests ... SKIPPED [INFO] Apache Sling Health Check Reactor POM . SKIPPED [INFO] Apache Sling Resource Access Security . SKIPPED [INFO] Apache Sling Resource Access Security Integration Tests SKIPPED [INFO] Apache Sling Models API ... SKIPPED [INFO] Apache Sling Models Implementation SKIPPED [INFO] Apache Sling Test Tools ... SKIPPED [INFO] Apache Sling Models Integration
Re: Sling Content Distribution bugfix release
Am 31.03.15 um 11:13 schrieb Carsten Ziegeler: Am 31.03.15 um 11:04 schrieb Tommaso Teofili: p.s. could anyone having administration permission on Sling Jira (maybe Carsten?) create a Content Distribution Core 0.1.1 version to correctly set the fixversion for SLING-4550? I've created content distribution core 0.1.2 and renamed it to 0.1.1 :) Usually we use even numbers for releases, but as you already started the release we can go with 0.1.1 Carsten Regards Carsten Thanks and regards, Tommaso 2015-03-31 10:34 GMT+02:00 Tommaso Teofili tommaso.teof...@gmail.com: Hi all, since Marius found and fixed an important bug [1] right after the cut of the 0.1.0 Sling Content Distribution release I'd like to create an RC just for sling.distribution.core 0.1.1 and start the vote shortly. Thanks and regards, Tommaso [1] : https://issues.apache.org/jira/browse/SLING-4550 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (SLING-4545) Add pull items configuration option to distribution sync agents
[ https://issues.apache.org/jira/browse/SLING-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-4545: - Fix Version/s: (was: Content Distribution 0.2.0) Content Distribution Core 0.1.1 Add pull items configuration option to distribution sync agents --- Key: SLING-4545 URL: https://issues.apache.org/jira/browse/SLING-4545 Project: Sling Issue Type: Improvement Components: Distribution Reporter: Marius Petria Assignee: Marius Petria Fix For: Content Distribution Core 0.1.1 Sync distribution agents pull one item at a time. This should be configurable as in the case of reverse agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: sling-trunk-1.6 #3237
See https://builds.apache.org/job/sling-trunk-1.6/3237/changes Changes: [tommaso] make distr.it work with latest snapshot -- [...truncated 796 lines...] [INFO] Apache Sling JSON Library . SKIPPED [INFO] Apache Sling SLF4J Implementation (Logback) ... SKIPPED [INFO] Apache Sling OSGi LogService Implementation ... SKIPPED [INFO] Apache Sling MIME type mapping support SKIPPED [INFO] Apache Sling Commons OSGi support . SKIPPED [INFO] Apache Sling Scheduler Support SKIPPED [INFO] Apache Sling Testing Utilities SKIPPED [INFO] Apache Sling Thread Dumper SKIPPED [INFO] Apache Sling Thread Support ... SKIPPED [INFO] Apache Sling Authentication Service ... SKIPPED [INFO] Apache Sling Form Based Authentication Handler SKIPPED [INFO] Apache Sling Engine Implementation SKIPPED [INFO] Apache Sling Repository API Bundle SKIPPED [INFO] Apache Sling Testing JCR Mock . SKIPPED [INFO] Apache Sling JCR Base Bundle .. SKIPPED [INFO] Apache Sling JCR ClassLoader .. SKIPPED [INFO] Apache Sling Initial Content Loader ... SKIPPED [INFO] Apache Sling Jackrabbit Embedded Repository ... SKIPPED [INFO] Apache Sling Jackrabbit UserManager Support ... SKIPPED [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SKIPPED [INFO] Apache Sling Wrapper Bundle for the JCR API ... SKIPPED [INFO] Apache Sling JCR Resource Resolver SKIPPED [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SKIPPED [INFO] Apache Sling Versioning Integration Tests . SKIPPED [INFO] Apache Sling JCR Repository Registration .. SKIPPED [INFO] Apache Sling Simple WebDAV Access to repositories . SKIPPED [INFO] Apache Sling DavEx Access to repositories . SKIPPED [INFO] Apache Sling JCR WebConsole Bundle SKIPPED [INFO] Apache Sling Oak Repository Server SKIPPED [INFO] Apache Sling SlingRepository Integration Tests SKIPPED [INFO] Apache Sling Servlet Resolver . SKIPPED [INFO] Apache Sling Default GET Servlets . SKIPPED [INFO] Apache Sling Default POST Servlets SKIPPED [INFO] Apache Sling Compat Servlets .. SKIPPED [INFO] Apache Sling Scripting Implementation API . SKIPPED [INFO] Apache Sling Scripting Core implementation SKIPPED [INFO] Apache Sling Scripting JavaScript Support . SKIPPED [INFO] Apache Sling Scripting JSP Support SKIPPED [INFO] Apache Sling JSP Tag Library .. SKIPPED [INFO] Apache Sling JSP Standard Tag Library . SKIPPED [INFO] Apache Sling Adapter Manager Implementation ... SKIPPED [INFO] Apache Sling Bundle Resource Provider . SKIPPED [INFO] Apache Sling Distributed Event Admin .. SKIPPED [INFO] Apache Sling Discovery API SKIPPED [INFO] Apache Sling Resource-Based Discovery Service . SKIPPED [INFO] Apache Sling Discovery Support Bundle . SKIPPED [INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED [INFO] Apache Sling Event Support SKIPPED [INFO] Apache Sling Feature Flags SKIPPED [INFO] Apache Sling Filesystem Resource Provider . SKIPPED [INFO] Apache Sling javax.activation bundle .. SKIPPED [INFO] Apache Sling Service User Mapper .. SKIPPED [INFO] Apache Sling Settings . SKIPPED [INFO] Apache Sling Web Console Branding . SKIPPED [INFO] Apache Sling Web Console Security Provider SKIPPED [INFO] Apache Sling Explorer . SKIPPED [INFO] Apache Sling Health Check Core SKIPPED [INFO] Apache Sling Health Check Annotations . SKIPPED [INFO] Apache Sling Health Check Samples . SKIPPED [INFO] Apache Sling Health Check Support Components .. SKIPPED [INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED [INFO] Apache Sling Health Check JUnit Bridge SKIPPED [INFO] Apache Sling Health Check Integration Tests ... SKIPPED [INFO] Apache Sling Health Check Reactor POM . SKIPPED [INFO] Apache Sling Resource Access Security . SKIPPED [INFO] Apache Sling Resource Access Security Integration Tests SKIPPED [INFO] Apache Sling Models API ... SKIPPED [INFO] Apache Sling Models Implementation SKIPPED [INFO] Apache Sling Test Tools ... SKIPPED [INFO] Apache Sling Models Integration Tests . SKIPPED [INFO] Apache Sling JUnit Core ... SKIPPED [INFO]
Re: [VOTE] Release Apache Sling Event 3.6.0
+1 Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Build failed in Jenkins: sling-trunk-1.6 #3236
See https://builds.apache.org/job/sling-trunk-1.6/3236/changes Changes: [amitgupt] SLING-4512 - Traversal Warnings in OAK while creating i18n JcrResourceBundle -- [...truncated 15273 lines...] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [4.487s] [INFO] Apache Sling MIME type mapping support SUCCESS [6.891s] [INFO] Apache Sling Commons OSGi support . SUCCESS [9.812s] [INFO] Apache Sling Scheduler Support SUCCESS [5.728s] [INFO] Apache Sling Testing Utilities SUCCESS [14.082s] [INFO] Apache Sling Thread Dumper SUCCESS [4.858s] [INFO] Apache Sling Thread Support ... SUCCESS [5.753s] [INFO] Apache Sling Authentication Service ... SUCCESS [6.575s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [8.306s] [INFO] Apache Sling Engine Implementation SUCCESS [23.601s] [INFO] Apache Sling Repository API Bundle SUCCESS [4.389s] [INFO] Apache Sling Testing JCR Mock . SUCCESS [4.845s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [4.673s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [3.434s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [5.091s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [18.467s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [10.847s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [4.340s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [3.802s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [41.841s] [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SUCCESS [14.888s] [INFO] Apache Sling Versioning Integration Tests . SUCCESS [10.856s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [6.761s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [5.416s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [4.561s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [3.967s] [INFO] Apache Sling Oak Repository Server SUCCESS [5.604s] [INFO] Apache Sling SlingRepository Integration Tests FAILURE [28.378s] [INFO] Apache Sling Servlet Resolver . SKIPPED [INFO] Apache Sling Default GET Servlets . SKIPPED [INFO] Apache Sling Default POST Servlets SKIPPED [INFO] Apache Sling Compat Servlets .. SKIPPED [INFO] Apache Sling Scripting Implementation API . SKIPPED [INFO] Apache Sling Scripting Core implementation SKIPPED [INFO] Apache Sling Scripting JavaScript Support . SKIPPED [INFO] Apache Sling Scripting JSP Support SKIPPED [INFO] Apache Sling JSP Tag Library .. SKIPPED [INFO] Apache Sling JSP Standard Tag Library . SKIPPED [INFO] Apache Sling Adapter Manager Implementation ... SKIPPED [INFO] Apache Sling Bundle Resource Provider . SKIPPED [INFO] Apache Sling Distributed Event Admin .. SKIPPED [INFO] Apache Sling Discovery API SKIPPED [INFO] Apache Sling Resource-Based Discovery Service . SKIPPED [INFO] Apache Sling Discovery Support Bundle . SKIPPED [INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED [INFO] Apache Sling Event Support SKIPPED [INFO] Apache Sling Feature Flags SKIPPED [INFO] Apache Sling Filesystem Resource Provider . SKIPPED [INFO] Apache Sling javax.activation bundle .. SKIPPED [INFO] Apache Sling Service User Mapper .. SKIPPED [INFO] Apache Sling Settings . SKIPPED [INFO] Apache Sling Web Console Branding . SKIPPED [INFO] Apache Sling Web Console Security Provider SKIPPED [INFO] Apache Sling Explorer . SKIPPED [INFO] Apache Sling Health Check Core SKIPPED [INFO] Apache Sling Health Check Annotations . SKIPPED [INFO] Apache Sling Health Check Samples . SKIPPED [INFO] Apache Sling Health Check Support Components .. SKIPPED [INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED [INFO] Apache Sling Health Check JUnit Bridge SKIPPED [INFO] Apache Sling Health Check Integration Tests ... SKIPPED [INFO] Apache Sling Health Check Reactor POM . SKIPPED [INFO] Apache Sling Resource Access Security . SKIPPED [INFO] Apache Sling Resource Access Security Integration Tests SKIPPED [INFO] Apache Sling Models API ... SKIPPED [INFO] Apache Sling Models Implementation SKIPPED [INFO] Apache Sling Test Tools
[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4558:
-
Attachment: SLING-4558.patch
Attached a simple change of the jcr installer's ConfigNodeConverter:
[^SLING-4558.patch]
If a {{sling:OsgiConfig}} node has the name {{serviceuser}}, then the special
case kicks in. The properties ({{user.mapping}} in particular) stay the same,
and the unique factory alias is automatically taken from the first mapping's
bundle name.
Example JCR structure:
{noformat}
/libs/project/config
+ serviceuser [sling:OsgiConfig]
- user.mapping = [org.example.app.app-bundle:myservice=myservice-user']
{noformat}
Note this only supports sling:OsgiConfig style, not the property files, but
that shouldn't be necessary given one always only configures the user.mapping
which doesn't have number values.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending -something, which confuses
people to whether that something must correspond to a bundle or service
name or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple serviceuser config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4558:
-
Description:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple {{serviceuser}} config node name would be better.
For reference, the target service is
[MappingConfigAmendment|https://github.com/apache/sling/blob/trunk/bundles/extensions/serviceusermapper/src/main/java/org/apache/sling/serviceusermapping/impl/MappingConfigAmendment.java]
was:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple {{serviceuser}} config node name would be better.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which
confuses people as to whether that something must correspond to a bundle or
service name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple {{serviceuser}} config node name would be better.
For reference, the target service is
[MappingConfigAmendment|https://github.com/apache/sling/blob/trunk/bundles/extensions/serviceusermapper/src/main/java/org/apache/sling/serviceusermapping/impl/MappingConfigAmendment.java]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4558) Simpler serviceuser config for service user mappings
Alexander Klimetschek created SLING-4558:
Summary: Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending -something, which confuses
people to whether that something must correspond to a bundle or service name
or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple serviceuser config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389843#comment-14389843
]
Alexander Klimetschek commented on SLING-4558:
--
One could go even further and turn the user.mapping into a jcr property
key/value mapping (using a space instead of : as delimiter between the bundle
and service name):
{noformat}
/libs/project/config
+ serviceuser [sling:OsgiConfig]
- org.example.app.app-bundle myservice = myservice-user
{noformat}
And maybe generalize this ... have an SPI for mapping such special
sling:OsgiConfig nodes based on their node name (if it does not contain a .).
Then this impl could actually reside in the service user mapping code base.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending -something, which confuses
people to whether that something must correspond to a bundle or service
name or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple serviceuser config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389835#comment-14389835
]
Alexander Klimetschek edited comment on SLING-4558 at 4/1/15 1:33 AM:
--
Attached a simple change of the jcr installer's ConfigNodeConverter:
[^SLING-4558.patch]
If a {{sling:OsgiConfig}} node has the name {{serviceuser}}, then the special
case kicks in. The properties ({{user.mapping}} in particular) stay the same,
and the unique factory alias is automatically taken from the first mapping's
bundle name.
Example JCR structure:
{noformat}
/libs/project/config
+ serviceuser [sling:OsgiConfig]
- user.mapping = [org.example.app.app-bundle:myservice=myservice-user]
{noformat}
Note this only supports sling:OsgiConfig style, not the property files, but
that shouldn't be necessary given one always only configures the user.mapping
which doesn't have number values.
was (Author: alexander.klimetschek):
Attached a simple change of the jcr installer's ConfigNodeConverter:
[^SLING-4558.patch]
If a {{sling:OsgiConfig}} node has the name {{serviceuser}}, then the special
case kicks in. The properties ({{user.mapping}} in particular) stay the same,
and the unique factory alias is automatically taken from the first mapping's
bundle name.
Example JCR structure:
{noformat}
/libs/project/config
+ serviceuser [sling:OsgiConfig]
- user.mapping = [org.example.app.app-bundle:myservice=myservice-user']
{noformat}
Note this only supports sling:OsgiConfig style, not the property files, but
that shouldn't be necessary given one always only configures the user.mapping
which doesn't have number values.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending -something, which confuses
people to whether that something must correspond to a bundle or service
name or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple serviceuser config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4558:
-
Description:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple serviceuser config node name would be better.
was:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending -something, which confuses
people to whether that something must correspond to a bundle or service name
or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple serviceuser config node name would be better.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which
confuses people as to whether that something must correspond to a bundle or
service name or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple serviceuser config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4558:
-
Description:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple serviceuser config node name would be better.
was:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple serviceuser config node name would be better.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which
confuses people as to whether that something must correspond to a bundle or
service name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple serviceuser config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings
[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4558:
-
Description:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple {{serviceuser}} config node name would be better.
was:
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which confuses
people as to whether that something must correspond to a bundle or service
name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows or
jcr repository limitations).
A simple serviceuser config node name would be better.
Simpler serviceuser config for service user mappings
Key: SLING-4558
URL: https://issues.apache.org/jira/browse/SLING-4558
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Alexander Klimetschek
Attachments: SLING-4558.patch
For a service user configuration (amendment), one has to currently remember a
weird long PID:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
plus making sure it has a unique ID by appending {{-something}}, which
confuses people as to whether that something must correspond to a bundle or
service name (not necessary) or they come up with these long names:
{{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
which then create too long paths for some cases (git checkouts under windows
or jcr repository limitations).
A simple {{serviceuser}} config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4557) Add JSON and XML validation to the XSS Protection API
[ https://issues.apache.org/jira/browse/SLING-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388572#comment-14388572 ] ASF GitHub Bot commented on SLING-4557: --- GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/81 SLING-4557 - Add JSON and XML validation to the XSS Protection API - Added validator methods to the API - Added JSON validation implementation using Apache Commons JSON - Added XML validation implementation using SAX - Added unit tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4557_json_xml_validation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/81.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #81 commit 3f910b2f90d5705d53cde31cc264c4c098c91eea Author: vladbailescu baile...@adobe.com Date: 2015-03-31T14:16:19Z SLING-4557 - Add JSON and XML validation to the XSS Protection API - Added validator methods to the API - Added JSON validation implementation using Apache Commons JSON - Added XML validation implementation using SAX - Added unit tests Add JSON and XML validation to the XSS Protection API - Key: SLING-4557 URL: https://issues.apache.org/jira/browse/SLING-4557 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: XSS Protection API 1.0.2 Reporter: Vlad Bailescu Priority: Minor Fix For: XSS Protection API 1.0.4 Add methods for JSON and XML validation in the XSS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] sling pull request: SLING-4557 - Add JSON and XML validation to th...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/81 SLING-4557 - Add JSON and XML validation to the XSS Protection API - Added validator methods to the API - Added JSON validation implementation using Apache Commons JSON - Added XML validation implementation using SAX - Added unit tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4557_json_xml_validation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/81.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #81 commit 3f910b2f90d5705d53cde31cc264c4c098c91eea Author: vladbailescu baile...@adobe.com Date: 2015-03-31T14:16:19Z SLING-4557 - Add JSON and XML validation to the XSS Protection API - Added validator methods to the API - Added JSON validation implementation using Apache Commons JSON - Added XML validation implementation using SAX - Added unit tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.1
+1 Robert On Tue, 2015-03-31 at 11:28 +0200, Tommaso Teofili wrote: Hi all, This is the vote for the first Sling Content Distribution Core release 0.1.1. We solved 1 issues there: https://issues.apache.org/jira/browse/SLING/fixforversion/12329868 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1223/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1223 /tmp/sling-staging Please cast your vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks and regards, Tommaso
[jira] [Created] (SLING-4557) Add JSON and XML validation to the XSS Protection API
Vlad Bailescu created SLING-4557: Summary: Add JSON and XML validation to the XSS Protection API Key: SLING-4557 URL: https://issues.apache.org/jira/browse/SLING-4557 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: XSS Protection API 1.0.2 Reporter: Vlad Bailescu Priority: Minor Fix For: XSS Protection API 1.0.4 Add methods for JSON and XML validation in the XSS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4174) introduction of data-sly-repeat
[
https://issues.apache.org/jira/browse/SLING-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-4174.
-
Resolution: Duplicate
Fix Version/s: Scripting Sightly Engine 1.0.0
introduction of data-sly-repeat
---
Key: SLING-4174
URL: https://issues.apache.org/jira/browse/SLING-4174
Project: Sling
Issue Type: New Feature
Components: Scripting
Reporter: Feike Visser
Fix For: Scripting Sightly Engine 1.0.0
I want to propose a new operation in Sightly: data-sly-repeat.
This to overcome situations where you want to loop through items, but where
you don't have a container element in your markup.
This is possible with data-sly-list and data-sly-unwrap, but that forces you
to add markup.
{code}
div data-sly-list=${resource.listChildren} data-sly-unwrap
div${child.path}/div
/div
{code}
With data-sly-repeat you would be able to write it like this:
{code}
div data-sly-repeat=${resource.listChildren}${child.path}/div
{code}
Moved spec-discussion to :
https://github.com/Adobe-Marketing-Cloud/sightly-spec/issues/4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3829) Add support for Content-Disposition attachment
[ https://issues.apache.org/jira/browse/SLING-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388688#comment-14388688 ] Carsten Ziegeler commented on SLING-3829: - [~asanso] I think the method setContentType(String type) can be improved. Right now, it's always going through all paths and all prefixes. The method can return as soon as it's calling setContentDisposition for one of the cases. There is no need to further check the other cases Add support for Content-Disposition attachment --- Key: SLING-3829 URL: https://issues.apache.org/jira/browse/SLING-3829 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Antonio Sanso Assignee: Antonio Sanso Priority: Minor Attachments: ContentDispositionFilter.java, SLING-3829-patch.txt In some situation will be useful (and safer) to force Content-Disposition attachment for some Content-Type (configurable ) under some specific (and sensitive) path (configurable) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4557) Add JSON and XML validation to the XSS Protection API
[ https://issues.apache.org/jira/browse/SLING-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388579#comment-14388579 ] Vlad Bailescu commented on SLING-4557: -- [~radu.cotescu] can you please check the submitted PR? Thank you! Add JSON and XML validation to the XSS Protection API - Key: SLING-4557 URL: https://issues.apache.org/jira/browse/SLING-4557 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: XSS Protection API 1.0.2 Reporter: Vlad Bailescu Priority: Minor Fix For: XSS Protection API 1.0.4 Add methods for JSON and XML validation in the XSS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4556) NPE in DiscoveryServiceImpl#activate
[
https://issues.apache.org/jira/browse/SLING-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388578#comment-14388578
]
Robert Munteanu commented on SLING-4556:
I've also seen this at startup ( with sling.run.modes=oak mostly I think )
{noformat}31.03.2015 17:06:06.216 *ERROR* [Thread-45] ERROR: Error calling
StartupListener
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler@6eed788d
(java.lang.NullPointerException)
java.lang.NullPointerException
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1123)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:611)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554)
at
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528)
at
org.apache.sling.discovery.impl.common.resource.ResourceHelper.getOrCreateResource(ResourceHelper.java:45)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.issueClusterLocalHeartbeat(HeartbeatHandler.java:285)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.issueHeartbeat(HeartbeatHandler.java:255)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.startupFinished(HeartbeatHandler.java:139)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.inform(HeartbeatHandler.java:132)
at
org.apache.sling.launchpad.base.impl.DefaultStartupHandler$1.addingService(DefaultStartupHandler.java:135)
at
org.apache.sling.launchpad.base.impl.DefaultStartupHandler$1.addingService(DefaultStartupHandler.java:118)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
at
org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:987)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4547)
at org.apache.felix.framework.Felix.registerService(Felix.java:3521)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:1003)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:992)
at
org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:134)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:1044)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:841)
at
org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:931)
at
org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:895)
at
Re: [VOTE] Release Apache Sling Event 3.6.0
+1 Robert On Tue, 2015-03-31 at 13:19 +0200, Carsten Ziegeler wrote: Hi, We solved 4 issues for this release https://issues.apache.org/jira/browse/SLING/fixforversion/12329661 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1224/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1224 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten
Re: Documentation for the Sling Resource Editor
Hi, I understand now how to change a page with the CMS. But can someone please tell me how to create a new one? I would like to add a link to a new page at 'http://sling.apache.org/documentation/bundles.html'. The idea is to have a link named Sling Resource Editor frontend under Content Presentation that links to the new page. Do I have to create a 'https://svn.apache.org/repos/asf/sling/site/trunk/content/documentation/bundles/resource-editor.mdtext' file in SVN and commit it there first? Best, Sandro Am 30.03.15 um 23:07 schrieb Robert Munteanu: Hi Sandro, On Mon, Mar 30, 2015 at 11:40 PM, Sandro Boehme sandro.boe...@gmx.de wrote: Hi, I would like to create online documentation for the Sling Resource Editor to get more users/contributors/committers for it. Now I wonder if it's practical (and allowed for me) to add the docu at the public Sling website even though the decommissioning of the CMS is proposed. Yes, please add the docs to the Sling website. If we end up migrating to a different system, we'll migrate everything anyway. Cheers, Robert Or if it's better to use the Confluence wiki. Can somebody tell me how to get write access if I should use the latter? Best, Sandro
Re: Documentation for the Sling Resource Editor
Hi, On Tue, Mar 31, 2015 at 5:24 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Do I have to create a 'https://svn.apache.org/repos/asf/sling/site/trunk/content/documentation/bundles/resource-editor.mdtext' file in SVN and commit it there first?... I usually do it like this, but you could also use cms.apache.org, IIRC it's edit directory there. -Bertrand
Re: [VOTE] Release Apache Sling Event 3.6.0
+1 On Tue, Mar 31, 2015 at 7:19 AM Carsten Ziegeler cziege...@apache.org wrote: Hi, We solved 4 issues for this release https://issues.apache.org/jira/browse/SLING/fixforversion/12329661 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1224/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1224 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Assigned] (SLING-4557) Add JSON and XML validation to the XSS Protection API
[ https://issues.apache.org/jira/browse/SLING-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-4557: --- Assignee: Radu Cotescu Add JSON and XML validation to the XSS Protection API - Key: SLING-4557 URL: https://issues.apache.org/jira/browse/SLING-4557 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: XSS Protection API 1.0.2 Reporter: Vlad Bailescu Assignee: Radu Cotescu Priority: Minor Fix For: XSS Protection API 1.0.4 Add methods for JSON and XML validation in the XSS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3829) Add support for Content-Disposition attachment
[
https://issues.apache.org/jira/browse/SLING-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389109#comment-14389109
]
Alexander Klimetschek commented on SLING-3829:
--
You should use a [Trie|http://en.wikipedia.org/wiki/Trie] data structure for
that, commons-collections 4.0 has one:
* interface
[Trie|http://commons.apache.org/proper/commons-collections/javadocs/api-release/org/apache/commons/collections4/Trie.html]
and implementation
[PatriciaTrie|http://commons.apache.org/proper/commons-collections/javadocs/api-release/org/apache/commons/collections4/trie/PatriciaTrie.html]
* (I think these should be embedded and inlined in the sling bundle, usually
only commons 3.x is available as bundle in Sling environments).
* example: https://code.google.com/p/patricia-trie/wiki/Examples
* see also
http://stackoverflow.com/questions/5595780/space-efficient-collection-for-strings-with-common-prefixes-java-implementatio
The {{contentDispositionPaths.contains(pathInfo)}} check only happens rarely,
since the root paths that would be configured ({{/content/usergenerated}},
{{/content/dam}}) would rarely be requested directly. The startsWith checks
become costly the more configurations are present.
Add support for Content-Disposition attachment
---
Key: SLING-3829
URL: https://issues.apache.org/jira/browse/SLING-3829
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Priority: Minor
Attachments: ContentDispositionFilter.java, SLING-3829-patch.txt
In some situation will be useful (and safer) to force Content-Disposition
attachment for some Content-Type (configurable ) under some specific (and
sensitive) path (configurable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Documentation for the Sling Resource Editor
Yeah, it worked well! It's browsing the directory, then Edit this directory and then an input field that has to be submitted via the 'Return' key as there is no submit button. The initial version is now online. Are there any statistics about such pages? Best, Sandro Am 31.03.15 um 18:10 schrieb Bertrand Delacretaz: Hi, On Tue, Mar 31, 2015 at 5:24 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Do I have to create a 'https://svn.apache.org/repos/asf/sling/site/trunk/content/documentation/bundles/resource-editor.mdtext' file in SVN and commit it there first?... I usually do it like this, but you could also use cms.apache.org, IIRC it's edit directory there. -Bertrand
[jira] [Assigned] (SLING-4525) XSS protection path mangling issue
[ https://issues.apache.org/jira/browse/SLING-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-4525: --- Assignee: Radu Cotescu XSS protection path mangling issue -- Key: SLING-4525 URL: https://issues.apache.org/jira/browse/SLING-4525 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Georg Koester Assignee: Radu Cotescu Priority: Minor Fix For: XSS Protection API 1.0.4 Attachments: 0001-Add-testcases-for-getValidHref-showing-problem-in-co.patch Last part in path gets prepended with an underscore if there is a colon in the query string. Test appended, to be applied on https://github.com/apache/sling/tree/196dea678c6010 Test output: Failed tests: XSSAPIImplTest.testGetValidHref:267 Requested '/content/items/searchpages.html?0_tag:id=geo' expected:/content/items/[searchpages.html?0_tag%3a]id=geo but was:/content/items/[_searchpages.html?0_tag_]id=geo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4525) XSS protection path mangling issue
[ https://issues.apache.org/jira/browse/SLING-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4525: Fix Version/s: XSS Protection API 1.0.4 XSS protection path mangling issue -- Key: SLING-4525 URL: https://issues.apache.org/jira/browse/SLING-4525 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Georg Koester Priority: Minor Fix For: XSS Protection API 1.0.4 Attachments: 0001-Add-testcases-for-getValidHref-showing-problem-in-co.patch Last part in path gets prepended with an underscore if there is a colon in the query string. Test appended, to be applied on https://github.com/apache/sling/tree/196dea678c6010 Test output: Failed tests: XSSAPIImplTest.testGetValidHref:267 Requested '/content/items/searchpages.html?0_tag:id=geo' expected:/content/items/[searchpages.html?0_tag%3a]id=geo but was:/content/items/[_searchpages.html?0_tag_]id=geo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4148) Put JCR dependent components into a distribution.jcr bundle
[ https://issues.apache.org/jira/browse/SLING-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-4148: Fix Version/s: (was: Content Distribution 0.1.0) Content Distribution Core 0.1.1 Put JCR dependent components into a distribution.jcr bundle --- Key: SLING-4148 URL: https://issues.apache.org/jira/browse/SLING-4148 Project: Sling Issue Type: Task Components: Distribution Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: Content Distribution Core 0.1.1 Some components (triggers, serialization, etc.) in _org.apache.sling.distribution.core_ are JCR dependent, meaning that they will only work if Sling is backed by JCR, so they should be put in a separate _org.apache.sling.distribution.jcr_ bundle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4556) NPE in DiscoveryServiceImpl#activate
Carsten Ziegeler created SLING-4556: --- Summary: NPE in DiscoveryServiceImpl#activate Key: SLING-4556 URL: https://issues.apache.org/jira/browse/SLING-4556 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.1.0 Reporter: Carsten Ziegeler 31.03.2015 05:33:44.001 *ERROR* [Thread-77] org.apache.sling.discovery.impl [org.apache.sling.discovery.impl.DiscoveryServiceImpl(85)] The activate method has thrown an exception (java.lang.NullPointerException) java.lang.NullPointerException: null at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1123) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:611) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:599) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:554) at org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:528) at org.apache.sling.discovery.impl.common.resource.ResourceHelper.getOrCreateResource(ResourceHelper.java:45) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listAnnouncementsInSameCluster(AnnouncementRegistryImpl.java:150) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listInstances(AnnouncementRegistryImpl.java:542) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.getTopology(DiscoveryServiceImpl.java:443) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.activate(DiscoveryServiceImpl.java:149) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE RESULTS] Accept the donation of the Hypermedia API Tools via SLING-4513
Vote passed with 5 +1s. Thank you for the interest. I'll follow up with a PMC chair. Thanks, Andrei
Jenkins build became unstable: sling-trunk-1.7 #1632
See https://builds.apache.org/job/sling-trunk-1.7/1632/changes
Jenkins build is back to normal : sling-trunk-1.6 #3238
See https://builds.apache.org/job/sling-trunk-1.6/3238/changes
Jenkins build became unstable: sling-trunk-1.8 #922
See https://builds.apache.org/job/sling-trunk-1.8/922/changes
