[
https://issues.apache.org/jira/browse/SLING-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237982#comment-14237982
]
Antonio Sanso commented on SLING-4228:
--------------------------------------
adding Jenkins failure link
https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.launchpad.testing/testReport/org.apache.sling.launchpad.webapp.integrationtest/ResourceResolverProxyTest/runWriteableResourcesTest/
thanks [~bdelacretaz]
> Multi-value sling:alias property test fails (ResourceResolverTest)
> ------------------------------------------------------------------
>
> Key: SLING-4228
> URL: https://issues.apache.org/jira/browse/SLING-4228
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Bertrand Delacretaz
> Assignee: Antonio Sanso
> Priority: Minor
> Fix For: Resource Resolver 1.1.10
>
>
> The ResourceResolverTest.test_resolve_with_sling_alias_multi_value
> server-side integration test currently fails.
> I ran it on revision 1640140 of the resourceresolver and it passes, so it
> looks like it's http://svn.apache.org/r1640141 that broke it, which points to
> [~asanso] committing SLING-3844
> That test sets a multi-value sling:alias property on its test node with {
> "kind", "enfant" } as values - I'm not sure how that's supposed to work but
> the behavior has definitely changed.
> FWIW here's how to quickly run this server-side test:
> {code}
> $ cd launchpad/testing
> $ mvn clean launchpad:run
> # in another terminal
> $ curl -X POST
> http://localhost:8888/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest/test_resolve_with_sling_alias_multi_value.json
> ...
> "failure":
> "test_resolve_with_sling_alias_multi_value(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
> expected:<\/[kind]> but was:<\/[enfant]>",
> {code}
> The ResourceResolverTest can then be debugged out of the
> launchpad/test-services module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
