You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/10/15 09:06:00 UTC

[jira] [Resolved] (SLING-9816) Lookup jsp includes from the class path if not found locally

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

Radu Cotescu resolved SLING-9816.
---------------------------------
    Resolution: Fixed

Implemented in [commit 3b994fe|https://github.com/apache/sling-jspc-maven-plugin/commit/3b994fe152b8df8e62164a43f73f105158f87588].

> Lookup jsp includes from the class path if not found locally
> ------------------------------------------------------------
>
>                 Key: SLING-9816
>                 URL: https://issues.apache.org/jira/browse/SLING-9816
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: JSPC Maven Plugin 2.2.2
>            Reporter: Karl Pauls
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: JSPC Maven Plugin 2.2.4
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When compiling a jsp that has an include it would be good if the jspc could try to find the included jsp from the class path if it doesn't exist locally (similar to what happens with taglibs). 
> This way, it would be possible to include jsps coming from a different project just by adding a dependency. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)