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 2017/03/13 08:30:04 UTC

[jira] [Resolved] (SLING-6612) HTL/Sightly sometimes fails to recompile an updated Java POJO located in the repository

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

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

Fixed in [r1786637|https://svn.apache.org/viewvc?view=revision&revision=1786637].

> HTL/Sightly sometimes fails to recompile an updated Java POJO located in the repository
> ---------------------------------------------------------------------------------------
>
>                 Key: SLING-6612
>                 URL: https://issues.apache.org/jira/browse/SLING-6612
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Sightly Engine 1.0.18
>            Reporter: Vlad Bailescu
>            Assignee: Radu Cotescu
>            Priority: Critical
>             Fix For: Scripting HTL Engine 1.0.34
>
>         Attachments: SLING-6612-test.patch
>
>
> HTL/Sightly sometimes fails to recompile an updated Java POJO located in the repository because the current implementation of the {{JavaUseProvider}} does not take into account the timestamps of the {{.java}} and {{.class}} files (and relies on {{ResourceChangeListener}} to track updates to the Java classes in the repo).
> I have attached a patch with a test that reproduces the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)