Last modified of jsp should not be compared against compiled class if jsp is modified -------------------------------------------------------------------------------------
Key: SLING-1990 URL: https://issues.apache.org/jira/browse/SLING-1990 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting JSP 2.0.14 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JSP 2.0.16 If a jsp is modified: a) on observation event is sent b) if an observation event arrived, the last modified of the jsp is compared with the last modified of the compiled class (if available) If the last modified of the jsp is older, no recompilation is done. This creates unexpected results if e.g. a package is downgraded and older versions of a jsp are installed (with older last modified values). The new jsps would still be used. The last modified check is actually still there to avoid recompilation on startup. We should distinguish between the two cases: do a last modified check on startup but no last modified check based on observation events -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira