Eclipse Community Forums: TMF (Xtext) » Issue with cyclic project dependencies

Help

Home

Home » Modeling » TMF (Xtext) » Issue with cyclic project dependencies

Show: Today's Messages :: Show Polls :: Message Navigator

Issue with cyclic project dependencies [message #1763427]

Mon, 15 May 2017 19:01

Lutz Wrage

Messages: 181
Registered: July 2009

Senior Member

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!

Report message to a moderator

Re: Issue with cyclic project dependencies [message #1763428 is a reply to message #1763427]

Mon, 15 May 2017 19:04

Christian Dietrich

Messages: 14285
Registered: July 2009

Senior Member

Sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=431608

Need professional support for Xtext, Xpand, EMF?
Go to: https://www.itemis.com/en/it-services/methods-and-tools/xtext
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

Report message to a moderator

Re: Issue with cyclic project dependencies [message #1763469 is a reply to message #1763428]

Tue, 16 May 2017 13:14

Lutz Wrage

Messages: 181
Registered: July 2009

Senior Member

We can do without cyclic dependencies. However, if a workspace ends up with cyclic dependencies I'd like to report this to the user so they know that they must fix the dependencies.
Any hints on where I could add that check such that it is executed during a build?

Report message to a moderator