[SLING-4191] Support resolving JSP scripts from the repository

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Sling Eclipse IDE 2.0.0
• Component/s: IDE
• Assignee: Unassigned
• Reporter: Robert Munteanu
• Created: 24/Nov/14 11:55
• Updated: 26/Feb/18 21:06

Description

A common pattern in Sling applications is to define several taglibs and imports in a globally included file and reference it from all JSPs, e.g.

<%@include file="/libs/foundation/global.jsp"%>

These files aren't part of the project checkout so the JSP editor will raise an error and is not able to provide auto-completion based on that global.jsp file.

We should be able to load these files from the repository, although it remains to be seen what we can do that:

• is fast
• stays in sync with changes in the repository initiated from other sources
• has an a well-defined and intuitive behaviour when the repository is not available

Issue Links

• links to: Github - Issue 25