[jira] [Assigned] (SLING-6957) Failing tests when updating version of org.apache.sling.serviceusermapper to 1.3.2
[
https://issues.apache.org/jira/browse/SLING-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso reassigned SLING-6957:
Assignee: Antonio Sanso
> Failing tests when updating version of org.apache.sling.serviceusermapper to
> 1.3.2
> --
>
> Key: SLING-6957
> URL: https://issues.apache.org/jira/browse/SLING-6957
> Project: Sling
> Issue Type: Bug
> Components: JCR
>Reporter: angela
>Assignee: Antonio Sanso
>
> when updating the version of {{org.apache.sling.serviceusermapper}} from
> _1.0.0_ to _1.3.2_ within the pom.xml of {{org.apache.sling.jcr.base}}, the
> build of this module fails the following tests:
> {code}
> Running org.apache.sling.jcr.base.RepositoryInitializersTest
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.155 sec <<<
> FAILURE! - in org.apache.sling.jcr.base.RepositoryInitializersTest
> inOrderInitializers(org.apache.sling.jcr.base.RepositoryInitializersTest)
> Time elapsed: 0.121 sec <<< ERROR!
> java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
> factory: No matching activation method with name 'configure' found in class
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
> at
> org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:69)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 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)
> Caused by: java.lang.RuntimeException: No matching activation method with
> name 'configure' found in class
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
> at
> org.apache.sling.testing.mock.osgi.OsgiServiceUtil.activateDeactivate(OsgiServiceUtil.java:157)
> at
> org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:190)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.registerServiceIfNotPresent(ResourceResolverFactoryInitializer.java:160)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.ensureResourceResolverFactoryActivatorDependencies(ResourceResolverFactoryInitializer.java:117)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.setUp(ResourceResolverFactoryInitializer.java:74)
> at
> org.apache.sling.testing.mock.sling.MockSling.newResourceResolverFactory(MockSling.java:88)
> at
> org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:45)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
> at
>
[jira] [Created] (SLING-6959) XssProtection changes html semantic caused by formatting
Lukas Kummer created SLING-6959:
---
Summary: XssProtection changes html semantic caused by formatting
Key: SLING-6959
URL: https://issues.apache.org/jira/browse/SLING-6959
Project: Sling
Issue Type: Bug
Affects Versions: Scripting Sightly Engine 1.0.2, XSS Protection API 1.0.2
Environment: AEM
Reporter: Lukas Kummer
Priority: Minor
Attachments: space.png
When using sightly the following html:
{code:html}
${component.infoline @ context='html'}
{code}
it will be compiled to:
{code:java}
String var_28 = ((" "+renderContext.toString(renderContext.call("xss",
renderContext.resolveProperty(_global_component, "infoline"), "html")))+" ");
{code}
which calls
org.apache.sling.scripting.sightly.impl.engine.extension.XSSRuntimeExtension.call(RenderContext,
Object...)
and later:
org.apache.sling.xss.impl.XSSAPIImpl.filterHTML(String)
When this method is called with this String:
{code:html}
Is it a threat or an opportunity?
Is it a threat or an opportunity?
{code}
will be turned into
{code:html}
Is it a threat
or an opportunity
?
Is it a threat or an opportunity?
{code}
which leads to the problem, that there will be a space between the word
opportunity and the question mark.
However, the formatting could be configured by changing the
SLING-INF/content/config.xml
(from to )
But anyway the formatting shouldn't change the semantics, which why the
formatting directive should be always false
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list
[
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
]
Konrad Windszus edited comment on SLING-6956 at 6/14/17 12:17 PM:
--
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to the new items being added at the end of the list
{code}
node1
node2
node3
node4
{code}
Only one underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should not change the order
{code}
node1
node2
node3
{code}
Some underlying resource being overlaid in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should lead to the order from the overlaid resources
{code}
node1
node3
node2
{code}
was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to the new items being added at the end of the list
{code}
node1
node2
node3
node4
{code}
Some underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should lead to the same order
{code}
node1
node2
node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should lead to
{code}
node1
node3
node2
{code}
> Sling Resource Merger: Resources being overlaid are always listed at the end
> of the list
>
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
> Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed
> last!
> This is also not desired. Only in case some resources have been added which
> were not defined by the underlying resource, the order should be changed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SLING-6738) Import ACLs with JSON content
[
https://issues.apache.org/jira/browse/SLING-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6738.
---
Resolution: Fixed
please note this is already supported for some years by JCR content loader -
but was not documented.
i've added some documentation about it:
http://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#acls-and-principals
please repopen the ticket if this does not fit your needs.
> Import ACLs with JSON content
> -
>
> Key: SLING-6738
> URL: https://issues.apache.org/jira/browse/SLING-6738
> Project: Sling
> Issue Type: Improvement
> Components: JCR
>Affects Versions: JCR ContentLoader 2.1.10
>Reporter: Guillaume Lucazeau
>
> It would be nice to be able to create ACLs found in a JSON content exported
> from Sling. Currently, the node are protected and the import fails.
> "rep:policy": {
> "jcr:primaryType": "rep:ACL",
> "allow": {
> "rep:privileges": [
> "jcr:addChildNodes"
> ],
> "rep:principalName": "myUser",
> "jcr:primaryType": "rep:GrantACE"
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SLING-6957) Failing tests when updating version of org.apache.sling.serviceusermapper to 1.3.2
[
https://issues.apache.org/jira/browse/SLING-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049199#comment-16049199
]
angela commented on SLING-6957:
---
[~asanso], i tried a few more things with different versions of the various
testing-mocking modules referenced in _org.apache.sling.jcr.base_ => always
different errors but not a single one that worked.
> Failing tests when updating version of org.apache.sling.serviceusermapper to
> 1.3.2
> --
>
> Key: SLING-6957
> URL: https://issues.apache.org/jira/browse/SLING-6957
> Project: Sling
> Issue Type: Bug
> Components: JCR
>Reporter: angela
>Assignee: Antonio Sanso
>
> when updating the version of {{org.apache.sling.serviceusermapper}} from
> _1.0.0_ to _1.3.2_ within the pom.xml of {{org.apache.sling.jcr.base}}, the
> build of this module fails the following tests:
> {code}
> Running org.apache.sling.jcr.base.RepositoryInitializersTest
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.155 sec <<<
> FAILURE! - in org.apache.sling.jcr.base.RepositoryInitializersTest
> inOrderInitializers(org.apache.sling.jcr.base.RepositoryInitializersTest)
> Time elapsed: 0.121 sec <<< ERROR!
> java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
> factory: No matching activation method with name 'configure' found in class
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
> at
> org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:69)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 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)
> Caused by: java.lang.RuntimeException: No matching activation method with
> name 'configure' found in class
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
> at
> org.apache.sling.testing.mock.osgi.OsgiServiceUtil.activateDeactivate(OsgiServiceUtil.java:157)
> at
> org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:190)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.registerServiceIfNotPresent(ResourceResolverFactoryInitializer.java:160)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.ensureResourceResolverFactoryActivatorDependencies(ResourceResolverFactoryInitializer.java:117)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.setUp(ResourceResolverFactoryInitializer.java:74)
> at
> org.apache.sling.testing.mock.sling.MockSling.newResourceResolverFactory(MockSling.java:88)
> at
> org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:45)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
> at
>
[jira] [Created] (SLING-6958) Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
Stefan Seifert created SLING-6958:
-
Summary: Sling Eclipse IDE Tooling fails when exporting rep:policy
nodes to server
Key: SLING-6958
URL: https://issues.apache.org/jira/browse/SLING-6958
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.1.0
Reporter: Stefan Seifert
Fix For: Sling Eclipse IDE 1.2.0
usecase - try to export an content package eclipse project with sling ide
tooling (i've tested only version 1.1.0) to a local instance, e.g. this one:
https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/tree/master/ui.apps
this fails once it hits the "rep:policy" node with this exception:
{noformat}
[14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
/apps/public/weretail/hapi_types : JcrResult[ success:true] (25 ms)
[14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
/apps/public/weretail/hapi_types/rep:policy : JcrResult[ success:false,
exception: org.apache.sling.ide.transport.RepositoryException -
javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.] (12 ms)
org.apache.sling.ide.transport.RepositoryException:
javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.
at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:76)
at
org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:45)
at
org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1$2.visit(ExportWizard.java:89)
at
org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
at
org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
at
org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
at
org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
at
org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
at
org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
at
org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
at
org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
at
org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
at
org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
at
org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
at
org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1.run(ExportWizard.java:81)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Caused by: javax.jcr.nodetype.ConstraintViolationException: {}allow is
protected.
at
org.apache.jackrabbit.jcr2spi.nodetype.EffectiveNodeTypeImpl.checkAddNodeConstraints(EffectiveNodeTypeImpl.java:375)
at
org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkAddNode(ItemStateValidator.java:388)
at
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.addNodeState(SessionItemStateManager.java:435)
at
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.visit(SessionItemStateManager.java:245)
at
org.apache.jackrabbit.jcr2spi.operation.AddNode.accept(AddNode.java:79)
at
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.execute(SessionItemStateManager.java:215)
at org.apache.jackrabbit.jcr2spi.NodeImpl.createNode(NodeImpl.java:1454)
at org.apache.jackrabbit.jcr2spi.NodeImpl.addNode(NodeImpl.java:186)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.createNode(AddOrUpdateNodeCommand.java:176)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:100)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:112)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:85)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:68)
... 17 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SLING-6957) Failing tests when updating version of
angela created SLING-6957:
-
Summary: Failing tests when updating version of
Key: SLING-6957
URL: https://issues.apache.org/jira/browse/SLING-6957
Project: Sling
Issue Type: Bug
Components: JCR
Reporter: angela
when updating the version of {{org.apache.sling.serviceusermapper}} from
_1.0.0_ to _1.3.2_ within the pom.xml of {{org.apache.sling.jcr.base}}, the
build of this module fails the following tests:
{code}
Running org.apache.sling.jcr.base.RepositoryInitializersTest
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.155 sec <<<
FAILURE! - in org.apache.sling.jcr.base.RepositoryInitializersTest
inOrderInitializers(org.apache.sling.jcr.base.RepositoryInitializersTest) Time
elapsed: 0.121 sec <<< ERROR!
java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
factory: No matching activation method with name 'configure' found in class
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
at
org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:69)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
at
org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
at
org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
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)
Caused by: java.lang.RuntimeException: No matching activation method with name
'configure' found in class
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
at
org.apache.sling.testing.mock.osgi.OsgiServiceUtil.activateDeactivate(OsgiServiceUtil.java:157)
at
org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:190)
at
org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.registerServiceIfNotPresent(ResourceResolverFactoryInitializer.java:160)
at
org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.ensureResourceResolverFactoryActivatorDependencies(ResourceResolverFactoryInitializer.java:117)
at
org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.setUp(ResourceResolverFactoryInitializer.java:74)
at
org.apache.sling.testing.mock.sling.MockSling.newResourceResolverFactory(MockSling.java:88)
at
org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:45)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
at
org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
at
org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
[jira] [Updated] (SLING-6957) Failing tests when updating version of org.apache.sling.serviceusermapper to 1.3.2
[
https://issues.apache.org/jira/browse/SLING-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated SLING-6957:
--
Summary: Failing tests when updating version of
org.apache.sling.serviceusermapper to 1.3.2 (was: Failing tests when updating
version of )
> Failing tests when updating version of org.apache.sling.serviceusermapper to
> 1.3.2
> --
>
> Key: SLING-6957
> URL: https://issues.apache.org/jira/browse/SLING-6957
> Project: Sling
> Issue Type: Bug
> Components: JCR
>Reporter: angela
>
> when updating the version of {{org.apache.sling.serviceusermapper}} from
> _1.0.0_ to _1.3.2_ within the pom.xml of {{org.apache.sling.jcr.base}}, the
> build of this module fails the following tests:
> {code}
> Running org.apache.sling.jcr.base.RepositoryInitializersTest
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.155 sec <<<
> FAILURE! - in org.apache.sling.jcr.base.RepositoryInitializersTest
> inOrderInitializers(org.apache.sling.jcr.base.RepositoryInitializersTest)
> Time elapsed: 0.121 sec <<< ERROR!
> java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
> factory: No matching activation method with name 'configure' found in class
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
> at
> org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:69)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
> at
> org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 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)
> Caused by: java.lang.RuntimeException: No matching activation method with
> name 'configure' found in class
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
> at
> org.apache.sling.testing.mock.osgi.OsgiServiceUtil.activateDeactivate(OsgiServiceUtil.java:157)
> at
> org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:190)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.registerServiceIfNotPresent(ResourceResolverFactoryInitializer.java:160)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.ensureResourceResolverFactoryActivatorDependencies(ResourceResolverFactoryInitializer.java:117)
> at
> org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.setUp(ResourceResolverFactoryInitializer.java:74)
> at
> org.apache.sling.testing.mock.sling.MockSling.newResourceResolverFactory(MockSling.java:88)
> at
> org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:45)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
> at
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
> at
>
[jira] [Commented] (SLING-6958) Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
[
https://issues.apache.org/jira/browse/SLING-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049383#comment-16049383
]
Konrad Windszus commented on SLING-6958:
Isn't this a duplicate of SLING-3827?
> Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
> -
>
> Key: SLING-6958
> URL: https://issues.apache.org/jira/browse/SLING-6958
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Stefan Seifert
> Fix For: Sling Eclipse IDE 1.2.0
>
>
> usecase - try to export an content package eclipse project with sling ide
> tooling (i've tested only version 1.1.0) to a local instance, e.g. this one:
> https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/tree/master/ui.apps
> this fails once it hits the "rep:policy" node with this exception:
> {noformat}
> [14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
> /apps/public/weretail/hapi_types : JcrResult[ success:true] (25 ms)
> [14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
> /apps/public/weretail/hapi_types/rep:policy : JcrResult[ success:false,
> exception: org.apache.sling.ide.transport.RepositoryException -
> javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.] (12
> ms)
> org.apache.sling.ide.transport.RepositoryException:
> javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.
> at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
> at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:76)
> at
> org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:45)
> at
> org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1$2.visit(ExportWizard.java:89)
> at
> org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at
> org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at
> org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at
> org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at
> org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1.run(ExportWizard.java:81)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: {}allow is
> protected.
> at
> org.apache.jackrabbit.jcr2spi.nodetype.EffectiveNodeTypeImpl.checkAddNodeConstraints(EffectiveNodeTypeImpl.java:375)
> at
> org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkAddNode(ItemStateValidator.java:388)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.addNodeState(SessionItemStateManager.java:435)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.visit(SessionItemStateManager.java:245)
> at
> org.apache.jackrabbit.jcr2spi.operation.AddNode.accept(AddNode.java:79)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.execute(SessionItemStateManager.java:215)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.createNode(NodeImpl.java:1454)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.addNode(NodeImpl.java:186)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.createNode(AddOrUpdateNodeCommand.java:176)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:100)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:112)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:85)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
> at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:68)
> ... 17 more
[jira] [Created] (SLING-6960) JCR Content Parser: Ignore security:acl and security:principals nodes
Stefan Seifert created SLING-6960:
-
Summary: JCR Content Parser: Ignore security:acl and
security:principals nodes
Key: SLING-6960
URL: https://issues.apache.org/jira/browse/SLING-6960
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Content Parser 1.2.2
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Fix For: JCR Content Parser 1.2.4
JCR content loader supports special JSON definitions for ACLs and principals
via {{security:acl}} and {[security:principals}} in JSON files.
those objects should be ignored by content parser because they require special
handling.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SLING-6960) JCR Content Parser: Ignore security:acl and security:principals nodes
[
https://issues.apache.org/jira/browse/SLING-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-6960:
--
Description:
JCR content loader supports special JSON definitions for ACLs and principals
via {{security:acl}} and {{security:principals}} in JSON files.
those objects should be ignored by content parser because they require special
handling.
was:
JCR content loader supports special JSON definitions for ACLs and principals
via {{security:acl}} and {[security:principals}} in JSON files.
those objects should be ignored by content parser because they require special
handling.
> JCR Content Parser: Ignore security:acl and security:principals nodes
> -
>
> Key: SLING-6960
> URL: https://issues.apache.org/jira/browse/SLING-6960
> Project: Sling
> Issue Type: Improvement
> Components: JCR
>Affects Versions: JCR Content Parser 1.2.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: JCR Content Parser 1.2.4
>
>
> JCR content loader supports special JSON definitions for ACLs and principals
> via {{security:acl}} and {{security:principals}} in JSON files.
> those objects should be ignored by content parser because they require
> special handling.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SLING-6960) JCR Content Parser: Ignore security:acl and security:principals nodes
[
https://issues.apache.org/jira/browse/SLING-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6960.
---
Resolution: Fixed
Completed: At revision: 1798723
> JCR Content Parser: Ignore security:acl and security:principals nodes
> -
>
> Key: SLING-6960
> URL: https://issues.apache.org/jira/browse/SLING-6960
> Project: Sling
> Issue Type: Improvement
> Components: JCR
>Affects Versions: JCR Content Parser 1.2.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: JCR Content Parser 1.2.4
>
>
> JCR content loader supports special JSON definitions for ACLs and principals
> via {{security:acl}} and {{security:principals}} in JSON files.
> those objects should be ignored by content parser because they require
> special handling.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SLING-6958) Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
[
https://issues.apache.org/jira/browse/SLING-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-6958:
--
Fix Version/s: (was: Sling Eclipse IDE 1.2.0)
> Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
> -
>
> Key: SLING-6958
> URL: https://issues.apache.org/jira/browse/SLING-6958
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Stefan Seifert
>
> usecase - try to export an content package eclipse project with sling ide
> tooling (i've tested only version 1.1.0) to a local instance, e.g. this one:
> https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/tree/master/ui.apps
> this fails once it hits the "rep:policy" node with this exception:
> {noformat}
> [14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
> /apps/public/weretail/hapi_types : JcrResult[ success:true] (25 ms)
> [14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
> /apps/public/weretail/hapi_types/rep:policy : JcrResult[ success:false,
> exception: org.apache.sling.ide.transport.RepositoryException -
> javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.] (12
> ms)
> org.apache.sling.ide.transport.RepositoryException:
> javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.
> at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
> at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:76)
> at
> org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:45)
> at
> org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1$2.visit(ExportWizard.java:89)
> at
> org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at
> org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at
> org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at
> org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at
> org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1.run(ExportWizard.java:81)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: {}allow is
> protected.
> at
> org.apache.jackrabbit.jcr2spi.nodetype.EffectiveNodeTypeImpl.checkAddNodeConstraints(EffectiveNodeTypeImpl.java:375)
> at
> org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkAddNode(ItemStateValidator.java:388)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.addNodeState(SessionItemStateManager.java:435)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.visit(SessionItemStateManager.java:245)
> at
> org.apache.jackrabbit.jcr2spi.operation.AddNode.accept(AddNode.java:79)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.execute(SessionItemStateManager.java:215)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.createNode(NodeImpl.java:1454)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.addNode(NodeImpl.java:186)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.createNode(AddOrUpdateNodeCommand.java:176)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:100)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:112)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:85)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
> at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:68)
> ... 17 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SLING-6961) FsResource: Ignore security:acl and security:principals nodes
Stefan Seifert created SLING-6961:
-
Summary: FsResource: Ignore security:acl and security:principals
nodes
Key: SLING-6961
URL: https://issues.apache.org/jira/browse/SLING-6961
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: File System Resource Provider 2.1.4, File System Resource
Provider 1.4.4
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Fix For: File System Resource Provider 1.4.6, File System Resource
Provider 2.1.6
JCR content loader supports special JSON definitions for ACLs and principals
via {{security:acl}} and {{security:principals}} in JSON files.
those objects should be ignored by fsresource or the parsing of the whole JSON
file will fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SLING-6958) Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
[
https://issues.apache.org/jira/browse/SLING-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6958.
---
Resolution: Duplicate
yes, i think so - i've look for an already existing ticket but did not find
that one
> Sling Eclipse IDE Tooling fails when exporting rep:policy nodes to server
> -
>
> Key: SLING-6958
> URL: https://issues.apache.org/jira/browse/SLING-6958
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Stefan Seifert
> Fix For: Sling Eclipse IDE 1.2.0
>
>
> usecase - try to export an content package eclipse project with sling ide
> tooling (i've tested only version 1.1.0) to a local instance, e.g. this one:
> https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/tree/master/ui.apps
> this fails once it hits the "rep:policy" node with this exception:
> {noformat}
> [14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
> /apps/public/weretail/hapi_types : JcrResult[ success:true] (25 ms)
> [14. Juni 2017 15:48:26 MESZ] AddOrUpdateNodeCommand ->
> /apps/public/weretail/hapi_types/rep:policy : JcrResult[ success:false,
> exception: org.apache.sling.ide.transport.RepositoryException -
> javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.] (12
> ms)
> org.apache.sling.ide.transport.RepositoryException:
> javax.jcr.nodetype.ConstraintViolationException: {}allow is protected.
> at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
> at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:76)
> at
> org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:45)
> at
> org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1$2.visit(ExportWizard.java:89)
> at
> org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at
> org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at
> org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at
> org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at
> org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at
> org.apache.sling.ide.eclipse.ui.internal.ExportWizard$1.run(ExportWizard.java:81)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: {}allow is
> protected.
> at
> org.apache.jackrabbit.jcr2spi.nodetype.EffectiveNodeTypeImpl.checkAddNodeConstraints(EffectiveNodeTypeImpl.java:375)
> at
> org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkAddNode(ItemStateValidator.java:388)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.addNodeState(SessionItemStateManager.java:435)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.visit(SessionItemStateManager.java:245)
> at
> org.apache.jackrabbit.jcr2spi.operation.AddNode.accept(AddNode.java:79)
> at
> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.execute(SessionItemStateManager.java:215)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.createNode(NodeImpl.java:1454)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.addNode(NodeImpl.java:186)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.createNode(AddOrUpdateNodeCommand.java:176)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:100)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:112)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:85)
> at
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
> at
[jira] [Commented] (SLING-3827) Unable to create nodes with protected properties, e.g. rep:User
[
https://issues.apache.org/jira/browse/SLING-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049385#comment-16049385
]
Stefan Seifert commented on SLING-3827:
---
same problem applies to rep:policy nodes with ACL definitions, see SLING-6958
for details.
> Unable to create nodes with protected properties, e.g. rep:User
> ---
>
> Key: SLING-3827
> URL: https://issues.apache.org/jira/browse/SLING-3827
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.4
>Reporter: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.2.0
>
>
> I tried to create a user using the tooling, and I get back an exception:
> The debug trace is
> {noformat}
> | Worker-886 | 2014-08-06 18:10:22.590 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | update | 96 |
> Created node at /home/users/system/blabla with primaryType rep:User |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateMixins
> | 347 | Added new mixin rep:AccessControllable to node at path
> /home/users/system/blabla |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateNode |
> 298 | Setting property rep:principalName with value
> org.apache.jackrabbit.spi.commons.value.QValueValue@b7c2c87f (raw =
> mcm-service) on node at /home/users/system/blabla |
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SLING-6961) FsResource: Ignore security:acl and security:principals nodes
[
https://issues.apache.org/jira/browse/SLING-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6961.
---
Resolution: Fixed
Completed: At revision: 1798724 (2.x)
Completed: At revision: 1798725 (1.x)
> FsResource: Ignore security:acl and security:principals nodes
> -
>
> Key: SLING-6961
> URL: https://issues.apache.org/jira/browse/SLING-6961
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: File System Resource Provider 1.4.4, File System
> Resource Provider 2.1.4
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Resource Provider 1.4.6, File System
> Resource Provider 2.1.6
>
>
> JCR content loader supports special JSON definitions for ACLs and principals
> via {{security:acl}} and {{security:principals}} in JSON files.
> those objects should be ignored by fsresource or the parsing of the whole
> JSON file will fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SLING-6957) Failing tests when updating version of org.apache.sling.serviceusermapper to 1.3.2
[
https://issues.apache.org/jira/browse/SLING-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated SLING-6957:
--
Description:
when updating the version of {{org.apache.sling.serviceusermapper}} from
_1.0.0_ to _1.3.2_ within the pom.xml of {{org.apache.sling.jcr.base}}, the
build of this module fails the following tests:
{code}
Running org.apache.sling.jcr.base.RepositoryInitializersTest
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.155 sec <<<
FAILURE! - in org.apache.sling.jcr.base.RepositoryInitializersTest
inOrderInitializers(org.apache.sling.jcr.base.RepositoryInitializersTest) Time
elapsed: 0.121 sec <<< ERROR!
java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
factory: No matching activation method with name 'configure' found in class
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
at
org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:69)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
at
org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
at
org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
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)
Caused by: java.lang.RuntimeException: No matching activation method with name
'configure' found in class
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl
at
org.apache.sling.testing.mock.osgi.OsgiServiceUtil.activateDeactivate(OsgiServiceUtil.java:157)
at
org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:190)
at
org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.registerServiceIfNotPresent(ResourceResolverFactoryInitializer.java:160)
at
org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.ensureResourceResolverFactoryActivatorDependencies(ResourceResolverFactoryInitializer.java:117)
at
org.apache.sling.testing.mock.sling.ResourceResolverFactoryInitializer.setUp(ResourceResolverFactoryInitializer.java:74)
at
org.apache.sling.testing.mock.sling.MockSling.newResourceResolverFactory(MockSling.java:88)
at
org.apache.sling.testing.mock.sling.context.ContextResourceResolverFactory.get(ContextResourceResolverFactory.java:45)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.newResourceResolverFactory(SlingContextImpl.java:107)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:98)
at
org.apache.sling.testing.mock.sling.junit.SlingContext.access$000(SlingContext.java:32)
at
org.apache.sling.testing.mock.sling.junit.SlingContext$1.before(SlingContext.java:113)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at
Re: [VOTE] Release Apache Sling Security 1.1.4
On Tue, 2017-06-13 at 12:47 +, Antonio Sanso wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part
[jira] [Commented] (SLING-6955) Convert Sling website to JBake and gitpubsub
[ https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049772#comment-16049772 ] Bertrand Delacretaz commented on SLING-6955: The site looks pretty good now but there's a number of "small" things to fix, I have added a TODO list in the README. > Convert Sling website to JBake and gitpubsub > > > Key: SLING-6955 > URL: https://issues.apache.org/jira/browse/SLING-6955 > Project: Sling > Issue Type: Bug > Components: Site >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz > > I've started experimenting with JBake to generate the Sling website. If that > works well we might switch to that + gitpubsub to have a more flexible way to > generate the site. > My current experiment is at https://github.com/bdelacretaz/sling-jbake, at > this point the site starts looking like the current one and many pages work > well. > Internal links will need to be converted, all *.md files need a more complete > "front matter" section, currently I have a stub for that, and I think images > need to move under the assets folder. > To play with that, generate the site with the bake.sh script (setup > shamelessly copied from https://github.com/apache/incubator-tamaya-site) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SLING-6955) Convert Sling website to JBake and gitpubsub
[ https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048873#comment-16048873 ] Bertrand Delacretaz commented on SLING-6955: Contributions are welcome of course, for now I'm aiming to recreate the website without any layout changes, to be able to validate the conversion. > Convert Sling website to JBake and gitpubsub > > > Key: SLING-6955 > URL: https://issues.apache.org/jira/browse/SLING-6955 > Project: Sling > Issue Type: Bug > Components: Site >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz > > I've started experimenting with JBake to generate the Sling website. If that > works well we might switch to that + gitpubsub to have a more flexible way to > generate the site. > My current experiment is at https://github.com/bdelacretaz/sling-jbake, at > this point the site starts looking like the current one and many pages work > well. > Internal links will need to be converted, all *.md files need a more complete > "front matter" section, currently I have a stub for that, and I think images > need to move under the assets folder. > To play with that, generate the site with the bake.sh script (setup > shamelessly copied from https://github.com/apache/incubator-tamaya-site) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SLING-6956) Sling Resource Merger: Resources being overlaid are always sorted at the end of the list
Konrad Windszus created SLING-6956: -- Summary: Sling Resource Merger: Resources being overlaid are always sorted at the end of the list Key: SLING-6956 URL: https://issues.apache.org/jira/browse/SLING-6956 Project: Sling Issue Type: Bug Affects Versions: Resource Merger 1.3.2 Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Resource Merger 1.3.4 Due to the change in SLING-4915, all overlaid resources are now always listed last! This is also not desired. Only in case some resources have been added which were not defined by the underlying resource, the order should be changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list
[ https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6956: --- Summary: Sling Resource Merger: Resources being overlaid are always listed at the end of the list (was: Sling Resource Merger: Resources being overlaid are always sorted at the end of the list) > Sling Resource Merger: Resources being overlaid are always listed at the end > of the list > > > Key: SLING-6956 > URL: https://issues.apache.org/jira/browse/SLING-6956 > Project: Sling > Issue Type: Bug >Affects Versions: Resource Merger 1.3.2 >Reporter: Konrad Windszus >Assignee: Konrad Windszus > Fix For: Resource Merger 1.3.4 > > > Due to the change in SLING-4915, all overlaid resources are now always listed > last! > This is also not desired. Only in case some resources have been added which > were not defined by the underlying resource, the order should be changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list
[
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
]
Konrad Windszus commented on SLING-6956:
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to
{code}
node1
node2
node3
node4
{code}
Some underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should lead to
{code}
node1
node2
node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should still lead to
{code}
node1
node2
node3
{code}
> Sling Resource Merger: Resources being overlaid are always listed at the end
> of the list
>
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
> Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed
> last!
> This is also not desired. Only in case some resources have been added which
> were not defined by the underlying resource, the order should be changed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list
[
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
]
Konrad Windszus edited comment on SLING-6956 at 6/14/17 12:03 PM:
--
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to the new items being added at the end of the list
{code}
node1
node2
node3
node4
{code}
Some underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should lead to the same order
{code}
node1
node2
node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should still lead to
{code}
node1
node2
node3
{code}
was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to
{code}
node1
node2
node3
node4
{code}
Some underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should lead to
{code}
node1
node2
node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should still lead to
{code}
node1
node2
node3
{code}
> Sling Resource Merger: Resources being overlaid are always listed at the end
> of the list
>
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
> Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed
> last!
> This is also not desired. Only in case some resources have been added which
> were not defined by the underlying resource, the order should be changed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list
[
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
]
Konrad Windszus edited comment on SLING-6956 at 6/14/17 12:08 PM:
--
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to the new items being added at the end of the list
{code}
node1
node2
node3
node4
{code}
Some underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should lead to the same order
{code}
node1
node2
node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should lead to
{code}
node1
node3
node2
{code}
was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node4
{code} should lead to the new items being added at the end of the list
{code}
node1
node2
node3
node4
{code}
Some underlying resources being modified
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node2
{code} should lead to the same order
{code}
node1
node2
node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
node1
node2
node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
node3
node2
{code} should still lead to
{code}
node1
node2
node3
{code}
> Sling Resource Merger: Resources being overlaid are always listed at the end
> of the list
>
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
> Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed
> last!
> This is also not desired. Only in case some resources have been added which
> were not defined by the underlying resource, the order should be changed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
