[jira] [Resolved] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

["Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org>]

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

Felix Meschberger resolved SLING-2296.
--------------------------------------

    Resolution: Fixed

The build failures are now fixed (thus the events are sent) and so this resolves this issue.
                
> Transient ResourceResolver bundle build failure on Linux
> --------------------------------------------------------
>
>                 Key: SLING-2296
>                 URL: https://issues.apache.org/jira/browse/SLING-2296
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.10
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Resource 2.1.0
>
>
> Often times I get build failures of the JCR ResourceResolver Bundle:
>   testDefaultWorkspace(org.apache.sling.jcr.resource.internal.JcrResourceListenerTest): expected:<3> but was:<1>
>   testInWs2(org.apache.sling.jcr.resource.internal.JcrResourceListenerTest): expected:<3> but was:<1>
> Looking and tracing the code it seems that the JcrResourceListener gets the JCR events and handles them correctly. But the sendOsgiEvent method does not actually forward the event. This is caused by the JcrResourceListener's internal resource resolver not (yet ?) knowing the added or changed resource and thus not being able to read it to get the resource type.
> The sendOsgiEvent method should be modified to make sure the event is sent regardless of whether the resource type can be resolved or not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira