[ 
https://issues.apache.org/jira/browse/SLING-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502577#comment-14502577
 ] 

Stefan Egli commented on SLING-4638:
------------------------------------

Yes, that it in fact already the case. Triple checking the code now for missing 
other stuff however. One detail is now fixed with 
http://svn.apache.org/r1674772 as noted below

> isCurrent() not always correctly set
> ------------------------------------
>
>                 Key: SLING-4638
>                 URL: https://issues.apache.org/jira/browse/SLING-4638
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.1.0
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Critical
>             Fix For: Discovery Impl 1.1.2
>
>
> With extending the TOPOLOGY_CHANGING phase in SLING-3432 and follow-up 
> tickets such as SLING-4634 and SLING-4635, the correctness of 
> TopologyView.isCurrent() is very important: currently it is not always 
> correctly set. This must be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to