[
https://issues.apache.org/jira/browse/SLING-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930332#comment-16930332
]
Vikas Saurabh commented on SLING-8710:
--------------------------------------
Ack. In that direction, I think allowing configuration via props (passed in
ctor) seems like the way forward. The tests would still need to make that
configuration available though - potentially using some common class as that
end.
Also, I think we should keep current logic of dynamic lanes evaluation if
configuration isn't provided.
Wdyt?
> IndexingClient should have configurable lanes
> ---------------------------------------------
>
> Key: SLING-8710
> URL: https://issues.apache.org/jira/browse/SLING-8710
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Reporter: Vikas Saurabh
> Priority: Major
> Labels: sling-IT
>
> {{IndexingClient}} currently relies on {{OsgiConsoleCient}} to peek into
> system's lane configuration. That, in turn, requires access to
> /system/console which might be blocked on the system which is being tested.
> As indexing lanes in a setup isn't a very dynamic property, a quick work
> around could be for {{IndexingClient}} to allow setting up "expected index
> lanes in target setup".
> This issue would be an improvement over what was implemented in SLING-7169.
> [~rombert] and [~volteanu], since most of the comments over there are from
> you guys, wdyt about this improvement?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
