| Issue with cyclic project dependencies [message #1763427] |
Mon, 15 May 2017 15:01  |
Eclipse User |
|
|
|
In our tool we have a number of DSLs that are not Java based. So we use a StateBasedContainerManager with WorkspaceProjectsState for all languages.
In a couple of workspaces we had funny effects when linking:
- Names referencing certain EClasses are resolved properly but marked with a greyed out error marker in the text editor, anyhow.
- Names are initially resolved just fine but we get errors after a clean build.
As it turned out, the workspaces had cyclic project references. Removing the cycles fixed all these issues. We haven't been able to track down exactly how the cyclic references cause the linking service go go astray, but we want to add functionality that detects cycles and marks the projects that reference themselves (directly or indirectly) with an error.
It looks like something should be added to a build that detects cycles, but how do I add functionality like that to an Xtext build? I'd appreciate any hint.
Thanks!
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04005 seconds
Home