Description Knut Wannheden 2011-11-22 04:05:20 EST

If an Xtext project contains multiple interdependent Xtext grammars a build is likely to result in linking error markers. The reason is that the Xtext language implementation doesn't use the lazy linker and all linking is already done as part of the first build phase. At this point any referenced EPackages may not yet be present in the index (e.g. when doing a clean build).

The builder is likely to keep the Xtext grammar resource in its resource set for the second build phase. Again as the lazy linker isn't used the linking errors remain.

Either the Xtext implementation should start using the lazy linker or the builder must be able to detect such situations and reload the resources in the second build phase. Or maybe both.