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
When developing a MagicDraw plugin that uses V4MD, its corresponding Gradle-based build system that has multiple query files, cross-file query references in Eclipse stops working quite regularly: every pattern that is called from another file is marked as one that cannot be found, until the mentioned file is (e.g. by editing it directly or executing a project build). However, after a file is changed again, the issue comes back.
This issue is not strictly related the V4MD, but so far I have only seen this issue with projects that use V4MD and the Gradle-based MagicDraw builds; however, in case of a project with many queries (~700 lines of VQL files in 5 files) the issue is totally reproducible.
My theory is that for some unexpected reason the Xtext Index gets cleaned up during the build, but I have no idea why that happens, it needs further evaluation.
The text was updated successfully, but these errors were encountered:
When developing a MagicDraw plugin that uses V4MD, its corresponding Gradle-based build system that has multiple query files, cross-file query references in Eclipse stops working quite regularly: every pattern that is called from another file is marked as one that cannot be found, until the mentioned file is (e.g. by editing it directly or executing a project build). However, after a file is changed again, the issue comes back.
This issue is not strictly related the V4MD, but so far I have only seen this issue with projects that use V4MD and the Gradle-based MagicDraw builds; however, in case of a project with many queries (~700 lines of VQL files in 5 files) the issue is totally reproducible.
My theory is that for some unexpected reason the Xtext Index gets cleaned up during the build, but I have no idea why that happens, it needs further evaluation.
The text was updated successfully, but these errors were encountered: