Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After the import of an existing SBuild project, workspace references are not resolved #3

Open
lefou opened this issue Feb 13, 2014 · 1 comment
Labels

Comments

@lefou
Copy link
Member

lefou commented Feb 13, 2014

After the import of an existing SBuild project, workspace references are not resolved, instead, the non-workspace resources (mostly jars) are references.

As a work around, the build file can be touched or changed. Afterwards, the classpath container will be refreshed and all available and referenced workspace projects are resolved properly from workspace.

This was first reported as SBuild-org/sbuild#138

@lefou lefou added the bug label Feb 13, 2014
@lefou
Copy link
Member Author

lefou commented Aug 18, 2014

Looks like, this is caused by the fact, that Eclipse has not built a complete Resource model for the project at the time the classpath is evaluated, which leads to a situation, that the preference store holding the workspace alias settings is empty. Hmm, I don't know the proper solution, but can imagine various workarounds, e.g. refreshing the ".settings" area programmaticaly when resolving the classpath container or listening for changes for the settings.

A fast user workaround for now is the new "Refresh SBuild Dependencies" action from #8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant