[SLING-9580] Make the dependency resolution more resource-type centric

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Scripting HTL JS Use Provider 1.2.2
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 10/Jul/20 11:22
• Updated: 12/Aug/20 10:06
• Resolved: 10/Jul/20 11:24

Description

The current (1.2.0 and before) implementation of the org.apache.sling.scripting.sightly.js.impl.use.DependencyResolver can be simplified and reduced to two use-cases:

1. caller is a JS script - resolve the dependency relative to the script, but taking resource type hierarchy in consideration
2. caller is a component script - resolve the dependency relative to the resource type, but traverse the resource type hierarchy if needed

Issue Links

• causes: SLING-9619 The JavaScript Use Provider does not allow loading scripts relative to search paths any more
• is cloned by: SLING-9599 Incomplete non-existing resource check
• relates to: SLING-9657 Same-name JS Use dependencies are not always correctly resolved