sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-4191) Support resolving JSP scripts from the repository
Date Mon, 26 Feb 2018 21:07:02 GMT

     [ https://issues.apache.org/jira/browse/SLING-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Munteanu updated SLING-4191:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.2.2)
                   Sling Eclipse IDE 1.2.4

> Support resolving JSP scripts from the repository
> -------------------------------------------------
>
>                 Key: SLING-4191
>                 URL: https://issues.apache.org/jira/browse/SLING-4191
>             Project: Sling
>          Issue Type: New Feature
>          Components: IDE
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.4
>
>
> 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.
> {code}<%@include file="/libs/foundation/global.jsp"%>{code}
> 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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message