[
https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467144#comment-15467144
]
Stefan Seifert commented on SLING-6040:
---------------------------------------
here is a proposal: https://github.com/apache/sling/pull/167
the change on sling-mock side is small: one new method, one new dependency.
on resource builder side we need no functional change, but we need to split up
the project into two parts (impl and integration-test including the sling-mock
based unit test) to remove the sling-mock dependency from the resourcebuilder
impl project to avoid cyclic dependencies.
> Add ResourceBuilder Support to sling-mock
> -----------------------------------------
>
> Key: SLING-6040
> URL: https://issues.apache.org/jira/browse/SLING-6040
> Project: Sling
> Issue Type: New Feature
> Components: Extensions, Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing Sling Mock 2.0.2, Resource Builder 1.0.0
>
>
> we want to provide the Sling ResourceBuilder as alternative way in sling mock
> to simply create test resources.
> currently sling mocks supports it's own "ContentBuilder" via the {{create()}}
> method on the context.
> a new method {{build()}} should be added which provides a preconfigred
> ResourceBuilder instance for the current resource resolver.
> alternatively the ResourceResolverFactory service can be accessed directly
> form the test code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
