[
https://issues.apache.org/jira/browse/SLING-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1991.
-------------------------------------
Resolution: Fixed
Distinguishing now between the two cases, also updated the handling of reloads
and classloader checks
Revision 1074080
> Last modified of java file should not be compared against compiled class if
> file is modified
> --------------------------------------------------------------------------------------------
>
> Key: SLING-1991
> URL: https://issues.apache.org/jira/browse/SLING-1991
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting Java 2.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Scripting Java 2.0.2
>
>
> If a java file is modified:
> a) on observation event is sent
> b) if an observation event arrived, the last modified of the java file is
> compared with the last modified of the compiled class (if available)
> If the last modified of the java file is older, no recompilation is done.
> This creates unexpected results if e.g. a package is downgraded and older
> versions of a java file are installed (with older last modified values). The
> new java files 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
