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 2016/08/26 14:29:20 UTC
[jira] [Resolved] (SLING-6005) UnitChangeMonitor should move to new
ResourceChangeListener API
[ https://issues.apache.org/jira/browse/SLING-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-6005.
---------------------------------
Resolution: Invalid
{{org.apache.sling.scripting.sightly.impl.compiler.UnitChangeMonitor}} has been renamed to {{org.apache.sling.scripting.sightly.impl.engine.ResourceBackedPojoChangeMonitor}} as part of SLING-5253, when the {{EventHandler}} implementation has also been swapped in favour of {{org.apache.sling.api.resource.observation.ResourceChangeListener}}.
> UnitChangeMonitor should move to new ResourceChangeListener API
> ----------------------------------------------------------------
>
> Key: SLING-6005
> URL: https://issues.apache.org/jira/browse/SLING-6005
> Project: Sling
> Issue Type: Task
> Components: Scripting
> Reporter: Hanish Bansal
>
> org.apache.sling.scripting.sightly.impl.compiler.UnitChangeMonitor currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API.
> See [0] for details :
> https://issues.apache.org/jira/browse/SLING-5994
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)