You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: