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

Project import and/or builds are hitting cyclic project errors where there are none #241

Closed
plaird opened this issue Jun 19, 2021 · 1 comment
Assignees
Labels
1.4.0 BEF 1.4.0 bug Something isn't working

Comments

@plaird
Copy link
Contributor

plaird commented Jun 19, 2021

Bazel does not allow cyclic dependencies, yet at times Eclipse will get into a state such that it detects a cycle in project dependencies from BEF managed projects. I believe there are a couple of bugs at work here.

This will appear as an error in the problem view, and there is no solution other than re-importing the workspace.

You may see this error on the BEF error log:
"Breaking out of infinite loop..."

@plaird plaird added the bug Something isn't working label Jun 19, 2021
@plaird plaird self-assigned this Jun 19, 2021
@plaird
Copy link
Contributor Author

plaird commented Jun 26, 2021

It turns out the workspace I imported did have a target level cyclic dependency, which is already tracked by #197. Closing this one.

@plaird plaird closed this as completed Jun 26, 2021
@plaird plaird added the 1.4.0 BEF 1.4.0 label Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.4.0 BEF 1.4.0 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant