[jira] [Commented] (SLING-4917) BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
[
https://issues.apache.org/jira/browse/SLING-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646340#comment-14646340
]
Radu Cotescu commented on SLING-4917:
-
[~olli], do you have any idea why the Karaf launchpad module cannot be found?
BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
-
Key: SLING-4917
URL: https://issues.apache.org/jira/browse/SLING-4917
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Radu Cotescu
Fix For: JCR ContentLoader 2.1.12
The mentioned test suite fails with the following errors:
{noformat}
---
Test set: org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
---
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.061 sec
FAILURE! - in org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
initialContentInstalled(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 1.03 sec ERROR!
java.io.IOException: Error resolving artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT: Could
not find artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:354)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:312)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296)
at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131)
at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:508)
at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:170)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:82)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:60)
at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:868)
at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:549)
at
org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:148)
at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:251)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2476)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2436)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:129)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:107)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.installAndStartBundles(NativeTestContainer.java:307)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.start(NativeTestContainer.java:175)
at
org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:79)
at org.ops4j.pax.exam.junit.PaxExam$2.evaluate(PaxExam.java:294)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:111)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
[VOTE] Release Apache Sling XSS Protection API 1.0.4
Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12329844 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12333112 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1305 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 1305 /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. Thanks, Radu
[jira] [Created] (SLING-4917) BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
Radu Cotescu created SLING-4917:
---
Summary: BasicInitialContentIT fails for the
org.apache.sling.jcr.contentloader module
Key: SLING-4917
URL: https://issues.apache.org/jira/browse/SLING-4917
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Radu Cotescu
Fix For: JCR ContentLoader 2.1.12
The mentioned test suite fails with the following errors:
{noformat}
---
Test set: org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
---
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.061 sec
FAILURE! - in org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
initialContentInstalled(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 1.03 sec ERROR!
java.io.IOException: Error resolving artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT: Could not
find artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:354)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:312)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296)
at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131)
at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:508)
at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:170)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:82)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:60)
at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:868)
at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:549)
at
org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:148)
at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:251)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2476)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2436)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:129)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:107)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.installAndStartBundles(NativeTestContainer.java:307)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.start(NativeTestContainer.java:175)
at
org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:79)
at org.ops4j.pax.exam.junit.PaxExam$2.evaluate(PaxExam.java:294)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:111)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
bundleStarted(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 0.005 sec ERROR!
java.lang.Exception: Unable to lock bundle cache:
java.nio.channels.OverlappingFileLockException
at
org.apache.felix.framework.cache.BundleCache.init(BundleCache.java:152)
at org.apache.felix.framework.Felix.init(Felix.java:593)
at
Re: [jira] [Resolved] (SLING-4917) BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
Radu, the issue is fixed, but I really don't like the use of the startup handler from org.apache.sling.launchpad.karaf in contentloader as this will block a release until I finally release it. We should come up with a generic startup handler _finally_ or use a simple dummy in the tests. Regards, O.
[jira] [Resolved] (SLING-4917) BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
[
https://issues.apache.org/jira/browse/SLING-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-4917.
-
Resolution: Fixed
r1693342
BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
-
Key: SLING-4917
URL: https://issues.apache.org/jira/browse/SLING-4917
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Radu Cotescu
Assignee: Oliver Lietz
Fix For: JCR ContentLoader 2.1.12
The mentioned test suite fails with the following errors:
{noformat}
---
Test set: org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
---
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.061 sec
FAILURE! - in org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
initialContentInstalled(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 1.03 sec ERROR!
java.io.IOException: Error resolving artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT: Could
not find artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:354)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:312)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296)
at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131)
at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:508)
at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:170)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:82)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:60)
at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:868)
at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:549)
at
org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:148)
at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:251)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2476)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2436)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:129)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:107)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.installAndStartBundles(NativeTestContainer.java:307)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.start(NativeTestContainer.java:175)
at
org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:79)
at org.ops4j.pax.exam.junit.PaxExam$2.evaluate(PaxExam.java:294)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:111)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
bundleStarted(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 0.005 sec ERROR!
[jira] [Assigned] (SLING-4917) BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
[
https://issues.apache.org/jira/browse/SLING-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz reassigned SLING-4917:
---
Assignee: Oliver Lietz
BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
-
Key: SLING-4917
URL: https://issues.apache.org/jira/browse/SLING-4917
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Radu Cotescu
Assignee: Oliver Lietz
Fix For: JCR ContentLoader 2.1.12
The mentioned test suite fails with the following errors:
{noformat}
---
Test set: org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
---
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.061 sec
FAILURE! - in org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
initialContentInstalled(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 1.03 sec ERROR!
java.io.IOException: Error resolving artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT: Could
not find artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:354)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:312)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296)
at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131)
at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:508)
at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:170)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:82)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:60)
at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:868)
at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:549)
at
org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:148)
at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:251)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2476)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2436)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:129)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:107)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.installAndStartBundles(NativeTestContainer.java:307)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.start(NativeTestContainer.java:175)
at
org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:79)
at org.ops4j.pax.exam.junit.PaxExam$2.evaluate(PaxExam.java:294)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:111)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
bundleStarted(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 0.005 sec ERROR!
[jira] [Updated] (SLING-4918) Frequent failures of AuthenticationResponseCodeTest
[
https://issues.apache.org/jira/browse/SLING-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated SLING-4918:
--
Description:
Lately all test methods of AuthenticationResponseCodeTest often fail on Jenkins
with the following (or similar) message:
{noformat}
expected:401 but was:500
Not able to fetch logs from [http://localhost:41600/system/sling/testlog].
TestLogServer probably not configured
{noformat}
When reproducing this locally, there is a NullPointerException in the logs:
{noformat}
29.07.2015 22:05:56.376 *WARN* [qtp1661403026-43]
org.eclipse.jetty.servlet.ServletHandler /system/sling/testlog
java.lang.NullPointerException: null
at
ch.qos.logback.core.read.CyclicBufferAppender.reset(CyclicBufferAppender.java:66)
at
org.apache.sling.junit.impl.servlet.TestLogServlet.resetAppender(TestLogServlet.java:158)
at
org.apache.sling.junit.impl.servlet.TestLogServlet.doGet(TestLogServlet.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:336)
at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:297)
at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:93)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:50)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:31)
...
{noformat}
was:
Lately all test methods of AuthenticationResponseCodeTest often fail on Jenkins
with the following (or similar) message:
{noformat}
expected:401 but was:500
Not able to fetch logs from [http://localhost:41600/system/sling/testlog].
TestLogServer probably not configured
{noformat}
Frequent failures of AuthenticationResponseCodeTest
Key: SLING-4918
URL: https://issues.apache.org/jira/browse/SLING-4918
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: JUnit Core 1.0.10
Reporter: Julian Sedding
Assignee: Julian Sedding
Lately all test methods of AuthenticationResponseCodeTest often fail on
Jenkins with the following (or similar) message:
{noformat}
expected:401 but was:500
Not able to fetch logs from [http://localhost:41600/system/sling/testlog].
TestLogServer probably not configured
{noformat}
When reproducing this locally, there is a NullPointerException in the logs:
{noformat}
29.07.2015 22:05:56.376 *WARN* [qtp1661403026-43]
org.eclipse.jetty.servlet.ServletHandler /system/sling/testlog
java.lang.NullPointerException: null
at
ch.qos.logback.core.read.CyclicBufferAppender.reset(CyclicBufferAppender.java:66)
at
org.apache.sling.junit.impl.servlet.TestLogServlet.resetAppender(TestLogServlet.java:158)
at
org.apache.sling.junit.impl.servlet.TestLogServlet.doGet(TestLogServlet.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:336)
at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:297)
at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:93)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:50)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:31)
...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4917) BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
[
https://issues.apache.org/jira/browse/SLING-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646499#comment-14646499
]
Oliver Lietz commented on SLING-4917:
-
Exam doesn't know the Apache Snapshots repo, but I remember a bug adding
additional repositories.
And the used Pax Exam and Pax URL versions are really old, we should update.
BasicInitialContentIT fails for the org.apache.sling.jcr.contentloader module
-
Key: SLING-4917
URL: https://issues.apache.org/jira/browse/SLING-4917
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Radu Cotescu
Fix For: JCR ContentLoader 2.1.12
The mentioned test suite fails with the following errors:
{noformat}
---
Test set: org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
---
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.061 sec
FAILURE! - in org.apache.sling.jcr.contentloader.it.BasicInitialContentIT
initialContentInstalled(org.apache.sling.jcr.contentloader.it.BasicInitialContentIT)
Time elapsed: 1.03 sec ERROR!
java.io.IOException: Error resolving artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT: Could
not find artifact
org.apache.sling:org.apache.sling.launchpad.karaf:jar:0.1.1-SNAPSHOT
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:354)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:312)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296)
at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131)
at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:508)
at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:170)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:82)
at
org.apache.felix.framework.cache.JarRevision.init(JarRevision.java:60)
at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:868)
at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:549)
at
org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:148)
at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:251)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2476)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2436)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:129)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:107)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.installAndStartBundles(NativeTestContainer.java:307)
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.start(NativeTestContainer.java:175)
at
org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:79)
at org.ops4j.pax.exam.junit.PaxExam$2.evaluate(PaxExam.java:294)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:111)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
[jira] [Created] (SLING-4918) Frequent failures of AuthenticationResponseCodeTest
Julian Sedding created SLING-4918:
-
Summary: Frequent failures of AuthenticationResponseCodeTest
Key: SLING-4918
URL: https://issues.apache.org/jira/browse/SLING-4918
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: JUnit Core 1.0.10
Reporter: Julian Sedding
Assignee: Julian Sedding
Lately all test methods of AuthenticationResponseCodeTest often fail on Jenkins
with the following (or similar) message:
{noformat}
expected:401 but was:500
Not able to fetch logs from [http://localhost:41600/system/sling/testlog].
TestLogServer probably not configured
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLING-4918) Frequent failures of AuthenticationResponseCodeTest
[
https://issues.apache.org/jira/browse/SLING-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding resolved SLING-4918.
---
Resolution: Fixed
Fix Version/s: JUnit Core 1.0.12
Committed tentative fix in [r1693340|https://svn.apache.org/r1693340] that
improves synchronization on the {{CyclicBufferAppender}} used inside
{{TestLogServlet}}.
Frequent failures of AuthenticationResponseCodeTest
Key: SLING-4918
URL: https://issues.apache.org/jira/browse/SLING-4918
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: JUnit Core 1.0.10
Reporter: Julian Sedding
Assignee: Julian Sedding
Fix For: JUnit Core 1.0.12
Lately all test methods of AuthenticationResponseCodeTest often fail on
Jenkins with the following (or similar) message:
{noformat}
expected:401 but was:500
Not able to fetch logs from [http://localhost:41600/system/sling/testlog].
TestLogServer probably not configured
{noformat}
When reproducing this locally, there is a NullPointerException in the logs:
{noformat}
29.07.2015 22:05:56.376 *WARN* [qtp1661403026-43]
org.eclipse.jetty.servlet.ServletHandler /system/sling/testlog
java.lang.NullPointerException: null
at
ch.qos.logback.core.read.CyclicBufferAppender.reset(CyclicBufferAppender.java:66)
at
org.apache.sling.junit.impl.servlet.TestLogServlet.resetAppender(TestLogServlet.java:158)
at
org.apache.sling.junit.impl.servlet.TestLogServlet.doGet(TestLogServlet.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:336)
at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:297)
at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:93)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:50)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:31)
...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4897) Sling Web Console - Log Tail Plugin
[ https://issues.apache.org/jira/browse/SLING-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Nagpal updated SLING-4897: Attachment: (was: sling-logtail.zip) Sling Web Console - Log Tail Plugin --- Key: SLING-4897 URL: https://issues.apache.org/jira/browse/SLING-4897 Project: Sling Issue Type: New Feature Components: Console Reporter: Varun Nagpal Labels: patch This issue tracks the introduction of a Log Tail Plugin for the Sling Log Web Console under /contrib As the name suggests, the plugin simulates the behaviour of the UNIX shell tail command and follows the server logs outputting on browser allowing for ease of log monitoring in remote systems. The plugin code depends on logback implementations and is sling independent currently. Relevant mail archive thread: http://apache-sling.73963.n3.nabble.com/Sling-Web-Console-Log-Tail-Plugin-td4050756.html External github src link: https://github.com/vnagpal81/sling-logtail -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4897) Sling Web Console - Log Tail Plugin
[ https://issues.apache.org/jira/browse/SLING-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Nagpal updated SLING-4897: Attachment: sling-logtail.zip Sling Web Console - Log Tail Plugin --- Key: SLING-4897 URL: https://issues.apache.org/jira/browse/SLING-4897 Project: Sling Issue Type: New Feature Components: Console Reporter: Varun Nagpal Labels: patch Attachments: sling-logtail.zip This issue tracks the introduction of a Log Tail Plugin for the Sling Log Web Console under /contrib As the name suggests, the plugin simulates the behaviour of the UNIX shell tail command and follows the server logs outputting on browser allowing for ease of log monitoring in remote systems. The plugin code depends on logback implementations and is sling independent currently. Relevant mail archive thread: http://apache-sling.73963.n3.nabble.com/Sling-Web-Console-Log-Tail-Plugin-td4050756.html External github src link: https://github.com/vnagpal81/sling-logtail -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-4897) Sling Web Console - Log Tail Plugin
[
https://issues.apache.org/jira/browse/SLING-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636949#comment-14636949
]
Varun Nagpal edited comment on SLING-4897 at 7/29/15 8:01 AM:
--
Attached zip containing code
{code}
sling-logtail.zip
{code}
with md5sum
{code}
$ md5sum.exe sling-logtail.zip
69576a5b3155684659c1112eb8923274 *sling-logtail.zip
{code}
was (Author: vnagpal):
Attached zip containing code
{code}
sling-logtail.zip
{code}
with md5sum
{code}
$ md5sum.exe sling-logtail.zip
6d14f2ef4748c00e63cbbaeda7224e3c *sling-logtail.zip
{code}
Sling Web Console - Log Tail Plugin
---
Key: SLING-4897
URL: https://issues.apache.org/jira/browse/SLING-4897
Project: Sling
Issue Type: New Feature
Components: Console
Reporter: Varun Nagpal
Labels: patch
Attachments: sling-logtail.zip
This issue tracks the introduction of a Log Tail Plugin for the Sling Log Web
Console under /contrib
As the name suggests, the plugin simulates the behaviour of the UNIX shell
tail command and follows the server logs outputting on browser allowing for
ease of log monitoring in remote systems.
The plugin code depends on logback implementations and is sling independent
currently.
Relevant mail archive thread:
http://apache-sling.73963.n3.nabble.com/Sling-Web-Console-Log-Tail-Plugin-td4050756.html
External github src link:
https://github.com/vnagpal81/sling-logtail
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Compilation error in models.validation-impl ( was: Build failed in Jenkins: sling-trunk-1.8 #1370 )
On Wed, 2015-07-29 at 08:05 +, Apache Jenkins Server wrote: See https://builds.apache.org/job/sling-trunk-1.8/1370/changes Changes: [kwin] SLING-4876 support resource type inheritance for validator models This closes #100 [chetanm] SLING-4914 - LogPanel should pass appender name as request parameter Changed the tailer approach. Now use url ending with tailer.txt and specify appender name as part of 'name' request param (snip) This looks like an actual error :-) and possibly related to SLING-4876. [ERROR] Failed to execute goal org.apache.maven.plugins:mavenorg.apache.sling.models.validation -impl: Compilation failure [ERROR] https://builds.apache.org/job/sling-trunk-1.8/ws/trunk/bundl es/extensions/models/validation -impl/src/main/java/org/apache/sling/models/validation/impl/ModelVali dationImpl.java:[74,57] no suitable method found for getValidationModel(org.apache.sling.api.resource.Resource) [ERROR] method org.apache.sling.validation.ValidationService.getValidationModel(java .lang.String,java.lang.String,boolean) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] method org.apache.sling.validation.ValidationService.getValidationModel(org. apache.sling.api.resource.Resource,boolean) is not applicable [ERROR] (actual and formal argument lists differ in length) Robert
Re: Compilation error in models.validation-impl ( was: Build failed in Jenkins: sling-trunk-1.8 #1370 )
Fixed it already. Sorry for that. On 29 Jul 2015, at 10:13, Robert Munteanu romb...@apache.org wrote: On Wed, 2015-07-29 at 08:05 +, Apache Jenkins Server wrote: See https://builds.apache.org/job/sling-trunk-1.8/1370/changes Changes: [kwin] SLING-4876 support resource type inheritance for validator models This closes #100 [chetanm] SLING-4914 - LogPanel should pass appender name as request parameter Changed the tailer approach. Now use url ending with tailer.txt and specify appender name as part of 'name' request param (snip) This looks like an actual error :-) and possibly related to SLING-4876. [ERROR] Failed to execute goal org.apache.maven.plugins:mavenorg.apache.sling.models.validation -impl: Compilation failure [ERROR] https://builds.apache.org/job/sling-trunk-1.8/ws/trunk/bundl es/extensions/models/validation -impl/src/main/java/org/apache/sling/models/validation/impl/ModelVali dationImpl.java:[74,57] no suitable method found for getValidationModel(org.apache.sling.api.resource.Resource) [ERROR] method org.apache.sling.validation.ValidationService.getValidationModel(java .lang.String,java.lang.String,boolean) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] method org.apache.sling.validation.ValidationService.getValidationModel(org. apache.sling.api.resource.Resource,boolean) is not applicable [ERROR] (actual and formal argument lists differ in length) Robert
[GitHub] sling pull request: SLING-4876 support inheritance for validation ...
Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/100 --- 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. ---
[jira] [Resolved] (SLING-4876) Support resource type inheritance for validator models
[ https://issues.apache.org/jira/browse/SLING-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-4876. Resolution: Fixed Support resource type inheritance for validator models -- Key: SLING-4876 URL: https://issues.apache.org/jira/browse/SLING-4876 Project: Sling Issue Type: Improvement Components: Validation Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Validation 1.0.0 Currently there must be a direct match of the resource type given in the validation model and the resource type of the content resource. But resource type inheritance should also be taken into account, so the validation model of the given resource type and the one for the super resource types should all be taken into account and the results should be merged! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4876) Support resource type inheritance for validator models
[ https://issues.apache.org/jira/browse/SLING-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645617#comment-14645617 ] ASF GitHub Bot commented on SLING-4876: --- Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/100 Support resource type inheritance for validator models -- Key: SLING-4876 URL: https://issues.apache.org/jira/browse/SLING-4876 Project: Sling Issue Type: Improvement Components: Validation Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Validation 1.0.0 Currently there must be a direct match of the resource type given in the validation model and the resource type of the content resource. But resource type inheritance should also be taken into account, so the validation model of the given resource type and the one for the super resource types should all be taken into account and the results should be merged! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [vote] Accept the contribution of Log Tail Plugin tracked in SLING-4897
Hi Robert, Fixed the issues related to AL headers and reattached the zip archive with new md5sum (69576a5b3155684659c1112eb8923274). Please have a look. Thanks. -- Varun On Fri, Jul 24, 2015 at 7:08 PM, Robert Munteanu romb...@apache.org wrote: On Wed, 2015-07-22 at 19:45 +0530, Varun Nagpal wrote: Hi, This thread is about voting for the acceptance of the Log Tail Plugin tracked in SLING-4897. An archive (sling-logtail.zip, md5sum 6d14f2ef4748c00e63cbbaeda7224e3c) containing the contribution is attached to SLING-4897 and otherwise available at [0]. With a rat check some files fail due to missing/unapproved licenses: Unapproved licenses: src/main/java/org/apache/sling/tail/impl/LogTailerWebConsolePlugin.jav a src/main/java/org/apache/sling/tail/LogFilter.java src/main/resources/libs/tail/css/tail.css src/main/resources/libs/tail/js/tail.js pom.xml To reproduce, change the parent pom version from 22 to 24 and run mvn verify This should be fixed before accepting the contribution. Thanks, Robert
[jira] [Resolved] (SLING-4913) Allow exclusion filters on vault package builder
[ https://issues.apache.org/jira/browse/SLING-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-4913. -- Resolution: Fixed Assignee: Marius Petria Allow exclusion filters on vault package builder Key: SLING-4913 URL: https://issues.apache.org/jira/browse/SLING-4913 Project: Sling Issue Type: Improvement Components: Distribution Reporter: Marius Petria Assignee: Marius Petria Fix For: Content Distribution Core 0.1.6 Allow exclusion filters on vault package builder, for example to exclude all .tokens nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [contrib] Contribution to Sling Web Console - Log Tail Plugin
Hi Varun I tried the log tail plugin and it looks quite useful especially for viewing logs on remote servers. I encountered a problem with it though. I see that after a couple of hours or so, it stops following the tail. I see that it does keep sending the ajax requests to the server to get the logs and gets a correct response as well but the tail just stops updating. Not sure if this is related to the log file length or the browser display limitation. Even refreshing the page does not help in fetching the latest logs. On Wed, Jul 22, 2015 at 7:40 PM, Varun Nagpal varun.nag...@gmail.com wrote: Hi All, As referred earlier on [0] I have developed a web console plugin to tail the server side logs on the browser. The motive to develop this was to ease access to logs while debugging issues on remote set ups. Apart from a UI feature set similar to baretail [1], it has the ability to filter log output using complex grammar and extensible filters. Request the dev community to consider it for contribution. Thanks and Regards, Varun Nagpal [0] http://apache-sling.73963.n3.nabble.com/Sling-Web-Console-Log-Tail-Plugin-td4050756.html [1] https://www.baremetalsoft.com/baretail/
[GitHub] sling pull request: SLING-4876 support inheritance for validation ...
GitHub user kwin opened a pull request: https://github.com/apache/sling/pull/100 SLING-4876 support inheritance for validation models You can merge this pull request into a Git repository by running: $ git pull https://github.com/kwin/sling SLING-4876-support-inheritance-for-validation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/100.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 #100 commit b3203ae889c56013ad2f845f8832ad0c4f5dcf1f Author: Konrad Windszus konrad.winds...@netcentric.biz Date: 2015-07-23T14:47:32Z SLING-4876 support resource type inheritance on validation models commit 8aaa907943b7796f022c0aafa617ab3efe7627b6 Author: Konrad Windszus konrad.winds...@netcentric.biz Date: 2015-07-23T16:16:12Z SLING-4876 pass around the resource resolver --- 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. ---
[jira] [Commented] (SLING-4895) Service registry should not be called from within synchronized block
[ https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645682#comment-14645682 ] Carsten Ziegeler commented on SLING-4895: - [~mpetria] Ah right, I'm currently trying to find a different solution which reduces the changes to a minimum Service registry should not be called from within synchronized block Key: SLING-4895 URL: https://issues.apache.org/jira/browse/SLING-4895 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Service User Mapper 1.2.0 Reporter: Carsten Ziegeler Fix For: Service User Mapper 1.2.2 Attachments: SLING-4895.diff RIght now, if e.g. an amendment is added/removed/updated, all registration/unregistration is done in a large synchronized block. This should be avoided -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3821) run launchpad integration tests against Sling on Karaf
[ https://issues.apache.org/jira/browse/SLING-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645719#comment-14645719 ] Oliver Lietz commented on SLING-3821: - Indeed, it's related to SLING-913 (r1690904) where a new dependency on webconsole was pulled in. run launchpad integration tests against Sling on Karaf -- Key: SLING-3821 URL: https://issues.apache.org/jira/browse/SLING-3821 Project: Sling Issue Type: Test Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4913) Allow exclusion filters on vault package builder
[
https://issues.apache.org/jira/browse/SLING-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645764#comment-14645764
]
Marius Petria commented on SLING-4913:
--
Committed revision 1693222.
VaultDistributionPackageBuilderFactory has a package.filters property. A filter
is formed from a root and then a list of includes/excludes. The excludes start
with - and the includes with +.
{noformat}
package.filters: [/content|-.*/excluded]
{noformat}
Allow exclusion filters on vault package builder
Key: SLING-4913
URL: https://issues.apache.org/jira/browse/SLING-4913
Project: Sling
Issue Type: Improvement
Components: Distribution
Reporter: Marius Petria
Fix For: Content Distribution Core 0.1.6
Allow exclusion filters on vault package builder, for example to exclude all
.tokens nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4876) Support resource type inheritance for validator models
[ https://issues.apache.org/jira/browse/SLING-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645619#comment-14645619 ] Konrad Windszus commented on SLING-4876: Applied PR in https://svn.apache.org/r1693191. Support resource type inheritance for validator models -- Key: SLING-4876 URL: https://issues.apache.org/jira/browse/SLING-4876 Project: Sling Issue Type: Improvement Components: Validation Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Validation 1.0.0 Currently there must be a direct match of the resource type given in the validation model and the resource type of the content resource. But resource type inheritance should also be taken into account, so the validation model of the given resource type and the one for the super resource types should all be taken into account and the results should be merged! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4895) Service registry should not be called from within synchronized block
[ https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645651#comment-14645651 ] Marius Petria commented on SLING-4895: -- [~cziegeler] that is exactly the concurrency fix. As updateServiceMappings is no longer synchronized, it can happen that two threads pass the guard an register a service for the same mapping, but in that case one needs to unregister one of the services. Service registry should not be called from within synchronized block Key: SLING-4895 URL: https://issues.apache.org/jira/browse/SLING-4895 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Service User Mapper 1.2.0 Reporter: Carsten Ziegeler Fix For: Service User Mapper 1.2.2 Attachments: SLING-4895.diff RIght now, if e.g. an amendment is added/removed/updated, all registration/unregistration is done in a large synchronized block. This should be avoided -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4895) Service registry should not be called from within synchronized block
[ https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-4895: Attachment: SLING-4895-alt.diff I've attached an alternative patch which uses a use count for mappings. However, this is a more complicated setup compared to the original version. on the other hand, it handles the case where several amendments return a mapping for the same combination - I'm not 100% sure if this is currently correctly handled. But maybe the simpler patch is already enough Service registry should not be called from within synchronized block Key: SLING-4895 URL: https://issues.apache.org/jira/browse/SLING-4895 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Service User Mapper 1.2.0 Reporter: Carsten Ziegeler Fix For: Service User Mapper 1.2.2 Attachments: SLING-4895-alt.diff, SLING-4895.diff RIght now, if e.g. an amendment is added/removed/updated, all registration/unregistration is done in a large synchronized block. This should be avoided -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4876) Support resource type inheritance for validator models
[ https://issues.apache.org/jira/browse/SLING-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645606#comment-14645606 ] ASF GitHub Bot commented on SLING-4876: --- GitHub user kwin opened a pull request: https://github.com/apache/sling/pull/100 SLING-4876 support inheritance for validation models You can merge this pull request into a Git repository by running: $ git pull https://github.com/kwin/sling SLING-4876-support-inheritance-for-validation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/100.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 #100 commit b3203ae889c56013ad2f845f8832ad0c4f5dcf1f Author: Konrad Windszus konrad.winds...@netcentric.biz Date: 2015-07-23T14:47:32Z SLING-4876 support resource type inheritance on validation models commit 8aaa907943b7796f022c0aafa617ab3efe7627b6 Author: Konrad Windszus konrad.winds...@netcentric.biz Date: 2015-07-23T16:16:12Z SLING-4876 pass around the resource resolver Support resource type inheritance for validator models -- Key: SLING-4876 URL: https://issues.apache.org/jira/browse/SLING-4876 Project: Sling Issue Type: Improvement Components: Validation Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Validation 1.0.0 Currently there must be a direct match of the resource type given in the validation model and the resource type of the content resource. But resource type inheritance should also be taken into account, so the validation model of the given resource type and the one for the super resource types should all be taken into account and the results should be merged! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4895) Service registry should not be called from within synchronized block
[
https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645607#comment-14645607
]
Carsten Ziegeler commented on SLING-4895:
-
I'll have a look. I think there is also a bug in the updateServiceMappings
method, it does:
if (!activeMappingRegistrations.containsKey(mapping)) {
...
and later on
final ServiceRegistration oldRegistration =
activeMappingRegistrations.put(mapping, registration);
but this will always return null as the if already checked that there is no
value in the map.
Service registry should not be called from within synchronized block
Key: SLING-4895
URL: https://issues.apache.org/jira/browse/SLING-4895
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Service User Mapper 1.2.0
Reporter: Carsten Ziegeler
Fix For: Service User Mapper 1.2.2
Attachments: SLING-4895.diff
RIght now, if e.g. an amendment is added/removed/updated, all
registration/unregistration is done in a large synchronized block. This
should be avoided
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [contrib] Contribution to Sling Web Console - Log Tail Plugin
Hi Satya, Thanks for the feedback and trying out the plugin. It would help me debug if you can provide me with a public URL where I can access the Sling instance you are running. Also, which browser are you using? It could be a browser DOM size limitation though I doubt it, since it doesn't work even after a document redraw (page refresh) -- Varun On Wed, Jul 29, 2015 at 2:58 PM, Satya Deep Maheshwari connus...@gmail.com wrote: Hi Varun I tried the log tail plugin and it looks quite useful especially for viewing logs on remote servers. I encountered a problem with it though. I see that after a couple of hours or so, it stops following the tail. I see that it does keep sending the ajax requests to the server to get the logs and gets a correct response as well but the tail just stops updating. Not sure if this is related to the log file length or the browser display limitation. Even refreshing the page does not help in fetching the latest logs. On Wed, Jul 22, 2015 at 7:40 PM, Varun Nagpal varun.nag...@gmail.com wrote: Hi All, As referred earlier on [0] I have developed a web console plugin to tail the server side logs on the browser. The motive to develop this was to ease access to logs while debugging issues on remote set ups. Apart from a UI feature set similar to baretail [1], it has the ability to filter log output using complex grammar and extensible filters. Request the dev community to consider it for contribution. Thanks and Regards, Varun Nagpal [0] http://apache-sling.73963.n3.nabble.com/Sling-Web-Console-Log-Tail-Plugin-td4050756.html [1] https://www.baremetalsoft.com/baretail/
[jira] [Resolved] (SLING-4914) LogPanel should pass appender name as request parameter
[ https://issues.apache.org/jira/browse/SLING-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved SLING-4914. Resolution: Fixed Change the implementation. Now url is like below http://localhost:8080/system/console/slinglog/tailer.txt?tail=number of lines to dumpname=appender name Done with http://svn.apache.org/r1693182 LogPanel should pass appender name as request parameter --- Key: SLING-4914 URL: https://issues.apache.org/jira/browse/SLING-4914 Project: Sling Issue Type: Bug Components: Commons Reporter: Chetan Mehrotra Assignee: Chetan Mehrotra Priority: Minor Fix For: Commons Log 4.0.6 SlingLogPanel currently passes the appender name as part of request url itself. This can at times pose problem as the appender name can be arbitrary. It would be better if the name is passed as part of request parameter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [contrib] Contribution to Sling Web Console - Log Tail Plugin
Thanks. I have shared the url privately with you. On Wed, Jul 29, 2015 at 3:14 PM, Varun Nagpal varun.nag...@gmail.com wrote: Hi Satya, Thanks for the feedback and trying out the plugin. It would help me debug if you can provide me with a public URL where I can access the Sling instance you are running. Also, which browser are you using? It could be a browser DOM size limitation though I doubt it, since it doesn't work even after a document redraw (page refresh) -- Varun On Wed, Jul 29, 2015 at 2:58 PM, Satya Deep Maheshwari connus...@gmail.com wrote: Hi Varun I tried the log tail plugin and it looks quite useful especially for viewing logs on remote servers. I encountered a problem with it though. I see that after a couple of hours or so, it stops following the tail. I see that it does keep sending the ajax requests to the server to get the logs and gets a correct response as well but the tail just stops updating. Not sure if this is related to the log file length or the browser display limitation. Even refreshing the page does not help in fetching the latest logs. On Wed, Jul 22, 2015 at 7:40 PM, Varun Nagpal varun.nag...@gmail.com wrote: Hi All, As referred earlier on [0] I have developed a web console plugin to tail the server side logs on the browser. The motive to develop this was to ease access to logs while debugging issues on remote set ups. Apart from a UI feature set similar to baretail [1], it has the ability to filter log output using complex grammar and extensible filters. Request the dev community to consider it for contribution. Thanks and Regards, Varun Nagpal [0] http://apache-sling.73963.n3.nabble.com/Sling-Web-Console-Log-Tail-Plugin-td4050756.html [1] https://www.baremetalsoft.com/baretail/
[jira] [Resolved] (SLING-4883) Extend content disposition filter protection to jcr:data
[
https://issues.apache.org/jira/browse/SLING-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-4883.
--
Resolution: Fixed
Fix Version/s: Security 1.0.12
Extend content disposition filter protection to jcr:data
Key: SLING-4883
URL: https://issues.apache.org/jira/browse/SLING-4883
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Fix For: Security 1.0.12
Attachments: SLING-4883-patch.txt
The current version of content disposition filter targets response content
type.
It would be nice to have a feature to also target forcing download of
{{jcr:data}} under configured paths
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4916) Refactor DistributionQueueItem to be independent of DistributionPackages
Marius Petria created SLING-4916: Summary: Refactor DistributionQueueItem to be independent of DistributionPackages Key: SLING-4916 URL: https://issues.apache.org/jira/browse/SLING-4916 Project: Sling Issue Type: Improvement Components: Distribution Reporter: Marius Petria Fix For: Content Distribution Core 0.1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4915) Order of sub-nodes is not maintained in case of a merge
Radu Cotescu created SLING-4915:
---
Summary: Order of sub-nodes is not maintained in case of a merge
Key: SLING-4915
URL: https://issues.apache.org/jira/browse/SLING-4915
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Affects Versions: Resource Merger 1.2.10
Reporter: Radu Cotescu
Priority: Minor
Fix For: Resource Merger 1.2.12
Given two content structures that should be merged by the Resource Merger, if
the second tree contains all the sub-nodes of the first tree, a new node added
in the second tree will always be added towards the end, irrespective of its
position in the sub-node tree.
Example:
{noformat}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node1
node4
node2
node3
{noformat}
When iterating over the child resources of {{/libs/p2/components/c1}},
{{node4}} will be the last child in the iteration instead of the second.
The workaround is to not define the redundant nodes and add the
{{sling:orderBefore}} property on {{node4}}, however this should be handled by
default by the merger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
version number changes in sling
Hi, I noticed that the version numbers of the poms in sling seem to be all over the place. If you look at [1] org.apache.felix | org.apache.sling.scripting.velocity current version is: 2.0.0-SNAPSHOT version before: 2.0.1-SNAPSHOT is that correct or am I looking at the commits the wrong way? thanks [1] http://www.headwire.com/sling/?path=contrib--scripting--velocity
[jira] [Resolved] (SLING-4403) XSS Configuration should allow caption tags
[ https://issues.apache.org/jira/browse/SLING-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4403. - Resolution: Fixed Fixed in [r1693280|https://svn.apache.org/r1693280]. XSS Configuration should allow caption tags --- Key: SLING-4403 URL: https://issues.apache.org/jira/browse/SLING-4403 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.0, XSS Protection API 1.0.2 Reporter: Amrit Verma Assignee: Radu Cotescu Fix For: XSS Protection API 1.0.4 caption tags should be allowed in output, currently they are removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-4584) Performance: XSSAPI.getValidHref should not be based on HTML filtering
[ https://issues.apache.org/jira/browse/SLING-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646117#comment-14646117 ] Radu Cotescu edited comment on SLING-4584 at 7/29/15 2:52 PM: -- Fixed in [r1685504|https://svn.apache.org/viewvc?view=revisionrevision=1685504]. Corrected excessive API version increase in [r1693281|https://svn.apache.org/viewvc?view=revisionrevision=1693281]. was (Author: radu.cotescu): Fixed in [r1685504|https://svn.apache.org/viewvc?view=revisionrevision=1685504]. Performance: XSSAPI.getValidHref should not be based on HTML filtering -- Key: SLING-4584 URL: https://issues.apache.org/jira/browse/SLING-4584 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.2 Reporter: Joel Richard Assignee: Radu Cotescu Labels: perfomance, xss Fix For: XSS Protection API 1.0.4 Attachments: 0001-SLING-4584-Performance-XSSAPI.getValidHref-should-no.patch Around 3% of the rendering time is spent in getValidHref because it uses AntiSamy (which is a HTML filter) to do the job. This is obviously a hack and adds a lot of unnecessary overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.6
+1 to both release distribution.core and distribution.samples (not binding) Tommaso 2015-07-29 16:30 GMT+02:00 Marius Petria mpet...@adobe.com: One more thing :). I also released (and included in the staging repo) org.apache.sling.distribution.sample-0.1.2 (which contains sample configs for various scenarios supported by distribution). Marius On 7/29/15, 5:25 PM, Marius Petria mpet...@adobe.com wrote: Hi, We solved 6 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12333012 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12323405 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1304/ 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 1304 /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.
[GitHub] sling pull request: SLING-4403 - XSS Configuration should allow ca...
Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/62 --- 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. ---
[jira] [Commented] (SLING-4403) XSS Configuration should allow caption tags
[ https://issues.apache.org/jira/browse/SLING-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646154#comment-14646154 ] ASF GitHub Bot commented on SLING-4403: --- Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/62 XSS Configuration should allow caption tags --- Key: SLING-4403 URL: https://issues.apache.org/jira/browse/SLING-4403 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.0, XSS Protection API 1.0.2 Reporter: Amrit Verma Assignee: Radu Cotescu Fix For: XSS Protection API 1.0.4 caption tags should be allowed in output, currently they are removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.6
+1 Cheers, Stefan On 7/29/15 4:25 PM, Marius Petria mpet...@adobe.com wrote: Hi, We solved 6 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12333012 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12323405 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1304/ 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 1304 /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.
[VOTE] Release Apache Sling Content Distribution Core version 0.1.6
Hi, We solved 6 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12333012 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12323405 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1304/ 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 1304 /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.
Re: version number changes in sling
On Wednesday 29 July 2015 06:45:50 Ruben Reusser wrote: Hi, hi Ruben, I noticed that the version numbers of the poms in sling seem to be all over the place. If you look at [1] org.apache.felix | org.apache.sling.scripting.velocity current version is: 2.0.0-SNAPSHOT version before: 2.0.1-SNAPSHOT is that correct or am I looking at the commits the wrong way? it is 2.0.0-SNAPSHOT and was 2.0.1-SNAPSHOT before (due to a cancelled release): http://svn.apache.org/viewvc/sling/trunk/contrib/scripting/velocity/pom.xml?view=log Regards, O. thanks [1] http://www.headwire.com/sling/?path=contrib--scripting--velocity
Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.6
One more thing :). I also released (and included in the staging repo) org.apache.sling.distribution.sample-0.1.2 (which contains sample configs for various scenarios supported by distribution). Marius On 7/29/15, 5:25 PM, Marius Petria mpet...@adobe.com wrote: Hi, We solved 6 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12333012 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12323405 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1304/ 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 1304 /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.
[jira] [Resolved] (SLING-4584) Performance: XSSAPI.getValidHref should not be based on HTML filtering
[ https://issues.apache.org/jira/browse/SLING-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4584. - Resolution: Fixed Assignee: Radu Cotescu Fixed in [r1685504|https://svn.apache.org/viewvc?view=revisionrevision=1685504]. Performance: XSSAPI.getValidHref should not be based on HTML filtering -- Key: SLING-4584 URL: https://issues.apache.org/jira/browse/SLING-4584 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.2 Reporter: Joel Richard Assignee: Radu Cotescu Labels: perfomance, xss Fix For: XSS Protection API 1.0.4 Attachments: 0001-SLING-4584-Performance-XSSAPI.getValidHref-should-no.patch Around 3% of the rendering time is spent in getValidHref because it uses AntiSamy (which is a HTML filter) to do the job. This is obviously a hack and adds a lot of unnecessary overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4560) XSSAPI#getValidHref is empty for valid Bengali or Hindi characters
[
https://issues.apache.org/jira/browse/SLING-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4560:
Fix Version/s: (was: XSS Protection API 1.0.4)
XSS Protection API 1.0.6
XSSAPI#getValidHref is empty for valid Bengali or Hindi characters
--
Key: SLING-4560
URL: https://issues.apache.org/jira/browse/SLING-4560
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Jean-Christophe Kautzmann
Fix For: XSS Protection API 1.0.6
I added (locally) 2 test cases to
org.apache.sling.xss.impl.XSSAPIImplTest#testGetValidHref:
{code}
{/etc/commerce/collections/中文, /etc/commerce/collections/中文},
{/etc/commerce/collections/⺁〡〢☉⊕〒, /etc/commerce/collections/⺁〡〢☉⊕〒},
{code}
the first test passes (chinese characters), the 2nd fails (bengali/hindi
characters) although it should pass as they are valid characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4273) Check list of required imports
[ https://issues.apache.org/jira/browse/SLING-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4273: Fix Version/s: (was: XSS Protection API 1.0.4) XSS Protection API 1.0.6 Check list of required imports -- Key: SLING-4273 URL: https://issues.apache.org/jira/browse/SLING-4273 Project: Sling Issue Type: Task Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Carsten Ziegeler Fix For: XSS Protection API 1.0.6 This is the current list of required imports for the xss module: javax.annotation, javax.crypto, javax.crypto.spec, javax.mail.internet, javax.naming,j avax.servlet, javax.servlet.http, javax.servlet.jsp, javax.servlet.jsp.tagext, javax.sql, javax.swing, javax.swing.border, javax.swing.event, javax.swing.filechooser, javax.swing.table, javax.swing.text, javax.swing.tree, javax.xml.datatype, javax.xml.namespace, javax.xml.parsers, javax.xml.transform, javax.xml.transform.dom, javax.xml.transform.sax, javax.xml.transform.stream, javax.xml.validation, org.apache.commons.codec.binary, org.apache.commons.collections, org.apache.commons.collections.comparators, org.apache.commons.collections.iterators, org.apache.commons.collections.keyvalue, org.apache.commons.collections.list, org.apache.commons.collections.map, org.apache.commons.collections.set, org.apache.commons.fileupload, org.apache.commons.fileupload.disk, org.apache.commons.fileupload.servlet, org.apache.commons.fileupload.util, org.apache.commons.httpclient, org.apache.commons.httpclient.methods, org.apache.commons.httpclient.params, org.apache.commons.lang, org.apache.commons.lang.exception, org.apache.commons.lang.text, org.apache.commons.logging, org.apache.log4j, org.apache.sling.api;version=[2.1,3), org.apache.sling.api.adapter;version=[2.2,3), org.apache.sling.api.resource;version=[2.1,3), org.apache.sling.commons.json;version=[2.0,3), org.apache.sling.commons.json.io;version=[2.0,3), org.apache.sling.xss;version=[1.0,1.1), org.osgi.service.event;version=[1.1,2), org.slf4j;version=[1.5,2), org.w3c.dom, org.w3c.dom.css, org.w3c.dom.events, org.w3c.dom.html, org.w3c.dom.ls, org.w3c.dom.ranges, org.w3c.dom.traversal, org.w3c.dom.views, org.xml.sax, org.xml.sax.ext, org.xml.sax.helpers Some of them shouldn't really be required like javax.mail.internet or the jsp api; for others like the apache commons stuff it would be nice to have versioned imports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4293) [XSS] Reduce footprint and dependencies
[ https://issues.apache.org/jira/browse/SLING-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4293: Affects Version/s: XSS Protection API 1.0.0 [XSS] Reduce footprint and dependencies --- Key: SLING-4293 URL: https://issues.apache.org/jira/browse/SLING-4293 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Felix Meschberger Fix For: XSS Protection API 1.0.6 Attachments: SLING-4293.patch The XSS bundle currently embeds all of the Antisamy, ESAPI, and Encoder libraries as well as substantial parts of Batik, NekoHTML, and Xerces. This is done by means of Private-Package and Embed-Dependency statements. Leveraging the BND Conditional-Package statement, both the size of the XSS bundle and the dependencies of it can be drastically reduced. The Conditional-Package statement basically causes just to include those packages that are actually needed to be embedded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4273) Check list of required imports
[ https://issues.apache.org/jira/browse/SLING-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4273: Affects Version/s: XSS Protection API 1.0.0 Check list of required imports -- Key: SLING-4273 URL: https://issues.apache.org/jira/browse/SLING-4273 Project: Sling Issue Type: Task Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Carsten Ziegeler Fix For: XSS Protection API 1.0.6 This is the current list of required imports for the xss module: javax.annotation, javax.crypto, javax.crypto.spec, javax.mail.internet, javax.naming,j avax.servlet, javax.servlet.http, javax.servlet.jsp, javax.servlet.jsp.tagext, javax.sql, javax.swing, javax.swing.border, javax.swing.event, javax.swing.filechooser, javax.swing.table, javax.swing.text, javax.swing.tree, javax.xml.datatype, javax.xml.namespace, javax.xml.parsers, javax.xml.transform, javax.xml.transform.dom, javax.xml.transform.sax, javax.xml.transform.stream, javax.xml.validation, org.apache.commons.codec.binary, org.apache.commons.collections, org.apache.commons.collections.comparators, org.apache.commons.collections.iterators, org.apache.commons.collections.keyvalue, org.apache.commons.collections.list, org.apache.commons.collections.map, org.apache.commons.collections.set, org.apache.commons.fileupload, org.apache.commons.fileupload.disk, org.apache.commons.fileupload.servlet, org.apache.commons.fileupload.util, org.apache.commons.httpclient, org.apache.commons.httpclient.methods, org.apache.commons.httpclient.params, org.apache.commons.lang, org.apache.commons.lang.exception, org.apache.commons.lang.text, org.apache.commons.logging, org.apache.log4j, org.apache.sling.api;version=[2.1,3), org.apache.sling.api.adapter;version=[2.2,3), org.apache.sling.api.resource;version=[2.1,3), org.apache.sling.commons.json;version=[2.0,3), org.apache.sling.commons.json.io;version=[2.0,3), org.apache.sling.xss;version=[1.0,1.1), org.osgi.service.event;version=[1.1,2), org.slf4j;version=[1.5,2), org.w3c.dom, org.w3c.dom.css, org.w3c.dom.events, org.w3c.dom.html, org.w3c.dom.ls, org.w3c.dom.ranges, org.w3c.dom.traversal, org.w3c.dom.views, org.xml.sax, org.xml.sax.ext, org.xml.sax.helpers Some of them shouldn't really be required like javax.mail.internet or the jsp api; for others like the apache commons stuff it would be nice to have versioned imports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4560) XSSAPI#getValidHref is empty for valid Bengali or Hindi characters
[
https://issues.apache.org/jira/browse/SLING-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4560:
Affects Version/s: XSS Protection API 1.0.0
XSSAPI#getValidHref is empty for valid Bengali or Hindi characters
--
Key: SLING-4560
URL: https://issues.apache.org/jira/browse/SLING-4560
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: XSS Protection API 1.0.0
Reporter: Jean-Christophe Kautzmann
Fix For: XSS Protection API 1.0.6
I added (locally) 2 test cases to
org.apache.sling.xss.impl.XSSAPIImplTest#testGetValidHref:
{code}
{/etc/commerce/collections/中文, /etc/commerce/collections/中文},
{/etc/commerce/collections/⺁〡〢☉⊕〒, /etc/commerce/collections/⺁〡〢☉⊕〒},
{code}
the first test passes (chinese characters), the 2nd fails (bengali/hindi
characters) although it should pass as they are valid characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4365) Streamline ESAPI configuration
[ https://issues.apache.org/jira/browse/SLING-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4365: Fix Version/s: (was: XSS Protection API 1.0.4) XSS Protection API 1.0.6 Streamline ESAPI configuration -- Key: SLING-4365 URL: https://issues.apache.org/jira/browse/SLING-4365 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Felix Meschberger Fix For: XSS Protection API 1.0.6 Currently the ESAPI is configured using the DefaultSecurityConfiguration class. This configuration is configured such as to: * read configuration from various file system locations, e.g. the user's home folder * list the helper classes to be used * configure the checking * configure logging In our context and setup, we don't want to have different classes configured, we want logging to always go through SLF4J logging and we want to limit and control where the configuration is read from. This issues is about creating a custom SecurityConfiguration class : * read from defined locations, probably one in the repository and one embedded in the bundle as a fallback. For example using the same configuration file as embedded default as for Sling Initial Content installation in the repository. * always log to SLF4J, maybe requiring an SLF4J based ESAPI LogFactory implementation. As a fallback, Log4J or commons logging APIs could still be used through the existing *-to-SLF4J API bridges we use. * Only support configuration of validation patterns (hence all classes statically defined) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4293) [XSS] Reduce footprint and dependencies
[ https://issues.apache.org/jira/browse/SLING-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4293: Fix Version/s: (was: XSS Protection API 1.0.4) XSS Protection API 1.0.6 [XSS] Reduce footprint and dependencies --- Key: SLING-4293 URL: https://issues.apache.org/jira/browse/SLING-4293 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Felix Meschberger Fix For: XSS Protection API 1.0.6 Attachments: SLING-4293.patch The XSS bundle currently embeds all of the Antisamy, ESAPI, and Encoder libraries as well as substantial parts of Batik, NekoHTML, and Xerces. This is done by means of Private-Package and Embed-Dependency statements. Leveraging the BND Conditional-Package statement, both the size of the XSS bundle and the dependencies of it can be drastically reduced. The Conditional-Package statement basically causes just to include those packages that are actually needed to be embedded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4365) Streamline ESAPI configuration
[ https://issues.apache.org/jira/browse/SLING-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4365: Affects Version/s: XSS Protection API 1.0.0 Streamline ESAPI configuration -- Key: SLING-4365 URL: https://issues.apache.org/jira/browse/SLING-4365 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: XSS Protection API 1.0.0 Reporter: Felix Meschberger Fix For: XSS Protection API 1.0.6 Currently the ESAPI is configured using the DefaultSecurityConfiguration class. This configuration is configured such as to: * read configuration from various file system locations, e.g. the user's home folder * list the helper classes to be used * configure the checking * configure logging In our context and setup, we don't want to have different classes configured, we want logging to always go through SLF4J logging and we want to limit and control where the configuration is read from. This issues is about creating a custom SecurityConfiguration class : * read from defined locations, probably one in the repository and one embedded in the bundle as a fallback. For example using the same configuration file as embedded default as for Sling Initial Content installation in the repository. * always log to SLF4J, maybe requiring an SLF4J based ESAPI LogFactory implementation. As a fallback, Log4J or commons logging APIs could still be used through the existing *-to-SLF4J API bridges we use. * Only support configuration of validation patterns (hence all classes statically defined) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4916) Refactor DistributionQueueItem to be independent of DistributionPackages
[ https://issues.apache.org/jira/browse/SLING-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-4916. -- Resolution: Fixed Resolved in https://github.com/apache/sling/commit/2e0a8dd45eda37924d032fa4b75878f48e27d0c3 Refactor DistributionQueueItem to be independent of DistributionPackages Key: SLING-4916 URL: https://issues.apache.org/jira/browse/SLING-4916 Project: Sling Issue Type: Improvement Components: Distribution Reporter: Marius Petria Fix For: Content Distribution Core 0.1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SLING-4916) Refactor DistributionQueueItem to be independent of DistributionPackages
[ https://issues.apache.org/jira/browse/SLING-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria reassigned SLING-4916: Assignee: Marius Petria Refactor DistributionQueueItem to be independent of DistributionPackages Key: SLING-4916 URL: https://issues.apache.org/jira/browse/SLING-4916 Project: Sling Issue Type: Improvement Components: Distribution Reporter: Marius Petria Assignee: Marius Petria Fix For: Content Distribution Core 0.1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
