[jira] Updated: (FELIX-2178) Importing projects into the workspace occaisionally triggers an erroneous filter of valid exports which causes resolver to miss available providers.

["David Savage (JIRA)" <ji...@apache.org>]

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

David Savage updated FELIX-2178:
--------------------------------

    Attachment: foobar.zip

Trivial project setup - project foo exports package com.foo which project bar imports.

To see this problem first import both projects into workspace, then delete project foo and reimport it - should see that foo is not added to Bundle Context Classpath. Hitting F5 (refresh) fixes this problem...

> Importing projects into the workspace occaisionally triggers an erroneous filter of valid exports which causes resolver to miss available providers.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-2178
>                 URL: https://issues.apache.org/jira/browse/FELIX-2178
>             Project: Felix
>          Issue Type: Bug
>          Components: Sigil
>         Environment: eclipse
>            Reporter: David Savage
>            Priority: Minor
>         Attachments: foobar.zip
>
>
> When a project is imported into the workspace this triggers the WorkspaceRepository.handleChange method which in turn fires a RepositoryChangeEvent. This leads to a ResolveProjectsJob being scheduled which eventually leads to a SigilProject.resetClasspath call to resolve available dependencies. Bizarrely when this chain of events occurs the WorkspaceRepository.findPackages call that is intended to filter out "runtime" packages - i.e. packages that are not really in the source code but are aggregated from other bundles - seems to see a partial view of projects - i.e. the project exists but cannot see the source folders. I'll attach two trivial projects which demonstrate this problem.
> This problem can be fixed by simply manually refreshing projects after an import.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.